hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
aac84734dd828878c9914c9a3545338d | 23.272 | 6.3 Mobile Originating call in Active Mode – No PS HO support | This procedure is executed when PS HO is not supported, in the normal case. Clause 6.6 describes the procedure when the procedure is rejected by the MME.
Figure 6.3-1: CS Call Request in E-UTRAN, Call in GERAN/UTRAN without PS HO
1a. The UE sends an Extended Service Request for mobile originating CS fallback to the MME... |
aac84734dd828878c9914c9a3545338d | 23.272 | 6.4 Mobile Originating call in Idle Mode | Mobile Originating call in Idle Mode procedure is specified by reusing the Mobile Originating Call in Active mode procedures as specified in clauses 6.2 and 6.3 with Extended Service Request for mobile originating CS fallback to the MME where the messages S1-AP UE Context Modification Request and Response are replaced ... |
aac84734dd828878c9914c9a3545338d | 23.272 | 6.5 Returning back to E-UTRAN | Once CS service ends in CS domain, existing mechanisms can be used to move the UE to E‑UTRAN, no specific CS Fallback mechanisms are needed.
During the release of an RR connection the MSC should indicate to GERAN/UTRAN that the RR connection (for call or CISS or LCS) was established as a result of CS fallback. GERAN an... |
aac84734dd828878c9914c9a3545338d | 23.272 | 6.6 Mobile Originated or Mobile terminated call rejected by the MME | The MME may reject an Extended Service Request either for mobile originated or mobile terminated CSFB. The following procedure covers this scenario.
Figure 6.6-1: CSFB MO or MT call, rejected by MME
1. UE is combined EPS/IMSI attached.
2. UE makes a decision to perform a mobile originated CS call or accepts CS paging f... |
aac84734dd828878c9914c9a3545338d | 23.272 | 7 Mobile Terminating Call | |
aac84734dd828878c9914c9a3545338d | 23.272 | 7.1 General | This clause describes the mobile terminating call procedures for the CS Fallback in EPS.
The MSC handles the timers, queuing and retransmission for sending the SGsAP-PAGING-REQUEST message on the SGs interface in the same way that it handles the sending of a PAGING message on the A or Iu interface. As a consequence, th... |
aac84734dd828878c9914c9a3545338d | 23.272 | 7.2 Mobile Terminating call in idle mode | The procedure for Mobile Terminating Call in idle mode is illustrated in figure 7.2-1, in the normal case. Clause 6.6 describes the procedure when the procedure is rejected by the MME.
Figure 7.2-1: Mobile Terminating Call in idle mode
1. G‑MSC receives IAM.
2. G‑MSC retrieves routing information of the terminating UE ... |
aac84734dd828878c9914c9a3545338d | 23.272 | 7.3 Mobile Terminating call in Active Mode - PS HO supported | This flow may be executed when the eNodeB knows that both the UE and the network support PS HO in the normal case. Clause 6.6 describes the procedure when the procedure is rejected by the MME.
Figure 7.3-1: CS Page in E-UTRAN, Call in GERAN/UTRAN
1a. The MSC receives an incoming voice call and responds by sending a Pag... |
aac84734dd828878c9914c9a3545338d | 23.272 | 7.4 Mobile Terminating call in Active Mode - No PS HO support | This procedure is executed when PS HO is not supported, in the normal case. Clause 6.6 describes the procedure when the procedure is rejected by the MME.
Figure 7.4-1: CS Page in E-UTRAN, Call in GERAN/UTRAN without PS HO
1a. The MSC receives an incoming voice call and responds by sending a Paging Request (IMSI or TMSI... |
aac84734dd828878c9914c9a3545338d | 23.272 | 7.5 Roaming Retry for CS fallback | The procedure in this clause may be applied for mobile terminated calls where the MSC, to which the UE sends the LAU, is different from the MSC that sent the paging message to the UE. The procedure is based on the "Mobile Terminating Roaming Retry Call" procedure defined in TS 23.018 [5] and there is an only minor adap... |
aac84734dd828878c9914c9a3545338d | 23.272 | 7.6 Returning back to E-UTRAN | Once CS service ends in CS domain, existing mechanisms can be used to move the UE to E-UTRAN, no specific CS Fallback mechanisms are needed.
During the release of an RR connection the MSC should indicate to GERAN/UTRAN that the RR connection (for call or CISS or LCS) was established as a result of CS fallback. GERAN an... |
aac84734dd828878c9914c9a3545338d | 23.272 | 7.7 Interaction with ISR | |
aac84734dd828878c9914c9a3545338d | 23.272 | 7.7.1 Void | |
aac84734dd828878c9914c9a3545338d | 23.272 | 7.7.2 Mobile Terminating Call when ISR is active and SGs is active between MSC/VLR and MME | Figure 7.7.2-1: Mobile Terminating Call when ISR is active and SGs is active between MSC/VLR and MME
1) G-MSC receives IAM.
2) G-MSC retrieves routing information of the terminating UE by Send Routing Info procedures as specified in TS 23.018 [5].
3) G-MSC sends IAM to the MSC/VLR on the terminating side as specified i... |
aac84734dd828878c9914c9a3545338d | 23.272 | 7.7.3 Void | |
aac84734dd828878c9914c9a3545338d | 23.272 | 7.8 Mobile Terminating Call when SGs is not active | Regular pre-Release 8 MSC procedures are performed without any ISR or SGs specifics. |
aac84734dd828878c9914c9a3545338d | 23.272 | 8 Other CS Services | |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.1 General | The MSC handles the timers, queuing and retransmission for sending the SGsAP-PAGING-REQUEST message on the SGs interface in the same way that it handles the sending of a PAGING message on the A or Iu interface. As a consequence, the MME and (if ISR is active) the SGSN shall not implement local retransmission schemes fo... |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.2 Short Message Service (SMS) | |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.2.1 General | The procedures for SMS in this specification apply only if the UE is EPS/IMSI attached and the Non Access Stratum signalling based SMS transfer is chosen by the UE and/or the home PLMN for delivering short messages.
This clause describes both the mobile originating and mobile terminating SMS over SGs procedures in EPS.... |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.2.2 Mobile originating SMS in Idle Mode | The following sequence flow shows the delivery of mobile originating SMS in idle mode. The message flows between the ME/UE and MSC/VLR are also broadly applicable to the Memory Available Notification.
Figure 8.2.2-1: Mobile originating SMS in idle mode
1. The combined EPS/IMSI attach procedure as described in clause 5.... |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.2.3 Mobile originating SMS in Active Mode | Mobile Originating SMS in active Mode procedure is specified by reusing the Mobile Originating SMS in Idle Mode with the following modification:
- The established signalling connection between the MS/UE and the MME is reused for the transport of the SMS message and the delivery report (i.e. the UE triggered Service Req... |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.2.4 Mobile terminating SMS in idle mode | The following sequence flow shows the delivery of mobile terminating SMS in idle mode.
Figure 8.2.4-1: Mobile terminating SMS in idle mode
1. The combined EPS/IMSI attach procedure as described in clause 5.2 has been performed.
2‑4. The SC initiates transfer of mobile terminating SMS. The HLR is requested for routing n... |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.2.5 Mobile terminating SMS in Active Mode | Mobile terminating SMS in Active Mode procedure is specified by reusing the Mobile Terminating SMS in Idle Mode with the following modification:
- There is no need for the MME to perform Paging of the MS/UE after step 5. MME continues with step 8a (i.e. steps 6 to 8 are skipped). The MME immediately sends a Downlink Un... |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.2.6 Co-Existence with SMS over generic 3GPP IP access | If the home operator has deployed SMS over generic 3GPP IP access and/or SMS-Instant Messaging Interworking as defined in TS 23.204 [15], and has configured the network and the UE for using SMS over IP or SMS-Instant Messaging Interworking, then an SMS or IM will be delivered over EPS in any visited network whether or ... |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.3 Location Services (LCS) | |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.3.1 MO-LR procedure | |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.3.1.1 General | MO-LR procedure in the CS fallback in EPS is performed as specified in TS 23.271 [8].
When the MO-LR procedure is triggered by the UE's application, UE will check the LCS Support Indication provided by the Attach and TAU procedures as specified in TS 23.401 [2]:
- If the LCS Support Indication indicates EPC-MO-LR is su... |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.3.1.2 MO-LR in Active Mode with IMS VoIP session - PS HO supported | Figure 8.3.1.2-1: MO-LR Request in E-UTRAN while UE is in IMS VoIP session
1a.-2. These steps are performed as defined in clause 6.2.
3. Based on UE measurement reports and CS Fallback Indicator in step 1b, the source E‑UTRAN decides to trigger an SRVCC handover to UTRAN/GERAN. Continuous SRVCC procedures are continued... |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.3.1.3 MO-LR in Active Mode with IMS VoIP session - No PS HO supported | The same procedure as described in clause 8.3.1.2 applies for "MO-LR in Active Mode with IMS VoIP session - No PS HO supported" case except that the SRVCC procedure in step 3 follows TS 23.216 [20], clause 6.2.2.1a. |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.3.2 MT-LR procedure | |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.3.2.1 MT-LR procedure if UE is not in IMS VoIP session | Figure 8.3.2.1-1: MT-LR procedure if UE is not in IMS VoIP session
1. MSC receives a PROVIDE_SUBSCRIBER_LOCATION message due to CS‑MT‑LR (TS 23.271 [8], clause 9.1.2).
2. MSC sends Paging (LCS Client Identity, LCS indicator) message to MME.
3. If the MME did not return the "SMS-only" indication to the UE during Attach ... |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.3.2.2 MT-LR procedure while UE is in IMS VoIP session | Figure 8.3.2.2-1: MT-LR procedure while UE is in IMS VoIP session
1. MSC receives a PROVIDE_SUBSCRIBER_LOCATION message due to CS MT LR (TS 23.271 [8], clause 9.1.2).
1a. The MSC responds by sending a Paging Request (LCS Client Identity, LCS indicator) to the MME over a SGs interface. The MSC only sends a CS Page for a... |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.3.3 NI-LR procedure | NI-LR procedure takes place during emergency calls, and is thus performed in GERAN/UTRAN during the Mobile Originating call procedure. |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.3.4 Returning back to E-UTRAN | Once CS service ends in CS domain, existing mechanisms as specified in TS 23.401 [2] can be used to move the UE to E-UTRAN, no specific CS Fallback mechanisms are needed.
During the release of an RR connection the MSC should indicate to GERAN/UTRAN that the RR connection (for call or CISS or LCS) was established as a r... |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.3.5 Co-Existence with Other Location Services | |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.3.5.1 Co-Existence with SUPL | There is no race condition between OMA AD SUPL [9] and CS Fallback for LCS. When network initiated SUPL procedure takes place, the paging message does not contain CN Domain Indicator by default. This prevents CS Fallback for LCS to take place. For SET initiated SUPL procedure, changing of RAT does not take place. |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.4 Other CS Services | |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.4.0 General | The procedures specified in this clause apply when the UE is EPS/IMSI attached and the CS domain is chosen by the UE and/or the home PLMN to deliver other types of CS services, i.e. services not covered explicitly in previous clauses, such as Call Independent Supplementary Services, real time end-to-end facsimile group... |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.4.1 Mobile-Initiated CS Services | |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.4.1.1 Mobile-Initiated CS Services if UE is not in IMS VoIP session | When UE is in active mode, UE and the network follow the procedure in clause 6.2 "Mobile Originating Call in Active‑Mode". After UE changes its RAT from E‑UTRAN to UTRAN/GERAN, it performs Mobile‑Initiated CS procedures relevant to the initiated CS service, e.g. Call Independent Supplementary Service procedure as speci... |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.4.1.2 Mobile-Initiated CS Services while UE is in IMS VoIP session | When the UE is in active mode with an IMS VoIP session and if the UE supports SRVCC procedures, the procedure for Mobile-Initiated CS Services while UE is in IMS VoIP session is the same as for "NW-Initiated CS Services while UE is in IMS VoIP session" in clause 8.4.2.2 from step 1b (Extended Service Request), with the... |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.4.2 NW-Initiated CS Services | |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.4.2.1 NW-Initiated CS Services if UE is not in IMS VoIP session | Figure 8.4.2.1-1: NW-Initiated CS Service procedure
1. MSC/VLR receives a trigger for a NW-Initiated CS procedure.
2. MSC/VLR sends Paging message to MME. For call independent supplementary service, the Paging message may include the SS service ID.
3. If the MME did not return the "SMS-only" indication to the UE during... |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.4.2.2 NW-Initiated CS Services while UE is in IMS VoIP session | Figure 8.4.2.2-1: NW-Initiated CS Service procedure while UE is in IMS VoIP session
1. MSC/VLR receives a trigger for a NW-Initiated CS procedure.
1a. The MSC responds by sending a Paging Request to the MME over a SGs interface. For call independent supplementary service, the Paging message may include the SS service I... |
aac84734dd828878c9914c9a3545338d | 23.272 | 8.4.3 Returning back to E-UTRAN | Once CS service ends in CS domain, existing mechanisms as specified in TS 23.401 [2] can be used to move the UE to E‑UTRAN, no specific CS Fallback mechanisms are needed. During the release of an RR connection the MSC should indicate to GERAN/UTRAN that the RR connection (for call or CISS or LCS) was established as a r... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 1 Scope
| The present document specifies the stage 2 of the service-based architecture used for location services in the 5G system, and corresponding Network Functions (NFs), NF services and procedures, to meet the service requirements defined in TS 22.261 [3] and TS 22.071 [2].
Location Services specified in the present docume... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 3 Definitions and Abbreviations
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 3.1 Definitions
| For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
5G enhanced positioning area: see TS 22.261 [3].
5G positioning service area: see ... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 3.2 Abbreviations
| For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
APN Access Point Name
APN-NI APN Network Identifier
EDT Early Data Trans... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4 Architecture Model and Concepts
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.1 General Concepts
| A general description of location services and service requirements are given in the specification TS 22.071 [2] and TS 22.261 [3]. Support of location services for GERAN, UTRAN and E-UTRAN access networks is described in TS 23.271 [4], TS 43.059 [5], TS 25.305 [17] and TS 36.305 [7].
The positioning of a UE can be su... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.2 Architectural Reference Model
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.2.1 Non-roaming reference architecture
| Figure 4.2.1-1 shows an architectural reference model for 5GS LCS for a non-roaming UE and PRU in reference point representation.
Figure 4.2.1-1: Non-roaming reference architecture for Location Services in reference point representation
NOTE 1: (R)AN represents NG-RAN, trusted non-3GPP access or untrusted non-3GPP ... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.2.2 Roaming reference architecture
| Figure 4.2.2-1 shows an architectural reference model for 5GS LCS for a roaming UE and PRU in reference point representation.
Figure 4.2.2-1: Roaming reference architecture for Location Services in reference point representation
NOTE 1: (R)AN represents NG-RAN, trusted non-3GPP access or untrusted non-3GPP access.
... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.2.3 Reference architecture with sidelink positioning
| Architectural reference model for 5GS LCS with sidelink positioning in reference point representation and in SBI representation is in clause 4.2 of TS 23.586 [40].
4.2a Interconnection between 5GC and EPC
4.2a.1 General
For MT-LR Location Request, when a LCS service request is received at 5GC GMLC, the target UE may... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.3 Functional description of LCS per network function
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.3.1 Access Network
| The Access Network is involved in the handling of various positioning procedures including positioning of a target UE, provision of location related information not associated with a particular target UE and transfer of positioning messages between an AMF or LMF and a target UE. The Access Network shall support determi... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.3.2 LCS Clients, Application Functions and Network Functions
| AFs and NFs may access LCS services from a GMLC in the same trust domain (e.g. in the same PLMN) using the Ngmlc interface or Event Exposure with location information from an AMF in the same trust domain using the Namf interface. The NWDAF collects UE location information by accessing GMLC directly.
LCS Clients may ac... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.3.3 Gateway Mobile Location Centre, GMLC
| The Gateway Mobile Location Centre (GMLC) contains functionality required to support LCS. In one PLMN, there may be more than one GMLC.
A GMLC is the first node an external LCS client accesses in a PLMN (i.e. the Le reference point is supported by the GMLC). AFs and NFs may access GMLC directly or via NEF. The GMLC ma... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.3.4 Location Retrieval Function, LRF
| The Location Retrieval Function (LRF) may be collocated with a GMLC or separate and is responsible for retrieving or validating location information, providing routing and/or correlation information for a UE which has initiated an IMS emergency session. The information is provided by an LRF to an E-CSCF. For more detai... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.3.5 UE
| A target UE may support positioning according to four different modes:
- UE assisted mode (the UE obtains location measurements and sends the measurements to another entity (e.g. an LMF) to compute a location);
- UE based mode (the UE obtains location measurements and computes a location estimate making use of assist... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.3.6 UDM
| The UDM contains LCS subscriber LCS privacy profile and routing information. The UDM is accessible from an AMF, GMLC or NEF via the Nudm interface.
The UDM may also contain an indication whether a UE is allowed to serve as a PRU and indication whether PRU is stationary PRU as part of the UE subscription data.
The UDM... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.3.7 Access and Mobility Management Function, AMF
| The AMF contains functionality responsible for managing positioning for a target UE for all types of location request. The AMF is accessible to the GMLC and NEF via the Namf interface, to the RAN via the N2 reference point and to the UE via the N1 reference point.
Functions which may be performed by an AMF to support ... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.3.8 Location Management Function, LMF
| The LMF manages the overall co-ordination and scheduling of resources required for the location of a UE that is registered with or accessing 5GCN. It also calculates or verifies a final location and any velocity estimate and may estimate the achieved accuracy. The LMF receives location requests for a target UE from the... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.3.9 Network Exposure Function, NEF
| An NEF provides a means of accessing location services by an external AF or internal AF. AFs access location services from an NEF using an API. Depending on QoS requirements, an NEF can forward a location request to a GMLC or request an event exposure for location information from serving AMF (optionally via a UDM). Wh... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.3.10 Unified Data Repository, UDR
| The UDR contains privacy data information for target UEs and may be updated by a serving AMF via UDM with new privacy information received from a UE.
|
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.3.11 Positioning Reference Unit, PRU
| A UE may support the functions of a PRU. The PRU supports the following functions including functions defined in TS 38.305 [9]:
- Support service level association, association update and disassociation with a serving LMF.
- The PRU sends service level association, association update or disassociation to LMF via LCS ... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.3.12 Network Repository Function, NRF
| In addition to the functions defined in TS 23.501 [18], the NRF may perform the following functions:
- Support to store or update PRU existence indication in TAI level in LMF profile based on request from PRU serving LMF.
- Support LMF(s) with PRU function discovery by AMF.
- LMF discovery by considering user plane ... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.3.13 Network Data Analytics Function, NWDAF
| LMF may provide input data to NWDAF for ML model training or ML model performance monitoring for LMF-based AI/ML Positioning.
LMF may obtain ML model from NWDAF for performing AI/ML Positioning.
|
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.4 Reference Point to Support Location Services
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.4.1 Le Reference Point
| The Le reference point supports location requests sent by an LCS Client to a GMLC or LRF.
The Le reference point may be supported using the Mobile Location Protocol (MLP) defined by OMA [13].
The Le reference point may also be supported using the HTTP-Enabled Location Delivery (HELD) [52] in location session associat... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.4.2 NL3 Reference Point
| The NL3 reference point supports location requests forwarded by an HGMLC to a VGMLC.
|
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.4.3 N1 Reference Point
| The N1 reference point supports transfer of supplementary services messages between a serving AMF and target UE to support privacy notification and verification and change of UE privacy preference. The N1 reference point also supports transfer of positioning protocol messages and location event reports between a target... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.4.4 N2 Reference Point
| The N2 reference point supports transfer of positioning messages, via an AMF, between an LMF and a RAN node, or N3IWF in the case of untrusted non-3GPP access. The N2 reference point also supports transfer of messages, via an AMF, from an LMF to an NG-RAN node, which carry assistance data to be broadcast by the NG-RAN ... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.4.5 Void
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.4.6 NL5 Reference Point
| The NL5 reference point supports location requests sent by an NEF or other NF to a GMLC.
|
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.4.7 NL2 Reference Point
| The NL2 reference point supports location requests sent by a GMLC to a serving AMF for a target UE.
Messages for the NL2 reference point are defined in TS 29.518 [16].
|
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.4.8 NL6 Reference Point
| The NL6 reference point supports queries from an HGMLC to a UDM for privacy subscription information for a target UE and routing information for a target UE.
|
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.4.9 N51 Reference Point
| The N51 reference point supports queries from an NEF to a serving AMF for the location of a target UE.
Messages for the N51 reference point are defined in TS 29.518 [16].
|
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.4.10 NL1 Reference Point
| The NL1 reference point supports location requests for a target UE sent from a serving AMF for the target UE to an LMF. Location requests are supported for immediate location and for deferred location for periodic or triggered location events.
The NL1 reference point also supports the transfer from an LMF to an AMF of... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.4.11 N52 Reference Point
| The N52 reference point supports queries from an NEF to a UDM for privacy subscription information for a target UE and routing information for a target UE. The N52 interface also supports a request from an NEF to a UDM to forward a location request from the NEF to a serving AMF for the target UE.
|
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.4.12 NL7 Reference Point
| The NL7 reference point supports location context transfer between two LMFs.
|
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.4.13 NL8 Reference Point
| The NL8 reference point supports LMF to receive location related analytics from NWDAF, provide input data for model training or model performance monitoring to NWDAF, or receive AI/ML positioning model from NWDAF, as defined in TS 23.288 [37].
|
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.4.14 NL9 Reference Point
| The NL9 reference point supports location requests sent by NWDAF to a GMLC.
|
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.4.15 NL10 Reference Point
| The NL10 reference point supports LMF to send location requests to GMLC in case of 5GC-MT-LR involving MBSR and MWAB. Additionally, this reference point is used by LMF to send location result directly to GMLC in case of Deferred Location or 5GC-MT-LR multiple location or in case of support for PNI-NPN architecture.
|
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.4.16 NL11 Reference Point
| NL11 reference point enables user plane between UE and LMF.
|
691e61617b7dc9da01beed39caa1e157 | 23.273 | 4.5 Service Based Interfaces to Support Location Services
| The 5GS LCS architecture contains the following service-based interfaces for Location Services:
Nlmf: Service-based interface exhibited by LMF.
Ngmlc: Service-based interface exhibited by GMLC.
|
691e61617b7dc9da01beed39caa1e157 | 23.273 | 5 High Level Features
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 5.1 LMF Discovery and Selection
| LMF selection functionality is supported by the AMF to determine an LMF for location estimation of the target UE or Ranging/Sidelink Positioning between Target UE and SL Reference UE. The LMF selection functionality is also supported by the LMF if it determines that it is unsuitable or unable to support location for th... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 5.2 3GPP access specific aspects
| When 3GPP access type is selected, the positioning methods for 3GPP access defined in TS 38.305 [9] apply.
Access Type Selection for LCS Service is defined in clause 5.3.2.
|
691e61617b7dc9da01beed39caa1e157 | 23.273 | 5.3 Non-3GPP Access Specific Aspects
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 5.3.1 Location Information for Non-3GPP Access
| If the UE registered to non-3GPP access, following information can be regarded as UE location information:
Table 5.3.1-1: Supported UE location information of non-3GPP access
Untrusted non-3GPP Access
Trusted non-3GPP Access
Wireline Access
UE Side
N5CW device Side for Trusted WLAN Access
5G-RG side for Wireli... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 5.3.2 Access Type Selection for LCS Service
| The positioning of a UE can be performed via either 3GPP access network or non-3GPP access network.
For a MT-LR Location Service request, in order to select the positioning access type, the GMLC uses information retrieved from the UDM and optionally serving AMFs, e.g. access type, its serving AMF identity(ies), and UE... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 5.4 UE LCS privacy
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 5.4.1 General
| An LCS client or AF may or may not be authorised to retrieve the UE location, e.g. for commercial use. UE LCS privacy is a feature which allows a UE and/or AF to control which LCS clients and AFs are and are not allowed access to UE location information. UE LCS privacy can be supported via subscription and via UE LCS p... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 5.4.2 Content of UE LCS Privacy Profile
| |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 5.4.2.1 General
| The UE LCS privacy profile shall include information related to classes of LCS client, referred to as "privacy classes", which are permitted, or conditionally permitted, to obtain location information for the UE. Privacy classes are defined in clause 9.5.3 of TS 23.271 [4], but not all classes defined in TS 23.271 [4] ... |
691e61617b7dc9da01beed39caa1e157 | 23.273 | 5.4.2.2 Privacy Classes
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.