Tech-invite  3GPPspecsRELsGlossariesSIP
Info21222324252627282931323334353637384‑5x

full Contents for  TS 23.502  Word version:   16.4.0

Top   Up   Prev   Next
1…   4.2.2.2.2   4.2.2.2.3…   4.2.3…   4.2.3.3   4.2.4…   4.2.6   4.2.7…   4.2.9…   4.3…   4.3.2.2…   4.3.2.2.2   4.3.2.2.3…   4.3.3   4.3.4   4.3.5…   4.3.5.2…   4.3.5.4…   4.3.5.6…   4.3.6…   4.4…   4.5…   4.9…   4.9.1.3…   4.9.2…   4.11…   4.11.1.2.2…   4.11.1.3…   4.11.1.4…   4.11.1.5…   4.11.2   4.11.3…   4.12…   4.12.6…   4.12a   4.12b   4.13…   4.13.4…   4.13.6…   4.14…   4.15…   4.15.4…   4.16…   4.16.4…   4.16.8…   4.17…   4.17.9…   4.18…   4.19…   4.23…   4.23.7…   4.23.9…   4.23.11…   4.24   4.25   4.26…   5…   5.2.3…   5.2.5…   5.2.6…   5.2.7…   5.2.8…   5.2.9…   5.2.12…   A…   E…   F…

 

4.13.4  Emergency ServicesWord-p. 275
4.13.4.1  General
If the 5GS supports Emergency Services, the support is indicated to UE via the Registration Accept message on per-TA-list and per-RAT basis, as described in TS 23.501.
If the 5GS supports Emergency Services Fallback, the support is indicated to UE via the Registration Accept message on per-TA-list and per-RAT basis, as described in TS 23.501.
The UE shall follow the domain selection rules for emergency session attempts as described in TS 23.167.
If the 5GC has indicated Emergency Services Fallback support for the TA and RAT where the UE is currently camping, and if the UE supports emergency services fallback, the UE shall initiate the Emergency Services Fallback procedure described in clause 4.13.4.2.
At QoS Flow establishment request for Emergency Services, the procedure described in clause 4.13.6.2 Inter RAT Fallback in 5GC for IMS voice or the procedure described in clause 4.13.6.1 EPS fallback for IMS voice may be triggered by the network, when configured.
Up
4.13.4.2  Emergency Services Fallback
The call flow in Figure 4.13.4.2-1 describes the procedure for emergency services fallback.
Up
Step 1.
UE camps on E-UTRA or NR cell in the 5GS (in either CM_IDLE or CM_CONNECTED state).
Step 2.
UE has a pending IMS emergency session request (e.g. voice) from the upper layers.
Step 3.
If the AMF has indicated support for emergency services using fallback via the Registration Accept message for the current RAT, the UE sends a Service Request message indicating that it requires emergency services fallback. The UE is not required to include the PDU Sessions that are not relevant for the emergency service in the List Of PDU Sessions to be Activated in the Service Request for the emergency service.
NOTE 1:
If the UE includes PDU Sessions to be Activated in the Service Request for the emergency service, it will delay the Emergency Services Fallback procedure.
Step 4.
5GC triggers a request for Emergency Services Fallback by executing an NG-AP procedure in which it indicates to NG-RAN that this is a fallback for emergency services. The AMF based on the support of Emergency Services in EPC or 5GC may indicate the target CN for the RAN node to know whether inter-RAT fallback or inter-system fallback is to be performed. When AMF initiates Redirection for UE(s) that have been successfully authenticated, AMF includes the security context in the request to trigger fallback towards NG-RAN.
Step 5.
Based on the target CN if indicated in message 4 or otherwise based on the RAN configuration, one of the following procedures is executed by NG-RAN:
Step 5a.
NG-RAN initiates handover (see clause 4.9.1.3) or redirection to a 5GC-connected E-UTRAN cell, if UE is currently camped on NR.
Step 5b.
NG-RAN initiates handover (see clause 4.11.1.2.1) or redirection to E-UTRAN connected to EPS. NG-RAN uses the security context provided by the AMF to secure the redirection procedure.
If the redirection procedure is used either in 5a or 5b the target CN type (EPC or 5GC) is also conveyed to the UE in order to be able to perform the appropriate NAS procedures (S1 or N1 Mode). The UE uses the emergency indication in the RRC message as specified in clause 6.2.2 of TS 36.331 and E-UTRAN provides the emergency indication to AMF (during Registration triggered by step 5a) and MME (during Tracking Area Update triggered by step 5b). Both the Registration and the Tracking Area Update requests should contain Follow-on request and active flag respectively to indicate that the UE has "user data pending". For the handover procedure used in step 5b see clause 4.11.1.2.1, step 1.
In step 5b, if the MME does not support emergency services for that UE, the MME should act such that the call for emergency service is likely to succeed promptly, e.g., if the UE successfully completed a combined TA/LA Update with the network, by using the CSFB procedures specified in TS 23.272.
NOTE 2:
If such a combined TA/LA Update is not successful, or the UE did not request a combined update, then, as specified in TS 23.167, the UE autonomously selects a RAT that may (but which might not) support the CS domain.
Step 6.
After handover or redirection to the target cell the UE establishes a PDU Session / PDN connection for IMS emergency services and performs the IMS procedures for establishment of an IMS emergency session (e.g. voice) as defined in TS 23.167.
Up
4.13.5  Location Services proceduresWord-p. 277
4.13.5.0  General [R16]
Location Service procedures are defined in TS 23.273.
4.13.5.1  5GC-NI-LR Procedure
Location Service procedures are defined in TS 23.273.
4.13.5.2  5GC-MT-LR Procedure without UDM Query
Location Service procedures are defined in TS 23.273.
4.13.5.3  5GC-MT-LR Procedure
Location Service procedures are defined in TS 23.273.
4.13.5.4  UE Assisted and UE Based Positioning Procedure
Location Service procedures are defined in TS 23.273.
4.13.5.5  Network Assisted Positioning Procedure
Location Service procedures are defined in TS 23.273.
4.13.5.6  Obtaining Non-UE Associated Network Assistance Data
Location Service procedures are defined in TS 23.273.
4.13.5.7  Location continuity for Handover of an Emergency session from NG-RAN
Location Service procedures are defined in TS 23.273.

Up   Top   ToC