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
⌀ |
|---|---|---|---|---|---|---|---|
5,701 | 23.3.2.3.3 Security Gateway | The Security Gateway (SeGW) FQDN shall be derived as follows. The "segw" <system> label is added in front of the operator's OAM realm domain name: segw.oam.mnc<MNC>.mcc<MCC>.3gppnetwork.org If particular operator deployment scenarios where there are multiple Security Gateways (one per vendor), the <vendor ID> label is added in front of the "segw" label: vendor<ViD>.segw.oam.mnc<MNC>.mcc<MCC>.3gppnetwork.org An example of a SeGW FQDN is: MCC = 123; MNC = 45; ViD = abcd; which gives the SeGW FQDN: "segw.oam.mnc045.mcc123.3gppnetwork.org" and "vendorabcd.segw.mnc045.mcc123.3gppnetwork.org". | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 23.3.2.3.3 |
5,702 | 7.8.1G Minimum requirements | The throughput shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annex A.8.2 with parameters specified in Table 7.8.1G-1 for the specified wanted signal mean power in the presence of two interfering signals Table 7.8.1G-1: Wide band intermodulation When UE is configured for simultaneous E-UTRA V2X sidelink and E-UTRA downlink reception for inter-band E-UTRA V2X / E-UTRA bands specified in Table 5.5G-2, the requirements in subclause 7.8.1G apply for the E-UTRA V2X sidelink reception and the requirements in subclause 7.8.1 apply for the E-UTRA downlink reception while all downlink carriers are active. For intra-band contiguous multi-carrier operation, the V2X UE throughput shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annex A.8.2 with parameters specified in Table 7.8.1G-2 for the specified wanted signal mean power in the presence of two interfering signals. Table 7.8.1G-2: Wide band intermodulation for intra-band contiguous multi-carrier for V2X UE | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 7.8.1G |
5,703 | 8.62 Fully qualified PDN Connection Set Identifier (FQ-CSID) | A fully qualified PDN Connection Set Identifier (FQ-CSID) identifies a set of PDN connections belonging to an arbitrary number of UEs on a MME, SGW, TWAN, ePDG or PGW. The FQ-CSID is used on S5, S8, S2a, S2b and S11 interfaces. The size of CSID is two octets. The FQ-CSID is coded as follows: Figure 8.62-1: FQ-CSID Where Node-ID Type values are: 0 indicates that Node-ID is a global unicast IPv4 address and p = 9. 1 indicates that Node-ID is a global unicast IPv6 address and p = 21. 2 indicates that Node-ID is a 4 octets long field with a 32 bit value stored in network order, and p= 9. The coding of the field is specified below: - Most significant 20 bits are the binary encoded value of (MCC * 1000 + MNC). - Least significant 12 bits is a 12 bit integer assigned by an operator to an MME, SGW, TWAN, ePDG or PGW. Other values of Node-ID Type are reserved. Values of Number of CSID other than 1 are only employed in the Delete PDN Connection Set Request. The node that creates the FQ-CSID, (i.e. MME for MME FQ-CSID, SGW for SGW FQ-CSID, TWAN for TWAN FQ-CSID, ePDG for ePDG FQ-CSID and PGW for PGW FQ-CSID), is responsible for making sure the Node-ID is globally unique and the CSID value is unique within that node. When a FQ-CSID is stored by a receiving node, it is stored on a PDN basis even for messages impacting only one bearer (i.e. Create Bearer Request). See 3GPP TS 23.007[ Restoration procedures ] [17] for further details on the CSID and what specific requirements are placed on the PGW, TWAN, ePDG, SGW and MME. | 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.62 |
5,704 | 6.5.2G.3 In-band emissions | For V2X sidelink physical channels PSCCH, PSSCH and PSBCH, the In-band emissions requirements shall be as specified for PUSCH in subclause 6.5.2.3 for the corresponding modulation and transmission bandwidth. When V2X transmissions are shortened due to transmission gap of 1 symbol at the end of the subframe, the In-band emissions measurement interval is reduced by one symbol, accordingly. For intra-band contiguous multi-carrier operation the in-band emission requirement of subcaluse 6.5.2A.3 shall apply. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.5.2G.3 |
5,705 | 8.3.1 Centralized Retransmission in Intra gNB-CU Cases | This mechanism allows to perform the retransmission of the PDCP PDUs that are not delivered by a gNB-DU (gNB-DU1) because the corresponding radio links toward the UE are subject to outage. When such outage occurs, the gNB-DU affected by outage informs the gNB-CU of such event. The gNB-CU can switch transmission of data traffic, as well as perform retransmission of undelivered PDCP PDUs, from the gNB-DU affected by outage to other available gNB-DUs (e.g. gNB-DU2 in Figure 8.3.1-1) with a well-functioning radio link toward the UE. The mechanism is also applicable in EN-DC and MR-DC with 5GC, refer to TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [12]. Figure 8.3.1-1: Procedure for centralized retransmission in intra gNB-CU scenarios The mechanism is shown in Figure 8.3.1-1 and targets the multi-connectivity scenario, where a UE is served by multiple data radio bearers established at least on two gNB-DUs, and it includes the following steps: 0. The UE is connected and can transmit/receive data to/from gNB-DU1 and gNB-DU2. 1. gNB-DU1 realizes that the radio link towards the UE is experiencing outage. 2. gNB-DU1 sends the "Radio Link Outage" notification message to the gNB-CU over the F1-U interface, as part of the DDDS PDU of the concerned data radio bearer. The message may include information to be used by the gNB-CU to perform retransmission of the PDCP PDUs that were not delivered by the gNB-DU1 (e.g. the highest transmitted NR PDCP Sequence Number, the highest successfully delivered NR PDCP Sequence Number and the lost NR-U Sequence Numbers). 3. gNB-CU decides to switch data traffic transmission and retransmission of PDCP PDUs that were undelivered in gNB-DU1 via gNB-DU2. gNB-CU stops sending downlink traffic to gNB-DU1. The radio leg between gNB-DU1 and the UE is not necessarily removed. 4. gNB-CU starts sending traffic (namely new PDUs and potentially retransmitted PDUs) to gNB-DU2. 5. If gNB-DU1 realizes that the radio link of the concerned data radio bearer is back in normal operation, it may send a "Radio Link Resume" notification message as part of the DDDS PDU over the F1-U interface to inform the gNB-CU that the radio link can be used again for the concerned data radio bearer. 6. gNB-CU may start sending traffic (namely new PDUs and potentially retransmitted PDUs) of the concerned data radio bearer via gNB-DU1 again. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.3.1 |
5,706 | 4.2.8.5.2 Reference Architecture | The architecture diagram in Figure 4.2.8.5.2-1 is based on the general 5GS architecture diagrams in clause 4.2 and shows the main network functions required to support 5GC access from N5CW devices. Other network functions are not shown for simplicity. Figure 4.2.8.5.2-1: Non-roaming and LBO Roaming Architecture for supporting 5GC access from N5CW devices The reference architecture in Figure 4.2.8.5.2-1 also supports N5CW device access to the subscribed SNPN or access to the SNPN with credentials owned by Credentials Holder. Other parts of the architecture are the same as defined in clause 5.30.2.9. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.8.5.2 |
5,707 | 9.3.2 EPS bearer identity | Bits 5 to 8 of the first octet of every EPS Session Management (ESM) message contain the EPS bearer identity. The EPS bearer identity and its use to identify a message flow are defined in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12]. If the UE or the MME or both do not support signalling for a maximum number of 15 EPS bearer contexts, the MME shall select the EPS bearer identity from the value range 5 to 15, or select the value 0 when it needs to indicate that no EPS bearer identity is assigned. NOTE: When assigning EPS bearer identities from the range 1 to 4, the MME can take into account that these EPS bearer contexts will be subject to local deactivation if the UE performs inter-system change to A/Gb mode or Iu mode or if it performs a change to an MME not supporting signalling for a maximum number of 15 EPS bearer contexts. | 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.3.2 |
5,708 | – UE-MeasurementsAvailable | The IE UE-MeasurementsAvailable is used to indicate all relevant available indicators for UE measurements. UE-MeasurementsAvailable information element -- ASN1START -- TAG-UE-MeasurementsAvailable-START UE-MeasurementsAvailable-r16 ::= SEQUENCE { logMeasAvailable-r16 ENUMERATED {true} OPTIONAL, logMeasAvailableBT-r16 ENUMERATED {true} OPTIONAL, logMeasAvailableWLAN-r16 ENUMERATED {true} OPTIONAL, connEstFailInfoAvailable-r16 ENUMERATED {true} OPTIONAL, rlf-InfoAvailable-r16 ENUMERATED {true} OPTIONAL, ..., [[ successHO-InfoAvailable-r17 ENUMERATED {true} OPTIONAL, sigLogMeasConfigAvailable-r17 BOOLEAN OPTIONAL ]], [[ successPSCell-InfoAvailable-r18 ENUMERATED {true} OPTIONAL ]] } -- TAG-UE-MeasurementsAvailable-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,709 | D.8.4 Unknown or unforeseen message type | If the UE or the network receives a UPDS message with message type not defined for the UPDS or not implemented by the receiver, it shall ignore the UPDS message. NOTE: A message type not defined for the UPDS in the given direction is regarded by the receiver as a message type not defined for the UPDS, see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [11]. If the UE receives a message not compatible with the UPDS state, the UE shall ignore the UPDS message. If the network receives a message not compatible with the UPDS state, the network actions are implementation dependent. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | D.8.4 |
5,710 | 4.2.10.1 UE triggered N3 data transfer establishment procedure | If UE and AMF successfully negotiate N3 data transfer in addition to Control Plane CIoT 5GS Optimisation based on the Preferred and Supported Network Behaviour as defined in clause 5.31.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], then the UE may, e.g. based on the amount of data to be transferred in uplink, initiate N3 data transfer establishment procedure for any PDU session for which Control Plane Only Indicator was not included. The UE triggered N3 data transfer establishment procedure may be initiated by the UE in CM-IDLE or CM-CONNECTED state and follows the UE triggered Service Request procedure as defined in clause 4.2.3.2 with the following differences. Step 1. The UE includes in the AN message a Service Request for Control Plane CIoT 5GS Optimisation (List Of PDU Sessions To Be Activated, List Of Allowed PDU Sessions, security parameters, PDU Session status, [NAS message container])). The List Of PDU Sessions To Be Activated is provided by UE when the UE wants to activate user plane resources for the PDU Session(s). The UE shall not include PDU sessions for which Control Plane Only Indicator was received in the List Of PDU Sessions To Be Activated. If the UE is camping on NB-IoT, the UE shall construct the List of PDU Sessions To Be Activated to not exceed 2 PDU session(s) with active user plane resources. If this procedure is triggered for paging response and the UE has at the same time some user data to be transferred, the UE may decide to request N3 data transfer establishment for one of more PDU sessions. The UE indicates this in the List Of PDU Sessions To Be Activated. Otherwise the UE does not identify any PDU Session in the List Of PDU Sessions To Be Activated. Step 4 or 5a. Upon reception of Nsmf_PDUSession_UpdateSMContext Request or after SMF initiated SM Policy Association Modification, based on UE request and local policies, the SMF decides whether to establish N3 data transfer for the PDU session. The SMF shall not decide to establish N3 data transfer for a PDU session for which Control Plane Only Inidcator was received. Step 11. The SMF indicates in Nsmf_PDUSession_UpdateSMContext Response whether to establish N3 data transfer, i.e. activate Data Radio Bearer and N3 tunnel, for the PDU session. Step 12. If the RAT type is NB-IoT, the AMF shall ensure that number of PDU Sessions with active user plane resources does not exceed 2. If the AMF decides to not include a PDU Session to be activated in the N2 message, the AMF indicates this to the SMF in step 15 Nsmf_PDUSession_UpdateSMContext Request in the List of PDU Sessions that failed to be established with the failure cause given in the N2 SM information element. The AMF includes a NAS service accept for Control Plane CIoT 5GS Optimisation containing information on the PDU sessions with established N3 data transfer, based on the request(s) from the SMF(s) in step 11. The network starts using N3 bearers for all DL data on this PDU session. Control Plane CIoT 5GS Optimisation is considered enabled for data transfer for all PDU sessions without established N3 data transfer. Step 13. The UE starts using N3 bearears for all UL data on this PDU session. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.10.1 |
5,711 | 6.1.3.1 Authentication procedure for EAP-AKA' | EAP-AKA' is specified in RFC 5448 [12]. The 3GPP 5G profile for EAP-AKA' is specified in the normative Annex F. The selection of using EAP-AKA' is described in sub-clause 6.1.2 of the present document. Figure 6.1.3.1-1: Authentication procedure for EAP-AKA' The authentication procedure for EAP-AKA' works as follows, cf. also Figure 6.1.3.1-1: 1. The UDM/ARPF shall first generate an authentication vector with Authentication Management Field (AMF) separation bit = 1 as defined in TS 33.102[ 3G security; Security architecture ] [9]. The UDM/ARPF shall then compute CK' and IK' as per the normative Annex A and replace CK and IK by CK' and IK'. 2. The UDM shall subsequently send this transformed authentication vector AV' (RAND, AUTN, XRES, CK', IK') to the AUSF from which it received the Nudm_UEAuthentication_Get Request together with an indication that the AV' is to be used for EAP-AKA' using a Nudm_UEAuthentication_Get Response message. NOTE: The exchange of a Nudm_UEAuthentication_Get Request message and an Nudm_UEAuthentication_Get Response message between the AUSF and the UDM/ARPF described in the preceding paragraph is the same as for trusted access using EAP-AKA' described in TS 33.402[ 3GPP System Architecture Evolution (SAE); Security aspects of non-3GPP accesses ] [11], sub-clause 6.2, step 10, except for the input parameter to the key derivation, which is the value of <network name>. The "network name" is a concept from RFC 5448 [12]; it is carried in the AT_KDF_INPUT attribute in EAP-AKA'. The value of <network name> parameter is not defined in RFC 5448 [12], but rather in 3GPP specifications. For EPS, it is defined as "access network identity" in TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [71], and for 5G, it is defined as "serving network name" in sub-clause 6.1.1.4 of the present document. In case SUCI was included in the Nudm_UEAuthentication_Get Request, UDM will include the SUPI in the Nudm_UEAuthentication_Get Response. If a subscriber has an AKMA subscription, the UDM shall include the AKMA indication and Routing indicator in the Nudm_UEAuthentication_Get Response. 3. The AUSF shall send the EAP-Request/AKA'-Challenge message to the SEAF in a Nausf_UEAuthentication_Authenticate Response message. 4. The SEAF shall transparently forward the EAP-Request/AKA'-Challenge message to the UE in a NAS message Authentication Request message. The ME shall forward the RAND and AUTN received in EAP-Request/AKA'-Challenge message to the USIM. This message shall include the ngKSI and ABBA parameter. In fact, SEAF shall include the ngKSI and ABBA parameter in all EAP-Authentication request message. The ngKSI will be used by the UE and AMF to identify the partial native security context that is created if the authentication is successful. The SEAF shall set the ABBA parameter as defined in Annex A.7.1. During an EAP authentication, the value of the ngKSI and the ABBA parameter sent by the SEAF to the UE shall not be changed. NOTE 1: The SEAF needs to understand that the authentication method used is an EAP method by evaluating the type of authentication method based on the Nausf_UEAuthentication_Authenticate Response message. 5. At receipt of the RAND and AUTN, the USIM shall verify the freshness of the AV' by checking whether AUTN can be accepted as described in TS 33.102[ 3G security; Security architecture ] [9]. If so, the USIM computes a response RES. The USIM shall return RES, CK, IK to the ME. If the USIM computes a Kc (i.e. GPRS Kc) from CK and IK using conversion function c3 as described in TS 33.102[ 3G security; Security architecture ] [9], and sends it to the ME, then the ME shall ignore such GPRS Kc and not store the GPRS Kc on USIM or in ME. The ME shall derive CK' and IK' according to Annex A.3. If the verification of the AUTN fails on the USIM, then the USIM and ME shall proceed as described in sub-clause 6.1.3. 3. 6. The UE shall send the EAP-Response/AKA'-Challenge message to the SEAF in a NAS message Auth-Resp message. 7. The SEAF shall transparently forward the EAP-Response/AKA'-Challenge message to the AUSF in Nausf_UEAuthentication_Authenticate Request message. 8. The AUSF shall verify the message by comparing the XRES and RES, and if the AUSF has successfully verified this message it shall continue as follows, otherwise it shall return an error to the SEAF. AUSF shall inform UDM about the authentication result (see sub-clause 6.1.4 of the present document for details on linking authentication confirmation). 9. The AUSF and the UE may exchange EAP-Request/AKA'-Notification and EAP-Response /AKA'-Notification messages via the SEAF. The SEAF shall transparently forward these messages. NOTE 2: EAP Notifications as described in RFC 3748 [27] and EAP-AKA Notifications as described in RFC 4187 [21] can be used at any time in the EAP-AKA exchange. These notifications can be used e.g. for protected result indications or when the EAP server detects an error in the received EAP-AKA response. 10. The AUSF derives EMSK from CK’ and IK’ as described in RFC 5448[12] and Annex F. The AUSF uses the most significant 256 bits of EMSK as the KAUSF and then calculates KSEAF from KAUSF as described in clause A.6. The AUSF shall send an EAP Success message to the SEAF inside Nausf_UEAuthentication_Authenticate Response, which shall forward it transparently to the UE. Nausf_UEAuthentication_Authenticate Response message contains the KSEAF. If the AUSF received a SUCI from the SEAF when the authentication was initiated (see sub-clause 6.1.2 of the present document), then the AUSF shall also include the SUPI in the Nausf_UEAuthentication_Authenticate Response message. The AUSF stores the KAUSF based on the home network operator's policy according to clause 6.1.1.1. NOTE 3: For lawful interception, the AUSF sending SUPI to SEAF is necessary but not sufficient. By including the SUPI as input parameter to the key derivation of KAMF from KSEAF, additional assurance on the correctness of SUPI is achieved by the serving network from both, home network and UE side. 11. The SEAF shall send the EAP Success message to the UE in the N1 message. This message shall also include the ngKSI and the ABBA parameter. The SEAF shall set the ABBA parameter as defined in Annex A.7.1. NOTE 4: Step 11 could be NAS Security Mode Command or Authentication Result. NOTE 5: The ABBA parameter is included to enable the bidding down protection of security features that may be introduced later. The key received in the Nausf_UEAuthentication_Authenticate Response message shall become the anchor key, KSEAF in the sense of the key hierarchy in sub-clause 6.2 of the present document. The SEAF shall then derive the KAMF from the KSEAF, the ABBA parameter and the SUPI according to Annex A.7 and send it to the AMF. On receiving the EAP-Success message, the UE derives EMSK from CK’ and IK’ as described in RFC 5448 and Annex F. The ME uses the most significant 256 bits of the EMSK as the KAUSF and then calculates KSEAF in the same way as the AUSF. The UE shall derive the KAMF from the KSEAF, the ABBA parameter and the SUPI according to Annex A.7. NOTE 6: As an implementation option, the UE creates the temporary security context as described in step 11 after receiving the EAP message that allows EMSK to be calculated. The UE turns this temporary security context into a partial security context when it receives the EAP Success. The UE removes the temporary security context if the EAP authentication fails. The further steps taken by the AUSF upon receiving a successfully verified EAP-Response/AKA'-Challenge message are described in sub-clause 6.1.4 of the present document. If the EAP-Response/AKA'-Challenge message is not successfully verified, the subsequent AUSF behaviour is determined according to the home network's policy. If AUSF and SEAF determine that the authentication was successful, then the SEAF provides the ngKSI and the KAMF to the AMF. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.1.3.1 |
5,712 | 8.121 ECGI List | MBMS Cell List is an extendable IE that is coded as depicted in Figure 8.120-1. The ECGI identity types are defined in 3GPP TS 23.003[ Numbering, addressing and identification ] [2]. Figure 8.121-1: ECGI List The Number of ECGI Fields shall indicate the number of ECGI fields in the ECGI List. In the present version of this specification, the Length n shall be set to m times 7 plus 2. The ECGI List shall consist of m ECGI fields. Each ECGI field shall be encoded as specified in clause 8.21.5 and thus is 7 octets long. | 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.121 |
5,713 | 6.39.3 Service Exposure | Requirements in this clause are subject to regulatory requirements and operator policy. The 5G system shall provide means to allow a trusted third-party to update the multimedia telephony service subscription and allocate a third-party specific identity to an authorized user. NOTE: The third party is authorized to change user identities for those subscriptions authorized by the operator. The following requirements apply to the originating side: - The 5G network shall provide a means for third parties (e.g. enterprises) to be authorized to verify the use of calling identity information by its authorized users. - The 5G network shall provide a means for authorized third parties to verify that an authenticated user is authorized to include or reference the pre-established calling identity information included in the call setup or retrieved by the called party. - The 5G network shall provide a means to verify the authenticity of the pre-established stored identity information that is referenced by the call setup and retrieved by the called party. The following requirements apply to the terminating side. - The 5G network shall provide a means for third parties (e.g. enterprises) to be able to verify the caller’s authorization to use the identity information either in addition to or instead of verification performed by the terminating PLMN. - The 5G network shall provide a means to verify the authenticity of any stored identity information referenced by the call setup to be presented to the called party. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.39.3 |
5,714 | 6.2.6 Local area data network (LADN) | The UE can receive the local area data network (LADN) information consisting of LADN DNNs and LADN service area information (a set of tracking areas that belong to the current registration area) during the registration procedure or the generic UE configuration update procedure (see subclause 5.5.1 and subclause 5.4.4). If the UE supports LADN per DNN and S-NSSAI, the UE can additionally receive the extended local area data network (LADN) information consisting of LADN DNNs, S-NSSAIs and LADN service area information (a set of tracking areas configured per DNN and S-NSSAI that belong to the current registration area) during the registration procedure or the generic UE configuration update procedure (see subclause 5.5.1 and subclause 5.4.4). If the UE is not operating in SNPN access operation mode, the UE considers the received LADN information or the extended LADN information to be valid only in the TAIs of the registered PLMN that are in the LADN service area information, and in the TAIs of the equivalent PLMNs if the LADN service area information includes TAIs for the equivalent PLMNs. When the AMF provides the UE with LADN service area information containing TAIs for the equivalent PLMNs, the AMF shall include these TAIs of the equivalent PLMNs in the UE's registration area. If the UE is operating in SNPN access operation mode, the UE considers the received LADN information or the extended LADN information to be valid only in the TAIs of the registered SNPN that are in the LADN service area information. The LADN DNN(s) received by the UE is also considered as LADN DNN(s) in the equivalent PLMNs. The UE shall consider itself to be located inside the LADN service area based on the LADN service area information. If the UE does not have anLADN service area information for the LADN DNN, the UE shall consider itself to be located outside the LADN service area. When the UE is located in the LADN service area and the UE is in substate 5GMM-REGISTERED.NORMAL-SERVICE, the UE may initiate: - the UE-requested PDU session establishment procedure with an LADN DNN to establish a PDU session for LADN; - the UE-requested PDU session establishment procedure with an LADN DNN and an S-NSSAI associated with the LADN to establish a PDU session for LADN if the extended LADN information is available at the UE; - the UE-requested PDU session modification procedure to modify the PDU session for LADN; - the service request procedure to re-establish the user-plane resources for the PDU session for LADN; or - the service request procedure or the UE-initiated NAS transport procedure to send CIoT user data via the control plane for a PDU session for LADN. NOTE 1: If the Service area list IE and at least one of the LADN information IE or the Extended LADN information IE was received by the UE, the Service area list IE is evaluated first. NOTE 1A: If the Extended LADN information IE was received with either the Partially allowed NSSAI IE or the Partially rejected NSSAI IE by the UE, the Partially allowed NSSAI IE or the Partially rejected NSSAI IE is evaluated first. When the UE is located outside the LADN service area, the UE is allowed: - to initiate the UE-requested PDU session release procedure to release a PDU session for LADN; or - to initiate the UE-requested PDU session modification procedure to indicate a change of 3GPP PS data off UE status. The AMF shall determine the UE presence in LADN service area as out of the LADN service area in the following cases: - if the DNN used for the LADN is included in the LADN information and the UE is located outside the LADN service area indicated in the LADN information; - if the DNN and the S-NSSAI used for the LADN are included in the extended LADN information and the UE is located outside the LADN service area indicated in the extended LADN information; - if the DNN used for the LADN is included in the extended LADN information and there is no S-NSSAI provided by the UE to establish a PDU session for LADN; or - if the DNN used for the LADN is included in the extended LADN information and the S-NSSAI provided by the UE to establish a PDU session for LADN is not associated with that LADN. If the UE has moved out of the LADN service area: a) the SMF shall: 1) release the PDU session for LADN; or 2) release the user-plane resources for the PDU session for LADN and maintain the PDU session for LADN; according to operator's policy; and b) the SMF shall not initiate the transfer of CIoT user data via the control plane to the UE for the PDU session for LADN. In case a2) and b): - if the UE has returned to the LADN service area, and the network has downlink user data pending, the network re-establishes the user-plane resources for the PDU session for LADN; - if the UE has returned to the LADN service area, and the network has downlink CIoT user data pending, the SMF shall initiate the CIoT user data via the control plane transfer to the UE; and - if the UE has not returned to the LADN service area after a period of time according to operator's policy, the SMF may release the PDU session for LADN. When the UE moves to 5GMM-DEREGISTERED state, the UE shall delete the stored LADN information, if any, and the stored extended LADN information, if any. NOTE 2: In this release, LADNs apply only to 3GPP access. Upon inter-system change from N1 mode to S1 mode in EMM-IDLE mode, the UE shall not transfer a PDU session for LADN to EPS. | 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.6 |
5,715 | 5.18 Recommended Bit Rate | The recommended bit rate procedure is used to provide the MAC entity with information about the bit rate which the eNB recommends. The bit rate is the recommended bit rate of the physical layer. Averaging window of default value 2000 ms will apply, as specified in TS 26.114[ IP Multimedia Subsystem (IMS); Multimedia telephony; Media handling and interaction ] [16]. The eNB may transmit the Recommended bit rate MAC control element to the MAC entity to indicate the recommended bit rate for the UE for a specific logical channel and a specific direction (either uplink or downlink). Upon reception of a Recommended bit rate MAC control element the MAC entity shall: - indicate to upper layers the recommended bit rate for the indicated logical channel and direction The MAC entity may request the eNB to indicate the recommended bit rate for a specific logical channel and a specific direction. If the MAC entity is requested by upper layers to query the eNB for the recommended bit rate for a logical channel and for a direction (i.e. for uplink or downlink), the MAC entity shall: - if a Recommended bit rate query for this logical channel and this direction has not been triggered: - trigger a Recommended bit rate query for this logical channel, direction, and desired bit rate. If the MAC entity has UL resources allocated for new transmission for this TTI the MAC entity shall: - for each Recommended bit rate query that the Recommended Bit Rate procedure determines has been triggered and not cancelled: - if bitRateQueryProhibitTimer for the logical channel and the direction of this Recommended bit rate query is configured, and it is not running; and - if the MAC entity has UL resources allocated for new transmission for this TTI and the allocated UL resources can accommodate a Recommended bit rate MAC control element plus its subheader as a result of logical channel prioritization: - instruct the Multiplexing and Assembly procedure to generate the Recommended bit rate MAC control element for the logical channel and the direction of this Recommended bit rate query; - start the bitRateQueryProhibitTimer for the logical channel and the direction of this Recommended bit rate query - cancel this Recommended bit rate query. | 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.18 |
5,716 | 8.98 Change to Report Flags | Change to Report Flags IE is coded as depicted in Figure 8.98-1. Figure 8.98-1: Change to Report Flags For each message the applicable flags of the Change to Report Flags IE shall be clearly specified in the individual message clause. The remaining flags of the Change to Report Flags IE not so indicated shall be discarded by the receiver. The receiver shall consider the value of the applicable flags as "0", if the Change to Report Flags IE is applicable for the message but not included in the message by the sender. The following bits within Octet 5 shall indicate: - Bit 8 to 3 – Spare, for future use and set to zero. - Bit 2 – TZCR (Time Zone Change to Report): When set to 1, this bit indicates that a UE Time Zone change still needs to be reported to the SGW/PGW. - Bit 1 – SNCR (Serving Network Change to Report): When set to 1, this bit indicates that a Serving Network change still need to be reported to the SGW/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 | 8.98 |
5,717 | 5.31.8 High latency communication | Functions for High latency communication may be used to handle mobile terminated (MT) communication with UEs being unreachable while using power saving functions as specified in clause 5.31.7 or due to discontinuous coverage as described in clause 5.4.13. "High latency" refers to the initial response time before normal exchange of packets is established. That is, the time it takes before a UE has woken up from its power saving state and responded to an initial downlink packet or signal. When a NR RedCap UE requests to use the power saving functions as specified in clause 5.31.7, then the AMF may, based on local policy, reroute the Registration Request to another AMF that supports High latency communication as specified in clause 6.3.5. High latency communication is supported by extended buffering of downlink data in the UPF, SMF or NEF when a UE is using power saving functions in CM-IDLE state or in RRC_INACTIVE state, or when the UE is using a satellite access with discontinuous coverage and the UE is not reachable. For UPF anchored PDU sessions the SMF configures during AN release or when NG-RAN indicates via the AMF the UE is in extended DRX for RRC_INACTIVE, the UPF with user data Forwarding Action Rule and user data Buffering Action Rule according to TS 29.244[ Interface between the Control Plane and the User Plane nodes ] [65]. The rules include instructions whether UPF buffering applies or the user data shall be forwarded to the SMF for buffering in the SMF. For NEF anchored PDU sessions only extended buffering in the NEF is supported in this release of the specification. During the Network Triggered Service Request procedure or Mobile Terminated Data Transport procedures when using Control Plane CIoT 5GS Optimisation, the AMF provides an Estimated Maximum Wait Time to the SMF if the SMF indicates the support of extended buffering. The SMF determines the Extended Buffering Time based on the received Estimated Maximum Wait Time or local configuration. The handling is e.g. specified in the Network Triggered Service Request procedure, clauses 4.2.3.3, 4.2.6, 4.24.2 and 4.25.5 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. High latency communication is also supported through notification procedures. The following procedures are available based on different monitoring events: - UE Reachability; - Availability after DDN failure; - Downlink Data Delivery Status. An AF may request a one-time "UE Reachability" notification when it wants to send data to a UE which is using a power saving function (see event subscription procedure in clause 4.15.3.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). The SCS/AS/AF then waits with sending the data until it gets a notification that the UE is reachable (see notification procedures in TS 23.502[ Procedures for the 5G System (5GS) ] [3]). An AF may request repeated "Availability after DDN failure" notifications where each UE reachability notification is triggered by a preceding DDN failure, i.e. the AF sends a downlink packet to request a UE reachability notification when the UE becomes reachable. That downlink packet is discarded by the UPF or SMF or NEF (see notification procedures in TS 23.502[ Procedures for the 5G System (5GS) ] [3]). An AF may request repeated "Downlink Data Delivery Status" notifications when it wants indications that DL data has been buffered or when buffered DL data has been delivered to the UE. If MICO mode or extended idle mode DRX is enabled, Idle Status Indication allows the AF to determine when the UE transitions into idle mode. When requesting to be informed of either "UE Reachability" or "Availability after DDN failure" notification, the AF may also request Idle Status Indication. If the UDM and the AMF support Idle Status Indication, then when the UE for which MICO mode or extended idle mode DRX is enabled transitions into idle mode, the AMF includes in the notification towards the NEF the time at which the UE transitioned into idle mode, the active time and the periodic registration update timer granted to the UE by the AMF, the eDRX cycle length and the Suggested number of downlink packets if a value was provided to the SMF. An AF may provide parameters related to High latency communication for different methods to UDM, via NEF, as part of provisioning capability as specified in clause 5.20. The UDM can further deliver the parameters to other NFs (e.g. AMF or SMF) as specified in clause 4.15.6 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. If the AMF is aware that some signalling or data is pending in the network for an UE that is known as being unreachable for a long duration, e.g. for UE's having extended idle mode DRX, extended DRX for RRC_INACTIVE or MICO enabled, the AMF maintains the N2 connection for at least the Extended Connected Time and provides the Extended Connected Time value in a NG-AP message to the RAN. The Extended Connected Time value indicates the minimum time the RAN should keep the UE in RRC_CONNECTED state regardless of inactivity. At inter-RAN node handovers, if some signalling or data are still pending, the target AMF may send the Extended Connected Time value to the target RAN node. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.31.8 |
5,718 | 4.3.2.1 Authentication request by the network | The network initiates the authentication procedure by transferring an AUTHENTICATION REQUEST message across the radio interface and starts the timer T3260. The AUTHENTICATION REQUEST message contains the parameters necessary to calculate the response parameters (see 3GPP TS 43.020[ Security related network functions ] [13] (in case of GSM authentication challenge) and 3GPP TS 33.102[ 3G security; Security architecture ] [5a] (in case of an UMTS authentication challenge)). In a GSM authentication challenge, the AUTHENTICATION REQUEST message also contains the GSM ciphering key sequence number allocated to the key which may be computed from the given parameters. In a UMTS authentication challenge, the AUTHENTICATION REQUEST message also contains the ciphering key sequence number allocated to the key set of UMTS ciphering key, UMTS integrity key and GSM ciphering key which may be computed from the given parameters. Furthermore, the ciphering key sequence number is also linked to a GSM Kc128 if after the authentication procedure the network in A/Gb mode selects an A5 ciphering algorithm that requires a 128-bit ciphering key. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.3.2.1 |
5,719 | A.15 Monitoring of common LAs of overlapping target RAT’s coverage | For CS fallback in EPS, as defined in section 5.1A of 3GPP TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [17], the fallback procedure is likely to be faster if the network can allocate a Location Area to the UE that is the LA of the overlapping target RAT's coverage. For this situation, the MME should avoid allocating TAI lists that span multiple Location Areas of the target RAT, this can be achieved by: - configuring the E-UTRAN cell's TAI to align the LA boundary of the target RAT; - the MME being configured to know which TAIs are within which LA; and - the MME using the TAI of the current E-UTRAN cell to derive the LAI. Also as specified in section 4.3.4 of 3GPP TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [17], to facilitate the alignment of TA boundaries with LA boundaries, the E-UTRAN can gather statistics (from the inbound inter-RAT mobility events of all UEs) of the most common LAs indicated in the RRC signalling. From such measurements per E-UTRAN cell basis, operators 1) can know the common LA(s) of the overlapping target RAT’s coverage for each TA, which is useful to configure the TAI list within which LA boundary to MME, operators can also 2) detect the case that TA spans multiple LAs if different most common LA(s) is/are reported from the E-UTRAN cells in the same TA, operators may take actions to rectify it if needed. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | A.15 |
5,720 | 6.5.4.1 COUNT-I | The integrity sequence number COUNT-I is 32 bits long. For signalling radio bearers (RB 0-4) there is one COUNT-I value per up-link signalling radio bearer and one COUNT-I value per down-link signalling radio bearer. COUNT-I is composed of two parts: a "short" sequence number and a "long" sequence number. The "short" sequence number forms the least significant bits of COUNT-I while the "long" sequence number forms the most significant bits of COUNT-I. The "short" sequence number is the 4-bit RRC sequence number (RRC SN) that is available in each RRC PDU. The "long" sequence number is the 28-bit RRC hyper frame number (RRC HFN) which is incremented at each RRC SN cycle. Figure 16a: The structure of COUNT-I The RRC HFN is initialised by means of the parameter START, which is described in section 6.4.8. The ME and the RNC then initialise the 20 most significant bits of the RRC HFN to START; the remaining bits of the RRC HFN are initialised to 0. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.5.4.1 |
5,721 | B.2.2 Revocation of subscriber certificates | Subscriber certificates that are used with EAP-TLS typically include static validity times. A certificate revocation list (CRL) as specified in RFC 5280 [48] and online certificate status protocol (OCSP) as specified in RFC 6960 [49] are means for the issuing certificate authority (CA) to revoke the certificates before their scheduled expiration date. In 5G security architecture, the UDM/ARPF is responsible for such subscriber status information. EAP-TLS peers and servers may also support Certificate Status Requests (OCSP stapling) as specified in RFC6066 [50] which allows peers to request the server's copy of the current status of certificates. The deployment of CRLs is demonstrated in figure B.2.2-1. When the UDM/ARPF maintains the CRLs, the lists may be periodically updated to AUSFs, and stored locally in AUSF. Figure B.2.2-1: AUSF requests CRL from UDM/ARPF The deployment of OSCP is demonstrated in figure B.2.2-2. When the UDM/ARPF supports OCSP, the AUSF may check the certificate status online. Figure B.2.2-2: AUSF requests the status of TLS certificate from UDM/ARPF | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | B.2.2 |
5,722 | 6.4.2 Slot/subslot-based physical downlink shared channel | For slot or subslot-based PDSCH, in this specification referred to as slot-PDSCH and subslot-PDSCH respectively, the following additions and exceptions hold in addition to those in clause 6.4: - PDSCH is not mapped to resource elements of SCCEs used by the associated SPDCCH, or resource elements used for UE-specific reference signals associated with SPDCCH - In case of slot-PDSCH: - the mapping to resource elements on antenna port not reserved for other purposes shall be in increasing order of first the index over the assigned physical resource blocks and then the index, for the slot of the assigned physical resources in the subframe, and - in case of UE-specific reference signals, the PDSCH is not mapped to any physical resource blocks carrying PBCH. - In case of subslot-PDSCH: - the mapping to resource elements on antenna port not reserved for other purposes shall be in increasing order of first the index over the assigned physical resource blocks and then the index, starting from given in Table 6.4.2-1. The starting value and the value range of depends on the number of symbols used for PDCCH and the subslot number in the subframe, according to Table 6.4.2-1, and - in case of UE-specific reference signals, - the PDSCH is not mapped to any physical resource blocks in frequency domain carrying PBCH or synchronization signals for the OFDM symbols of the given subslot. - and in case the DCI associated with the subslot-PDSCH indicates the absence of the UE-specific reference signals (see DMRS position indicator field in TS 36.212[ Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding ] [3]), the PDSCH is not mapped to any physical resource blocks in frequency domain that carried PBCH or synchronization signals for the OFDM symbols of the previous subslot. Table 6.4.2-1: Starting value of index , i.e. , for subslot PDSCH - For PDSCH associated with UE-specific reference signals, - the PDSCH shall only be mapped to physical resource blocks in frequency domain assigned for PDSCH transmission where the assignment maps to both physical resource blocks of a PRG. - the subslot-PDSCH shall not be mapped to the physical resource blocks of a PRG in case the resource elements of the associated SPDCCH are mapped to those physical resource blocks. - In addition, the following additions and exceptions related to L1 signaling and/or higher layer configuration controlling rate-matching around SPDCCH resources hold: - PDSCH is not mapped to resource elements belonging to a SPDCCH resource set configured with higher layer parameter rateMatchingMode indicating 'm2' if either this SPDCCH resource set is not configured with higher layer parameter spdcch-L1-ReuseIndication or it is configured with higher layer parameter spdcch-L1-ReuseIndication 'n1' or 'n2' indicating '0' for the SPDCCH resource set. - PDSCH is not mapped to resource elements belonging to a SPDCCH resource set configured with higher layer parameter rateMatchingMode indicating 'm3' if the SPDCCH associated with PDSCH is found in this SPDCCH resource set and if either this SPDCCH resource set is not configured with higher layer parameter spdcch-L1-ReuseIndication or it is configured with higher layer parameter spdcch-L1-ReuseIndication 'n1' or 'n2' indicating '0' for the SPDCCH resource set. If the SPDCCH associated with PDSCH is found on a candidate belonging to two SPDCCH resource sets, the SPDCCH is assumed to be found in both SPDCCH resource sets. - PDSCH is not mapped to resource elements belonging to a SPDCCH resource set configured with higher layer parameter rateMatchingMode indicating 'm4' if the SPDCCH associated with PDSCH is not found in this SPDCCH resource set and if either this SPDCCH resource set is not configured with higher layer parameter spdcch-L1-ReuseIndication or it is configured with higher layer parameter spdcch-L1-ReuseIndication 'n1' or 'n2' indicating '0' for the SPDCCH resource set. - PDSCH is not mapped to resource elements belonging to a SPDCCH resource set configured with higher layer parameter spdcch-L1-ReuseIndication 'n0' if the bit of the Used/Unused SPDCCH resource indication field corresponding to this SPDCCH resource set in the DCI format 7 associated with PDSCH is set to 1. - PDSCH is not mapped to resource elements belonging to SCCE#0 to SCCE#of a SPDCCH resource set configured with higher layer parameter spdcch-L1-ReuseIndication 'n1' or 'n2' indicating '2' for the SPDCCH resource set if the most significant bit of the Used/Unused SPDCCH resource indication field in the DCI format 7 associated with PDSCH is set to 1. - PDSCH is not mapped to resource elements belonging to SCCE# to SCCE# of a SPDCCH resource set configured with higher layer parameter spdcch-L1-ReuseIndication 'n1' or 'n2' indicating '2' for the SPDCCH resource set if the least significant bit of the Used/Unused SPDCCH resource indication field in the DCI format 7 associated with PDSCH is set to 1. - It should be noted that not mapping PDSCH to resource elements belonging to a SPDCCH resource set holds irrespective of other indications (spdcch-L1-ReuseIndication or rateMatchingMode) associated with other SPDCCH resource sets (if configured). - For a UE with the higher-layer parameter blindSlotSubslotPDSCH-Repetitions set to TRUE and PDSCH associated with a downlink assignment sent on PDCCH/SPDCCH with DCI format 7 indicating transmissions, the rate-matching around SPDCCH resources if applicable for PDSCH in the valid slots/subslots following the slot/subslot containing the downlink assignment follows - the rate-matching around SPDCCH resources of the PDSCH in the slot/subslot containing the downlink assignment, if the DCI format 7 indicating transmissions is received on SPDCCH. - the rate-matching around SPDCCH resources of the PDSCH in the SPDCCH resource set according to rateMatchingMode indicating 'm2', if configured by higher layers, if the DCI format 7 indicating transmissions is received on PDCCH. For other configurations of rateMatchingMode, no rate-matching around SPDCCH resources for PDSCH in the valid slots/subslots following the PDCCH with DCI format 7 indicating PDSCH transmissions is applied.. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.4.2 |
5,723 | 5.4.4.1a UE radio capability signalling optimisation (RACS) | With the increase of the size of UE radio capabilities driven e.g. by additional frequency bands and combinations thereof for E-UTRA and NR, an efficient approach to signal UE Radio Capability Information over the radio interface and other network interfaces is defined with RACS. In this Release of the specification, RACS does not apply to NB-IOT. RACS works by assigning an identifier to represent a set of UE radio capabilities. This identifier is called UE Radio Capability ID. A UE Radio Capability ID can be either UE manufacturer-assigned or PLMN-assigned, as specified in clause 5.9.10. The UE Radio Capability ID is an alternative to the signalling of the UE Radio Capability information over the radio interface, within NG-RAN, from NG-RAN to E-UTRAN, from AMF to NG-RAN and between CN nodes supporting RACS. PLMN-assigned UE Radio Capability ID is assigned to the UE using the UE Configuration Update Command, or Registration Accept as defined in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The UCMF shall be configured with a Version ID for PLMN-assigned UE Radio Capability IDs, defined in clause 5.9.10. The UCMF (UE radio Capability Management Function) stores all UE Radio Capability ID mappings in a PLMN and is responsible for assigning every PLMN-assigned UE Radio Capability ID in this PLMN, see clause 6.2.21. The UCMF stores the UE Radio Capability IDs alongside the UE Radio Capability information and the UE Radio Capability for Paging they map to. Each UE Radio Capability ID stored in the UCMF can be associated to one or both UE radio capabilities formats specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [51] and TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28]. The two UE radio capabilities formats shall be identifiable by the AMF and UCMF and the AMF shall store the TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28] format only. An NG-RAN which supports RACS can be configured to operate with one of two modes of operation when providing the UE radio capabilities to the AMF when the NG-RAN executes a UE Radio Capability Enquiry procedure (see TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28]) to retrieve UE radio capabilities from the UE: - Mode of operation A): The NG-RAN provides to the AMF both formats (i.e. the TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28] format and TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [51] format). The NG-RAN derives one of the UE Radio Capability formats using local transcoding of the other format it receives from the UE and extracts the E-UTRAN UE Radio Capability for Paging and NR UE Radio Capability for Paging from the UE Radio capabilities. - Mode of operation B): The NG-RAN provides to the AMF the TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28] format only. In a PLMN supporting RACS only in 5GS, Mode of Operation B shall be configured. If the PLMN supports RACS in both EPS and 5GS: - If RAN nodes in the EPS and 5GS are configured in Mode of operation B, then the UCMF shall be capable to transcode between TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [51] and TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28] formats and the UCMF shall be able to generate the RAT-specific UE Radio Capability for Paging information from the UE Radio Capability. - If the NG-RAN is configured to operate according to Mode A, then also the E-UTRAN shall be configured to operate according to mode A and the UMCF is not required to transcode between TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [51] and TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28] formats and the AMF shall provide the UE Radio Capability for Paging information. When the NG-RAN updates the AMF with new UE radio capabilities information, the AMF provides the information obtained from the NG-RAN to the UCMF even if the AMF already has a UE Radio Capability ID for that UE. The UCMF then returns a value of UE Radio Capability ID. If the value is different from the one stored in the AMF, the AMF updates the UE Radio Capability ID it stores and provides this new value to the NG-RAN (if applicable) and to the UE. In order to be able to interpret the UE Radio Capability ID a Network Function or node may store a local copy of the mapping between the UE Radio Capability ID and its corresponding UE Radio Capability information i.e. a dictionary entry. When no mapping is available between a UE Radio Capability ID and the corresponding UE Radio Capability information in a Network Function or node, this Network Function or node shall be able to retrieve this mapping and store it. - An AMF which supports RACS shall store such UE Radio Capability ID mapping at least for all the UEs that it serves that have a UE Radio Capability ID assigned. - The NG-RAN performs local caching of the UE Radio Capability information for the UE Radio Capability IDs for the UEs it is serving, and potentially for other UE Radio Capability IDs according to suitable local policies. - When the NG-RAN needs to retrieve the mapping of a UE Radio Capability ID to the corresponding UE Radio Capability information, it queries the AMF using N2 signalling defined in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]. - When the AMF needs to obtain a PLMN-assigned UE Radio Capability ID for a UE from the UCMF, it provides the UE Radio Capability information it has for the current radio configuration of the UE and the IMEI/TAC for the UE and the UCMF returns a UE Radio Capability ID. The AMF shall provide to the UCMF the UE Radio Capability information (and at least in Mode A, the UE Radio Capability for Paging) obtained from the NG-RAN in one or both the TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [51] and TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28] formats depending on how the RAN is configured. The UCMF stores the association of this IMEI/TAC with this UE Radio Capability ID and the UE Radio Capability information and the UE Radio Capability for Paging in all the formats it receives. The UE Radio Capability information formats the AMF provides shall be identifiable at the UCMF. - When the AMF needs to obtain the UE Radio Capability information and the UE Radio Capability for Paging associated to a UE Radio Capability ID it provides the UE Radio Capability ID to the UCMF with an indication that it is requesting the TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28] format and the UCMF returns a mapping of the UE Radio Capability ID to the corresponding UE Radio Capability information in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28] format to the AMF. - UEs, AMFs and RAN nodes which support RACS learn the current value of the Version ID when a new PLMN-assigned UE Radio Capability ID is received from the UCMF and the Version ID it contains is different from the ones in their PLMN Assigned UE Radio Capability ID cache. For a PLMN, PLMN-assigned UE Radio Capability IDs related to old values (i.e. not current value) of the Version ID can be removed from cache but, if so, prior to removing any cached PLMN-assigned UE radio Capability IDs with the current value of the Version ID. The AMF, RAN and UE may continue to use the stored PLMN assigned UE Radio Capability IDs with old values of the Version ID, until these are purged from cache. If an out of date PLMN assigned UE Radio Capability ID is removed form an AMF cache, the AMF shall proceed to assign a new PLMN assigned UE Radio Capability ID to all the UEs for which the UE context includes the removed PLMN-assigned UE Radio Capability ID using a UE Configuration Update procedure, or when these UEs perform a Registration. If the AMF attempts to resolve a PLMN assigned UE Radio capability ID with an old Version ID, the UCMF shall return an error code indicating that the Version ID in the UE radio capability ID is no longer current and proceed to assign a new UE Radio Capability ID to the UE. If at any time the AMF has neither a valid UE Radio Capability ID nor any stored UE radio capabilities for the UE, the AMF may trigger the RAN to provide the UE Radio Capability information and subsequently request the UCMF to allocate a UE Radio Capability ID. - The RAN, in order to support MOCN network sharing scenarios, shall be capable to cache PLMN assigned UE Radio Capability IDs per PLMN ID. A network may utilise the PLMN-assigned UE Radio Capability ID, without involving the UE, e.g. for use with legacy UEs. Mutual detection of the support of the RACS feature happens between directly connected NG-RAN nodes and between NG-RAN and AMF using protocol means as defined in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34] and TS 38.423[ NG-RAN; Xn Application Protocol (XnAP) ] [99]. To allow for a mix of RACS-supporting and non-RACS-supporting RAN nodes over the Xn interfaces, the UE Radio Capability ID should be included in the Path Switch signalling during Xn based handover and Handover Request during N2 based handover between AMF and NG-RAN. In addition, RACS-supporting RAN nodes can be discovered across inter-CN node boundaries by using the mechanism defined in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34] that allows the source NG-RAN node to retrieve information on the level of support for a certain feature at the target NG-RAN side by means of information provided within the Source to Target and Target to Source transparent handover containers during handover procedure. The support of RACS by peer AMFs or MMEs is based on configuration in a PLMN or across PLMNs. A UE that supports WB-E-UTRA and/or NR indicates its support for RACS to AMF using UE MM Core Network Capability as defined in clause 5.4.4a. A UE that supports RACS and stores an applicable UE Radio Capability ID for the current UE Radio Configuration in the PLMN, shall signal the UE Radio Capability ID in the Initial, and Mobility Registration procedure as defined in TS 23.502[ Procedures for the 5G System (5GS) ] [3] and based on triggers defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. If both PLMN-assigned for the current PLMN and UE manufacturer-assigned UE Radio Capability IDs are stored in the UE and applicable in the PLMN, the UE shall signal the PLMN-assigned UE Radio Capability ID in the Registration Request message. When a PLMN decides to switch to request a particular type of UE to use UE manufacturer-assigned UE Radio Capability ID(s): - The UCMF sends a Nucmf_UECapabilityManagement_Notify message to the AMF including either a list of UE Radio Capability IDs (if the UE was previously using any PLMN-assigned IDs) or the IMEI/TAC values corresponding to UE types that are requested to use UE manufacturer-assigned UE Radio Capability ID. These values are stored in a "UE Manufacturer Assigned operation requested list" in the AMF. - The AMF uses the Registration Accept message or the UE Configuration Update command message to request the UE to delete all the PLMN-assigned UE Radio Capability ID(s) for this PLMN if the UE is, respectively, registering or is registered with PLMN-assigned ID or IMEI/TAC values matching one value in the "UE Manufacturer Assigned operation requested list". NOTE 1: It is expected that in a given PLMN the UCMF and AMFs will be configured to either use a UE manufacturer-assigned operation requested list based on a list of PLMN-assigned UE Radio Capability IDs or a list of IMEI/TACs, but not both. NOTE 2: The strategy for triggering of the deletion of PLMN-assigned UE Radio Capability ID(s) in the UE by the AMF is implementation-specific (e.g. can be used only towards UEs in CM-CONNECTED state). - a UE that receives indication to delete all the PLMN-assigned UE Radio Capability IDs in the Registration Accept message, or UE Configuration Update command message, shall delete any PLMN-assigned UE Radio Capability IDs for this PLMN. The UE proceeds to register with a UE manufacturer-assigned UE Radio Capability ID that is applicable to the current UE Radio configuration. - When the "UE Manufacturer Assigned operation requested list" contains PLMN-assigned UE Radio Capability IDs, the UCMF shall avoid re-assigning PLMN-assigned UE Radio Capability IDs that were added to the "UE Manufacturer Assigned operation requested list" in the AMFs to any UE. - The AMF stores a PLMN-assigned ID in the "UE Manufacturer Assigned operation requested list" for a time duration that is implementation specific, but IMEI/TACs are stored until the UCMF require to remove certain TACs from the list (i.e. the list of IMEI/TACs which are requested to use UE manufacturer-assigned IDs in the AMF and UCMF is synchronised at all times). - The UCMF can request at any time the AMF to remove PLMN-assigned ID(s) or IMEI/TAC(s) values from the UE manufacturer-assigned operation requested list. NOTE 3: The AMF can decide to remove a UE Radio Capability ID from the "UE Manufacturer Assigned operation requested list" list e.g. because no UE with that UE Radio Capability ID has connected to the network for long time. If later a UE with such UE Radio Capability ID connects to the network, the AMF contacts the UCMF to resolve the UE Radio Capability ID, and at this point the UCMF can trigger again the deletion of the UE Radio Capability ID by including this in the "UE Manufacturer Assigned operation requested list" of the AMF. The serving AMF stores the UE Radio Capability ID related to selected PLMN for a UE in the UE context and provides this UE Radio Capability ID to NG-RAN as part of the UE context information using N2 signalling. During inter PLMN mobility, the new AMF shall delete the UE Radio Capability ID received from the old AMF, unless the operator policy indicates that all UE Radio Capability IDs used in the old PLMN is also valid in the new PLMN. NOTE 4: If AMF decides to allocate TAIs of multiple PLMN IDs as part of Registration Area to the UE then AMF provides the UE Radio Capability ID of the new selected PLMN to the NG-RAN during UE mobility, whether the UE Radio Capability ID is taken from stored UE context previously assigned by the same new selected PLMN or generated freshly each time a new PLMN is selected is up to AMF implementation. The UE stores the PLMN-assigned UE Radio Capability ID in non-volatile memory when in RM-DEREGISTERED state and can use it again when it registers in the same PLMN. NOTE 5: It is assumed that UE does not need to store the access stratum information (i.e. UE-E-UTRA-Capability and UE-NR-Capability specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [51] and TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28], respectively) that was indicated by the UE to the network when the PLMN-assigned UE Radio Capability ID was assigned by the network. However, it is assumed that the UE does store the related UE configuration (e.g. whether or not GERAN or UTRAN or MBMS is enabled/disabled). At any given time at most one UE Radio Capability ID is used from the UE context in CN and RAN which is related to the selected PLMN. The number of PLMN-assigned UE Radio Capability IDs that the UE stores in non-volatile memory is left up to UE implementation. However, to minimise the load (e.g. from radio signalling) on the Uu interface and to provide smoother inter-PLMN mobility (e.g. at land borders) the UE shall be able to store at least the latest 16 PLMN-assigned UE Radio Capability IDs (along with the PLMN that assigned them). This number is independent of the UE manufacturer-assigned UE Radio Capability ID(s) the UE may store. It shall be possible for a UE to change, e.g. upon change in its usage settings, the set of UE radio capabilities in time and signal the associated UE Radio Capability ID, if available. The UE stores the mapping between the UE Radio Capability ID and the corresponding UE Radio Capability Information for every UE Radio Capability ID it stores. If the UE's Radio Capability Information changes and regardless of whether the UE has an associated UE Radio Capability ID for the updated UE Radio Capability information, the UE shall perform the Registration procedure by sending a Registration Request message to the AMF with the Registration type set to Mobility Registration Update which includes "UE Radio Capability Update" and: - If the UE has an associated UE Radio Capability ID for the updated UE Radio Capability information, the UE shall include it in the Registration Request message so that the AMF, upon receiving it, shall update the UE's context with this UE Radio Capability ID. - If the UE does not have an associated UE Radio Capability ID for the updated UE Radio Capability information, the UE shall not include any UE Radio Capability ID in the Registration Request message so that the AMF, upon receiving this Registration Request without any UE Radio Capability ID, retrieves the UE radio capabilities from the UE as defined in clause 5.4.4.1. The NG-RAN may apply RRC filtering of UE radio capabilities when it retrieves the UE Radio Capability Information from the UE as defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28]. NOTE 6: In a RACS supporting PLMN, the filter of UE radio capabilities configured in NG-RAN is preferably as wide in scope as possible (e.g. PLMN-wide). In this case, it corresponds e.g. to the super-set of bands, band-combinations and RATs the PLMN deploys and not only to the specific NG-RAN node or region. NOTE 7: If the filter, included in the UE Radio Capability information, of UE radio capabilities configured in two NG-RAN nodes is different, during handover between these two nodes, it is possible that the target NG-RAN node might need to enquire the UE for its UE Radio Capability Information again and trigger re-allocation of a PLMN-assigned UE Radio Capability ID leading to extra signalling. Additionally, a narrow filter might reduce the list of candidate target nodes. If a UE supports both NB-IoT and other RATs that do support RACS (e.g. WB-E-UTRA and/or NR) then (since there is no support for RACS in NB-IoT) the UE handles the RACS procedures as follows: - NB-IoT specific UE Radio Capability Information is handled in UE, NG-RAN and AMF according to clause 5.4.4.1 and in EPS according to TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]. - when the UE is not camping on NB-IoT, the RAN provides UE radio capabilities for other RATs but not NB-IoT UE radio capabilities, according to TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27] and TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [30]. As a result the UE Radio Capability ID that is assigned by the network corresponds only to the UE radio capabilities of the non-NB-IoT RATs. The UE uses the UE Radio Capability IDs assigned only in Mobility Registration Update procedures performed over non-NB-IoT RATs. Support for RACS in EPS is defined in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.4.1a |
5,724 | 4.5.2 MM connection information transfer phase | After the MM connection has been established, it can be used by the CM sublayer entity for information transfer. According to the protocol architecture described in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20], each CM entity will have its own MM connection. These different MM connections are identified by the protocol discriminator PD and, additionally, by the transaction identifier TI. All MM common procedures may be initiated at any time while MM connections are active. Except for Short Message Control which uses a separate layer 2 low priority data link, no priority mechanism is defined between the CM, MM and RR sublayer messages. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.5.2 |
5,725 | A.4 New QoS Flow with Explicit NAS Signalling | The following figure shows an example message flow when the gNB receives a new QoS flow establishment request from CN that involves NAS explicit signalling. The QoS flow establishment request provides the gNB and UE with the QoS parameters for the QFI. In this example, the gNB decides to establish a new DRB (rather than re-use an existing one) for this QoS flow and provides the mapping rule over RRC signalling. NAS procedures details between gNB and 5GC can be found in TS 23.501[ System architecture for the 5G System (5GS) ] [3], TS 23.502[ Procedures for the 5G System (5GS) ] [22] and TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [26]. Figure A.4-1: DL data with new QoS Flow ID sent over new DRB with explicit signalling 0. PDU session DRB(s) have been already established. 1. gNB receives a PDU SESSION RESOURCE MODIFY REQUEST message from AMF for a new QoS flow. 2. If gNB cannot find an existing DRB to map this new QoS flow, it decides to establish a new DRB. 3. gNB sends an RRCReconfiguration message to UE including the DRB configuration with the new QFI to DRB mapping rule and the NAS message received at step 1. 4. UE establishes the DRB for the new QoS flow associated with this PDU session and updates the mapping rules. 5. UE sends an RRCReconfigurationComplete message to gNB. 6. gNB sends a PDU SESSION RESOURCE MODIFY RESPONSE message to AMF. 7. User Plane Data can then be exchanged between UE and gNB over DRB(s) according to the mapping rules and between UPF and gNB over the tunnel for the PDU session. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | A.4 |
5,726 | 26.2 Domain name for MC services confidentiality protection of MC services identities | A Domain Name for MC Services confidentiality protection used in a host part of a SIP URI indicates that the user part of the SIP URI contains a confidentiality protected MC Services identity. This Domain Name shall be the string "mc1-encrypted.3gppnetwork.org". Protected MCPTT identities are constructed according to 3GPP TS 24.379[ Mission Critical Push To Talk (MCPTT) call control; Protocol specification ] [111]. Protected MCData identities are constructed according to 3GPP TS 24.282[ Mission Critical Data (MCData) signalling control; Protocol specification ] [116]. Protected MCVideo identities are constructed according to 3GPP TS 24.281[ Mission Critical Video (MCVideo) signalling control; Protocol specification ] [115]. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 26.2 |
5,727 | 6.1.3.2.2 RES* verification failure in SEAF or AUSF or both | This clause describes how RES* verification failure in the SEAF or in the AUSF shall be handled. In step 9 in Figure 6.1.3.2-1, the SEAF shall compute HRES* from RES* according to Annex A.5, and the SEAF shall compare HRES* and HXRES*. If they don’t coincide, then the SEAF shall consider the authentication as unsuccessful. The SEAF shall proceed with step 10 in Figure 6.1.3.2-1 and after receiving the Nausf_UEAuthentication_Authenticate Response message from the AUSF in step 12in Figure 6.1.3.2-1, proceed as described below: - If the AUSF has indicated in the Nausf_UEAuthentication_Authenticate Response message to the SEAF that the verification of the RES* was not successful in the AUSF, or - if the verification of the RES* was not successful in the SEAF, then the SEAF shall either reject the authentication by sending an Authentication Reject to the UE if the SUCI was used by the UE in the initial NAS message or the SEAF/AMF shall initiate an Identification procedure with the UE if the 5G-GUTI was used by the UE in the initial NAS message to retrieve the SUCI and an additional authentication attempt may be initiated. Also, if the SEAF does not receive any Nausf_UEAuthentication_Authenticate Response message from the AUSF as expected, then the SEAF shall either reject the authentication to the UE or initiate an Identification procedure with the UE. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.1.3.2.2 |
5,728 | 4.4.3.4 N4 Report Procedure | The N4 Report procedure shall be used by the UPF to report information to the SMF which is not related to a specific N4 session, e.g. to report a user plane path failure affecting all the N4 sessions towards a remote GTP-U peer. N4 Report procedure can be used by the UPF to report the clock drift between the external time and 5GS time for one or more external working domains as specified in TS 29.244[ Interface between the Control Plane and the User Plane nodes ] [69]. Figure 4.4.3.4-1: N4 report procedure The UPF detects that an event has to be reported and starts the procedure by sending an N4 Report message (UPF ID, list of [event, status]) to the SMF. The SMF responds with an N4 report ACK message (SMF ID). The event parameter contains the name of the event and UPF ID. The status parameter contains the actual information the control plane function is interested in. If the UPF detects clock drifting between 5G time and one or more time working domains, the UPF reports the corresponding external domain number and the time offset and cumulative rate Ratio according to the provisioning from the SMF as defined in clause 5.27.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The UPF includes the Network Instance (if available) and the combination of DNN and S-NSSAI (if available) in the report. NOTE: When the UPF supports more than one NW-TT, the SMF can use the Network Instance or DNN/S-NSSAI to associate the report with the corresponding N4 sessions and NW-TT. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.4.3.4 |
5,729 | 10.2.2.3.2 Handover | When UE attempts to make Xn/N2 handover, UE and gNB derive and transfer the keys as normal to re-use the normal handover mechanism. Since the derived keys have no ability to affect the output of the NULL algorithms it is irrelevant that the network and the UE derive different keys. This implies that source gNB will forward UE 5G security capability which contains NIA0 and NEA0 only to target gNB. So the target gNB can only select NIA0 for integrity protection and NEA0 for confidential protection. If the UE does not receive any selection of new AS security algorithms during a intra-gNB-CU handover, the UE continues to use the same algorithms as before the handover (see TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [22]). | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 10.2.2.3.2 |
5,730 | 5.3.5.13.4 Conditional reconfiguration evaluation | The UE shall: 1> for each condReconfigId within the VarConditionalReconfig: 2> if the RRCReconfiguration within condRRCReconfig includes the masterCellGroup including the reconfigurationWithSync: 3> if the associated condExecutionCondPSCell is configured: 4> consider the cell which has a physical cell identity matching the value indicated in the ServingCellConfigCommon included in the reconfigurationWithSync within the masterCellGroup in the received condRRCReconfig to be applicable cell; and 4> consider the cell which has a physical cell identity matching the value indicated in the ServingCellConfigCommon included in the reconfigurationWithSync within the secondaryCellGroup within the nr-SCG within the received condRRCReconfig to be applicable cell; 3> else: 4> consider the cell which has a physical cell identity matching the value indicated in the ServingCellConfigCommon included in the reconfigurationWithSync within the masterCellGroup in the received condRRCReconfig to be applicable cell; 2> else if the RRCReconfiguration within condRRCReconfig includes the secondaryCellGroup including the reconfigurationWithSync: 3> if the cell which has a physical cell identity matching the value indicated in the ServingCellConfigCommon included in the reconfigurationWithSync within the secondaryCellGroup within the received condRRCReconfig is not the PSCell: 4> consider the cell to be applicable cell; 2> if condExecutionCondSCG is configured: 3> in the remainder of the procedure, consider each measId indicated in the condExecutionCondSCG as a measId in the VarMeasConfig associated with the SCG measConfig; 2> if the condExecutionCondPSCell is configured: 3> in the remainder of the procedure, consider each measId indicated in the condExecutionCondPSCell as a measId in the VarMeasConfig associated with the MCG measConfig; 2> if condExecutionCond is configured: 3> if it is configured via SRB3 or configured within nr-SCG or within nr-SecondaryCellGroupConfig (specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]) via SRB1: 4> in the remainder of the procedure, consider each measId indicated in the condExecutionCond as a measId in the VarMeasConfig associated with the SCG measConfig; 3> else: 4> in the remainder of the procedure, consider each measId indicated in the condExecutionCond as a measId in the VarMeasConfig associated with the MCG measConfig; 2> for each measId included in the measIdList within VarMeasConfig indicated in the condExecutionCond, condExecutionCondSCG, or condExecutionCondPSCell associated to condReconfigId: 3> if the condTriggerConfig is not configured with nesEvent: 4> if the condEventId is associated with condEventT1, and if the entry condition applicable for this event associated with the condReconfigId, i.e. the event corresponding with the condEventId(s) of the corresponding condTriggerConfig within VarConditionalReconfig, is fulfilled for the applicable cell; or 4> if the condEventId is associated with condEventD1, and if the entry conditions applicable for this event associated with the condReconfigId, i.e. the event corresponding with the condEventId(s) of the corresponding condTriggerConfig within VarConditionalReconfig, is fulfilled for the applicable cell during the corresponding timeToTrigger defined for this event within the VarConditionalReconfig; or 4> if the condEventId is associated with condEventD2, and if the entry conditions applicable for this event associated with the condReconfigId, i.e., the event corresponding with the condEventId(s) of the corresponding condTriggerConfig within VarConditionalReconfig, is fulfilled for the applicable cell during the corresponding timeToTrigger defined for this event within the VarConditionalReconfig; or 4> if the condEventId is associated with condEventA3, condEventA4 or condEventA5, and if the entry condition(s) applicable for this event associated with the condReconfigId, i.e. the event corresponding with the condEventId(s) of the corresponding condTriggerConfig within VarConditionalReconfig, is fulfilled for the applicable cells for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event within the VarConditionalReconfig: 5> consider the event associated to that measId to be fulfilled; 4> if the measId for this event associated with the condReconfigId has been modified; or 4> if the condEventId is associated with condEventT1, and if the leaving condition applicable for this event associated with the condReconfigId, i.e. the event corresponding with the condEventId(s) of the corresponding condTriggerConfig within VarConditionalReconfig, is fulfilled for the applicable cell; or 4>if the condEventId is associated with condEventD1, and if the leaving condition(s) applicable for this event associated with the condReconfigId, i.e. the event corresponding with the condEventId(s) of the corresponding condTriggerConfig within VarConditionalReconfig, is fulfilled for the applicable cell during the corresponding timeToTrigger defined for this event within the VarConditionalReconfig; or 4> if the condEventId is associated with condEventD2, and if the leaving condition(s) applicable for this event associated with the condReconfigId, i.e., the event corresponding with the condEventId(s) of the corresponding condTriggerConfig within VarConditionalReconfig, is fulfilled for the applicable cell during the corresponding timeToTrigger defined for this event within the VarConditionalReconfig; or 4> if the condEventId is associated with condEventA3, condEventA4 or condEventA5, and if the leaving condition(s) applicable for this event associated with the condReconfigId, i.e. the event corresponding with the condEventId(s) of the corresponding condTriggerConfig within VarConditionalReconfig, is fulfilled for the applicable cells for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event within the VarConditionalReconfig: 5> consider the event associated to that measId to be not fulfilled; 3> else: 4> if NES mode indication is received from lower layers, indicating that the NES-specific CHO execution condition is enabled; and 4> if the entry condition(s) applicable for this event associated with the condReconfigId, i.e. the event corresponding with the condEventId(s) of the corresponding condTriggerConfig within VarConditionalReconfig, is fulfilled for the applicable cells for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event within the VarConditionalReconfig: 5> consider the event associated to that measId to be fulfilled; 4> if the measId for this event associated with the condReconfigId has been modified; or 4> if NES mode indication is received from lower layers, indicating that the NES-specific CHO execution condition is disabled; or 4> if the leaving condition(s) applicable for this event associated with the condReconfigId, i.e. the event corresponding with the condEventId(s) of the corresponding condTriggerConfig within VarConditionalReconfig, is fulfilled for the applicable cells for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event within the VarConditionalReconfig: 5> consider the event associated to that measId to be not fulfilled; 2> if condExecutionCondPSCell is not configured: 3> if event(s) associated to all measId(s) within condTriggerConfig for the applicable cell are fulfilled: 4> consider the applicable cell, associated to that condReconfigId, as a triggered cell; 4> initiate the conditional reconfiguration execution, as specified in 5.3.5.13.5; 2> else: 3> if event(s) associated to all measId(s), as indicated in the condExecutionCond and condExecutionCondPSCell, within condTriggerConfig for a target candidate cell within the stored condRRCReconfig are fulfilled: 4> consider the target candidate PCell within the stored condRRCReconfig, associated to that condReconfigId, as a triggered PCell; 4> consider the target candidate PSCell within the stored condRRCReconfig, associated to that condReconfigId, as a triggered PSCell; 4> initiate the conditional reconfiguration execution, as specified in 5.3.5.13.5. 2> if one of the events associated to the measIds within condTriggerConfig for the applicable cell within the stored condRRCReconfig is not configured with nesEvent, and the other event associated to the measIds within condTriggerConfig for the applicable cell within the stored condRRCReconfig is configured with nesEvent, and at least one of them is fulfilled: 3> consider the applicable cell within the stored condRRCReconfig, associated to that condReconfigId, as a triggered cell; 3> initiate the conditional reconfiguration execution, as specified in 5.3.5.13.5; NOTE 1: Up to 2 MeasId can be configured for each condReconfigId, if condExecutionCondPSCell is not configured. The conditional reconfiguration event of the 2 MeasId may have the same or different event conditions, triggering quantity, time to trigger, and triggering threshold. NOTE 2: Void. NOTE 3: For CHO with candidate SCGs, up to 2 MeasId can be configured for condExecutionCond and up to 2 MeasId can be configured for condExecutionCondPSCell for each condReconfigId. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.13.4 |
5,731 | 8.2.1.2.3 Minimum Requirement 2 Tx Antenna Port (demodulation subframe overlaps with aggressor cell ABS) | The requirements are specified in Table 8.2.1.2.3-2, with the addition of parameters in Table 8.2.1.2.3-1 and the downlink physical channel setup according to Annex C.3.2 and Annex C.3.3. The purpose is to verify the performance of transmit diversity (SFBC) with 2 transmit antennas if the PDSCH transmission in the serving cell takes place in subframes that overlap with ABS [9] of the aggressor cell. In Table 8.2.1.2.3-1, Cell 1 is the serving cell, and Cell 2 is the aggressor cell. The downlink physical channel setup for Cell 1 is according to Annex C.3.2 and for Cell 2 is according to Annex C.3.3, respectively. Table 8.2.1.2.3-1: Test Parameters for Transmit diversity Performance (FRC) Table 8.2.1.2.3-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.2.1.2.3 |
5,732 | 4.12.7 UE or network Requested PDU Session Release via Untrusted non-3GPP access | Clause 4.12.7 specifies how a UE or network can release a PDU Session via an untrusted non-3GPP Access Network. The UE requested PDU Session Release procedure via Untrusted non-3GPP access applies in non-roaming, roaming with LBO as well as in home-routed roaming scenarios. For non-roaming and LBO scenarios, if the UE is simultaneously registered to a 3GPP access in a PLMN different from the PLMN of the N3IWF, the functional entities in the following procedures are located in the PLMN of the N3IWF. For home-routed roaming scenarios, the AMF, V-SMF and associated UPF in VPLMN in the following procedure is located in the PLMN of the N3IWF. NOTE: If the UE is simultaneously registered to 3GPP access in the same PLMN as non-3GPP access, when non-3GPP access is not available to the UE (e.g. due to out of non-3GPP access coverage) or UE is in CM-IDLE for non-3GPP access, the UE may perform the PDU Session Release procedure via 3GPP access as described in clause 4.3.4. Figure 4.12.7-1: UE Requested PDU Session Release via Untrusted non-3GPP access 1. One or more PDU Sessions are already established for the UE using the procedure described in clause 4.12.2. 2. The UE sends a NAS message (N1 SM container (PDU Session Release Request), PDU Session ID) to the AMF via the N3IWF as defined in clause 4.3.4. 3. For non-roaming and roaming with LBO, the steps 1a (from AMF) to 4 according to the PDU Session Release procedure defined in clause 4.3.4.2 are executed. For home-routed roaming, the steps 1a (from AMF) to step 7 according to the PDU Session Release procedure defined in clause 4.3.4.3 are executed. 4. This step is the same as step 4 in clause 4.3.4.2 (non-roaming and LBO) and step 6 in clause 4.3.4.3 (home-routed roaming). If the message received from the SMF does not include N2 SM Resource Release request, the AMF sends N2 Downlink NAS transport (N1 SM container (PDU Session Release Command), PDU Session ID,Cause) message to the N3IWF and steps 5 to 8 are skipped. 5. Upon receiving AN session release request message from the AMF, the N3IWF triggers the release of the corresponding Child SA by sending INFORMATIONAL EXCHANGE (Delete Payload) to the UE. Delete payload is included in the message listing the SPIs of the Child SAs to be deleted to this PDU Session as described in RFC 7296 [3]. 6. The UE responds with INFORMATIONAL EXCHANGE (Delete Payload) message. Delete payload is included for the paired SAs going in the other direction as described in RFC 7296 [3]. 7. This step is the same as step 6 in 4.3.4.2 (non-roaming and LBO) and step 8 in clause 4.3.4.3 (home-routed roaming). 8. For non-roaming and roaming with LBO, steps 7 according to the PDU Session Release procedure defined in clause 4.3.4.2 are executed. For home-routed roaming, step 9-10 according to the PDU Session Release procedure defined in clause 4.3.4.3 are executed. 9. The N3IWF delivers the NAS message (N1 SM container (PDU Session Release Command), PDU Session ID, Cause) to the UE. 10. The UE sends a NAS message (N1 SM container (PDU Session Release Ack), PDU Session ID) to the N3IWF. 11. This step is the same as step 9 in 4.3.4.2 (non-roaming and LBO) and step 11 in clause 4.3.4.3 (home-routed roaming). Steps 5 and 9 may happen consecutively. Step 10 may happen before step 6. 12. For non-roaming and roaming with LBO, all steps after step 10 in the PDU Session Release procedure defined in clause 4.3.4.2 are executed. In the case of home-routed roaming, all steps after step 12 in the PDU Session Release procedure defined in clause 4.3.4.3 are executed. The network requested PDU Session Release procedure via Untrusted non-3GPP access is the same as the network requested PDU Session Release Procedure specified in clause 4.3.4.2 (for Non-Roaming and Roaming with Local Breakout) with the following differences: - The (R)AN corresponds to an N3IWF. - In step 5 the N3IWF upon receiving N2 SM request to release the AN resources associated with the PDU Session from the AMF, the N3IWF triggers the release of the corresponding Child SA to the UE as specified in step 5 and 6, in Figure 4.12.7-1. - User Location Information is not included in the step 6, 7a, 9, 10a and 12 of the procedure. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.12.7 |
5,733 | 6.2.5F Configured transmitted Power for category NB1 and NB2 | For each slot i the category NB1and NB2 UE is allowed to set its configured maximum output power PCMAX,c. The configured maximum output power PCMAX,c is set within the following bounds: PCMAX_L,c ≤ PCMAX,c ≤ PCMAX_H,c Where PCMAX_L,c = MIN { PEMAX,c , PPowerClass – MPRc – A-MPRc} PCMAX_H,c = MIN { PEMAX,c, PPowerClass} PEMAX,c is the value given to IE P-Max, defined in [7] PPowerClass is the maximum category NB1 and NB2 UE power specified in Table 6.2.2F-1 without taking into account the associated tolerance MPRc is specified in subclause 6.2.3F A-MPRc = 0dB unless otherwise stated. The measurement period for PUMAX,c is at least one sub-frame (1ms) for 15 KHz channel spacing, and at least a 2ms slot (excluding the 2304Ts gap when UE is not transmitting) respectively for the 3.75 KHz channel spacing. The measured maximum output power PUMAX,c shall be within the following bounds: PCMAX_L,c – T(PCMAX_L,c) ≤ PUMAX,c ≤ PCMAX_H,c + T(PCMAX_H,c) Where T(PCMAX) is defined by the tolerance table below and applies to PCMAX_L,c and PCMAX_H,c separately. Table 6.2.5F-1: PCMAX tolerance for power class 3 Table 6.2.5F-2: PCMAX tolerance for power class 5 Table 6.2.5F-3: PCMAX tolerance for power class 6 | 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.5F |
5,734 | 8.13.3.3.1 Minimum Requirement Single-Layer Spatial Multiplexing 2 Tx Antenna Port with TM4 interference model (Cell-Specific Reference Symbols) for FDD PCell | 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.3.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 TDD FDD CA with FDD PCell and with 2 DL CCs, the requirements are specified in Table 8.13.3.3.1-4, based on single carrier requirement specified in Table 8.13.3.3.1-2 and Table 8.13.3.3.1-3, with the addition of the parameters in Table 8.13.3.3.1-1 and the downlink physical channel setup according to Annex C.3.2. Table 8.13.3.3.1-1: Test Parameters for Single-Layer Spatial Multiplexing (FRC) with TM4 interference model for CA Table 8.13.3.3.1-2: Single carrier performance for Enhanced Performance Requirement Type A for FDD PCell and SCell (FRC) Table 8.13.3.3.1-3: Single carrier performance for Enhanced Performance Requirement Type A for TDD SCell (FRC) Table 8.13.3.3.1-4: Minimum performance for multiple CA configurations with 2DL CCs (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.13.3.3.1 |
5,735 | – MUSIM-GapConfig | The IE MUSIM-GapConfig specifies the MUSIM gap configuration and controls setup/release of MUSIM gaps. MUSIM-GapConfig information element -- ASN1START -- TAG-MUSIM-GAPCONFIG-START MUSIM-GapConfig-r17 ::= SEQUENCE { musim-GapToReleaseList-r17 SEQUENCE (SIZE (1..3)) OF MUSIM-GapId-r17 OPTIONAL, -- Need N musim-GapToAddModList-r17 SEQUENCE (SIZE (1..3)) OF MUSIM-Gap-r17 OPTIONAL, -- Need N musim-AperiodicGap-r17 MUSIM-GapInfo-r17 OPTIONAL, -- Need N ..., [[ musim-GapPriorityToAddModList-r18 SEQUENCE (SIZE (1..3)) OF GapPriority-r17 OPTIONAL, -- Need N musim-GapKeep-r18 ENUMERATED {true} OPTIONAL -- Need R ]] } MUSIM-Gap-r17 ::= SEQUENCE { musim-GapId-r17 MUSIM-GapId-r17, musim-GapInfo-r17 MUSIM-GapInfo-r17 } -- TAG-MUSIM-GAPCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,736 | 4.7.2.2 Periodic routing area updating | The periodic routing area updating procedure is used to periodically notify the availability of the MS to the network. The procedure is controlled in the MS by timer T3312. The value of timer T3312 is sent by the network to the MS in the messages ATTACH ACCEPT and ROUTING AREA UPDATE ACCEPT. The value of timer T3312 shall be unique within a RA. If the value of timer T3312 received by the MS in A/Gb mode or received in Iu mode in a message with integrity protection contains an indication that the timer is deactivated or the timer value is zero, then timer T3312 is deactivated and the MS shall not perform the periodic routing area updating procedure. In Iu mode, if the value of timer T3312 is received in a message without integrity protection and the indicated value is larger than the last received value, or the indicated value is "deactivated" or zero, the MS shall use the last received value. If there is no last received value, then the MS shall use the default value. In A/Gb mode, the timer T3312 is reset and started with its initial value, when the READY timer is stopped or expires. Timer T3312 is stopped and shall be set to its initial value for the next start when the READY timer is started. If after a READY timer negotiation the READY timer value is set to zero, timer T3312 is reset and started with its initial value. If the initial READY timer value is zero, the timer T3312 is reset and started with its initial value, when the ROUTING AREA UPDATE REQUEST message is transmitted. In Iu mode, timer T3312 is reset and started with its initial value, when the MS changes from PMM-CONNECTED to PMM-IDLE mode. Timer T3312 is stopped when the MS enters PMM-CONNECTED mode. If the MS is attached for emergency bearer services, when timer T3312 expires, the MS shall not initiate a periodic routing area updating procedure, but shall locally detach from the network. When the MS is camping on a suitable cell, it may re-attach to regain normal service. If the MS is not attached for emergency bearer services, when timer T3312 expires, the periodic routing area updating procedure shall be started and timer T3312 shall be set to its initial value for the next start. If the MS is in a state other than GMM-REGISTERED.NORMAL-SERVICE when timer T3312 expires, the periodic routing area updating procedure is delayed until the MS returns to GMM-REGISTERED.NORMAL-SERVICE. In A/Gb mode, if the MS in MS operation mode B is in the state GMM-REGISTERED.SUSPENDED when timer T3312 expires the periodic routing area updating procedure is delayed until the state is left. If ISR is activated, the MS shall keep both timer T3412 and timer T3312. The two separate timers run in the MS for updating the MME and the SGSN independently. The MS shall start timer T3323 if timer T3312 expires, and timer T3346 is running or the MS is in one of the following states: - GMM-REGISTERED.NO-CELL-AVAILABLE; - GMM-REGISTERED.PLMN-SEARCH; - GMM-REGISTERED.UPDATE-NEEDED; or - GMM-REGISTERED.LIMITED-SERVICE. The MS shall initiate the routing area updating procedure and stop timer T3323 when the MS enters the state GMM-REGISTERED.NORMAL-SERVICE before timer T3323 expires. After expiry of timer T3323 the MS shall deactivate ISR by setting its TIN to "GUTI". If timer T3323 expires, the MS shall memorize that it has to initiate a routing area updating procedure when it returns to state GMM-REGISTERED.NORMAL-SERVICE. The network supervises the periodic routing area updating procedure by means of the mobile reachable timer. If the MS is not attached for emergency bearer services, the mobile reachable timer shall be longer than timer T3312. In this case, by default, the mobile reachable timer is 4 minutes greater than timer T3312. NOTE 1: According to subclause 4.7.5.1.5, if a periodic routing area updating procedure fails repeatedly, it can take more than 7 minutes before the MS starts using MM specific procedures. The network may include timer T3312 extended value IE in the ATTACH ACCEPT message or ROUTING AREA UPDATE ACCEPT message only if the MS indicates support of the timer T3312 extended value in the MS network feature support IE. If the network includes the timer T3312 extended value IE in the ATTACH ACCEPT message or ROUTING AREA UPDATE ACCEPT message, the network shall use the timer T3312 extended value IE as the value of timer T3312. If ISR is not activated, when the mobile reachable timer expires, typically the network stops sending paging messages to the mobile and may take other appropriate actions. If the MS is attached for emergency bearer services, the SGSN shall set the mobile reachable timer with a value equal to timer T3312. When the mobile reachable timer expires, the SGSN shall locally detach the MS. In A/Gb mode, the mobile reachable timer is reset and started with the value as indicated above, when the READY timer is stopped or expires. The mobile reachable timer is stopped when the READY timer is started. In A/Gb mode, if after a READY timer negotiation the READY timer value is set to zero, the mobile reachable timer is reset and started with its initial value. If the initial READY timer value is zero, the mobile reachable timer is reset and started with its initial value, when the ROUTING AREA UPDATE REQUEST message is received. In Iu mode, the mobile reachable timer is reset and started with the value as indicated above, when the MS changes from PMM-CONNECTED to PMM-IDLE mode. The mobile reachable timer is stopped when the MS enters PMM-CONNECTED mode. If ISR is activated, upon expiry of the mobile reachable timer the network shall start the implicit detach timer. By default, the implicit detach timer is 4 minutes greater than timer T3323. If the implicit detach timer expires before the MS contacts the network, the network shall implicitly detach the MS and deactivate ISR. If ISR is not activated, upon expiry of the mobile reachable timer the network may start the implicit detach timer. The value of the implicit detach timer is network dependent. If the implicit detach timer expires before the MS contacts the network, the network shall implicitly detach the MS. If the network includes the T3324 value IE in the ATTACH ACCEPT message or ROUTING AREA UPDATE ACCEPT message and if the MS is not attached for emergency bearer services and has no PDN connection for emergency bearer services, the network shall set the active timer to a value equal to the value of timer T3324. If the MS has established a PDN connection for emergency bearer services after receiving the timer T3324 value IE in the ATTACH ACCEPT message or ROUTING AREA UPDATE ACCEPT message, the active timer shall not be started. When the active timer expires, typically the network stops sending paging messages to the mobile and may take other appropriate actions. In A/Gb mode, the active timer is reset and started with the value as indicated above, when the READY timer is stopped or expires. The active timer is stopped when the READY timer is started. In Iu mode, the active timer is reset and started with the value as indicated above, when the MS changes from PMM-CONNECTED to PMM-IDLE mode. The active timer is stopped when the MS enters PMM-CONNECTED mode. NOTE 2: ISR is not activated when the network includes the T3324 value IE in the ATTACH ACCEPT message or ROUTING AREA UPDATE ACCEPT message. If the SGSN includes timer T the ROUTING AREA UPDATE REJECT message or the SERVICE REJECT message and timer T3346 is greater than timer T3312, the SGSN sets the mobile reachable timer and the implicit detach timer such that the sum of the timer values is greater than timer T3346. NOTE 3: According to subclause 4.7.5.1.5, if a periodic routing area updating procedure fails repeatedly, it can take more than 7 minutes before the MS starts using MM specific procedures. If the MS is both IMSI attached for GPRS and non-GPRS services, and if the MS lost coverage of the registered PLMN and timer T3312 expires or timer T3323 expires, then: a) if the MS returns to coverage in a cell that supports GPRS and that indicates that the network is in network operation mode I, then the MS shall either perform the combined routing area update procedure indicating "combined RA/LA updating with IMSI attach"; or b) if the MS returns to coverage in a cell in the same RA that supports GPRS and that indicates that the network is in network operation mode II, then the MS shall perform the periodic routing area updating procedure indicating "Periodic updating"; or c) if the MS was both IMSI attached for GPRS and non-GPRS services in network operation mode I and the MS returns to coverage in a cell in the same LA that does not support GPRS, then the MS shall perform the periodic location updating procedure. In addition, the MS shall perform a combined routing area update procedure indicating "combined RA/LA updating with IMSI attach" when the MS enters a cell that supports GPRS and that indicates that the network is in network operation mode I; or d) if the MS returns to coverage in a new RA, the description given in subclause 4.7.5 applies. If this subclause specifies that the MS shall perform a periodic routing area updating procedure, but subclause 4.7.5 specifies the MS shall perform a normal or combined routing area updating procedure, the description in subclause 4.7.5 takes precedence. If the MS is both IMSI attached for GPRS and non-GPRS services in a network that operates in network operation mode I, and if the MS has camped on a cell that does not support GPRS, and timer T3312 expires or timer T3323 expires, then the MS shall start an MM location updating procedure. In addition, the MS shall perform a combined routing area update procedure indicating "combined RA/LA updating with IMSI attach" when the MS enters a cell that supports GPRS and indicates that the network is in operation mode I. If timer T3312 expires or timer T3323 expires during an ongoing CS connection, then a MS operating in MS operation mode B shall treat the expiry of T3312 when the MM state MM-IDLE is entered, analogous to the descriptions for the cases when the timer expires out of coverage or in a cell that does not support GPRS. In A/Gb mode, timer T3312 and timer T3323 shall not be stopped when a GPRS MS enters state GMM-REGISTERED.SUSPENDED. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.2.2 |
5,737 | 6.2 RSRQ related measurements | a) This measurement provides a bin distribution (histogram) of the periodical E-UTRAN RSRQ measurements received from all of UEs in the measured E-UTRAN cell. To collect this measurement, the eNodeB needs to trigger the periodical UE measurement reports towards all of the UEs in the measured E-UTRAN cell. b) CC c) Receipt by the eNodeB from the UE of MeasurementReport message indicating a periodical UE measurement report where IE MeasResults field includes rsrqResult. The event triggered MeasurementReport messages are excluded. This measurement shall be increased for each reported value RSRQ_LEV (See in 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [18]). For every one or two RSRQ_LEV(s) a separate measurement is defined. (See in 3GPP TS 36.133[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management ] [19]) d) Each measurement is an integer value. e) MR. Rsrq.y y is an integer from 00 to 17. Note: 00 of y indicates RSRQ_00, namely RSRQ < -19.5dB, 01 of y indicates RSRQ_01 and RSRQ_02, namely -19.5 RSRQ < -18.5dB, 02 of y indicates RSRQ_03 and RSRQ_04, namely -18.5 RSRQ < -17.5dB, … 16 of y indicates RSRQ_31 and RSRQ_32, namely -4.5 RSRQ < -3.5dB, 17 of y indicates RSRQ_33 and RSRQ_34, namely -3.5dB RSRQ , (See in 3GPP TS36.133[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management ] [19]) f) EUtranCellTDD EUtranCellFDD g) Valid for packet switched traffic. h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 6.2 |
5,738 | 4.23.2 List of "PLMNs not allowed to operate at the present UE location" | For 3GPP satellite NG-RAN the UE shall store a list of "PLMNs not allowed to operate at the present UE location". Each entry consists of: a) the PLMN identity of the PLMN which sent a message including 5GMM cause value #78 "PLMN not allowed to operate at the present UE location" via satellite NG-RAN access technology; and b) the geographical location, if known by the UE, where 5GMM cause value #78 was received on satellite NG-RAN access technology; and c) if the geographical location exists, a UE implementation specific distance value. Before storing a new entry in the list, the UE shall delete any existing entry with the same PLMN identity. Upon storing a new entry, the UE starts a timer instance associated with the entry with an implementation specific value that shall not be set to a value smaller than the timer value indicated by the network in the Lower bound timer value IE, if any. If the Lower bound timer value IE was not provided by the network, the value of the timer shall be set based on the UE implementation. The UE is allowed to attempt to access a PLMN via satellite NG-RAN access technology which is part of the list of "PLMNs not allowed to operate at the present UE location" only if: a) the current UE location is known, a geographical location is stored for the entry of this PLMN, and the distance to the current UE location is larger than a UE implementation specific value; or b) the access is for emergency services (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] for further details). NOTE: When the UE is accessing network for emergency services, it is up to operator and regulatory policies whether the network needs to determine if the UE is in a location where network is not allowed to operate. The list shall accommodate three or more entries. The maximum number of entries is an implementation decision. When the list is full and a new entry has to be inserted, the oldest entry shall be deleted. Each entry shall be removed if for the entry: a) the UE successfully registers via satellite NG-RAN access technology to the PLMN stored in the entry except when the UE registers for emergency services; or b) the timer instance associated with the entry expires. The UE may delete the entry in the list, if the current UE location is known, a geographical location is stored for the entry of this PLMN, and the distance to the current UE location is larger than a UE implementation specific value. If the UE is in 5GMM-DEREGISTERED.LIMITED-SERVICE state and an entry from the list of "PLMNs not allowed to operate at the present UE location" is removed, the UE shall perform PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. When the UE is switched off, the UE shall keep the list of "PLMNs not allowed to operate at the present UE location" in its non-volatile memory. The UE shall delete the list of "PLMNs not allowed to operate at the present UE location" if the USIM is removed. If the UE is switched off when the timer instance associated with the entry in the list is running, the UE shall behave as follows when the UE is switched on and the USIM in the UE remains the same: let t1 be the time remaining for timer instance associated with the entry in the list to 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 and considered expired. If the UE is not capable of determining t, then the UE shall restart the timer with the value t1. | 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.23.2 |
5,739 | 5.30.2.10.4 Remote Provisioning of UEs in Onboarding Network | 5.30.2.10.4.1 General Remote Provisioning of UEs that registered with an Onboarding Network enables provisioning the UE with SNPN credentials for primary authentication and other information to enable access to the desired SNPN. Onboarding Services are provided using a PDU Session for DNN and S-NSSAI used for onboarding allowing remote provisioning of UEs via User Plane. The PDU Session may be restricted only to be used for Remote Provisioning of the UE. 5.30.2.10.4.2 Onboarding configuration for the UE In order to enable UP Remote Provisioning of SNPN credentials for a UE, UE Configuration Data for User Plane Remote Provisioning are either pre-configured on the UE or provided by the ONN. UE Configuration Data for User Plane Remote Provisioning provided by the ONN take precedence over corresponding configuration data stored in the UE. UE Configuration Data for User Plane Remote Provisioning consist of PVS IP address(es) and/or PVS FQDN(s). If the UE does not have any PVS IP address or PVS FQDN after the establishment of the PDU Session used for User Plane Remote Provisioning, the UE may construct an FQDN for PVS discovery as defined in TS 23.003[ Numbering, addressing and identification ] [19]. The UE Configuration Data for User Plane Remote Provisioning may be stored in the ME. The UE Configuration Data for User Plane Remote Provisioning (i.e. PVS IP address(es) or PVS FQDN(s), or both) may be: - locally configured in the SMF of ONN; and/or - provided by the DCS to the AMF of ON-SNPN as part of the authentication procedure as specified in TS 33.501[ Security architecture and procedures for 5G System ] [29] and sent by the AMF in the Nsmf_PDUSession_CreateSMContext Request message to the SMF If the SNPN acting as ON-SNPN is not capable to provide access to Localized Services, the PVS IP address(es) and/or PVS FQDN(s) provided by the DCS take precedence over the locally configured PVS IP address(es) and/or PVS FQDN(s) in the ON-SNPN. If the SNPN acting as ON-SNPN is capable to provides access to Localized Services, the SMF should include both DCS provided and the locally configured PVS IP address(es) and/or PVS FQDN(s), in the UE Configuration Data for User Plane Remote Provisioning. If the PCF is used for User Plane Remote Provisioning, the SMF provides the UE Configuration Data to the PCF as described in clause 5.30.2.10.4.3. The UE Configuration Data for User Plane Remote Provisioning may be provided to the UE during the establishment of the PDU Session used for User Plane Remote Provisioning as part of Protocol Configuration Options (PCO) in the PDU Session Establishment Response. NOTE: If there are multiple PVS IP addresses and/or PVS FQDNs in the UE, how the UE selects PVS from this information is up to UE implementation. 5.30.2.10.4.3 User Plane Remote Provisioning of UEs when Onboarding Network is an ON-SNPN The AMF selects an SMF used for User Plane Remote Provisioning using the SMF discovery and selection functionality as described in clause 6.3.2. The S-NSSAI and DNN of the AMF Onboarding Configuration Data may be used to discover and select an SMF for User Plane Remote Provisioning. Alternatively, for SMF selection, the AMF Onboarding Configuration Data may contain a configured SMF for the S-NSSAI and DNN used for onboarding. The AMF provides Onboarding Indication to SMF via Nsmf_PDUSession_CreateSMContext request message when a PDU Session used for User Plane Remote Provisioning is established. During PDU Session establishment for remote provisioning, the AMF may provide the PVS IP address(es) and/or PVS FQDN(s) to the SMF. When a UPF is selected for User Plane Remote Provisioning, the UPF selection function described in clause 6.3.3 for normal services is applied considering the S-NSSAI and DNN used for onboarding. The SMF or the PCF may store S-NSSAI and DNN information used for onboarding. Onboarding Configuration Data available to PCF (for details see TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]) and/or SMF may include PVS FQDN(s) and/or PVS IP address(es). The SMF and the PCF may use Onboarding Indication and DNN and S-NSSAI used for onboarding to access the Onboarding Configuration Data. NOTE: The SMF is aware about the PVS IP address(es) and/or PVS FQDN(s) in one of the following ways: either received from the AMF or retrieved locally from the Onboarding Configuration Data. When the UE registered for Onboarding (i.e. 5GS Registration Type is set to the value "SNPN Onboarding") successfully completes the User Plane Remote Provisioning of SNPN credentials via the Onboarding Network, then the UE should deregister from the Onboarding Network. Initial QoS parameters used for User Plane Remote Provisioning are configured in the SMF when dynamic PCC is not used. Dynamic PCC may be used for a PDU Session used for User Plane Remote Provisioning as described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. If a PCF is used and the AMF provided an Onboarding Indication, the SMF provides Onboarding Indication to the PCF when requesting an SM Policy Association. The SMF may provide the UE Configuration Data (i.e. PVS IP address(es) and/or PVS FQDN(s)) to the PCF when requesting an SM Policy Association. The QoS Flows of a restricted PDU Session, which is associated with the S-NSSAI/DNN used for Onboarding, shall be dedicated to Onboarding Services. The SMF may configure in the UPF PDR(s) and FAR(s) including PVS and DNS server IP addresses to block any traffic that is not from or to PVS and DNS server addresses. If the UE is registered for Onboarding (i.e. 5GS Registration Type is set to the value "SNPN Onboarding"), the network should apply S-NSSAI and DNN in the Onboarding Configuration Data for the PDU Session Establishment request from the UE. 5.30.2.10.4.4 User Plane Remote Provisioning of UEs when Onboarding Network is a PLMN Subscription data of such a UE shall contain the DNN and S-NSSAI used for onboarding. The AMF selects an SMF used for User Plane Remote Provisioning using the SMF discovery and selection functionality as described in clause 6.3.2, considering the DNN and S-NSSAI used for onboarding provided by the UE or the default DNN and S-NSSAI provided by UDM. The UPF selection function described in clause 6.3.3 is applied, considering the DNN and S-NSSAI used for onboarding. The SMF may be configured with one or more PVS FQDN(s) and/or PVS IP address(es) per DNN and S-NSSAI used for onboarding. When the UE requests a PDU Session used for User Plane Remote Provisioning by using DNN and S-NSSAI used for onboarding, the SMF sends the PVS FQDN(s) and/or PVS IP address(es) associated to the DNN and S-NSSAI of the PDU Session to the UE as part of Protocol Configuration Options (PCO) in the PDU Session Establishment Response if the following conditions are met: - the UE subscription data contains the DNN and S-NSSAI used for onboarding; and - the SMF has obtained the PVS FQDN(s) and/or PVS IP address(es) associated to the DNN and S-NSSAI of the PDU Session from local configuration; and - the UE has requested PVS information via PCO in PDU Session Establishment Request. NOTE 1: Local PCC or dynamic PCC can be used as described for PLMNs in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] and based on operator policy, PDR(s) and FAR(s) can be configured to restrict traffic other than provisioning traffic between PVS/DNS server(s) and UE(s). NOTE 2: If the UE receives multiple PVS IP addresses and/or PVS FQDNs, how the UE uses this information is up to UE implementation. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.30.2.10.4 |
5,740 | 6.6.4.1 COUNT-C | The ciphering sequence number COUNT-C is 32 bits long. There is one COUNT-C value per up-link radio bearer and one COUNT-C value per down-link radio bearer using RLC AM or RLC UM. For all transparent mode RLC radio bearers of the same CN domain COUNT-C is the same, and COUNT-C is also the same for uplink and downlink. COUNT-C is composed of two parts: a "short" sequence number and a "long" sequence number. The "short" sequence number forms the least significant bits of COUNT-C while the "long" sequence number forms the most significant bits of COUNT-C. The update of COUNT-C depends on the transmission mode as described below (see figure 16c). Figure 16c: The structure of COUNT-C for all transmission modes - For RLC TM on DCH, the "short" sequence number is the 8-bit connection frame number CFN of COUNT-C. It is independently maintained in the ME MAC-d entity and the SRNC MAC-d entity. The "long" sequence number is the 24-bit MAC-d HFN, which is incremented at each CFN cycle. - For RLC UM mode, the "short" sequence number is the 7-bit RLC sequence number (RLC SN) and this is part of the RLC UM PDU header. The "long" sequence number is the 25-bit RLC UM HFN which is incremented at each RLC SN cycle. - For RLC AM mode, the "short" sequence number is the 12-bit RLC sequence number (RLC SN) and this is part of the RLC AM PDU header. The "long" sequence number is the 20-bit RLC AM HFN which is incremented at each RLC SN cycle. The hyperframe number HFN is initialised by means of the parameter START, which is described in section 6.4.8. The ME and the RNC then initialise the 20 most significant bits of the RLC AM HFN, RLC UM HFN and MAC-d HFN to START. The remaining bits of the RLC AM HFN, RLC UM HFN and MAC-d HFN are initialised to zero. When a new radio bearer is created during a RRC connection in ciphered mode, the HFN is initialised by the current START value (see section 6.4.8). | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.6.4.1 |
5,741 | 9.3.19.2 Release complete (mobile station to network direction) | This message is sent from the mobile station to the network to indicate that the mobile station has released the transaction identifier and that the network shall release the transaction identifier. See table 9.69a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: RELEASE COMPLETE Significance: local (note) Direction: mobile station to network direction Table 9.69a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : RELEASE COMPLETE message content (mobile station to network direction) NOTE: This message has local significance; however, it may carry information of global significance when used as the first call clearing 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 | 9.3.19.2 |
5,742 | 16.1.6.2 Redundant data transmission via single UPF and single RAN node | Two NG-U tunnels are setup between single UPF and single NG-RAN node for redundant transmission of the QoS flows when PDU session setup or modification is initiated. The two NG-U tunnels are transferred via disjointed transport layer paths. The 5GC provides the indicator per QoS flow to the NG-RAN for the redundant transmission. For downlink, the NG-RAN node eliminates the duplicated packets per QoS flow. For uplink, the NG-RAN node replicates the packets and transmits them via the two NG-U tunnels. The indicator per QoS flow for redundant transmission is transferred to the target NG-RAN node in case of handover. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.1.6.2 |
5,743 | 8.109 Presence Reporting Area Information | Presence Reporting Area Information is coded as depicted in Figure 8.109-1. Figure 8.109-1: Presence Reporting Area Information The PRA Identifier in octets 5 to 7 shall be present and shall contain the identifier of the PRA the UE is entering or leaving. It shall be encoded using full hexadecimal representation (binary, not ASCII encoding). The PRA Identifier is defined in clause 19.10 of 3GPP TS 23.003[ Numbering, addressing and identification ] [2]. The PRA Identifier in the Octets 5 to 7 shall be set to the PRA Set ID if the MME/SGSN is requested to report the change of UE presence in a PRA Set. In this case: - the Additional PRA (APRA) flag in octet 8 shall be set to 1 if the reporting of change of UE presence for the PRA Set is active and the UE presence has changed for at least one PRA within the PRA Set (i.e. if the UE enters or leaves the PRA Set, or the UE moves between the PRAs within the PRA Set). The subsequent 4 octets shall then be present and shall contain the identifier of the individual PRA within the PRA Set which the UE has newly entered or left, with the information of whether the UE is inside or outside this PRA. - the Additional PRA (APRA) flag in octet a+3 shall be set to 1 if the UE presence status has changed for more than one individual PRA within the PRA Set. In that case, the subsequent 4 Octets shall be included and encoded as specified above for the octets a to a+3. The MME/SGSN shall report each individual PRA(s) within the PRA Set that the UE has newly entered or left. - if the reporting of change of UE presence for the PRA Set is inactive, i.e. the INAPRA flag in octet 8 is set to 1, then the Additional PRA (APRA) flag in octet 8 shall not be set to 1 and no Additional PRA Identifier shall be included. The Inside PRA flag (IPRA) shall be set to 1 if the UE is inside or enters the Presence Reporting Area identified by the PRA Identifier. The Outside PRA flag (OPRA) shall be set to 1 if the UE is outside or leaves the Presence Reporting Area identified by the PRA Identifier. The Inactive PRA (INAPRA) flag in octet 8 shall be set to 1 if the PRA is inactive in the MME/SGSN, i.e. the reporting of change of UE presence in this PRA is currently deactivated in the MME/SGSN, e.g. due to an overload situation. Either the IPRA or the OPRA flag or the INAPRA shall be set to 1, not several ones, for a given Presence Reporting Area Identifier. | 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.109 |
5,744 | 4.3.15 Selected IP Traffic Offload (SIPTO) function | The SIPTO function enables an operator to offload certain types of traffic at a network node close to that UE's point of attachment to the access network. The SIPTO function specified in this TS applies to IP PDN Types and Ethernet and Non-IP PDN Types. SIPTO above RAN can be achieved by selecting a set of GWs (S-GW and P-GW) that is geographically/topologically close to a UE's point of attachment. SIPTO above RAN corresponds to a traffic offload through a P-GW located in the mobile operator's core network. SIPTO applies to both the non-roaming case and, provided appropriate roaming agreements are in place between the operators, to the roaming case. Offload of traffic for a UE is available for UTRAN and E-UTRAN accesses only. When the UE enters to UTRAN/E-UTRAN from another type of access network (e.g., from GERAN), it is the responsibility of the new SGSN/MME to decide whether to perform deactivation with reactivation request for a given PDN connection, depending on SIPTO permissions for the relevant APN. Realization for SIPTO above RAN relies on the same architecture models and principles as for local breakout described in clause 4.2. In order to select a set of appropriate GW (S-GW and P-GW) based on geographical/topological proximity to UE, the GW selection function specified in TS 29.303[ Domain Name System Procedures; Stage 3 ] [61] uses the UE's current location information. In order for the operator to allow/prohibit SIPTO on per user and per APN basis, subscription data in the HSS is configured to indicate to the MME if offload is allowed or prohibited. If the SIPTO permissions information from the HSS conflicts with MME's configuration for that UE, then SIPTO is not used. If HSS indicates VPLMN address not allowed, then VPLMN (i.e. MME) shall not provide SIPTO. In the absence of any SIPTO permissions indication from the HSS the VPLMN (i.e MME) shall not provide SIPTO. The MME may be configured on a per APN basis as to whether or not to use SIPTO (e.g. to handle the case where the HSS is not configured with SIPTO information for the UE). For SIPTO above RAN, as a result of UE mobility (e.g. detected by the MME at TAU or SGSN at RAU or movement from GERAN), the target MME may wish to redirect a PDN connection towards a different GW that is more appropriate for the UE's current location, e.g. MME may know whether the UE's new location is served by the same GW as the old one. When the MME decides upon the need for GW relocation, the MME deactivates the impacted PDN connections indicating "reactivation requested" as specified in clause 5.10.3. If all of the PDN connections for the UE need to be relocated, the MME may initiate the "explicit detach with reattach required" procedure as specified in clause 5.3.8.3. NOTE: If either of the above procedures for GW relocation are initiated while the UE has active applications, it may cause disruption of services that are affected if the IP address changes. | 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.15 |
5,745 | 5.35A.2 Configuration of the MBSR | In order for an MBSR to operate as a mobile IAB node, it receives configuration from the OAM system of the serving PLMN as specified in TS 38.401[ NG-RAN; Architecture description ] [42]. The MBSR IAB-UE establishes a secure and trusted connection to the OAM server only if it is authorized to operate as MBSR in the serving PLMN as defined in TS 38.401[ NG-RAN; Architecture description ] [42]. In addition, the MBSR(IAB-UE) is assumed to be configured with preferred PLMN lists and forbidden PLMNs by the HPLMN to perform PLMN selection as specified in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17]. When a PDU session is used for the MBSR to access the OAM server, the MBSR establishes a dedicated PDU session for the OAM traffic. The serving PLMN provides an Allowed NSSAI and establishes the PDU session for the OAM server access, considering the S-NSSAI and DNN requested by MBSR and/or the default values in subscription data. The MBSR can be (pre-)configured with UE policy or provisioned using existing UE Policy mechanism as defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] including the OAM access PDU session parameters for the authorized PLMNs. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.35A.2 |
5,746 | 14.2 Home network realm | The home network realm shall be in the form of an Internet domain name, e.g. operator.com, as specified in RFC 1035 [19]. When attempting to authenticate within WLAN access, the WLAN UE shall derive the home network domain name from the IMSI as described in the following steps: 1. take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [27], 3GPP TS 51.011[ Specification of the Subscriber Identity Module - Mobile Equipment (SIM-ME) interface ] [66]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning; 2. use the MCC and MNC derived in step 1 to create the "mnc<MNC>.mcc<MCC>. 3gppnetwork.org" domain name; 3. add the label "wlan." to the beginning of the domain name. An example of a WLAN NAI realm is: IMSI in use: 234150999999999; Where: MCC = 234; MNC = 15; MSIN = 0999999999 Which gives the home network domain name: wlan.mnc015.mcc234.3gppnetwork.org. NOTE: If it is not possible for the WLAN UE to identify whether a 2 or 3 digit MNC is used (e.g. SIM is inserted and the length of MNC in the IMSI is not available in the "Administrative data" data file), it is implementation dependent how the WLAN UE determines the length of the MNC (2 or 3 digits). | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 14.2 |
5,747 | 24.11 ProSe Discovery UE ID 24.11.1 General | The ProSe Discovery UE ID as described in 3GPP TS 23.303[ Proximity-based services (ProSe); Stage 2 ] [103] identifies the UE participating in restricted ProSe direct discovery in the context of the ProSe Function. It is composed of two parts as follows: - The PLMN ID of the ProSe Function that assigned the ProSe Discovery UE ID, i.e. Mobile Country Code (MCC) and Mobile Network Code (MNC). - A temporary identifier allocated by the ProSe Function. The content of the temporary identifier is not specified in 3GPP. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 24.11 |
5,748 | 10.2.2.2 UE sets up an IMS Emergency session with emergency registration | UEs that are in limited service state (LSM) request emergency services by initiating the Registration procedure with the indication that the registration is to receive emergency services, referred to as Emergency Registration. UEs that had earlier registered for normal services but now cannot be authenticated by the serving network, shall initiate Emergency Registration procedure to request emergency services. It shall be possible to configure whether the network allows or rejects an emergency registration request and whether it allows unauthenticated UEs to establish bearers for unauthenticated IMS emergency sessions or not. The AMF may attempt to authenticate the UE after receiving the emergency registration request. If authentication failed in the UE during an emergency registration request, the UE shall wait for a NAS SMC command to set up an unauthenticated emergency bearer. If authentication failed in the serving network and if the serving network policy does not allow unauthenticated IMS Emergency Sessions, the UE and AMF shall proceed as with the normal initial registration requests. The AMF shall reject the unauthenticated emergency bearer setup request from the UE. If authentication failed in the serving network and if the serving network policy allow unauthenticated IMS Emergency Sessions, then the AMF shall support unauthenticated emergency bearer setup and the behaviours of the UE and the AMF are as described below. a) UE behaviour: After sending Emergency Registration request to the serving network the UE shall know of its own intent to establish an unauthenticated IMS Emergency Session. The UE shall proceed as specified for the non-emergency case in except that the UE shall accept a NAS SMC selecting NEA0 and NIA0 algorithms from the AMF. If the UE accepts a NAS SMC selecting NEA0 and NIA0 algorithms from the AMF as part of Emergency Registration request, then the primary authentication performed if any shall be considered as unsuccessful and the newly generated KAUSF is not stored. NOTE: In case of authentication success the AMF will send a NAS SMC selecting algorithms with a non-NULL integrity algorithm, and the UE will accept it. b) AMF behavior: After receiving Emergency Registration request from the UE, the AMF knows of that UE's intent to establish an unauthenticated IMS Emergency Session. - If the AMF cannot identify the subscriber, or cannot obtain authentication vector (when SUPI is provided), the AMF shall send NAS SMC with NULL algorithms to the UE regardless of the supported algorithms announced previously by the UE. - After the unsuccessful verification of the UE, the AMF shall send NAS SMC with NULL algorithms to the UE regardless of the supported algorithms announced previously by the UE. - If both, the Emergency Registration request and an AUTHENTICATION FAILURE message with error code as defined in 24.501 [35] clauses 5.4.1.2.4.5 (for EAP based authentication) or 5.4.1.3.7 (for 5G AKA based authentication) are received by the AMF from the UE, then the AMF shall send NAS SMC with NULL algorithms to the UE regardless of the supported algorithms announced previously by the UE. If the UE has initiated a PDU session establishment procedure to establish bearers for unauthenticated IMS emergency sessions and the AMF has indicated to the SMF that this is an unauthenticated emergency call, then the SMF shall indicate 'Not Needed' in the UP security policy for both UP confidentiality and UP integrity protection to the ng-eNB/gNB. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 10.2.2.2 |
5,749 | 5.31.7.4 MICO mode with Active Time | During a Registration procedure the UE may optionally request an Active Time value from the AMF as part of MICO Mode negotiation. In response, if the AMF receives an Active Time value from the UE and determines that the MICO mode is allowed for the UE, the AMF may assign an Active Time value for the UE, e.g. based on local configuration, Expected UE Behaviour if available, UE requested Active Time value, UE subscription information and network policies, and indicates it to the UE during Registration procedure. When an Active Time value is assigned to the UE the AMF shall consider the UE reachable for paging after the transition from CM-CONNECTED to CM-IDLE for the duration of the Active Time. Together with the Active Time value, the UE may request a periodic registration time value as specified in clause 5.31.7.45. When the AMF indicates MICO mode with an Active Time to a UE, the registration area may be constrained by paging area size. To avoid paging in the entire PLMN, when the AMF allocates the Active Time the AMF should not allocate "all PLMN" registration area to the UE. The UE and AMF shall set a timer corresponding to the Active Time value negotiated during the most recent Registration procedure. The UE and AMF shall start the timer upon entering CM-IDLE state from CM-CONNECTED. When the timer expires (i.e. reaches the Active Time) the UE enters MICO mode and the AMF can deduce that the UE has entered MICO mode and is not available for paging. If the UE enters CM-CONNECTED state before the timer expires, the UE and AMF shall stop and reset the timer. If no Active Time value was negotiated during the most recent Registration procedure the UE shall not start the timer and it shall instead enter MICO mode directly upon entering CM-IDLE state. Active Time is not transferred between AMF and MME. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.31.7.4 |
5,750 | 8.13.2.4.1 Minimum Requirement Enhanced Performance Requirement Type A – Single-layer Spatial Multiplexing with TM9 interference model (User-Specific Reference Symbols) | The purpose of these tests is to verify closed loop rank one performance on one of the antenna ports 7 or 8 without a simultaneous transmission on the other antenna port in the serving cell when the PDSCH transmission in the serving cell is interfered by PDSCH of one dominant interfering cell applying transmission mode 9 interference model defined in clause B.5.4. In 8.13.2.4.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.2.4.1-3, based on single carrier requirement specified in Table 8.13.2.4.1-2, with the addition of the parameters in Table 8.13.2.4.1-1 and the downlink physical channel setup according to Annex C.3.2. Table 8.13.2.4.1-1: Test Parameters for Testing CDM-multiplexed DM RS (single layer) with TM9 interference model for CA Table 8.13.2.4.1-2: Single carrier performance for multiple CA configurations Enhanced Performance Requirement Type A, CDM-multiplexed DM RS Table 8.13.2.4.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.2.4.1 |
5,751 | 5.9.3.2 Initiation | The UE applies the broadcast MRB establishment procedure to start receiving an MBS session of an MBS broadcast service it is interested in. The procedure may be initiated e.g. upon start of the MBS session, upon entering a cell providing an MBS broadcast service the UE is interested in, upon becoming interested in the ongoing MBS broadcast service, upon removal of the UE capability limitations inhibiting reception of the ongoing MBS broadcast service UE is interested in. The UE applies the broadcast MRB release procedure to stop receiving a session of an MBS broadcast service. The procedure may be initiated e.g. upon stop of the MBS session, upon leaving the cell broadcasting the MBS service the UE is interested in, upon losing interest in the MBS service, when capability limitations start inhibiting reception of the concerned service. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.9.3.2 |
5,752 | 7.1.4 Network Function Service Authorization | NF service authorization shall ensure the NF Service Consumer is authorized to access the NF service provided by the NF Service Provider, according to e.g. the policy of NF, the policy from the serving operator, the inter-operator agreement. Service authorization information shall be configured as one of the components in NF profile of the NF Service Producer. It shall include the NF type (s) and NF realms/origins allowed to consume NF Service(s) of NF Service Producer. Due to roaming agreements and operator policies, a NF Service Consumer shall be authorised based on UE/subscriber/roaming information and NF type, the Service authorization may entail two steps: - Check whether the NF Service Consumer is permitted to discover the requested NF Service Producer instance during the NF service discovery procedure. This is performed on a per NF granularity by NRF. NOTE 1: When NF discovery is performed based on local configuration, it is assumed that locally configured NFs are authorized. - Check whether the NF Service Consumer is permitted to access the requested NF Service Producer for consuming the NF service, with a request type granularity. This is performed on a per UE, subscription or roaming agreements granularity. This type of NF Service authorization shall be embedded in the related NF service logic. NOTE 2: The security of the connection between NF Service Consumer and NF Service Producer is specified in TS 33.501[ Security architecture and procedures for 5G System ] [29]. NOTE 3: It is expected that an NF authorization framework exists in order to perform consumer NF authorization considering UE, subscription or roaming agreements granularity. This authorization is assumed to be performed without configuration of the NRF regarding UE, subscription or roaming information. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 7.1.4 |
5,753 | 5.7.3F Carrier frequency and EARFCN for category NB1 and NB2 | The carrier frequency of category NB1/NB2 in the downlink is designated by the E-UTRA Absolute Radio Frequency Channel Number (EARFCN) in the range 0 – 262143 and the Offset of category NB1/NB2 Channel Number to EARFCN in the range {-10,-9,-8,-7,-6,-5,-4,-3,-2,-1,-0.5,0,1,2,3,4,5,6,7,8,9} for FDD and in the range {-10,-9,-8.5,-8,-7,-6,-5,-4.5,-4,-3,-2,-1,-0.5,0,1,2,3,3.5,4,5,6,7,7.5,8,9} for TDD. The relation between EARFCN, Offset of category NB1/NB2 Channel Number to EARFCN and the carrier frequency in MHz for the downlink is given by the following equation, where FDL is the downlink carrier frequency of category NB1/NB2, FDL_low and NOffs-DL are given in table 5.7.3-1, NDL is the downlink EARFCN, MDL is the Offset of category NB1/NB2 Channel Number to downlink EARFCN. FDL = FDL_low + 0.1(NDL – NOffs-DL) + 0.0025*(2MDL+1) The carrier frequency of category NB1/NB2 in the uplink is designated by the E-UTRA Absolute Radio Frequency Channel Number (EARFCN) in the range 0 –262143, and the Offset of category NB1/NB2 Channel Number to EARFCN in the range {-10,-9,-8,-7,-6,-5,-4,-3,-2,-1,0,1,2,3,4,5,6,7,8,9} for FDD and in the range {-11,-10,-9.5,-9,-8.5, -8,-7.5,-7,-6.5,-6,-5.5,-5,-4.5,-4,-3.5,-3,-2.5,-2,-1.5,-1,-0.5,0,0.5,1,1.5,2,2.5,3,3.5,4,4.5,5,5.5,6,6.5,7,7.5,8,8.5,9,9.5,10, 11} for TDD. The relation between EARFCN, Offset of category NB1/NB2 Channel Number to EARFCN and the carrier frequency in MHz for the uplink is given by the following equation, where FUL is the uplink carrier frequency of category NB1/NB2, FUL_low and NOffs-UL are given in table 5.7.3-1, NUL is the uplink EARFCN, MUL is the Offset of category NB1/NB2 Channel Number to uplink EARFCN. FUL = FUL_low + 0.1(NUL – NOffs-UL) + 0.0025*(2MUL) NOTE 1: For category NB1/NB2, NDL or NUL is different than the value of EARFCN that corresponds to E-UTRA downlink or uplink carrier frequency for in-band and guard band operation. NOTE 2: For FDD MDL = -0.5 is not applicable for in-band and guard band operation. For TDD MDL {-0.5,+3.5,-4.5,+7.5,-8.5} is not applicable for in-band and guard band operation. NOTE 3: For the carrier including NPSS/NSSS for in-band and guard band operation, MDL is selected from {-2,-1,0,1}. NOTE 4: For the carrier including NPSS/NSSS for stand-alone operation, MDL = -0.5. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.7.3F |
5,754 | 5.4.4.3 Generic UE configuration update accepted by the UE | Upon receiving the CONFIGURATION UPDATE COMMAND message, the UE shall stop timer T3346 if running and use the contents to update appropriate information stored within the UE. If "acknowledgement requested" is indicated in the Acknowledgement bit of the Configuration update indication IE in the CONFIGURATION UPDATE COMMAND message, the UE shall send a CONFIGURATION UPDATE COMPLETE message. If the UE receives a new 5G-GUTI in the CONFIGURATION UPDATE COMMAND message, the UE shall consider the new 5G-GUTI as valid, the old 5G-GUTI as invalid, stop timer T3519 if running, and delete any stored SUCI; otherwise, the UE shall consider the old 5G-GUTI as valid. The UE shall provide the 5G-GUTI to the lower layer of 3GPP access if the CONFIGURATION UPDATE COMMAND message is sent over the non-3GPP access, and the UE is in 5GMM-REGISTERED in both 3GPP access and non-3GPP access in the same PLMN. If the UE receives a new TAI list in the CONFIGURATION UPDATE COMMAND message, the UE shall consider the new TAI list as valid and the old TAI list as invalid; otherwise, the UE shall consider the old TAI list as valid. If the registration area contains TAIs belonging to different PLMNs, which are equivalent PLMNs, and a) the UE already has stored allowed NSSAI for the current registration area, the UE shall store the allowed NSSAI for the current registration area in each of the allowed NSSAIs which are associated with each of the PLMNs in the registration area; b) the UE already has stored rejected NSSAI for the current registration area, the UE shall store the rejected NSSAI for the current registration area in each of the rejected NSSAIs which are associated with each of the PLMNs in the registration area; c) the UE already has stored rejected NSSAI for the failed or revoked NSSAA, the UE shall store the rejected NSSAI for the failed or revoked NSSAA in each of the rejected NSSAIs which are associated with each of the PLMNs in the registration area; d) the UE already has stored rejected NSSAI for the maximum number of UEs reached, the UE shall store the rejected NSSAI for the maximum number of UEs reached in each of the rejected NSSAIs which are associated with each of the PLMNs in the registration area; and e) the UE already has stored pending NSSAI, the UE shall store the pending NSSAI in each of the pending NSSAIs which are associated with each of the PLMNs in the registration area. If the UE receives a new truncated 5G-S-TMSI configuration in the CONFIGURATION UPDATE COMMAND message, the UE shall consider the new truncated 5G-S-TMSI configuration as valid and the old truncated 5G-S-TMSI configuration as invalid; otherwise, the UE shall consider the old truncated 5G-S-TMSI configuration as valid. If the UE receives a new service area list in the CONFIGURATION UPDATE COMMAND message, the UE shall consider the new service area list as valid and the old service area list as invalid; otherwise, the UE shall consider the old service area list, if any, as valid. If the UE receives new NITZ information in the CONFIGURATION UPDATE COMMAND message, the UE considers the new NITZ information as valid and the old NITZ information as invalid; otherwise, the UE shall consider the old NITZ information as valid. If the UE receives a LADN information IE in the CONFIGURATION UPDATE COMMAND message, the UE shall consider the old LADN information as invalid and the new LADN information as valid, if any; otherwise, the UE shall consider the old LADN information as valid. If the UE receives an Extended LADN information IE in the CONFIGURATION UPDATE COMMAND message, the UE shall consider the old extended LADN information as invalid and the new extended LADN information as valid, if any; otherwise, the UE shall consider the old extended LADN information as valid. If the UE receives a new allowed NSSAI for the associated access type in the CONFIGURATION UPDATE COMMAND message, the UE shall consider the new allowed NSSAI as valid for the associated access type, store the allowed NSSAI for the associated access type as specified in subclause 4.6.2.2 and consider the old allowed NSSAI for the associated access type as invalid; otherwise, the UE shall consider the old allowed NSSAI as valid for the associated access type. If the UE receives a new configured NSSAI in the CONFIGURATION UPDATE COMMAND message, the UE shall consider the new configured NSSAI for the registered PLMN or SNPN as valid and the old configured NSSAI for the registered PLMN or SNPN as invalid; otherwise, the UE shall consider the old configured NSSAI for the registered PLMN or SNPN as valid. The UE shall store the new configured NSSAI as specified in subclause 4.6.2.2. In addition, if the CONFIGURATION UPDATE COMMAND message contains: a) an NSSRG information IE, the UE shall store the contents of the NSSRG information IE as specified in subclause 4.6.2.2. If the UE receives a new configured NSSAI in the CONFIGURATION UPDATE COMMAND message and no NSSRG information IE, the UE shall delete any stored NSSRG information, if any, as specified in subclause 4.6.2.2; NOTE 1: When the UE receives the NSSRG information IE, the UE may provide the NSSRG information to lower layers for the purpose of NSAG-aware cell reselection. b) an S-NSSAI location validity information IE, the UE shall store the contents of the S-NSSAI location validity information IE as specified in subclause 4.6.2.2. If the UE receives a new configured NSSAI in the CONFIGURATION UPDATE COMMAND message and no S-NSSAI location validity information IE, the UE shall delete any stored S-NSSAI location validity information, if any, as specified in subclause 4.6.2.2; c) an S-NSSAI time validity information IE, the UE shall store the contents of the S-NSSAI time validity information IE as specified in subclause 4.6.2.2. If the UE receives a new configured NSSAI in the CONFIGURATION UPDATE COMMAND message and no S-NSSAI time validity information IE, the UE shall delete any stored S-NSSAI time validity information, if any, as specified in subclause 4.6.2.2; or d) an On-demand NSSAI IE, the UE shall store the contents of the On-demand NSSAI IE as specified in subclause 4.6.2.2. If the UE receives a new Configured NSSAI IE in the CONFIGURATION UPDATE COMMAND message and no On-demand NSSAI IE, the UE shall delete any stored on-demand NSSAI as specified in subclause 4.6.2.2. The UE shall stop slice deregistration inactivity timer, if running for the S-NSSAI which is deleted from the on-demand NSSAI. If the UE receives the Network slicing indication IE in the CONFIGURATION UPDATE COMMAND message with the Network slicing subscription change indication set to "Network slicing subscription changed", the UE shall delete the network slicing information for each and every PLMN or SNPN except for the current PLMN or SNPN as specified in subclause 4.6.2.2 and remove all tracking areas from the list of "5GS forbidden tracking areas for roaming" which were added due to rejection of S-NSSAI due to "S-NSSAI not available in the current registration area". If the UE receives Operator-defined access category definitions IE in the CONFIGURATION UPDATE COMMAND message and the Operator-defined access category definitions IE contains one or more operator-defined access category definitions, the UE shall delete any operator-defined access category definitions stored for the RPLMN and shall store the received operator-defined access category definitions for the RPLMN. If the UE receives the Operator-defined access category definitions IE in the CONFIGURATION UPDATE COMMAND message and the Operator-defined access category definitions IE contains no operator-defined access category definitions, the UE shall delete any operator-defined access category definitions stored for the RPLMN. If the CONFIGURATION UPDATE COMMAND message does not contain the Operator-defined access category definitions IE, the UE shall not delete the operator-defined access category definitions stored for the RPLMN. If the UE receives the SMS indication IE in the CONFIGURATION UPDATE COMMAND message with the SMS availability indication set to: a) "SMS over NAS not available", the UE shall consider that SMS over NAS transport is not allowed by the network; and b) "SMS over NAS available", the UE may request the use of SMS over NAS transport by performing a registration procedure for mobility and periodic registration update as specified in subclause 5.5.1.3, after the completion of the generic UE configuration update procedure. If the UE receives the CAG information list IE or the Extended CAG information list IE in the CONFIGURATION UPDATE COMMAND message, the UE shall: a) replace the "CAG information list" stored in the UE with the received CAG information list IE or the Extended CAG information list IE when received in the HPLMN or EHPLMN; NOTE 2: When the UE receives the CAG information list IE or the Extended CAG information list IE in the HPLMN derived from the IMSI, the EHPLMN list is present and is not empty and the HPLMN is not present in the EHPLMN list, the UE behaves as if it receives the CAG information list IE or the Extended CAG information list IE in a VPLMN. b) replace the serving VPLMN's entry of the "CAG information list" stored in the UE with the serving VPLMN's entry of the received CAG information list IE or the Extended CAG information list IE when the UE receives the CAG information list IE or the Extended CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN; or NOTE 3: When the UE receives the CAG information list IE or the Extended CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN, entries of a PLMN other than the serving VPLMN, if any, in the received CAG information list IE or the Extended CAG information list IE are ignored. c) remove the serving VPLMN's entry of the "CAG information list" stored in the UE when the UE receives the CAG information list IE or the Extended CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN and the CAG information list IE or the Extended CAG information list IE does not contain the serving VPLMN's entry. The UE shall store the "CAG information list" received in the CAG information list IE or the Extended CAG information list IE as specified in annex C. If the received "CAG information list" includes an entry containing the identity of the current PLMN and the UE had set the CAG bit to "CAG supported" in the 5GMM capability IE of the REGISTRATION REQUEST message, the UE shall operate as follows. a) If the UE receives the CONFIGURATION UPDATE COMMAND message via a CAG cell, none of the CAG-ID(s) supported by the current CAG cell is authorized based on the "Allowed CAG list" of the entry for the current PLMN in the received "CAG information list", and: 1) the entry for the current PLMN in the received "CAG information list" does not include an "indication that the UE is only allowed to access 5GS via CAG cells", then the UE shall enter the state 5GMM-REGISTERED.LIMITED-SERVICE and shall search for a suitable cell according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C] with the updated "CAG information list"; or 2) the entry for the current PLMN in the received "CAG information list" includes an "indication that the UE is only allowed to access 5GS via CAG cells" and: i) if one or more CAG-ID(s) are authorized based on the "Allowed CAG list" of the entry for the current PLMN in the received "CAG information list", the UE shall enter the state 5GMM-REGISTERED.LIMITED-SERVICE and shall search for a suitable cell according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] with the updated "CAG information list"; or ii) if no CAG-ID is authorized based on the "Allowed CAG list" of the entry for the current PLMN in the received "CAG information list" and: A) the UE does not have an emergency PDU session, then the UE shall enter the state 5GMM-REGISTERED.PLMN-SEARCH and shall apply the PLMN selection process defined in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] with the updated "CAG information list"; or B) the UE has an emergency PDU session, then the UE shall perform a local release of all PDU sessions associated with 3GPP access except for the emergency PDU session and enter the state 5GMM-REGISTERED.LIMITED-SERVICE; or b) If the UE receives the CONFIGURATION UPDATE COMMAND message via a non-CAG cell and the entry for the current PLMN in the received "CAG information list" includes an "indication that the UE is only allowed to access 5GS via CAG cells" and: 1) if one or more CAG-ID(s) are authorized based on the "allowed CAG list" for the current PLMN in the received "CAG information list", the UE shall enter the state 5GMM-REGISTERED.LIMITED-SERVICE and shall search for a suitable cell according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] with the updated "CAG information list"; or 2) if no CAG-ID is authorized based on the "Allowed CAG list" of the entry for the current PLMN in the received "CAG information list"and: i) the UE does not have an emergency PDU session, then the UE shall enter the state 5GMM-REGISTERED.PLMN-SEARCH and shall apply the PLMN selection process defined in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] with the updated "CAG information list"; or ii) the UE has an emergency PDU session, then the UE shall perform a local release of all PDU sessions associated with 3GPP access except for the emergency PDU session and enter the state 5GMM-REGISTERED.LIMITED-SERVICE. If the received "CAG information list" does not include an entry containing the identity of the current PLMN and the UE receives the CONFIGURATION UPDATE COMMAND message via a CAG cell, the UE shall enter the state 5GMM-REGISTERED.LIMITED-SERVICE and shall search for a suitable cell according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C] with the updated "CAG information list". If the CONFIGURATION UPDATE COMMAND message indicates "registration requested" in the Registration requested bit of the Configuration update indication IE and: a) contains no other parameters or contains at least one of the following parameters: a new allowed NSSAI, a new partially allowed NSSAI, a new configured NSSAI, a new NSSRG information or the Network slicing subscription change indication, and: 1) an emergency PDU session exists, the UE shall, after the completion of the generic UE configuration update procedure and the release of the emergency PDU session, release the existing N1 NAS signalling connection. Additionally, the UE shall: i) if any Tsor-cm timer(s) were running and have stopped, attempt to obtain service on a higher priority PLMN (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]); or ii) in all other cases, start a registration procedure for mobility and periodic registration update as specified in subclause 5.5.1.3; or 2) no emergency PDU Session exists, the UE shall, after the completion of the generic UE configuration update procedure and the release of the existing N1 NAS signalling connection: i) if any Tsor-cm timer(s) were running and have stopped, attempt to obtain service on a higher priority PLMN (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]); or ii) in all other cases, start a registration procedure for mobility and periodic registration update as specified in subclause 5.5.1.3; b) a MICO indication is included without a new allowed NSSAI, a new configured NSSAI, a new NSSRG information or the Network slicing subscription change indication, the UE shall, after the completion of the generic UE configuration update procedure, start a periodic registration procedure for mobility and registration update as specified in subclause 5.5.1.3 to re-negotiate MICO mode with the network; c) an Additional configuration indication IE is included, and: 1) "release of N1 NAS signalling connection not required" is indicated in the Signalling connection maintain request bit of the Additional configuration indication IE; and 2) a new allowed NSSAI, a new configured NSSAI, a new NSSRG information or the Network slicing subscription change indication is not included in the CONFIGURATION UPDATE COMMAND message, the UE shall, after the completion of the generic UE configuration update procedure, start a registration procedure for mobility and periodic registration update as specified in subclause 5.5.1.3; or d) a UE radio capability ID deletion indication IE set to "Network-assigned UE radio capability IDs deletion requested" is included, and: 1) the UE is not in NB-N1 mode; 2) a new allowed NSSAI, a new configured NSSAI, a new NSSRG information or a Network slicing subscription change indication is not included; and 3) the UE has set the RACS bit to "RACS supported" in the 5GMM capability IE of the REGISTRATION REQUEST message, the UE shall, after the completion of the generic UE configuration update procedure, start a registration procedure for mobility and periodic registration update as specified in subclause 5.5.1.3. The UE receiving the rejected NSSAI in the CONFIGURATION UPDATE COMMAND message takes the following actions based on the rejection cause in the rejected S-NSSAI(s): "S-NSSAI not available in the current PLMN or SNPN" The UE shall add the rejected S-NSSAI(s) in the rejected NSSAI for the current PLMN or SNPN as specified in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI(s) in the current PLMN or SNPN over any access until switching off the UE, the UICC containing the USIM is removed, the entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) are removed as described in subclause 4.6.2.2. "S-NSSAI not available in the current registration area" The UE shall add the rejected S-NSSAI(s) in the rejected NSSAI for the current registration area as specified in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI(s) in the current registration area over the current access until switching off the UE, the UE moving out of the current registration area, the UICC containing the USIM is removed, the entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) are removed as described in subclause 4.6.2.2. "S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization" The UE shall add the rejected S-NSSAI(s) in the rejected NSSAI for the failed or revoked NSSAA as specified in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI in the current PLMN or SNPN over any access until switching off the UE, the UICC containing the USIM is removed, the entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) are removed as described in subclause 4.6.1 and 4.6.2.2. "S-NSSAI not available due to maximum number of UEs reached" Unless the back-off timer value received along with the S-NSSAI is zero, the UE shall add the rejected S-NSSAI(s) in the rejected NSSAI for the maximum number of UEs reached as specified in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI in the current PLMN or SNPN over the current access until switching off the UE, the UICC containing the USIM is removed, the entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) are removed as described in subclauses 4.6.1 and 4.6.2.2. NOTE 4: If the back-off timer value received along with the S-NSSAI in the rejected NSSAI for the maximum number of UEs reached is zero as specified in subclause 10.5.7.4a of 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [12], the UE does not consider the S-NSSAI as the rejected S-NSSAI. If there is one or more S-NSSAIs in the rejected NSSAI with the rejection cause "S-NSSAI not available due to maximum number of UEs reached", then for each S-NSSAI, the UE shall behave as follows: a) stop the timer T3526 associated with the S-NSSAI, if running; b) start the timer T3526 with: 1) the back-off timer value received along with the S-NSSAI, if back-off timer value is received along with the S-NSSAI that is neither zero nor deactivated; or 2) an implementation specific back-off timer value, if no back-off timer value is received along with the S-NSSAI; and c) remove the S-NSSAI from the rejected NSSAI for the maximum number of UEs reached when the timer T3526 associated with the S-NSSAI expires. If the UE receives the NSAG information IE in the CONFIGURATION UPDATE COMMAND message, the UE shall store the NSAG information as specified in subclause 4.6.2.2. If the UE receives the Alternative NSSAI IE in the CONFIGURATION UPDATE COMMAND message, the UE shall store the alternative NSSAI as specified in subclause 4.6.2.2. If the UE receives the On-demand NSSAI IE in the CONFIGURATION UPDATE COMMAND message, the UE shall store the on-demand NSSAI as specified in subclause 4.6.2.2. If the UE receives a T3447 value IE in the CONFIGURATION UPDATE COMMAND message and has indicated "service gap control supported" in the REGISTRATION REQUEST, then the UE shall replace the stored T3447 value with the received value in the T3447 value IE, and if neither zero nor deactivated use the received T3447 value with the timer T3447 next time it is started. If the received T3447 value is zero or deactivated, then the UE shall stop the timer T3447 if running. If the UE is not in NB-N1 mode, the UE has set the RACS bit to "RACS supported" in the 5GMM capability IE of the REGISTRATION REQUEST message and the CONFIGURATION UPDATE COMMAND message includes: a) a UE radio capability ID deletion indication IE set to "Network-assigned UE radio capability IDs deletion requested", the UE shall delete any network-assigned UE radio capability IDs associated with the RPLMN or RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the selected entry of the "list of subscriber data" or the selected PLMN subscription stored at the UE; or b) a UE radio capability ID IE, the UE shall store the UE radio capability ID as specified in annex C. If the UE is not currently registered for emergency services and the emergency registered bit of the 5GS registration result IE in the CONFIGURATION UPDATE COMMAND message is set to "Registered for emergency services", the UE shall consider itself registered for emergency services and shall locally release all non-emergency PDU sessions, if any. If the UE receives the service-level-AA container IE of the CONFIGURATION UPDATE COMMAND message, the UE passes it to the upper layer. NOTE 5: The service-level-AA container IE can include a service-level-AA payload of type "C2 authorization payload" that includes pairing information for the direct C2 communication, or the security information as specified in TS 33.256[ Security aspects of Uncrewed Aerial Systems (UAS) ] [24B], or both. If the CONFIGURATION UPDATE COMMAND message includes the service-level-AA response in the Service-level-AA container IE with the SLAR field set to "Service level authentication and authorization was not successful or service level authorization is revoked", the UE shall forward the service-level-AA response to the upper layers, so the UUAA authorization data is deleted as specified in 3GPP TS 33.256[ Security aspects of Uncrewed Aerial Systems (UAS) ] [24B]. If the UE receives the List of PLMNs to be used in disaster condition IE in the CONFIGURATION UPDATE COMMAND message and the UE supports MINT, the UE shall delete the "list of PLMN(s) to be used in disaster condition" stored in the ME together with the PLMN ID of the RPLMN, if any, and may store the "list of PLMN(s) to be used in disaster condition" included in the List of PLMNs to be used in disaster condition IE in the ME together with the PLMN ID of the RPLMN. If the UE receives the Disaster roaming wait range IE in the CONFIGURATION UPDATE COMMAND message and the UE supports MINT, the UE shall delete the disaster roaming wait range stored in the ME, if any, and store the disaster roaming wait range included in the Disaster roaming wait range IE in the ME. If the UE receives the Disaster return wait range IE in the CONFIGURATION UPDATE COMMAND message and the UE supports MINT, the UE shall delete the disaster roaming wait range stored in the ME, if any, and store the disaster roaming wait range included in the Disaster roaming wait range IE in the ME. If the UE receives, the Discontinuous coverage maximum time offset IE in the CONFIGURATION UPDATE COMMAND message, the UE shall replace any previously received discontinuous coverage maximum time offset value on the same satellite NG-RAN RAT type and PLMN with the latest received timer value. If the UE receives the Updated PEIPS assistance information IE in the CONFIGURATION UPDATE COMMAND message and the UE supports NR paging subgrouping, the UE shall use the PEIPS assistance information included in the Updated PEIPS assistance information IE. If the UE receives a CONFIGURATION UPDATE COMMAND message with the MPS indicator bit in the Priority indicator IE set to "Access identity 1 valid": - via 3GPP access; or - via non-3GPP access if the UE is registered to the same PLMN or SNPN over 3GPP access and non-3GPP access; the UE shall act as a UE with access identity 1 configured for MPS, as described in subclause 4.5.2, in all NG-RAN of the registered PLMN and its equivalent PLMNs or in the case of SNPN, as described in subclause 4.5.2A, in all NG-RAN of the registered SNPN and its equivalent SNPNs. If the UE receives a CONFIGURATION UPDATE COMMAND message with the MPS indicator bit in the Priority indicator IE set to "Access identity 1 valid": - via non-3GPP access; or - via 3GPP access if the UE is registered to the same PLMN or SNPN over 3GPP access and non-3GPP access; the UE shall act as a UE with access identity 1 configured for MPS, as described in subclause 4.5.2, in non-3GPP access of the registered PLMN and its equivalent PLMNs or in the case of SNPN, as described in subclause 4.5.2A, in non-3GPP access of the registered SNPN and its equivalent SNPNs. The MPS indicator bit in the Priority indicator IE provided in the CONFIGURATION UPDATE COMMAND message is valid: - in all NG-RAN of the registered PLMN and its equivalent PLMNs, or in the case of SNPN in all NG-RAN of the registered SNPN and its equivalent SNPNs, until: - the UE receives a REGISTRATION ACCEPT message with the MPS indicator bit set to "Access identity 1 not valid" or the UE receives a CONFIGURATION UPDATE COMMAND message with the MPS indicator bit of the Priority indicator IE set to "Access identity 1 not valid": - via 3GPP access; or - via non-3GPP access if the UE is registered to the same PLMN or SNPN over 3GPP access and non-3GPP access; or - the UE selects a non-equivalent PLMN (or in the case of SNPN, selects a non-equivalent SNPN); or - in non-3GPP access of the registered PLMN and its equivalent PLMNs, or in the case of SNPN in non-3GPP access of the registered SNPN and its equivalent SNPNs, until: - the UE receives a REGISTRATION ACCEPT message with the MPS indicator bit set to "Access identity 1 not valid" or the UE receives a CONFIGURATION UPDATE COMMAND message with the MPS indicator bit of the Priority indicator IE set to "Access identity 1 not valid": - via non-3GPP access; or - via 3GPP access if the UE is registered to the same PLMN or SNPN over 3GPP access and non-3GPP access; or - the UE selects a non-equivalent PLMN (or in the case of SNPN, selects a non-equivalentSNPN). Access identity 1 is only applicable while the UE is in N1 mode. If the UE receives a CONFIGURATION UPDATE COMMAND message with the MCS indicator bit in the Priority indicator IE set to "Access identity 2 valid": - via 3GPP access; or - via non-3GPP access if the UE is registered to the same PLMN or SNPN over 3GPP access and non-3GPP access; the UE shall act as a UE with access identity 2 configured for MCS, as described in subclause 4.5.2, in all NG-RAN of the registered PLMN and its equivalent PLMNs or in the case of SNPN, as described in subclause 4.5.2A, in all NG-RAN of the registered SNPN and its equivalent SNPNs. If the UE receives a CONFIGURATION UPDATE COMMAND message with the MCS indicator bit in the Priority indicator IE set to "Access identity 2 valid": - via non-3GPP access; or - via 3GPP access if the UE is registered to the same PLMN or SNPN over 3GPP access and non-3GPP access; the UE shall act as a UE with access identity 2 configured for MCS, as described in subclause 4.5.2, in non-3GPP access of the registered PLMN and its equivalent PLMNs or in the case of SNPN, as described in subclause 4.5.2A, in non-3GPP access of the registered SNPN and its equivalent SNPNs. The MCS indicator bit in the Priority indicator IE provided in the CONFIGURATION UPDATE COMMAND message is valid: - in all NG-RAN of the registered PLMN and its equivalent PLMNs, or in the case of SNPN in all NG-RAN of the registered SNPN and its equivalent SNPNs, until: - the UE receives a REGISTRATION ACCEPT message with the MCS indicator bit set to "Access identity 2 not valid" or the UE receives a CONFIGURATION UPDATE COMMAND message with the MCS indicator bit of the Priority indicator IE set to "Access identity 2 not valid": - via 3GPP access; or - via non-3GPP access if the UE is registered to the same PLMN or SNPN over 3GPP access and non-3GPP access; or - the UE selects a non-equivalent PLMN (or in the case of SNPN, selects a non-equivalent SNPN); or - in non-3GPP access of the registered PLMN and its equivalent PLMNs, or in the case of SNPN in non-3GPP access of the registered SNPN and its equivalent SNPNs, until: - the UE receives a REGISTRATION ACCEPT message with the MCS indicator bit set to "Access identity 2 not valid" or the UE receives a CONFIGURATION UPDATE COMMAND message with the MCS indicator bit of the Priority indicator IE set to "Access identity 2 not valid": - via non-3GPP access; or - via 3GPP access if the UE is registered to the same PLMN or SNPN over 3GPP access and non-3GPP access; or - the UE selects a non-equivalent PLMN (or in the case of SNPN, selects a non-equivalentSNPN). Access identity 2 is only applicable while the UE is in N1 mode. If the UE supporting UAS services is not currently registered for UAS services and the CONFIGURATION UPDATE COMMAND message includes the service-level-AA service status indication in the Service-level-AA container IE with the UAS field set to "UAS services enabled", then the UE passes the service-level-AA service status indication to the upper layers. If the UE supporting the reconnection to the network due to RAN timing synchronization status change receives the RAN timing synchronization IE with the RecReq bit set to "Reconnection requested" in the CONFIGURATION UPDATE COMMAND message, the UE shall operate as specified in subclauses 5.3.1.4, 5.5.1.3.2, and 5.6.1.1. If the UE operating as MBSR receives the MBSRAI field of the Feature authorization indication IE in the CONFIGURATION UPDATE COMMAND message, the UE NAS layer informs the lower layers of the status of MBSR authorization. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.4.3 |
5,755 | 5.2.6.22.2 Nnef_AMPolicyAuthorization_Create service operation | Service operation name: Nnef_AMPolicyAuthorization_Create Description: Authorizes the request and triggers an Npcf_AMPolicyAuthorization_Create, potentially translating GPSI to SUPI. Inputs, Required: GPSI. Inputs, Optional: Throughput requirements, service coverage requirements, policy duration, subscribed event(s). The subscribed event includes Event ID as specified in Nnef_AMPolicyAuthorization_Notify service operation, Event Reporting Information defined in Table 4.15.1-1 (only the Event Reporting mode and the immediate reporting flag when applicable), Notification Target Address. Outputs, Required: Success or Failure. Outputs, Optional: Identification of the created application context, the inputs that can be accepted by the PCF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.22.2 |
5,756 | 5.4.1 UE reachability in CM-IDLE 5.4.1.1 General | Reachability management is responsible for detecting whether the UE is reachable and providing UE location (i.e. access node) for the network to reach the UE. This is done by paging UE and UE location tracking. The UE location tracking includes both UE registration area tracking (i.e. UE registration area update) and UE reachability tracking ((i.e. UE periodic registration area update)). Such functionalities can be either located at 5GC (in the case of CM-IDLE state) or NG-RAN (in the case of CM-CONNECTED state). The UE and the AMF negotiate UE reachability characteristics for CM-IDLE state during Registration procedures. Three UE reachability categories are negotiated between UE and AMF for CM-IDLE state: 1. UE reachability allowing Mobile Terminated data while the UE is CM-IDLE state. - The UE location is known by the network on a Tracking Area List granularity - Paging procedures apply to this category. - Mobile originating and mobile terminated data apply in this category for both CM-CONNECTED and CM-IDLE state. 2. Mobile Initiated Connection Only (MICO) mode: - Mobile originated data applies in this category for both CM-CONNECTED and CM-IDLE state. - Mobile terminated data is only supported when the UE is in CM-CONNECTED state. 3. UE unreachability due to Unavailability Period: - Mobile originated data and Mobile terminated data are not transmitted in this category (handling of data by extending buffering may apply). - Paging procedure is not applicable to this category. Whenever a UE in RM-REGISTERED state enters CM-IDLE state, it starts a periodic registration timer according to the periodic registration timer value received from the AMF during a Registration procedure. The AMF allocates a periodic registration timer value to the UE based on local policies, subscription information and information provided by the UE. After the expiry of the periodic registration timer, the UE shall perform a periodic registration. If the UE moves out of network coverage when its periodic registration timer expires, the UE shall perform a Registration procedure when it next returns to the coverage. The AMF runs a Mobile Reachable timer for the UE. The timer is started with a value longer than the UE's periodic registration timer whenever the CM state for the UE in RM-REGISTERED state changes to CM-IDLE. If the AMF receives an elapsed time from RAN when RAN initiate UE context release indicating UE unreachable, the AMF should deduce a Mobile Reachable timer value based on the elapsed time received from RAN and the normal Mobile Reachable timer value. The AMF stops the Mobile Reachable timer, if the UE CM state in the AMF moves to CM-CONNECTED state. If the Mobile Reachable timer expires, the AMF determines that the UE is not reachable. However, the AMF does not know for how long the UE remains not reachable, thus the AMF shall not immediately de-register the UE. Instead, after the expiry of the Mobile Reachable timer, the AMF should clear the PPF and shall start an Implicit De-registration timer, with a relatively large value. The AMF shall stop the Implicit De-registration timer and set the PPF if the AMF moves the UE CM state in the AMF to CM-CONNECTED state. NOTE: If the UE CM state in the AMF is CM-IDLE, then AMF considers the UE always unreachable if the UE is in MICO mode (refer to clause 5.4.1.3). If the UE indicates an Unavailability Period Duration, then AMF shall consider the UE as unreachable and will not trigger the Paging procedure (e.g. clear the PPF) until the UE registers for normal service again (e.g. set the PPF). Once the event that makes the UE unavailable is completed or cancelled in the UE, the UE shall initiate the registration procedure in order to resume normal service. If the PPF is not set, the AMF does not page the UE and shall reject any request for delivering DL signalling or data to this UE. If the Implicit De-registration timer expires before the UE contacts the network, the AMF implicitly de-register the UE. As part of deregistration for a particular access (3GPP or non-3GPP), the AMF shall request the UE's related SMF to release the PDU Sessions established on that access. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.1 |
5,757 | 5.2.18.3.2 Nucmf_UECapabilityManagement_Assign service operation | Service or service operation name: Nucmf_UECapabilityManagement_Assign Description: The NF consumer sends to the UCMF: - the UE Radio Access Capability (and its Coding Format); or - the UE Radio Access Capability and UE Radio Capability for Paging in both TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [16] and TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12] coding formats; and obtains a PLMN-assigned UE Radio Capability ID in return. Inputs, Required: UE Radio Access Capability(s), UE Radio Capability for Paging(s), Coding format(s), IMEI/TAC. Inputs, Optional: One or more UE Radio Capability for Paging. Outputs, Required: UE Radio Capability ID. Outputs, Optional: None. The AMF does not send NB-IoT Radio Access Capability to the UCMF. The Coding format indicates the format of the UE Radio Access Capability as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [16] or TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.18.3.2 |
5,758 | 8.10.1.1.5B Single-layer Spatial Multiplexing (With Enhanced DMRS table configured) | For single-layer transmission on antenna port 7, 8, 11 or 13 upon detection of a PDCCH with DCI format 2C, the requirement is specified in Table 8.10.1.1.5B-2, with the addition of the parameters in Table 8.10.1.1.5B-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of the test is to verify rank-1 performance on antenna port 11 with a simultaneous transmission on the antenna port 7, 8 or 13 with DMRS enhancement table and 4 orthogonal DMRS ports (dmrs-Enhancements-r13 UE-EUTRA-Capability [7]). Table 8.10.1.1.5B-1: Test Parameters for Testing CDM-multiplexed DM RS (single layer) with interfering simultaneous transmission (FRC) with multiple CSI-RS configurations with Enhanced DMRS table Table 8.10.1.1.5B-2: Minimum performance for CDM-multiplexed DM RS with interfering simultaneous transmission (FRC) with multiple CSI-RS configurations with Enhanced DMRS table | 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.10.1.1.5B |
5,759 | 17.6.4 STA Command | The STA command, defined in IETF RFC 6733 (DIAMETER BASE) [111], is indicated by the Command-Code field set to 275 and the ‘R’ bit cleared in the Command Flags field, is sent in response to an STR command (e.g. De-registration procedure). The relevant AVPs that are of use for the Gmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gmb purposes and should be ignored by the receiver or processed according to the relevant specifications. Message Format: <ST-Answer> ::= < Diameter Header: 275, PXY > < Session-Id > { Result-Code } { Origin-Host } { Origin-Realm } * [ Class ] [ Error-Message ] [ Error-Reporting-Host ] [ Failed-AVP ] [ Origin-State-Id ] * [ Redirect-Host ] [ Redirect-Host-Usage ] [ Redirect-Max-Cache-Time ] * [ Proxy-Info ] | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 17.6.4 |
5,760 | 8.4.2.1 EN-DC | This clause gives the SgNB release procedure in EN-DC given that the en-gNB consists of a gNB-CU and gNB-DU(s). MN initiated SN Release Figure 8.4.2.1-1 SgNB release procedure in EN-DC (MN initiated) 1~8: refer to TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [12]. NOTE: The timing of sending the Step 2 SGNB RELEASE REQUEST ACKNOWLEDGE message is an example, it may be sent e.g. after step a1 or after a2 and it is up to implementation. a1. After receiving SGNB RELEASE REQUEST message from MeNB, gNB-CU sends the UE CONTEXT MODIFICATION REQUEST message to gNB-DU to stop the data transmission for the UE. It is up to gNB-DU implementation when to stop the UE scheduling. a2. gNB-DU responds to gNB-CU with UE CONTEXT MODIFICATION RESPONSE message. a3. After receiving the UE CONTEXT RELEASE message from MeNB, the gNB-CU sends the UE CONTEXT RELEASE COMMAND message to the gNB-DU to release the UE context. a4. The gNB-DU responds to the gNB-CU with the UE CONTEXT RELEASE COMPLETE message. SN initiated SN Release Figure 8.4.2.1-2 SgNB release procedure in EN-DC (SN initiated) 1~8: refer to TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [12]. a1. gNB-CU sends the UE CONTEXT MODIFICATION REQUEST message to gNB-DU to stop the data transmission for the UE. It is up to gNB-DU implementation when to stop the UE scheduling. This step may occur before step 1. a2. gNB-DU responds to gNB-CU with UE CONTEXT MODIFICATION RESPONSE message. a3. After receiving the UE CONTEXT RELEASE message from MeNB, the gNB-CU sends the UE CONTEXT RELEASE COMMAND message to the gNB-DU to release the UE context. a4. The gNB-DU responds to the gNB-CU with the UE CONTEXT RELEASE COMPLETE message. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.4.2.1 |
5,761 | 6.3.10 Handling of 3GPP PS data off | A UE, which supports 3GPP PS data off (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]), can be configured with up to two lists of 3GPP PS data off exempt services as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or in the EF3GPPPSDATAOFF USIM file as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]: - a list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN (if the EHPLMN list is present); and - a list of 3GPP PS data off exempt services to be used in the VPLMN. If only the list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN (if the EHPLMN list is present) is configured at the UE, this list shall be also used in the VPLMN. If the UE supports 3GPP PS data off, the UE shall provide the 3GPP PS data off UE status in the Protocol configuration options IE during attach, UE-requested PDN connectivity, and UE-requested bearer resource modification procedure (see clause 5.5.1, 6.5.1, and 6.5.4). NOTE 1: The sending of the 3GPP PS data off UE status to the network happens also when the user activates or deactivates 3GPP PS data off while connected via WLAN access only, and then handover to 3GPP access occur. The network informs the UE about the support of 3GPP PS data off during the activation of the default bearer of a PDN connection (see clause 6.4.1). If 3GPP PS data off support is not indicated in the Protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, the UE shall not indicate any change of 3GPP PS data off UE status for the PDN connection established by the default EPS bearer context activation procedure; otherwise the UE shall indicate change of the 3GPP PS data off UE status for the PDN connection by using the UE-requested bearer resource modification procedure as specified in clause 6.5.4. If the network does not provide indication of support of 3GPP PS data off during default EPS bearer context activation procedure of the PDN connection, the UE behaviour for non-exempt service requests from the network is implementation dependent. When the 3GPP PS data off UE status is "activated": a) the UE does not send uplink IP packets except: - for those services indicated in the list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN (if the EHPLMN list is present) as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] when the UE is in its HPLMN or EHPLMN (if the EHPLMN list is present); - for those services indicated in the list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN (if the EHPLMN list is present) when the UE is in the VPLMN, if only the list of 3GPP PS data off exempt services to be used in the HPLMN or EHPLMN (if the EHPLMN list is present) is configured to the UE as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A]; - for those services indicated in the list of 3GPP PS data off exempt services to be used in the VPLMN when the UE is in the VPLMN, if the list of 3GPP PS data off exempt services to be used in the VPLMN is configured to the UE as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A]; - for those services indicated in the EF3GPPPSDATAOFF USIM file as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]; - any uplink traffic due to procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [13D]; and - any uplink traffic due to procedures specified in 3GPP TS 24.623[ Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating Supplementary Services ] [50]; and b) the UE does not send uplink non-IP or Ethernet user data packets. Otherwise the UE sends uplink user data packets without restriction. NOTE 2: If the UE supports 3GPP PS data off, uplink IP packets are filtered as specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [13D] in L.3.1.5. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.3.10 |
5,762 | 13.2.3.6 Precedence of policies in the SEPP | This clause specifies the order of precedence of data-type encryption policies and modification policies available in a SEPP. In increasing order of precedence, the following policies apply for a message to be sent on N32: 1. The set of default rules specified in the present specification: - For the data-type encryption policy, the rules on data-types that are mandatory to be encrypted according to clause 5.9.3.3. - For the modification policy, the basic validation rules defined in clause 13.2.3.4. 2. Manually configured policies: - For the data-type encryption policy: rules according to clause 13.2.3.2, on a per roaming partner basis. - For the modification policy: rules according to clause 13.2.3.4, per roaming partner and per IPX provider that is used for the specific roaming partner. NOTE 1: It is assumed that operators agree both data-type encryption and modification policy in advance, for example as part of their bilateral roaming agreement. The protection policies exchanged via N32-c during the initial connection establishment only serve the purpose of detecting possible misconfigurations. NOTE 2: It is assumed that the default rules and manually configured policies do not overlap or contradict each other. The manually configured policies are used to extend the protection by the default rules in the present document and are applied on top of them. When a SEPP receives a data-type encryption or modification policy on N32-c as specified in clause 13.2.2.2, it shall compare it to the one that has been manually configured for this specific roaming partner and IPX provider. If a mismatch occurs for one of the two policies, the SEPP shall perform one of the following actions, according to operator policy: - Send the error message as specified in TS 29.573[ 5G System; Public Land Mobile Network (PLMN) Interconnection; Stage 3 ] [73], clause 6.1.4.3.2, to the peer SEPP. - Create a local warning. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.2.3.6 |
5,763 | 16a.4.7 ASR Command | The Abort-Session-Request (ASR) command, defined in IETF RFC 6733 (Diameter Base) [111], is indicated by the Command-Code set to 274 and the message flags’ ‘R’ bit set, is sent by the Diameter server to the GGSN to request that the PDP Context identified by the 3GPP-NSAPI AVP is to be terminated. The absence of the 3GPP-NSAPI AVP will indicate to the GGSN that all the PDP contexts for this particular user and sharing the same user session need to be deleted. Similarly, for P-GW, the ASR command is sent by the Diamater server to the P-GW to request that the EPS bearer identified by the 3GPP-NSAPI AVP is to be terminated. In the absence of the 3GPP-NSAPI AVP or if the value of 3GPP-NSAPI AVP points to the default EPS bearer, the P-GW shall terminate the IP-CAN session associated with the same user session. The relevant AVPs that are of use for the Gi/Sgi interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gi/Sgi purposes and should be ignored by the receiver or processed according to the relevant specifications. The bold marked AVPs in the message format indicate optional AVPs for Gi/Sgi, or modified existing AVPs. Message Format: <ASR> ::= < Diameter Header: 274, REQ, PXY > < Session-Id > { Origin-Host } { Origin-Realm } { Destination-Realm } { Destination-Host } { Auth-Application-Id } [ Origin-State-Id ] * [ Proxy-Info ] [ 3GPP-NSAPI ] * [ Route-Record ] * [ AVP ] | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 16a.4.7 |
5,764 | A.17 SoR-MAC-IAUSF generation function | When deriving a SoR-MAC-IAUSF from KAUSF, the following parameters shall be used to form the input S to the KDF. - FC = 0x77, - P0 = SoR header, - L0 = length of SoR header, - P1 = CounterSoR, - L1 = length of CounterSoR, - P2 = octets included in SoR transparent container (in clause 9.11.3.51 of TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35]) beyond (and not including) octet 22, - L2 = length of list data included in P2 The input key KEY shall be KAUSF. The selection of parameters included in P2 shall be the same as the selection of input to the Nausf_SoRProtection service operation. If none of these parameters are included in Nausf_SoRProtection service operation, P2 and L2 are not included for SoR-MAC-IAUSF generation. The SOR header is either received from the requester NF (e.g UDM), or constructed by the AUSF, as described in clause 9.11.3.51 of TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35], based on the information received from the requester NF (e.g. UDM), i.e. ACK Indication and List of preferred PLMN/access technology combinations or secured packet (if provided). The SoR-MAC-IAUSF is identified with the 128 least significant bits of the output of the KDF. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | A.17 |
5,765 | 4.7.1.3 P-TMSI signature | The network may assign a P-TMSI signature to an MS in an attach, routing area update, or P-TMSI reallocation procedure. Only in combination with a valid P-TMSI, this P-TMSI signature is used by the MS for authentication and identification purposes in the subsequent attach, routing area update or detach procedure. If the MS has no valid P-TMSI it shall not use the P-TMSI signature in the subsequent attach, routing area update or detach procedure. Upon successful completion of the subsequent attach or routing area update procedure, the used P-TMSI signature shall be deleted. Upon completion of an MS initiated detach procedure, the used P-TMSI signature shall be deleted. Upon completion of a network initiated detach procedure the P-TMSI signature shall be kept, unless explicitly specified otherwise in subclause 4.7.4.2.2. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.1.3 |
5,766 | – SL-Thres-RSRP-List | IE SL-Thres-RSRP-List indicates a threshold used for sensing based UE autonomous resource selection (see TS 38.215[ NR; Physical layer measurements ] [9]). A resource is excluded if it is indicated or reserved by a decoded SCI and PSSCH/PSCCH RSRP in the associated data resource is above the threshold defined by IE SL-Thres-RSRP-List. A NR sidelink resource is excluded if the corresponding PSFCH transmission occasions overlap with resources indicated or reserved by the decoded EUTRA SCI in time domain and EUTRA PSSCH RSRP in the associated data resource is above the threshold defined by IE sl-NRPSFCH-EUTRA-ThresRSRP-List. A NR sidelink resource is excluded if it is indicated or reserved by the decoded EUTRA SCI and EUTRA PSSCH RSRP in the associated data resource is above the threshold defined by IE sl-NRPSSCH-EUTRA-ThresRSRP-List. Value 0 corresponds to minus infinity dBm, value 1 corresponds to -128dBm, value 2 corresponds to -126dBm, value n corresponds to (-128 + (n-1)*2) dBm and so on, value 66 corresponds to infinity dBm. SL-Thres-RSRP-List information element -- ASN1START -- TAG-SL-THRES-RSRP-LIST-START SL-Thres-RSRP-List-r16 ::= SEQUENCE (SIZE (64)) OF SL-Thres-RSRP-r16 SL-Thres-RSRP-r16 ::= INTEGER (0..66) -- TAG-SL-THRES-RSRP-LIST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,767 | 9.9.3.50 HashMME | The purpose of the HashMME information element is to transfer a 64-bit hash value to the UE so the UE can check the MME calculated value against the value locally calculated by the UE to determine whether the ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message sent by the UE has been modified. The HashMME information element is coded as shown in figure 9.9.3.50.1 and table 9.9.3.50.1. The HashMME is a type 4 information element with a length of 10 octets. Figure 9.9.3.50.1: HashMME information element Table 9.9.3.50.1: HashMME 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.50 |
5,768 | 5.4.2.6 Abnormal cases in the UE | The following abnormal cases can be identified: a) Transmission failure of SECURITY MODE COMPLETE message or SECURITY MODE REJECT message indication from lower layers (if the security mode control procedure is triggered by a registration procedure). The UE shall abort the security mode control procedure and re-initiate the registration procedure. b) Transmission failure of SECURITY MODE COMPLETE message or SECURITY MODE REJECT message indication with change in the current TAI (if the security mode control procedure is triggered by a service request procedure). If the current TAI is not in the TAI list, the security mode control procedure shall be aborted and a registration procedure shall be initiated. If the current TAI is still part of the TAI list, the security mode control procedure shall be aborted and it is up to the UE implementation how to re-run the ongoing procedure that triggered the security mode control procedure. c) Transmission failure of SECURITY MODE COMPLETE message or SECURITY MODE REJECT message indication without change in the current TAI (if the security mode control procedure is triggered by a service request procedure). The security mode control procedure shall be aborted and it is up to the UE implementation how to re-run the ongoing procedure that triggered the security mode control 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 | 5.4.2.6 |
5,769 | 6.3.4.2.2 SRS time mask | In the case a single SRS transmission, the ON power is defined as the mean power over the symbol duration excluding any transient period; Figure 6.3.4.2.2-1 and Figure 6.3.4.2.2-1A. In the case a dual SRS transmission, the ON power is defined as the mean power for each symbol duration excluding any transient period. Figure 6.3.4.2.2-2 There are no additional requirements on UE transmit power beyond that which is required in subclause 6.2.2 and subclause 6.6.2.3 Figure 6.3.4.2.2-1: Single SRS time mask for Frame Structure Type 1 and Frame Structure Type 2 For Frame Structure Type 3 and single SRS transmission, the SRS time mask is specified in 6.3.4.2-2A; the OFF power requirement applies [5] s after the end of the SRS symbol. Figure 6.3.4.2.2-1A: Single SRS time mask for Frame Structure Type 3 Figure .2.2-2: Dual SRS time mask for the case of UpPTS transmissions For SRS transmission mapped to two or more OFDM symbols the ON power is defined as the mean power for each symbol duration excluding any transient period. For consecutive SRS transmissions without power change, Figure .2.2-3 applies. Figure .2.2-3: Consecutive SRS time mask for the case when no power change is required When power change between consecutive SRS transmissions is required, then Figure .2.2-4 and Figure .2.2-5 apply. Figure .2.2-4: Consecutive SRS time mask for the case when power change is required Figure .2.2-5: Time mask for SRS antenna switching The above transient period applies to all the transmit CCs in CA with the CC sounding SRS. UE RF requirements do not apply during this transient period. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.3.4.2.2 |
5,770 | 5.3.13.3 Actions related to transmission of RRCResumeRequest or RRCResumeRequest1 message | The UE shall set the contents of RRCResumeRequest or RRCResumeRequest1 message as follows: 1> if field useFullResumeID is signalled in SIB1: 2> select RRCResumeRequest1 as the message to use; 2> set the resumeIdentity to the stored fullI-RNTI value; 1> else: 2> select RRCResumeRequest as the message to use; 2> set the resumeIdentity to the stored shortI-RNTI value; 1> restore the RRC configuration, RoHC state, the EHC context(s), the UDC state, the stored QoS flow to DRB mapping rules and the KgNB and KRRCint keys from the stored UE Inactive AS context except for the following: - masterCellGroup; - mrdc-SecondaryCellGroup, if stored; and - pdcp-Config; 1> set the resumeMAC-I to the 16 least significant bits of the MAC-I calculated: 2> over the ASN.1 encoded as per clause 8 (i.e., a multiple of 8 bits) VarResumeMAC-Input; 2> with the KRRCint key in the UE Inactive AS Context and the previously configured integrity protection algorithm; and 2> with all input bits for COUNT, BEARER and DIRECTION set to binary ones; 1> derive the KgNB key based on the current KgNB key or the NH, using the nextHopChainingCount value received in the previous RRCRelease message and stored in the UE Inactive AS Context, as specified in TS 33.501[ Security architecture and procedures for 5G System ] [11]; 1> derive the KRRCenc key, the KRRCint key, the KUPint key and the KUPenc key; 1> configure lower layers to apply integrity protection for all radio bearers except SRB0 and MRBs using the configured algorithm and the KRRCint key and KUPint key derived in this clause immediately, i.e., integrity protection shall be applied to all subsequent messages received and sent by the UE; NOTE 1: Only DRBs with previously configured UP integrity protection shall resume integrity protection. 1> configure lower layers to apply ciphering for all radio bearers except SRB0 and MRBs and to apply the configured ciphering algorithm, the KRRCenc key and the KUPenc key derived in this clause, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE; 1> re-establish PDCP entities for SRB1; 1> resume SRB1; 1> if the resume procedure is initiated for SDT: 2> for each radio bearer that is configured for SDT and for SRB1: 3> restore the RLC-BearerConfig associated with the RLC bearers of masterCellGroup and pdcp-Config from the UE Inactive AS context; 3> if the radio bearer is a DRB configured with Ethernet Header Compression: 4> indicate to lower layer that ethernetHeaderCompression is not configured; 3> if the radio bearer is a DRB configured with UDC: 4> indicate to lower layer that uplinkDataCompression is not configured; 3> if the radio bearer is a DRB configured with ROHC function: 4> if sdt-DRB-ContinueROHC is set to cell and the resume procedure is initiated in a cell that is the same as the PCell in which the UE received the previous RRCRelease message; or 4> if sdt-DRB-ContinueROHC is set to rna and the resume procedure is initiated in a cell belonging to the same RNA as the PCell in which the UE received the previous RRCRelease message: 5> indicate to lower layer that drb-continueROHC is configured; 4> else: 5> indicate to lower layer that drb-continueROHC is not configured; 3> re-establish PDCP entity for the radio bearer that is configured for SDT without triggering PDCP status report; 2> resume all the radio bearers that are configured for SDT; 1> submit the selected message RRCResumeRequest or RRCResumeRequest1 for transmission to lower layers. NOTE 2: Only DRBs with previously configured UP ciphering shall resume ciphering. NOTE 2a: Before the lower layers first transmit the RRCResumeRequest or RRCResumeRequest1, the UE may initiate a new resume procedure if other conditions for initiation of the resume procedure as specified in 5.3.13.2 are satisfied. If lower layers indicate an integrity check failure while T319 is running or SDT procedure is ongoing, perform actions specified in 5.3.13.5. If the UE is an (e)RedCap UE and the (e)RedCap-specific initial downlink BWP is not associated with CD-SSB, the UE may continue cell re-selection related measurements as well as cell re-selection evaluation, otherwise the UE shall continue cell re-selection related measurements as well as cell re-selection evaluation. If the conditions for cell re-selection are fulfilled, the UE shall perform cell re-selection as specified in 5.3.13.6. NOTE 3: For L2 U2N Remote UE in RRC_INACTIVE, the cell (re)selection procedure as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20] and relay (re)selection procedure as specified in 5.8.15.3 are performed independently and it is up to UE implementation to select either a cell or a L2 U2N Relay UE. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.13.3 |
5,771 | 28.8 Generic Public Subscription Identifier (GPSI) | The Generic Public Subscription Identifier (GPSI) is defined in clause 5.9.8 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [119]. The GPSI is defined as: - a GPSI type: in this release of the specification, it may indicate an MSISDN or an External Identifier; and - dependent on the value of the GPSI type: - an MSISDN as defined in clause 3.3; or - an External Identifier as defined in clause 19.7.2. NOTE: Depending on the protocol used to convey the GPSI, the GPSI type can take different formats. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.8 |
5,772 | Bearer Resource Command | A Bearer Resource Command message shall be sent from a MME to a SGW and forwarded to PGW as a part of the UE requested bearer resource allocation procedure or UE requested bearer resource modification procedure (which is used also for a dedicated bearer deactivation or dedicated bearer activation), as specified by 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [23]. The message shall also be sent on the S4 interface by a SGSN to a SGW and on the S5/S8 interface by a SGW to a PGW as part of the MS initiated PDP Context modification procedure, or secondary PDP context activation procedure. The message shall also be sent on the S11/S4 interface by an MME/S4-SGSN to a SGW and on the S5/S8 or S2a/S2b interface by a SGW or a TWAN/ePDG to a PGW as part of the UE-initiated IP flow mobility procedure and the UE requested IP flow mapping procedure, as specified by 3GPP TS 23.161[ Network-Based IP Flow Mobility (NBIFOM); Stage 2 ] [71]. Table 7.2.5-1 specifies the presence of the IEs in the message. Table -1: Information Elements in a Bearer Resource Command NOTE: Depending on the protocol type on the S5/S8 interface, the SGW or the PGW will determine if the UE is requesting an Allocation/Modification operation of bearer resources for a traffic flow aggregate based on the TFT operation code and the packet filter ID value in the Traffic Aggregate (TAD) IE and/or the presence of the EPS Bearer ID IE. Table 7.2.5-2: Overload Control Information within Bearer Resource Command | 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 | Bearer |
5,773 | 6.1.3.16 AUL confirmation MAC Control Element | The AUL confirmation MAC control element of one octet is identified by a MAC PDU subheader with LCID as specified in table 6.2.1-2. It has a fixed size and consists of a single octet containing seven C-fields and one R-field. The AUL confirmation MAC control element with one octet is defined as follows (figure 6.1.3.16-1). The AUL confirmation MAC control element of four octets is identified by a MAC PDU subheader with LCID as specified in table 6.2.1-2. It has a fixed size and consists of a four octets containing 31 C-fields and one R-field. The AUL confirmation MAC control element of four octets is defined as follows (figure 6.1.3.16-2). For the case with no serving cell with a ServCellIndex (TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]) larger than 7, AUL confirmation MAC control element of one octet is applied, otherwise AUL confirmation MAC control element of four octets is applied. - Ci: if there is an SCell configured with SCellIndex i as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8], this field indicates whether a PDCCH containing AUL activation or AUL release of the autonomous uplink configuration in the SCell with SCellIndex i has been received, else the MAC entity shall ignore the Ci field. The Ci field is set to "1" to indicate that a PDCCH containing AUL activation or AUL release of the autonomous uplink configuration in the SCell with SCellIndex i has been received in the TTI in which AUL confirmation has been triggered. The Ci field is set to "0" to indicate that a PDCCH containing AUL activation or AUL release of the autonomous uplink configuration in the SCell with SCellIndex i has not been received in the TTI in which AUL confirmation has been triggered; - R: Reserved bit, set to "0". Figure 6.1.3.16-1: AUL confirmation MAC Control Element of one octet Figure 6.1.3.16-2: AUL confirmation MAC Control Element of four octets | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.1.3.16 |
5,774 | – MeasurementReport | The MeasurementReport message is used for the indication of measurement results. Signalling radio bearer: SRB1, SRB3 RLC-SAP: AM Logical channel: DCCH Direction: UE to Network MeasurementReport message -- ASN1START -- TAG-MEASUREMENTREPORT-START MeasurementReport ::= SEQUENCE { criticalExtensions CHOICE { measurementReport MeasurementReport-IEs, criticalExtensionsFuture SEQUENCE {} } } MeasurementReport-IEs ::= SEQUENCE { measResults MeasResults, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } -- TAG-MEASUREMENTREPORT-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,775 | 4.15.4.4 Internal Event Exposure Subscription/Unsubscription via UDM | This clause describes an indirect method of event exposure subscription in AMF and SMF via UDM for a UE or group of UEs. This can be used after the removal of UE context in the AMF including event exposure subscriptions, or the creation of new UE context in AMF or SMF. In this case, the UDM is responsible for (re)creating event exposure subscriptions in AMF and SMF. Figure 4.15.4.4-1: Internal Event exposure subscription/unsubscription in AMF or SMF via UDM 1. A consumer of event exposure for events detected in AMF or SMF (e.g. NWDAF) sends an Nudm_EventExposure Subscribe/Unsubscribe request to the UDM for a UE or group of UEs, including the subscription details (Event ID, Event filters, etc.). 2. UDM examines the event type and subscription details to determine whether one or more events are to be detected by the AMF. In this case, for those applicable events that are detected by the AMF, if an AMF is registered in UDM for the UE (or for a UE that is member of the group of UEs), UDM creates an Namf_EventExposure Subscribe/Unsubscribe request and sends it to the AMF of the UE, including the subscription details. 3. AMF answers with an Namf_EventExposure Subscribe/Unsubscribe response. 4. UDM examines the event type and subscription details to determine whether one or more events are to be detected by the SMF. In this case, for those applicable events that are detected by the SMF, if one or more SMFs are registered in UDM for the UE (or for a UE that is member of the group of UEs), UDM creates an Nsmf_EventExposure Subscribe/Unsubscribe request and sends it to each applicable SMF of the UE, including the subscription details. 5. SMF answers with an Nsmf_EventExposure Subscribe/Unsubscribe response. 6. UDM sends an Nudm_EventExposure Subscribe/Unsubscribe response to the consumer of event exposure. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.4.4 |
5,776 | 9.1.3 Handling of simultaneous sidelink and uplink/downlink transmissions | For a given frequency, on an uplink subframe included in discTxGapConfig [9], a UE shall not transmit an uplink transmission that is not a PRACH transmission and that is partly or completely overlapping in time with a PSDCH transmission or a SLSS transmission for PSDCH by the same UE. Else, for a given carrier frequency and sidelink transmission mode 1 or 2 or sidelink discovery, a UE shall not transmit a sidelink signal or channel overlapping partly or completely in time with an uplink transmission from the same UE. For a given carrier frequency, no PSDCH, PSCCH, or PSSCH transmission shall occur from a UE in a sidelink subframe configured for synchronization purposes by the higher-layer parameters - syncOffsetIndicator1 or syncOffsetIndicator2 in [9] if the UE has no serving cell fulfilling the S criterion according to [10, clause 5.2.3.2], or - syncOffsetIndicator in commSyncConfig or discSyncConfig which includes txParameters in [9] if the UE has a serving cell fulfilling the S criterion according to [10, clause 5.2.3.2]. The UE may assume the same configuration in commSyncConfig and discSyncConfig. For a given carrier frequency, with the exception of PSSCH transmissions with transmission mode 1 and same sidelink cyclic prefix as PUSCH, no sidelink transmissions shall occur in sidelink subframe from a UE if uplink SRS is transmitted from the same UE in uplink subframe . A UE with limited transmission capabilities, on an uplink subframe included in discTxGapConfig [9], shall first prioritize a PSDCH transmission or a SLSS transmission for PSDCH over an uplink transmission that is not a PRACH transmission. Else, a UE with limited transmission capabilities shall at a given time first prioritize uplink transmissions, followed by sidelink transmission mode 1 or 2 or sidelink discovery. A UE with limited transmission capabilities shall at a given time prioritize sidelink communication transmissions (PSSS, SSSS, PSBCH, PSSCH, PSCCH) over sidelink discovery transmissions (PSDCH). A UE with limited reception capabilities, on a downlink subframe included in discRxGapConfig [9], shall first prioritize reception of PSDCH or 11reception of SLSS for PSDCH over downlink reception. Else, a UE with limited reception capabilities shall at a given time first prioritize downlink reception over sidelink reception. A UE with limited reception capabilities shall at a given time first prioritize sidelink communication reception, sidelink discovery reception on carriers configured by the eNodeB, and last sidelink discovery reception on carriers not configured by the eNodeB. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.1.3 |
5,777 | 6.4.2 Dedicated EPS bearer context activation procedure 6.4.2.1 General | The purpose of the dedicated EPS bearer context activation procedure is to establish an EPS bearer context with specific QoS and TFT between the UE and the EPC. The network may initiate the dedicated EPS bearer context activation procedure to enable transport of a UE policy container with the length of two octets from the network to the UE and a related UE policy container with the length of two octets from the UE to the network. The UE policy containers with the length of two octets enable transfer of messages of the network-requested UE policy management procedure as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] annex D. In WB-S1 mode, the dedicated EPS bearer context activation procedure is initiated by the network, but may be requested by the UE by means of the UE requested bearer resource allocation procedure (see clause 6.5.3) or the UE requested bearer resource modification procedure (see clause 6.5.4). The dedicated bearer context activation procedure can be part of the attach procedure or be initiated together with the default EPS bearer context activation procedure when the UE initiated stand-alone PDN connectivity procedure. If the attach procedure or the default EPS bearer context activation procedure fails, the UE shall consider that the dedicated bearer activation has implicitly failed. The network may initiate the dedicated EPS bearer context activation procedure together with the completion of the service request procedure. In NB-S1 mode, the dedicated EPS bearer contexts activation procedure is not used. Upon an inter-system mobility from WB-S1 mode to NB-S1 mode in EMM-IDLE mode, if the UE has at least one dedicated EPS bearer context in ESM state BEARER CONTEXT ACTIVE, the UE shall locally deactivate any such dedicated EPS bearer context and shall include the EPS bearer context status IE in TRACKING AREA UPDATE REQUEST message. Upon an inter-system change from WB-N1 mode to NB-S1 mode in EMM-IDLE mode for the UE operating in single-registration mode, the UE shall set each mapped dedicated EPS bearer context, if any, to ESM state BEARER CONTEXT INACTIVE and shall then include the EPS bearer context status IE in the TRACKING AREA UPDATE REQUEST message. NOTE: 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74] clause 9.3 specifies that a packet filter applicable for the downlink direction is not mandatory in a TFT. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.4.2 |
5,778 | – VarMeasConfig | The UE variable VarMeasConfig includes the accumulated configuration of the measurements to be performed by the UE, covering intra-frequency, inter-frequency and inter-RAT mobility related measurements. VarMeasConfig UE variable -- ASN1START -- TAG-VARMEASCONFIG-START VarMeasConfig ::= SEQUENCE { -- Measurement identities measIdList MeasIdToAddModList OPTIONAL, -- Measurement objects measObjectList MeasObjectToAddModList OPTIONAL, -- Reporting configurations reportConfigList ReportConfigToAddModList OPTIONAL, -- Other parameters quantityConfig QuantityConfig OPTIONAL, s-MeasureConfig CHOICE { ssb-RSRP RSRP-Range, csi-RSRP RSRP-Range } OPTIONAL } -- TAG-VARMEASCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,779 | 16a.5 Gi/Sgi specific AVPs | The following table lists the Gi/Sgi specific Diameter AVPs. The Vendor-Id header of all Gi/Sgi specific AVPs defined in the present specification shall be set to 3GPP (10415). Table 9a: Gi/Sgi specific AVPs The information represented by some of the Sgi AVPs may not be available to the P-GW depending on the UE’s radio access and the S5/S8 protocol type (GTP or PMIP). For example, the P-GW will be aware of the User Location Info (e.g. TAI) if the user is in LTE access and GTP based S5/S8 is used. However, such information is not passed to the P-GW when PMIP based S5/S8 is utilised. In such scenarios, if an Sgi specific AVP is configured in the P-GW to be transferred to the Diameter AAA server, but the information in the P-GW is not up to date or not available; the P-GW shall not send the corresponding AVP, unless otherwise stated in the AVP definitions in subclause 16.4.7.2. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 16a.5 |
5,780 | 5.2.6.17.2 Nnef_UCMFProvisioning_Create operation | Service operation name: Nnef_UCMFProvisioning_Create Description: The consumer creates a UCMF dictionary entry (or more entries) for a Manufacturer-assigned UE Radio Capability ID via the NEF. For each UE Radio Capability ID the following inputs are provided: a) a UE radio access capability set with respective Coding format or the UE radio access capability set in both TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [16] and TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12] coding formats and each RATs' UE Radio Capability for Paging; and b) the related UE model(s) IMEI/TAC value(s) the UE radio capability ID applies to. Inputs, Required: (list of) [UE Radio Capability ID, set(s) of UE Radio Access Capability set and UE Radio Capability for Paging and respective Coding format(s), (List of) IMEI/TAC value(s)]. Inputs, Optional: None. Outputs, Required: None. Outputs, Optional: None. The Coding format(s) indicates the format of the respective UE radio access capabilities as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [16] or TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.17.2 |
5,781 | 4.7.13.4 Service request procedure not accepted by the network | If the Service request cannot be accepted, the network returns a SERVICE REJECT message to the mobile station. Based on local policies or configurations in the network, if the network determines to change the periodic routing area update timer (T3312), or if the network determines to change the PSM usage or the value of the timer T3324 in the MS for which PSM is allowed by the network, the network may return a SERVICE REJECT with the cause #10 "implicitly detached" to the MS. If the service request for mobile originated services is rejected due to general NAS level mobility management congestion control, the network shall set the GMM cause value to #22 "congestion" and assign a back-off timer T3346. An MS that receives a SERVICE REJECT message containing a reject cause other than GMM cause value #25 or the message is integrity protected, shall reset the service request attempt counter, shall stop the timer T3317. If the SERVICE REJECT message containing GMM cause value #25 was received without integrity protection, then the MS shall discard the message. The MS shall then take different actions depending on the received reject cause value: # 3 (Illegal MS); or # 6 (Illegal ME); - The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2), shall delete the list of equivalent PLMNs and enter the state GMM-DEREGISTERED.NO-IMSI. Furthermore, it shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number and shall consider the SIM/USIM as invalid for GPRS services until switching off or the SIM/USIM is removed. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. - A GPRS MS operating in MS operation mode A or B shall in addition set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall abort the RR connection, unless an emergency call is ongoing. The SIM/USIM shall be considered as invalid also for non-GPRS services until switching off or the SIM/USIM is removed or the timer T3245 expires as described in subclause 4.1.1.6. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the service request procedure is rejected with the EMM cause with the same value. # 7 (GPRS services not allowed); - The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2.9) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number. The SIM/USIM shall be considered as invalid for GPRS services until switching off or the SIM/USIM is removed. The new state is GMM-DEREGISTERED. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. A GPRS MS operating in MS operation mode A or B which is already IMSI attached for CS services is still IMSI attached for CS services in the network. A GPRS MS operating in MS operation mode A or B in network operation mode I shall then proceed with the appropriate MM specific procedure. NOTE 1: Optionally the MS starts the timer T3340 as described in subclause 4.7.1.9. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the service request procedure is rejected with the EMM cause with the same value. # 8 (GPRS services and non-GPRS services not allowed); The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause .2) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number. The new GMM state is GMM-DEREGISTERED.NO-IMSI. The MS shall set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number. The MS shall delete the list of equivalent PLMNs. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall abort the RR connection, unless an emergency call is ongoing. The SIM/USIM shall be considered as invalid for GPRS and non-GPRS services until switching off or the SIM/USIM is removed. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. NOTE 2: Optionally the MS starts the timer T3340 as described in subclause 4.7.1.9. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the service request procedure is rejected with the EMM cause with the same value. # 9 (MS identity cannot be derived by the network); - The MS shall set the GPRS update status to GU2 NOT UPDATED (and shall store it according to subclause 4.1.3.2), enter the state GMM-DEREGISTERED.NORMAL-SERVICE, and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number. If the rejected request was not for initiating a PDN connection for emergency bearer services, the MS may subsequently, automatically initiate the GPRS attach procedure. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the service request procedure is rejected with the EMM cause with the same value. # 10 (Implicitly detached); - A GPRS MS operating in MS operation mode B in network operation mode I is IMSI detached for both GPRS and CS services. A GPRS MS operating in MS operation mode A in network operation mode I is detached for GPRS services. If no RR connection exists then the MS is also IMSI detached for the CS services. - The MS shall change to state GMM-DEREGISTERED.NORMAL-SERVICE. If the rejected request was not for initiating a PDN connection for emergency bearer services, the MS shall then perform a new attach procedure. The MS should also activate PDP context(s) that were originally activated by the MS to replace any previously MS activated PDP context(s). The MS should also perform the procedures needed in order to activate any previously active multicast service(s). If S1 mode is supported in the MS, the MS shall handle the EMM state as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the service request procedure is rejected with the EMM cause with the same value. NOTE 3: In some cases, user interaction may be required and then the MS cannot activate the PDP and MBMS context(s) automatically. # 11 (PLMN not allowed); - The MS shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and enter the state GMM-DEREGISTERED. The MS shall delete the list of equivalent PLMNs. - The MS shall store the PLMN identity in the "forbidden PLMN list" and if the MS is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112]) then the MS shall start timer T3245 and proceed as described in subclause 4.1.1.6. If the message has been successfully integrity checked by the lower layers and the MS maintains a PLMN-specific attempt counter for that PLMN, then the MS shall set this counter to the MS implementation-specific maximum value. The MS shall start timer T3340 as described in subclause 4.7.1.9. - If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the RR connection is subsequently released: - A GPRS MS operating in MS operation mode A shall set the update status to U3 ROAMING NOT ALLOWED and shall delete any TMSI, LAI and ciphering key sequence number. The new MM state is MM IDLE. - The MS shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. An MS in GAN mode shall request a PLMN list in GAN (see 3GPP TS 44.318[ None ] [76b]) prior to perform a PLMN selection from this list according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the service request procedure is rejected with the EMM cause with the same value. # 12 (Location area not allowed); - The MS shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and shall change to state GMM-DEREGISTERED.LIMITED-SERVICE. - The mobile station shall store the LAI in the list of "forbidden location areas for regional provision of service". The MS shall start timer T3340 as described in subclause 4.7.1.9. - If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the RR connection is subsequently released: - If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number and shall reset the location update attempt counter. The new MM state is MM IDLE. - The MS shall perform a cell selection according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98]. NOTE 4: The cell selection procedure is not applicable for an MS in GAN mode. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the service request procedure is rejected with the EMM cause with the same value. # 13 (Roaming not allowed in this location area); - The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and shall change to state GMM-REGISTERED.LIMITED-SERVICE. - The MS shall store the LAI in the list of "forbidden location areas for roaming". The MS shall start timer T3340 as described in subclause 4.7.1.9. - If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the RR connection is subsequently released: - If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED and shall reset the location update attempt counter. The new MM state is MM IDLE. - The MS shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. An MS in GAN mode shall request a PLMN list in GAN (see 3GPP TS 44.318[ None ] [76b]) prior to perform a PLMN selection from this list according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state and EPS update status as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the service request procedure is rejected with the EMM cause with the same value. # 15 (No Suitable Cells In Location Area); - The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and shall change to state GMM-REGISTERED.LIMITED-SERVICE. - The MS shall store the LAI in the list of "forbidden location areas for roaming". The MS shall start timer T3340 as described in subclause 4.7.1.9. - If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the RR connection is subsequently released: - If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED and shall reset the location update attempt counter. The new MM state is MM IDLE. - The MS shall search for a suitable cell in another location area or a tracking area according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [121]. NOTE 5: The cell selection procedure is not applicable for an MS in GAN mode. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state and EPS update status as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the service request procedure is rejected with the EMM cause with the same value. #22 (Congestion); If the T3346 value IE is present in the SERVICE REJECT message and the value indicates that this timer is neither zero nor deactivated, the MS shall proceed as described below, otherwise it shall be considered as an abnormal case and the behaviour of the MS for this case is specified in subclause 4.7.13.5. If the rejected request was not for initiating a PDN connection for emergency bearer services, the MS shall abort the service request procedure and enter state GMM-REGISTERED, and stop timer T3317 if still running. The MS shall stop timer T3346 if it is running. If the SERVICE REJECT message is integrity protected, the MS shall start timer T3346 with the value provided in the T3346 value IE. If the SERVICE REJECT message is not integrity protected, the MS shall start timer T3346 with a random value from the default range specified in table 11.3a. The MS stays in the current serving cell and applies normal cell reselection process. The service request procedure may be started by CM layer, if it is still necessary, when timer T3346 expires or is stopped. A GPRS MS operating in MS operation mode A or B which is already IMSI attached for CS services in the network is still IMSI attached for CS services in the network. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state and EPS update status as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the service request procedure is rejected with the EMM cause with the same value. # 25 (Not authorized for this CSG) - Cause #25 is only applicable in UTRAN Iu mode and when received from a CSG cell. Other cases are considered as abnormal cases and the specification of the mobile station behaviour is given in subclause 4.7.13.5. - The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and shall change to state GMM-REGISTERED.LIMITED-SERVICE. - If the CSG ID and associated PLMN identity of the cell where the MS has sent the SERVICE REQUEST message are contained in the Allowed CSG list stored in the MS, the MS shall remove the entry corresponding to this CSG ID and associated PLMN identity from the Allowed CSG list. - If the CSG ID and associated PLMN identity of the cell where the MS has sent the SERVICE REQUEST message are contained in the Operator CSG list, the MS shall proceed as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14] subclause 3.1A. The MS shall start timer T3340 as described in subclause 4.7.1.9. If the MS is IMSI attached for non-GPRS services, the MS shall set the update status to U3 ROAMING NOT ALLOWED and shall reset the location update attempt counter. The new MM state is MM IDLE. - The MS shall search for a suitable cell according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98]. - If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state and EPS update status as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the service request procedure is rejected with the EMM cause with the same value. # 40 (No PDP context activated) - The MS shall deactivate locally all active PDP and MBMS contexts and the MS shall enter the state GMM-REGISTERED.NORMAL-SERVICE. If the rejected request was not for initiating a PDN connection for emergency bearer services, the MS may also activate PDP context(s) that were originally activated by the MS to replace any previously MS activated PDP context(s). The MS may also perform the procedures needed in order to activate any previously active multicast service(s). NOTE 6: In some cases, user interaction may be required and then the MS cannot activate the PDP and MBMS context(s) automatically. Other values are considered as abnormal cases. The specification of the MS behaviour in those cases is described in subclause 4.7.13.5. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.13.4 |
5,782 | Modify Bearer Response | The Modify Bearer Response message shall be sent on the S11/S4 interfaces by the SGW to the MME/S4-SGSN, on the S5/S8 interfaces by the PGW to the SGW and on the S2b interface by the PGW to the ePDG as part of the procedures listed for the Modify Bearer Request (see clause 7.2.7). If the MME has sent the counter for the RRC Cause "MO Exception data" in the Modify Bearer Resquest, the MME shall reset the counter value when receiving the Modify Bearer Response message. If handling of default bearer fails, then Cause at the message level shall be a failure cause. Possible Cause values are specified in Table 8.4-1. Message specific cause values are: - "Request accepted". - "Request accepted partially". - "Context not found". - "Service not supported". Table -1: Information Elements in a Modify Bearer Response Table -2: Bearer Context modified within Modify Bearer Response Table -3: Bearer Context marked for removal within Modify Bearer Response Table 7.2.8-4: Load Control Information within Modify Bearer Response Table 7.2.8-5: Overload Control Information within Modify Bearer Response Table 7.2.8-6: PGW Change Info within Modify Bearer Response | 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 | Modify |
5,783 | C.1.1 Sequence number generation schemes C.1.1.1 General scheme | According to section 6.3 of this specification, authentication vectors are generated in the authentication centre (AuC) using sequence numbers. This section specifies how these sequence numbers are generated. Authentication vectors may be generated and sent by the AuC in batches. The sequence numbers for the authentication vectors in a batch are generated one after the other according to the process described below. (1) In its binary representation, the sequence number consists of two concatenated parts SQN = SEQ || IND. is an index used in the array scheme described in C.1.2 and C.2.2. SEQ in its turn consists of two concatenated parts SEQ = SEQ1 || SEQ2. SEQ1 represents the most significant bits of SEQ, and SEQ2 represents the least significant bits of represents the least significant bits of SQN. (2) There is a counter SQNHE in the HE. SQN is stored by this counter. SQNHE is an individual counter, i.e. there is one per user. We have SQNHE = SEQHE || INDHE. (3) There is a global counter, e.g. a clock giving universal time. For short we call the value of this global counter at any one time GLC. If GLC is taken from a clock it is computed mod p, where p = 2n and n is the length of GLC and of SEQ2 in bits. (4) If GLC is taken from a clock then there is a number D > 0 such that the following holds: (i) the time interval between two consecutive increases of the clock (the clock unit) shall be chosen such that, for each user, at most D batches are generated at the AuC during any D clock units; (ii) the clock rate shall be significantly higher than the average rate at which batches are generated for any user; (iii) D << 2n. (5) When the HE needs new sequence numbers SQN to create a new batch of authentication vectors, HE retrieves the (user-specific) value of SEQHE = SEQ1HE || SEQ2HE from the database. (i) If SEQ2HE < GLC < SEQ2HE + p – D + 1 then HE sets SEQ= SEQ1HE || GLC; (ii) if GLC SEQ2HE GLC+D - 1 or SEQ2HE + p – D + 1 GLC then HE sets SEQ = SEQHE +1; (iii) if GLC+D - 1 < SEQ2HE then HE sets SEQ = (SEQ1HE +1) || GLC. (iv) After the generation of the authentication vector has been completed SEQHE is reset to SEQ; (v) for the handling of see C.1.2. NOTES 1. The clock unit and the value D have to be chosen with care so that condition (4)(i) is satisfied for every user at all times. Otherwise, user identity confidentiality may be compromised. When the parameters are chosen appropriately sequence numbers for a particular user do not reveal significant information about the user's identity. If authentication vectors for the CS and the PS domains are not separated by other means it is recommended to choose D >1 as requests from the two different domains may arrive completely independently. 2. By setting the parameters in C.1.1.1 (1) to (5) in an appropriate way the general scheme specified in this subsection also includes the cases where either SEQ2 is void and SEQ = SEQ1 or else, SEQ1 is void and SEQ = SEQ2, as follows: (a) If SEQ2 is void the generation of sequence numbers is not time-based. We then formally set SEQ2 GLC 0 (identical to zero) and D = 1. Conditions (4)(i) to (iii) do not apply as there is no clock. Then (5)(ii) always holds, and SEQ is incremented by 1 at each request. For better readability, this case is separated out in C.1.1.2. (b) If SEQ1 is void then we set D = 1. Assuming a start condition SEQ2HE < GLC and the absence of failures in the AuC, the condition (5)(i) then always holds, and SEQ = GLC for each request, i.e. the generation of sequence numbers is entirely time-based. In order to also accommodate potential failures in the AuC for entirely time-based sequence number , the variant described in the following Annex C.1.1.3 may be used. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | C.1.1 |
5,784 | 5.27.2.2 TSC Assistance Container determination based on PSFP | In the case of integration with IEEE TSN network, the TSN AF determines a TSC Assistance Container (defined in Table 5.27.2-2) and provides it to the PCF. The determination of TSC Assistance Container based on Per-Stream Filtering and Policing (PSFP) information applies only to Ethernet type PDU Sessions. NOTE 1: This clause assumes that PSFP information as defined in IEEE Std 802.1Q [98] and Table K.3.1-1is provided by CNC. PSFP information may be provided by CNC if TSN AF has declared PSFP support to CNC. TSN AF indicates the support for PSFP to CNC only if all the DS-TT and NW-TT ports of the 5GS Bridge have indicated support of PSFP. Means to derive the TSC Assistance Container if PSFP is not supported by 5GS and/or the CNC are beyond the scope of this specification. The TSN AF may be able to identify the ingress port and thereby the PDU Session as described in clause 5.28.2. The TSN AF interfaces towards the CNC for the PSFP (IEEE Std 802.1Q [98]) managed objects that correspond to the PSFP functionality implemented by the DS-TT and the NW-TT. Thus, when PSFP information is provided by the CNC, the TSN AF may extract relevant parameters from the PSFP configuration. The TSN AF calculates traffic pattern parameters (such as burst arrival time with reference to the ingress port and periodicity). TSN AF also obtains the flow direction as specified in clause 5.28.2. Survival Time may be pre-configured in TSN AF. TSN AF may enable aggregation of TSN streams if the TSN streams belong to the same traffic class, terminate in the same egress port and have the same periodicity and compatible Burst arrival time. When Survival Time information is provided for a TSN stream, then it should not be aggregated with other TSN streams into a single QoS Flow, or if they are aggregated, then the Survival Time parameter shall not be provided. One set of parameters and one TSC Assistance Container are created by the TSN AF for multiple TSN streams to enable aggregation of TSN streams to the same QoS Flow. Annex I describe how the traffic pattern information is determined. NOTE 2: Further details of aggregation of TSN streams (including determination of burst arrival times that are compatible so that TSN streams can be aggregated) are left for implementation. NOTE 3: In order for the TSN AF to get Burst Arrival Time, Periodicity on a per TSN stream basis, support for IEEE Std 802.1Q [98] (as stated in clause 4.4.8.2) Per-Stream Filtering and Policing (PSFP) with stream gate operation is a prerequisite. For a UE-UE TSC stream, the (TSN) AF divides the stream into one uplink stream and one or more downlink streams as defined in clause 5.28.2. The TSN AF binds the uplink and downlink streams to the PDU Sessions, and provides the streams on AF Session basis to the PCF(s). The TSN AF calculates traffic pattern parameters for the UL and the DL stream using the PSFP configuration (if provided) respectively: - For the uplink stream, the Flow Direction is set to uplink and traffic pattern parameters (such as burst arrival time with reference to the ingress port and periodicity) is determined as described in Annex I. - For downlink stream, the Flow Direction is set to downlink, the burst arrival time is set to sum of burst arrival time of the UL stream and 5GS Bridge delay of PDU Session carrying the UL stream, and the periodicity is determined as described in Annex I. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.27.2.2 |
5,785 | 4.7.13.1 Service Request procedure initiation | The MS initiates the Service request procedure by sending a SERVICE REQUEST message. The timer T3317 shall be started after the SERVICE REQUEST message has been sent and state GMM-SERVICE-REQUEST-INITIATED is entered. The message SERVICE REQUEST shall contain the P-TMSI and the Service type shall indicate either "data", "signalling", "paging response", "MBMS multicast service reception" or "MBMS broadcast service reception". The MS shall not issue another Service request when the MS is in state GMM-SERVICE-REQUEST-INITIATED If the PDP context status information element is included in the SERVICE REQUEST message, then the network shall deactivate all those PDP contexts locally (without peer to peer signalling between the MS and the network) which are not in SM state PDP-INACTIVE on the network side, but are indicated by the MS as being in state PDP-INACTIVE. If the MBMS context status information element is included in the SERVICE REQUEST message, then the network shall deactivate all those MBMS contexts locally (without peer to peer signalling between the MS and network) which are not in SM state PDP-INACTIVE on the network side, but are indicated by the MS as being in state PDP-INACTIVE. If no MBMS context status information element is included, then the network shall deactivate all MBMS contexts locally which are not in SM state PDP-INACTIVE on the network side. For a Service Request of type "data", the MS may include the Uplink data status information element in the SERVICE REQUEST message. The Uplink data status information indicates which preserved PDP contexts have pending uplink data to be sent. If the Uplink data status information element is included in the SERVICE REQUEST message with service type "data", the network may use this information to determine which of the RABs for the preserved PDP contexts to re-establish. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.13.1 |
5,786 | 4.24 Minimization of service interruption | The UE and the network may support Minimization of service interruption (MINT). MINT aims to enable a UE to obtain service from a PLMN offering disaster roaming services when a disaster condition applies to the UE's determined PLMN with disaster condition. If the UE supports MINT, the indication of whether disaster roaming is enabled in the UE, the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN', the one or more "list of PLMN(s) to be used in disaster condition", disaster roaming wait range and disaster return wait range provisioned by the network, if available, are stored in the non-volatile memory in the ME as specified in annex C and are kept when the UE enters 5GMM-DEREGISTERED state. Annex C specifies condition under which the indication of whether disaster roaming is enabled in the UE, the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN', the one or more "lists of PLMN(s) to be used in disaster condition", disaster roaming wait range and disaster return wait range stored in the ME are deleted. Upon selecting a PLMN for disaster roaming as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]: a) if the UE does not have a stored disaster roaming wait range, the UE shall perform a registration procedure for disaster roaming services on the selected PLMN as described in subclause 5.5.1; and b) if the UE has a stored disaster roaming wait range, the UE shall generate a random number within the disaster roaming wait range and start a timer with the generated random number. While the timer is running, the UE shall not initiate registration on the selected PLMN except if the UE needs to request an emergency PDU session, in which case the UE shall initiate the registration procedure, set the 5GS registration type IE to "emergency registration" in the REGISTRATION REQUEST message and keep the timer running. Upon expiration of the timer, if the UE does not have an emergency PDU session, the UE shall perform a registration procedure for disaster roaming services as described in subclause 5.5.1 if still camped on the selected PLMN. If the UE has an emergency PDU session when the timer expires, the registration procedure for disaster roaming services as described in subclause 5.5.1 shall be performed after the release of the emergency PDU session, if the UE is still camped on the selected PLMN. The timer started with a generated random number within the disaster roaming wait range is stopped and the UE shall perform a PLMN selection as described in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5], if: a) the UE has successfully registered over non-3GPP access on another PLMN; b) the UE has successfully registered with an allowable PLMN; or c) an NG-RAN cell selected for camping of the selected PLMN broadcasts neither the disaster related indication nor a "list of one or more PLMN(s) with disaster condition for which disaster roaming services is offered by the available PLMN" including the determined PLMN with Disaster Condition (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]). Upon determining that a disaster condition has ended and that the UE shall perform PLMN selection as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]: a) if the UE does not have a stored disaster return wait range, the UE shall perform a registration procedure on the selected PLMN; and b) if the UE has a stored disaster return wait range, the UE shall generate a random number within the disaster return wait range and start a timer with the generated random number value. While the timer is running, the UE shall not initiate registration on the selected PLMN except if the UE needs to request an emergency PDU session, in which case the UE shall initiate the registration procedure, set the 5GS registration type IE to "emergency registration" in the REGISTRATION REQUEST message and keep the timer running. Upon expiration of the timer, if the UE does not have an emergency PDU session, the UE shall perform a registration procedure if still camped on the selected PLMN. If the UE has an emergency PDU session when the timer expires, the registration procedure as described in subclause 5.5.1 shall be performed after the release of the emergency PDU session, if the UE is still camped on the selected PLMN. When the AMF assigns a registration area to the UE registered for disaster roaming services, the AMF shall only include TAIs covering the area with the disaster condition. When the AMF determines that the disaster condition has ended and the UE which is registered for disaster roaming services has an emergency PDU session, the AMF shall initiate the generic UE configuration update procedure to indicate that the UE is registered for emergency services as described in subclause 5.4.4.2. Interworking with EPS is not supported for UEs that are registered for disaster roaming services. When registering for disaster roaming services, the UE indicates to the network that S1 mode is not supported as described in subclause 5.5.1.2.2. While registered for disaster roaming services and upon a need to establish an emergency PDU session or perform emergency services fallback, the UE initiates the registration procedure for mobility and periodic registration update and indicates that S1 mode is supported as described in subclause 5.5.1.3.2. If the UE is registered for disaster roaming services and the registered PLMN is removed from forbidden PLMN lists due to reasons specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] subclause 4.4.6 or in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] Annex C, then UE shall initiate the de-registration procedure and perform PLMN selection as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.24 |
5,787 | 6.6.2.2.1 Minimum requirement (network signalled value "NS_03", “NS_11”, "NS_20", and “NS_21”) | Additional spectrum emission requirements are signalled by the network to indicate that the UE shall meet an additional requirement for a specific deployment scenario as part of the cell handover/broadcast message. When "NS_03", "NS_11", "NS_20" or "NS_21" is indicated in the cell, the power of any UE emission shall not exceed the levels specified in Table 6.6.2.2.1-1. Table 6.6.2.2.1-1: Additional requirements NOTE: As a general rule, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy, sensitivity and efficiency, the resolution bandwidth may be smaller than the measurement bandwidth. When the resolution bandwidth is smaller than the measurement bandwidth, the result should be integrated over the measurement bandwidth in order to obtain the equivalent noise bandwidth of the measurement bandwidth. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.6.2.2.1 |
5,788 | 7.3.18 Configuration Transfer Tunnel | A Configuration Transfer Tunnel message shall be used to: - tunnel eNodeB Configuration Transfer messages from a source MME to a target MME over the S10 interface. The purpose of the eNodeB Configuration Transfer is to transfer information from an eNodeB to a target eNodeB or an en-gNB connected to a target eNB in unacknowledged mode (see 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10]). - tunnel eNodeB Configuration Transfer messages from a source MME to a target AMF, or to tunnel Uplink RAN Configuration Transfer messages from a source AMF to a target MME, over the N26 interface. This is to transfer RAN configuration information or inter-system SON configuration information between an eNodeB and a gNB in unacknowledged mode (see 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10] and 3GPP TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [84]). Table 7.3.18-1 specifies the presence requirements and conditions of the IEs in the message. Table 7.3.18-1: Information Elements in a Configuration Transfer Tunnel Message | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 7.3.18 |
5,789 | 5.1.3.2.4.7 EMM-REGISTERED.NO-CELL-AVAILABLE | E-UTRAN coverage has been lost, PSM is active in the UE or the access stratum is de-activated due to discontinuous coverage (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]). If PSM is active, the UE can deactivate PSM at any time by activating the AS layer when the UE needs to send mobile originated signalling or user data. Otherwise, the UE shall not initiate any EMM procedure except for cell and PLMN reselection. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.1.3.2.4.7 |
5,790 | 5.8 User Plane Management 5.8.1 General | User Plane Function(s) handle the user plane path of PDU Sessions. 3GPP specifications support deployments with a single UPF or multiple UPFs for a given PDU Session. UPF selection is performed by SMF. The details of UPF selection is described in clause 6.3.3. The number of UPFs supported for a PDU Session is unrestricted. For an IPv4 type PDU Session or an IPv6 type PDU Session without multi-homing or an IPv4v6 type PDU Session, when multiple PDU Session Anchors are used (due to UL CL being inserted), only one IPv4 address and/or IPv6 prefix is allocated for the PDU Session. For an IPv6 multi-homed PDU Session there are multiple IPv6 prefixes allocated for the PDU Session as described in clause 5.6.4.3. If the SMF had requested the UPF to proxy ARP or IPv6 Neighbour Solicitation for an Ethernet DNN, the UPF should respond to the ARP or IPv6 Neighbour Solicitation Request, itself. Deployments with one single UPF used to serve a PDU Session do not apply to the Home Routed case and may not apply to the cases described in clause 5.6.4. Deployments where a UPF is controlled either by a single SMF or multiple SMFs (for different PDU Sessions) are supported. UPF traffic detection capabilities may be used by the SMF in order to control at least following features of the UPF: - Traffic detection (e.g. classifying traffic of IP type, Ethernet type, or unstructured type) - Traffic reporting (e.g. allowing SMF support for charging). - QoS enforcement (The corresponding requirements are defined in clause 5.7). - Traffic routing (e.g. as defined in clause 5.6.4. for UL CL or IPv6 multi-homing). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.8 |
5,791 | 5.16.3.3 Homogeneous support for IMS voice over PS Session supported indication | 5GC shall support the usage of "Homogeneous Support of IMS Voice over PS Sessions" indication between AMF and UDM. When the AMF initiates Nudm_UECM_Registration operation to the UDM, it shall: - if "IMS Voice over PS Sessions" is supported homogeneously in all TAs in the serving AMF for the UE, include the "Homogeneous Support of IMS Voice over PS Sessions" indication set to "Supported"; - if none of the TAs of the serving AMF supports "IMS Voice over PS Sessions" for the UE, include the "Homogeneous Support of IMS Voice over PS Sessions" indication set to "Not supported"; - if "IMS Voice over PS Sessions" support is either non-homogeneous or unknown, not include the "Homogeneous Support of IMS Voice over PS Sessions" indication. The AMF shall be able to provide the "Homogeneous Support of IMS Voice over PS Sessions" indication as described above to the UDM using Nudm_UECM_Update operation as specified in clause 4.2.2.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The UDM shall take this indication into account when doing Terminating Access Domain Selection (T-ADS) procedure for IMS voice. NOTE: A TA supports "IMS Voice over PS Sessions" if the serving AMF indicates IMS voice over PS Session Supported Indication over 3GPP access to the UE, as described in clause 5.16.3.2. In order to support routing of incoming IMS voice calls to the correct domain, the network-based T-ADS (see TS 23.292[ IP Multimedia Subsystem (IMS) centralized services; Stage 2 ] [63] and TS 23.221[ Architectural requirements ] [23]) requires that the "Homogeneous Support of IMS Voice over PS Sessions" indication is set to "Supported" for all registered TAs of the UE or "Not supported" for all registered TAs of the UE. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.16.3.3 |
5,792 | A.3.9 Guidelines on use of ToAddModList and ToReleaseList | In order to benefit from delta signalling when modifying lists with many and/or large elements, so-called add/mod- and release- lists should be used. Instead of a single list containing all elements of the list, the ASN.1 provides two lists. One list is used to convey the actual elements that are to be added to the list or modified in the list. The second list conveys only the identities (IDs) of the list elements that are to be released from the list. In other words, the ASN.1 defines only means to signal modifications to a list maintained in the receiver (typically the UE). An example is provided below: -- /example/ ASN1START AnExampleIE ::= SEQUENCE { elementsToAddModList SEQUENCE (SIZE (1..maxNrofElements)) OF Element OPTIONAL, -- Need N elementsToReleaseList SEQUENCE (SIZE (1..maxNrofElements)) OF ElementId OPTIONAL, -- Need N ... } Element ::= SEQUENCE { elementId ElementId, aField INTEG ER (0..16777215), anotherField OCTET STRING, ... } ElementId ::= INTEGER (0..maxNrofElements-1) maxNrofElements INTEGER ::= 50 maxNrofElements-1 INTEGER ::= 49 -- /example/ ASN1STOP As can be seen, the elements of the list must contain an identity (INTEGER) that identifies the elements unambiguously upon addition, modification and removal. It is recommended to define an IE for that identifier (here ElementId) so that it can be used both for a field inside the element as well as in the elementsToReleaseList. Both lists should be made OPTIONAL and flagged as "Need N". The need code reflects that the UE does not maintain the received lists as such but rather updates its configuration using the information therein. In other words, it is not possible to provide via delta signalling an update to a previously signalled elementsToAddModList or elementsToReleaseList (which Need M would imply). The update is always in relation to the UE's internal configuration. Note that the release of a field (a list element as well as any other field) releases all its sub-fields (sub-fields configured by elementsToAddModList and any other sub-field). If no procedural text is provided for a set of ToAddModList and ToReleaseList, the following generic procedure applies: The UE shall: 1> for each ElementId in the elementsToReleaseList,: 2> if the current UE configuration includes an Element with the given ElementId: 3> release the Element from the current UE configuration; 1> for each Element in the elementsToAddModList: 2> if the current UE configuration includes an Element with the given ElementId: 3> modify the configured Element in accordance with the received Element; 2> else: 3> add received Element to the UE configuration. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | A.3.9 |
5,793 | 9.2.7 CM service abort | This message is sent by the mobile station to the network to request the abortion of the first MM connection establishment in progress and the release of the RR connection. See table 9.2.9/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: CM SERVICE ABORT Significance: dual Direction: mobile station to network Table 9.2.9/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : CM SERVICE ABORT message content | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.2.7 |
5,794 | 5.2.6.11.4 Nnef_ServiceParameter_Delete operation | Service operation name: Nnef_ServiceParameter_Delete Description: The consumer deletes service specific parameters from the UDR via the NEF. Inputs, Required: Service Descriptor (e.g. the combination of DNN and S-NSSAI, an AF-Service-Identifier or an External Application Identifier), Transaction Reference ID. Inputs, Optional: Target UE identifiers (e.g. the address (IP or Ethernet) of the UE if available, GPSI if available, External Group Identifier if available) or "PLMN ID(s) of inbound roamers". Outputs, Required: Operation execution result indication. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.11.4 |
5,795 | 16.13.3 Identification, access and camping restrictions | A RedCap UE can be identified by the network during Random Access procedure via MSG3/MSGA from a RedCap specific LCID(s) and optionally via MSG1/MSGA (PRACH occasion or PRACH preamble). An eRedCap UE can be identified by the network during Random Access procedure via MSG3/MSGA from an eRedCap specific LCID(s) and optionally via MSG1. For RedCap UE identification via MSG1/MSGA, RedCap specific Random Access configuration may be configured by the network. For eRedCap UE identification via MSG1, eRedCap specific Random Access configuration may be configured by the network. For MSG3/MSGA, an (e)RedCap UE is identified by the dedicated LCID(s) indicated for CCCH identification (CCCH or CCCH1) regardless whether (e)RedCap specific Random Access configuration is configured by the network. (e)RedCap UEs with 1 Rx branch and 2 Rx branches can be allowed separately via system information. In addition, (e)RedCap UEs in Half-Duplex FDD mode can be allowed via system information. A RedCap specific IFRI can be provided in SIB1, when absent, RedCap UEs access is not allowed. An eRedCap specific IFRI can be provided in SIB1, when absent, eRedCap UEs access is not allowed. Information on which frequencies (e)RedCap UE access is allowed can be provided in system information. An (e)RedCap UE with 1 Rx branch applies the associated offset for broadcasted cell specific RSRP thresholds for random access, SDT, cell edge condition and cell (re)selection criterion as specified in TS 38.133[ NR; Requirements for support of radio resource management ] [13]. NOTE: It is up to the E-UTRA network, if possible, to avoid handover attempts of an (e)RedCap UE to a target NR cell not supporting (e)RedCap. It is up to the (e)RedCap UE implementation, if possible, to recover from handover attempts to a target NR cell not supporting (e)RedCap. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.13.3 |
5,796 | 4.7.3.2.5 Abnormal cases in the MS | The MS shall proceed as follows: 1) If the combined attach was successful for GPRS services only and the ATTACH ACCEPT message contained a cause value not treated in subclause 4.7.3.2.3.2 or the GMM Cause IE is not included in the message, the MS shall proceed as follows: a) The MS shall stop timer T3310 if still running, and shall enter state MM IDLE. The routing area updating attempt counter shall be incremented; b) If the routing area updating attempt counter is less than 5, and the stored RAI is equal to the RAI of the current serving cell and the GMM update status is equal to GU1 UPDATED: - the MS shall keep the GMM update status GU1 UPDATED and changes state to GMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM. The MS shall start timer T3311. When timer T3311 expires the combined routing area update procedure indicating "combined RA/LA updating with IMSI attach" is triggered again; and c) If the routing area updating attempt counter is greater than or equal to 5: - the MS shall start timer T3302 and shall change to state GMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM; and - a GPRS MS operating in MS operation mode A shall then proceed with appropriate MM specific procedure; a GPRS MS operating in MS operation mode B may then proceed with appropriate MM specific procedures. The MM sublayer shall act as in network operation mode II as long as the combined GMM procedures are not successful and no new RA is entered; and 2) Otherwise, the abnormal cases specified in subclause 4.7.3.1.5 apply with the following modification. If the GPRS attach attempt counter is incremented according to subclause 4.7.3.1.5 the next actions depend on the Location Area Identities (stored on SIM/USIM and the one of the current serving cell) and the value of the attach attempt counter: - if the update status is U1 UPDATED, and the stored LAI is equal to the one of the current serving cell and the attach attempt counter is smaller than 5, then the mobile station shall keep the update status to U1 UPDATED, the new MM state is MM IDLE substate NORMAL SERVICE; - if the attach attempt counter is smaller than 5 and, additionally, the update status is different from U1 UPDATED or the stored LAI is different from the one of the current serving cell, then the mobile station shall delete any LAI, TMSI, ciphering key sequence number stored in the SIM/USIM and list of equivalent PLMNs and set the update status to U2 NOT UPDATED. The MM state remains MM LOCATION UPDATING PENDING; or - if the attach attempt counter is greater or equal to 5, then the mobile station shall delete any LAI, TMSI, ciphering key sequence number stored in the SIM/USIM and list of equivalent PLMNs and set the update status to U2 NOT UPDATED. A GPRS MS operating in MS operation mode A shall then proceed with appropriate MM specific procedure; a GPRS MS operating in MS operation mode B may then proceed with appropriate MM specific procedures. The MM sublayer shall act as in network operation mode II as long as the combined GMM procedures are not successful and no new RA is entered. The new MM state is MM IDLE substate ATTEMPTING TO UPDATE or optionally MM IDLE substate PLMN SEARCH in order to perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.3.2.5 |
5,797 | 4.2.1.7 Mean E-RAB Setup time | a) This measurement provides the mean time per QCI it takes to establish an E-RAB. b) DER (n=1) c) This measurement is obtained by accumulating the time intervals for every successfully established E-RAB between the receipt of an E-RAB SETUP REQUEST or INITIAL CONTEXT SETUP REQUEST message and the transmission of the corresponding E-RAB SETUP RESPONSE or INITIAL CONTEXT SETUP RESPONSE message by the eNodeB over the granularity period. The end value of this time will then be divided by the number of successfully established E-RABs in the granularity period to give the arithmetic mean. The accumulator shall be reinitialised at the beginning of each granularity period. The measurement is split into subcounters per QCI, and the possible QCIs are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. d) Each measurement is an integer value (in milliseconds). e) The measurement name has the form ERAB.EstabTimeMean.QCI where QCI identifies the E-RAB level quality of service class. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switching. h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.2.1.7 |
5,798 | 6.6.2.2.7 Minimum requirement (network signalled value "NS_35") | Additional spectrum emission requirements are signalled by the network to indicate that the UE shall meet an additional requirement for a specific deployment scenario as part of the cell handover/broadcast message. When "NS_35" is indicated in the cell, the power of any UE emission shall not exceed the levels specified in Table 6.6.2.2.7-1. Table 6.6.2.2.7-1: Additional requirements NOTE: As a general rule, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy, sensitivity and efficiency, the resolution bandwidth may be smaller than the measurement bandwidth. When the resolution bandwidth is smaller than the measurement bandwidth, the result should be integrated over the measurement bandwidth in order to obtain the equivalent noise bandwidth of the measurement bandwidth. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.6.2.2.7 |
5,799 | 4.7.7.7 Use of established security contexts | In A/Gb mode, in the case of an established GSM security context, the GPRS GSM ciphering key shall be taken into use by the MS before the AUTHENTICATION AND CIPHERING RESPONSE message is transmitted. In A/Gb mode, in the case of an established UMTS security context, and if the network indicates in the AUTHENTICATION AND CIPHERING REQUEST message to the MS that a GEA ciphering algorithm that requires a 64-bit ciphering key shall be taken into use, then the GPRS GSM ciphering key shall be taken into use by the MS before the AUTHENTICATION AND CIPHERING RESPONSE message is transmitted. The network shall derive a GPRS GSM ciphering key from the GPRS UMTS ciphering key and the GPRS UMTS integrity key, by using the conversion function named "c3" defined in 3GPP TS 33.102[ 3G security; Security architecture ] [5a]. In A/Gb mode, in the case of an established UMTS security context, and if the network indicates in the AUTHENTICATION AND CIPHERING REQUEST message to the MS that a GEA ciphering algorithm that requires a 128-bit ciphering key shall be taken into use, then the MS shall take the following actions: - if authentication is not requested and a GEA ciphering algorithm that requires 64-bit ciphering key is in use, the MS shall take into use the GPRS GSM Kc128 derived by the ME from the GPRS UMTS ciphering key and GPRS UMTS integrity key of the established UMTS security context in use (see 3GPP TS 33.102[ 3G security; Security architecture ] [5a]) before the AUTHENTICATION AND CIPHERING RESPONSE message is transmitted;. - if authentication is not requested and a GEA ciphering algorithm that requires 128-bit ciphering key is in use, the GPRS GSM Kc128 of the established UMTS security context in use still applies; otherwise, the MS shall take into use the GPRS GSM Kc128 derived by the ME from the GPRS UMTS ciphering key and the GPRS UMTS integrity key provided by the USIM during the latest successful authentication procedure (see subclause 4.7.7.3a) before the AUTHENTICATION AND CIPHERING RESPONSE message is transmitted. In A/Gb mode, in the case of an established UMTS security context, and if the network indicates in the AUTHENTICATION AND CIPHERING REQUEST message to the MS that a GEA ciphering algorithm that requires a 128-bit ciphering key shall be taken into use, then the network shall derive a GPRS GSM Kc128 (see subclause 4.7.7.3a). In A/Gb mode, if an established UMTS security context context is available in the network, if the MS indicates support of integrity protection to the network and the network supports integrity protection, if the network indicates in the AUTHENTICATION AND CIPHERING REQUEST message to the MS that a new GPRS GSM integrity algorithm shall be taken into use but no authentication is requested, then the GPRS GSM Kint of the established UMTS security context in use still applies in the MS and network. In A/Gb mode, in the case of an established UMTS security context, and if the network indicates in the AUTHENTICATION AND CIPHERING REQUEST message to the MS that a GIA integrity protection algorithm that requires a 128-bit integrity key shall be taken into use but no authentication is requested, then the GPRS GSM Kint of the established UMTS security context in use still applies in the MS. In A/Gb mode, if during an ongoing, already ciphering protected RR connection, the network initiates a new Authentication and ciphering procedure, the new GPRS GSM ciphering key or GPRS GSM Kc128 shall be taken into use by the MS before the AUTHENTICATION AND CIPHERING RESPONSE message is transmitted. In case of inter-system change to Iu mode after receipt of the AUTHENTICATION AND CIPHERING REQUEST message, the MS and the network shall take the new keys into use immediately after the inter-system change. In Iu mode, in the case of an established GSM security context, the ME shall derive a GPRS UMTS ciphering key and a GPRS UMTS integrity key from the GPRS GSM ciphering key by using the conversion functions named "c4" and "c5" defined in 3GPP TS 33.102[ 3G security; Security architecture ] [5a]. The derived GPRS UMTS ciphering key and GPRS UMTS integrity key shall be taken into use by the MS when a valid SECURITY MODE COMMAND message indicating PS domain is received during an RR connection (the definition of a valid SECURITY MODE COMMAND message is given in 3GPP TS 25.331[ None ] [23c]). The network shall derive a GPRS UMTS ciphering key and a GPRS UMTS integrity key from the GPRS GSM ciphering key by using the conversion functions named "c4" and "c5" defined in 3GPP TS 33.102[ 3G security; Security architecture ] [5a]. In Iu mode, in the case of an established UMTS security context, the GPRS UMTS ciphering key and the GPRS UMTS integrity key shall be taken into use by the MS when a valid SECURITY MODE COMMAND message indicating PS domain is received during a PS signalling connection (the definition of a valid SECURITY MODE COMMAND message is given in 3GPP TS 25.331[ None ] [23c]). In Iu mode, if the MS received a valid SECURITY MODE COMMAND message indicating PS domain in Iu mode or a valid AUTHENTICATION AND CIPHERING REQUEST message in A/Gb mode before the network initiates a new authentication and ciphering procedure and establishes a new GSM/UMTS security context, the new GPRS UMTS ciphering key and GPRS UMTS integrity key are taken into use by the MS, when a new valid SECURITY MODE COMMAND message indicating PS domain is received during the PS signalling connection. In case of inter-system change to A/Gb mode, the MS and the network shall take the new keys into use immediately after the inter-system change. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.7.7 |
5,800 | A.4.3 Non-critical extension of messages A.4.3.1 General principles | The mechanisms to extend a message in a non-critical manner are defined in A.3.3. W.r.t. the use of extension markers, the following additional guidelines apply: - When further non-critical extensions are added to a message that has been critically extended, the inclusion of these non-critical extensions in earlier critical branches of the message should be avoided when possible. - The extension marker ("...") is the primary non-critical extension mechanism that is used but empty sequences may be used if length determinant is not required. Examples of cases where a length determinant is not required: - at the end of a message; - at the end of a structure contained in a BIT STRING or OCTET STRING. - When an extension marker is available, non-critical extensions are preferably placed at the location (e.g. the IE) where the concerned parameter belongs from a logical/ functional perspective (referred to as the 'default extension location'). - It is desirable to aggregate extensions of the same release or version of the specification into a group, which should be placed at the lowest possible level. - In specific cases it may be preferable to place extensions elsewhere (referred to as the 'actual extension location') e.g. when it is possible to aggregate several extensions in a group. In such a case, the group should be placed at the lowest suitable level in the message. - In case placement at the default extension location affects earlier critical branches of the message, locating the extension at a following higher level in the message should be considered. - In case an extension is not placed at the default extension location, an IE should be defined. The IE's ASN.1 definition should be placed in the same ASN.1 clause as the default extension location. In case there are intermediate levels in-between the actual and the default extension location, an IE may be defined for each level. Intermediate levels are primarily introduced for readability and overview. Hence intermediate levels need not always be introduced e.g. they may not be needed when the default and the actual extension location are within the same ASN.1 clause. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | A.4.3 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.