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,201 | 5.7.7.3 PDU Set Error Rate | The PDU Set Error Rate (PSER) defines an upper bound for the rate of PDU Sets that have been processed by the sender of a link layer protocol (e.g. RLC in RAN of a 3GPP access) but that are not successfully delivered by the corresponding receiver to the upper layer (e.g. PDCP in RAN of a 3GPP access). Thus, the PSER defines an upper bound for a rate of non-congestion related PDU Set losses. The purpose of the PSER is to allow for appropriate link layer protocol configurations (e.g. RLC and HARQ in RAN of a 3GPP access). NOTE 1: In this Release, a PDU Set is considered as successfully delivered only when all PDUs of a PDU Set are delivered successfully. NOTE 2: How RAN enforces PSER is up to RAN implementation. A QoS Flow is associated with at most one PDU Set Error Rate value per direction. PSER is an optional parameter. If the PSER is available, the PSER supersedes the PER. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.7.3 |
5,202 | 4.3.7.4.2 NAS level congestion control | 4.3.7.4.2.1 General NAS level congestion control contains the functions: "APN based congestion control" and "General NAS level Mobility Management control". The use of the APN based congestion control is for avoiding and handling of EMM and ESM signalling congestion associated with UEs with a particular APN. Both UEs and network shall support the functions to provide APN based EMM and ESM congestion control. The MME may detect the NAS signalling congestion associated with the APN and start and stop performing the APN based congestion control based on criteria such as: - Maximum number of active EPS bearers per APN; - Maximum rate of EPS Bearer activations per APN; - One or multiple PDN GWs of an APN are not reachable or indicated congestion to the MME; - Maximum rate of MM signalling requests associated with the devices with a particular subscribed APN; and/or - Setting in network management. The MME may detect the NAS signalling congestion associated with the UEs belonging to a particular group. The MME may start and stop performing the group specific NAS level congestion control based on criteria such as: - Maximum rate of MM and SM signalling requests associated with the devices of a particular group; and/or - Setting in network management. The MME may detect the NAS signalling congestion associated with the UEs that belong to a particular group and are subscribed to a particular APN. The MME may start and stop performing the APN and group specific NAS level congestion control based on criteria such as: - Maximum number of active EPS bearers per group and APN; - Maximum rate of MM and SM signalling requests associated with the devices of a particular group and a particular subscribed APN; and/or - Setting in network management. The MME should not apply NAS level congestion control for high priority access and emergency services. With General NAS level Mobility Management control, the MME may also use the reject of NAS level Mobility Management signalling requests under general congestion conditions such as detecting congestion of one or several DCNs in an MME serving multiple DCNs. In addition, for UEs that don't support the Service Gap Control feature (see clause 4.3.17.9), the MME may return a Mobility Management back-off timer to the UE in responses to requests where the intention is to send MO data or re-attach with PDN connectivity when the Service gap timer for the UE is running at the MME. 4.3.7.4.2.2 APN based Session Management congestion control The APN based Session Management congestion control may be activated by MME due to e.g. congestion situation at MME, or by OAM at MME, or by a restart or recovery condition of a PDN GW, or by a partial failure or recovery of a PDN GW for a particular APN(s). The MME may reject the EPS Session Management (ESM) requests from the UE (e.g. PDN Connectivity, or Bearer Resource Allocation Requests) with a Session Management back-off timer when ESM congestion associated with the APN is detected. If the UE provides no APN, then the MME uses the APN which is used in PDN GW selection procedure. The MME may deactivate PDN connections belonging to a congested APN by sending the NAS Deactivate EPS Bearer Context Request message to the UE with a Session Management back-off timer. If Session Management back-off timer is set in the NAS Deactivate EPS Bearer Context Request message then the cause "reactivation requested" should not be set. NOTE 1: UEs that don't support the Session Management back-off timer (including earlier release of UE) might contribute to increasing the signalling load in the MME by reattempting Session Management procedure. The MME may store a Session Management back-off time per UE and APN when congestion control is active for an APN if a request without the low access priority indicator is rejected by the MME. The MME may immediately reject any subsequent request from the UE targeting to the APN before the stored Session Management back-off time is expired. If the MME stores the Session Management back-off time per UE and APN and the MME decides to send a Session Management Request message to a UE connected to the congested APN (e.g. due to decreased congestion situation), the MME shall clear the Session Management back-off time prior to sending any Session Management Request message to the UE. NOTE 2: The above functionality is to diminish the performance advantage for UEs that do not support the NAS level back-off timer (e.g. pre-Rel-10 UEs) compared to UEs that do support it. Upon reception of the Session Management back-off timer in the EPS Session Management reject message or in the NAS Deactivate EPS Bearer Context Request message, the UE shall take the following actions until the timer expires: - If APN is provided in the rejected EPS Session Management Request message or if the Session Management back-off timer is received in the NAS Deactivate EPS Bearer Context Request message, the UE shall not initiate any Session Management procedures for the congested APN. The UE may initiate Session Management procedures for other APNs. - If APN is not provided in the rejected EPS Session Management Request message, the UE shall not initiate any Session Management requests of any PDN type without APN. The UE may initiate Session Management procedures for specific APN. - Cell/TA/PLMN/RAT change do not stop the Session Management back-off timer. - The UE is allowed to initiate the Session Management procedures for high priority access and emergency services even when the Session Management back-off timer is running. - The UE is allowed to initiate Bearer Resource Modification procedure to report 3GPP PS Data Off status change when the EPS Session Management back off timer is running. - If the UE receives a network initiated EPS Session Management Request message for the congested APN while the Session Management back-off timer is running, the UE shall stop the Session Management back-off timer associated with this APN and respond to the MME. - If the UE is configured with a permission for overriding low access priority and the Session Management back-off timer is running due to a reject message received in response to a request with low access priority, the upper layers in the UE may request the initiation of Session Management procedures without low access priority. The UE is allowed to initiate PDN disconnection procedure (e.g. sending PDN Disconnection Request) when the EPS Session Management back off timer is running. NOTE 3: The UE does not delete the related Session Management back-off timer when disconnecting a PDN connection. The UE shall support a separate Session Management back-off timer for every APN that the UE may activate. To avoid that large amounts of UEs initiate deferred requests (almost) simultaneously, the MME should select the Session Management back-off timer value so that deferred requests are not synchronized. The APN based Session Management congestion control is applicable to the NAS ESM signalling initiated from the UE in the control plane. The Session Management congestion control does not prevent the UE to send and receive data or initiate Service Request procedures for activating user plane bearers towards the APN(s) that are under ESM congestion control. 4.3.7.4.2.3 APN based Mobility Management congestion control The MME may perform the APN based congestion control for UEs with a particular subscribed APN by rejecting Attach procedures with a Mobility Management back-off timer. When congestion control is active for UEs with a particular subscribed APN, a Mobility Management back-off timer may be sent by the MME to UE. If MME maintains the UE context, the MME may store the back-off time per UE if a request without the low access priority indicator is rejected by the MME. The MME may immediately reject any subsequent request from the UE before the stored back-off time is expired. NOTE 1: The above functionality is to diminish the performance advantage for UEs that do not support the NAS level back-off timer (e.g. pre-Rel-10 UEs) compared to UEs that do support it. After rejecting Attach Requests, the MME should keep the Subscriber Data for some time. This allows for rejection of subsequent requests without HSS signalling when the congestion situation resulting from UEs with a particular subscribed APN persists. NOTE 2: Prior to the reject of attach messages of a UE by the MME, Subscriber Data for a UE may be present at the MME because it was not deleted after the UE's detach. In this case when APN based congestion control is active for a particular APN in the MME, the first reject of an attach message by the MME for this UE, may be done without HSS signalling as well. While the Mobility Management back-off timer is running, the UE shall not initiate any NAS request for Mobility Management procedures. However, the UE is allowed to initiate the Mobility Management procedures for high priority access and emergency services even when the Mobility Management back-off timer is running. While the Mobility Management back-off timer is running, the UE is allowed to perform Tracking Area Update if it is already in connected mode. While the Mobility Management back-off timer is running, the UE configured with a permission for overriding low access priority is allowed to initiate the Mobility Management procedures without low access priority if the Mobility Management back-off timer was started due to a reject message received in response to a request with low access priority and the upper layers in the UE request to activate a PDN connection without low access priority or the UE has an activated PDN connection that is not with low access priority. To avoid that large amounts of UEs initiate deferred requests (almost) simultaneously, the MME should select the Mobility Management back-off timer value so that deferred requests are not synchronized. NOTE 3: When receiving the Mobility Management back-off timer the UE behaviour is not APN specific. 4.3.7.4.2.4 General NAS level Mobility Management congestion control Under general overload conditions the MME may reject Mobility Management signalling requests from UEs. When a NAS request is rejected, a Mobility Management back-off timer may be sent by the MME and MME may store the back-off time per UE if a request without the low access priority indicator is rejected by the MME and if MME maintains the UE context. The MME may immediately reject any subsequent request from the UE before the stored back-off time is expired. While the Mobility Management back-off timer is running, the UE shall not initiate any NAS request for Mobility Management procedures except for Detach procedure and except for high priority access, emergency services and mobile terminated services. After any such Detach procedure, the back-off timer continues to run. While the Mobility Management back-off timer is running, the UE is allowed to perform Tracking Area Update if it is already in connected mode. If the UE receives a paging request from the MME while the Mobility Management back off timer is running, the UE shall stop the Mobility Management back-off timer and initiate the Service Request procedure or the Tracking Area Update procedure as described in clause 5.3.3.0. While the Mobility Management back-off timer is running, the UE configured with a permission for overriding low access priority is allowed to initiate the Mobility Management procedures without low access priority if the Mobility Management back-off timer was started due to a reject message received in response to a request with low access priority and the upper layers in UE request to establish a PDN connection without low access priority or the UE has an established PDN connection that is without low access priority. While the Mobility Management back-off timer is running, the UE configured with permission for sending exception reporting is allowed to initiate the Control Plane Service Request procedure for exception reporting. If the Mobility Management back-off timer was started due to a reject message received in response to a request for exception reporting, the UE shall not initiate the Control Plane Service Request procedure for exception reporting while the Mobility Management back-off timer is running. The Mobility Management back-off timer shall not impact Cell/RAT and PLMN change. Cell/RAT and TA change do not stop the Mobility Management back-off timer. The Mobility Management back-off timer shall not be a trigger for PLMN reselection. The back-off timer is stopped as defined in TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46] when a new PLMN that is not an equivalent PLMN is accessed. To avoid that large amounts of UEs initiate deferred requests (almost) simultaneously, the MME should select the Mobility Management back-off timer value so that the deferred requests are not synchronized. When the UE receives a handover command, the UE shall proceed with the handover procedure regardless of whether Mobility Management back-off timer is running. The MME should not reject Tracking Area Update procedures that are performed when the UE is already in connected mode. For idle mode inter CN node mobility, the MME may reject Tracking Area Update procedures and include a Mobility Management back off timer value in the Tracking Area Reject message. If the MME rejects Tracking Area Update request or Service request with a Mobility Management back-off timer which is larger than the sum of the UE's periodic TAU timer plus the Implicit Detach timer, the MME should adjust the mobile reachable timer and/or Implicit Detach timer such that the MME does not implicitly detach the UE while the Mobility Management back-off timer is running. NOTE: This is to minimize unneeded signalling after the Mobility Management back-off timer expires. 4.3.7.4.2.5 Group specific NAS level congestion control The group specific NAS level congestion control applies to a specific group of UEs. Each group has a group identifier assigned. A UE belongs to a group, if the corresponding group identifier is stored in the UE's subscription data in the HSS. A UE may belong to multiple groups and the MME may perform the Group specific NAS level congestion control to an UE as described below independent of whether Group specific NAS level congestion control is activated for one, multiple, or all groups the UE belongs to. The group identifier shall be stored per UE in the HSS and obtained by the MME as part of normal HSS signalling. A UE is not aware of a group subscription. The group specific NAS level congestion control may be activated for Session Management signalling, or for Mobility Management signalling, or both. The group specific NAS level congestion control is activated based on operator policies. When the group specific NAS level congestion control for Session Management signalling is active for a particular group, the MME's behaviour is similar to that in clause 4.3.7.4.2.2, with the following modifications: - MME may apply ESM congestion control to all subscribed APNs for UEs that belong to this particular group. NOTE: How the MME applies ESM congestion control to all subscribed APNs is left to Stage 3. - The MME rejects the EPS Session Management (ESM) request(s) from the UE belonging to this particular group (e.g. PDN Connectivity, or Bearer Resource Allocation Requests) with a Session Management back-off timer. When group specific NAS level congestion control for Mobility Management signalling is active for a particular group, the MME's behaviour is similar to that in clause 4.3.7.4.2.3, but applied to UEs subscribed to this particular group rather that subscribed to a particular APN. Group specific NAS level congestion control is performed at the MME based on the UE's subscription information provided by the HSS. There is no impact on the UE, and hence, UE's behaviour as described in clauses 4.3.7.4.2.2 and 4.3.7.4.2.3 does not change. 4.3.7.4.2.6 APN and group specific NAS level congestion control The APN and group specific NAS level congestion control is the intersection of APN specific NAS level congestion control and Group specific NAS level congestion control, i.e. it applies to a specific group of UEs with a particular subscribed APN. Each group of UEs has a group identifier assigned and stored in the HSS. A UE may belong to multiple groups and the MME may perform the APN and group specific NAS level congestion control to an UE as described below independent of whether the APN and group specific NAS level congestion control is activated for one, multiple or all groups the UE belongs to. The group identifier(s) shall be stored per UE in the HSS and obtained by the MME as part of normal HSS signalling. A UE is not aware of the group identifier(s) that the UE belongs to. The APN and group specific NAS level congestion control may be activated for Session Management signalling, or for Mobility Management signalling, or both. The APN and group specific NAS level congestion control is activated based on operator policies. When the APN and group specific NAS level congestion control for Session Management signalling is activated for a UE belonging to a particular group and initiating signalling to a particular APN, the MME's behaviour is similar to that in clause 4.3.7.4.2.2, with the following modifications: - The EPS Session Management (ESM) congestion control is applied to this particular APN, and for UEs belonging to this particular group, - The MME may reject ESM requests from the UEs belonging to this particular group and attaching to this particular APN (e.g. PDN Connectivity, or Bearer Resource Allocation Requests) with a Session Management back-off timer. If the UE provides no APN, then the MME uses the APN which is used in PDN GW selection procedure. - The MME may deactivate PDN connections of the UEs, belonging to this particular group and attaching to this particular APN, by sending the NAS Deactivate EPS Bearer Context Request message to the UE with a Session Management back-off timer. When the APN and group specific NAS level congestion control for Mobility Management signalling is activated for a UE belonging to a particular group and with a particular subscribed APN, the MME's behaviour is similar to that in clause 4.3.7.4.2.3, but applied to UEs with this particular subscribed APN and belonging to this particular group. APN and group specific NAS level congestion control is performed at the MME based on the UE's subscription information provided by the HSS. There is no impact on the UE, and hence, UE's behaviour described in clauses 4.3.7.4.2.2 and 4.3.7.4.2.3 does not change. 4.3.7.4.2.7 Control Plane data specific NAS level congestion control Under overload conditions the MME may restrict requests from UEs for data transmission via Control Plane CIoT EPS Optimisation. A Control Plane data back-off timer may be returned by the MME (e.g.in Attach/TAU/RAU Accept messages, Service Reject message or Service Accept message). While the Control Plane data back-off timer is running, the UE shall not initiate any data transfer via Control Plane CIoT EPS Optimisation, i.e. the UE shall not send any Control Plane Service Request with ESM Data Transport message as defined in TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46]. The MME shall store the Control Plane data back-off timer per UE and shall reject any further request (other than exception reporting and a response to paging) for data transmission via Control Plane Service Request from that UE while the Control Plane data back-off timer is still running. NOTE 1: The Control Plane data back-off timer does not affect any other mobility management or session management procedure. NOTE 2: The Control Plane data back-off timer does not apply to user plane data communication. If the UE is allowed to send exception reporting, the UE may initiate Control Plane Service Request for exception reporting even if Control Plane data back-off timer is running. The UE may respond with Control Plane Service Request without ESM Data Transport to a paging even if the Control Plane data back-off timer is running. If the MME receives a Control Plane Service Request in reponse to paging, and the MME has a Control Plane data back-off timer running for the UE, and the MME is not overloaded, and MME decides to accept the Control Plane Service Request, then the MME shall respond with Service Accept message without the Control Plane data back-off timer and stop the Control Plane data back-off timer. If the UE receives a Service Accept message without the Control Plane data back-off timer from the MME while the Control Plane data back-off timer is running, the UE shall stop the Control Plane data back-off timer. The Control Plane data back-off timer in the UE and the MME is stopped at PLMN change. If the MME receives a Control Plane Service Request with ESM Data Transport message, and decides to send the UE a Control Plane data back-off timer, the MME may decide to process the Control Plane Service Request with ESM Data Transport message, i.e. decrypt and forward the data payload, or not based on the following: - If the UE has additionally indicated in a NAS Release Assistance Information in the NAS PDU that no further Uplink or Downlink Data transmissions are expected, then the MME may process (integrity check/decipher/forward) the received Control Plane data packet, and send SERVICE ACCEPT to the UE with Control Plane data back-off timer. The UE interprets this as successful transmission of the Control Plane data packet and starts the Control Plane data back-off timer. - For all other cases, the MME may decide to not process the received control plane data packet and sends SERVICE REJECT to the UE with Control Plane data back-off timer. The UE interprets this indication as unsuccessful delivery of the control plane data packet and starts the Control Plane data back-off timer. Then MME may take into consideration whether the PDN Connection is set to Control Plane only to make the decision whether to reject the packet and send SERVICE REJECT or move the PDN connection to user plane and process the data packet. - Alternatively, if UE has not provided in the in Control Plane service request the NAS Release Assistance Information, and the EPS bearer belongs to a PDN connection not set to Control Plane only, and UE supports User Plane CIoT Optimisation (or legacy S1-U), then the MME may initiate establishment of S1-U bearer during Data Transport in Control Plane CIoT EPS Optimisation (according to the procedure defined in clause 5.3.4B.4). In this case MME may also return a Control Plane data back-off timer within the NAS message. The MME only includes the Control Plane data back-off timer if the UE has indicated support for Control Plane data back-off timer in the Attach/TAU/RAU request. NOTE 3: If the MME is overloaded or close to overload, but the UE has not indicated support for Control Plane data back-off timer, the MME can use other overload control mechanisms, e.g. mobility management back-off timer or use user plane data communication. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.7.4.2 |
5,203 | 5.5.1.3.8 Abnormal cases on the network side | The following abnormal cases can be identified: a) Lower layer failure If a lower layer failure occurs before the message REGISTRATION COMPLETE has been received from the UE and timer T3550 is running, the AMF shall abort the procedure, enter 5GMM-IDLE mode. If a new 5G-GUTI was assigned to the UE in the REGISTRATION ACCEPT message, the AMF shall consider both, the old and new 5G-GUTIs as valid until the old 5G-GUTI can be considered as invalid by the AMF. If a new TAI list was provided in the REGISTRATION ACCEPT message, both the old and new TAI lists shall also be considered valid until the old TAI list can be considered invalid by the AMF. If the old 5G-GUTI was allocated by an AMF other than the current AMF, the current AMF does not need to retain the old 5G-GUTI. Additionally, if the REGISTRATION ACCEPT message includes: 1) Negotiated PEIPS assistance information IE: i) containing a new Paging subgroup ID and the UE is previously assigned a different Paging subgroup ID then, the AMF shall consider both, the old and new Paging subgroup IDs as valid until the old Paging subgroup ID can be considered as invalid by the AMF; or NOTE 0: If the UE was not previously assigned a paging subgroup ID by the AMF, then AMF informs RAN about the new PEIPS assistance information, i.e., paging subgroup ID and it is up to RAN how to handle the old information at RAN and new information from AMF so that the paging is not missed. ii) containing no Paging subgroup ID or no Negotiated PEIPS assistance information IE, then the AMF shall delete any old Paging subgroup ID stored in the 5GMM context of the UE. 2) Negotiated WUS assistance information IE: i) containing a new UE paging probability information value and the UE is previously assigned a different UE paging probability information value then, the AMF shall consider both, the old and new UE paging probability information values as valid until the old UE paging probability information value can be considered as invalid by the AMF; or ii) containing no UE paging probability information value or no Negotiated WUS assistance information IE, then the AMF shall delete any old UE paging probability information value stored in the 5GMM context of the UE. During this period: 1) if the new 5G-GUTI is used by the UE in a subsequent message, then: i) the AMF shall consider the old 5G-GUTI as invalid and, additionally, the old TAI list as invalid if a new TAI list was provided with the new 5G-GUTI in the REGISTRATION ACCEPT message; ii) if the AMF assigns a new Paging subgroup ID to the UE in the REGISTRATION ACCEPT message, then, the AMF shall consider the new Paging subgroup ID as valid and the old Paging subgroup ID, if any, as invalid; and iii) if the AMF assigns a new UE paging probability information value in the Negotiated WUS assistance information IE to the UE in the REGISTRATION ACCEPT message, then, the AMF shall consider the new UE paging probability information value as valid and the old UE paging probability information value, if any, as invalid. 2) if the old 5G-GUTI is used by the UE in a subsequent message, the AMF may use the identification procedure followed by a generic UE configuration update procedure. If the AMF in the REGISTRATION ACCEPT message: i) assigns a new Paging subgroup ID to the UE, then, the AMF shall include the PEIPS assistance information; or ii) does not assign a Paging subgroup ID to the UE then, the AMF shall not include the PEIPS assistance information; and initiate the generic UE configuration update procedure; and 3) if the UE needs to be paged: i) if in the REGISTRATION ACCEPT message a new Paging subgroup ID in the Negotiated PEIPS assistance information IE is assigned to the UE: - that previously has no Paging subgroup ID assigned then, the AMF shall use the new Paging subgroup ID for paging the UE; - that is same as the old Paging subgroup ID then, the AMF shall use the same Paging subgroup ID for paging the UE; or - that is different than the old Paging subgroup ID then, the AMF may first use the old Paging subgroup ID followed by the new Paging subgroup ID for paging the UE. ii) if in the REGISTRATION ACCEPT message a new UE paging probability information value in the Negotiated WUS assistance information IE is assigned to the UE: - that previously has no UE paging probability information value assigned then, the AMF shall use the new UE paging probability information value for paging the UE; - that is same as the old UE paging probability information value then, the AMF shall use the same UE paging probability information value for paging the UE; or - that is different than the old UE paging probability information value then, the AMF may first use the old UE paging probability information value followed by the new UE paging probability information value for paging the UE. iii) the AMF selects the 5G-GUTI and TAI list as follows: - the AMF may first use the old 5G-S-TMSI from the old 5G-GUTI for paging within the area defined by the old TAI list for an implementation dependent number of paging attempts using the selected Paging subgroup ID or the selected UE paging probability information value in the WUS assistance information IE. If a new TAI list was provided in the REGISTRATION ACCEPT message, the new TAI list should also be used for paging. Upon response from the UE, the AMF may initiate the generic UE configuration update procedure. If the response is received from a tracking area within the old and new TAI list, the network shall initiate the generic UE configuration update procedure. If in the REGISTRATION ACCEPT message a new Paging subgroup ID was assigned to the UE that is different than the old Paging subgroup ID then the network shall initiate the generic UE configuration update procedure; and - if no response is received to the paging attempts using the old 5G-S-TMSI from the old 5G-GUTI and the old Paging subgroup ID or the old UE paging probability information value in the WUS assistance information IE, the AMF may use the new 5G-S-TMSI from the new 5G-GUTI and the new Paging subgroup ID or the new UE paging probability information value in the WUS assistance information IE, if any, for paging, for an implementation dependent number of paging attempts. In this case, if a new TAI list was provided with the new 5G-GUTI in the REGISTRATION ACCEPT message, the new TAI list shall be used instead of the old TAI list. b) Protocol error. If the REGISTRATION REQUEST message has been received with a protocol error, the AMF shall return a REGISTRATION REJECT message with one of the following 5GMM cause values: #96 invalid mandatory information; #99 information element non-existent or not implemented; #100 conditional IE error; or #111 protocol error, unspecified. c) T3550 time out. On the first expiry of the timer, the AMF shall retransmit the REGISTRATION ACCEPT message and shall reset and restart timer T3550. The retransmission is performed four times, i.e. on the fifth expiry of timer T3550, the registration procedure for mobility and periodic registration update procedure is aborted. During this period the AMF acts as described for case a) above. d) REGISTRATION REQUEST with 5GS registration type IE set to "mobility registration updating" or "periodic registration updating" received after the REGISTRATION ACCEPT message has been sent and before the REGISTRATION COMPLETE message is received, if the REGISTRATION COMPLETE message is expected. 1) If one or more of the information elements in the REGISTRATION REQUEST message differ from the ones received within the previous REGISTRATION REQUEST message, the previously initiated registration procedure for mobility and periodic registration update shall be aborted if the REGISTRATION COMPLETE message has not been received and the new registration procedure for mobility and periodic registration update shall be progressed; or 2) if the information elements do not differ, then the REGISTRATION ACCEPT message shall be resent and timer T3550 shall be restarted. In that case, the retransmission counter related to timer T3550 is not incremented. e) More than one REGISTRATION REQUEST message with 5GS registration type IE set to "mobility registration updating" or "periodic registration updating" received and neither REGISTRATION ACCEPT message nor REGISTRATION REJECT message has been sent. 1) If one or more of the information elements in the REGISTRATION REQUEST message differs from the ones received within the previous REGISTRATION REQUEST message, the previously initiated registration procedure for mobility and periodic registration update shall be aborted and the new registration procedure for mobility and periodic registration update shall be progressed; or 2) if the information elements do not differ, then the network shall continue with the previous registration procedure for mobility and periodic registration update and shall not treat any further this REGISTRATION REQUEST message. f) Lower layers indication of non-delivered NAS PDU due to handover. If the REGISTRATION ACCEPT message or REGISTRATION REJECT message could not be delivered due to an intra AMF handover and the target TA is included in the TAI list, then upon successful completion of the intra AMF handover the AMF shall retransmit the REGISTRATION ACCEPT message or REGISTRATION REJECT message. If a failure of the handover procedure is reported by the lower layer and the N1 NAS signalling connection exists, the AMF shall retransmit the REGISTRATION ACCEPT message or REGISTRATION REJECT message. g) DEREGISTRATION REQUEST message received before REGISTRATION COMPLETE message is received, if the REGISTRATION COMPLETE message is expected. If the De-registration type IE is set to "switch off": The AMF shall abort the signalling for the registration procedure for mobility and periodic registration update towards the UE and shall progress the de-registration procedure as described in subclause 5.5.2.2. NOTE 1: Internally in the AMF, before processing the de-registration request, the AMF can perform the necessary signalling procedures for the registration procedure for mobility and periodic registration update before progressing the de-registration procedure. If the De-registration type IE is set to other type than "switch off": The AMF shall proceed with registration procedure for mobility and periodic registration update and shall progress the de-registration procedure after successful completion of the registration procedure for mobility and periodic registration update. h) If the REGISTRATION REQUEST message with 5GS registration type IE indicating "periodic registration updating" is received by the new AMF which does not have the 5GMM context data related to the subscription, the new AMF may send the REGISTRATION REJECT message with 5GMM cause #10 "implicitly de-registered". i) Based on operator policy, if the mobility and periodic registration update request from a UE not supporting CAG is rejected due to CAG restrictions, the network shall reject the mobility and periodic registration update request with a 5GMM cause value other than the 5GMM cause #76 (Not authorized for this CAG or authorized for CAG cells only). NOTE 2: 5GMM cause #7 (5GS services not allowed), 5GMM cause #11 (PLMN not allowed), 5GMM cause #27 (N1 mode not allowed), 5GMM cause #73 (Serving network not authorized) can be used depending on the subscription of the UE and whether the UE roams or not. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.1.3.8 |
5,204 | 4.2.2.7 Service State, RECEIVING GROUP CALL (NORMAL SERVICE) | Only applicable for mobile stations supporting VGCS listening or VBS listening: When in state MM IDLE and service state RECEIVING GROUP CALL (NORMAL SERVICE), the mobile station shall: - perform normal location updating when a new location area is entered; - perform location updating procedure at expiry of timer T3211 or T3213; - perform periodic updating at expiration of timer T3212; - perform IMSI detach; - support requests from the GCC or BCC layers; - indicate notifications or paging information to the GCC or BCC layer; - respond to notification if the GCC or BCC sublayer requests the reception of a voice group or broadcast call for which no channel description has been received in the notification by the RR sublayer; - request the RR sublayer to receive another voice group or broadcast call if the GCC or BCC sublayer requests the reception of a voice group or broadcast call for which a channel description has been received in the notification by the RR sublayer. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.2.2.7 |
5,205 | 5.2.2.4.4 Namf_MT_EnableGroupReachability service operation | Service operation name: Namf_MT_EnableGroupReachability. Description: NF Service Consumer use this service operation to request paging towards a group of UEs. Inputs, Required: Multicast Session ID, UE list, Associated PDU Session ID list, UE reachability Notification Address. Inputs, Optional: MBS service area. Outputs, Required: None. Outputs, Optional: List of UEs in connected state (out of the input list). This service operation is used in 5G MBS as specified in TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [78]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.2.4.4 |
5,206 | 4.6.2 Mobility management aspects 4.6.2.1 General | Upon registration to a PLMN or SNPN (except for the registration procedure for periodic registration update, the initial registration for onboarding services in SNPN, and the registration procedure for mobility registration update when registered for onboarding services in SNPN), the UE shall send to the AMF the requested NSSAI which includes one or more S-NSSAIs of the allowed NSSAI for the PLMN or SNPN or the configured NSSAI for the PLMN or SNPN and corresponds to the network slice(s) to which the UE intends to register with, if: a) the UE has a configured NSSAI for the current PLMN or SNPN; b) the UE has an allowed NSSAI for the current PLMN or SNPN; or c) the UE has neither allowed NSSAI for the current PLMN or SNPN nor configured NSSAI for the current PLMN or SNPN and has a default configured NSSAI. In this case the UE indicates to the AMF that the requested NSSAI is created from the default configured NSSAI. In roaming scenarios, if the mapped S-NSSAI(s) associated to the allowed NSSAI or the configured NSSAI are missing, the UE shall locally set the mapped S-NSSAI to the same value as the received S-NSSAI. Additionally, if the UE receives a Rejected NSSAI IE or an Extended rejected NSSAI IE without associated mapped S-NSSAI(s), and the rejected NSSAI is different from the rejected NSSAI for the failed or revoked NSSAA, the UE shall locally set the mapped S-NSSAI(s) to the same value as the received S-NSSAI. NOTE 1: The above occurs only when the UE is roaming and the AMF compliant with earlier versions of the specification omits providing to the UE a mapped S-NSSAI for one or more S-NSSAIs in, e.g., the allowed NSSAI or configured NSSAI. Other than S-NSSAIs contained in the NSSAIs described above, the requested NSSAI can be formed based on the S-NSSAI(s) available in the UE (see subclause 5.5.1.3.2 for further details). In roaming scenarios, the UE shall also provide the mapped S-NSSAI(s) for the requested NSSAI. NOTE 2: If the UE did not receive a mapped S-NSSAI for one or more S-NSSAIs in the allowed NSSAI or configured NSSAI, the UE still uses the S-NSSAI as received from the serving network (i.e., without the locally set mapped S-NSSAI) in any NAS message. The AMF verifies if the requested NSSAI is permitted based on the subscribed S-NSSAIs in the UE subscription and, in roaming scenarios the mapped S-NSSAI(s) provided by the UE, and if so then the AMF shall provide the UE with the allowed NSSAI for the PLMN or SNPN, and shall also provide the UE with the mapped S-NSSAI(s) for the allowed NSSAI for the PLMN or SNPN. Additionally, if the AMF allows one or more subscribed S-NSSAIs for the UE, the AMF may include the allowed subscribed S-NSSAI(s) in the allowed NSSAI in the REGISTRATION ACCEPT message. The AMF shall ensure that there are not two or more S-NSSAIs of the allowed NSSAI which are mapped to the same S-NSSAI of the HPLMN or the subscribed SNPN. If a) all the S-NSSAIs included in the requested NSSAI are rejected, or the requested NSSAI was not included by the UE; b) all default S-NSSAIs are not allowed; and c) the UE is neither registering nor registered for onboarding services in SNPN and the UE is neither registering nor registered for emergency services; then the AMF may reject the registration request (see subclauses 5.5.1.2.5 and 5.5.1.3.5 for further details). In roaming scenarios, if the mapped S-NSSAI(s) associated to requested NSSAI are missing, the AMF shall locally set the mapped S-NSSAI to the same value as the received S-NSSAI. NOTE 3: In roaming scenarios, when the UE is compliant with earlier versions of the specification or when the serving network does not provide a mapped S-NSSAI for one or more S-NSSAIs in the allowed NSSAI or configured NSSAI, the UE can omit a mapped S-NSSAI for one or more S-NSSAIs in requested NSSAI. The set of network slice(s) for a UE can be changed at any time while the UE is registered to a PLMN or SNPN, and the change may be initiated by the network or the UE. In this case, the allowed NSSAI and associated registration area may be changed during the registration procedure or the generic UE configuration update procedure. The configured NSSAI and the rejected NSSAI may be changed during the registration procedure or the generic UE configuration update procedure. The default configured NSSAI may be changed by sending a UE parameters update transparent container to the UE during the NAS transport procedure. The pending NSSAI may be changed during the registration procedure. In addition, using the generic UE configuration update procedure, the network may trigger the registration procedure in order to update the allowed NSSAI. The UE in NB-N1 mode does not include the requested NSSAI during the registration procedure if the 5GS registration type IE indicates "mobility registration updating", procedure is not initiated to change the slice(s) that the UE is currently registered to, and the UE is still in the current registration area. The AMF does not include the allowed NSSAI during a registration procedure with the 5GS registration type IE indicating "mobility registration updating" for the UE in NB-N1 mode, except if the allowed NSSAI has changed for the UE. The UE does not include the requested NSSAI during the registration procedure if the 5GS registration type IE indicates "SNPN onboarding registration" or the UE is registered for onboarding services in SNPN. The AMF does not include the allowed NSSAI during a registration procedure with the 5GS registration type IE indicating "SNPN onboarding registration" or during a registration procedure when the UE is registered for onboarding services in SNPN. The UE considers the last received allowed NSSAI as valid until the UE receives a new allowed NSSAI. | 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.6.2 |
5,207 | 8.89 Temporary Mobile Group Identity (TMGI) | The TMGI contains the Temporary Mobile Group Identity allocated to the MBMS Bearer Service. The BM-SC always includes the MCC and MNC when allocating the TMGI, see 3GPP TS 29.061[ Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) ] [38]. It is coded as specified in Figure 8.89-1. Figure 8.89-1: TMGI Octets 5 to 10 shall be encoded as octets 3 to octet 8 in the figure 10.5.154 of 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [5]. | 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.89 |
5,208 | 4.2.7.3 AMF Failure or Planned Maintenance handling procedure | For UE(s) in CM-CONNECTED state: - If AMF failure is detected by 5G-AN, all NGAP UE TNLA binding for UEs served by that AMF are released. - If AMF becomes unavailable due to planned maintenance, the AMF notifies the 5G-AN about the unavailable GUAMI(s) and provides optionally a target AMF Name corresponding to each unavailable GUAMI. The 5G-AN releases all NGAP UE TNLA binding of the UEs related to the indicated unavailable GUAMI(s) unless the notification from the AMF includes an indicator that the AMF will rebind or release the NGAP UE TNLA binding on a per UE-basis. In that case, if 5G-AN supports, the 5G-AN waits the release until the timer expires so that the AMF may release or rebind the N2AP UE-TNLA binding on per UE-basis. - For the release NGAP TNLA binding, the affected UE is kept in CM-CONNECTED state and the corresponding N3 interface is also kept. For UE(s) in CM-IDLE state, when it subsequently returns from CM-IDLE state and the 5G-AN receives an initial NAS message with a 5G S-TMSI or GUAMI, the 5G-AN uses 5G S-TMSI or GUAMI to select the target AMF, the 5G-AN forwards N2 message. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.7.3 |
5,209 | 16.5.4 Fallback | RAT fallback towards E-UTRA connected to 5GC is performed when NR does not support Emergency Services and System fallback towards E-UTRA connected to EPS is performed when 5GC does not support Emergency Services. Depending on factors such as CN interface availability, network configuration and radio conditions, the fallback procedure results in either CONNECTED state mobility (handover procedure) or IDLE state mobility (redirection) - see TS 23.501[ System architecture for the 5G System (5GS) ] [3] and TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.5.4 |
5,210 | – UEInformationRequestSidelink | The UEInformationRequestSidelink message is used to transfer UE information in sidelink, e.g. the end-to-end QoS information for L2 U2U Relay operation. Signalling radio bearer: SL-SRB3 RLC-SAP: AM Logical channel: SCCH Direction: L2 U2U Remote UE to L2 U2U Relay UE UEInformationRequestSidelink message -- ASN1START -- TAG-UEINFORMATIONREQUESTSIDELINK-START UEInformationRequestSidelink-r18 ::= SEQUENCE { rrc-TransactionIdentifier-r18 RRC-TransactionIdentifier, criticalExtensions CHOICE { ueInformationRequestSidelink-r18 UEInformationRequestSidelink-r18-IEs, criticalExtensionsFuture SEQUENCE {} } } UEInformationRequestSidelink-r18-IEs ::= SEQUENCE { sl-E2E-QoS-ConnectionListPC5-r18 SEQUENCE (SIZE (1.. maxNrofSL-Dest-r16)) OF SL-E2E-QoS-ConnectionPC5-r18 OPTIONAL, -- Need N lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } SL-E2E-QoS-ConnectionPC5-r18 ::= SEQUENCE { sl-DestinationIdentityRemoteUE-r18 SL-DestinationIdentity-r16, sl-QoS-InfoList-r18 SEQUENCE (SIZE (1..maxNrofSL-QFIsPerDest-r16)) OF SL-QoS-Info-r16 } -- TAG-UEINFORMATIONREQUESTSIDELINK-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,211 | – ERedCapParameters | The IE ERedCapParameters is used to indicate the UE capabilities supported by eRedCap UEs. ERedCapParameters information element -- ASN1START -- TAG-EREDCAPPARAMETERS-START ERedCapParameters-r18::= SEQUENCE { -- R1 48-1: eRedCap UE with reduced peak data rate and reduced baseband bandwidth in FR1 supportOfERedCap-r18 ENUMERATED {supported}, -- R1 48-2: eRedCap UE with reduced peak data rate without reduced baseband bandwidth in FR1 eRedCapNotReducedBB-BW-r18 ENUMERATED {supported} OPTIONAL, eRedCapIgnoreCapabilityFiltering-r18 ENUMERATED {supported} OPTIONAL } -- TAG-EREDCAPPARAMETERS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,212 | 8.22.3 Intra-DU direct path addition on top of indirect path | The signaling flow for intra-DU direct path addition is shown in Fig. 8.22.3-1. This procedure is only applicable to the MP Remote UE using PC5 link. Figure 8.22.3-1: Signalling procedure of intra-DU direct path addition on top of indirect path 1. The Uu measurement configuration and measurement report signalling are performed between MP Remote UE and gNB-CU to evaluate both relay link measurement and Uu link measurement. The MP Remote UE may report Uu measurement results of neighboring cells and one or multiple candidate MP Relay UE(s). 2. The gNB-CU decides to add the direct path to MP Remote UE under the same gNB-DU. 3. The gNB-CU sends the UE CONTEXT MODIFICATION REQUEST message for the MP Remote UE to the gNB-DU, which contains at least the direct path configuration. 4. The gNB-DU responds to the gNB-CU with a UE CONTEXT MODIFICATION RESPONSE message. 5. The gNB-CU sends an RRCReconfiguration message to the MP Relay UE to update the indirect path configuration if necessary. 6. The gNB-CU sends the DL RRC MESSAGE TRANSFER message for MP Remote UE by including the RRCReconfiguration message to the gNB-DU. The contents in the RRCReconfiguration message may include at least direct path addition configuration, RLC channel configuration, bearer mapping and the associated radio bearer(s). 7. The gNB-DU sends the RRCReconfiguration message to the MP Remote UE. 8. The MP Remote UE performs random access procedure at the gNB-DU. 9. The MP Remote UE sends the RRCReconfigurationComplete message to the gNB-DU via direct path in order to complete the direct path addition procedure. 9a. In case the SRB1 with duplication is configured, the RRCReconfigurationComplete message is also sent to the gNB-DU via indirect path. 10/10a. The gNB-DU sends the UL RRC MESSAGE TRANSFER message to gNB-CU by including the RRCReconfigurationComplete message. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.22.3 |
5,213 | 21.3 QoE Measurement Continuity for Mobility | QoE measurement collection continuity for intra-system intra-RAT handover is supported, with the Area Scope parameters configured by the OAM, where the network is responsible for keeping track of whether the UE is inside or outside the area scope. A UE continues an ongoing QoE measurement even if it leaves the area scope, unless the network indicates to the UE to release the application layer measurement configuration. For the handover, the source gNB may transmit the information related to one or more application layer measurement configurations of the UE to the target gNB via XnAP or NGAP. For signalling-based QoE, the service type indication, QoE reference, and, optionally, the MCE IP address, measurement configuration application layer ID, MDT alignment information, area scope, slice support list for QMC, available RAN visible QoE metrics and measurement status are passed to the target gNB. For management-based QoE, the service type indication, measurement configuration application layer ID, the MCE IP address and QoE measurement status are passed to the target gNB. For RRC_INACTIVE state mobility, QoE measurement configuration(s) of a specific UE can be retrieved from the gNB hosting the UE context when it resumes to the RRC_CONNECTED state. For signalling-based QoE, at handover to a target gNB that supports QoE measurement collection, the target gNB decides which of the application layer measurement configurations should be kept or released, e.g., based on application layer measurement configuration information received from the source gNB in Xn/NG signalling. The continuity of QoE measurement configuration and reporting in NR-DC scenario is supported as specified in TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [21]. For QoE sessions pertaining to data flows received via MBS broadcast, QoE measurement collection may continue during the RRC_INACTIVE and RRC_IDLE. Upon UE's transition from RRC_IDLE to RRC_CONNECTED, the gNB serving the UE should ensure that it does not release an already configured signalling-based QoE measurement configuration for the sake of configuring a new management-based QoE measurement configuration. QoE measurements for ongoing sessions should be continued when switching between MBS multicast and unicast transmission modes. When the UE resumes the connection with a gNB that does not support QoE, the UE releases all application layer measurement configurations. QoE measurement collection continuity for intra-system inter-RAT handover is supported. For the handover from NR to LTE, only one QoE measurement can be continued when the UE connects to the target LTE node. The source gNB decides which QoE measurement to keep and sends the information about this QoE measurement to the target ng-eNB. For intra-5GC handover from E-UTRA to NR, the UE releases the LTE QoE configuration if received from the source RAT and the UE applies NR QoE configuration(s) if received from the target RAT. For intra-5GC handover from NR to E-UTRA, the UE releases all NR QoE configuration(s) if received from the source RAT, and the UE applies the LTE QoE configuration if received from the target RAT. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 21.3 |
5,214 | 6.2.1 Description | A key feature of 5G is support for UEs with different mobility management needs. 5G will support UEs with a range of mobility management needs, including UEs that are - stationary during their entire usable life (e.g. sensors embedded in infrastructure), - stationary during active periods, but nomadic between activations (e.g. fixed access), - mobile within a constrained and well-defined space (e.g. in a factory), and - fully mobile. Moreover, some applications require the network to ensure seamless mobility of a UE so that mobility is hidden from the application layer to avoid interruptions in service delivery while other applications have application specific means to ensure service continuity. But these other applications can still require the network to minimize interruption time to ensure that their application-specific means to ensure service continuity work effectively. With the ever-increasing multimedia broadband data volumes, it is also important to enable the offloading of IP traffic from the 5G network onto traditional IP routing networks via an IP anchor node close to the network edge. As the UE moves, changing the IP anchor node can be needed in order to reduce the traffic load in the system, reduce end-to-end latency and provide a better user experience. The flexible nature of a 5G system will support different mobility management methods that minimize signalling overhead and optimize access for these different types of UEs. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.2.1 |
5,215 | 5.7.3.7 Maximum Data Burst Volume | Each GBR QoS Flow with Delay-critical resource type shall be associated with a Maximum Data Burst Volume (MDBV). MDBV denotes the largest amount of data that the 5G-AN is required to serve within a period of 5G-AN PDB. Every standardized 5QI (of Delay-critical GBR resource type) is associated with a default value for the MDBV (specified in QoS characteristics Table 5.7.4.1). The MDBV may also be signalled together with a standardized 5QI to the (R)AN, and if it is received, it shall be used instead of the default value. The MDBV may also be signalled together with a pre-configured 5QI to the (R)AN, and if it is received, it shall be used instead of the pre-configured value. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.3.7 |
5,216 | 6.27.2 Requirements | The 5G system shall provide 5G positioning services in compliance with regulatory requirements. NOTE 1: example of regulatory requirements encompasses requirements on emergency calls (e.g. e911), reliability and safety requirement (RAMS) applicable to some use cases and verticals, implementation of Priority, Precedence, Preemption (PPP) mechanisms to ensure sufficient reliability metrics are reached. The 5G system shall provide different 5G positioning services, supported by different single and hybrid positioning methods to supply absolute and relative positioning. NOTE 2: hybrid positioning methods include both the combination of 3GPP positioning technologies and the combination of 3GPP positioning technologies with non-3GPP positioning technologies such as, GNSS (e.g. Beidou, Galileo, GPS, Glonass), Network-based Assisted GNSS and High-Accuracy GNSS, Terrestrial Beacon Systems, dead-reckoning sensors (e.g. IMU, barometer), WLAN/Bluetooth-based positioning. The 5G system shall enable an MCX UE to use the 5G positioning services to determine its position with the associated uncertainty/confidence of the position, on request, triggered by an event or periodically. The 5G System shall be able to provide the 5G positioning services in case of roaming. The 5G system shall support mechanisms to determine the UE’s position-related data for period when the UE is outside the coverage of 3GPP RAT-dependent positioning technologies but within the 5G positioning service area (e.g. within the coverage of satellite access). The 5G system shall be able to make the position-related data available to an application or to an application server existing within the 5G network, external to the 5G network, or in the User Equipment. NOTE 3: the position service latency can be tailored to the use cases. The 5G system shall be able to manage and log position-related data in compliance with applicable traceability, authentication and security regulatory requirements. The 5G network shall be able to request the UE to provide its position-related-data on request—together with the accuracy of its position—triggered by an event or periodically and to request the UE to stop providing its position-related data periodically. NOTE 4: This requirement does not preclude whether the position is computed in the UE or elsewhere in the 5G System (e.g. core network). The 5G system shall support mechanisms to configure dynamically the update rate of the position-related data to fulfil different performances (e.g. power consumption, position service latency) or different location modes. NOTE 5: for example, the 5G System needs to be able to request the UE to provide its location periodically with an update rate ranging from one location every [1 s to 10 s] in location normal mode to one location every [30 s to 300 s, or more] in location power saving mode. The 5G System needs to allow UEs to sleep for extended periods (e.g. one week), without requiring the UE to update its position data. The 5G system shall allow the UE to trigger a different update rate of the position-related data based on whether the UE is moving or not. The 5G system shall be able to determine the position-related data of the 5G positioning services with any update rate ranging from one set of position-related data every 0,1 s to one set of position-related data every month. NOTE 6: the position service latency can be tailored to the use cases. The 5G System shall be able to negotiate the positioning methods according to the operator's policy or the application’s requirements or the user's preferences and shall support mechanisms to allow the network or the UE to trigger this negotiation. The 5G system shall supply a method for the operator to configure and manage different positioning services for different users. The 5G system shall be able to determine the reliability, and the uncertainty or confidence level, of the position-related data. The 5G system shall be able to access to the positioning methods used for calculating the position-related data and to the associated uncertainty/confidence indicators. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.27.2 |
5,217 | 7.2 Group Call Area Identification | Grouping of cells into specific group call areas occurs in support of both the Voice Group Call Service and the Voice Broadcast Service. These service areas are known by a "Group Call Area Identity" (Group Call Area Id). No restrictions are placed on what cells may be grouped into a given group call area. The Group Call Area ID is a number uniquely assigned to a group call area in one network and with a maximum value depending on the composition of the voice group call reference or voice broadcast reference defined under 7.3. The formats of the Group Call Area ID for VGCS and the Group Call Area ID for VBS are identical. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 7.2 |
5,218 | F.1 QoS monitoring for assurance | This Clause discusses how QoS monitoring information can be used for assurance purposes. For background information on assurance see [19] and appendix A.3 in [20]. Assurance consists of four major steps (see Figure F.1-1 and [18]): Customer's QoS requirements These state the level of quality required by the customer of a service. This information is divulged to the provider. Service provider's offerings of QoS (or planned/targeted QoS) This is a statement of the level of quality expected to be offered to the customer by the service provider. QoS achieved/delivered This is the level of quality achieved and delivered to the customer. Monitoring information is divulged to the customer. Customer rating of QoS The customer can compare the QoS achieved by the provider with the QoS requirements (see above) and its own experience of the QoS. This is a crucial step for establishing assurance about the fulfillment of the customer's requirements. Figure F.1-1: QoS assurance by use of QoS monitoring information NOTE: This Figure is based on the trust model in reference [18]. The start time and the duration of the QoS monitoring is specified in the parameter observation time interval, which is exchanged between the customer, for instance an application consuming a communication service, and the provider (for instance a private 5G network providing a communication service). The observation time interval is the time interval during which a series of measurements is conducted. In the context of QoS monitoring, these are the measurements necessary for assessing the QoS of communication services, for instance the measurement of end-to-end latencies. Examples of parameters to be monitored by the provider are given in annex C in reference [36]. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | F.1 |
5,219 | 5.7.3.6 Averaging Window | Each GBR QoS Flow shall be associated with an Averaging window. The Averaging window represents the duration over which the GFBR and MFBR shall be calculated (e.g. in the (R)AN, UPF, UE). Every standardized 5QI (of GBR and Delay-critical GBR resource type) is associated with a default value for the Averaging window (specified in QoS characteristics Table 5.7.4.1). The averaging window may also be signalled together with a standardized 5QI to the (R)AN and UPF, and if it is received, it shall be used instead of the default value. The Averaging window may also be signalled together with a pre-configured 5QI to the (R)AN, and if it is received, it shall be used instead of the pre-configured value. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.3.6 |
5,220 | 5.5.1.1.2 X2-based handover without Serving GW relocation | This procedure is used to hand over a UE from a source eNodeB to a target eNodeB using X2 when the MME is unchanged and decides that the Serving GW is also unchanged. The presence of IP connectivity between the Serving GW and the source eNodeB, as well as between the Serving GW and the target eNodeB is assumed. Figure 5.5.1.1.2-1: X2-based handover without Serving GW relocation NOTE 1: For a PMIP-based S5/S8, procedure steps (A) are defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. 1a. If the PLMN has configured secondary RAT usage reporting, the source eNodeB during the handover execution phase may provide RAN usage data Report (Secondary RAT usage data, handover flag) to the MME. The source eNodeB shall provide this only when the Target eNodeB has confirmed handover over X2 interface (see TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5] and the source eNodeB has sent a HO command to the UE). The handover flag indicates to the MME that it should buffer the usage data report before forwarding it to the Serving GW. 1b. The target eNodeB sends a Path Switch Request message to MME to inform that the UE has changed cell, including the TAI+ECGI of the target cell and the list of EPS bearers to be switched. If Dual Connectivity is activated for the UE, the PSCell ID shall be included in the Path Switch Request message. If the target cell is a CSG cell, the target eNodeB includes the CSG ID of the target cell in Path Switch Request message. If the target cell is in hybrid mode, it includes the CSG ID of the target cell and CSG Access Mode set to "hybrid" in the Path Switch Request message. Moreover, the Path Switch Request message contains the CSG Membership Status IE if the hybrid cell accessed by the UE has a different CSG from the source cell or the source cell does not have a CSG ID. The MME determines the CSG membership based on the CSG ID and the target PLMN id received from the target eNodeB.The MME updates the User CSG information based on the CSG ID and CSG Access Mode received from the target eNodeB and CSG membership if one of the parameters has changed. For SIPTO at the Local Network with stand-alone GW architecture, the target eNodeB shall include the Local Home Network ID of the target cell in the Path Switch Request message. The MME determines that the Serving GW can continue to serve the UE. 2. The MME sends a Modify Bearer Request (eNodeB address(es) and TEIDs for downlink user plane for the accepted EPS bearers, ISR Activated, Secondary RAT usage data, User Location Information, PSCell ID) message per PDN connection to the Serving GW for each PDN connection where the default bearer has been accepted by the target eNodeB. If the PDN GW requested location information change reporting, the MME also includes the User Location Information IE in this message if it is different compared to the previously sent information. If the UE Time Zone has changed, the MME includes the UE Time Zone IE in this message. If the Serving Network has changed, the MME includes the new Serving Network IE in this message. If ISR was activated before this procedure, MME should maintain ISR. The UE is informed about the ISR status in the Tracking Area Update procedure. If the Serving GW supports Modify Access Bearers Request procedure and if there is no need for the SGW to send the signalling to the PDN GW, the MME may send Modify Access Bearers Request (eNodeB address(es) and TEIDs for downlink user plane for the accepted EPS bearers, ISR Activated) per UE to the Serving GW to optimise the signalling. The MME includes the Secondary RAT usage data if the MME received it from the source eNodeB in step 1a. The MME includes the PSCell ID if the MME received it from the target eNodeB in step 1b. If the PDN GW requested UE's User CSG information (determined from the UE context), the MME includes the User CSG Information IE in this message if the User CSG Information has changed. The MME uses the list of EPS bearers to be switched, received in step 1, to determine whether any dedicated EPS bearers in the UE context have not been accepted by the target eNodeB. The MME releases the non-accepted dedicated bearers by triggering the bearer release procedure as specified in clause 5.4.4.2. If the Serving GW receives a DL packet for a non-accepted bearer, the Serving GW drops the DL packet and does not send a Downlink Data Notification to the MME. If the default bearer of a PDN connection has not been accepted by the target eNodeB and there are multiple PDN connections active, the MME shall consider all bearers of that PDN connection as failed and release that PDN connection by triggering the MME requested PDN disconnection procedure specified in clause 5.10.3. If none of the default EPS bearers have been accepted by the target eNodeB or there is a LIPA PDN connection that has not been released, the MME shall act as specified in step 6. 3. If the Serving GW has received the User Location Information IE and/or the UE Time Zone IE and/or the Serving Network IE and/or User CSG Information IE from the MME in step 2 the Serving GW informs the PDN GW(s) about this information that e.g. can be used for charging, by sending the message Modify Bearer Request (Serving GW Address and TEID, User Location Information IE and/or UE Time Zone IE and/or Serving Network IE and/or User CSG Information IE, Secondary RAT usage data) per PDN connection to the PDN GW(s) concerned. The Serving GW shall return a Modify Bearer Response (Serving GW address and TEID for uplink traffic) message to the MME as a response to a Modify Bearer Request message, or a Modify Access Bearers Response (Serving GW address and TEID for uplink traffic) as a response to a Modify Access Bearers Request message. If the Serving GW cannot serve the MME Request in the Modify Access Bearers Request message without S5/S8 signalling or without corresponding Gxc signalling when PMIP is used over the S5/S8 interface, it shall respond to the MME with indicating that the modifications are not limited to S1-U bearers, and the MME shall repeat its request using Modify Bearer Request message per PDN connection. The Serving GW forwards the Secondary RAT usage data to the PDN GW, if the Serving GW received it in step 2 and if PGW secondary RAT usage data reporting is active. 4. The Serving GW starts sending downlink packets to the target eNodeB using the newly received address and TEIDs. A Modify Bearer Response message is sent back to the MME. 5. In order to assist the reordering function in the target eNodeB, the Serving GW shall send one or more "end marker" packets on the old path immediately after switching the path as defined in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5], clause 10.1.2.2. 6. The MME confirms the Path Switch Request message with the Path Switch Request Ack message. If the UE-AMBR is changed, e.g. all the EPS bearers which are associated to the same APN are rejected in the target eNodeB, the MME shall provide the updated value of UE-AMBR to the target eNodeB in the Path Switch Request Ack message. If the CSG membership status was included in the Path Switch Request message, the MME shall include its verified CSG membership status in the Path Switch Request Ack message. If some EPS bearers have not been switched successfully in the core network, the MME shall indicate in the Path Switch Request Ack message which bearers failed to be established (see more detail in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]) and for dedicated bearers initiate the bearer release procedure as specified in clause 5.4.4.2 to release the core network resources of the failed dedicated EPS bearers. The target eNodeB shall delete the corresponding bearer contexts when it is informed that bearers have not been established in the core network. If none of the default EPS bearers have been switched successfully in the core network or if they have not been accepted by the target eNodeB or the LIPA PDN connection has not been released, the MME shall send a Path Switch Request Failure message (see more detail in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]) to the target eNodeB. The MME performs explicit detach of the UE as described in the MME initiated detach procedure of clause 5.3.8.3. If the MME supports RACS as defined in clause 5.11.3a and has UE Radio Capability ID stored in the UE's context it includes it in the Path Switch Request Ack message, if the target eNodeB supports RACS. 7. By sending Release Resource the target eNodeB informs success of the handover to source eNodeB and triggers the release of resources. This step is specified in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. 8. The UE initiates a Tracking Area Update procedure when one of the conditions listed in clause "Triggers for tracking area update" applies. If ISR is activated for the UE when the MME receives the Tracking Area Update Request, the MME should maintain ISR by indicating ISR Activated in the Tracking Area Update Accept message. NOTE 2: It is only a subset of the TA update procedure that is performed by the MME, since the UE is in ECM-CONNECTED state and the MME is not changed. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.5.1.1.2 |
5,221 | 4.3.2.14.1 PDU session with integrity protection | At 5G-SRVCC from NG-RAN to UTRAN handover of a PDU session for which the "null integrity protection algorithm" 5G-IA0 has not been used (see 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [126]), when the MS receives the command to perform handover, the MS shall derive a new KASME_SRVCC from KAMF as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [170]. The MS shall set the CKSN of the derived UMTS security context to the value of the eKSI associated with the new KASME_SRVCC and derive security keys CKSRVCC and IKSRVCC from the new KASME_SRVCC as specified in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [123]. The MS shall apply these derived security keys, handle the STARTCS value as specified in 3GPP TS 25.331[ None ] [23c] and replace an already established UMTS security context for the CS domain, if any, in the USIM, when the 5G-SRVCC handover from NG-RAN to UTRAN has been completed successfully. The network shall replace an already established UMTS security context for the CS domain, if any, when the 5G-SRVCC handover from NG-RAN to UTRAN has been completed successfully. If the 5G-SRVCC handover from NG-RAN to UTRAN has not been completed successfully, the MS and the network shall delete the new derived UMTS security context for the CS domain. Additionally, the network shall delete the already established UMTS security context for the CS domain, if the CKSN of the already established UMTS security context is equal to the CKSN of the new derived UMTS security context for the CS domain. | 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.14.1 |
5,222 | 5.8.3.3 Actions related to transmission of SidelinkUEInformationNR message | The UE shall set the contents of the SidelinkUEInformationNR message as follows: 1> if the UE initiates the procedure to indicate it is (no more) interested to receive NR sidelink communication/positioning; or 1> if the UE initiates the procedure to request (configuration/ release) of NR sidelink communication/positioning transmission resources or to report to the network that a sidelink radio link failure, sidelink RRC reconfiguration failure or sidelink carrier failure has been declared; or 1> if the UE initiates the procedure to report to the network the sidelink DRX configuration for NR sidelink unicast reception; or 1> if the UE initiates the procedure to report to the network the sidelink DRX assistance information or the sidelink DRX configuration reject information for NR sidelink unicast transmission; or 1> if the UE initiates the procedure to report to the network the Destination Layer-2 ID and QoS profile(s) associated with its interested service(s) that sidelink DRX is applied for NR sidelink groupcast or broadcast reception; or 1> if the UE initiates the procedure to report to the network the Destination Layer-2 ID and the sidelink DRX on/off indication for the corresponding destination for NR sidelink groupcast transmission; or 1> if the UE initiates the procedure to indicate it is (no more) interested to receive NR sidelink discovery messages; or 1> if the UE initiates the procedure to request (configuration/ release) of NR sidelink discovery messages transmission resources; or 1> if the UE initiates the procedure to request (configuration/ release) of NR sidelink U2N or U2U relay communication transmission resources or report other parameters related to U2N relay operation (i.e. UE includes all concerned information, irrespective of what triggered the procedure): 2> if SIB12 including sl-ConfigCommonNR is provided by the PCell: 3> if configured by upper layers to receive NR sidelink communication: 4> include sl-RxInterestedFreqList and set it to the frequency for NR sidelink communication reception; 3> if configured by upper layers to transmit non-relay NR sidelink communication and/or to transmit NR sidelink relay communication; or 3> if configured by upper layers to transmit NR sidelink L3 U2U relay communication [and SIB12 includes FFS gNB capability indication]: 4> include sl-TxResourceReqList and set its fields (if needed) as follows for each destination for which it requests network to assign NR sidelink communication resource: 5> set sl-DestinationIdentity to the destination identity configured by upper layer for NR sidelink communication transmission; 5> set sl-CastType to the cast type of the associated destination identity configured by the upper layer for the NR sidelink communication transmission; 5> set sl-RLC-ModeIndication to include the RLC mode(s) and optionally QoS profile(s) of the sidelink QoS flow(s) of the associated RLC mode(s), if the associated bi-directional sidelink DRB has been established due to the configuration by RRCReconfigurationSidelink; 5> set sl-QoS-InfoList to include QoS profile(s) of the sidelink QoS flow(s) of the associated destination configured by the upper layer for the NR sidelink communication transmission; 5> set sl-InterestedFreqList to indicate the frequency of the associated destination for NR sidelink communication transmission; 5> set sl-TypeTxSyncList to the current synchronization reference type used on the associated sl-InterestedFreqList for NR sidelink communication transmission; 5> set sl-CapabilityInformationSidelink to include UECapabilityInformationSidelink message, if any, received from the associated peer UE; 5> if sl-FreqInfoListSizeExt is included in SIB12-IEs: 6> set sl-QoS-InfoList to include the frequency(ies), and Tx Profile mapped to the sidelink QoS flow(s) of the associated destination configured by the upper layer for the NR sidelink communication transmission; 4> if a sidelink radio link failure or a sidelink RRC reconfiguration failure has been declared, according to clauses 5.8.9.3 and 5.8.9.1.8, respectively; 5> include sl-FailureList and set its fields as follows for each destination for which it reports the NR sidelink communication failure: 6> set sl-DestinationIdentity to the destination identity configured by upper layer for NR sidelink communication transmission; 6> if the sidelink RLF is detected as specified in clause 5.8.9.3: 7> set sl-Failure as rlf for the associated destination for the NR sidelink communication transmission; 6> else if RRCReconfigurationFailureSidelink is received: 7> set sl-Failure as configFailure for the associated destination for the NR sidelink communication transmission; 4> if a sidelink carrier failure has been indicated by MAC layer; 5> include sl-CarrierFailureList and set its fields as follows for each destination for which it reports the sidelink carrier failure: 6> set sl-DestinationIdentity to the destination identity for which the concerned sidelink carrier failure is indicated; 6> set sl-CarrierFailure to include the concerned carrier for which the sidelink carrier failure is indicated; 3> if SIB12 includes sl-NonRelayDiscovery and if configured by upper layers to receive NR sidelink non-relay discovery messages, or if SIB12 includes sl-L2U2N-Relay and if configured by upper layers to receive NR sidelink L2 U2N relay discovery messages, or if SIB12 includes sl-L3U2N-RelayDiscovery and if configured by upper layers to receive NR sidelink L3 U2N relay discovery messages; or 3> if SIB12 includes [FFS gNB capability indication] and if configured by upper layers to receive NR sidelink U2U relay discovery messages: 4> include sl-RxInterestedFreqListDisc and set it to the frequency for NR sidelink discovery messages reception; 3> if SIB12 includes sl-L2U2N-Relay and the UE is capable of L2 U2N remote UE: 4> include sl-SourceIdentityRemoteUE and set it to the source identity configured by upper layer for NR sidelink L2 U2N relay communication transmission; 3> if SIB12 includes sl-NonRelayDiscovery and if configured by upper layers to transmit NR sidelink non-relay discovery messages, or if SIB12 includes sl-L2U2N-Relay and if configured by upper layers to transmit NR sidelink L2 U2N relay discovery messages, or if SIB12 includes sl-L3U2N-RelayDiscovery and if configured by upper layers to transmit NR sidelink L3 U2N relay discovery messages; or 3> if SIB12 includes [FFS gNB capability indication] and if configured by upper layers to transmit NR sidelink U2U relay discovery messages: 4> include sl-TxResourceReqListDisc and set its fields (if needed) as follows for each destination for which it requests network to assign NR sidelink discovery messages resource: 5> set sl-DestinationIdentityDisc to the destination identity configured by upper layer for NR sidelink discovery messages transmission; 5> if the UE is acting as L2 U2N Relay UE: 6> set sl-SourceIdentityRelayUE to the source identity configured by upper layer for NR sidelink L2 U2N relay discovery messages transmission; 5> set sl-CastTypeDisc to the cast type of the associated destination identity for the NR sidelink discovery messages transmission; 5> set sl-TxInterestedFreqListDisc to indicate the frequency of the associated destination for NR sidelink discovery messages transmission; 5> set sl-TypeTxSyncListDisc to the current synchronization reference type used on the associated sl-InterestedFreqList for NR sidelink discovery messages transmission; 5> set sl-DiscoveryType to the current discovery type of the associated destination identity configured by the upper layer for NR sidelink discovery messages transmission; 3> if SIB12 includes sl-L2U2N-Relay and if configured by upper layers to transmit NR sidelink L2 U2N relay communication and the UE is acting as L2 U2N Relay UE: 4> include sl-TxResourceReqL2U2N-Relay in sl-TxResourceReqListCommRelay and set its fields (if needed) as follows for each destination for which it requests network to assign NR sidelink L2 U2N relay communication resource: 5> set sl-DestinationIdentityL2U2N to the destination identity configured by upper layer for NR sidelink L2 U2N relay communication transmission; 5> set sl-TxInterestedFreqListL2U2N to indicate the frequency of the associated destination for NR sidelink L2 U2N relay communication transmission; 5> set sl-TypeTxSyncListL2U2N to the current synchronization reference type used on the associated sl-InterestedFreqListL2U2N for NR sidelink L2 U2N relay communication transmission; 5> set sl-LocalID-Request to request local ID for L2 U2N Remote UE transiting to RRC_CONNECTED or in RRC_CONNECTED state; 5> set sl-PagingIdentityRemoteUE to the paging UE ID received from peer L2 U2N Remote UE, if it is not released as in 5.8.9.8.3; 5> set sl-CapabilityInformationSidelink to include UECapabilityInformationSidelink message, if any, received from peer UE; 4> include ue-Type and set it to relayUE; 3> if SIB12 includes sl-L2U2N-Relay and if configured by upper layers to transmit NR sidelink L2 U2N relay communication and the UE has a selected L2 U2N Relay UE: 4> include sl-TxResourceReqL2U2N-Relay in sl-TxResourceReqListCommRelay and set its fields (if needed) as follows to request network to assign NR sidelink L2 U2N relay communication resource: 5> set sl-TxInterestedFreqListL2U2N to indicate the frequency of the associated destination for NR sidelink L2 U2N relay communication transmission; 5> set sl-TypeTxSyncListL2U2N to the current synchronization reference type used on the associated sl-InterestedFreqListL2U2N for NR sidelink L2 U2N relay communication transmission; 5> set sl-CapabilityInformationSidelink to include UECapabilityInformationSidelink message, if any, received from peer UE; 4> include ue-Type and set it to remoteUE; 3> if SIB12 includes sl-L3U2N-RelayDiscovery and if configured by upper layers to transmit NR sidelink L3 U2N relay communication: 4> include sl-TxResourceReqL3U2N-Relay in sl-TxResourceReqListCommRelay and set its fields (if needed) as follows for each destination for which it requests network to assign NR sidelink L3 U2N relay communication resource: 5> set sl-DestinationIdentity to the destination identity configured by upper layer for NR sidelink L3 U2N relay communication transmission; 5> set sl-CastType to the cast type of the associated destination identity configured by the upper layer for the NR sidelink L3 U2N relay communication transmission; 5> set sl-RLC-ModeIndication to include the RLC mode(s) and optionally QoS profile(s) of the sidelink QoS flow(s) of the associated RLC mode(s), if the associated bi-directional sidelink DRB has been established due to the configuration by RRCReconfigurationSidelink; 5> set sl-QoS-InfoList to include QoS profile(s) of the sidelink QoS flow(s) of the associated destination configured by the upper layer for the NR sidelink L3 U2N relay communication transmission; 5> set sl-TxInterestedFreqList to indicate the frequency of the associated destination for NR sidelink L3 U2N relay communication transmission; 5> set sl-TypeTxSyncList to the current synchronization reference type used on the associated sl-InterestedFreqList for NR sidelink L3 U2N relay communication transmission; 5> set sl-CapabilityInformationSidelink to include UECapabilityInformationSidelink message, if any, received from peer UE; 4> include ue-Type and set it to relayUE if the UE is acting as NR sidelink L3 U2N Relay UE or to remoteUE otherwise; 3> if SIB12 includes [FFS gNB capability indication] and if configured by upper layers to transmit NR sidelink L2 U2U relay communication and the UE is acting as L2 U2U Relay UE: 4> include sl-TxResourceReqL2-U2U and set its fields (if needed) as follows for each destination for which it requests network to assign NR sidelink L2 U2U relay communication resource: 5> set sl-DestinationIdentityL2-U2U to the destination identity configured by upper layer for NR sidelink L2 U2U relay communication transmission to peer L2 U2U Remote UE; 5> set sl-TxInterestedFreqListL2-U2U to indicate the frequency of the associated destination for NR sidelink L2 U2U relay communication transmission; 5> set sl-TypeTxSyncListL2-U2U to the current synchronization reference type used on the associated sl-InterestedFreqListL2-U2U for NR sidelink L2 U2U relay communication transmission; 5> set sl-CapabilityInformationSidelink to include UECapabilityInformationSidelink message, if any, received from peer L2 U2U Remote UE; 5> include sl-U2U-InfoList and set its fields (if needed) for each entry as follows, to report the related information of the connected L2 Remote UEs: 6> include the source L2 U2U Remote UE's source L2 destination in sl-TargetUE-Identity; 6> include sl-PerSLRB-QoS-InfoList, with each entry including the per-SLRB second-hop QoS profile and the corresponding sl-RemoteUE-SLRB-Identity which is set to the same value as the SLRB-PC5-ConfigIndex received in RRCReconfigurationSidelink message from the L2 U2U Remote UE for the same end-to-end SLRB; 3> if SIB12 includes [FFS gNB capability indication] and if configured by upper layers to transmit NR sidelink L2 U2U relay communication and the UE has a selected L2 U2U Relay UE: 4> include sl-TxResourceReqL2-U2U and set its fields (if needed) as follows to request network to assign NR sidelink L2 U2U relay communication resource: 5> set sl-DestinationIdentityL2-U2U to the destination identity configured by upper layer for NR sidelink L2 U2U relay communication transmission to L2 U2U Relay UE; 5> set sl-TxInterestedFreqListL-2U2U to indicate the frequency of the associated destination for NR sidelink L2 U2U relay communication transmission; 5> set sl-TypeTxSyncListL2-U2U to the current synchronization reference type used on the associated sl-InterestedFreqListL2-U2U for NR sidelink L2 U2U relay communication transmission; 5> set sl-CapabilityInformationSidelink to include UECapabilityInformationSidelink message received from L2 U2U Relay UE and the peer L2 U2U Remote UE, if any; 5> include sl-U2U-InfoList and set its fields (if needed) for each entry as follows to report the related end-to-end and the first hop information for the end-to-end PC5 connection with each peer L2 U2U Remote UE: 6> set sl-TargetUE-Identity to the destination identity configured by upper layer for NR sidelink L2 U2U relay communication transmission to peer L2 U2U Remote UE; 6> set sl-E2E-QoS-InfoList to include end-to-end QoS profile(s) of the sidelink QoS flow(s) of the associated destination configured by the upper layer for the NR sidelink L2 U2U relay communication transmission to peer L2 U2U Remote UE; 6> set sl-PerSLRB-QoS-InfoList to include the first-hop split PDB of the sidelink QoS flow(s) received from the sl-SplitQoS-InfoListPC5 in UEInformationResponseSidelink message for the associated destination in accordance with the received sl-TargetUE-Identity; 3> if sl-DRX-ConfigCommonGC-BC is included in SIB12-IEs: 4> if configured by upper layers to perform NR sidelink reception: 5> include sl-RxDRX-ReportList and set its fields (if needed) as follows for each destination for which it reports to network: 6> set sl-DRX-ConfigFromTx to include the accepted sidelink DRX configuration of the associated destination for NR sidelink unicast communication, if received from the associated peer UE; 5> include sl-RxInterestedGC-BC-DestList and set its fields (if needed) as follows for each Destination Layer-2 ID for which it reports to network: 6> set sl-RxInterestedQoS-InfoList to include the QoS profile of its interested service(s) that sidelink DRX is applied for the associated destination for NR sidelink groupcast or broadcast reception; NOTE 1: It is up to UE implementation to set the QoS profile in sl-RxInterestedQoS-InfoList for reception of NR sidelink discovery message or ProSe Direct Link Establishment Request message as described in TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [72], or for reception of Direct Link Establishment Request message as described in TS 24.587[ Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 ] [57]. 6> set sl-DestinationIdentity to the associated destination identity configured by upper layer for NR sidelink groupcast or broadcast reception; 4> if configured by upper layers to perform NR sidelink transmission and configured with sl-ScheduledConfig: 5> include sl-TxResourceReqList and/or sl-TxResourceReqListCommRelay and/or sl-FailureList and set its fields (if needed) as follows for each destination for which it reports to network: 6> set sl-DRX-InfoFromRxList to include the sidelink DRX assistance information of the associated destination, if any, received from the associated peer UE; 6> if the RRCReconfigurationCompleteSidelink message includes the sl-DRX-ConfigReject: 7> set sl-Failure as drxReject-v1710 for the associated destination for the NR sidelink communication transmission; 6> set sl-DRX-Indication to include the sidelink DRX on/off indication for the associated destination for NR sidelink groupcast transmission; 2> if SIB23 including sl-PosConfigCommonNR is provided by the PCell; 3> if configured to transmit SL-PRS: 4> include sl-PosTxResourceReqList and set its fields (if needed) as follows for each destination for which it requests network to assign NR sidelink positioning resource: 5> set sl-DestinationIdentity to the destination identity configured by upper layer for NR sidelink positioning transmission; 5> set sl-CastType to the cast type of the associated destination identity configured by the upper layer for the NR sidelink positioning transmission; 5> set sl-RLC-ModeIndication to include the RLC mode(s) 5> set sl-InterestedFreqList to indicate the frequency of the associated destination for SL-PRS transmission; 5> set sl-TypeTxSyncList to the current synchronization reference type used on the associated sl-InterestedFreqList for NR sidelink positioning transmission; 3> if configured to receive sidelink control information for SL-PRS measurements; 4> include sl-PosRxInterestedFreqList and set it to the frequency for NR sidelink positioning reception. Editor's Note: FFS on sl-PosTxResourceReqList 1> if the UE initiates the procedure while connected to an E-UTRA PCell: 2> submit the SidelinkUEInformationNR to lower layers via SRB1, embedded in E-UTRA RRC message ULInformationTransferIRAT as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], clause 5.6.28; 1> else: 2> submit the SidelinkUEInformationNR message to lower layers for transmission. NOTE 2: When multiple lists are reported in SidelinkUEInformationNR, a UE can report up to maxNrofSL-Dest-r16 SL destinations in sl-TxResourceReqList, sl-TxResourceReqListDisc and sl-TxResourceReqListCommRelay in total. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.3.3 |
5,223 | 4.3.25 Dedicated Core Networks (DCNs) 4.3.25.1 General | This feature enables an operator to deploy multiple DCNs within a PLMN with each DCN consisting of one or multiple CN nodes. Each DCN may be dedicated to serve specific type(s) of subscriber. This is an optional feature and enables DCNs to be deployed for one or multiple RATs (e.g. GERAN, UTRAN, E-UTRAN, WB-E-UTRAN and NB-IoT). There can be several motivations for deploying DCNs, e.g. to provide DCNs with specific characteristics/functions or scaling, to isolate specific UEs or subscribers (e.g. M2M subscribers, subscribers belonging to a specific enterprise or separate administrative domain, etc.). A DCN comprises of one or more MME/SGSN and it may comprise of one or more SGW/PDN GW/PCRF. This feature enables subscribers to be allocated to and served by a DCN based on subscription information ("UE Usage Type"). The feature in this clause handles both DCN selections without any specific UE functionality, i.e. it works also with UEs of earlier releases and UE assisted DCN selection. The main specific functions are for routing and maintaining UEs in their respective DCN. The following deployment scenarios are supported for DCN: - DCNs may be deployed to support one RAT only, (e.g. only dedicated MMEs are deployed to support E-UTRAN and dedicated SGSNs are not deployed), to support multiple RATs, or to support all RATs. - Networks deploying DCNs may have a default DCN, which is managing UEs for which a DCN is not available or if sufficient information is not available to assign a UE to a DCN. One or multiple DCNs may be deployed together with a default DCN that all share the same RAN. - The architecture supports scenarios where the DCN is only deployed in a part of the PLMN e.g. only for one RAT or only in a part of the PLMN area. Such heterogeneous or partial deployment of DCNs may, depending on operator deployment and configuration, result in service with different characteristics or functionality, depending on whether the UE is inside or outside the service area or RAT that supports the DCN. NOTE 1: Heterogeneous or partial deployment of DCNs may result in increased occurrence of UEs first being served by a CN node in the default DCN and then being redirected to a CN node in the DCN that serves the UE when the UE moves from areas outside of DCN coverage to an area of DCN coverage. It may also result in an increased re-attach rate in the network. As this has impacts on the required capacity of the default CN nodes deployed at edge of DCN coverage, it is not recommended to deploy DCNs heterogeneously or partially. - Even if the DCN is not deployed to serve a particular RAT or service area of PLMN, the UE in that RAT or service area may still be served by a PDN GW from the DCN. High level overview for supporting DCNs is provided below. Details are captured in appropriate clauses of this specification, TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7] and TS 23.236[ Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes ] [30]. - An optional subscription information parameter ("UE Usage Type") is used in the selection of a DCN. An operator configures which of his DCN(s) serves which UE Usage Type(s). The HSS provides the "UE Usage Type" value in the subscription information of the UE to the MME/SGSN. Both standardized and operator specific values for UE Usage Type are possible. - The serving network selects the DCN based on the operator configured (UE Usage Type to DCN) mapping, other locally configured operator's policies and the UE related context information available at the serving network, e.g. information about roaming. UEs with different UE Usage Type values may be served by the same DCN. Moreover, UEs that share the same UE Usage Type value may be served by different DCNs. - If the configuration shows no DCN for the specific "UE Usage Type" value in the subscription information, then the serving MME/SGSN serves the UE by the default DCN or selects a DCN using serving operator specific policies. - Some subscribers may be configured without "UE Usage Type" value. In this case, the MME/SGSN may select the DCN that serves the UE using locally configured operator's policies and the UE related context information available at the serving network (other than UE provided DCN-ID). The MME/SGSN performs procedures described in clauses 5.19.1 and 5.19.2. - The "UE Usage Type" is associated with the UE (describing its usage characteristic), i.e. there is only one UE Usage Type" per UE subscription. - For each DCN, one or more CN nodes may be configured as part of a pool. - For MME, the MMEGI(s) identifies a DCN within the PLMN. For SGSNs, a group identifier(s) identifies a DCN within the PLMN. That is, the group of SGSNs that belong to a DCN within a PLMN. This identifier may have the same format as NRI (e.g. an NRI value that does not identify a specific SGSN node in the serving area) in which case it is called "Null-NRI" or it may have a format independent of NRI, in which case it is called "SGSN Group ID". The "Null-NRI" or "SGSN Group ID" is provided by an SGSN to RAN which triggers the NNSF procedure to select an SGSN from the group of SGSNs corresponding to the Null-NRI/SGSN Group ID (see clause 5.19.1). NOTE 2: SGSN Group IDs enable to handle deployment scenarios where in a service area all NRI values are allocated to SGSNs and hence no NRI value remains that can be used as Null-NRI. - The dedicated MME/SGSN that serves the UE selects a dedicated S-GW and P-GW based on UE Usage Type. - At initial access to the network if sufficient information is not available for RAN to select a specific DCN, the RAN may selects a CN node from the default DCN. A redirection to another DCN may then be required. - To redirect a UE from one DCN to a different DCN, the redirection procedure via RAN, described in clause 5.19.1, is used to forward the NAS message of the UE to the target DCN. - All selection functions are aware of DCN(s), including the network node selection function (NNSF) of RAN nodes, for selecting and maintaining the appropriate DCN for the UEs. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.25 |
5,224 | 4.23.14 Pause of charging | When I-SMF is involved for a PDU Session, the procedure for pause of charging in home routed roaming case defined in clause 4.4.4 is applied by replacing the H-SMF with SMF and V-SMF with I-SMF. When a Local UPF (PSA) is involved, the SMF stops or starts the usage reporting including usage reporting at the Local UPF (PSA) via the I-SMF. For a PDU Session, if charging has been paused previously, in addition to the conditions for stopping pause of charging as described in clause 4.4.4, the charging is unpaused in the following case: - When the SMF receives Nsmf_PDUSession_Create Request from a new I-SMF or Nsmf_PDUSession_CreateSMContext request from AMF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.14 |
5,225 | 6.1.1 Overall Architecture of NG-RAN | Figure 6.1-1: Overall architecture The NG-RAN consists of a set of gNBs connected to the 5GC through the NG interface. NOTE: As specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [2], NG-RAN could also consists of a set of ng-eNBs, an ng-eNB may consist of an ng-eNB-CU and one or more ng-eNB-DU(s). An ng-eNB-CU and an ng-eNB-DU is connected via W1 interface. The general principle described in this clause also applies to ng-eNB and W1 interface, if not explicitly specified otherwise. An gNB can support FDD mode, TDD mode or dual mode operation. gNBs can be interconnected through the Xn interface. A gNB may consist of a gNB-CU and one or more gNB-DU(s). A gNB-CU and a gNB-DU is connected via F1 interface. One gNB-DU is connected to only one gNB-CU. NOTE: In case of network sharing with multiple cell ID broadcast, each Cell Identity associated with a subset of PLMNs corresponds to a gNB-DU and the gNB-CU it is connected to, i.e. the corresponding gNB-DUs share the same physical layer cell resources. NOTE: For resiliency, a gNB-DU may be connected to multiple gNB-CUs by appropriate implementation. NG, Xn and F1 are logical interfaces. For NG-RAN, the NG and Xn-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs, terminate in the gNB-CU. For EN-DC, the S1-U and X2-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs, terminate in the gNB-CU. The gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB. A possible deployment scenario is described in Annex A. The node hosting user plane part of NR PDCP (e.g. gNB-CU, gNB-CU-UP, and for EN-DC, MeNB or SgNB depending on the bearer split) shall perform user inactivity monitoring and further informs its inactivity or (re)activation to the node having C-plane connection towards the core network (e.g. over E1, X2). The node hosting NR RLC (e.g. gNB-DU) may perform user inactivity monitoring and further inform its inactivity or (re)activation to the node hosting control plane, e.g. gNB-CU or gNB-CU-CP. UL PDCP configuration (i.e. how the UE uses the UL at the assisting node) is indicated via X2-C (for EN-DC), Xn-C (for NG-RAN) and F1-C. Radio Link Outage/Resume for DL and/or UL is indicated via X2-U (for EN-DC), Xn-U (for NG-RAN) and F1-U. The NG-RAN is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL). The NG-RAN architecture, i.e. the NG-RAN logical nodes and interfaces between them, is defined as part of the RNL. For each NG-RAN interface (NG, Xn, F1) the related TNL protocol and the functionality are specified. The TNL provides services for user plane transport, signalling transport. In NG-Flex configuration, each NG-RAN node is connected to all AMFs of AMF Sets within an AMF Region supporting at least one slice also supported by the NG-RAN node. The AMF Set and the AMF Region are defined in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. If security protection for control plane and user plane data on TNL of NG-RAN interfaces has to be supported, NDS/IP TS 33.501[ Security architecture and procedures for 5G System ] [13] shall be applied. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 6.1.1 |
5,226 | 8.2.1.3.4 Minimum Requirement 2 Tx Antenna Port (demodulation subframe overlaps with aggressor cell ABS and CRS assistance information are configured) | The requirements for non-MBSFN ABS are specified in Table 8.2.1.3.4-2, with the addition of parameters in Table 8.2.1.3.4-1. The purpose is to verify the performance of large delay CDD with 2 transmit antennas if the PDSCH transmission in the serving cell takes place in subframes that overlap with ABS [9] of the aggressor cells with CRS assistance information. In Table 8.2.1.3.4-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup for Cell 1 is according to Annex C.3.2 and for Cell 2 and Cell 3 is according to Annex C.3.3, respectively. The CRS assistance information [7] includes Cell 2 ad Cell3. Table 8.2.1.3.4-1: Test Parameters for Large Delay CDD (FRC) – Non-MBSFN ABS Table 8.2.1.3.4-2: Minimum Performance Large Delay CDD (FRC) – Non-MBSFN ABS | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.1.3.4 |
5,227 | 5.4.6.2 Core Network assisted RAN parameters tuning | Core Network assisted RAN parameters tuning aids the RAN to minimize the UE state transitions and achieve optimum network behaviour. How the RAN uses the CN assistance information is not defined in this specification. Core Network assisted RAN parameters tuning may be derived by the AMF per UE in the AMF based on collection of UE behaviour statistics, Expected UE Behaviour and/or other available information about the UE (such as subscribed DNN, SUPI ranges, or other information). If the AMF maintains Expected UE Behaviour parameters, Network Configuration parameters (as described in clause 4.15.6.3 or 4.15.6.3a, TS 23.502[ Procedures for the 5G System (5GS) ] [3]) or SMF derived CN assisted RAN parameters tuning, the AMF may use this information for selecting the CN assisted RAN parameter values. If the AMF is able to derive the Mobility Pattern of the UE (as described in clause 5.3.4.2), the AMF may take the Mobility Pattern information into account when selecting the CN assisted RAN parameter values. The SMF uses the SMF-Associated parameters (e.g. Expected UE Behaviour parameters or Network Configuration parameters of the UE) to derive the SMF derived CN assisted RAN parameters tuning. The SMF sends the SMF derived CN assisted RAN parameters tuning to the AMF during the PDU Session establishment procedure and if the SMF-Associated parameters change the PDU Session modification procedure is applied. The AMF stores the SMF derived CN assisted RAN parameters tuning in the PDU Session level context. The AMF uses the SMF derived CN assisted RAN parameters tuning to determine a PDU Session level "Expected UE activity behaviour" parameters set, which may be associated with a PDU Session ID, as described below in this clause. The Expected UE Behaviour parameters or the Network Configuration parameters can be provisioned by external party via the NEF to the AMF or SMF, as described in clause 5.20. The CN assisted RAN parameters tuning provides the RAN with a way to understand the UE behaviour for these aspects: - "Expected UE activity behaviour", i.e. the expected pattern of the UE's changes between CM-CONNECTED and CM-IDLE states or the duration of CM-CONNECTED state. This may be derived e.g. from the statistical information, or Expected UE Behaviour or from subscription information. The AMF derives one or more sets of the "Expected UE activity behaviour" parameters for the UE as follows: - AMF may derive and provide to the RAN a UE level of "Expected UE activity behaviour" parameters set considering the Expected UE Behaviour parameters or Network Configuration parameters received from the UDM (see clauses 4.15.6.3 or 4.15.6.3a of TS 23.502[ Procedures for the 5G System (5GS) ] [3]) and the SMF derived CN assisted RAN parameters tuning associated with a PDU Session using Control Plane CIoT 5GS Optimisation. This set of "Expected UE activity behaviour" parameters is valid for the UE; and - AMF may provide to the RAN a PDU Session level "Expected UE activity behaviour" parameters set, e.g. considering the SMF derived CN assisted RAN parameters tuning, per established PDU Session. The PDU Session level "Expected UE activity behaviour" set of parameters is associated with and valid for a PDU Session ID. The RAN may consider the PDU Session level "Expected UE activity behaviour" parameters when the User Plane resources for the PDU Session are activated; - "Expected HO behaviour", i.e. the expected interval between inter-RAN handovers. This may be derived by the AMF e.g. from the Mobility Pattern information; - "Expected UE mobility", i.e. whether the UE is expected to be stationary or mobile. This may be derived e.g. from the statistical information or Expected UE Behaviour parameters or from subscription information; - "Expected UE moving trajectory" which may be derived e.g. from the statistical information or Expected UE Behaviour parameters or from subscription information; or - "UE Differentiation Information" including the Expected UE Behaviour parameters excluding the Expected UE moving trajectory (see clause 4.15.6.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]) to support Uu operation optimisation for NB-IoT UE differentiation if the RAT type is NB-IoT. The AMF decides when to send this information to the RAN as "Expected UE activity behaviour" carried in N2 request over the N2 interface (see TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]). NOTE: The calculation of the CN assistance information, i.e. the algorithms used and related criteria, and the decision when it is considered suitable and stable to send to the RAN are vendor specific. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.6.2 |
5,228 | 5.8.13.3 NR sidelink discovery transmission | A UE capable of NR sidelink discovery that is configured by upper layer to transmit NR sidelink discovery message shall: 1> if the frequency used for NR sidelink discovery is included in sl-FreqInfoToAddModList in sl-ConfigDedicatedNR within RRCReconfiguration message; or if the frequency used for NR sidelink discovery is included in sl-FreqInfoList within SIB12: 2> if the UE is in RRC_CONNECTED and uses the frequency included in sl-ConfigDedicatedNR within RRCReconfiguration message: 3> if the UE is acting as NR sidelink U2N Relay UE and sl-DiscConfig is included in RRCReconfiguration, and if the NR sidelink U2N Relay UE threshold conditions as specified in 5.8.14.2 are met based on sl-RelayUE-Config; or 3> if the UE is selecting NR sidelink U2N Relay UE / has a selected NR sidelink U2N Relay UE/ configured with measurement object associated to L2 U2N Relay UEs and sl-DiscConfig is included in RRCReconfiguration, and if the NR sidelink U2N Remote UE threshold conditions as specified in 5.8.15.2 are met based on sl-RemoteUE-Config; or 3> if the UE is selecting NR sidelink U2U Relay UE / has a selected NR sidelink U2U Relay UE and sl-DiscConfig is included in RRCReconfiguration, and if the NR sidelink U2U Remote UE threshold conditions associated with the peer NR Sidelink U2U Remote UE as specified in 5.8.17.2 are met based on sl-RemoteUE-ConfigU2U; or 3> if the UE acting as Target Remote UE is performing U2U Relay Discovery with Model B and sl-DiscConfig is included in RRCReconfiguration, and if the NR sidelink U2U Remote UE threshold conditions associated with the NR sidelink U2U Relay UE as specified in 5.8.17.2 are met based on sl-RemoteUE-ConfigU2U; or 3> if the UE acting as U2U Relay UE is performing U2U Relay Discovery with Model A or Model B response message as specified in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [65]; or 3> if the UE acting as U2U Relay UE is performing U2U Relay Discovery with Model B as specified in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [65] and sl-DiscConfig is included in RRCReconfiguration, and if the NR sidelink U2U Relay UE threshold conditions as specified in 5.8.16.2 are met based on sl-RelayUE-ConfigU2U; or NOTE 1: For U2U Relay UE and Target Remote UE, it can be up to UE implementation on cross-layer interaction for the AS layer condition check for discovery message forwarding. 3> if the UE is performing NR sidelink non-relay discovery: 4> if the UE is configured with sl-ScheduledConfig: 5> if T310 for MCG or T311 is running; and if sl-TxPoolExceptional is included in sl-FreqInfoList for the concerned frequency in SIB12 or included in sl-ConfigDedicatedNR in RRCReconfiguration; or 5> if T301 is running and the cell on which the UE initiated RRC connection re-establishment provides SIB12 including sl-TxPoolExceptional for the concerned frequency; or 5> if T304 for MCG is running and the UE is configured with sl-TxPoolExceptional included in sl-ConfigDedicatedNR for the concerned frequency in RRCReconfiguration: 6> configure lower layers to perform the sidelink resource allocation mode 2 based on random selection using the resource pool indicated by sl-TxPoolExceptional as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] for NR sidelink discovery transmission; 5> else: 6> configure lower layers to perform the sidelink resource allocation mode 1 using the resource pool indicated by sl-DiscTxPoolScheduling or sl-TxPoolScheduling for NR sidelink discovery transmission on the concerned frequency in RRCReconfiguration; 5> if T311 is running, configure the lower layers to release the resources indicated by rrc-ConfiguredSidelinkGrant (if any); 4> if the UE is configured with sl-UE-SelectedConfig: 5> if the sl-DiscTxPoolSelected for NR sidelink discovery transmission on the concerned frequency is included in the sl-ConfigDedicatedNR within RRCReconfiguration, and if a result of full/partial sensing, if selected and is allowed by sl-AllowedResourceSelectionConfig, on the resources configured in sl-DiscTxPoolSelected for NR sidelink discovery transmission on the concerned frequency included in sl-ConfigDedicatedNR within RRCReconfiguration is not available in accordance with TS 38.214[ NR; Physical layer procedures for data ] [19]; or 5> if the sl-DiscTxPoolSelected for NR sidelink discovery transmission on the concerned frequency is not included in the sl-ConfigDedicatedNR within RRCReconfiguration, and a result of full/partial sensing, if selected and is allowed by sl-AllowedResourceSelectionConfig, on the resources configured in sl-TxPoolSelectedNormal for NR sidelink discovery transmission on the concerned frequency included in sl-ConfigDedicatedNR within RRCReconfiguration is not available in accordance with TS 38.214[ NR; Physical layer procedures for data ] [19]; 6> if sl-TxPoolExceptional for the concerned frequency is included in RRCReconfiguration; or 6> if the PCell provides SIB12 including sl-TxPoolExceptional in sl-FreqInfoList for the concerned frequency: 7> configure lower layers to perform the sidelink resource allocation mode 2 based on random selection using the resource pool indicated by sl-TxPoolExceptional as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] for NR sidelink discovery transmission; 5> else, if the sl-DiscTxPoolSelected for NR sidelink discovery transmission on the concerned frequency is included in the sl-ConfigDedicatedNR within RRCReconfiguration: 6> configure lower layers to perform the sidelink resource allocation mode 2 based on resource selection operation according to sl-AllowedResourceSelectionConfig (as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] and TS 38.214[ NR; Physical layer procedures for data ] [19]) using the pools of resources indicated by sl-DiscTxPoolSelected for NR sidelink discovery transmission on the concerned frequency in RRCReconfiguration; 5> else, if the sl-TxPoolSelectedNormal for NR sidelink discovery transmission on the concerned frequency is included in the sl-ConfigDedicatedNR within RRCReconfiguration: 6> configure lower layers to perform the sidelink resource allocation mode 2 based on resource selection operation according to sl-AllowedResourceSelectionConfig (as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] and TS 38.214[ NR; Physical layer procedures for data ] [19]) using the pools of resources indicated by sl-TxPoolSelectedNormal for NR sidelink discovery transmission on the concerned frequency in RRCReconfiguration; 2> else if the cell chosen for NR sidelink discovery transmission provides SIB12: 3> if the UE is acting as NR sidelink U2N Relay UE and sl-DiscConfigCommon is included in SIB12, and if the NR sidelink U2N Relay UE threshold conditions as specified in 5.8.14.2 are met based on sl-RelayUE-ConfigCommon in SIB12; or 3> if the UE is selecting NR sidelink U2N Relay UE / has a selected NR sidelink U2N Relay UE and sl-DiscConfigCommon is included in SIB12, and if the NR sidelink U2N Remote UE threshold conditions as specified in 5.8.15.2 are met based on sl-RemoteUE-ConfigCommon in SIB12; or 3> if the UE is selecting NR sidelink U2U Relay UE / has a selected NR sidelink U2U Relay UE and sl-DiscConfigCommon is included in SIB12, and if the NR sidelink U2U Remote UE threshold conditions associated with the peer NR Sidelink U2U Remote UE as specified in 5.8.17.2 are met based on sl-RemoteUE-ConfigCommonU2U in SIB12; or 3> if the UE acting as Target Remote UE is performing U2U Relay Discovery with Model B and if the NR sidelink U2U Remote UE threshold conditions associated with the NR sidelink U2U Relay UE as specified in 5.8.17.2 are met based on sl-RemoteUE-ConfigCommonU2U in SIB12; or 3> if the UE acting as U2U Relay UE is performing U2U Relay Discovery with Model A or Model B response message as specified in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [65]; or 3> if the UE acting as U2U Relay UE is performing U2U Relay Discovery with Model B as specified in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [65] and if the NR sidelink U2U Relay UE threshold conditions as specified in 5.8.16.2 are met based on sl-RelayUE-ConfigCommonU2U in SIB12; or 3> if the UE is performing NR sidelink non-relay discovery: 4> if SIB12 includes sl-DiscTxPoolSelected for NR sidelink discovery transmission on the concerned frequency, and a result of full/partial sensing, if selected and is allowed by sl-AllowedResourceSelectionConfig, on the resources configured in the sl-DiscTxPoolSelected for NR sidelink discovery transmission is available in accordance with TS 38.214[ NR; Physical layer procedures for data ] [19] or random selection, if allowed by sl-AllowedResourceSelectionConfig, is selected: 5> configure lower layers to perform the sidelink resource allocation mode 2 based on resource selection operation according to sl-AllowedResourceSelectionConfig using the pools of resources indicated by sl-DiscTxPoolSelected for NR sidelink discovery transmission on the concerned frequency in SIB12 as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]; 4> else if SIB12 includes sl-TxPoolSelectedNormal for NR sidelink discovery transmission on the concerned frequency, and a result of full/partial sensing, if selected and is allowed by sl-AllowedResourceSelectionConfig, on the resources configured in the sl-TxPoolSelectedNormal for NR sidelink discovery transmission is available in accordance with TS 38.214[ NR; Physical layer procedures for data ] [19] or random selection, if allowed by sl-AllowedResourceSelectionConfig, is selected: 5> configure lower layers to perform the sidelink resource allocation mode 2 based on resource selection operation according to sl-AllowedResourceSelectionConfig using the pools of resources indicated by sl-TxPoolSelectedNormal for NR sidelink discovery transmission on the concerned frequency in SIB12 as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]; 4> else if SIB12 includes sl-TxPoolExceptional for the concerned frequency: 5> from the moment the UE initiates RRC connection establishment or RRC connection resume, until receiving an RRCReconfiguration including sl-ConfigDedicatedNR, or receiving an RRCRelease or an RRCReject; or 5> if a result of full/partial sensing, if selected and is allowed by sl-AllowedResourceSelectionConfig, on the resources configured in sl-DiscTxPoolSelected for NR sidelink discovery transmission on the concerned frequency in SIB12 is not available in accordance with TS 38.214[ NR; Physical layer procedures for data ] [19]; or 5> if sl-DiscTxPoolSelected for NR sidelink discovery transmission on the concerned frequency is not included in SIB12 and if a result of full/partial sensing, if selected and is allowed by sl-AllowedResourceSelectionConfig, on the resources configured in sl-TxPoolSelectedNormal for NR sidelink discovery transmission on the concerned frequency in SIB12 is not available in accordance with TS 38.214[ NR; Physical layer procedures for data ] [19]: 6> configure lower layers to perform the sidelink resource allocation mode 2 based on random selection (as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]) using one of the pools of resources indicated by sl-TxPoolExceptional for NR sidelink discovery transmission on the concerned frequency; 1> else if out of coverage on the concerned frequency for NR sidelink discovery: 2> if the UE is acting as L3 U2N Relay UE; or 2> if the UE is selecting NR sidelink U2N Relay UE / has a selected NR sidelink U2N Relay UE and if the NR sidelink U2N Remote UE threshold conditions as specified in 5.8.15.2 are met based on sl-PreconfigDiscConfig in SidelinkPreconfigNR; or 2> if the UE is selecting NR sidelink U2U Relay UE / has a selected NR sidelink U2U Relay UE and if the NR sidelink U2U Remote UE threshold conditions associated with the peer NR sidelink U2U Remote UE as specified in 5.8.17.2 are met based on sl-RemoteUE-PreconfigU2U in SidelinkPreconfigNR; or 2> if the UE acting as Target Remote UE is performing U2U Relay Discovery with Model B and if the NR sidelink U2U Remote UE threshold conditions associated with the NR sidelink U2U Relay UE as specified in 5.8.17.2 are met based on sl-RemoteUE-PreconfigU2U in SidelinkPreconfigNR; or 2> if the UE acting as U2U Relay UE is performing U2U Relay Discovery with Model A or Model B response message as specified in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [65]; or 2> if the UE acting as U2U Relay UE is performing U2U Relay Discovery with Model B as specified in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [65] and if the NR sidelink U2U Relay UE threshold conditions as specified in 5.8.16.2 are met based on sl-RelayUE-PreconfigU2U in SidelinkPreconfigNR; or 2> if the UE is performing NR sidelink non-relay discovery: 3> configure lower layers to perform the sidelink resource allocation mode 2 based on resource selection operation according to sl-AllowedResourceSelectionConfig (as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] and TS 38.213[ NR; Physical layer procedures for control ] [13]) using the pools of resources indicated in sl-DiscTxPoolSelected or sl-TxPoolSelectedNormal for NR sidelink discovery transmission on the concerned frequency in SidelinkPreconfigNR. NOTE 2: It is up to UE implementation to determine, in accordance with TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], which resource pool to use if multiple resource pools are configured, and which resource allocation scheme is used in the AS based on UE capability (for a UE in RRC_IDLE/RRC_INACTIVE) and the allowed resource schemes sl-allowedResourceSelectionConfig in the resource pool configuration. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.13.3 |
5,229 | 5.3.3.1 Tracking Area Update procedure with Serving GW change | Figure 5.3.3.1-1: Tracking Area Update procedure with Serving GW change NOTE 1: For a PMIP-based S5/S8, procedure steps (A) and (B) are defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. Steps 9 and 10 concern GTP based S5/S8. NOTE 2: In the case of Tracking Area Update without MME change the signalling in steps 4, 5, 7 and steps 12-17 are skipped. 1. One of the triggers described in clause 5.3.3.0 for starting the TAU procedure occurs. 2. The UE initiates the TAU procedure by sending, to the eNodeB, a TAU Request (UE Core Network Capability, MS Network Capability, Preferred Network behaviour, Support for restriction of use of Enhanced Coverage, old GUTI, Old GUTI type, last visited TAI, active flag, signalling active flag, EPS bearer status, P-TMSI Signature, additional GUTI, eKSI, NAS sequence number, NAS-MAC, KSI, Voice domain preference and UE's usage setting, UE has UE Radio Capability ID assigned for the selected PLMN, Requested IMSI Offset, Release Request indication, Paging Restriction Information, Unavailability Period Duration, Start of Unavailability Period) message together with RRC parameters indicating the Selected Network and the old GUMMEI. An exception is that, if the TAU was triggered for load re-balancing purposes (see clause 4.3.7.3), the old GUMMEI is not included in the RRC parameters. The UE shall set the Old GUTI Type to indicate whether the Old GUTI is a native GUTI or is mapped from a P-TMSI and RAI. If the UE's TIN indicates "GUTI" or "RAT-related TMSI" and the UE holds a valid GUTI then the old GUTI indicates this valid GUTI. If the UE's TIN indicates "P-TMSI" and the UE holds a valid P-TMSI and related RAI then these two elements are indicated as the old GUTI. Mapping a P-TMSI and RAI to a GUTI is specified in Annex H. When the UE is in connected mode (e.g. in URA_PCH) when it reselects to E-UTRAN, the UE shall set its TIN to "P-TMSI". If the UE holds a valid GUTI and the old GUTI indicates a GUTI mapped from a P-TMSI and RAI, then the UE indicates the GUTI as additional GUTI. If the old GUTI indicates a GUTI mapped from a P-TMSI and RAI, and the UE has a valid P-TMSI signature, the P-TMSI signature shall be included. The additional GUTI in the Tracking Area Update Request message allows the new MME to find any already existing UE context stored in the new MME when the old GUTI indicates a value mapped from a P-TMSI and RAI. Alternatively, when a UE only supports E-UTRAN, it identifies itself with the old GUTI and sets the Old GUTI Type to 'native'. The RRC parameter "old GUMMEI" takes its value from the identifier that is signalled as the old GUTI according to the rules above. For a combined MME/SGSN the eNodeB is configured to route the MME-code(s) of this combined node to the same combined node. This eNodeB is also configured to route MME-code(s) of GUTIs that are generated by the UE's mapping of the P-TMSIs allocated by the combined node. Such an eNodeB configuration may also be used for separate nodes to avoid changing nodes in the pool caused by inter RAT mobility. The last visited TAI shall be included in order to help the MME produce a good list of TAIs for any subsequent TAU Accept message. Selected Network indicates the network that is selected. Active flag is a request by UE to activate the radio and S1 bearers for all the active EPS Bearers by the TAU procedure when the UE is in ECM-IDLE state. Signalling active flag is a request by UE using Control Plane CIoT EPS Optimisation to maintain the NAS signalling connection after Tracking Area Update Procedure is completed in order to transmit pending Data using the Data Transport in Control Plane CIoT EPS Optimisation or NAS signalling. The EPS bearer status indicates each EPS bearer that is active in the UE. The TAU Request message shall be integrity protected by the NAS-MAC as described in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [41]. eKSI, NAS sequence number and NAS-MAC are included if the UE has valid EPS security parameters. NAS sequence number indicates the sequential number of the NAS message. KSI is included if the UE indicates a GUTI mapped from a P-TMSI in the information element "old GUTI". In the RRC connection establishment signalling associated with the TAU Request, the UE indicates its support of the CIoT EPS Optimisations relevant for MME selection. For UE using CIoT EPS Optimisation without any activated PDN connection, there is no active flag or EPS bearer status included in the TAU Request message. For a UE with a running Service Gap timer in the UE the UE shall not set the active flag and the signalling active flag in the TAU request message (see clause 4.3.17.9) except for network access for regulatory prioritized services like Emergency services or exception reporting. If the UE has any PDN connection of PDN Type "non-IP" or "Ethernet", the UE shall send the EPS bearer status in the TAU Request message. The UE sets the voice domain preference and UE's usage setting according to its configuration, as described in clause 4.3.5.9. The UE includes extended idle mode DRX parameters information element if it needs to enable extended idle mode DRX, even if extended idle mode DRX parameters were already negotiated before. The UE may include UE paging probability information if it supports the assignment of WUS Assistance Information from the MME to assist the eNodeB's Wake-Up Signal (WUS) group decision (see TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]). If a UE includes a Preferred Network Behaviour, this defines the Network Behaviour the UE is expecting to be available in the network as defined in clause 4.3.5.10. If the UE supports RACS as defined in clause 5.11.3a, and if the UE is provisioned with a UE Radio Capability ID for use in the selected PLMN (i.e. PLMN-assigned for the specific PLMN or manufacturer-assigned), the UE includes a flag that indicates it has an assigned UE Radio Capability ID for use in the selected PLMN but the actual UE Radio Capability ID is provided to MME after security context is established in step 6 (see below). If a Multi-USIM UE wants to enter ECM-IDLE state it includes the Release Request indication and optionally provides Paging Restriction Information. If a Multi-USIM UE needs to modify the Paging Occasions in order to avoid paging collisions, it sends a Requested IMSI Offset to the MME, in order to signal an alternative IMSI as described in clause 4.3.33 In the case of satellite access for Cellular IoT, the MME may verify the UE location and determine whether the PLMN is allowed to operate at the UE location, as described in clause 4.13.4. If the UE receives a TAU Reject message with cause value indicating that the selected PLMN is not allowed to operate at the present UE location, the UE shall attempt to select a PLMN as specified in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [10]. If the UE is using a eNodeB that provides discontinuous coverage (e.g. for satellite access with discontinuous coverage), the UE may include an Unavailability Period Duration and Start of Unavailability Period, see clause 4.13.8.2. 3. The eNodeB derives the MME address from the RRC parameters carrying the old GUMMEI, the indicated Selected Network and the RAT (NB-IoT or WB-E-UTRAN). If that MME is not associated with that eNodeB or the GUMMEI is not available or the UE indicates that the TAU procedure was triggered by load re-balancing, the eNodeB selects an MME as described in clause 4.3.8.3 on "MME Selection Function". The eNodeB forwards the TAU Request message together with the CSG access mode, CSG ID, TAI+ECGI of the cell from where it received the message and with the Selected Network to the new MME. CSG ID is provided by RAN if the UE sends the TAU Request message via a CSG cell or a hybrid cell. CSG access mode is provided if the UE sends the TAU Request message via a hybrid cell. If the CSG access mode is not provided but the CSG ID is provided, the MME shall consider the cell as a CSG cell. For SIPTO at the Local Network with stand-alone GW architecture the eNodeB includes the Local Home Network ID in the Initial UE Message and in Uplink NAS Transport message if the target cell is in a Local Home Network. To assist Location Services, the eNodeB indicates the UE's Coverage Level to the MME. If the MME supports RACS, and the MME detects that the selected PLMN is different from the currently registered PLMN for the UE, the MME provides the UE Radio Capability ID of the newly selected PLMN in the UE context to the eNodeB as described in clause 5.11.3a. 4. The new MME differentiates the type of the old node, i.e. MME or SGSN, as specified in clause 4.3.19, uses the GUTI received from the UE to derive the old MME/S4 SGSN address, and sends a Context Request (old GUTI, complete TAU Request message, P-TMSI Signature, MME Address, UE validated, CIoT EPS Optimisation support indication) message to the old MME/old S4 SGSN to retrieve user information. UE Validated indicates that the new MME has validated the integrity protection of the TAU message, e.g. based on native EPS security context for the UE. To validate the Context Request the old MME uses the complete TAU Request message and the old S4 SGSN uses the P-TMSI Signature and responds with an appropriate error if integrity check fails in old MME/S4 SGSN. This shall initiate the security functions in the new MME. If the security functions authenticate the UE correctly, the new MME shall send a Context Request (IMSI, complete TAU Request message, MME Address, UE Validated) message to the old MME/S4 SGSN with the UE Validated set. If the new MME indicates that it has authenticated the UE or if the old MME/old S4 SGSN correctly validates the UE, then the old MME/old S4 SGSN starts a timer. If the UE with emergency bearers is not authenticated in the old MME/old S4 SGSN (in a network supporting unauthenticated UEs) the old MME/old S4 SGSN continues the procedure with sending a Context Response and starting the timer also when it cannot validate the Context Request. If a RLOS attached UE is not successfully authenticated in the old MME, the old MME continues the procedure with sending a Context Response and starting the existing timer also when it cannot validate the Context Request. If the new MME supports CIoT EPS Optimisation, CIoT EPS Optimisation support indication is included in the Context Request indicating support for various CIoT EPS Optimisations (e.g. support for header compression for CP CIoT EPS Optimisation, etc.). 5. If the Context Request is sent to an old MME the old MME responds with a Context Response (IMSI, MSISDN, ME Identity (IMEISV), MM Context, EPS Bearer Context(s), Serving GW signalling Address and TEID(s), ISR Supported, MS Info Change Reporting Action (if available), CSG Information Reporting Action (if available), UE Time Zone, UE Core Network Capability, UE Specific DRX Parameters, Remaining Running Service Gap timer, LTE-M UE Indication) message. If the new MME supports CIoT EPS Optimisation and the use of header compression has been negotiated between the UE and the old MME, the Context Response also includes the Header Compression Configuration which includes the information necessary for the ROHC channel setup but not the RoHC context itself. If the Context Request is sent to an old S4 SGSN the old S4 SGSN responds with a Context Response (MM Context, EPS Bearer Context(s), Serving GW signalling Address and TEID(s), ISR Supported, MS Info Change Reporting Action (if available), CSG Information Reporting Action (if available), UE Time Zone, UE Core Network Capability, UE Specific DRX Parameters). If the source MME has not yet reported a non-zero MO Exception Data Counter to the PDN GW, the Context Response also includes the MO Exception Data Counter as described in TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [43]. The MM Context contains security related information as well as other parameters (including IMSI and ME Identity (if available)) as described in clause 5.7.2 (Information Storage for MME). The unused Authentication Quintets in the MM Context are also maintained in the SGSN. TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [41] gives further details on the transfer of security related information. If the MM Context received with the Context Response message did not include IMEISV and the MME does not already store the IMEISV of the UE, the MME shall retrieve the ME Identity (IMEISV) from the UE. The PDN GW Address and TEID(s) (for GTP-based S5/S8) or GRE Keys (PMIP-based S5/S8 at the PDN GW(s) for uplink traffic) and the TI(s), is part of the EPS Bearer Context. If the UE is not known in the old MME/old S4 SGSN or if the integrity check for the TAU Request message fails, the old MME/old S4 SGSN responds with an appropriate error cause. ISR Supported is indicated if the old MME/old S4 SGSN and associated Serving GW are capable to activate ISR for the UE. If the UE receives emergency bearer services from the old MME/old S4 SGSN and the UE is UICCless, IMSI can not be included in the Context Response. For emergency attached UEs, if the IMSI cannot be authenticated, then the IMSI shall be marked as unauthenticated. Also, in this case, security parameters are included only if available. For a RLOS attached UE, the old MME includes an RLOS indication to the new MME. If the RLOS attached UE in the old MME does not have a USIM, IMSI can not be included in the Context Response. If the RLOS attached UE has USIM but the IMSI cannot be successfully authenticated, then the IMSI shall be marked as unauthenticated. Also, in this case, security parameters are included only if available. If SIPTO at the Local Network is active for a PDN connection in the architecture with stand-alone GW, the old MME/old S4 SGSN shall include the Local Home Network ID of the old cell in the EPS Bearer context corresponding to the SIPTO at the Local Network PDN connection. For UE using CIoT EPS Optimisation without any activated PDN connection, there is no EPS Bearer Context(s) included in the Context Response message. Based on the CIoT EPS Optimisation support indication, old MME only transfers the EPS Bearer Context(s) that the new MME supports. If the new MME does not support CIoT EPS Optimisation, EPS Bearer Context(s) of non-IP PDN connection are not transferred to the new MME. If the new MME does not support Ethernet PDN Type, EPS Bearer Context(s) of Ethernet PDN type are not transferred to the new MME. If the EPS Bearer Context(s) of a PDN connection has not been transferred, the old MME shall consider all bearers of that PDN connection as failed and release that PDN connection by triggering the MME requested PDN disconnection procedure specified in clause 5.10.3. The buffered data in the old MME is discarded after receipt of Context Acknowledgement. If the EPS Bearer Context(s) are to be transferred to the new MME, the old MME also includes the Serving GW IP address and TEID for both S1-U and S11-U, if available. If the Old MME is aware the UE is a LTE-M UE, it provides the LTE-M UE Indication to the new MME. During inter PLMN mobility, the new MME shall delete the UE Radio Capability ID received from the old MME, unless the operator policy indicates that all UE Radio Capability IDs used in the old PLMN are also valid in the new PLMN. 6. If the integrity check of TAU Request message (sent in step 2) failed, then authentication is mandatory. The authentication functions are defined in clause 5.3.10 on "Security Function". Ciphering procedures are described in clause 5.3.10 on "Security Function". If GUTI allocation is going to be done and the network supports ciphering, the NAS messages shall be ciphered. If this TAU request is received for a UE which is already in ECM_CONNECTED state and the PLMN-ID of the TAI sent by the eNodeB in Step 3 is different from that of the GUTI, included in the TAU Request message, the MME shall delay authenticating the UE until after Step 21 (TAU Complete message). NOTE 3: The MME delays the authentication such that the UE first updates its registered PLMN-ID to the new PLMN-ID selected by the RAN during handover. The new PLMN-ID is provided by the MME to the UE as part of the GUTI in the TAU accept message in Step 20. Doing this ensures that the same PLMN-ID is used in the derivation of the Kasme key by both the network and the UE. If the new MME is configured to allow emergency bearer services for unauthenticated UE the new MME behave as follows: - where a UE has only emergency bearer services, the MME either skip the authentication and security procedure or accepts that the authentication may fail and continues the Tracking Area Update procedure; or - where a UE has both emergency and non-emergency bearer services and authentication fails, the MME continues the Tracking Area Update procedure and deactivates all the non-emergency PDN connections as specified in clause 5.10.3. If the new MME is configured to allow Restricted Local Operator Services, the new MME, based on local regulation and operator policy, may skip the authentication and security procedure, or may perform authentication if security parameters are available, or obtainable from HSS, and continues the Tracking Area Update procedure regardless of the authentication result. If the UE indicated it has a UE Radio Capability ID assigned for use in the selected PLMN in step 2, the MME may request the UE to provide the UE Radio Capability ID in Security Mode Command, if the MME needs to get the UE Radio Capability ID from the UE e.g. at inter-PLMN mobility. If enquired by the MME the UE shall include the UE Radio Capability ID in Security Mode Command Accept for the supported UE radio capabilities. 7. The MME (if the MME has changed then it is the new MME) determines to relocate the Serving GW. The Serving GW is relocated when the old Serving GW cannot continue to serve the UE. The MME (if the MME has changed then it is the new MME) may also decide to relocate the Serving GW if a new Serving GW is expected to serve the UE longer and/or with a more optimal UE to PDN GW path, or if a new Serving GW can be co-located with the PDN GW. Selection of a new Serving GW is performed according to clause 4.3.8.2 on "Serving GW selection function". If the MME has changed the new MME sends a Context Acknowledge (Serving GW change indication) message to the old MME/old S4 SGSN. Serving GW change indication indicates a new Serving GW has been selected. The old MME/old S4 SGSN marks in its UE context that the information in the GWs is invalid. And, if the old node is an MME, the old MME marks in its UE context that the information in the HSS is invalid. This ensures that the old MME/old S4 SGSN updates the GWs, and the old MME updates the HSS, if the UE initiates a TAU or RAU procedure back to the old MME/old S4 SGSN before completing the ongoing TAU procedure. NOTE 4: Updating the GWs refers to deletion of session(s) on the Serving GW followed by re-creation of session(s) on the Serving GW. The re-creation of session(s) on the Serving GW will result in successful re-establishment of the S5/S8 tunnel between the selected Serving GW and the PDN GW. If the security functions do not authenticate the UE correctly, then the TAU shall be rejected, and the new MME shall send a reject indication to the old MME/old S4 SGSN. The old MME/old S4 SGSN shall continue as if the Identification and Context Request was never received. ISR is not indicated in the Context Acknowledge as ISR is not activated due to the S-GW change. For UE using CIoT EPS Optimisation without any activated PDN connection, the steps 8, 9, 10, 11, 18 and 19 are skipped. 8. If the MME has changed the new MME verifies the EPS bearer status received from the UE with the bearer contexts received from the old MME/old S4 SGSN. If the MME has not changed the MME verifies EPS bearer status from the UE with the bearer contexts available in the MM context. The MME releases any network resources related to EPS bearers that are not active in the UE. If there is no bearer context at all, the MME rejects the TAU Request. If the MME selected a new Serving GW it sends a Create Session Request (IMSI, MSISDN, bearer contexts, MME Address and TEID, Type, the Protocol Type over S5/S8, RAT type, LTE-M RAT type reporting to PGW flag, Serving Network, UE Time Zone, MO Exception data counter) message per PDN connection to the selected new Serving GW. The PDN GW address and TFT (for PMIP-based S5/S8) are indicated in the bearer Contexts. Type indicates to the Serving GW to send the Modify Bearer Request to the PDN GW. The Protocol Type over S5/S8 is provided to Serving GW which protocol should be used over S5/S8 interface. RAT type indicates a change in radio access. If it is a mobility from a SGSN to a MME and if the MME supports location information change reporting, the MME shall include the User Location Information (according to the supported granularity) in the Create Session Request, regardless of whether location information change reporting had been requested in the previous RAT by the PDN GW. If it is an inter MME mobility and if the PDN GW requested location information change reporting, the MME includes the User Location Information IE in this message if it is different compared to the previously sent information. If the PDN GW requested User CSG information, the MME also includes the User CSG Information IE in this message. If Control Plane CIoT EPS Optimisation applies, the MME may also indicate S11-U tunnelling of NAS user data and send its own S11-U IP address and MME DL TEID for DL data forwarding by the SGW. The MME shall include the MO Exception data counter if it has received the counter for RRC cause "MO Exception data" in the Context Response message. If only the Control Plane CIoT EPS Optimisation is used, the MME shall include a Control Plane Only PDN Connection Indicator in Create Session Request. If the new MME receives the EPS bearer context with SCEF, then the new MME updates the SCEF as defined in TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74]. If the UE is using the LTE-M RAT type and the PDN GW expects the LTE-M RAT type reporting as specified in clause 5.11.5, the MME also includes the LTE-M RAT type reporting to PGW flag to indicate to the Serving GW to forward the LTE-M RAT type to the PDN GW. 9. The Serving GW informs the PDN GW(s) about the change of for example the RAT type that e.g. can be used for charging, by sending the message Modify Bearer Request (Serving GW Address and TEID, RAT type, Serving Network, PDN Charging Pause Support Indication) per PDN connection to the PDN GW(s) concerned. User Location Information IE and/or UE Time Zone IE and/or User CSG Information IE and/or MO Exception data counter are also included if they are present in step 8. The Serving GW and PDN GW indicate each use of the RRC establishment cause "MO Exception Data" by the related counter on its CDR. If the Serving GW has received the Control Plane Only PDN Connection Indicator in step 8, the Serving GW indicates the use of CP only on its CDR. If LTE-M RAT type and the LTE-M RAT type reporting to PGW flag were received at step 8, the Serving GW shall include the LTE-M RAT type in the Modify Bearer Request message to the PGW. Otherwise the Serving GW includes RAT type WB-E-UTRAN. 9a If dynamic PCC is deployed, and RAT type information needs to be conveyed from the PDN GW to the PCRF, then the PDN GW shall send RAT type information to the PCRF by means of an IP-CAN Session Modification procedure as defined in TS 23.203[ Policy and charging control architecture ] [6]. NOTE 5: The PDN GW does not need to wait for the PCRF response, but continues in the next step. If the PCRF response leads to an EPS bearer modification the PDN GW should initiate a bearer update procedure. 10. The PDN GW updates its bearer contexts and returns a Modify Bearer Response (MSISDN, Charging Id, PDN Charging Pause Enabled Indication (if PDN GW has chosen to enable the function)) message. The MSISDN is included if the PDN GW has it stored in its UE context. If there has been a RAT change towards E-UTRAN and location information change reporting is required and supported in the target MME, the PDN GW shall provide MS Info Change Reporting Action in the Modify Bearer Response. If the Serving GW is relocated, the PDN GW shall send one or more "end marker" packets on the old path immediately after switching the path in order to assist the reordering function in the target eNodeB. If the Serving GW has no downlink user plane established, the Serving GW shall discard the "end marker" received from the PDN GW and shall not send Downlink Data Notification. Otherwise the Serving GW shall forward the "end marker" packets to the source eNodeB or source S4 SGSN. 11. The Serving GW updates its bearer context. This allows the Serving GW to route bearer PDUs to the PDN GW when received from eNodeB. The Serving GW returns a Create Session Response (Serving GW address and TEID for user plane and control plane and PDN GW TEIDs (for GTP-based S5/S8) or GRE keys (for PMIP-based S5/S8) for uplink traffic and control plane, MS Info Change Reporting Action) message to the new MME. If Control Plane CIoT EPS Optimisation applies and if the MME does not include Control Plane Only PDN Connection Indicator in the Create Session Request: - If separation of S11-U from S1-U is required, the Serving GW shall include the Serving GW IP address and TEID for S11-U and additionally the Serving GW IP address and TEID for S1-U in the Create Session Response. - Otherwise, if separation of S11-U from S1-U is not required, the Serving GW includes the Serving GW IP address and TEID for S11-U in Create Session Response. When the MME receives the Create Session Response message, the MME checks if there is a "Availability after DDN Failure" monitoring event or a "UE Reachability" monitoring event configured for the UE in the MME and in such a case sends an event notification (see TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74] for further information). 12. The new MME verifies whether it holds subscription data for the UE identified by the GUTI, the additional GUTI or by the IMSI received with the context data from the old CN node. If there are no subscription data in the new MME for this UE, or for some network sharing scenario (e.g. GWCN) if the PLMN-ID of the TAI supplied by the eNodeB is different from that of the GUTI in the UE's context, then the new MME sends an Update Location Request (MME Identity, IMSI, ULR-Flags, MME Capabilities, Homogeneous Support of IMS Voice over PS Sessions, UE SRVCC capability, equivalent PLMN list, ME Identity (IMEISV)) message to the HSS. ULR-Flags indicates that update location is sent from an MME and the MME registration shall be updated in HSS. The HSS does not cancel any SGSN registration. The MME capabilities indicate the MME's support for regional access restrictions functionality. The inclusion of the equivalent PLMN list indicates that the MME supports the inter-PLMN handover to a CSG cell in an equivalent PLMN using the subscription information of the target PLMN. The "Homogenous Support of IMS Voice over PS Sessions" indication (see clause 4.3.5.8A) shall not be included unless the MME has completed its evaluation of the support of "IMS Voice over PS Session" as specified in clause 4.3.5.8. The ME Identity is included if step 5 caused the MME to retrieve the IMEISV from the UE. NOTE 6: At this step, the MME may not have all the information needed to determine the setting of the IMS Voice over PS Session Supported indication for this UE (see clause 4.3.5.8). Hence the MME can send the "Homogenous Support of IMS Voice over PS Sessions" later on in this procedure. If the UE initiates the TAU procedure in a VPLMN supporting Autonomous CSG Roaming and the HPLMN has enabled Autonomous CSG Roaming in the VPLMN (via Service Level Agreement) and the MME needs to retrieve the CSG subscription information of the UE from the CSS, the MME initiates the Update CSG Location Procedure with CSS as described in clause 5.3.12. If the MME determines that only the UE SRVCC capability has changed, the MME sends a Notify Request to the HSS to inform about the changed UE SRVCC capability. If all the EPS bearers of the UE have emergency ARP value, the new MME may skip the update location procedure or proceed even if the update location fails. If the UE is RLOS attached, the new MME skips the Update Location procedure. 13. The HSS sends the message Cancel Location (IMSI, Cancellation Type) to the old MME with Cancellation Type set to Update Procedure. 14. If the timer started in step 4 is not running, the old MME removes the MM context. Otherwise, the contexts are removed when the timer expires. It also ensures that the MM context is kept in the old MME for the case the UE initiates another TAU procedure before completing the ongoing TAU procedure to the new MME. The old MME acknowledges with the message Cancel Location Ack (IMSI). 15. When old S4 SGSN receives the Context Acknowledge message and if the UE is in Iu Connected, the old S4 SGSN sends an Iu Release Command message to the RNC after the timer started in step 4 has expired. 16. The RNC responds with an Iu Release Complete message. 17. The HSS acknowledges the Update Location Request message by sending an Update Location Ack (IMSI, Subscription Data) message to the new MME. The Subscription Data may contain the CSG subscription data for the registered PLMN and for the equivalent PLMN list requested by MME in step 12. The subscription data may contain Enhanced Coverage Restricted parameter. If received from the HSS, MME stores this Enhanced Coverage Restricted parameter in the MME MM context. The subscription data may contain a Service Gap Time. If received from the HSS, the MME stores this Service Gap Time in the MME MM context for the UE and passes it to the UE in the Tracking Area Update Accept message. The subscription data may contain Subscribed Paging Time Window parameter that applies to the UEs on a specific RAT, e.g. NB-IoT. If received from the HSS, MME stores this Subscribed Paging Time Window parameter in the MME MM context. If the Update Location is rejected by the HSS, the new MME rejects the TAU Request from the UE with an appropriate cause. In such cases, the new MME releases any local MME EPS Bearer contexts for this particular UE, and additionally deletes the EPS bearer resources in the new Serving GW by sending the Delete Session Request (Cause, Operation Indication) messages to the new Serving GW. The Operation Indication flag shall not be set. Therefore, the new Serving GW receiving this request shall not initiate a delete procedure towards the PDN GW. If the UE initiates the TAU procedure at a CSG cell, the new MME shall check whether the CSG ID and associated PLMN is contained in the CSG subscription and is not expired. If the CSG ID and associated PLMN is not present or expired, the MME shall send a Tracking Area Update reject message to the UE with an appropriate cause value. The UE shall remove the CSG ID and associated PLMN from its Allowed CSG list if present. If the UE has ongoing emergency bearer services no CSG access control shall be performed. If all checks are successful then the new MME constructs a context for the UE. 18. If the MME has changed, when the timer started in step 4 expires the old MME/old S4 SGSN releases any local MME or SGSN bearer resources and additionally the old MME/old S4 SGSN deletes the EPS bearer resources by sending the Delete Session Request (Cause, Operation Indication) messages to the old Serving GW if it received the Serving GW change indication in the Context Acknowledge message in step 7. When the Operation Indication flag is not set, that indicates to the old Serving GW that the old Serving GW shall not initiate a delete procedure towards the PDN GW. If ISR is activated the Cause indicates to the old S-GW that the old S-GW shall delete the bearer resources on the other old CN node by sending Delete Bearer Request message(s) to that CN node. If the MME has not changed, step 11 triggers the release of the EPS bearer resources at the old Serving GW. 19. The Serving GW acknowledges with Delete Session Response (Cause) messages. The Serving GW discards any packets buffered for the UE. 20. If due to regional subscription restrictions or access restrictions (e.g. CSG restrictions) (received in update location procedure in step 17) the UE is not allowed to access the TA: - The MME rejects the Tracking Area Update Request with an appropriate cause to the UE. - For UEs with emergency EPS bearers, i.e. at least one EPS bearer has an ARP value reserved for emergency services, the new MME accepts the Tracking Area Update Request and deactivates all non-emergency PDN connections as specified in clause 5.10.3. If the Tracking Area Update procedure is initiated in ECM-IDLE state, all non-emergency EPS bearers are deactivated by the Tracking Area Update procedure without bearer deactivation signalling between the UE and the MME. If the TAU request message includes Paging Restriction Information, the MME may accept or reject the Paging Restriction Information requested by the UE based on operator policy. If the MME rejects the Paging Restriction Information, the MME removes any stored Paging Restriction Information from the UE context and discards the UE requested Paging Restriction Information. If the MME accepts the Paging Restriction Information from the UE, the MME stores the Paging Restriction Information from the UE in the UE context and then enforces it in the Network Triggered Service Request procedure as described in clause 5.3.4.3. The MME informs the UE about the acceptance/rejection of the requested Paging Restriction Information in the TAU Accept message. If the TAU Request message does not include any Paging Restriction Information, the MME shall delete any stored Paging Restriction Information for this UE and stop restricting paging accordingly. If the TAU Request message includes a Release Request indication, the MME does not activate the user plane setup procedure in the subsequent steps and triggers the S1 release procedure as described in clause 5.3.5 after the completion of TAU procedure. The MME sends a TAU Accept (GUTI, TAI list, EPS bearer status, NAS sequence number, NAS-MAC, IMS Voice over PS session supported, Emergency Service Support indicator, LCS Support Indication, Supported Network Behaviour, Service Gap Time, Enhanced Coverage Restricted, Indication of support of 15 EPS bearers per UE, PLMN-assigned UE Radio Capability ID, indication for PLMN-assigned UE Radio Capability ID deletion, Accepted IMSI Offset, Connection Release Supported, Paging Cause Indication for Voice Service Supported, Reject Paging Request Supported, Paging Restriction Supported, Paging Timing Collision Control Supported, Paging Restriction Information acceptance/rejection, Forbidden TAI(s), Enhanced Discontinuous Coverage Support, Return To Coverage Notification Not Required, Unavailability Period Duration, Start of Unavailability Period, Maximum Time Offset) message to the UE. If the active flag is set the MME may provide the eNodeB with Handover Restriction List. GUTI is included if the MME allocates a new GUTI. If the active flag is set in the TAU Request message the user plane setup procedure can be activated in conjunction with the TAU Accept message. If the DL Data Buffer Expiration Time for the UE in the MME has not expired, the user plane setup procedure is activated even if the MME did not receive the active flag in the TAU Request message. If the new MME receives the Downlink Data Notification message or any downlink signalling message while the UE is still connected, the user plane setup procedure may be activated even if the new MME did not receive the active flag in the TAU Request message. The procedure is described in detail in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. The message sequence should be the same as for the UE triggered Service Request procedure specified in clause 5.3.4.1 from the step when MME establishes the bearer(s). The MME indicates the EPS bearer status IE to the UE. The UE removes any internal resources related to bearers that are not marked active in the received EPS bearer status. If the EPS bearer status information was in the TAU Request, the MME shall indicate the EPS bearer status to the UE. Handover Restriction List is described in clause 4.3.5.7 "Mobility Restrictions". The MME sets the IMS Voice over PS session supported as described in clause 4.3.5.8. For UE using CIoT EPS Optimisation without any activated PDN connection, there is no EPS bearer status included in the TAU Accept message. The MME indicates the CIoT EPS Optimisations it supports and prefers in the Supported Network Behaviour information as defined in clause 4.3.5.10. If there is a Service Gap timer running for the UE in the MME, and the active flag or the signalling active flag is received in the TAU Request message, the MME shall ignore the active flag and signalling active flag and not perform any of the actions related to these flags except if the TAU Request message has been received when the UE has a PDN connection for emergency bearer services established or is establishing a PDN connection for emergency bearer services or if the UE is configured to use high priority access (AC 11-15) in selected PLMN. The MME shall include the Service Gap Time in the TAU Accept message if the UE has indicated Service Gap Control capability and either if Service Gap Time was received in step 17 from HSS in the subscription information or if the Service Gap Time in the subscription information has been updated by HSS User Profile management (i.e. the Insert Subscriber Data procedure in clause 5.3.9.2). If the UE included support for restriction of use of Enhanced Coverage in step 1, the MME sends Enhanced Coverage Restricted parameter to the eNodeB in the S1-AP message as defined in clause 4.3.28. The MME also sends the Enhanced Coverage Restricted parameter to the UE in the TAU Accept message. UE shall store Enhanced Coverage Restricted parameter and shall use the value of Enhanced Coverage Restricted parameter to determine if enhanced coverage feature should be used or not. If the MME successfully obtained Header Compression Configuration parameters in step 5 it indicates the continued use of previous negotiated configuration to the UE in the Header Compression Context Status for each EPS Bearer of the UE. When Header Compression Context Status indicates that the previous negotiated configuration can no longer be used for some EPS bearers, the UE shall stop performing header compression and decompression, when sending or receiving data using Control Plane CIoT EPS Optimisation on these EPS bearers. If the MME did not receive the Voice Support Match Indicator in the MM Context, then the MME may send a UE Radio Capability Match Request to the eNodeB as described in clause 5.3.14. If the MME hasn't received Voice Support Match Indicator from the eNodeB then, based on implementation, MME may set IMS Voice over PS session supported Indication and update it at a later stage. After step 12, and in parallel to any of the preceding steps, the MME shall send a Notify Request (Homogeneous Support of IMS Voice over PS Sessions) message to the HSS: - If the MME has evaluated the support of IMS Voice over PS Sessions, see clause 4.3.5.8, and - If the MME determines that it needs to update the Homogeneous Support of IMS Voice over PS Sessions, see clause 4.3.5.8A. The Emergency Service Support indicator informs the UE that Emergency bearer services are supported. LCS Support Indication indicates whether the network supports the EPC-MO-LR and/or CS-MO-LR as described in TS 23.271[ Functional stage 2 description of Location Services (LCS) ] [57]. Indication for support of 15 EPS bearers per UE indicates the network support for up to 15 EPS bearers per UE as defined in clause 4.12. If the UE included extended idle mode DRX parameters information element, the MME includes extended idle mode DRX parameters information element if it decides to enable extended idle mode DRX with Paging Time Window length assigned considering Subscribed Paging Time Window (if available) and the local policy. Additionally, for a UE using an eNodeB that provides discontinuous coverage (e.g. for satellite access with discontinuous coverage), the MME may consider Unavailability Period Duration and/or Start of Unavailability Period as described in clause 4.13.8.2 when determining idle mode DRX parameters. If the UE provided the UE paging probability information in Step 2, the MME takes it into account when generating the WUS Assistance Information. If the MME has determined WUS Assistance Information for the UE, the MME shall send the WUS Assistance Information to the UE (see TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]). When receiving the TAU Accept message and there is no ISR Activated indication the UE shall set its TIN to "GUTI". For a S-GW change, ISR Activated is never indicated by the MME as it needs a RAU with the same S-GW first to activate ISR. For an MME change, ISR is not activated by the new MME to avoid context transfer procedures with two old CN nodes. If the TAU procedure is initiated by manual CSG selection and occurs via a CSG cell, the UE upon receiving the TAU Accept message shall add the CSG ID and associated PLMN to its Allowed CSG list if it is not already present. Manual CSG selection is not supported if the UE has emergency bearers established. If the user plane setup is performed in conjunction with the TAU Accept message and the TAU is performed via a hybrid cell, then the MME shall send an indication whether the UE is a CSG member to the RAN along with the S1-MME control message. Based on this information, the RAN may perform differentiated treatment for CSG and non-CSG members. NOTE 7: If the UE receives a TAU Accept message via a hybrid cell, the UE does not add the corresponding CSG ID and associated PLMN to its Allowed CSG list. Adding a CSG ID and associated PLMN to the UE's local Allowed CSG list for a hybrid cell is performed only by OTA or OMA DM procedures. If the UE receives a Service Gap Time in the TAU Accept message, the UE shall store this parameter and apply Service Gap Control (see clause 4.3.17.9). If the UE has indicated support for dual connectivity with NR in the TAU Request and the UE is not allowed to use NR as Secondary RAT, the MME indicates that to the UE in the TAU Accept message. If the user plane setup is performed and if RACS is supported and MME has UE Radio Capability ID in UE context, valid for the PLMN the UE is currently in, it signals the UE Radio Capability ID to the eNodeB as defined in clause 5.11.3a. If the eNodeB does not have mapping between the specific UE Radio Capability ID and the UE radio capabilities, it shall use the procedure described in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36] to retrieve the mapping from the Core Network. When the UE supports RACS, and the MME needs to configure the UE with a UE Radio Capability ID, and the MME already has the UE radio capabilities for the UE, the MME may provide the UE with the UE Radio Capability ID for the UE radio capabilities the UCMF returns to the MME for this UE. If the UE had included a UE Specific DRX parameter for NB-IoT in the Tracking Area Update Request, the MME includes the Accepted NB-IoT DRX parameter. If the UE provided a Requested IMSI Offset in step 2, but the network prefers a different value, the MME provides the UE with an Accepted IMSI Offset different from the one provided in step 2. Otherwise the value of the Accepted IMSI Offset the MME sends is the value of the Requested IMSI Offset sent by the UE in step 2. The MME stores the value of the alternative IMSI derived (see clause 4.3.33) from the Accepted IMSI Offset provided to the UE in the UE context. If a Multi-USIM UE does not provide a Requested IMSI Offset in step 1, the MME erases any alternative IMSI value in the UE context. NOTE 8: The MME does not remove IMSI Offset value if the Tracking Area Update Request is for periodic Tracking Area Update. If the Multi-USIM UE has indicated one or more Multi-USIM specific Capabilities are supported in the UE Core Network Capability in step 2, the MME shall indicate whether the corresponding one or more Multi-USIM specific features described in clause 4.3.33 are supported based on network capability and preference by the network (based on local network policy) by providing one or more of the Connection Release Supported, Paging Cause Indication for Voice Service Supported, Reject Paging Request Supported, Paging Restriction Supported and Paging Timing Collision Control Supported indications. The MME shall only indicate Paging Restriction Supported together with either Connection Release Supported or Reject Paging Request Supported. The UE shall only use Multi-USIM specific features that the MME indicated as being supported. In the case of Emergency attached UE, the MME shall not indicate support for any Multi-USIM feature to the UE. If the MME receives multiple TAIs from E-UTRAN in step 3 and determines that some, but not all, TAIs in the received list of TAIs are forbidden by subscription or by operator policy, the MME shall include the forbidden TAI(s) in the TAU Accept message. If both UE and network support discontinuous coverage, the MME provides the Enhanced Discontinuous Coverage Support indication as described in clause 4.13.8.1. For a UE using an eNodeB that provides discontinuous coverage (e.g. for satellite access with discontinuous coverage), the MME may provide Return To Coverage Notification Not Required, which requests the UE in ECM_IDLE state to not perform the TAU procedure when it returns to coverage, and/or provide the UE with an Unavailability Period Duration and/or Start of Unavailability Period if available, as described in clause 4.13.8.2. The MME may also provide a Maximum Time Offset as described in clause 4.13.8.6. 21. If GUTI was included in the TAU Accept, or the MME indicates an Accepted IMSI Offset to the UE in step 20, the UE acknowledges the received message by returning a TAU Complete message to the MME. When the "Active flag" is not set in the TAU Request message and the Tracking Area Update was not initiated in ECM-CONNECTED state, the new MME releases the signalling connection with UE, according to clause 5.3.5. For a UE using Control Plane CIoT EPS Optimisation, when the "Signalling active flag" is set, the new MME shall not release the NAS signalling connection with the UE immediately after the TAU procedure is completed. NOTE 9: The new MME may initiate E-RAB establishment (see TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]) after execution of the security functions, or wait until completion of the TA update procedure. For the UE, E-RAB establishment may occur any time after the TA update request is sent. In the case of a rejected tracking area update operation, due to regional subscription, roaming restrictions or access restrictions (see TS 23.221[ Architectural requirements ] [27] and TS 23.008[ Organization of subscriber data ] [28]) the new MME should not construct an MM context for the UE. In the case of receiving the subscriber data from HSS, the new MME may construct an MM context and store the subscriber data for the UE to optimise signalling between the MME and the HSS. A reject shall be returned to the UE with an appropriate cause and the S1 connection shall be released. Upon return to idle, the UE shall act according to TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [10]. The new MME shall determine the Maximum APN restriction based on the received APN Restriction of each bearer context in the Context Response message and then store the new Maximum APN restriction value. The bearer contexts shall be prioritized by the new MME. If the new MME is unable to support the same number of active bearer contexts as received from old MME/SGSN, the prioritisation is used to decide which bearer contexts to maintain active and which ones to delete. In any case, the new MME shall first update all contexts in one or more P-GWs and then deactivate the bearer context(s) that it cannot maintain as described in the clause "MME Initiated Dedicated Bearer Deactivation Procedure". This shall not cause the MME to reject the tracking area update. The new MME shall not deactivate emergency service related EPS bearers, i.e. EPS bearers with ARP value reserved for emergency services. NOTE 10: If MS (UE) was in PMM-CONNECTED state the bearer contexts are sent already in the Forward Relocation Request message as described in the clause "Serving RNS relocation procedures" of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. If the tracking area update procedure fails a maximum allowable number of times, or if the MME returns a Tracking Area Update Reject (Cause) message, the UE shall enter EMM DEREGISTERED state. If the new MME identifies that the RAT type has changed, the MME checks the subscription information to identify for each APN whether to maintain the PDN connection, disconnect the PDN connection with a reactivation request, or, disconnect the PDN connection without reactivation request. If the MME decides to deactivate a PDN connection it performs MME-initiated PDN Connection Deactivation procedure after the tracking area update procedure is completed but before the S1/RRC interface connection is released. Existing ESM cause values as specified in TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46] (e.g. #39, "reactivation requested"; #66 "Requested APN not supported in current RAT and PLMN combination"; and for a dedicated bearer, possibly #37 "EPS QoS not accepted") are used to cause predictable UE behaviour. If all the PDN connections are disconnected and the UE does not support "attach without PDN connectivity", the MME shall request the UE to detach and reattach. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.3.1 |
5,230 | 6.5.4.5 Abnormal cases in the UE | The following abnormal cases can be identified: a) Expiry of timer T3481: On the first expiry of the timer T3481, the UE shall resend the BEARER RESOURCE MODIFICATION REQUEST and shall reset and restart timer T3481. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3481, the UE shall abort the procedure, release the PTI allocated for this activation and enter the state PROCEDURE TRANSACTION INACTIVE. In addition, if the UE had initiated resource release for all the traffic flows for the bearer, it shall deactivate the EPS bearer context locally without peer-to-peer signalling between the UE and the MME. In order to synchronize the EPS bearer context status with the MME, on indication of "back to E-UTRAN coverage" from the lower layers, the UE shall send a TRACKING AREA UPDATE REQUEST message that includes the EPS bearer context status IE to the MME. b) Unknown EPS bearer context: Upon receipt of the BEARER RESOURCE MODIFICATION REJECT message including ESM cause #43 "invalid EPS bearer identity", the UE shall deactivate the existing EPS bearer context locally without peer-to-peer signalling between the UE and the MME and shall stop the timer T3481. c) Collision of a UE requested bearer resource modification procedure and an EPS bearer context deactivation procedure: When the UE receives a DEACTIVATE EPS BEARER CONTEXT REQUEST message during the bearer resource modification procedure, and the EPS bearer identity indicated in the DEACTIVATE EPS BEARER CONTEXT REQUEST message is an EPS bearer context the UE indicated in the UE requested bearer resource modification procedure, then the UE shall abort the UE requested bearer resource modification procedure and shall stop the timer T3481 and proceed with the EPS bearer context deactivation procedure. d) Rejection of a UE requested bearer resource modification procedure when the UE has initiated the procedure to release all traffic flows for the bearer: Upon receipt of a BEARER RESOURCE MODIFICATION REJECT message with ESM cause value #31 "request rejected, unspecified", if the UE had initiated resource release for all the traffic flows for the bearer, it shall deactivate the EPS bearer context locally without peer-to-peer signalling between the UE and the MME and shall stop the timer T3481. In order to synchronize the EPS bearer context status with the MME, the UE may send a TRACKING AREA UPDATE REQUEST message that includes the EPS bearer context status IE to the MME. e) Collision of UE requested bearer resource modification procedure and EPS bearer context modification procedure: The handling of the same abnormal case as described in clause 6.4.3.5 applies. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.5.4.5 |
5,231 | A.3.4 Information elements | Each IE (information element) type is specified in an ASN.1 clause similar to the one shown in the example below. -- /example/ ASN1START PRACH-ConfigSIB ::= SEQUENCE { rootSequenceIndex INTEGER (0..1023), prach-ConfigInfo PRACH-ConfigInfo } PRACH-Config ::= SEQUENCE { rootSequenceIndex INTEGER (0..1023), prach-ConfigInfo PRACH-ConfigInfo OPTIONAL -- Need N } PRACH-ConfigInfo ::= SEQUENCE { prach-ConfigIndex ENUMERATED {ffs}, highSpeedFlag ENUMERATED {ffs}, zeroCorrelationZoneConfig ENUMERATED {ffs} } -- ASN1STOP IEs should be introduced whenever there are multiple fields for which the same set of values apply. IEs may also be defined for other reasons e.g. to break down a ASN.1 definition in to smaller pieces. A group of closely related IE type definitions, like the IEs PRACH-ConfigSIB and PRACH-Config in this example, are preferably placed together in a common ASN.1 clause. The IE type identifiers should in this case have a common base, defined as the generic type identifier. It may be complemented by a suffix to distinguish the different variants. The "PRACH-Config" is the generic type identifier in this example, and the "SIB" suffix is added to distinguish the variant. The clause heading and generic references to a group of closely related IEs defined in this way should use the generic type identifier. The same principle should apply if a new version, or an extension version, of an existing IE is created for critical or non-critical extension of the protocol (see clause A.4). The new version, or the extension version, of the IE is included in the same ASN.1 clause defining the original. A suffix is added to the type identifier, using the naming conventions defined in clause A.3.1.2, indicating the release or version of the where the new version, or extension version, was introduced. Local IE type definitions, like the IE PRACH-ConfigInfo in the example above, may be included in the ASN.1 clause and be referenced in the other IE types defined in the same ASN.1 clause. The use of locally defined IE types should be encouraged, as a tool to break up large and complex IE type definitions. It can improve the readability of the code. There may also be a benefit for the software implementation of the protocol end-points, as these IE types are typically provided by the ASN.1 compiler as independent data elements, to be used in the software implementation. An IE type defined in a local context, like the IE PRACH-ConfigInfo, should not be referenced directly from other ASN.1 clauses in the RRC specification. An IE type which is referenced in more than one ASN.1 clause should be defined in a separate clause, with a separate heading and a separate ASN.1 clause (possibly as one in a set of closely related IE types, like the IEs PRACH-ConfigSIB and PRACH-Config in the example above). Such IE types are also referred to as 'global IEs'. NOTE: Referring to an IE type, that is defined as a local IE type in the context of another ASN.1 clause, does not generate an ASN.1 compilation error. Nevertheless, using a locally defined IE type in that way makes the IE type definition difficult to find, as it would not be visible at an outline level of the specification. It should be avoided. The ASN.1 clause specifying the contents of one or more IE types, like in the example above, may be followed by a field description table, where a further description of, e.g., the semantic properties of the fields of the information elements may be included. This table may be absent, similar as indicated in clause A.3.3 for the specification of the PDU type. The general format of the field description table is the same as shown in clause A.3.3 for the specification of the PDU type. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | A.3.4 |
5,232 | 16.12.5.1 RRC Connection Management | The L2 U2N Remote UE needs to establish its own PDU sessions/DRBs with the network before user plane data transmission. The NR sidelink PC5 unicast link establishment procedures can be used to setup a secure unicast link between L2 U2N Remote UE and L2 U2N Relay UE before L2 U2N Remote UE establishes a Uu RRC connection with the network via L2 U2N Relay UE. The establishment of Uu SRB1/SRB2 and DRB of the L2 U2N Remote UE is subject to Uu configuration procedures for L2 UE-to-Network Relay. The following high level connection establishment procedure in Figure 16.12.5.1-1 applies to a L2 U2N Relay and L2 U2N Remote UE: Figure 16.12.5.1-1: Procedure for L2 U2N Remote UE connection establishment 1. The L2 U2N Remote and L2 U2N Relay UE perform discovery procedure, and establish a PC5-RRC connection using the NR sidelink PC5 unicast link establishment procedure. 2. The L2 U2N Remote UE sends the first RRC message (i.e., RRCSetupRequest) for its connection establishment with gNB via the L2 U2N Relay UE, using a specified PC5 Relay RLC channel configuration. The L2 U2N Relay UE sends the SidelinkUEInformationNR message to request for the dedicated configurations required to support the relay operation for the L2 U2N Remote UE. If the L2 U2N Relay UE is not in RRC_CONNECTED, it needs to do its own Uu RRC connection establishment upon reception of a message on the specified PC5 Relay RLC channel. After L2 U2N Relay UE's RRC connection establishment procedure and sending the SidelinkUEInformationNR message, gNB configures SRB0 relaying Uu Relay RLC channel to the U2N Relay UE. The gNB responds with an RRCSetup message to L2 U2N Remote UE. The RRCSetup message is sent to the L2 U2N Remote UE using SRB0 relaying Uu Relay RLC channel over Uu and a specified PC5 Relay RLC channel over PC5. NOTE 1: Void. 3. The gNB and L2 U2N Relay UE perform relaying channel setup procedure over Uu. According to the configuration from gNB, the L2 U2N Relay/Remote UE establishes a PC5 Relay RLC channel for relaying of SRB1 towards the L2 U2N Remote/Relay UE over PC5. 4. The RRCSetupComplete message is sent by the L2 U2N Remote UE to the gNB via the L2 U2N Relay UE using SRB1 relaying channel over PC5 and SRB1 relaying channel configured to the L2 U2N Relay UE over Uu. Then the L2 U2N Remote UE is as in RRC_CONNECTED with the gNB. 5. The L2 U2N Remote UE and gNB establish security following the Uu security mode procedure and the security messages are forwarded through the L2 U2N Relay UE. 6. The gNB sends an RRCReconfiguration message to the L2 U2N Remote UE via the L2 U2N Relay UE, to setup the end-to-end SRB2/DRBs of the L2 U2N Remote UE. The L2 U2N Remote UE sends an RRCReconfigurationComplete message to the gNB via the L2 U2N Relay UE as a response. In addition, the gNB may configure additional Uu Relay RLC channels between the gNB and L2 U2N Relay UE, and PC5 Relay RLC channels between L2 U2N Relay UE and L2 U2N Remote UE for the relaying traffic. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.12.5.1 |
5,233 | 7.7.1D Minimum requirements for ProSe | The throughput shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annex A.6.2 with parameters specified in Tables 7.7.1D-1, 7.7.1D-2, and 7.7.1D-3. Table 7.7.1D-1: Spurious response parameters for ProSe Direct Discovery Table 7.7.1D-2: Spurious response parameters for ProSe Direct Communication Table 7.7.1D-3: Spurious response for ProSe For the UE which supports inter-band CA configuration in Table 7.3.1-1A, Pinterferer power defined in Table 7.7.1D-3 is increased by the amount given by ΔRIB,c in Table 7.3.1-1A. | 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.7.1D |
5,234 | – LTM-CSI-ResourceConfig | The IE LTM-CSI-ResourceConfig defines a group of one or more CSI resources for one or more LTM candidate configurations. LTM-CSI-ResourceConfig information element -- ASN1START -- TAG-LTM-CSI-RESOURCECONFIG-START LTM-CSI-ResourceConfig-r18 ::= SEQUENCE { ltm-CSI-ResourceConfigId-r18 LTM-CSI-ResourceConfigId-r18, ltm-CSI-SSB-ResourceSet-r18 LTM-CSI-SSB-ResourceSet-r18, ... } LTM-CSI-SSB-ResourceSet-r18 ::= SEQUENCE { ltm-CSI-SSB-ResourceList-r18 SEQUENCE (SIZE (1..maxNrofLTM-CSI-SSB-ResourcesPerSet-r18)) OF SSB-Index, ltm-CandidateIdList-r18 SEQUENCE (SIZE (1..maxNrofLTM-CSI-SSB-ResourcesPerSet-r18)) OF LTM-CandidateId-r18, ... } -- TAG-LTM-CSI-RESOURCECONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,235 | 4.9 Disabling and re-enabling of UE's NB-IoT capability | If the UE supports disabling and re-enabling of UE's NB-IoT capability and the UE in NB-S1 mode is disabling the NB-IoT capability, it should proceed as follows: a) select E-UTRAN, or for the UE which supports CIoT EPS optimization select satellite E-UTRAN via "WB-E-UTRAN(LEO)", "WB-E-UTRAN(MEO)", or "WB-E-UTRAN(GEO)", of the registered PLMN or a PLMN from the list of equivalent PLMNs; b) if E-UTRAN, or for the UE which supports CIoT EPS optimization if satellite E-UTRAN via "WB-E-UTRAN(LEO)", "WB-E-UTRAN(MEO)", or "WB-E-UTRAN(GEO)", of the registered PLMN or a PLMN from the list of equivalent PLMNs cannot be found, select another RAT (GERAN, UTRAN, or NG-RAN if the UE has not disabled its N1 mode capability for 3GPP access as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54]) of the registered PLMN or a PLMN from the list of equivalent PLMNs; c) if another RAT of the registered PLMN or a PLMN from the list of equivalent PLMNs cannot be found, or the UE does not have a registered PLMN, then perform PLMN selection as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. As an implementation option, instead of performing PLMN selection, the UE may select another RAT of the chosen PLMN; or d) if no other allowed PLMN and RAT combinations are available, then the UE may re-enable the NB-IoT capability and remain registered for EPS services in NB-IoT of the registered PLMN. If the UE chooses this option, then it may periodically attempt to select another PLMN and RAT combination that can provide non-EPS services. How this periodic scanning is done, is UE implementation dependent. If the NB-IoT capability is disabled, the UE shall re-enable the NB-IoT capability when: - performing a PLMN selection unless the UE has already re-enabled the NB-IoT capability when performing bullet c) or d) above; or - the UE powers off and powers on again or the USIM is removed. If the UE in NB-S1 mode receives an ATTACH REJECT or TRACKING AREA UPDATE REJECT message including both EMM cause #15 "no suitable cells in tracking area" and an Extended EMM cause IE with value "NB-IoT not allowed" after the UE requests access to the NB-IoT, in order to prevent unwanted cell reselection from GERAN, UTRAN, E-UTRAN or NG-RAN to NB-IoT, the UE may: - disable the NB-IoT capability: - indicate the access stratum layer(s) of disabling of the NB-IoT capability; and - memorize the identity of the PLMN where the NB-IoT capability was disabled and use that stored information in subsequent PLMN selections as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. NOTE: The UE can only disable the NB-IoT capability when in EMM-IDLE mode. If the UE in NB-S1 mode is required to disable the NB-IoT capability and select E-UTRAN radio access technology, and the UE is in the EMM-CONNECTED mode, the UE shall locally release the established NAS signalling connection and enter the EMM-IDLE mode before selecting E-UTRAN radio access technology. As an implementation option, the UE may start a timer for enabling the NB-IoT capability. On expiry of this timer, the UE may enable the NB-IoT capability. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.9 |
5,236 | 5.6.3 Notification procedure 5.6.3.1 General | The notification procedure is used by the network: a) to request the UE, by sending the NOTIFICATION message over 3GPP access, to re-establish the user-plane resources of PDU session(s) associated with non-3GPP access over 3GPP access or to deliver 5GSM downlink signalling messages associated with non-3GPP access over 3GPP access when the UE is in 5GMM-IDLE mode over non-3GPP access and in 5GMM-CONNECTED mode over 3GPP access; or b) to request the UE, by sending the NOTIFICATION message over non-3GPP access, to re-establish user-plane resources of the PDU session(s) or to deliver downlink signalling associated with 3GPP access over 3GPP access when the UE is in 5GMM-CONNECTED mode over non-3GPP access and: 1) in 5GMM-IDLE mode over 3GPP access when the UE is not in MICO mode; or 2) in 5GMM-IDLE mode with suspend indication over 3GPP access when the UE is not in MICO mode. The network shall not use the NOTIFICATION message to re-establish user-plane resources of PDU session(s) associated with non-3GPP access over 3GPP access if all the PDU sessions of the UE that are established over the 3GPP access are associated with control plane only indication. . The network shall not use the NOTIFICATION message over non-3GPP access, if: a) the MUSIM UE supports the paging indication for voice services; b) the network has indicated "paging indication for voice services supported" to the UE; and c) the AMF detects that the downlink data is related to voice service (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]). | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.6.3 |
5,237 | 9.2.1.1 FDD | The following requirements apply to UE Category ≥1. For the parameters specified in Table 9.2.1.1-1 and Table 9.2.1.1-2, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2, the reported CQI value according to RC.1 FDD / RC.14 FDD in Table A.4-1 shall be in the range of ±1 of the reported median more than 90% of the time. If the PDSCH BLER using the transport format indicated by median CQI is less than or equal to 0.1, the BLER using the transport format indicated by the (median CQI + 1) shall be greater than 0.1. If the PDSCH BLER using the transport format indicated by the median CQI is greater than 0.1, the BLER using transport format indicated by (median CQI – 1) shall be less than or equal to 0.1. The applicability of the requirement with 5MHz bandwidth as specificed in Table 9.2.1.1-2 is defined in 9.1.1.1. Table 9.2.1.1-1: PUCCH 1-0 static test (FDD) Table 9.2.1.1-2: PUCCH 1-0 static test (FDD 5MHz) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.2.1.1 |
5,238 | 5.5.2.1.2 Preparation phase | Figure 5.5.2.1.2-1: E-UTRAN to UTRAN Iu mode Inter RAT HO, preparation phase 1. The source eNodeB decides to initiate an Inter-RAT handover to the target access network, UTRAN Iu mode. At this point both uplink and downlink user data is transmitted via the following: Bearer(s) between UE and source eNodeB, GTP tunnel(s) between source eNodeB, Serving GW and PDN GW. If the UE has an ongoing emergency bearer service the source eNodeB shall not initiate PS handover to a UTRAN cell that is not IMS voice capable. NOTE 1: The process leading to the handover decision is outside of the scope of this specification. 2. The source eNodeB sends a Handover Required (S1AP Cause, Target RNC Identifier, CSG ID, CSG access mode, Source to Target Transparent Container) message to the source MME to request the CN to establish resources in the target RNC, target SGSN and the Serving GW. The bearers that will be subject to data forwarding (if any) are identified by the target SGSN in a later step (see step 7 below). When the target cell is a CSG cell or a hybrid cell, the source eNodeB shall include the CSG ID of the target cell. If the target cell is a hybrid cell, the CSG access mode shall be indicated. 3. The source MME determines from the 'Target RNC Identifier' IE that the type of handover is IRAT Handover to UTRAN Iu mode. The source MME selects the target SGSN as described in clause 4.3.8.4 on "SGSN Selection Function". The Source MME initiates the Handover resource allocation procedure by sending a Forward Relocation Request (IMSI, Target Identification, CSG ID, CSG Membership Indication, MM Context, PDN Connections, MME Tunnel Endpoint Identifier for Control Plane, MME Address for Control plane, Source to Target Transparent Container, RAN Cause, MS Info Change Reporting Action (if available), CSG Information Reporting Action (if available), UE Time Zone, ISR Supported, Serving Network) message to the target SGSN. The information ISR Supported is indicated if the source MME and associated Serving GW are capable to activate ISR for the UE. When ISR is activated the message should be sent to the SGSN that maintains ISR for the UE when this SGSN is serving the target identified by the Target Identification. This message includes all PDN Connections active in the source system and for each PDN Connection includes the associated APN, the address and the uplink Tunnel endpoint parameters of the Serving GW for control plane, and a list of EPS Bearer Contexts. RAN Cause indicates the S1AP Cause as received from source eNodeB. The old Serving Network is sent to target MME to support the target MME to resolve if Serving Network is changed. The source MME shall perform access control by checking the UE's CSG subscription when CSG ID is provided by the source eNodeB. If there is no subscription data for this CSG ID or the CSG subscription is expired, and the target cell is a CSG cell, the source MME shall reject the handover with an appropriate cause unless the UE has emergency bearer services. The source MME includes the CSG ID in the Forward Relocation Request when the target cell is a CSG cell or hybrid cell. When the target cell is a hybrid cell, or if there are one or several emergency bearers and the target cell is a CSG cell, the CSG Membership Indication indicating whether the UE is a CSG member shall be included in the Forward Relocation Request message. The MM context includes information on the EPS Bearer context(s). The source MME does not include any EPS Bearer Context information for "Non-IP" bearers or for any SCEF connection. If none of the UE's EPS Bearers can be supported by the selected target SGSN, the source MME rejects the handover attempt by sending a Handover Preparation Failure (Cause) message to the Source eNodeB. NOTE 2: If the handover is successful, the source MME will signal to the SGW and/or SCEF to release any non-included EPS Bearers after step 6 of the Execution procedure. The non-included bearers are locally released by the UE following the Bearer Context Status synchronisation that occurs during the Routing Area Update at step 10 of the Execution procedure. The target SGSN maps the EPS bearers to PDP contexts 1-to-1 and maps the EPS Bearer QoS parameter values of an EPS bearer to the Release 99 QoS parameter values of a bearer context as defined in Annex E Prioritization of PDP Contexts is performed by the target core network node, i.e. target SGSN. The MM context contains security related information, e.g. supported ciphering algorithms as described in TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [43]. Handling of security keys is described in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [41]. The target SGSN shall determine the Maximum APN restriction based on the APN Restriction of each bearer context in the Forward Relocation Request, and shall subsequently store the new Maximum APN restriction value. If SIPTO at the Local Network is active for a PDN connection in the architecture with stand-alone GW the source MME shall include the Local Home Network ID of the source cell in the PDN Connections corresponding to the SIPTO at the Local Network PDN connection. 4. The target SGSN determines if the Serving GW is to be relocated, e.g., due to PLMN change. If the Serving GW is to be relocated, the target SGSN selects the target Serving GW as described under clause 4.3.8.2 on "Serving GW selection function", and sends a Create Session Request message (IMSI, SGSN Tunnel Endpoint Identifier for Control Plane, SGSN Address for Control plane, PDN GW address(es) for user plane, PDN GW UL TEID(s) for user plane, PDN GW address(es) for control plane, and PDN GW TEID(s) for control plane, the Protocol Type over S5/S8, Serving Network) per PDN connection to the target Serving GW. The Protocol Type over S5/S8 is provided to Serving GW which protocol should be used over S5/S8 interface. The target SGSN establishes the EPS Bearer context(s) in the indicated order. The SGSN deactivates, as provided in step 7 of the execution phase, the EPS Bearer contexts which cannot be established. 4a. The target Serving GW allocates its local resources and returns a Create Session Response (Serving GW address(es) for user plane, Serving GW UL TEID(s) for user plane, Serving GW Address for control plane, Serving GW TEID for control plane) message to the target SGSN. 5. The target SGSN requests the target RNC to establish the radio network resources (RABs) by sending the message Relocation Request (UE Identifier, Cause, CN Domain Indicator, Integrity protection information (i.e. IK and allowed Integrity Protection algorithms), Encryption information (i.e. CK and allowed Ciphering algorithms), RAB to be setup list, CSG ID, CSG Membership Indication, Source RNC to Target RNC Transparent Container, Service Handover related information). If the Access Restriction is present in the MM context, the Service Handover related information shall be included by the target SGSN for the Relocation Request message in order for RNC to restrict the UE in connected mode to handover to the RAT prohibited by the Access Restriction. For each RAB requested to be established, RABs To Be Setup shall contain information such as RAB ID, RAB parameters, Transport Layer Address, and Iu Transport Association. The RAB ID information element contains the NSAPI value, and the RAB parameters information element gives the QoS profile. The Transport Layer Address is the Serving GW Address for user plane (if Direct Tunnel is used) or the SGSN Address for user plane (if Direct Tunnel is not used), and the Iu Transport Association corresponds to the uplink Tunnel Endpoint Identifier Data in Serving GW or SGSN respectively. Ciphering and integrity protection keys are sent to the target RNC to allow data transfer to continue in the new RAT/mode target cell without requiring a new AKA (Authentication and Key Agreement) procedure. Information that is required to be sent to the UE (either in the Relocation Command message or after the handover completion message) from RRC in the target RNC shall be included in the RRC message sent from the target RNC to the UE via the transparent container. More details are described in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [41]. The Target SGSN shall include the CSG ID and CSG Membership Indication when provided by the source MME in the Forward Relocation Request message. In the target RNC radio and Iu user plane resources are reserved for the accepted RABs. Cause indicates the RAN Cause as received from source MME. The Source RNC to Target RNC Transparent Container includes the value from the Source to Target Transparent Container received from the source eNodeB. If the target cell is a CSG cell, the target RNC shall verify the CSG ID provided by the target SGSN, and reject the handover with an appropriate cause if it does not match the CSG ID for the target cell. If the target cell is in hybrid mode, the target RNC may use the CSG Membership Indication to perform differentiated treatment for CSG and non-CSG members. If the target cell is a CSG cell, and if the CSG Membership Indication is "non member", the target RNC only accepts the emergency bearers. 5a. The target RNC allocates the resources and returns the applicable parameters to the target SGSN in the message Relocation Request Acknowledge (Target RNC to Source RNC Transparent Container, RABs setup list, RABs failed to setup list). Upon sending the Relocation Request Acknowledge message the target RNC shall be prepared to receive downlink GTP PDUs from the Serving GW, or Target SGSN if Direct Tunnel is not used, for the accepted RABs. Each RABs setup list is defined by a Transport Layer Address, which is the target RNC Address for user data, and the Iu Transport Association, which corresponds to the downlink Tunnel Endpoint Identifier for user data. Any EPS Bearer contexts for which a RAB was not established are maintained in the target SGSN and the UE. These EPS Bearer contexts shall be deactivated by the target SGSN via explicit SM procedures upon the completion of the routing area update (RAU) procedure. 6. If 'Indirect Forwarding' and relocation of Serving GW apply and Direct Tunnel is used the target SGSN sends a Create Indirect Data Forwarding Tunnel Request message (Target RNC Address and TEID(s) for DL data forwarding) to the Serving GW. If 'Indirect Forwarding' and relocation of Serving GW apply and Direct Tunnel is not used, then the target SGSN sends a Create Indirect Data Forwarding Tunnel Request message (SGSN Address and TEID(s) for DL data forwarding) to the Serving GW. Indirect forwarding may be performed via a Serving GW which is different from the Serving GW used as the anchor point for the UE. 6a. The Serving GW returns a Create Indirect Data Forwarding Tunnel Response (Cause, Serving GW Address(es) and Serving GW DL TEID(s) for data forwarding) message to the target SGSN. 7. The target SGSN sends the message Forward Relocation Response (Cause, SGSN Tunnel Endpoint Identifier for Control Plane, SGSN Address for Control Plane, Target to Source Transparent Container, Cause, RAB Setup Information, Additional RAB Setup Information, Address(es) and TEID(s) for User Traffic Data Forwarding, Serving GW change indication) to the source MME. Serving GW change indication indicates a new Serving GW has been selected. The Target to Source Transparent Container contains the value from the Target RNC to Source RNC Transparent Container received from the target RNC. The IE 'Address(es) and TEID(s) for User Traffic Data Forwarding' defines the destination tunnelling endpoint for data forwarding in target system, and it is set as follows: - If 'Direct Forwarding' applies, or if 'Indirect Forwarding' and no relocation of Serving GW apply and Direct Tunnel is used, then the IE 'Address(es) and TEID(s) for User Traffic Data Forwarding' contains the addresses and GTP-U tunnel endpoint parameters to the Target RNC received in step 5a. - If 'Indirect Forwarding' and relocation of Serving GW apply, then the IE 'Address(es) and TEID(s) for User Traffic Data Forwarding' contains the addresses and DL GTP-U tunnel endpoint parameters to the Serving GW received in step 6. This is independent from using Direct Tunnel or not. - If 'Indirect Forwarding' applies and Direct Tunnel is not used and relocation of Serving GW does not apply, then the IE 'Address(es) and TEID(s) for User Traffic Data Forwarding' contains the DL GTP-U tunnel endpoint parameters to the Target SGSN. 8. If "Indirect Forwarding" applies, the Source MME sends the message Create Indirect Data Forwarding Tunnel Request (Address(es) and TEID(s) for Data Forwarding (received in step 7)), EPS Bearer ID(s)) to the Serving GW used for indirect forwarding. Indirect forwarding may be performed via a Serving GW which is different from the Serving GW used as the anchor point for the UE. 8a. The Serving GW returns the forwarding parameters by sending the message Create Indirect Data Forwarding Tunnel Response (Cause, Serving GW Address(es) and TEID(s) for Data Forwarding). If the Serving GW doesn't support data forwarding, an appropriate cause value shall be returned and the Serving GW Address(es) and TEID(s) will not be included in the message. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.5.2.1.2 |
5,239 | 9.2.2.4.1 UE triggered transition from RRC_INACTIVE to RRC_CONNECTED | The following figure describes the UE triggered transition from RRC_INACTIVE to RRC_CONNECTED in case of UE context retrieval success: Figure 9.2.2.4.1-1: UE triggered transition from RRC_INACTIVE to RRC_CONNECTED (UE context retrieval success) 1. The UE resumes from RRC_INACTIVE, providing the I-RNTI, allocated by the last serving gNB. 2. The gNB, if able to resolve the gNB identity contained in the I-RNTI, requests the last serving gNB to provide UE Context data. 3. The last serving gNB provides UE context data. 4/5. The gNB and UE completes the resumption of the RRC connection. NOTE: User Data can also be sent in step 5 if the grant allows. 6. If loss of DL user data buffered in the last serving gNB shall be prevented, the gNB provides forwarding addresses. 7/8. The gNB performs path switch. 9. The gNB triggers the release of the UE resources at the last serving gNB. After step 1 above, when the gNB decides to use a single RRC message to reject the Resume Request right away and keep the UE in RRC_INACTIVE without any reconfiguration (e.g. as described in the two examples below), or when the gNB decides to setup a new RRC connection, SRB0 (without security) is used. Conversely, when the gNB decides to reconfigure the UE (e.g. with a new DRX cycle or RNA) or when the gNB decides to push the UE to RRC_IDLE, SRB1 (with integrity protection and ciphering as previously configured for that SRB) shall be used. NOTE: SRB1 can only be used once the UE Context is retrieved i.e. after step 3. The following figure describes the UE triggered transition from RRC_INACTIVE to RRC_CONNECTED in case of UE context retrieval failure: Figure 9.2.2.4.1-2: UE triggered transition from RRC_INACTIVE to RRC_CONNECTED (UE context retrieval failure) 1. The UE resumes from RRC_INACTIVE, providing the I-RNTI, allocated by the last serving gNB. 2. The gNB, if able to resolve the gNB identity contained in the I-RNTI, requests the last serving gNB to provide UE Context data. 3. The last serving gNB cannot retrieve or verify the UE context data. 4. The last serving gNB indicates the failure to the gNB. 5. The gNB performs a fallback to establish a new RRC connection by sending RRCSetup. 6. A new connection is setup as described in clause 9.2.1.3. The following figure describes the rejection form the network when the UE attempts to resume a connection from RRC_INACTIVE: Figure 9.2.2.4.1-3: Reject from the network, UE attempts to resume a connection 1. UE attempts to resume the connection from RRC_INACTIVE. 2. The gNB is not able to handle the procedure, for instance due to congestion. 3. The gNB sends RRCReject (with a wait time) to keep the UE in RRC_INACTIVE. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.2.2.4.1 |
5,240 | 9.9.3.55 Additional information requested | The purpose of the Additional information requested information element is to enable the UE to request ciphering keys for deciphering of ciphered broadcast assistance data. The Additional information requested information element is coded as shown in figure 9.9.3.55.1 and table 9.9.3.55.1. The Additional information requested is a type 3 information element with a length of 2 octets. Figure 9.9.3.55.1: Additional information requested information element Table 9.9.3.55.1: Additional information requested 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.55 |
5,241 | 9.11.3.5 5GS network feature support | The purpose of the 5GS network feature support information element is to indicate whether certain features are supported by the network. The 5GS network feature support information element is coded as shown in figure 9.11.3.5.1 and table 9.11.3.5.1. The 5GS network feature support is a type 4 information element with a minimum length of 3 octets and a maximum length of 6 octets. If: - the length of 5GS network feature support contents field is set to one, then the UE shall interpret this as a receipt of an information element with all bits of octet 4, octet 5 and octet 6 coded as zero. - the length of 5GS network feature support contents field is set to two, the UE shall interpret this as a receipt of an information element with all bits of octet 5 and octet 6 coded as zero. - the length of 5GS network feature support contents field is set to three, the UE shall interpret this as a receipt of an information element with all bits of octet 6 coded as zero. Figure 9.11.3.5.1: 5GS network feature support information element Table 9.11.3.5.1: 5GS network feature support information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.3.5 |
5,242 | 8.4.2.2.8 Enhanced Downlink Control Channel Performance Requirement Type B - 2 Tx Antenna Port with Non-Colliding CRS Dominant Interferer | The purpose of this test is to verify the Enhanced Downlink Control Channel Performance Requirement Type A for PDCCH/PCFICH with 2 transmit antennas for the case of dominant interferer with the non-colliding CRS pattern and applying interference model defined in clause B.7.1. For the parameters specified in Table 8.4.2-1 and Table 8.4.2.2.8-1, the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.4.2.2.8-2. In Table 8.4.2.2.8-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the agressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided and includes Cell 2 and Cell 3. Table 8.4.2.2.8-1: Test Parameters for PDCCH/PCFICH Table 8.4.2.2.8-2: Minimum Performance for PDCCH/PCFICH for Enhanced Downlink Control Channel Performance Requirement Type B | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.4.2.2.8 |
5,243 | I.5 SUPI privacy for standalone non-public networks | The UE shall support SUPI privacy as defined in clause 6.12 with the following exception. When using an authentication method other than 5G AKA or EAP-AKA', the location of the functionality related to SUPI privacy in the UE is out of scope. In scenarios where the EAP-method supports privacy, the UE may send an anonymous SUCI based on configuration. Furthermore, the privacy considerations for EAP TLS (given in Annex B.2.1.2) should be taken into account when using an authentication method other than 5G AKA or EAP-AKA'. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | I.5 |
5,244 | 4.1.1.3 Core Network System Information for MM (Iu mode only) | In the network broadcast system information some of the system information is used by MM. At reception of new system information, the RRC layer in the MS delivers the contents of the CN common system information and the CS domain specific system information to the MM layer in the MS. The Core Network system information is included in specific information elements within some RRC messages sent to MS (see 3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]). In the Core Network system information the Common system information part and the CS domain specific system information part contains settings of parameters controlling MM functionality. No MM messages contain the Core Network System Information. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.1.1.3 |
5,245 | 5.7.1H Channel spacing for LTE based 5G terrestrial broadcast | Nominal channel spacing between adjacent broadcast channels is defined as follows Nominal Channel spacing = PMCH bandwidth where PMCH bandwidth is the broadcast bandwidth for all broadcast carriers in the same geographical area is indicated by upper layer signaling pmch-Bandwidth in the MBSFN area (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [7]). The requirements in this specification do not apply for heterogeneous broadcast bandwidths in the same geographical area. | 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.1H |
5,246 | 5.3 Identification of the HSS for SMS | The HSS may also be identified by a HSS-ID. The HSS-ID shall consist of decimal digits (0 through 9) only and be composed of the MCC consisting of three digits, the MNC consisting of two or three digits and an index consisting of one to several digits. The number of digits in the HSS-ID shall not exceed 15. This composition is compatible with the IMSI one. The HSS-ID shall not be identical to the complete IMSI of a UE. NOTE: The composition of the HSS-ID is compatible with the composition of the IMSI in clause 2.2 for routing purposes. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3 |
5,247 | 5.5.3.11 Charging principles for network slice differentiation in 5G roaming | In the 5G System, the Network Slice is identified by an S-NSSAI (Single Network Slice Selection Assistance Information) within a PLMN, and charging principles for roaming are based on clause 5.15.6 of TS 23.501[ System architecture for the 5G System (5GS) ] [215]. The HPLMN shall be able to collect charging information in 5G data connectivity and 5G connection and mobility for the home subscribers while roaming, with associated used HPLMN S-NSSAI(s) for retail charging. The VPLMN shall be able to collect charging information in 5G data connectivity and 5G connection and mobility for in-bound roamers, with associated VPLMN S-NSSAI(s) and, in addition, the mapping to HPLMN S-NSSAI(s), for the purpose of wholesale towards the HPLMN. These principles are applicable in both Roaming Home Routed and Local Breakout scenarios. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 5.5.3.11 |
5,248 | 9.2.2.5 RNA update | The following figure describes the UE triggered RNA update procedure involving context retrieval over Xn. The procedure may be triggered when the UE moves out of the configured RNA, or periodically. Figure 9.2.2.5-1: RNA update procedure with UE context relocation 1. The UE resumes from RRC_INACTIVE, providing the I-RNTI allocated by the last serving gNB and appropriate cause value, e.g., RAN notification area update. 2. The gNB, if able to resolve the gNB identity contained in the I-RNTI, requests the last serving gNB to provide UE Context, providing the cause value received in step 1. 3. The last serving gNB may provide the UE context (as assumed in the following). Alternatively, the last serving gNB may decide to move the UE to RRC_IDLE (and the procedure follows steps 3 and later of figure 9.2.2.5-3) or, if the UE is still within the previously configured RNA, to keep the UE context in the last serving gNB and to keep the UE in RRC_INACTIVE (and the procedure follows steps 3 and later of figure 9.2.2.5-2). 4. The gNB may move the UE to RRC_CONNECTED (and the procedure follows step 4 of Figure 9.2.2.4.1-1), or send the UE back to RRC_IDLE (in which case an RRCRelease message is sent by the gNB), or send the UE back to RRC_INACTIVE as assumed in the following. 5. If loss of DL user data buffered in the last serving gNB shall be prevented, the gNB provides forwarding addresses. 6./7. The gNB performs path switch. 8. The gNB keeps the UE in RRC_INACTIVE state by sending RRCRelease with suspend indication. 9. The gNB triggers the release of the UE resources at the last serving gNB. The following figure describes the RNA update procedure for the case when the UE is still within the configured RNA and the last serving gNB decides not to relocate the UE context and to keep the UE in RRC_INACTIVE: Figure 9.2.2.5-2: Periodic RNA update procedure without UE context relocation 1. The UE resumes from RRC_INACTIVE, providing the I-RNTI allocated by the last serving gNB and appropriate cause value, e.g., RAN notification area update. 2. The gNB, if able to resolve the gNB identity contained in the I-RNTI, requests the last serving gNB to provide UE Context, providing the cause value received in step 1. 3. The last serving gNB stores received information to be used in the next resume attempt (e.g. C-RNTI and PCI related to the resumption cell), and responds to the gNB with the RETRIEVE UE CONTEXT FAILURE message including an encapsulated RRCRelease message. The RRCRelease message includes Suspend Indication. 4. The gNB forwards the RRCRelease message to the UE. The following figure describes the RNA update procedure for the case when the last serving gNB decides to move the UE to RRC_IDLE: Figure 9.2.2.5-3: RNA update procedure with transition to RRC_IDLE 1. The UE resumes from RRC_INACTIVE, providing the I-RNTI allocated by the last serving gNB and appropriate cause value, e.g., RAN notification area update. 2. The gNB, if able to resolve the gNB identity contained in the I-RNTI, requests the last serving gNB to provide UE Context, providing the cause value received in step 1. 3. Instead of providing the UE context, the last serving gNB provides an RRCRelease message to move the UE to RRC_IDLE. 4. The last serving gNB deletes the UE context. 5. The gNB sends the RRCRelease which triggers the UE to move to RRC_IDLE. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.2.2.5 |
5,249 | 5.30.2 Stand-alone Non-Public Networks 5.30.2.0 General | SNPN 5GS deployments are based on: - the architecture depicted in clause 4.2.3; - the architecture for 5GC with Untrusted non-3GPP access (Figure 4.2.8.2.1-1) for either access to SNPN services via a PLMN (and vice versa) or for direct access to SNPN via non-3GPP access; - the architecture for 5GC with Trusted non-3GPP access (Figure 4.2.8.2.1-2); and - the additional functionality covered in clause 5.30.2. Alternatively, a Credentials Holder (CH) may authenticate and authorize access to an SNPN separate from the Credentials Holder based on the architecture specified in clause 5.30.2.9. Idle and connected mode mobility is supported as defined in clause 5.30.2.11. Clauses 5.30.2.1 to 5.30.2.11 specify the common SNPN aspects applicable to both 3GPP and non-3GPP access, except where stated differently. Aspects specific to Untrusted non-3GPP access for SNPN are specified in clause 5.30.2.12. Aspects specific to Trusted non-3GPP access for SNPN are specified in clause 5.30.2.13. Aspects specific to N5CW devices accessing SNPN services are specified in clause 5.30.2.15. The following 5GS features and functionalities are not supported for SNPNs: - Interworking with EPS; - Emergency services when the UE accesses the SNPN over NWu via a PLMN; - Roaming, e.g. roaming between SNPNs. However, it is possible for a UE to access an SNPN with credentials from a CH as described in clause 5.30.2.9 and to move between equivalent SNPNs; - Handover between SNPN and PLMN or PNI-NPN; - CIoT 5GS Optimizations; - CAG; and - Proximity based Services (ProSe) as defined in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [128]. A UE with two or more network subscriptions, where one or more network subscriptions may be for a subscribed SNPN, can apply procedures specified for Multi-USIM UEs as described in clause 5.38. The UE shall use a separate PEI for each network subscription when it registers to the network. NOTE: The number of preconfigured PEIs for a UE is limited. If the number of network subscriptions for a UE is greater than the preconfigured number of PEIs, the number of network subscriptions that can be registered with the network simultaneously is restricted by the number of pre-configured number of PEIs. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.30.2 |
5,250 | 4.15.13 Assistance for Member UE selection 4.15.13.0 General | With the initial subscription request, the AF provides a list of target UEs in the form of a list of GPSIs or a list of UE IP addresses and at least one Member UE filtering criterion as part of the service operation parameters to assist the candidate UEs selection. Upon receiving the AF request, NEF triggers corresponding 5GC procedures to retrieve from 5GC NFs the information for each UE in the list of target member UEs. Before sending the list(s) of candidate UEs to the AF, NEF consolidates all the information collected from other 5GC NFs and derives one or more list(s) of candidate UEs and possibly additional information according to the Member UE filtering criteria requested by the AF. AF may subsequently update the Member UE filtering criteria and notify the NEF with Subscription Correlation ID. AF does not include the list of target member UEs. AF may request to update the parameters (e.g. expiry time, time window for selecting the candidate UEs) for the subscribed Member UE filtering criteria with Subscription Correlation ID. AF may also request to update by adding new Member UE filtering criteria or removing part of the subscribed Member UE filtering criteria. The Member UE selection assistance capability can be used to assist the AF to select the list of member UEs to support application service (e.g. FL operation) and it is further defined in clause 5.46.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Additionally, AF may leverage the 5GC network exposure for Member UE selection without the NEF assistance as described in clause 5.46.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. An example of how the AF leverages the 5GC network exposure for Member UE selection is described in (informative) Annex I. AF may also unsubscribe the previous subscription for Member UE selection assistance information as described in clause 4.15.13.7. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.13 |
5,251 | 4.15.6.3a Network Configuration parameters | The Network Configuration parameters are the parameters sent from an AF by invoking the Nnef_ParameterProvision Service as described in clause 4.15.6.2. The Network Configuration parameters are described in Table 4.15.6.3a-1. Table 4.15.6.3a-1: Description of Network Configuration parameters The parameters Maximum Response Time and Maximum Latency are stored in the UDM and the Maximum Response Time is sent to the AMF for event monitoring as specified in 4.15.3.2.3b. The AMF may use the Maximum Response Time parameter as guide to configure: - Extended Connected time for MICO mode; - when to send reachability notifications to AF relative to expected reachability events (e.g. paging occasions). If the UDM received multiple Network Configuration requests, the UDM shall accept the request as long as the Maximum Latency (if received) and/or the Maximum Response Time (if received) are within the range defined by operator policies. The UDM shall use the minimum value of Maximum Latency(s) to derive the subscribed periodic registration timer and use the maximum value of Maximum Response Time(s) to derive the subscribed Active Time as specified in step 2 of clause 4.15.3.2.3b. If the newly derived value is changed comparing to the one last time sent to the AMF, the UDM notify the AMF of the updated value via Nudm_SDM_Notification message. If there is a deletion of Network Configuration request, the UDM re-calculates the values (see step 2 in clause 4.15.3.2.3b) and notify the AMF if needed. The Suggested Number of Downlink Packets is classified as SMF associated subscription data. If the NEF is providing DNN and S-NSSAI as specified in clause 4.15.3.2.3, then the UDM is able to associate the parameters with subscribed DNN and S-NSSAI and provides the Suggested Number of Downlink Packets consolidated as specified in 4.15.3.2.3b to the SMF for the PDU Session associated with the specific DNN and S-NSSAI as specified in clause 4.15.6.2. The SMF may use the Suggested Number of Downlink Packets parameter to configure the number of packets to buffer in the SMF/UPF (in the case of UPF anchored PDU sessions) or in the NEF (in the case of NEF anchored PDU session) when the UE is not reachable and extended buffering of downlink data is activated. A Validity Time may be associated with any of the Network Configuration parameters. When the validity time expires, the related NFs delete their local copy of the associated Network Configuration parameter(s). If the deletion results in subscribed value change, the UDM shall notify the AMF or SMF of the changed value. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.6.3a |
5,252 | 5.27.1a Periodic deterministic communication | This clause describes 5G System features that allow support of periodic deterministic communication where the traffic characteristics are known a-priori, and a schedule for transmission from the UE to a downstream node, or from the UPF to an upstream node is provided via external protocols outside the scope of 3GPP (e.g. IEEE 802.1 TSN). The features include the following: - Providing TSC Assistance Information (TSCAI) that describe TSC flow traffic characteristics (as described in clause 5.27.2) at the gNB ingress and the egress of the UE for traffic in downlink and uplink direction, respectively; - Support for hold & forward buffering mechanism (see clause 5.27.4) in DS-TT and NW-TT to de-jitter flows that have traversed the 5G System. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.27.1a |
5,253 | 4.2.8.2.2 LBO Roaming Architecture | Figure 4.2.8.2.2-1: LBO Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in the same VPLMN as 3GPP access Figure 4.2.8.2.2-2: LBO Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in a different PLMN from 3GPP access Figure 4.2.8.2.2-3: LBO Roaming architecture for 5G Core Network with trusted non-3GPP access using the same VPLMN as 3GPP access Figure 4.2.8.2.2-4: LBO Roaming architecture for 5G Core Network with trusted non-3GPP access using a different PLMN than 3GPP access NOTE 1: The reference architecture in all above figures only shows the architecture and the network functions directly connected to support non-3GPP access, and other parts of the architecture are the same as defined in clause 4.2. NOTE 2: The reference architecture in all above figures supports service based interfaces for AMF, SMF and other NFs not represented in the figures. NOTE 3: The two N2 instances in Figure 4.2.8.2.2-1 and in Figure 4.2.8.2.2-3 terminate to a single AMF for a UE which is connected to the same 5G Core Network over 3GPP access and non-3GPP access simultaneously. NOTE 4: The two N3 instances in Figure 4.2.8.2.2-1 and in Figure 4.2.8.2.2-3 may terminate to different UPFs when different PDU Sessions are established over 3GPP access and non-3GPP access. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.8.2.2 |
5,254 | 13.2.2.4.1 N32-f context ID | The N32-f context ID is used to refer to an N32-f context. The SEPPs shall create the N32-f context ID during the N32-c negotiation and use it over N32-f to inform the receiving peer which security context to use for decryption of a received message. The initiating SEPP shall send the initiating SEPP’s N32-f context ID to the responding SEPP which the responding SEPP shall use to identify the N32-f connection with this initiating SEPP. Vice versa, the responding SEPP shall send the responding SEPP’s N32-f context ID to the initiating SEPP which the initiating SEPP shall use to identify the N32-f connection with this responding SEPP. To avoid collision of the N32-f context ID value, the SEPPs shall select the N32-f context ID as a random value during the exchange over N32-c. During transfer of application data over N32-f, the SEPP shall include the N32-f context ID in a separate IE in the metadata part of the JSON structure, see clause 13.2.4.2. The receiving SEPP shall use this information to apply the correct key and parameters during decryption and validation. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.2.2.4.1 |
5,255 | 13a.2.1 IMS Specific Configuration in the GGSN/P-GW | The GGSN/P-GW shall have a list of preconfigured addresses of signalling servers (P-CSCF servers). This list shall be provided to MSs/UEs on request. The list shall be possible to preconfigure per APN. The GGSN/P-GW shall have locally preconfigured packet filters, and/or applicable PCC rules, as specified in 3GPP TS 29.212[ Policy and Charging Control (PCC); Reference points ] [75] to be applied on the dedicated signalling bearer (e.g. PDP context). The packet filters shall filter up-link and down-link packets and only allow traffic to/from the signalling servers and to DNS and DHCP servers. The locally preconfigured packet filters shall be possible to pre-configure per APN. It shall be possible to enable/disable the use of the Gx interface per APN. When Gx is enabled the GGSN/P-GW shall handle IP-CAN Bearer Establishment (e.g. Create PDP Context Requests) as specified in 3GPP TS 29.212[ Policy and Charging Control (PCC); Reference points ] [75]. The GGSN/P-GW shall support IPv4 and/or IPv6 addresses and protocol for IMS signalling and IMS bearers. The methods for an MS/UE to discover P-CSCF address(es) may vary depending on the access technology that the MS/UE is on. The details of the P-CSCF discovery mechanisms for various accesses are specified in 3GPP TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [52] and 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [47]. For example, for an MS/UE accesing to IMS via GPRS in GERAN and UTRAN, the GGSN shall provide support for P-CSCF discovery in three different ways (see 3GPP TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [52] and 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [47]): - GPRS procedure for P-CSCF discovery, i.e. request and provision of P-CSCF address(es) within the PCO IE in GPRS Session Management procedures (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [54]). - Via DHCP servers i.e. the GGSN shall provide the functionality of a DHCP relay agent - If the MS/UE has a P-CSCF FQDN locally configured and request the DNS IP address(es) from the GGSN (via PCO or DHCP procedures), the GGSN shall be able to provide DNS IP address(es) to the MS/UE. Similarly, the PGW shall have similar functional support depending on the P-CSCF discovery methods supported by the UE on the access technology. For example, for a UE in 3GPP access network (i.e. GERAN, UTRAN, EUTRAN), the P-GW shall support same functions as the GGSN that are specified above except that the P-GW does not act as a DHCP relay agent between the MS/UE and the external DHCP server. In other words, as specified in clause 13 of this document, the P-GW shall have DHCP server function towards the MS/UE while acting as a DHCP client towards external DHCP server, if the P-GW is configured to request DNS and/or P-CSCF IP addresses from external DHCP servers. The GGSN/P-GW shall be able to deliver DNS and/or P-CSCF addresses to the MS/UE if requested by the MS/UE via PCO (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [54] and 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [84]) or via DHCP procedures using the relevant DHCP options for IPv4/IPv6 DNS and SIP servers (see RFC 2132 [85], RFC 3361 [86], RFC 3646 [87] and RFC 3319 [88]). On APNs providing IMS services, the information advertised in Router Advertisements from GGSN/P-GW to MSs/UEs shall be configured in the same manner as for other APNs providing IPv6 services (see subclause 11.2.1.3.4), except that the "O-flag" shall be set. NOTE: The "O- flag" shall be set in IPv6 Router Advertisement messages sent by the GGSN/P-GW for APNs used for IMS services. This will trigger a DHCP capable MS/UE to start a DHCPv6 session to retrieve server addresses and other configuration parameters. An MS/UE which doesn’t support DHCP will simply ignore the "O-flag". An MS/UE, which doesn’t support DHCP, shall request IMS specific configuration (e.g. P-CSCF address) via the other discovery methods supported in the MS/UE (i.e. via locally configured P-CSCF address/FQDN in the MS/UE or via PCO procedure, if applicable). The GGSN/P-GW shall have configurable policy rules for controlling bearers (e.g. PDP contexts) used for signalling as specified in section 13a.2.2.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 | 13a.2.1 |
5,256 | 8.123 Remote User ID | Remote User ID is transferred via GTP tunnels and is coded as depicted in Figure 8.123-1. The Remote User ID IE shall contain one IMSI identity and, if available, one IMEI identity and/or one MSISDN identity. The flag MSISDNF in octet 5 indicates if the MSISDN shall be present in the respective field. The flag IMEIF in octet 5 indicates if the IMEI shall be present in the respective field. The IMSI field including the Length of IMSI shall be always present. Figure 8.123-1: Remote User ID The coding of IMSI field, from octets 7 to 'a' shall be encoded as the octets 5 to n+4 of the IMSI IE type specified in clause 8.3. The coding of MSISDN field, octets 'b+1' to 'c' shall be encoded as the octets 5 to n+4 of the MSISDN IE type specified in clause 8.11. The coding of IMEI field, octets 'd+1' to 'e' shall be encoded as the octets 5 to n+4 of the MEI IE type specified in clause 8.10. | 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.123 |
5,257 | 10.5.6.9 LLC service access point identifier | The purpose of the LLC service access point identifier information element is to identify the service access point that is used for the GPRS data transfer at LLC layer. The LLC service access point identifier is a type 3 information element with a length of 2 octets. The value part of a LLC service access point identifier information element is coded as shown in figure 10.5.141/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.159/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.141/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : LLC service access point identifier information element Table 10.5.159/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : LLC service access point identifier information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.6.9 |
5,258 | G.3 Causes related to PLMN specific network failures and congestion/Authentication Failures | Cause value = 20 MAC failure This cause is sent to the network if the USIM detects that the MAC in the AUTHENTICATION REQUEST or AUTHENTICATION_AND_CIPHERING REQUEST message is not fresh (see 3GPP TS 33.102[ 3G security; Security architecture ] [5a]). Cause value = 21 Synch failure This cause is sent to the network if the USIM detects that the SQN in the AUTHENTICATION REQUEST or AUTHENTICATION_AND_CIPHERING REQUEST message is out of range (see 3GPP TS 33.102[ 3G security; Security architecture ] [5a]). Cause value = 17 Network failure This cause is sent to the MS if the MSC cannot service an MS generated request because of PLMN failures, e.g. problems in MAP. Cause value = 22 Congestion This cause is sent to the MS if the network cannot serve a request from the MS because of congestion (e.g. congestion of the MSC or SGSN or GGSN or PDN Gateway; no channel; facility busy/congested etc.). Cause value = 23 GSM authentication unacceptable This cause is sent to the network in Iu mode if a USIM is inserted in the MS and there is no Authentication Parameter AUTN IE present in the AUTHENTICATION REQUEST or AUTHENTICATION_AND_CIPHERING REQUEST message. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | G.3 |
5,259 | 8.51.3 Macro eNodeB ID | The Target Type is Macro eNodeB ID for: - handover to E-UTRAN Macro eNodeB; - RAN Information Relay towards E-UTRAN; and - a TNL address discovery response of a candidate en-gNB via the S1 interface or via inter-system signalling (see clauses 22.3.6.2 and 22.3.6.3 of 3GPP TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [19]). In this case the Target ID field shall be coded as depicted in Figure 8.51-2. Figure 8.51-2: Target ID for Type Macro eNodeB The Macro eNodeB ID consists of 20 bits. Bit 4 of Octet 9 is the most significant bit and bit 1 of Octet 11 is the least significant bit. The coding of the Macro eNodeB ID is the responsibility of each administration. Coding using full hexadecimal representation (binary, not ASCII encoding) shall be used. | 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.51.3 |
5,260 | 4.16.14.2.1 Management of access and mobility related policy information at start and stop of application traffic | This procedure applies when the AF provides a service coverage area or the indication of high throughput associated with the Application Identifer(s). Figure 4.16.14.2.1-1: Management of access and mobility related policy information at start and stop of application traffic 1. The AMF establishes an AM Policy Association for retrieving access and mobility related policy information, e.g. RFSP index value, as described in clause 4.16.1.2. 2. If the access and mobility related policy information depends on the application in use, then depending on operator policies in the PCF, the PCF may subscribe to the BSF, then step 3 follows, or provides its PCF binding information to the AMF in step 1 with the indication to be notified about the PCF for the PDU Session for a DNN, S-NSSAI, then step 4 follows. 3. The PCF for the UE determines that access and mobility related policy information (e.g. RFSP index value) depends on the detection of one or more application(s) in use, the DNN, S-NSSAI used to access each Application Id is configured in the PCF or retrieved from the UDR as part of the Application Data Set, then subscribes to the BSF to be notified when a PCF for the PDU Session for this SUPI is registered in the BSF, by invoking Nbsf_Management_Subscribe (SUPI, list of (DNN, S-NSSAI)(s)). Steps 4 and 5 are repeated for each PCF registered for a PDU Session to a (DNN, S-NSSAI) included in the Nbsf_Management. 4. The SMF establishes a SM Policy Association as described in clause 4.16.4. The allocated UE address/prefix, SUPI, DNN, S-NSSAI and the PCF address is registered in the BSF, as described in clause 6.1.1.2.2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 5a. If the PCF for the UE subscribed to the BSF, then the BSF notifies that a PCF for the PDU Session is registered in the BSF, by invoking Nbsf_Management_Notify (DNN, S-NSSAI, UE address(es), PCF address, PCF instance id, PCF Set ID, level of binding). When there are multiple PDU Sessions to the same (DNN, S-NSSAI) the BSF provides multiple notification to the PCF. 5b. If the PCF for the UE sent the request to notify that a PCF for the PDU Session is available to the AMF in step 1, then the PCF for the PDU Sessions sends Npcf_PolicyAuthorization_Notify (EventID set to SM Policy Association established, UE address, PCF address, PCF instance is, PCF Set ID) to the PCF indicated in the PCF binding information provided by the SMF. 6. The PCF for the UE subscribes to notifications of event "start/stop of application traffic" as defined in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], using Npcf_PolicyAuthorization_Subscribe (UE address, EventId, EventFilter set to "list of Application Identifiers") to the PCF for the PDU Session to the DNN, S-NSSAI. The PCF for the PDU Session then generates PCC Rules including the Application Identifier in the SDF template, if there are multiple Application Identifiers included in the Npcf_PolicyAuthorization, the PCF generates PCC Rules for each Application Identifier. The response includes the NotificationCorrelationId. 7. The PCF installs PCC Rules and the Policy Control Request Trigger to detect "start/stop of application traffic" in the SMF. 8. The SMF detects that the Policy Control Request Trigger is met, then reports the start/stop of application traffic to the PCF serving the PDU Session. 9. The PCF for the UE is notified on the start/stop of application traffic by Npcf_PolicyAuthorization_Notify (NotificationCorrelationId, EventId set to "start/stop of application traffic", EventInformation including the ApplicationId). When the reporting of start and stop of a list of Application(s) was requested, the PCF for the PDU Session provides multiple notification to the PCF for the UE. 10. The PCF checks operator policies and then may change access and mobility related policy information (e.g. RFSP index value) based on the reporting of start/stop of application traffic. 11. The SM Policy Association is terminated as described in clause 4.16.6. The allocated UE address/prefix, SUPI, DNN, S-NSSAI and the PCF address are deregistered in the BSF. 12a. If the PCF for the UE subscribed to the BSF, then the BSF notifies that the PCF serving a PDU Session is deregistered in the BSF, by invoking Nbsf_Management_Notify (Binding Identifier for the PDU Session). 12b. If the PCF for the UE sent the request to notify that a PCF for the PDU Session is available to the AMF in step 1, then the PCF for the PDU Session sends Npcf_PolicyAuthoritation_Notify ((EventID set to SM Policy Association termination, Notification Correlation Id). NOTE: The PCF for the UE may subscribe to the notifications of newly registered PCF for the PDU Session and subscribe to the "start/stop of application traffic detection" events for multiple applications with different application identifiers. When PCF receives the notifications for multiple applications, the PCF for the UE can determine which access and mobility related policy information to apply based on local configuration and operator policy. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.14.2.1 |
5,261 | 5.6.1.4.1 UE is not using 5GS services with control plane CIoT 5GS optimization | For cases other than h) in subclause 5.6.1.1, the UE shall treat the reception of the SERVICE ACCEPT message as successful completion of the procedure. The UE shall reset the service request attempt counter, stop timer T3517 and enter the state 5GMM-REGISTERED. For case h) in subclause 5.6.1.1, a) the UE shall treat the indication from the lower layers when the UE has changed to S1 mode or E-UTRA connected to 5GCN (see 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]) as successful completion of the procedure and stop timer T3517; b) if a UE operating in single-registration mode has changed to S1 mode, it shall disable the N1 mode capability for 3GPP access (see subclause 4.9.2); and c) the AMF shall not check for CAG restrictions. If the PDU session status information element is included in the SERVICE REQUEST message, then: a) for single access PDU sessions, the AMF shall: 1) perform a local release of all those PDU sessions which are not in 5GSM state PDU SESSION INACTIVE on the AMF side associated with the access type the SERVICE REQUEST message is sent over, but are indicated by the UE as being in 5GSM state PDU SESSION INACTIVE; and 2) request the SMF to perform a local release of all those PDU sessions. If any of those PDU sessions is associated with one or more multicast MBS sessions, the SMF shall consider the UE as removed from the associated multicast MBS sessions; and b) for MA PDU sessions, the AMF shall: 1) for MA PDU sessions having user plane resources established in the AMF only on the access the SERVICE REQUEST message is sent over, but are indicated by the UE as no user plane resources established: i) for all those MA PDU sessions without a PDN connection established as a user-plane resource, perform a local release of all those MA PDU sessions and request the SMF to perform a local release of all those MA PDU sessions. If the MA PDU session is associated with one or more multicast MBS sessions, the SMF shall consider the UE as removed from the associated multicast MBS sessions; and ii) for all those MA PDU sessions with a PDN connection established as a user-plane resource, perform a local release of user plane resources of all those PDU sessions on the access the SERVICE REQUEST message is sent over and request the SMF to perform a local release of user plane resources of all those PDU sessions on the access type the SERVICE REQUEST message is sent over; and 2) for MA PDU sessions having user plane resources established on both accesses in the AMF, but are indicated by the UE as no user plane resources established: i) perform a local release of user plane resources of all those PDU sessions on the access the SERVICE REQUEST message is sent over; and ii) request the SMF to perform a local release of user plane resources of all those PDU sessions on the access type the SERVICE REQUEST message is sent over. If the SERVICE REQUEST message is sent over 3GPP access and the MA PDU session is associated with one or more multicast MBS sessions, the SMF shall consider the UE as removed from the associated multicast MBS sessions. If the AMF needs to initiate PDU session status synchronization or a PDU session status IE was included in the SERVICE REQUEST message, the AMF shall include a PDU session status IE in the SERVICE ACCEPT message to indicate: - which single access PDU sessions associated with the access type the SERVICE ACCEPT message is sent over are not in 5GSM state PDU SESSION INACTIVE in the AMF; and - which MA PDU sessions are not in 5GSM state PDU SESSION INACTIVE and having user plane resources established in the AMF on the access the SERVICE ACCEPT message is sent over. If the PDU session status information element is included in the SERVICE ACCEPT message, then: a) for single access PDU sessions, the UE shall perform a local release of all those PDU sessions which are not in 5GSM state PDU SESSION INACTIVE or PDU SESSION ACTIVE PENDING on the UE side associated with the access type the SERVICE ACCEPT message is sent over, but are indicated by the AMF as in 5GSM state PDU SESSION INACTIVE. If a locally released PDU session is associated with one or more multicast MBS sessions, the UE shall locally leave the associated multicast MBS sessions; and b) for MA PDU sessions, for all those PDU sessions which are not in 5GSM state PDU SESSION INACTIVE or PDU SESSION ACTIVE PENDING and have user plane resources established on the UE side associated with the access the SERVICE ACCEPT message is sent over, but are indicated by the AMF as no user plane resources established: 1) for MA PDU sessions having user plane resources established only on the access type the SERVICE ACCEPT message is sent over, the UE shall perform a local release of those MA PDU sessions. If a locally released MA PDU session is associated with one or more multicast MBS sessions, the UE shall locally leave the associated multicast MBS sessions; and 2) for MA PDU sessions having user plane resources established on both accesses, the UE shall perform a local release on the user plane resources on the access type the SERVICE ACCEPT message is sent over. If the user plane resources over 3GPP access are released and the MA PDU session is associated with one or more multicast MBS sessions, the UE shall locally leave the associated multicast MBS sessions. If the Uplink data status IE is included in the SERVICE REQUEST message and the UE is: a) not in NB-N1 mode; or b) in NB-N1 mode and the UE does not indicate a request to have user-plane resources established for a number of PDU sessions that exceeds the UE's maximum number of supported user-plane resources; the AMF shall: a) indicate the SMF to re-establish the user-plane resources for the corresponding PDU sessions; b) include the PDU session reactivation result IE in the SERVICE ACCEPT message to indicate the user-plane resources re-establishment result of the PDU sessions for which the UE requested to re-establish the user-plane resources; and c) determine the UE presence in LADN service area (see subclause 6.2.6) and forward the UE presence in LADN service area towards the SMF, if the corresponding PDU session is a PDU session for LADN. If the Allowed PDU session status IE is included in the SERVICE REQUEST message, the AMF shall: a) for a 5GSM message from each SMF that has indicated pending downlink signalling only, forward the received 5GSM message via 3GPP access to the UE after the SERVICE ACCEPT message is sent; b) for each SMF that has indicated pending downlink data only: 1) notify the SMF that reactivation of the user-plane resources for the corresponding PDU session(s) associated with non-3GPP access cannot be performed if the corresponding PDU session ID(s) are not indicated in the Allowed PDU session status IE; and 2) notify the SMF that reactivation of the user-plane resources for the corresponding PDU session(s) associated with non-3GPP access can be performed if: i) for a UE not in NB-N1 mode, the corresponding PDU session ID(s) are indicated in the Allowed PDU session status IE; or ii) for a UE in NB-N1 mode, the corresponding PDU session ID(s) are indicated in the Allowed PDU session status IE, and the resulting number of PDU sessions with established user-plane resources does not exceed the UE's maximum number of supported user-plane resources; c) for each SMF that have indicated pending downlink signalling and data: 1) notify the SMF that reactivation of the user-plane resources for the corresponding PDU session(s) associated with non-3GPP access cannot be performed if the corresponding PDU session ID(s) are not indicated in the Allowed PDU session status IE; 2) notify the SMF that reactivation of the user-plane resources for the corresponding PDU session(s) associated with non-3GPP access can be performed if: i) for a UE not in NB-N1 mode, the corresponding PDU session ID(s) are indicated in the Allowed PDU session status IE; or ii) for a UE in NB-N1 mode, the corresponding PDU session ID(s) are indicated in the Allowed PDU session status IE, and the resulting number of PDU sessions with established user-plane resources does not exceed the UE's maximum number of supported user-plane resources; and 3) discard the received 5GSM message for PDU session(s) associated with non-3GPP access; and d) include the PDU session reactivation result IE in the SERVICE ACCEPT message to indicate the successfully re-established user-plane resources for the corresponding PDU sessions, if any. If due to regional subscription restrictions or access restrictions the UE is not allowed to access the TA or due to CAG restrictions the UE is not allowed to access the cell, but the UE has an emergency PDU session established, the AMF may accept the SERVICE REQUEST message and indicate to the SMF to perform a local release of all non-emergency PDU sessions (associated with 3GPP access if it is due to CAG restrictions) and informs the UE via the PDU session status IE in the SERVICE ACCEPT message. The AMF shall not indicate to the SMF to release the emergency PDU session. If the AMF indicated to the SMF to perform a local release of all non-emergency PDU sessions (associated with 3GPP access if it is due to CAG restrictions), the network shall behave as if the UE is registered for emergency services. If the PDU session reactivation result IE is included in the SERVICE ACCEPT message indicating that the user-plane resources have been successfully reactivated for a PDU session that was indicated by the UE in the Allowed PDU session status IE as allowed to be re-established over 3GPP access, the UE considers the corresponding PDU session to be associated with the 3GPP access. If the user-plane resources of a PDU session have been successfully reactivated over the 3GPP access, the AMF and SMF update the associated access type of the corresponding PDU session. If the user-plane resources cannot be established for a PDU session, the AMF shall include the PDU session reactivation result IE in the SERVICE ACCEPT message indicating that user-plane resources for the corresponding PDU session cannot be re-established, and: a) if the user-plane resources cannot be established because the SMF indicated to the AMF that the UE is located out of the LADN service area (see 3GPP TS 29.502[ 5G System; Session Management Services; Stage 3 ] [20A]), the AMF shall include the PDU session reactivation result error cause IE with the 5GMM cause set to #43 "LADN not available"; b) if the user-plane resources cannot be established because the SMF indicated to the AMF that only prioritized services are allowed (see 3GPP TS 29.502[ 5G System; Session Management Services; Stage 3 ] [20A]), the AMF shall include the PDU session reactivation result error cause IE with the 5GMM cause set to #28 "restricted service area"; c) if the user-plane resources cannot be established because the SMF indicated to the AMF that the resource is not available in the UPF (see 3GPP TS 29.502[ 5G System; Session Management Services; Stage 3 ] [20A]), the AMF shall include the PDU session reactivation result error cause IE with the 5GMM cause set to #92 "insufficient user-plane resources for the PDU session"; d) if the user-plane resources cannot be established because the SMF indicated to the AMF that the S-NSSAI associated with the PDU session is unavailable due to NSAC (see 3GPP TS 29.502[ 5G System; Session Management Services; Stage 3 ] [20A]), the AMF shall include the PDU session reactivation result error cause IE with the 5GMM cause set to #69 "insufficient resources for specific slice"; or e) otherwise, the AMF may include the PDU session reactivation result error cause IE to indicate the cause of failure to re-establish the user-plane resources. NOTE 1: It is up to UE implementation when to re-send a request for user-plane re-establishment for the associated PDU session after receiving a PDU session reactivation result error cause IE with a 5GMM cause set to #92 "insufficient user-plane resources for the PDU session". NOTE 2: The UE can locally start a back-off timer after receiving a PDU session reactivation result error cause IE with a 5GMM cause set to #69 "insufficient resources for specific slice". The value of the back-off timer is up to UE implementation. Upon expiry of the back-off timer, the UE can re-send a request for user-plane re-establishment for the associated PDU session. For case a and b, - if the AMF has a service area list or LADN information which is applicable to the current TAI of the UE and was not yet provided to the UE, before sending the SERVICE ACCEPT message the AMF shall initiate the generic UE configuration update procedure and include the service area list or LADN information or both in the CONFIGURATION UPDATE COMMAND message; and - if timer T3540 is not started (see subclause 5.3.1.3, item f), and the UE did not receive a CONFIGURATION UPDATE COMMAND message during the service request procedure, the UE may initiate a registration procedure for mobility or periodic registration update. If timer T3540 is started and the UE does not receive a CONFIGURATION UPDATE COMMAND message before the established N1 NAS signalling connection is released by the network or timer T3540 expires or is stopped as specified in subclause 5.3.1.3, the UE may initiate the registration procedure for mobility or periodic registration update upon release of the N1 NAS signalling connection. If the PDU session reactivation result IE is included in the SERVICE ACCEPT message indicating that the user-plane resources cannot be established for a PDU session that was indicated by the UE in the Allowed PDU session status IE as allowed to be re-established over 3GPP access, the UE considers the corresponding PDU session to be associated with the non-3GPP access. If the MUSIM UE does not include the Paging restriction IE in the SERVICE REQUEST message, the AMF shall delete any stored paging restriction for the UE and stop restricting paging. For case m in subclause 5.6.1.1 when the MUSIM UE sets the Request type to "NAS signalling connection release" in the SERVICE REQUEST message, the AMF shall initiate the release of the N1 NAS signalling connection after the completion of the service request procedure. For cases o and p in subclause 5.6.1.1 when the MUSIM UE sets the Request type to "NAS signalling connection release" or to "Rejection of paging" in the UE request type IE in the SERVICE REQUEST message and if the UE requests restriction of paging by including the Paging restriction IE, the AMF: - if accepts the paging restriction, shall include the 5GS additional request result IE in the SERVICE ACCEPT message and set the Paging restriction decision to "paging restriction is accepted". The AMF shall store the paging restriction of the UE and enforce these restrictions in the paging procedure as described in subclause 5.6.2; or - if rejects the paging restriction, shall include the 5GS additional request result IE in the SERVICE ACCEPT message and set the Paging restriction decision to "paging restriction is rejected", and shall discard the received paging restriction. The AMF shall delete any stored paging restriction for the UE and stop restricting paging; and the AMF shall initiate the release of the N1 NAS signalling connection as follows: - for case o in subclause 5.6.1.1, after the completion of the service request procedure; - for case p in subclause 5.6.1.1, after the completion of the generic UE configuration update procedure that is triggered after the completion of the service request procedure. If the SERVICE REQUEST message is for emergency services fallback, the AMF triggers the emergency services fallback procedure as specified in subclause 4.13.4.2 of 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]. If the UE having an emergency PDU session associated with 3GPP access sent the SERVICE REQUEST message via: a) a CAG cell and none of the CAG-ID(s) of the CAG cell are authorized based on the "Allowed CAG list" for the current PLMN in the UE's subscription; or b) a non-CAG cell in a PLMN for which the UE's subscription contains an "indication that the UE is only allowed to access 5GS via CAG cells"; the network shall accept the SERVICE REQUEST message and release all non-emergency PDU sessions associated with 3GPP access locally. The emergency PDU session associated with 3GPP access and PDU sessions associated with non-3GPP access shall not be released. If the AMF received the list of TAIs from the satellite NG-RAN as described in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], and determines that, by UE subscription and operator's preferences, any but not all TAIs in the received list of TAIs is forbidden for roaming or for regional provision of service, the AMF shall include the TAI(s) in: a) the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE; or b) the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for regional provision of service" IE; or c) both; in the SERVICE ACCEPT message. NOTE 9: Void. If the UE receives the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE in the SERVICE ACCEPT message and the TAI(s) included in the IE is not part of the list of "5GS forbidden tracking areas for roaming", the UE shall store the TAI(s) belonging to the serving PLMN or equivalent PLMN(s) and ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s) included in the IE into the list of "5GS forbidden tracking areas for roaming" and remove the TAI(s) from the stored TAI list if present. If the UE receives the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for regional provision of service" IE in the SERVICE ACCEPT message and the TAI(s) included in the IE is not part of the list of "5GS forbidden tracking areas for regional provision of service", the UE shall store the TAI(s) belonging to the serving PLMN or equivalent PLMN(s) and ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s) included in the IE into the list of "5GS forbidden tracking areas for regional provision of service" and remove the TAI(s) from the stored TAI list if present. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.6.1.4.1 |
5,262 | 8.51.5 Extended Macro eNodeB ID | The Target Type is Extended Macro eNodeB ID for: - handover to E-UTRAN Macro eNodeB; - RAN Information Relay towards E-UTRAN; and - a TNL address discovery response of a candidate en-gNB via the S1 interface or via inter-system signalling (see clauses 22.3.6.2 and 22.3.6.3 of 3GPP TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [19]). In this case the Target ID field shall be coded as depicted in Figure 8.51-4. Figure 8.51-4: Target ID for Type Extended Macro eNodeB The Extended Macro eNodeB ID consists of 21 bits. The coding of the Macro eNodeB ID is the responsibility of each administration. Coding using full hexadecimal representation (binary, not ASCII encoding) shall be used. If the SMeNB flag is not set the Extended Macro eNodeB ID contains a Long Macro eNodeB ID with a length of 21 Bits. Bit 5 of Octet 9 is the most significant bit and bit 1 of Octet 11 is the least significant bit. If the SMeNB flag is set the Extended Macro eNodeB ID contains a Short Macro eNodeB ID with a length of 18 Bits. Bits 5 to 3 of Octet 9 shall be set to 0 by the sender and shall be ignored by the receiver. Bit 2 of Octet 9 is the most significant bit and bit 1 of Octet 11 is the least significant bit. | 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.51.5 |
5,263 | 6.5 AOA related measurements | a) This measurement provides a bin distribution (histogram) of the periodical E-UTRAN AOA 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 aoaResult. The event triggered MeasurementReport messages are excluded. This measurement shall be increased for each reported value AOA_ANGLE (See in 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [18]). For every 5 AOA_ANGLE (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]) Note: antenna deployment. Note: this measurement is only valid for eNodeB with antenna array. d) Each measurement is an integer value. e) MR.EutranAOA.y y is an integer from 00 to 71. Note: 00 of y indicates from AOA_ANGLE _000 to AOA_ANGLE_009, namely 0 AOA_ANGLE < 5 degree, … 71 of y indicates from AOA_ANGLE _710 to AOA_ANGLE _719, namely 355 AOA_ANGLE < 360 degree. (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.5 |
5,264 | 5.7.8.1a Measurement configuration | The purpose of this procedure is to update the idle/inactive measurement configuration. The UE initiates this procedure while T331 is running and SDT procedure is not ongoing and one of the following conditions is met: 1> upon selecting a cell when entering RRC_IDLE or RRC-INACTIVE from RRC_CONNECTED or RRC_INACTIVE; or 1> upon update of system information (SIB4, or SIB11), e.g. due to intra-RAT cell (re)selection; While in RRC_IDLE or RRC_INACTIVE, and T331 is running, the UE shall: 1> if VarMeasIdleConfig includes neither a measIdleCarrierListEUTRA nor a measIdleCarrierListNR received from the RRCRelease message: 2> if the UE supports idleInactiveEUTRA-MeasReport: 3> if the SIB11 includes the measIdleConfigSIB and contains measIdleCarrierListEUTRA: 4> store or replace the measIdleCarrierListEUTRA of measIdleConfigSIB of SIB11 within VarMeasIdleConfig; 3> else: 4> remove the measIdleCarrierListEUTRA in VarMeasIdleConfig, if stored; 2> if the UE supports idleInactiveNR-MeasReport: 3> if SIB11 includes the measIdleConfigSIB and contains measIdleCarrierListNR: 4> store or replace the measIdleCarrierListNR of measIdleConfigSIB of SIB11 within VarMeasIdleConfig; 3> else: 4> remove the measIdleCarrierListNR in VarMeasIdleConfig, if stored; 1> for each entry in the measIdleCarrierListNR within VarMeasIdleConfig that does not contain an ssb-MeasConfig received from the RRCRelease message: 2> if there is an entry in measIdleCarrierListNR in measIdleConfigSIB of SIB11 that has the same carrier frequency and subcarrier spacing as the entry in the measIdleCarrierListNR within VarMeasIdleConfig and that contains ssb-MeasConfig: 3> delete the ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig; 3> store the SSB measurement configuration from SIB11 into nrofSS-BlocksToAverage, absThreshSS-BlocksConsolidation, smtc, ssb-ToMeasure, deriveSSB-IndexFromCell, and ss-RSSI-Measurement within ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig; 2> else if there is an entry in interFreqCarrierFreqList of SIB4 with the same carrier frequency and subcarrier spacing as the entry in measIdleCarrierListNR within VarMeasIdleConfig: 3> delete the ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig; 3> store the SSB measurement configuration from SIB4 into nrofSS-BlocksToAverage, absThreshSS-BlocksConsolidation, smtc, ssb-ToMeasure, deriveSSB-IndexFromCell, and ss-RSSI-Measurement within ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig; 2> else: 3> remove the ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig, if stored; 1> perform measurements according to 5.7.8.2a. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.8.1a |
5,265 | 13.3 Detection and handling of requests which have timed out at the originating entity 13.3.1 General | This procedure enables an entity which receives a request to know when the request times out at the originating entity, and to stop further processing, at the receiver and further upstream entities, a request which has timed out at the originating entity. The originating entities (i.e. MME, SGSN, TWAN and ePDG) and the receiving entities (i.e. SGW, PGW, PCRF, 3GPP AAA Server) shall be NTP synchronized. This procedure may be used between entities pertaining to the same PLMN, and if allowed by operator policy, between entities pertaining to different PLMNs. This procedure shall not affect the setting of the retransmission timers by intermediate entities. E.g. the SGW shall set its T3 and N3 retransmission parameters as specified in this specification, irrespective of the time at which the request times out at the originating entity. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 13.3 |
5,266 | 7.3.1D Minimum requirements (QPSK) for ProSe | When UE is configured for E-UTRA ProSe reception non-concurrent with E-UTRA uplink transmissions for E-UTRA ProSe operating bands specified in Table 5.5D-1, the throughput shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annexes A.6.2 with parameters specified in Table 7.3.1D-1 and Table 7.3.1D-2. Table 7.3.1D-1: Reference sensitivity for ProSe Direct Discovery QPSK PREFSENS Table 7.3.1D-2: Reference sensitivity for ProSe Direct Communication QPSK PREFSENS NOTE: Table 7.3.1D-1/ Table 7.3.1D-2 is intended for conformance tests and does not necessarily reflect the operational conditions of the network, where the number of allocated resource blocks will be practically constrained by other factors. For the UE which supports ProSe in an operating band as specified in Section 5.5D, and the UE also supports a E-UTRA downlink inter-band carrier aggregation configuration in Table 7.3.1-1A or Table 7.3.1-1B, the minimum requirement for reference sensitivity in Table 7.3.1D-1 and Table 7.3.1D-2 shall be increased by the amount given in ΔRIB,c in Table 7.3.1-1A and Table 7.3.1-1B for the corresponding E-UTRA ProSe band. When UE is configured for E-UTRA ProSe reception on PCC for the inter-band E-UTRA ProSe / E-UTRA bands specified in Table 5.5D-2, there are no further requirements for reference sensitivity beyond those specified above when only PCC is configured in Table 7.3.1D-1 and Table 7.3.1D-2. When UE is configured for E-UTRA ProSe reception on SCC or a non-serving carrier concurrent with E-UTRA uplink for inter-band E-UTRA ProSe / E-UTRA bands specified in Table 5.5D-2, E-UTRA ProSe throughput shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annexes A.6.2 with parameters specified in Table 7.3.1D-1 and Table 7.3.1D-2. The reference sensitivity is defined to be met with E-UTRA uplink assigned to one band (that differs from the ProSe operating band) and all E-UTRA downlink carriers active. The E-UTRA uplink resource blocks shall be located as close as possible to E-UTRA ProSe operating band but confined within the transmission bandwidth configuration for the channel bandwidth (Table 5.6-1). The uplink configuration for the E-UTRA operating band is specified in Table 7.3.1D-3. NOTE: The E-UTRA uplink channel bandwidth and transmission bandwidth specified in this Table 7.3.1D-3 are intended for conformance tests and does not restrict the operating conditions of the network. Table 7.3.1D-3: Uplink configuration for E-UTRA band / E-UTRA CA band | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 7.3.1D |
5,267 | 4.13.2.8 Number of successful reconfigurations of LTE DRB to LWA DRB | a) This measurement provides the number of attempted reconfigurations of LTE DRB to LWA DRB. b) CC c) On receipt of RRCConnectionReconfigurationComplete message (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [18]) by the eNB, corresponding to the transmitted RRCConnectionReconfiguration message which triggered the measurement "Number of attempted reconfigurations of LTE DRB to LWA DRB" (see clause 4.13.2.7). d) An integer value e) LWI.LteToLwaDrbReconfSucc f) WLANMobilitySet g) Valid for packet switched traffic h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.13.2.8 |
5,268 | 4.12.3 Deregistration procedure for untrusted non-3gpp access | Figure 4.12.3-1: Deregistration procedure for untrusted non-3gpp access 1. The Deregistration procedure is triggered by one of the events: 1a. For UE-initiated Deregistration as in steps from 1 to 7 of Figures 4.2.2.3.2-1. 1b. For network initiated deregistration as in steps from 1 to 6 of Figure 4.2.2.3.3-1. If the UE is in CM-CONNECTED state either in 3GPP access, non-3GPP access or both, - the AMF may explicitly deregister the UE by sending a Deregistration request message ( Deregistration type, access type set to non-3GPP) to the UE as in step 2 of Figure 4.2.2.3.3-1. - the UDM may want to request the deletion of the subscribers RM contexts and PDU Sessions with the reason for removal set to subscription withdrawn to the registered AMF as in step 1 of Figure 4.2.2.3.3-1. 2. AMF to N3IWF: The AMF sends a N2 Context UE Release Command message to the N3IWF with the cause set to Deregistration to release N2 signalling as defined in step 4 of clause 4.12.4.2. 3. N3IWF to UE: The N3IWF sends INFORMATIONAL Request (Delete payload) message to the UE. The Delete payload is included to indicate the release of the IKE SA. 4. UE to N3IWF: The UE sends an empty INFORMATIONAL Response message to acknowledge the release of the IKE SA as described in RFC 7296 [3]. Non-3GPP access specific resources are released including the IKEv2 tunnel (and the associated IPSec resources) and the local UE contexts in N3IWF (N3 tunnel Id). 5. N3IWF to AMF: The N3IWF acknowledges the N2 UE Context Release Command message by sending N2 UE Context Release Complete message to the AMF as defined in step 7 of clause 4.12.4.2. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.12.3 |
5,269 | 5.33.3 QoS Monitoring for packet delay 5.33.3.1 General | QoS Monitoring for packet delay can be applied based on 3rd party application request or PCF policy control or both, e.g. to assist URLLC services. The packet delay between UE and PSA UPF is a combination of the RAN part of UL/DL packet delay as defined in TS 38.314[ NR; Layer 2 measurements ] [120] and UL/DL packet delay between NG-RAN and PSA UPF. The NG-RAN is required to provide the QoS monitoring results on the RAN part of UL/DL packet delay measurement. The measurement of the UL/DL packet delay between NG-RAN and PSA UPF can be performed on different levels of granularities, i.e. per QoS Flow per UE level, or per GTP-U path level, subject to the operators' configuration. The PCF generates the authorized QoS Monitoring policy for a service data flow based on the QoS Monitoring request received from the AF (as described in clause 6.1.3.21 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]). The PCF includes the authorized QoS Monitoring policy in the PCC rule and provides it to the SMF. When SMF receives the authorized QoS Monitoring policy for packet delay in a PCC rule from the PCF (as described in clause 6.1.3.21 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]), SMF configures the UPF(s) and NG-RAN to perform delay measurements according to the method selected: per QoS Flow per UE QoS measurement (as described in clause 5.33.3.2) or per GTP-U Path measurement (as described in clause 5.33.3.3). The SMF configure the UPF to report the QoS monitoring results for the QoS Flow as described in clause 5.8.2.18 with parameters determined by the SMF based on the authorized QoS Monitoring policy received from the PCF and/or local configuration. The UPF reporting behaviour for QoS Monitoring for packet delay of a QoS Flow is the same when per QoS Flow per UE level measurement (described further in clause 5.33.3.2) or when per GTP-U path level measurement (described further in clause 5.33.3.3) is used. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.33.3 |
5,270 | 4.3.18 Multimedia Priority Service 4.3.18.1 General | Multimedia Priority Service (MPS) allows certain subscribers (i.e. Service Users as per TS 22.153[ Multimedia priority service ] [68]) priority access to system resources in situations such as during congestion, creating the ability to deliver or complete sessions of a high priority nature. Service Users are government-authorized personnel, emergency management officials and/or other authorized users. MPS supports priority sessions on an "end-to-end" priority basis. MPS is based on the ability to invoke, modify, maintain and release sessions with priority, and deliver the priority media packets under network congestion conditions. MPS is supported in a roaming environment when roaming agreements are in place and where regulatory requirements apply. NOTE 1: If a session terminates on a server in the Internet (e.g. web-based service), then the remote end and the Internet transport are out of scope for this specification. MPS is supported for Service Users using UEs connecting via 3GPP access. MPS is also supported for Service Users using UEs that support connecting via Trusted or Untrusted non-3GPP access via WLAN as specified in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2] for MPS. ePDG selection is according to clause 4.5.4 in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. A Service User obtains priority access to the Radio Access Network by using the Access Class Barring mechanism according to TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37] and TS 22.011[ Service accessibility ] [67]. This mechanism provides preferential access to UEs based on its assigned Access Class. If a Service User belongs to one of the special access-classes as defined in TS 22.011[ Service accessibility ] [67], the UE has preferential access to the network compared to ordinary users in periods of congestion. MPS subscription allows users to receive priority services, if the network supports MPS. The same MPS subscription applies to access via 3GPP access and non-3GPP access via WLAN. MPS subscription entitles a USIM with special Access Class(es). MPS subscription includes indication for support of Priority EPS Bearer Service, IMS priority service and CS Fallback priority service support for the end user. Priority level regarding Priority EPS Bearer Service and IMS are also part of the MPS subscription information. The usage of priority level is defined in TS 23.203[ Policy and charging control architecture ] [6] and TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [52]. NOTE 2: The MPS subscription on the USIM is also used for 3GPP procedures with priority treatment over WLAN for UEs that support MPS over Trusted and Untrusted non-3GPP access via WLAN feature. NOTE 3: The above statements for the Priority EPS Bearer Service are also applicable for the MPS for Data Transport Service. An MPS Service User is treated as an On Demand MPS subscriber or not, based on regional/national regulatory requirements. On Demand service is based on Service User invocation/revocation explicitly and applied to the PDN connections for an APN. When not On Demand, MPS service does not require invocation, and provides priority treatment for all EPS bearers for a given Service User after attachment to the EPS network. NOTE 4: According to regional/national regulatory requirements and operator policy, On-Demand MPS Service Users can be assigned the highest priority. Since the Service User has an access class within the range for priority services, the Establishment Cause in RRC connection request is set to highPriorityAccess. When the eNodeB receives mobile initiated signalling with establishment cause set to highPriorityAccess, the eNodeB handles the RRC connection request with priority. When the MME receives and verifies mobile initiated signalling with establishment cause set to highPriorityAccess, the MME establishes the S1 bearer with priority. The terminating network identifies the priority of the MPS session and applies priority treatment, including paging with priority, to ensure that the MPS session can be established with priority to the terminating user (either a Service User or normal user). Priority treatment for MPS includes priority message handling, including priority treatment during authentication, security, and location management procedures. Priority treatment for MPS session requires appropriate ARP and QCI (where necessary for non-GBR bearers) setting for bearers according to the operator's policy. When an MPS session is requested by a Service User, the following bearer management principles apply in the network: - EPS bearers (including default bearer) employed in an MPS session shall be assigned ARP value settings appropriate for the priority level of the Service User. - Setting ARP pre-emption capability and vulnerability for MPS bearers, subject to operator policies and depending on national/regional regulatory requirements. - Pre-emption of non-Service Users over Service Users during network congestion situation, subject to operator policy and national/regional regulations. Priority treatment is applicable to IMS based multimedia services, priority EPS bearer services (PS data without IMS interaction) and CS Fallback. For Multimedia Priority services any EPC functions, procedures and capabilities are provided according to this clause's specification except when specified differently in the following clauses. | 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.18 |
5,271 | 5.5.2.3.2 Network-initiated de-registration procedure completion by the UE | Upon receiving the DEREGISTRATION REQUEST message, if the DEREGISTRATION REQUEST message indicates "re-registration required" and the de-registration request is for 3GPP access, the UE shall perform a local release of the PDU sessions over 3GPP access, if any. If a PDU session is associated with one or more multicast MBS sessions, the UE shall locally leave the associated multicast MBS sessions. If there is an MA PDU session with user plane resources established on both 3GPP access and non-3GPP access in the same PLMN or in different PLMNs, the UE shall perform a local release of the user plane resources on 3GPP access. If there is an MA PDU session with user plane resources established on 3GPP access only, the UE shall perform a local release of the MA PDU session. If the MA PDU session is associated with one or more multicast MBS sessions, the UE shall locally leave the associated multicast MBS sessions. The UE shall stop the timer(s) T3346, T3396, T3584, T3585 and 5GSM back-off timer(s) not related to congestion control (see subclause 6.2.12), if running. If the UE is operating in single-registration mode, the UE shall also stop the ESM back-off timer(s) not related to congestion control (see subclause 6.3.6 in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]), if running. The UE shall send a DEREGISTRATION ACCEPT message to the network and enter the state 5GMM-DEREGISTERED for 3GPP access. Furthermore, the UE shall, after the completion of the de-registration procedure, and the release of the existing NAS signalling connection, if any Tsor-cm timer(s) were running and have stopped, the UE shall 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]) on 3GPP access, otherwise initiate an initial registration. The UE should also re-establish any previously established PDU sessions over 3GPP access. For any previously established MA PDU sessions with user plane resources established on both accesses the UE should also re-establish the user plane resources over 3GPP access, and for any previously established MA PDU sessions with user plane resources established only on the 3GPP access the UE should re-establish the MA PDU session over 3GPP access. Upon receiving the DEREGISTRATION REQUEST message, if the DEREGISTRATION REQUEST message indicates "re-registration required" and the de-registration request is for non-3GPP access, the UE shall perform a local release of the PDU sessions over non-3GPP access, if any. If there is an MA PDU session with user plane resources established on both 3GPP access and non-3GPP access in the same PLMN or in different PLMNs, the UE shall perform a local release of the user plane resources on non-3GPP access. If there is an MA PDU session with a PDN connection as a user-plane resource and user plane resources established on non-3GPP access, the UE shall perform a local release of the user plane resources on non-3GPP access. If there is an MA PDU session with user plane resources established on non-3GPP access only, the UE shall perform a local release of the MA PDU session. The UE shall stop the timer(s) T3346, T3396, T3584 and T3585, if it is running. The UE shall send a DEREGISTRATION ACCEPT message to the network and enter the state 5GMM-DEREGISTERED for non-3GPP access. Furthermore, the UE shall, after the completion of the de-registration procedure, and the release of the existing NAS signalling connection, initiate an initial registration over non-3GPP. The UE should also re-establish any previously established PDU sessions over non-3GPP access. For any previously established MA PDU sessions with user plane resources established on both accesses the UE should also re-establish the user plane resources over non-3GPP access, and for any previously established MA PDU sessions with user plane resources established only on the non-3GPP access the UE should re-establish the MA PDU session over non-3GPP access, and for any previously established MA PDU sessions with a PDN connection as a user-plane resource and user plane resources established on non-3GPP access the UE should re-establish the user plane resources over non-3GPP access. Upon receiving the DEREGISTRATION REQUEST message, if the DEREGISTRATION REQUEST message indicates "re-registration required" and the de-registration request is for both 3GPP access and non-3GPP access when the UE is registered in the same PLMN for both accesses, the UE shall perform a local release of the MA PDU sessions and PDU sessions over both 3GPP access and non-3GPP access, if any. If an MA PDU session or a PDU sessions is associated with one or more multicast MBS sessions, the UE shall locally leave the associated multicast MBS sessions. The UE shall stop the timer(s) T3346, T3396, T3584 and T3585, if it is running. The UE shall send a DEREGISTRATION ACCEPT message to the network and enter the state 5GMM-DEREGISTERED for both 3GPP access and non-3GPP access. Furthermore, the UE shall, after the completion of the de-registration procedure, and the release of the existing NAS signalling connection, if any Tsor-cm timer(s) were running and have stopped, the UE shall 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]) on 3GPP access, otherwise initiate an initial registration over both 3GPP access and non-3GPP access. The UE should also re-establish any previously established PDU sessions over both 3GPP access and non-3GPP access. For any previously established MA PDU sessions the UE should also re-establish the MA PDU session and the user plane resources which were established previously. NOTE 1: When the de-registration type indicates "re-registration required", user interaction is necessary in some cases when the UE cannot re-establish the PDU session (s), if any, automatically. Upon receiving the DEREGISTRATION REQUEST message, if the DEREGISTRATION REQUEST message indicates "re-registration not required" and the de-registration request is for 3GPP access, the UE shall perform a local release of the PDU sessions over 3GPP access, if any. If a PDU session is associated with one or more multicast MBS sessions, the UE shall locally leave the associated multicast MBS sessions. If there is an MA PDU session with user plane resources established on both 3GPP access and non-3GPP access in the same PLMN or in different PLMNs, the UE shall perform a local release of the user plane resources on 3GPP access. If there is an MA PDU session with user plane resources established on 3GPP access only, the UE shall perform a local release of the MA PDU session. If the MA PDU session is associated with one or more multicast MBS sessions, the UE shall locally leave the associated multicast MBS sessions. The UE shall send a DEREGISTRATION ACCEPT message to the network and enter the state 5GMM-DEREGISTERED for 3GPP access. Upon receiving the DEREGISTRATION REQUEST message, if the DEREGISTRATION REQUEST message indicates "re-registration not required" and the de-registration request is for non-3GPP access, the UE shall perform a local release of the PDU sessions over non-3GPP access, if any. If there is an MA PDU session with user plane resources established on both 3GPP access and non-3GPP access in the same PLMN or in different PLMNs, the UE shall perform a local release of the user plane resources on non-3GPP access. If there is an MA PDU session with a PDN connection as a user-plane resource and user plane resources established on non-3GPP access, the UE shall perform a local release of the user plane resources on non-3GPP access. If there is an MA PDU session with user plane resources established on non-3GPP access only, the UE shall perform a local release of the MA PDU session. The UE shall send a DEREGISTRATION ACCEPT message to the network and enter the state 5GMM-DEREGISTERED for non-3GPP access. Upon receiving the DEREGISTRATION REQUEST message, if the DEREGISTRATION REQUEST message indicates "re-registration not required" and the de-registration request is for both 3GPP access and non-3GPP access when the UE is registered in the same PLMN for both accesses, the UE shall perform a local release of the MA PDU sessions and PDU sessions over both 3GPP access and non-3GPP access, if any. If an MA PDU session or a PDU session is associated with one or more multicast MBS sessions, the UE shall locally leave the associated multicast MBS sessions. The UE shall send a DEREGISTRATION ACCEPT message to the network and enter the state 5GMM-DEREGISTERED for both 3GPP access and non-3GPP access. Upon receiving the DEREGISTRATION REQUEST message, if the DEREGISTRATION REQUEST message includes the rejected NSSAI, the UE 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 store 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 in the current PLMN or SNPN over any access until switching off the UE, the UICC containing the USIM is removed, an entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, if the UE does not support access to an SNPN using credentials from a credentials holder and equivalent SNPNs, the selected entry of the "list of subscriber data" is updated, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both 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 store the rejected S-NSSAI(s) in the rejected NSSAI for the current registration area as described 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, an 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 store 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 2: 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 a 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. Upon sending a DEREGISTRATION ACCEPT message, the UE shall delete the rejected NSSAI as specified in subclause 4.6.2.2. Regardless of the 5GMM cause value received in the DEREGISTRATION REQUEST message via satellite NG-RAN, -- if the UE receives the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE in the DEREGISTRATION REQUEST message, the UE shall store the TAI(s) belonging to the serving PLMN or equivalent PLMN(s) and ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s) included in the IE, if not already stored, into the list of "5GS forbidden tracking areas for roaming"; and - if the UE receives the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for regional provision of service" IE in the DEREGISTRATION REQUEST message, the UE shall store the TAI(s) belonging to the serving PLMN or equivalent PLMN(s) and ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s) included in the IE, if not already stored, into the list of "5GS forbidden tracking areas for regional provision of service". Upon receiving the DEREGISTRATION REQUEST message, the 5G-RG shall delete the contexts of the AUN3 devices behind the 5G-RG, if any. If the de-registration type indicates "re-registration required", then the UE shall ignore the 5GMM cause IE if received. If the de-registration type indicates "re-registration not required", the UE shall take the actions depending on the received 5GMM cause value: #3 (Illegal UE); #6 (Illegal ME) The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. - In case of PLMN, the UE shall consider the USIM as invalid for 5GS services until switching off, the UICC containing the USIM is removed or the timer T3245 expires as described in subclause 5.3.19A.1; In case of SNPN, if the UE is not registered for onboarding services in SNPN and the UE does not support access to an SNPN using credentials from a credentials holder and does not support equivalent SNPNs, the UE shall consider the selected entry of the "list of subscriber data" with the SNPN identity of the current SNPN as invalid until the UE is switched off, the entry is updated or the timer T3245 expires as described in subclause 5.3.19A.2. In case of SNPN, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs, or both, the UE shall consider the selected entry of the "list of subscriber data" as invalid for 3GPP access until the UE is switched off, the entry is updated or the timer T3245 expires as described in subclause 5.3.19A.2. Additionally, if EAP based primary authentication and key agreement procedure using EAP-AKA' or 5G AKA based primary authentication and key agreement procedure was performed in the current SNPN, the UE shall consider the USIM as invalid for the current SNPN until switching off, the UICC containing the USIM is removed or the timer T3245 expires as described in subclause 5.3.19A.2. If the UE is not registered for onboarding services in SNPN, the UE shall delete the list of equivalent PLMNs (if any) or the list of equivalent SNPNs (if any), and shall enter the state 5GMM-DEREGISTERED.NO-SUPI. If the de-registration request is for 3GPP access only or for both 3GPP access and non-3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, TAI list and eKSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when a DETACH REQUEST is received with the EMM cause with the same value and with detach type set to "re-attach not required". The USIM shall be considered as invalid also for non-EPS services until switching off or the UICC containing the USIM is removed or the timer T3245 expires as described in subclause 5.3.7a in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]. If the UE is registered for onboarding services in SNPN, the UE shall reset the registration attempt counter, store the SNPN identity in the "permanently forbidden SNPNs" list for onboarding services, enter state 5GMM-DEREGISTERED.PLMN-SEARCH, and perform an SNPN selection or an SNPN selection for onboarding services according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the UE also supports the registration procedure over the other access, the UE shall in addition handle 5GMM parameters and 5GMM state for this access, as described for this 5GMM cause value. #7 (5GS services not allowed). The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. In case of PLMN, the UE shall consider the USIM as invalid for 5GS services until switching off, the UICC containing the USIM is removed or the timer T3245 expires as described in subclause 5.3.19A.1; In case of SNPN, if the UE is not registered for onboarding services in SNPN and the UE does not support access to an SNPN using credentials from a credentials holder and does not support equivalent SNPNs, the UE shall consider the selected entry of the "list of subscriber data" with the SNPN identity of the current SNPN as invalid for 5GS services until the UE is switched off, or the entry is updated or the timer T3245 expires as described in subclause 5.3.19A.2. In case of SNPN, if the UE is not registered for onboarding services in SNPN and the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs, or both, the UE shall consider the selected entry of the "list of subscriber data" as invalid for 3GPP access until the UE is switched off, the entry is updated or the timer T3245 expires as described in subclause 5.3.19A.2. Additionally, if EAP based primary authentication and key agreement procedure using EAP-AKA' or 5G AKA based primary authentication and key agreement procedure was performed in the current SNPN, the UE shall consider the USIM as invalid for the current SNPN until switching off, the UICC containing the USIM is removed or the timer T3245 expires as described in subclause 5.3.19A.2. If the UE is not registered for onboarding services in SNPN, the UE shall enter the state 5GMM-DEREGISTERED.NO-SUPI. If the de-registration request is for 3GPP access only or for both 3GPP access and non-3GPP access and and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list and eKSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when a DETACH REQUEST is received with the EMM cause with the same value and with detach type set to "re-attach not required". If the UE is registered for onboarding services in SNPN, the UE shall reset the registration attempt counter, store the SNPN identity in the "permanently forbidden SNPNs" list for onboarding services, enter state 5GMM-DEREGISTERED.PLMN-SEARCH, and perform an SNPN selection or an SNPN selection for onboarding services according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the UE also supports the registration procedure over the other access, the UE shall in addition handle 5GMM parameters and 5GMM state for this access, as described for this 5GMM cause value. #11 (PLMN not allowed). This cause value received from a cell belonging to an SNPN is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.2.3.4. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. The UE shall delete the list of equivalent PLMNs, shall reset the registration attempt counter. For 3GPP access the UE shall enter the state 5GMM-DEREGISTERED.PLMN-SEARCH, and for non-3GPP access the UE shall enter state 5GMM-DEREGISTERED.LIMITED-SERVICE. The UE shall store the PLMN identity in the forbidden PLMN list as specified in subclause 5.3.13A and if the UE is configured to use timer T3245 then the UE shall start timer T3245 and proceed as described in subclause 5.3.19A.1. For 3GPP access the UE shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5], and for non-3GPP access the UE shall perform network selection as defined in 3GPP TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [18]. If the de-registration request is for 3GPP access only or for both 3GPP access and non-3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list, eKSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when a DETACH REQUEST is received with the EMM cause with the same value and with detach type set to "re-attach not required". If the UE also supports the registration procedure over the other access to the same PLMN, the UE shall in addition handle 5GMM parameters and 5GMM state for this access, as described for this 5GMM cause value. If the UE receives the Disaster return wait range IE in the DEREGISTRATION REQUEST message and the UE supports MINT, the UE shall delete the disaster return wait range stored in the ME, if any, and store the disaster return wait range included in the Disaster return wait range IE in the ME. #12 (Tracking area not allowed). The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete last visited registered TAI and TAI list. If the UE is not registering or has not registered to the same PLMN over both 3GPP access and non-3GPP access, the UE shall additionally delete 5G-GUTI and ngKSI. The UE shall reset the registration attempt counter and shall enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE. If the UE is not operating in SNPN access operation mode and the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for regional provision of service" IE is not included in the DEREGISTRATION REQUEST message, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for regional provision of service". Otherwise, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for regional provision of service" for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the de-registration request is for 3GPP access only or for both 3GPP access and non-3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters, EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list, eKSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when a DETACH REQUEST is received with the EMM cause with the same value and with detach type set to "re-attach not required". #13 (Roaming not allowed in this tracking area). The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete last visited registered TAI and TAI list. If the UE is not registering or has not registered to the same PLMN over both 3GPP access and non-3GPP access, the UE shall additionally delete 5G-GUTI, ngKSI, and the list of equivalent PLMNs (if available) or the list of equivalent SNPNs (if available). The UE shall reset the registration attempt counter. For 3GPP access the UE shall change to state 5GMM-DEREGISTERED.PLMN-SEARCH, and for non-3GPP access the UE shall change to state 5GMM-DEREGISTERED.LIMITED-SERVICE. If the UE is not operating in SNPN access operation mode and the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE is not included in the DEREGISTRATION REQUEST message, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming". Otherwise, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription. For 3GPP access the UE shall perform a PLMN selection or SNPN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5], and for non-3GPP access the UE shall perform network selection as defined in 3GPP TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [18]. If the de-registration request is for 3GPP access only or for both 3GPP access and non-3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list, eKSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when a DETACH REQUEST is received with the EMM cause with the same value and with detach type set to "re-attach not required". #15 (No suitable cells in tracking area). The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any last visited registered TAI and TAI list. If the UE is not registering or has not registered to the same PLMN over both 3GPP access and non-3GPP access, the UE shall additionally delete 5G-GUTI and ngKSI. The UE shall reset the registration attempt counter and shall enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE. If the UE is not operating in SNPN access operation mode and the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE is not included in the DEREGISTRATION REQUEST message, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming". Otherwise, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription. The UE shall search for a suitable cell in another tracking area 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]. If the de-registration request is for 3GPP access only or for both 3GPP access and non-3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list, eKSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when a DETACH REQUEST is received with the EMM cause with the same value and with detach type set to "re-attach not required". If received over non-3GPP access and de-registration request is for non-3GPP access only, the cause shall be considered as an abnormal case and the behaviour of the UE for this case is specified in subclause 5.5.2.3.4. #22 (Congestion). If the T3346 value IE is present in the DEREGISTRATION REQUEST message and the value indicates that this timer is neither zero nor deactivated, the UE shall proceed as described below, otherwise it shall be considered as an abnormal case and the behaviour of the UE for this case is specified in subclause 5.5.2.3.4. The UE shall stop timer T3346 if it is running, set the 5GS update status to 5U2 NOT UPDATED, reset the registration attempt counter and enter the state 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION. The UE shall start timer T3346 with the value provided in the T3346 value IE. If the de-registration request is for 3GPP access only or for both 3GPP access and non-3GPP access and the UE is operating in the single-registration mode, the UE shall set the EPS update status to EU2 NOT UPDATED, reset the attach attempt counter and shall enter the state EMM-DEREGISTERED. #27 (N1 mode not allowed). The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. Additionally, the UE shall reset the registration attempt counter and shall enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE. The UE shall disable the N1 mode capability for both 3GPP access and non-3GPP access (see subclause 4.9). If the de-registration request is for 3GPP access only or for both 3GPP access and non-3GPP access and the UE is operating in single-registration mode, the UE shall in addition set the EPS update status to EU3 ROAMING NOT ALLOWED and shall delete any 4G-GUTI, last visited registered TAI, TAI list and eKSI. Additionally, the UE shall reset the attach attempt counter and enter the state EMM-DEREGISTERED. #36 (IAB-node operation not authorized). This cause value is only applicable when received over 3GPP access by a UE operating as an IAB-node. This cause value received from a 5G access network other than 3GPP access or received by a UE not operating as an IAB-node is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.2.3.4. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. If: 1) the UE is not operating in SNPN access operation mode, i) the UE shall delete the list of equivalent PLMNs and reset the registration attempt counter and store the PLMN identity in the forbidden PLMN list as specified in subclause 5.3.13A and if the UE is configured to use timer T3245 then the UE shall start timer T3245 and proceed as described in subclause 5.3.19a.1. The UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]; and ii) If the UE is operating in single-registration mode, the UE shall in addition handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list, eKSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when DETACH REQUEST is received with the EMM cause with the same value and with detach type set to "re-attach not required"; or 2) the UE is operating in SNPN access operation mode, i) the UE shall reset the registration attempt counter and store the SNPN identity in the "temporarily forbidden SNPNs" list for 3GPP access 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. The UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. #62 (No network slices available). The UE shall set the 5GS update status to 5U2 NOT UPDATED and enter state 5GMM-DEREGISTERED.NORMAL-SERVICE or 5GMM-DEREGISTERED.PLMN-SEARCH. Additionally, the UE shall reset the registration attempt counter. The UE receiving the rejected NSSAI in the DEREGISTRATION REQUEST 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 store 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, an 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 store the rejected S-NSSAI(s) in the rejected NSSAI for the current registration area as described 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 store 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 3: 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 a 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 has an allowed NSSAI or configured NSSAI that contains S-NSSAI(s) which are not included in the rejected NSSAI, the UE may stay in the current serving cell, apply the normal cell reselection process and start an initial registration with a requested NSSAI that includes any S-NSSAI from the allowed NSSAI or the configured NSSAI that is not in the rejected NSSAI. Otherwise the UE may perform a PLMN selection or SNPN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] and additionally, the UE may disable the N1 mode capability for the current PLMN or SNPN if the UE does not have an allowed NSSAI and each S-NSSAI in configured NSSAI, if available, was rejected with cause "S-NSSAI not available in the current PLMN or SNPN" or "S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization" as described in subclause 4.9. If the UE has neither allowed NSSAI for the current PLMN or SNPN nor configured NSSAI for the current PLMN or SNPN and, 1) if at least one S-NSSAI in the default configured NSSAI is not rejected, the UE may stay in the current serving cell, apply the normal cell reselection process, and start an initial registration with a requested NSSAI with that default configured NSSAI; or 2) if all the S-NSSAI(s) in the default configured NSSAI are rejected and at least one S-NSSAI is rejected due to "S-NSSAI not available in the current registration area", i) if the UE is not operating in SNPN access operation mode and the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE is not included in the DEREGISTRATION REQUEST message, the UE shall store the TAI(s) belonging to current registration area in the list of "5GS forbidden tracking areas for roaming", memorize the TAI(s) belonging to current registration area were stored in the list of "5GS forbidden tracking areas for roaming" for S-NSSAI is rejected due to "S-NSSAI not available in the current registration area" and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE. The UE shall search for a suitable cell in another tracking area not belonging to current registration area 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]; or ii) if the UE is operating in SNPN access operation mode, the UE shall store the TAI(s) belonging to current registration area in the list of "5GS forbidden tracking areas for roaming", memorize the TAI(s) belonging to current registration area were stored in the list of "5GS forbidden tracking areas for roaming" for S-NSSAI is rejected due to "S-NSSAI not available in the current registration area" for the current SNPN 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, and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE. The UE shall search for a suitable cell in another tracking area not belonging to current registration area 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]. 3) otherwise, the UE may perform a PLMN selection or SNPN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] and additionally, the UE may disable the N1 mode capability for the current PLMN or SNPN if each S-NSSAI in the default configured NSSAI was rejected with cause "S-NSSAI not available in the current PLMN or SNPN" or "S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization" as described in subclause 4.9. If 1) the UE has allowed NSSAI for the current PLMN or SNPN or configured NSSAI for the current PLMN or SNPN or both and all the S-NSSAIs included in the allowed NSSAI or the configured NSSAI or both are rejected; or 2) the UE has neither allowed NSSAI for the current PLMN or SNPN nor configured NSSAI for the current PLMN or SNPN and all the S-NSSAIs included in the default configured NSSAI are rejected, and the UE has rejected NSSAI for the maximum number of UEs reached, and the UE wants to obtain services in the current serving cell without performing a PLMN selection or SNPN selection, the UE may stay in the current serving cell and attempt to use the rejected S-NSSAI(s) for the maximum number of UEs reached in the current serving cell after the rejected S-NSSAI(s) are removed as described in subclause 4.6.2.2. If the de-registration request is for 3GPP access only or for both 3GPP access and non-3GPP access and the UE is operating in single-registration mode, the UE shall in addition set the EPS update status to EU2 NOT UPDATED, reset the attach attempt counter and enter the state EMM-DEREGISTERED. #72 (Non-3GPP access to 5GCN not allowed). If received over non-3GPP access when the UE is registered over non-3GPP access, or received over 3GPP access and de-registration request is for non-3GPP access when the UE is registered in the same PLMN for both accesses, the UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete 5G-GUTI, last visited registered TAI, TAI list and ngKSI for non-3GPP access. Additionally, the UE shall reset the registration attempt counter and enter the state 5GMM-DEREGISTERED for non-3GPP access. NOTE 4: The 5GMM sublayer states, the 5GMM parameters and the registration status are managed per access type independently, i.e. 3GPP access or non-3GPP access (see subclauses 4.7.2 and 5.1.3). The UE shall disable the N1 mode capability for non-3GPP access (see subclause 4.9.3). As an implementation option, if the UE is not currently registered over 3GPP access, the UE may enter the state 5GMM-DEREGISTERED.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 ] [5]. If received over 3GPP access and de-registration request is for 3GPP access only, the cause shall be considered as an abnormal case and the behaviour of the UE for this case is specified in subclause 5.5.2.3.4. #74 (Temporarily not authorized for this SNPN). 5GMM cause #74 is only applicable when received from a cell belonging to an SNPN. 5GMM cause #74 received from a cell not belonging to an SNPN is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.2.3.4. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list, ngKSI and the list of equivalent SNPNs (if available). The UE shall reset the registration attempt counter and shall store the SNPN identity in the "temporarily forbidden SNPNs" list or "temporarily forbidden SNPNs for access for localized services in SNPN" list if the SNPN is an SNPN selected for localized services in SNPN as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] for the specific access type for which the message was received and the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the UE supports access to an SNPN using credentials from a credentials holder, the UE shall store the SNPN identity in the "temporarily forbidden SNPNs" list along with the GIN(s) broadcasted by the SNPN if any, for the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the UE supports access to an SNPN providing access for localized services in SNPN and the access for localized services in SNPN has been enabled, the UE shall store the SNPN identity in the list of "temporarily forbidden SNPNs for access for localized services in SNPN" (if the SNPN was selected according to subclause 4.9.3.1.1 bullet a0) of 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]) along with the GIN(s) broadcasted by the SNPN if any, for the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the UE is not registered for onboarding services in SNPN, the UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the UE is registered for onboarding services in SNPN, the UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection or an SNPN selection for onboarding services according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. #75 (Permanently not authorized for this SNPN). 5GMM cause #75 is only applicable when received from a cell belonging to an SNPN with a globally-unique SNPN identity. 5GMM cause #75 received from a cell not belonging to an SNPN or a cell belonging to an SNPN with a non-globally-unique SNPN identity is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.2.3.4. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list, ngKSI and the list of equivalent SNPNs (if available). The UE shall reset the registration attempt counter and store the SNPN identity in the "permanently forbidden SNPNs" list or "permanently forbidden SNPNs for access for localized services in SNPN" list if the SNPN is an SNPN selected for localized services in SNPN as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] for the specific access type for which the message was received and the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the UE supports access to an SNPN using credentials from a credentials holder, the UE shall store the SNPN identity in the "permanently forbidden SNPNs" list along with the GIN(s) broadcasted by the SNPN if any, for the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the UE supports access to an SNPN providing access for localized services in SNPN and the access for localized services in SNPN has been enabled, the UE shall store the SNPN identity in the list of "permanently forbidden SNPNs for access for localized services in SNPN" (if the SNPN was selected according to subclause 4.9.3.1.1 bullet a0) of 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]) along with the GIN(s) broadcasted by the SNPN if any, for the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the UE is not registered for onboarding services in SNPN, the UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the UE is registered for onboarding services in SNPN, the UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection or an SNPN selection for onboarding services according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. #76 (Not authorized for this CAG or authorized for CAG cells only). This cause value received via non-3GPP access or from a cell belonging to an SNPN is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.2.3.4. The UE shall set the 5GS update status to 5U3.ROAMING NOT ALLOWED, store the 5GS update status according to subclause 5.1.3.2.2, and reset the registration attempt counter. If 5GMM cause #76 is received from: 1) a CAG cell, and if the UE receives a "CAG information list" in the CAG information list IE or the Extended CAG information list IE included in the DEREGISTRATION REQUEST message, the UE shall: i) 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; ii) 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 5: 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. iii) 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. Otherwise, the UE shall delete the CAG-ID(s) of the cell from the "allowed CAG list" for the current PLMN, if the CAG-ID(s) are authorized based on the "Allowed CAG list". In the case the "allowed CAG list" for the current PLMN only contains a range of CAG-IDs, how the UE deletes the CAG-ID(s) of the cell from the "allowed CAG list" for the current PLMN is up to UE implementation. In addition: i) if the entry in the "CAG information list" for the current PLMN does not include an "indication that the UE is only allowed to access 5GS via CAG cells" or if the entry in the "CAG information list" for the current PLMN includes an "indication that the UE is only allowed to access 5GS via CAG cells" and one or more CAG-ID(s) are authorized based on the updated "allowed CAG list" for the current PLMN, then the UE shall enter the state 5GMM-DEREGISTERED.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"; ii) if the entry in the "CAG information list" for the current PLMN includes an "indication that the UE is only allowed to access 5GS via CAG cells" and no CAG-ID is authorized based on the updated "allowed CAG list" for the current PLMN, then the UE shall enter the state 5GMM-DEREGISTERED.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 iii) if the "CAG information list" does not include an entry for the current PLMN, then the UE shall enter the state 5GMM-DEREGISTERED.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". 2) a non-CAG cell, and if the UE receives a "CAG information list" in the CAG information list IE or the Extended CAG information list IE included in the DEREGISTRATION REQUEST message, the UE shall: i) 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; ii) 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 6: 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. iii) 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. Otherwise, the UE shall store an "indication that the UE is only allowed to access 5GS via CAG cells" in the entry of the "CAG information list" for the current PLMN, if any. If the "CAG information list" stored in the UE does not include the current PLMN's entry, the UE shall add an entry for the current PLMN to the "CAG information list" and store an "indication that the UE is only allowed to access 5GS via CAG cells" in the entry of the "CAG information list" for the current PLMN. If the UE does not have a stored "CAG information list", the UE shall create a new "CAG information list" and add an entry with an "indication that the UE is only allowed to access 5GS via CAG cells" for the current PLMN. In addition: i) if one or more CAG-ID(s) are authorized based on the "allowed CAG list" for the current PLMN, then the UE shall enter the state 5GMM-DEREGISTERED.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; or ii) if no CAG-ID is authorized based on the "allowed CAG list" for the current PLMN, then the UE shall enter the state 5GMM-DEREGISTERED.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". If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall in addition set the EPS update status to EU3 ROAMING NOT ALLOWED, reset the attach attempt counter and enter the state EMM-DEREGISTERED. #77 (Wireline access area not allowed). 5GMM cause #77 is only applicable when received from a wireline access network by the 5G-RG or the W-AGF acting on behalf of the FN-CRG (or on behalf of the N5GC device). 5GMM cause #77 received from a 5G access network other than a wireline access network and 5GMM cause #77 received by the W-AGF acting on behalf of the FN-BRG are considered as abnormal cases and the behaviour of the UE is specified in subclause 5.5.2.3.4. When received over wireline access network, the 5G-RG and the W-AGF acting on behalf of the FN-CRG (or on behalf of the N5GC device) shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2), shall delete 5G-GUTI, last visited registered TAI, TAI list and ngKSI, shall reset the registration attempt counter, shall enter the state 5GMM-DEREGISTERED and shall act as specified in subclause 5.3.23. NOTE 7: The 5GMM sublayer states, the 5GMM parameters and the registration status are managed per access type independently, i.e. 3GPP access or non-3GPP access (see subclauses 4.7.2 and 5.1.3). #78 (PLMN not allowed to operate at the present UE location). This cause value received from a non-satellite NG-RAN cell is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.2.3.4. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete last visited registered TAI and TAI list. If the UE is not registering or has not registered to the same PLMN over both 3GPP access and non-3GPP access, the UE shall additionally delete 5G-GUTI and ngKSI. Additionally, the UE shall reset the registration attempt counter. The UE shall store the PLMN identity and, if it is known, the current geographical location in the list of "PLMNs not allowed to operate at the present UE location" and shall start a corresponding timer instance (see subclause 4.23.2). The UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the de-registration request is for 3GPP access only or for both 3GPP access and non-3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list, eKSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when a DETACH REQUEST is received with the EMM cause with the same value and with detach type set to "re-attach not required". #79 (UAS services not allowed). - A UE which is not a UE supporting UAS services receiving this cause value shall considered it as an abnormal case and the behaviour of the UE is specified in subclause 5.5.2.3.4. A UE supporting UAS service shall set the 5GS update status to 5U2 NOT UPDATED and enter state 5GMM-DEREGISTERED.NORMAL-SERVICE or 5GMM-DEREGISTERED.PLMN-SEARCH. Additionally, the UE shall reset the registration attempt counter. If the UE re-attempt the registration procedure to the current PLMN, the UE shall not include the service-level device ID set to the CAA-level UAV ID in the Service-level-AA container IE of REGISTRATION REQUEST message. If the de-registration request is for 3GPP access only or for both 3GPP access and non-3GPP access and the UE is operating in single-registration mode, the UE shall in addition set the EPS update status to EU2 NOT UPDATED, reset the attach attempt counter and enter the state EMM-DEREGISTERED. #93 (Onboarding services terminated). If the UE is not registered for onboarding services in SNPN, this cause value received from a cell belonging to an SNPN is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.2.3.4. If the UE is not operating in SNPN access operation mode, the UE shall enter the state 5GMM-DEREGISTERED.PLMN-SEARCH and perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the UE is operating in SNPN access operation mode, the UE shall enter the state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. NOTE 8: In case the configuration of one or more entries of the "list of subscriber data" was not completed at the time of network-initiated de-registration procedure, the UE can retry registration after the de-registration procedure is completed. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.2.3.2 |
5,272 | 6.15.1 Description | Energy efficiency is a critical issue in 5G. The potential to deploy systems in areas without a reliable energy source requires new methods of managing energy consumption not only in the UEs but throughout all components of the 5G system. Small form factor UEs also typically have a small battery and this not only puts constrains on general power optimization but also on how the energy is consumed. With smaller batteries it is more important to understand and follow the limitations for the both the maximum peak and continuous current drain. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.15.1 |
5,273 | 6.4.2.2 Multiple active NAS connections in the same PLMN's serving network | When the UE is registered in a serving network over two types of access (e.g. 3GPP and non-3GPP), then the UE has two active NAS connections with the same AMF. A common 5G NAS security context is created during the registration procedure over the first access type. In order to realize cryptographic separation and replay protection, the common NAS security-context shall have parameters specific to each NAS connection. The connection specific parameters include a pair of NAS COUNTs for uplink and downlink and unique NAS connection identifier. The value of the unique NAS connection identifier shall be set to "0x01" for 3GPP access and set to "0x02" for non-3GPP access. All other parameters as e.g. algorithm identifiers in the common NAS security context are common to multiple NAS connections. In non-mobility cases, when the UE is simultaneously registered over both types of accesses, and if NAS key re-keying as described in clause 6.9.4.2 or if NAS key refresh as described in clause 6.9.4.3 takes place over one of the accesses (say access A): 1) If the other access (access B) is in CM-CONNECTED state, then the new NAS security context shall only be activated over that access (access A). The UE and the AMF shall not change the NAS security context in use on the other access (say access B). In order to activate the new NAS security context over the other access (access B), the AMF shall trigger a NAS SMC run over that access either in the current running procedure or a subsequent NAS procedure. During the second NAS SMC run (on access B), the AMF shall include the same ngKSI associated with the new NAS security context and the same algorithm choices as for the first access. After a successful second NAS SMC procedure over the other access (access B), both the UE and the AMF shall delete the old NAS security context. 2) Whenever the AMF sends a NAS SMC over access (access A) and AMF considers the UE to not be in CM-CONNECTED state on the other access (access B), the AMF shall additionally activate (if not already in use on the other access) the security context that is active on the other accesses. Similarly, whenever the UE receives a NAS SMC over the access (access A) and UE is not in CM-CONNECTED state on the other access (access B), the UE additionally activates (if not already in use on the other access) the security context on the other access. In case of 3GPP access mobility or interworking with EPS, the following procedures apply: 1) If the UE is in CM-CONNECTED state on the non-3GPP access, then: a) if the AMF does not have the security context the UE is using on the non-3GPP access (e.g. KAMF change on 3GPP access when the AMF changes), then in order to activate the same NAS security context that is in use over the 3GPP access the AMF shall run a NAS SMC procedure on the non-3GPP access; or b) in the case of handover from EPS, then a mapped context will be in use on the 3GPP access and a different security context will be active on the non-3GPP access. To align the security contexts in use over both accesses, the AMF shall run a NAS SMC procedure over one access to take into use on that access the security context that is in use on the other access. In the case that a native security context is in use on the non-3GPP access, then the NAS SMC procedure shall be on the 3GPP access to take the native security context into use. 2) Whenever the AMF sends a Registration Accept over the 3GPP access and AMF considers the UE to not be in CM-CONNECTED state on the non-3GPP access, the AMF shall activate (if not already in use on the non-3GPP access) the security context that is in use on the 3GPP access on the non-3GPP access. The AMF shall keep a native security context that was in use on non-3GPP access if the security context in use on the 3GPP access is a mapped security context. In order to take this native security context into use, the AMF shall run a NAS SMC procedure. Similarly, whenever the UE receives a Registration Accept over the 3GPP access and UE is not in CM-CONNECTED state on the non-3GPP access, the UE activates (if not already in use on the non-3GPP access) the security context that is in use on the 3GPP access on the non-3GPP access. The UE shall keep a native security context that was in use on non-3GPP access if the security context in use on the 3GPP access is a mapped security context. To recover from a failure to align the NAS security contexts due to a state mis-match between AMF and UE, the AMF can align the security contexts in use on the 3GPP and non-3GPP access using the a NAS SMC procedure during a subsequent registration procedure (that was either initiated by the UE or sent in response to a Service Reject if the UE sends a Service Request). | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.4.2.2 |
5,274 | 6.1.2 TMSI reallocation procedure | The purpose of the mechanism described in this subsection is to allocate a new TMSI/LAI pair to a user by which he may subsequently be identified on the radio access link. The procedure should be performed after the initiation of ciphering. The ciphering of communication over the radio path is specified in clause 6.6. The allocation of a temporary identity is illustrated in Figure 3. Figure 3: TMSI allocation The allocation of a temporary identity is initiated by the VLR. The VLR generates a new temporary identity (TMSIn) and stores the association of TMSIn and the permanent identity IMSI in its database. The TMSI should be unpredictable. The VLR then sends the TMSIn and (if necessary) the new location area identity LAIn to the user. Upon receipt the user stores TMSIn and automatically removes the association with any previously allocatedTMSI. The user sends an acknowledgement back to the VLR. Upon receipt of the acknowledgement the VLR removes the association with the old temporary identity TMSIo and the IMSI (if there was any) from its database. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.1.2 |
5,275 | 5.2.2.5 Call accept | In the "mobile terminating call confirmed" state or the "call received" state, the call control entity in the mobile station indicates acceptance of a mobile terminating call by: - sending a CONNECT message to its peer entity in the network; - starting Timer T313; and - entering the "connect request" state. If the call control entity of the mobile station has indicated "No Bearer" as the SI value in the CALL CONFIRMED message, it shall assign the SI value and include the SI information element in the CONNECT message. Otherwise the SI information element shall not be included in the CONNECT 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 | 5.2.2.5 |
5,276 | 9.11.4.31 Received MBS container | The purpose of the Received MBS container information element is to indicate to the UE the information of the multicast MBS sessions that the network accepts or rejects the UE to join, the information of the multicast MBS sessions that the UE is removed from, or the information of the updated MBS service area. The Received MBS container information element is coded as shown in figure 9.11.4.31.1, figure 9.11.4.31.2, figure 9.11.4.31.3, figure 9.11.4.31.4, figure 9.11.4.31.5, figure 9.11.4.31.6, figure 9.11.4.31.7, figure 9.11.4.31.8, figure 9.11.4.31.9, figure 9.11.4.31.10, figure 9.11.4.31.11 and table 9.11.4.31.1. The Received MBS container is a type 6 information element with a minimum length of 9 octets and a maximum length of 65538 octets. Figure 9.11.4.31.1: Received MBS container information element Figure 9.11.4.31.2: Received MBS information Figure 9.11.4.31.3: MBS service area for MBS service area indication = "MBS service area included as MBS TAI list" Figure 9.11.4.31.4: MBS service area for MBS service area indication = "MBS service area included as NR CGI list" Figure 9.11.4.31.5: MBS service area for MBS service area indication = "MBS service area included as MBS TAI list and NR CGI list" Figure 9.11.4.31.6: NR CGI list Figure 9.11.4.31.7: NR CGI Figure 9.11.4.31.8: MBS timers for MBS timer indication = "MBS start time" Figure 9.11.4.31.9: MBS timers for MBS timer indication = "MBS back-off timer" Figure 9.11.4.31.10: MBS security container Figure 9.11.4.31.11: MBS security keys set Table 9.11.4.31.1: Received MBS container information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.4.31 |
5,277 | 5.4.4.1.3 Completion of clearing | A call control entity of the mobile station in any call control state shall, upon receipt of a RELEASE COMPLETE message from its peer entity in the network: stop all running call control timers; release the MM connection; and return to the "null" state. 5.4.4.1.3.1 Abnormal cases The call control entity of the mobile station in the "release request" state shall at first expiry of timer T308 retransmit the RELEASE message and restart timer T308. At second expiry of timer T308, the call control entity of the mobile station shall: release the MM connection; and return to the "null" state. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.4.1.3 |
5,278 | 5.4.10 GNSS validity duration reporting | For a NB-IoT UE, a BL UE or a UE in enhanced coverage in a non-terrestrial network, an indication may be sent by upper layer to report the remaining GNSS measurement validity duration. If the GNSS validity duration reporting procedure has been triggered: - if the MAC entity has UL resources allocated for new transmission for this TTI, and; - if the allocated UL resources can accommodate the GNSS Validity Duration Report MAC control element plus its subheader, as a result of logical channel prioritization: - instruct the Multiplexing and Assembly procedure to generate the GNSS Validity Duration Report MAC control element as defined in clause 6.1.3.23. - else: - initiate a Random Access procedure (see clause 5.1). | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.4.10 |
5,279 | 10.5.5.3a Integrity algorithm | The purpose of the integrity algorithm information element is to specify which integrity algorithm shall be used. The integrity algorithm is a type 1 information element. The integrity algorithm information element is coded as shown in figure 10.5.5.3a-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.5.3a-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.5.3a-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Integrity algorithm information element Table 10.5.5.3a-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Integrity algorithm information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.5.3a |
5,280 | 5.4.3.3 NAS security mode command accepted by the UE | Upon receipt of the SECURITY MODE COMMAND message, the UE shall check whether the security mode command can be accepted or not. This is done by performing the integrity check of the message and by checking that the received replayed UE security capabilities, the received replayed UE additional security capabilities, if included in the SECURITY MODE COMMAND message, and the received nonceUE have not been altered compared to the latest values that the UE sent to the network. However, the UE is not required to perform the checking of the received nonceUE if the UE does not want to re-generate the K'ASME (i.e. the SECURITY MODE COMMAND message is to derive and take into use a mapped EPS security context and the eKSI matches the current EPS security context, if it is a mapped EPS security context). When the UE has a PDN connection for emergency bearer services established or the UE is establishing a PDN connection for emergency bearer services or the UE is requesting attach for access to RLOS, the UE is not required to locally re-generate the KASME (i.e. the SECURITY MODE COMMAND message is used to derive and take into use a native EPS security context where the KSI value "000" is included in the NAS key set identifier IE and the EIA0 and EEA0 are included as the selected NAS security algorithms). The UE shall accept a SECURITY MODE COMMAND message indicating the "null integrity protection algorithm" EIA0 as the selected NAS integrity algorithm only if the message is received for a UE that has a PDN connection for emergency bearer services established, or a UE that is attached for access to RLOS, or a UE that is establishing a PDN connection for emergency bearer services or a UE that is requesting attach for access to RLOS. If the type of security context flag included in the SECURITY MODE COMMAND message is set to "native security context" and if the KSI matches a valid non-current native EPS security context held in the UE while the UE has a mapped EPS security context as the current EPS security context, the UE shall take the non-current native EPS security context into use which then becomes the current native EPS security context and delete the mapped EPS security context. If the SECURITY MODE COMMAND message can be accepted, the UE shall take the EPS security context indicated in the message into use. The UE shall in addition reset the uplink NAS COUNT counter if: - the SECURITY MODE COMMAND message is received in order to take an EPS security context into use created after a successful execution of the EPS authentication procedure; - the SECURITY MODE COMMAND message received includes the type of security context flag set to "mapped security context" in the NAS key set identifier IE the eKSI does not match the current EPS security context, if it is a mapped EPS security context. If the SECURITY MODE COMMAND message can be accepted and a new EPS security context is taken into use and SECURITY MODE COMMAND message does not indicate the "null integrity protection algorithm" EIA0 as the selected NAS integrity algorithm, the UE shall: - if the SECURITY MODE COMMAND message has been successfully integrity checked using an estimated downlink NAS COUNT equal 0, then the UE shall set the downlink NAS COUNT of this new EPS security context to 0; - otherwise the UE shall set the downlink NAS COUNT of this new EPS security context to the downlink NAS COUNT that has been used for the successful integrity checking of the SECURITY MODE COMMAND message. If the SECURITY MODE COMMAND message can be accepted, the UE shall send a SECURITY MODE COMPLETE message integrity protected with the selected NAS integrity algorithm and the EPS NAS integrity key based on the KASME or mapped K'ASME if the type of security context flag is set to "mapped security context" indicated by the eKSI. When the SECURITY MODE COMMAND message includes the type of security context flag set to "mapped security context" in the NAS key set identifier IE, the nonceMME and the nonceUE, then the UE shall either: - generate K'ASME from both the nonceMME and the nonceUE as indicated in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19]; or - check whether the SECURITY MODE COMMAND message indicates the eKSI of the current EPS security context, if it is a mapped EPS security context, in order not to re-generate the K'ASME. Furthermore, if the SECURITY MODE COMMAND message can be accepted, the UE shall cipher the SECURITY MODE COMPLETE message with the selected NAS ciphering algorithm and the EPS NAS ciphering key based on the KASME or mapped K'ASME indicated by the eKSI. The UE shall set the security header type of the message to "integrity protected and ciphered with new EPS security context". From this time onward the UE shall cipher and integrity protect all NAS signalling messages with the selected NAS ciphering and NAS integrity algorithms. If the MME indicated in the SECURITY MODE COMMAND message that the IMEISV is requested, the UE shall include its IMEISV in the SECURITY MODE COMPLETE message. In WB-S1 mode, if the MME indicated in the SECURITY MODE COMMAND message that the UE radio capability ID is requested, the UE shall: - if the UE has an applicable network-assigned UE radio capability ID for the current UE radio configuration in the selected PLMN, include the applicable network-assigned UE radio capability ID in the UE radio capability ID IE of the SECURITY MODE COMPLETE message; and - if the UE: a) does not have an applicable network-assigned UE radio capability ID for the current UE radio configuration in the selected PLMN; and b) has an applicable manufacturer-assigned UE radio capability ID for the current UE radio configuration, include the applicable manufacturer-assigned UE radio capability ID in the UE radio capability ID IE of the SECURITY MODE COMPLETE message. If, during an ongoing attach or tracking area updating procedure, the SECURITY MODE COMMAND message includes a HASHMME, the UE shall compare HASHMME with a hash value locally calculated as described in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19] from the entire plain ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message that the UE had sent to initiate the procedure. If HASHMME and the locally calculated hash value are different, the UE shall include the complete ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message which the UE had previously sent in the Replayed NAS message container IE of the SECURITY MODE COMPLETE message. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.3.3 |
5,281 | 5.2.27.2.2 Ntsctsf_TimeSynchronization_ConfigCreate operation | Service operation name: Ntsctsf_TimeSynchronization_ConfigCreate Description: Authorize the request, create a time synchronization configuration and activate the time synchronization service with the configuration. Inputs, Required: Reference to time synchronization capability set (i.e. the Subscription Correlation ID as in the response to Ntsctsf_TimeSynchronization_CapsSubscribe request), user plane node ID, mandatory service parameters as described in Table 4.15.9.3-1, Notification Target Address. Inputs, Optional: Optional service parameters as described in Table 4.15.9.3-1. Outputs, Required: Operation execution result indication, in successful operation the PTP instance reference. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.27.2.2 |
5,282 | – PDCCH-ServingCellConfig | The IE PDCCH-ServingCellConfig is used to configure UE specific PDCCH parameters applicable across all bandwidth parts of a serving cell. PDCCH-ServingCellConfig information element -- ASN1START -- TAG-PDCCH-SERVINGCELLCONFIG-START PDCCH-ServingCellConfig ::= SEQUENCE { slotFormatIndicator SetupRelease { SlotFormatIndicator } OPTIONAL, -- Need M ..., [[ availabilityIndicator-r16 SetupRelease {AvailabilityIndicator-r16} OPTIONAL, -- Need M searchSpaceSwitchTimer-r16 INTEGER (1..80) OPTIONAL -- Need R ]], [[ searchSpaceSwitchTimer-v1710 INTEGER (81..1280) OPTIONAL -- Need R ]] } -- TAG-PDCCH-SERVINGCELLCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,283 | 6.21.1 Description | The increased density of access nodes needed to meet future performance objectives poses considerable challenges in deployment and acquiring spectrum and antenna locations. RAN sharing is seen as a technical solution to these issues. In RAN Sharing operations, NG-RAN resources can be used by multiple network operators. Indirect Network Sharingis one of the possible sharing methods. During NG-RAN sharing, the security and privacy of shared networks, non-shared networks, and subscribers need to be maintained without negative effects. Especially in the case of Indirect Network Sharing, where the involvement of the core network of the hosting operator e.g. for signalling exchange between the users and the core network of the participating operator could cause exposure of the subscriber’s information to the hosting network, an extra scrutiny of the security mechanism is expected to avoid sharing the information that is not needed for the Indirect Network Sharing operation (e.g. network topology) and protect the information that is needed for the Indirect Network Sharing operation between the hosting operator and the participating operator. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.21.1 |
5,284 | Modify Bearer Request | The direction of this message shall be from MME/S4-SGSN to SGW and/or from SGW to PGW (see Table 6.1-1). The Modify Bearer Request message shall only be sent on the S11 interface by the MME to the SGW and on the S5/S8 interfaces by the SGW to the PGW as part of the procedures: - E-UTRAN Tracking Area Update without SGW Change - UE triggered Service Request - S1-based Handover - UTRAN Iu mode to E-UTRAN Inter RAT handover - GERAN A/Gb mode to E-UTRAN Inter RAT handover - Tracking Area Update procedure with a RAT type change - E-UTRAN Initial Attach - Handover from Trusted or Untrusted Non-3GPP IP Access to E-UTRAN with GTP on S5/S8 interface (see clauses 8.2, 8.6 and 16.11 of 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [45]) - UE requested PDN connectivity - SGSN to MME combined hard handover and SRNS relocation procedure - X2-based handover without SGW relocation - UTRAN/GERAN to E-UTRAN SRVCC - HSS-based P-CSCF restoration for 3GPP access (see 3GPP TS 23.380[ IMS Restoration Procedures ] [61]) - Connection Resume procedure (see clause 5.3.5A of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3]) - reception of the RRC establishment cause "MO Exception data" in the NB-IoT RAT It shall also only be sent on the S11 interface by the MME to the SGW as part of the procedure: - E-UTRAN Initiated E-RAB modification procedure - Handover from Trusted or Untrusted Non-3GPP IP Access to E-UTRAN with PMIP on S5/S8 interface (see clauses 8.2 and 16.11 of 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [45]) - Tracking Area Update procedure with Serving GW change and data forwarding - Mobile Originated Data transport in Control Plane CIoT EPS optimisation with P-GW connectivity - Mobile Terminated Data Transport in Control Plane CIoT EPS optimisation with P-GW connectivity - Establishment of S1-U bearer during Data Transport in Control Plane CIoT EPS optimisation procedure (see clause 5.3.4B.4 of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3]). It shall also only be sent on the S4 interface by the SGSN to the SGW and on the S5/S8 interfaces by the SGW to the PGW as part of the procedures: - Routeing Area Update with MME interaction and without SGW change - E-UTRAN to UTRAN Iu mode Inter RAT handover - E-UTRAN to GERAN A/Gb mode Inter RAT handover - Inter SGSN Routeing Area Update Procedure and Combined Inter SGSN RA / LA Update to S4 SGSNs without SGW change - Iu mode RA Update Procedure without SGW change - Serving RNS Relocation Procedure - Combined Hard Handover and SRNS Relocation Procedure - Combined Cell / URA Update and SRNS Relocation Procedure - Enhanced Serving RNS Relocation without SGW relocation - UE Initiated Service Request Procedure - Iu mode to A/Gb mode Intra SGSN Change - A/Gb mode to Iu mode Intra SGSN Change - Iu mode to A/Gb mode Inter-SGSN Change - A/Gb mode to Iu mode Inter-SGSN Change - Paging Response with no established user plane on S4 - PDP Context Activation Procedure - Handover from Trusted or Untrusted Non-3GPP IP Access to UTRAN/GERAN with GTP on S5/S8 interface (see clauses 8.2, 8.6 and 16.11 of 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [45]) - UTRAN/GERAN to UTRAN (HSPA) SRVCC - HSS-based P-CSCF restoration for 3GPP access (see 3GPP TS 23.380[ IMS Restoration Procedures ] [61]) It shall also only be sent on the S4 interface by the SGSN to the SGW as part of the procedures: - RAB Assignment Procedure - SRVCC from E-UTRAN to UTRAN or GERAN with DTM HO support procedures and SRVCC from UTRAN (HSPA) to UTRAN or GERAN with DTM HO support. - Handover from Trusted or Untrusted Non-3GPP IP Access to UTRAN/GERAN with PMIP on S5/S8 interface (see clauses 8.2 and 16.11 of 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [45]) - Routeing Area Update procedure with Serving GW change and data forwarding and only on the S5/S8 interfaces by the SGW to the PGW as part of the procedures: - Tracking Area Update procedure with SGW change - Gn/Gp SGSN to S4 SGSN Routing Area Update - X2 based handover with SGW relocation - Gn/Gp SGSN to MME Tracking Area Update - Enhanced Serving RNS Relocation with SGW relocation - Routeing Area Update with MME interaction and with SGW change - Inter SGSN Routeing Area Update Procedure and Combined Inter SGSN RA / LA Update using S4 with SGW change - Iu mode RA Update Procedure using S4 with SGW change - Restoration of PDN connections after an SGW failure if the MME/SGSN and PGW support these procedures as specified in 3GPP TS 23.007[ Restoration procedures ] [17] - MME triggered Serving GW relocation - S4-SGSN triggered Serving GW relocation - PGW Pause of Charging procedure and on the S2b interface by the ePDG to the PGW as part of the procedures: - UE initiated IPsec tunnel update procedure If the optional network triggered service restoration feature is supported by the MME, SGSN and SGW, then the Modify Bearer Request message shall also be sent as part of the network triggered service restoration procedure with ISR during an intra MME TAU and an intra S4-SGSN RAU procedure for UEs that had ISR active before either the MME or the S4-SGSN has restarted, as specified in 3GPP TS 23.007[ Restoration procedures ] [17]: - on the S11 interface by the MME to the SGW, if the MME detected that the ISR associated S4-SGSN has restarted and UE performs a TAU procedure; - on the S4 interface by the S4-SGSN to the SGW, if the S4-SGSN detected that the ISR associated MME has restarted and UE performs a RAU procedure. This message can be used as an implicit resume of the suspended bearers in the SGW and in the PGW (see 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [43] clauses 6.2.2.1 and 6.3.2.1, 3GPP TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [21] clauses 6.3, 6.5 and 7.4). A Modify Bearer Request used as an implicit resume can contain zero or more IE(s), depending on the conditions of presence of the IEs specified in table 7.2.7-1. The PGW should not consider a Modify Bearer Request with zero IE as an error. The Modify Bearer Request message may also be sent in the following cases from the S4-SGSN to the SGW/PGW to report a change of Serving Network, User CSG Information or/and UE Time Zone which occured during a previous RAU procedure without SGSN change but which has not been reported yet to the SGW/PGW, or to indicate to the PGW that the UE is available for signalling if the PDN connection is delay tolerant and if there is pending network initiated PDN connection signalling: - during a Service Request procedure to establish data radio bearers for the corresponding PDP context for a UE in UTRAN with an existing S4-U tunnel; - when the SGSN receives an uplink LLC PDU for user data or any valid LLC frame serving as a paging response from a UE in GERAN with an existing S4-U tunnel. The Modify Bearer Request message may also be sent in the following cases from the S4-SGSN to the SGW/PGW to report a change of User Location Information which occured during a previous RAU procedure without SGSN change but which has not been reported yet to the SGW/PGW, if the S4-SGSN is configured to defer the reporting of ULI change until a RAB/user plane is established: - during a Service Request procedure to establish data radio bearers for the corresponding PDP context for a UE in UTRAN with an existing S4-U tunnel; - when the SGSN receives an uplink LLC PDU for user data or any valid LLC frame serving as a paging response for a UE in GERAN with an existing S4-U tunnel. NOTE 1: the S4-SGSN can alternatively send a Change Notification Request message in the above cases, if no other information which requires the sending of a Modify Bearer Request, needs to be reported to the PGW. The Modify Bearer Request message may also be sent by the MME to the SGW/PGW to report a change of Serving Network, User Location Information, User CSG Information, UE Time Zone or/and RAT Type, when user data is transported in NAS signalling, for a UE with an existing S11-U tunnel. When requesting the PGW to pause or unpause charging for a PDN connection, the SGW shall wait for the PGW acknowledgement (i.e. Modify Bearer Response) before sending a new pause or unpause request. NOTE 2: this ensures that the PGW always act per the most recent SGW request in particular in scenarios where the SGW would need to request the PGW to pause and unpause charging in a row (or vice-versa) and the Modify Bearer Request messages would arrive out of order at the PGW. Upon receipt of a request from the PGW/PCRF/OCS in a message other than Create Bearer Request and Update Bearer Request to report changes of UE presence in new or modified Presence Reporting Area(s), the MME/S4-SGSN shall immediately send a Modify Bearer Request message or a Change Notification Request message to report to the PGW whether the UE is inside or outside the new or modified Presence Reporting Area(s) or whether the Presence Reporting Area(s) is inactive. The MME/S4-SGSN shall also send a Modify Bearer Request message or a Change Notification Request message to report any subsequent change of UE presence in the Presence Reporting Area, as specified in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3] and 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [35]. If the Modify Bearer Request message is sent from the old MME/SGSN as part of Tracking/Routeing Area Update procedure with SGW change and data forwarding as specified in clause 5.3.3.1A of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3], the old MME/SGSN shall only include the Bearer Contexts to be modified IE. NOTE 3: Since the UE has left the old MME/SGSN, some information related to the UE, e.g. ULI, UE Time Zone, CSG, RAT Type in the old MME/SGSN are not valid any more. Upon receipt of a Modify Bearer Request message that includes the Presence Reporting Area Information from the MME/S4-SGSN, the SGW shall send a Modify Bearer Request message on the S5/S8 interface if any of the following condition is met: - ISR is not active; - ISR is active, and the RAT Type has changed since last reported or the CPRAI flag has been set to 1. The MME shall increment the "MO Exception data counter" by one each time the MME has received the RRC cause "MO Exception data". The MME may defer sending a Modify Bearer Request message to report a non-zero value for the MO Exception Data Counter based on local configuration. Upon receipt of a Modify Bearer Request message that includes the Secondary RAT Usage Data Report from the MME, the SGW shall send a Modify Bearer Request message on the S5/S8 interface if the IRPGW flag is set to 1 in the Secondary RAT Usage Data Report IE. Table -1: Information Elements in a Modify Bearer Request Table -2: Bearer Context to be modified within Modify Bearer Request Table -3: Bearer Context to be removed within Modify Bearer Request Table 7.2.7-4: Overload Control Information within Modify Bearer Request | 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,285 | 4.7.5.2.4 Combined routing area updating not accepted by the network | If the combined routing area updating cannot be accepted, the network sends a ROUTING AREA UPDATE REJECT message to the MS. An MS that receives a ROUTING AREA UPDATE REJECT message containing a reject cause other than GMM cause value #25 or the message is integrity protected, shall stop the timer T3330, and shall enter the state MM IDLE. If a ROUTING AREA UPDATE REJECT message containing a reject cause other than GMM cause value #25 is received or the message is integrity protected, the MS shall stop any ongoing transmission of user data. If the ROUTING AREA UPDATE REJECT message containing GMM cause value #25 was received without integrity protection, then the MS shall discard the message. If the routing area update request 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. The MS shall then take different actions depending on the received reject cause: # 3 (Illegal MS); # 6 (Illegal ME), or # 8 (GPRS services and non GPRS services not allowed); The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED and the update status to U3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and shall delete any P-TMSI, P-TMSI signature, TMSI, RAI, LAI, ciphering key sequence number and GPRS ciphering key sequence number. The MS shall consider the SIM/USIM as invalid for GPRS and 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. The MS shall delete the list of equivalent PLMNs, and shall enter the state GMM-DEREGISTERED.NO-IMSI. 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 1: Optionally the MS starts the timer T3340 as described in subclause 4.7.1.9 for reject cause #8. 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 combined tracking area update 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) 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 MS shall enter the state 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 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 combined tracking area update 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. A GPRS MS operating in MS operation mode A or B in network operation mode I which is already IMSI attached for CS services in the network, is still IMSI attached for CS services in the network. If the rejected request was not for initiating a PDN connection for emergency bearer services, then - a GPRS MS operating in MS operation mode A or B shall 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 - 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 combined tracking area update procedure is rejected with the EMM cause with the same value. # 10 (Implicitly detached); A GPRS MS operating in MS operation mode A or B in network operation mode I, is IMSI detached for both GPRS and CS services in the network. The MS shall enter the 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 combined tracking area update 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/MBMS context(s) automatically. # 11 (PLMN not allowed); The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED and the update status to U3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and enter the state GMM-DEREGISTERED. Furthermore, the MS shall delete any P-TMSI, P-TMSI signature, TMSI, RAI, LAI, ciphering key sequence number GPRS ciphering key sequence number, shall delete the list of equivalent PLMNs, and shall reset the routing area updating attempt counter and the location update attempt counter. 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. The MS shall then 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, KSI and tracking area updating attempt counter 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 combined tracking area update 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), shall reset the routing area updating attempt counter and shall change to state GMM-DEREGISTERED.LIMITED-SERVICE. The MS shall in addition 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 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. 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, KSI and tracking area updating attempt counter 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 combined tracking area update 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 clause 4.1.3.2), and shall delete the list of equivalent PLMNs. The MS shall reset the routing area updating attempt counter, and shall enter the state GMM-REGISTERED.LIMITED-SERVICE. The MS shall in addition 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 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. 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]. The MS shall indicate the Update type IE "combined RA/LA updating with IMSI attach" when performing the routing area updating procedure following the PLMN selection. 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 and tracking area updating attempt counter 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 combined tracking area update procedure is rejected with the EMM cause with the same value. # 14 (GPRS services not allowed in this PLMN); The MS shall delete any RAI, P-TMSI, P-TMSI signature, and GPRS ciphering key sequence number stored, shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2), shall reset the routing area updating attempt counter and shall change to state GMM-DEREGISTERED. The MS shall store the PLMN identity in the "forbidden PLMNs for GPRS service" 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 subclause 4.1.1.6. If the message has been successfully integrity checked by the lower layers and the MS maintains a PLMN-specific PS-attempt counter for that PLMN, then the MS shall set this counter to the 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. As an implementation option, a GPRS MS operating in operation mode A or B may perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. If an MS in GAN mode performs a PLMN selection, it 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]. The MS shall not perform the optional PLMN selection in the case where the PLMN providing this reject cause is: - On the "User Controlled PLMN Selector with Access Technology " or, - On the "Operator Controlled PLMN Selector with Access Technology " list or, - A PLMN identified as equivalent to any PLMN, within the same country, contained in the lists above. 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, KSI and tracking area updating attempt counter 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 combined tracking area update 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 clause 4.1.3.2), shall reset the routing area updating attempt counter and shall change to state GMM-REGISTERED.LIMITED-SERVICE. The MS shall in addition 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 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. The MS shall search for a suitable cell in another location area according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98]. NOTE 5: The cell selection procedure is not applicable for an MS in GAN mode. The MS shall indicate the Update type IE "combined RA/LA updating with IMSI attach" when performing the routing area updating procedure. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status and tracking area updating attempt counter 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 combined tracking area update procedure is rejected with the EMM cause with the same value. #22 (Congestion); If the T3346 value IE is present in the ROUTING AREA UPDATE 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.5.2.5. The MS shall abort the routing area updating procedure, reset the routing area updating attempt counter and set the GPRS update status to GU2 NOT UPDATED. If the rejected request was not for initiating a PDN connection for emergency bearer services, the MS shall change to state GMM-REGISTERED.ATTEMPTING-TO-UPDATE. The MS shall stop timer T3346 if it is running. If the ROUTING AREA UPDATE REJECT message is integrity protected, the MS shall start timer with the value provided in the T3346 value IE. If the ROUTING AREA UPDATE REJECT message is not integrity protected, the ME 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 the normal cell reselection process. The routing area updating procedure is started, if still necessary, when timer T3346 expires or is stopped. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, and tracking area updating attempt counter 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 tracking area update 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.5.2.5. The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and store it according to subclause 4.1.3.2) and shall reset the routing area updating attempt counter. The state is changed to GMM-REGISTERED.LIMITED-SERVICE. If the CSG ID and associated PLMN identity of the cell where the MS has sent the ROUTING AREA UPDATE 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 ROUTING AREA UPDATE 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, 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, EPS update status and tracking area updating attempt counter 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 combined tracking area update procedure is rejected with the EMM cause with the same value. Other values are considered as abnormal cases. The specification of the MS behaviour in those cases is described in subclause 4.7.5.2.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.5.2.4 |
5,286 | 6.5.4.3 UE requested bearer resource modification procedure accepted by the network | Upon receipt of the BEARER RESOURCE MODIFICATION REQUEST message, the MME checks whether the resources requested by the UE can be established, modified or released by verifying the EPS bearer identity given in the EPS bearer identity for packet filter IE. If the bearer resource modification requested is accepted by the network, the MME shall initiate either a dedicated EPS bearer context activation procedure, an EPS bearer context modification procedure or an EPS bearer context deactivation procedure. If the request to re-negotiate header compression configuration associated to an EPS bearer context is accepted by the network, the MME shall initiate an EPS bearer context modification procedure. If the bearer resource modification requests a release of bearer resources that results in the TFT of the EPS bearer context containing only packet filters applicable to the uplink direction, the network may initiate the EPS bearer context deactivation procedure. Upon receipt of an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST, MODIFY EPS BEARER CONTEXT REQUEST or DEACTIVATE EPS BEARER CONTEXT REQUEST message with a PTI which matches the value used for the BEARER RESOURCE MODIFICATION REQUEST message, the UE shall stop timer T3481 and enter the state PROCEDURE TRANSACTION INACTIVE. The UE should ensure that the procedure transaction identity (PTI) assigned to this procedure is not released immediately. The way to achieve this is implementation dependent. While the PTI value is not released, the UE regards any received ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST or MODIFY EPS BEARER CONTEXT REQUEST or DEACTIVATE EPS BEARER CONTEXT REQUEST message with the same PTI value as a network retransmission (see clause 7.3.1). i) If the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message is received, the UE shall verify that the EPS bearer identity given in the EPS bearer identity IE is not already used by any EPS bearer context. The UE shall then proceed as described in clause 6.4.2.3 or clause 6.4.2.4. ii) If the MODIFY EPS BEARER CONTEXT REQUEST message is received, the UE verifies that the EPS bearer identity given in the EPS bearer identity IE is any of the active EPS bearer contexts. The UE shall then proceed as described in clause 6.4.3.3 or clause 6.4.3.4. iii) If the DEACTIVATE EPS BEARER CONTEXT REQUEST message is received, the UE verifies that the EPS bearer identity given in the EPS bearer identity IE is one of the active EPS bearer contexts. The UE shall then proceed as described in clause 6.4.4.3. In case i, after successful completion of the dedicated EPS bearer context activation procedure, the network may initiate an EPS bearer context modification procedure to delete the packet filters which have packet filter identifiers indicated by the UE in the Traffic flow aggregate IE in the BEARER RESOURCE MODIFICATION REQUEST message and for which the network created new packet filters during the dedicated EPS bearer context activation procedure. In this case the MME shall set the procedure transaction identity value in the MODIFY EPS BEARER CONTEXT REQUEST message to "no procedure transaction identity assigned". | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.5.4.3 |
5,287 | 9.11.3.43 PDU session reactivation result error cause | The purpose of the PDU session reactivation result error cause information element is to indicate error causes for PDU session ID(s) where there was a failure to establish the user-plane resources. The PDU session reactivation result error cause information element is coded as shown in figure 9.11.3.43.1 and table 9.11.3.43.1. The PDU session reactivation result error cause is a type 6 information element with a minimum length of 5 octets and a maximum length of 515 octets. Figure 9.11.3.43.1: PDU session reactivation result error cause information element Table 9.11.3.43.1: PDU session reactivation result error cause information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.3.43 |
5,288 | 8.11.3 RRC Connection Reestablishment – separate PLMN signalling | The signalling flow for RRC Connection Reestablishment for network sharing with multiple cell-ID broadcast with separate per-PLMN signalling is shown in Figure 8.11.3-1. In this example message flow - each F1-C/Xn-C interface instance uses either a separate signalling transport or a share signalling transport with other interface instances. - the New gNB-DUA/B entity shown in Figure 8.11.3-1 is a simplified representation of the New gNB-DUA of PLMN A, the New gNB DUB of PLMN B and respective radio resources of the shared cell. Figure 8.11.3-1: RRC Connection Reestablishment and network sharing with multiple cell-ID broadcast 1. The UE sends the RRCReestablishmentRequest. 2A-5A. Depicts the case where the UE context could not be retrieved by the new gNB-CUA. In step 2A, the NR CGI associated to PLMNA is indicated. In step 5A, the gNB-CUA would prepare the possibility to revert back to normal RRC Connection Establishment, indicating that the UE Context was not retrieveable and may include the re-directed RRC message as received in step 1. After step 5A, the gNB-DUA may redirect the UE towards the PLMN indicated in DL RRC MESSAGE TRANSFER message, if the PLMN assistance information is provided by the gNB-CUA. If the New gNB-DUA/B was not able to deduce the RRC message from step 1, this indicator triggers step 2B. The New gNB-DUA is supposed to trigger the release the UE-associated signalling connection (not shown). 2B-5B. Depicts the case where the UE context was retrieveable by the New gNB-CUB. In step 2B, the NR CGI associated to PLMNB is indicated. Step 2B also includes the C-RNTI allocated at reception of step 1. 6-8. The RRC Connection Reestablishment continues with the New gNB-CUB. NOTE: If all gNB-CUs indicate that the UE context is not retrievable, the RRC connection reestablishment falls back to RRC Connection setup, as described in clause 8.11.2. NOTE: Initiating procedures from gNB-DUA towards gNB-CUA and from gNB-DUB to gNB-CUB in parallel is not precluded. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.11.3 |
5,289 | 9.2.6.1 Frame structure type 3 with FDD Pcell | The following requirements apply to UE Category ≥1. For the parameters specified in Table 9.2.6.1-1, Table 9.2.6.1-2, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2, two sets of CQI reports are obtained for LAA Scell. The first one is obtained by reports whose reference resource is in the downlink subframes with 6 dB transmission power boost, i.e., high power subframes. The second one is obtained by reports whose reference resource is in the downlink subframe with 0 dB transmission power boost, i.e., low power subframe. In the test, PDSCH transport format in high power subframe is determined by first set of CQI reports and PDSCH transport format in low power subframe is determined by second set of CQI reports. The reported CQI value in the first set of reports shall be in the range of ±1 of the reported median more than 90% of the first set of reports. The reported CQI value in the second set of reports shall be in the range of ±1 of the reported median more than 90% of the second set of reports. If the PDSCH BLER in the high power subframes using the transport format indicated by wideband CQI median is less than or equal to 0.1, the BLER in high power subframes using the transport format indicated by the (wideband CQI median + 1) shall be greater than 0.1. If the PDSCH BLER in the high power subframes using the transport format indicated by the wideband CQI median is greater than 0.1, the BLER in high power subframes using transport format indicated by (wideband CQI median – 1) shall be less than or equal to 0.1. If the PDSCH BLER in the low power subframes using the transport format indicated by wideband CQI median is less than or equal to 0.1, the BLER in low power subframes using the transport format indicated by the (wideband CQI median + 1) shall be greater than 0.1. If the PDSCH BLER in the low power subframes using the transport format indicated by the wideband CQI median is greater than 0.1, the BLER in low power subframes using transport format indicated by (wideband CQI median – 1) shall be less than or equal to 0.1. The value of the wideband CQI median for first set of CQI reports minus the wideband CQI median for second set of CQI reports shall be larger than or equal to 2 in Test 1 and Test 2. Table 9.2.6.1-1: Parameters for PUSCH 3-0 static test on FDD Pcell Table 9.2.6.1-2: PUSCH 3-0 static test on LAA Scell | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.2.6.1 |
5,290 | – NPN-IdentityInfoList | The IE NPN-IdentityInfoList includes a list of NPN identity information. NPN-IdentityInfoList information element -- ASN1START -- TAG-NPN-IDENTITYINFOLIST-START NPN-IdentityInfoList-r16 ::= SEQUENCE (SIZE (1..maxNPN-r16)) OF NPN-IdentityInfo-r16 NPN-IdentityInfo-r16 ::= SEQUENCE { npn-IdentityList-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF NPN-Identity-r16, trackingAreaCode-r16 TrackingAreaCode, ranac-r16 RAN-AreaCode OPTIONAL, -- Need R cellIdentity-r16 CellIdentity, cellReservedForOperatorUse-r16 ENUMERATED {reserved, notReserved}, iab-Support-r16 ENUMERATED {true} OPTIONAL, -- Need S ..., [[ gNB-ID-Length-r17 INTEGER (22..32) OPTIONAL -- Need R ]], [[ mobileIAB-Support-r18 ENUMERATED {true} OPTIONAL -- Need S ]] } -- TAG-NPN-IDENTITYINFOLIST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,291 | 6.3.6 N3IWF selection 6.3.6.1 General | When the UE supports connectivity with N3IWF but does not support connectivity with ePDG, as specified in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [43], the UE shall perform the procedure in clause 6.3.6.2 for selecting an N3IWF. When the UE supports connectivity with N3IWF, as well as with ePDG, as specified in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [43], the UE shall perform the procedure in clause 6.3.6.3 for selecting either an N3IWF or an ePDG, i.e. for selecting a non-3GPP access node. In both cases above the UE can be configured by the HPLMN with the same information that includes: 1) ePDG identifier configuration: It contains the FQDN or IP address of the ePDG in the HPLMN, as specified in clause 4.5.4.3 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [43]. This is used only when the UE supports connectivity with ePDG and attempts to select an ePDG. It is ignored in all other cases. 2) N3IWF identifier configuration: It contains the FQDN or IP address of the N3IWF in the HPLMN. 3) Extended Home N3IWF identifier configuration: It contains one or multiple tuples of FQDN/IP address of the N3IWF in the HPLMN and the S-NSSAIs supported by this N3IWF. 4) Non-3GPP access node selection information: It contains a prioritized list of PLMNs and for each PLMN it includes (i) a "Preference" parameter which indicates if ePDG or N3IWF is preferred in this PLMN and (ii) an FQDN parameter which indicates if the Tracking/Location Area Identity FQDN or the Operator Identifier FQDN (as specified in clause 4.5.4.4 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [43]) should be used when discovering the address of an ePDG or N3IWF in this PLMN. The list of PLMNs shall include the HPLMN and shall include an "any PLMN" entry, which matches any PLMN the UE is connected to except the HPLMN. 5) Slice-specific N3IWF prefix configuration: It contains one or multiple tuples consisting of: - List of supported S-NSSAIs; - Prefix for the Prefixed N3IWF OI or TA FQDNs. NOTE 1: Extended Home N3IWF identifier configuration and Slice-specific N3IWF prefix configuration are assumed to be provided to the UE as part of ANDSP. The ePDG identifier configuration, the N3IWF identifier configuration, the Extended Home N3IWF identifier configuration and the Slice-specific N3IWF Prefix Configuration are optional parameters, while the Non-3GPP access node selection information is required and shall include at least the HPLMN and the "any PLMN" entry. If the ePDG identifier configuration is configured in the UE, then, when the UE decides to select an ePDG in the HPLMN (according to the procedure in clause 6.3.6.3), the UE shall use the ePDG identifier configuration to find the IP address of the ePDG in the HPLMN and shall ignore the FQDN parameter of the HPLMN in the Non-3GPP access node selection information. If the N3IWF identifier configuration or the Extended Home N3IWF identifier configuration is configured in the UE, then, when the UE decides to select an N3IWF in the HPLMN (according to the procedure in clause 6.3.6.3 for combined N3IWF/ePDG selection and the procedure in clause 6.3.6.2 for Stand-alone N3IWF selection), the UE shall use the Extended Home N3IWF identifier configuration, if available, and otherwise the N3IWF identifier configuration to find the IP address of the N3IWF in the HPLMN and shall ignore the FQDN parameter of the HPLMN in the Non-3GPP access node selection information. The HPLMN's PCF takes the UE's subscribed S-NSSAIs into account when providing Extended Home N3IWF identifier configuration and/or Slice-specific N3IWF Prefix Configuration to the UE. If a UE does not support the Extended Home N3IWF identifier configuration and the Slice-specific N3IWF Prefix Configuration, then the HPLMN provides to the UE the Non-3GPP access node selection information and the N3IWF identifier configuration by taking into account the UE's subscribed S-NSSAIs. NOTE 2: If the HPLMN deploys multiple N3IWFs with different TAs which support different S-NSSAIs, then the HPLMN can configure a UE with N3IWF identifier configuration so that the UE selects an N3IWF that supports the UE's subscribed S-NSSAIs. The UE can be configured by the VPLMN with the following information applicable for the V-PLMN: Slice-specific N3IWF prefix configuration: It contains one or multiple tuples consisting of: - List of supported S-NSSAIs; - Prefix for the Prefixed N3IWF OI or TA FQDNs. To enable the V-PCF to provide the UE with Slice-specific N3IWF prefix configuration, the AMF provides the V-PCF with the Configured NSSAI for the serving PLMN during the UE Policy Association Establishment/Modification procedure. NOTE 3: In non-roaming cases, the UE PCF already receives the subscribed NSSAI from the UDR. Therefore, there is no need for the AMF to provide the Configured NSSAI to the PCF in the non-roaming case. NOTE 4: PCF (V-PCF in the roaming case) is assumed to be locally configured with information about the slices supported by the different N3IWFs in the serving PLMN. During the registration procedure the AMF may determine if the N3IWF selected by the UE is suitable for the S-NSSAI(s) requested by the UE considering the UE subscription. If the AMF determines that a different N3IWF should be selected as described in clause 4.12.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], the AMF: - may, if the UE supports slice-based N3IWF selection, triggers the UE Policy Association Establishment or UE Policy Association Update procedure to provide the UE with updated N3IWF selection information as described in clause 6.15.2.1; when the AMF is informed by the PCF that the update of UE policy information on the UE is completed as described in clause 4.12.2.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], the AMF releases UE Policy Association if the UE is not registered over 3GPP access before proceeding to the Registration Reject over untrusted non-3GPP access; - shall send a Registration Reject message to the UE. The AMF may include target N3IWF information (FQDN and/or IP address) in the Registration Reject so that the UE can, if supported by the UE, use the target N3IWF information to select the N3IWF to register to 5GC if the UE wishes to send the same Requested NSSAI as during the previous Registration Request. The target N3IWF information only applies to the one N3IWF selection performed by the UE just after receiving the Registration Reject. The AMF may determine the N3IWF based on the list of supported TAs and the corresponding list of supported slices for each TA obtained as defined in clause 5.15.8. NOTE 5: The operator is assumed to ensure that UEs that do not support slice-based N3IWF selection always select an N3IWF that supports at least one slice requested by the UE. This is to avoid unnecessary and potentially repetitive rejections of those UEs. To ensure this, the operator is assumed to provide identifiers of N3IWFs that only support a subset of the slices configured in the network only to UEs that support slice-based N3IWF selection. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.6 |
5,292 | 19.4.2 Fully Qualified Domain Names (FQDNs) 19.4.2.1 General | The encoding of any identifier used as part of a Fully Qualifed Domain Name (FQDN) shall follow the Name Syntax defined in IETF RFC 2181 [18], IETF RFC 1035 [19] and IETF RFC 1123 [20]. An FQDN consists of one or more labels. Each label is coded as a one octet length field followed by that number of octets coded as 8 bit ASCII characters. Following IETF RFC 1035 [19] the labels shall consist only of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-). Following IETF RFC 1123 [20], the label shall begin and end with either an alphabetic character or a digit. The case of alphabetic characters is not significant. Identifiers are not terminated by a length byte of zero. NOTE: A length byte of zero is added by the querying entity at the end of the FQDN before interrogating a DNS server. For the purpose of presentation, identifiers are usually displayed as a string in which the labels are separated by dots (e.g. "Label1.Label2.Label3"). | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.4.2 |
5,293 | – RLC-Config | The IE RLC-Config is used to specify the RLC configuration of SRBs, multicast MRBs and DRBs. RLC-Config information element -- ASN1START -- TAG-RLC-CONFIG-START RLC-Config ::= CHOICE { am SEQUENCE { ul-AM-RLC UL-AM-RLC, dl-AM-RLC DL-AM-RLC }, um-Bi-Directional SEQUENCE { ul-UM-RLC UL-UM-RLC, dl-UM-RLC DL-UM-RLC }, um-Uni-Directional-UL SEQUENCE { ul-UM-RLC UL-UM-RLC }, um-Uni-Directional-DL SEQUENCE { dl-UM-RLC DL-UM-RLC }, ... } UL-AM-RLC ::= SEQUENCE { sn-FieldLength SN-FieldLengthAM OPTIONAL, -- Cond Reestab t-PollRetransmit T-PollRetransmit, pollPDU PollPDU, pollByte PollByte, maxRetxThreshold ENUMERATED { t1, t2, t3, t4, t6, t8, t16, t32 } } DL-AM-RLC ::= SEQUENCE { sn-FieldLength SN-FieldLengthAM OPTIONAL, -- Cond Reestab t-Reassembly T-Reassembly, t-StatusProhibit T-StatusProhibit } UL-UM-RLC ::= SEQUENCE { sn-FieldLength SN-FieldLengthUM OPTIONAL -- Cond Reestab } DL-UM-RLC ::= SEQUENCE { sn-FieldLength SN-FieldLengthUM OPTIONAL, -- Cond Reestab t-Reassembly T-Reassembly } T-PollRetransmit ::= ENUMERATED { ms5, ms10, ms15, ms20, ms25, ms30, ms35, ms40, ms45, ms50, ms55, ms60, ms65, ms70, ms75, ms80, ms85, ms90, ms95, ms100, ms105, ms110, ms115, ms120, ms125, ms130, ms135, ms140, ms145, ms150, ms155, ms160, ms165, ms170, ms175, ms180, ms185, ms190, ms195, ms200, ms205, ms210, ms215, ms220, ms225, ms230, ms235, ms240, ms245, ms250, ms300, ms350, ms400, ms450, ms500, ms800, ms1000, ms2000, ms4000, ms1-v1610, ms2-v1610, ms3-v1610, ms4-v1610, spare1} PollPDU ::= ENUMERATED { p4, p8, p16, p32, p64, p128, p256, p512, p1024, p2048, p4096, p6144, p8192, p12288, p16384,p20480, p24576, p28672, p32768, p40960, p49152, p57344, p65536, infinity, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} PollByte ::= ENUMERATED { kB1, kB2, kB5, kB8, kB10, kB15, kB25, kB50, kB75, kB100, kB125, kB250, kB375, kB500, kB750, kB1000, kB1250, kB1500, kB2000, kB3000, kB4000, kB4500, kB5000, kB5500, kB6000, kB6500, kB7000, kB7500, mB8, mB9, mB10, mB11, mB12, mB13, mB14, mB15, mB16, mB17, mB18, mB20, mB25, mB30, mB40, infinity, spare20, spare19, spare18, spare17, spare16, spare15, spare14, spare13, spare12, spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} T-Reassembly ::= ENUMERATED { ms0, ms5, ms10, ms15, ms20, ms25, ms30, ms35, ms40, ms45, ms50, ms55, ms60, ms65, ms70, ms75, ms80, ms85, ms90, ms95, ms100, ms110, ms120, ms130, ms140, ms150, ms160, ms170, ms180, ms190, ms200, spare1} T-StatusProhibit ::= ENUMERATED { ms0, ms5, ms10, ms15, ms20, ms25, ms30, ms35, ms40, ms45, ms50, ms55, ms60, ms65, ms70, ms75, ms80, ms85, ms90, ms95, ms100, ms105, ms110, ms115, ms120, ms125, ms130, ms135, ms140, ms145, ms150, ms155, ms160, ms165, ms170, ms175, ms180, ms185, ms190, ms195, ms200, ms205, ms210, ms215, ms220, ms225, ms230, ms235, ms240, ms245, ms250, ms300, ms350, ms400, ms450, ms500, ms800, ms1000, ms1200, ms1600, ms2000, ms2400, spare2, spare1} SN-FieldLengthUM ::= ENUMERATED {size6, size12} SN-FieldLengthAM ::= ENUMERATED {size12, size18} RLC-Config-v1610 ::= SEQUENCE { dl-AM-RLC-v1610 DL-AM-RLC-v1610 } RLC-Config-v1700 ::= SEQUENCE { dl-AM-RLC-v1700 DL-AM-RLC-v1700, dl-UM-RLC-v1700 DL-UM-RLC-v1700 } DL-AM-RLC-v1610 ::= SEQUENCE { t-StatusProhibit-v1610 T-StatusProhibit-v1610 OPTIONAL, -- Need R ... } DL-AM-RLC-v1700 ::= SEQUENCE { t-ReassemblyExt-r17 T-ReassemblyExt-r17 OPTIONAL -- Need R } DL-UM-RLC-v1700 ::= SEQUENCE { t-ReassemblyExt-r17 T-ReassemblyExt-r17 OPTIONAL -- Need R } T-StatusProhibit-v1610 ::= ENUMERATED { ms1, ms2, ms3, ms4, spare4, spare3, spare2, spare1} T-ReassemblyExt-r17 ::= ENUMERATED {ms210, ms220, ms340, ms350, ms550, ms1100, ms1650, ms2200} -- TAG-RLC-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,294 | J.1 SRVCC from NR to UTRAN J.1.1 General | 5G Single Radio Voice Call Continuity (SRVCC) is specified in 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [72], TS 23.501[ System architecture for the 5G System (5GS) ] [2] and TS 23.502[ Procedures for the 5G System (5GS) ] [8]. This clause specifies the security aspect to support SRVCC from 5G to UTRAN. SRVCC from UTRAN to 5G shall not be allowed. After a 5G to UTRAN SRVCC session has terminated, a UE shall run a successfully (re)authentication in 5GS before allowed to access 5G. During SRVCC from 5G to UTRAN CS, the MSC server should never know the KAMF nor should the KAMF be revealed to an entity other than an AMF. The AMF derives new key(s) to create a mapped SRVCC security context for the MSC server instead of sending KAMF to the MSC server. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | J.1 |
5,295 | 4.8 Interworking with E-UTRAN connected to EPC 4.8.1 General | In order to interwork with E-UTRAN connected to EPC, the UE supporting both S1 mode and N1 mode can operate in single-registration mode or dual-registration mode (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]). Support of single-registration mode is mandatory for UEs supporting both S1 mode and N1 mode. During the EPS attach procedure (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]) or initial registration procedure (see subclause 5.5.1.2), the mode for interworking is selected if the UE supports both S1 mode and N1 mode, and the network supports interworking. The mode for interworking may also be selected during the EPS tracking area updating procedure (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]) or registration procedure for mobility and periodic registration update (see subclause 5.5.1.3). For interworking between E-UTRAN connected to EPC and TNGF or N3IWF connected to 5GCN, the UE shall operate as specified in either subclause 4.8.2.3 or subclause 4.8.3. Which subclause the UE follows is chosen by the UE irrespective of the interworking without N26 interface indicator. | 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.8 |
5,296 | 5.4.7 E-UTRAN initiated E-RAB modification procedure | When SCG bearer option is applied to support dual connectivity operation, this procedure is used to transfer bearer contexts to and from Secondary eNodeB (see TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]) or Secondary gNodeB (see TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [85]). During this procedure, both the MME and Serving GW are never relocated. The presence of IP connectivity between the Serving GW and the Master eNodeB (see TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5] or TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [85] for Master eNodeB definition), as well as between the Serving GW and the Secondary RAN node is assumed. NOTE: In E-UTRAN, eNodeB is not allowed to negotiate bearer-level QoS parameters as defined in clause 4.7.2.1. Figure 5.4.7-1: E-UTRAN initiated E-RAB modification procedure 1. The Master eNodeB sends a E-RAB Modification Indication message (eNodeB address(es) and TEIDs for downlink user plane for all the EPS bearers, CSG Membership Information, Secondary RAT usage data) to the MME. The Master eNodeB indicates for each bearer whether it is modified or not. If the PLMN has configured secondary RAT usage reporting and the eNodeB has Secondary RAT usage data to report, the Secondary RAT usage data is included. The eNodeB shall include the ECGI and, if Dual Connectivity is activated for the UE, the PSCell ID, in the E-RAB Modification Indication message. If the Secondary eNodeB is a hybrid access eNodeB, the Master eNodeB includes the CSG Membership Information for the SCG bearer(s) in the E-RAB Modification Indication message. The MME determines the CSG membership based on the CSG Membership Information as specified in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5], but does not update the User CSG Information in the Core Network. A failure of the CSG Membership Information verification does not impact the E-UTRAN initiated E-RAB modification procedure. 2. The MME sends a Modify Bearer Request (eNodeB address(es) and TEIDs for downlink user plane for all the EPS bearers, ISR Activated, User Location Information, PSCell ID, Secondary RAT usage data and indication to send it to PDN GW) message per PDN connection to the Serving GW, only for the affected PDN connections. If ISR was activated before this procedure, MME should maintain ISR. The UE is informed about the ISR status in the Tracking Area Update procedure. If the Serving GW supports Modify Access Bearers Request procedure and if there is no need for the SGW to send the signalling to the PDN GW, the MME may send a Modify Access Bearers Request (eNodeB address(es) and TEIDs for downlink user plane for all the EPS bearers, ISR Activated) to the Serving GW to optimise the signalling. If the MME received Secondary RAT usage data in step 1, the MME shall include it in this message. If the MME received PSCell ID in step 1, the MME shall include it in this message. If Secondary RAT usage data was included and if PGW secondary RAT usage data reporting is active, the Serving GW shall send Modify Bearer Request (Secondary RAT usage data) message to the PDN GW for each PDN connection. The PDN GW responds with Modify Bearer Response message to the Serving GW. 3. The Serving GW returns a Modify Bearer Response (Serving GW address and TEID for uplink traffic) message to the MME as a response to a Modify Bearer Request message, or a Modify Access Bearers Response (Serving GW address and TEID for uplink traffic) as a response to a Modify Access Bearers Request message. The Serving GW starts sending downlink packets to the eNodeB using the newly received address and TEID. 4. In order to assist the reordering function in the Master eNodeB and/or Secondary RAN nodes, for the bearers that are switched between Master eNodeB and Secondary RAN nodes, the Serving GW shall send one or more "end marker" packets on the old path immediately after switching the path as defined in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5], clause 10.1.2.2. 5. The MME confirms the E-RAB modification with the E-RAB Modification Confirm (CSG Membership Status) message. The MME indicates for each bearer whether it was successfully modified, kept unmodified or already released by the EPC as defined in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]. For the EPS bearers that have not been switched successfully in the core network, it is the MME decision whether to maintain or release the corresponding EPS bearers. The eNodeB uses the CSG Membership Status to decide on further actions, as specified in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.7 |
5,297 | 8.103 RAN/NAS Cause | RAN/NAS Cause is coded as depicted in Figure 8.103-1. Figure 8.103-1: RAN/NAS Cause The Protocol Type field shall be encoded as per Table 8.103 -0: Table 8.103-0: Protocol Type values All spare bits shall be set to zeros by the sender and ignored by the receiver. The Cause Value field shall be coded as follows: - For S1-AP Cause, the Cause Value field shall contain a non-transparent copy of the cause value of the corresponding IE (see clause 8.2.2), "Cause", as defined in clause 9.2.1.3 in 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10]. The Cause Type field shall contain the RAN Cause subcategory as specified in 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10] and it shall be encoded as in Table 8.103-1. The value of the Cause Value field (and the associated RAN cause subcategory) is transferred over the S1-AP interface and encoded into one octet as binary integer. Table 8.103-1: Cause Type values and their meanings - For EMM and ESM Causes, the Cause Value field shall contain the cause value as specified respectively for the "EMM Cause" IE and "ESM Cause" IE in clauses 9.9.3.9 and 9.9.4.4 of 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [23], or for the "Cause" IE in clause 8.11 of 3GPP TS 24.244[ Wireless LAN control plane protocol for trusted WLAN access to EPC; Stage 3 ] [66]. The value of the Cause Value field (which has a range of 0..255) shall be transferred encoded into one octet as binary integer. The Cause Type field shall be ignored by the receiver. - For Diameter Cause, the Cause Value field shall contain the cause value as specified for the Diameter Termination-Cause AVP in IETF RFC 3588 [39]. The Cause Value field shall be encoded into 2 octets as binary integer of the Termination-Cause AVP value. The currently assigned values for the Termination-Cause AVP can be found in the IANA registry for Termination-Cause AVP Values, IANA, "Termination-Cause AVP Values (code 295)", http://www.iana.org/assignments/aaa-parameters/aaa-parameters.xhtml#aaa-parameters-16. The Cause Type field shall be ignored by the receiver. - For IKEv2 Cause, the Cause Value field shall contain the cause value as specified for the Internet Key Exchange Version 2 (IKEv2) Parameters, Notify message error type, in IETF RFC 7296 [67]. The Cause Value field shall be encoded into 2 octets as binary integer of the IKEv2 notify message error type value. The currently assigned values for the IKEv2 notify message error type can be found in the IANA registry for "Internet Key Exchange Version 2 (IKEv2) Parameters", http://www.iana.org/assignments/ikev2-parameters/ikev2-parameters.xhtml#ikev2-parameters-14 The Cause Type field shall be ignored by the receiver. | 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.103 |
5,298 | 6.3.20 ADRF discovery and selection | Multiple instances of ADRF may be deployed in a network. The NF consumers shall utilize the NRF to discover ADRF instance(s) unless ADRF information is available by other means, e.g. locally configured on NF consumers. The ADRF selection function in NF consumers selects an ADRF instance based on the available ADRF instances. NOTE: When NF consumer is DCCF, the DCCF can have information available already from previous registrations of ADRFs. In this case, NRF discovery is not needed. The following factors may be considered by the NF consumer for ADRF selection: - S-NSSAI. - ML model storage capability. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.20 |
5,299 | 28.3.2.6 5GS Tracking Area Identity (TAI) FQDN | The 5GS Tracking Area Identity (TAI) FQDN shall be constructed as follows: "tac-lb<TAC-low-byte>.tac-mb<TAC-middle-byte>.tac-hb<TAC-high-byte>.5gstac. 5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org" where the <TAC>, together with the <MCC> and <MNC> shall identify the 5GS Tracking Area Identity, and shall be encoded as follows: - <MNC> = 3 digits - <MCC> = 3 digits If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the 5GS TAI FQDN. - The 5GS TAC is a 24-bit integer. The <TAC-high-byte> is the hexadecimal string of the most significant byte in the TAC and the <TAC-low-byte > is the hexadecimal string of the least significant byte. If there are less than 2 significant digits in <TAC-low-byte>, <TAC-middle-byte> or <TAC-high-byte >, "0" digit(s) shall be inserted at the left side to fill the 2 digits coding; As an example, the 5GS Tracking Area Identity for the 5GS TAC H'0B1A21, MCC 345 and MNC 12 is coded in the DNS as: "tac-lb21.tac-mb1a.tac-hb0b.5gstac.5gc.mnc012.mcc345.3gppnetwork.org" | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.3.2.6 |
5,300 | 4.7.3.1.1 GPRS attach procedure initiation | In state GMM-DEREGISTERED, the MS initiates the GPRS attach procedure by sending an ATTACH REQUEST message to the network, starts timer T3310 and enters state GMM-REGISTERED-INITIATED. If timer T3302 is currently running, the MS shall stop timer T3302. If timer T3311 is currently running, the MS shall stop timer T3311. If the MS is configured for "AttachWithIMSI" as specified in 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] and the selected PLMN is neither the registered PLMN nor in the list of equivalent PLMNs, the MS shall include the IMSI in the Mobile identity IE in the ATTACH REQUEST message. For all other cases: If the MS does not support S1 mode: - the MS capable of both Iu mode and A/Gb mode or only of A/Gb mode shall include a valid P-TMSI, if any is available, the P-TMSI signature associated with the P-TMSI and the routing area identity associated with the P-TMSI in the ATTACH REQUEST message. In addition, the MS shall include P-TMSI type IE with P-TMSI type set to "native P-TMSI". If there is no valid P-TMSI available, the IMSI shall be included instead of the P-TMSI and P-TMSI signature. If the MS supports S1 mode: - if the TIN indicates "GUTI" and the MS holds a valid GUTI allocated by an MME, the MS shall map the GUTI into the Mobile identity IE, P-TMSI signature IE and Old routing area identification IE. The MS shall also include P-TMSI type IE with P-TMSI type set to "mapped P-TMSI". Additionally, if the MS holds a valid P-TMSI and RAI, the MS shall indicate the P-TMSI in the Additional mobile identity IE and the RAI in the Additional old routing area identification IE. NOTE: The mapping of the GUTI to the P-TMSI, P-TMSI signature and RAI is specified in 3GPP TS 23.003[ Numbering, addressing and identification ] [10]. - If the TIN indicates "P-TMSI" or "RAT-related TMSI" and the MS holds a valid P-TMSI and a RAI, the MS shall indicate the P-TMSI in the Mobile identity IE and the RAI in the Old routing area identification IE. The MS shall also include P-TMSI type IE with P-TMSI type set to "native P-TMSI". If a P-TMSI signature is associated with the P-TMSI, the MS shall include it in the Old P-TMSI signature IE. - If the TIN is deleted and - the MS holds a valid P-TMSI and a RAI, the MS shall indicate the P-TMSI in the Mobile identity IE and the RAI in the Old routing area identification IE. The MS shall also include P-TMSI type IE with P-TMSI type set to "native P-TMSI". If a P-TMSI signature is associated with the P-TMSI, the MS shall include it in the Old P-TMSI signature IE; or - the MS does not hold a valid P-TMSI and RAI, but holds a valid GUTI allocated by an MME, the MS shall map the GUTI into the Mobile identity IE, P-TMSI signature IE and Old routing area identification IE. The MS shall also include P-TMSI type IE with P-TMSI type set to "mapped P-TMSI"; or - the MS does not hold a valid P-TMSI, RAI or GUTI, the MS shall include the IMSI in the Mobile identity IE. - Otherwise the MS shall include the in the Mobile identity IE. In the cases when the MS maps a GUTI into the Mobile identity IE, P-TMSI signature IE and Old routing area identification IE, then: - If a current EPS security exists, the P-TMSI signature shall include a truncated NAS token as specified in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [123]. In the GPRS ciphering key sequence number IE, the MS shall indicate the value of the eKSI associated with the current EPS security context. The MS shall derive CK' and IK' from the KASME and the NAS uplink COUNT value corresponding to the NAS token derived and handle the START value as specified in 3GPP TS 25.331[ None ] [23c]. Then, the MS shall store the mapped UMTS security context replacing the established UMTS security context for the PS domain. - If a current EPS security does not exist, the MS shall set the truncated NAS token included in the P-TMSI signature to all zeros and the GPRS ciphering key sequence number to "No key is available". If the MS is attaching for emergency bearer services and does not hold a valid GUTI, P-TMSI or IMSI as described above, the IMEI shall be included in the Mobile identity IE. The MS shall also indicate within the DRX parameters whether it supports the split pg cycle option on CCCH. The optional support of the split pg cycle on CCCH by the network is indicated in SI13 or PSI1. Split pg cycle on CCCH is applied by both the network and the MS when the split pg cycle option is supported by both (see 3GPP TS 45.002[ None ] [32]). If the MS supports eDRX and requests the use of eDRX, the MS shall include the extended DRX parameters IE in the ATTACH REQUEST message. In Iu mode, if the MS wishes to prolong the established PS signalling connection after the GPRS attach procedure (for example, the MS has any CM application request pending), it may set a follow-on request pending indicator on (see subclause 4.7.13). An MS attaching for emergency bearer services shall set the follow-on request pending indicator. If the MS supports PSM and requests the use of PSM, then the MS shall include the T3324 value IE with a requested timer value in the ATTACH REQUEST message. When the MS includes the T3324 value IE and the MS indicates support for extended periodic timer value in the MS network feature support IE, it may also include the T3312 extended value IE to request a particular T3312 value to be allocated. In A/Gb mode, if the MS supports the restriction on use of enhanced coverage, then the MS shall set the Restriction on use of enhanced coverage capability bit to "Mobile station supports restriction of use of enhanced coverage" in the MS network capability IE of the ATTACH REQUEST message. If the MS supports dual connectivity of E-UTRA with New Radio (NR), then the MS shall set the Dual connectivity of E-UTRA with NR capability bit to "Mobile station supports dual connectivity of E-UTRA with NR" in the MS network capability IE of the ATTACH REQUEST message. In A/Gb mode, if a UMTS security context is available and if the MS indicates support of integrity protection in the MS network capability IE included in the ATTACH REQUEST message, then the MS shall derive a GPRS GSM Kint key as described in subclause 4.7.7.3b and a GPRS GSM Kc128 key as described in subclause 4.7.7.3a. The MS shall then assign the GPRS GSM Kint key, the GPRS GSM Kc128 key, the GPRS GSM integrity algorithm and the GPRS GSM ciphering algorithm (identified by the information in the Ciphering Algorithm IE and Integrity Algorithm IE stored in the non-volatile ME memory) to the LLC layer, and indicate to the LLC layer that it shall start integrity protection. This shall be done so that the LLC layer can integrity protect, but not cipher, the ATTACH REQUEST message. The MS shall include the CKSN in the CKSN IE in the ATTACH REQUEST message. If the MS has no UMTS security context available, then the MS shall not integrity protect the ATTACH REQUEST message in the LLC layer. In this case the MS shall set the CKSN IE to the value "no key is available" and send the ATTACH REQUEST unprotected. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.3.1.1 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.