Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.586  Word version:  18.5.0

Top   Top   Up   Prev   Next
1…   4.2…   4.2.2   4.2.3   4.2.4…   4.3…   5…   5.5…   6…   6.4…   6.5…   6.7…   6.9…

 

6.5  Procedure for UE Positioning assisted by Sidelink Positioning and involving 5GCp. 39

6.5.1  Procedures for Network based SL Positioning for UE with NAS connectionp. 39

6.5.1.1  MO-LR Procedure for Network based SL Positioning for UE with NAS connectionp. 39

UE can trigger 5GC-MO-LR and the LMF determines that SL positioning will be used to determine the absolute location of the UE as specified in 5GC-MO-LR procedure using SL positioning in clause 6.20.2 of TS 23.273 or the UE can trigger SL-MO-LR procedure defined in clause 6.20.1 of TS 23.273 is performed with the following adaptations:
  • UE1 is the Target UE, and UE2/.../UEn is the Located UE.
  • It is indicated in step 8 that location calculation assistance by the network is needed and absolute location is required.
Up

6.5.1.2  MT-LR Procedure for Network-based SL Positioning for UE with NAS connectionp. 40

5GC-MT-LR using SL positioning procedure as defined in clause 6.20.5 of TS 23.273 is performed with the following adaptations:
  • The LMF performs the absolute location estimation.

6.5.2  Procedures for Network-based SL Positioning for UE without NAS connectionp. 40

The procedures for Network based SL positioning for UE without NAS connection apply to the following cases:
  • when the Target UE initiates 5GC-MO-LR request to obtain its own absolute location and cannot establish a NAS connection or cannot be served by a Ranging/SL positioning capable LMF
  • when the target UE detects an event configured by the network during an initial 5GC-MT-LR procedure when the Target UE has the NAS connection
The procedures for Network based SL positioning for UE without NAS connection takes the SL-MO-LR procedure in TS 23.273 as baseline with following adaptations based on the functionalities described in clause 5.5.3:
  • UEx (one of the UE2/.../UEn) is the Target UE that cannot set up a NAS connection or that cannot be served by a Ranging/SL positioning capable LMF, and UE1 is Located UE that is in coverage and can be served by a Ranging/SL positioning capable LMF.
  • In step2, it is the UEx (Target UE) that performs UE1 (Located UE) discovery.
  • In step 6, when the UEx(Target UE) initiates SL-MO-LR service request to UE1(Located UE), the UEx(Target UE) requests UE1(Located UE) to return the Target UE's absolute location and may indicate whether the absolute location should be transferred to an LCS client or AF. For transfer to an LCS Client or AF, Target UE ID and the Deferred routing ID may be included.
  • It is the UE 1 as the Located UE that performs the SL-MO-LR with the step 8~23 with following adaptions:
    • In Step 8: UE1(Located UE) sends SL-MO-LR request which indicates that the Target UE's absolute location is required, may indicate that the location calculation assistance by the network is needed, and may indicate that location results need to be transferred to the LCS client or AF for UEx (Target UE). For transfer to the LCS Client or AF, the Target UE ID, i.e. Application Layer ID and the Deferred routing ID may be included along with the SL-MO-LR request. The SL positioning measurement data may be included in step 8.
    • The LMF determines the network based calculation taking the obtained capability of UE in step 10 and step 11 into account.
    • The LMF requests for the location information from the UE1(Located UE) in step14.
    • The step17 for UE based calculate is not needed.
    • The UE1(Located UE) returns the SL location measurement data to the LMF in step18.
    • When SL positioning measurement data was provided in step 8, step 12~17 may be omitted.
    • The LMF calculates the location result (i.e. the absolute Location of Target UE) based on the SL location measurement data and the location of the UE1(Located UE) in step19, and provides the location of UEx(Target UE) to the UE1 (Located UE) in step 22.
    • In case the LMF has the valuable UEx(Target UE) context based on the Deferred routing ID, then the LMF provides the resulting location of the UEx(Target UE) via the GMLC to the LCS Client or AF in step 22. In case the UEx(Target UE) context was deleted, transferring location of the UEx(Target UE) to the LCS Client or AF is not proceeded.
  • The UE1 (Located UE) returns the absolute location result (i.e. the absolute Location of Target UE) to the UEx(Target UE) in step23 over PC5.
    In this Release, Procedures for Network-based SL Positioning for UE without NAS connection is not supported.
Up

6.5.3  Procedures for Network-assisted SL Positioning for UE with NAS connectionp. 41

6.5.3.1  MO-LR Procedure for Network-assisted SL Positioning for UE with NAS connectionp. 41

The procedures defined in this clause apply to Network-assisted SL Positioning for UE with NAS connection, as defined in clause 5.5.4, when the service request is initiated by the Target UE.
If the Located UE(s) is known to the Target UE (e.g. based on Located UE discovery and selection), SL-MO-LR procedure defined in clause 6.20.1 of TS 23.273 is performed with the following adaptations:
  • UE1 is the Target UE, and UE2/.../UEn is the Located UE. UE1 provides application layer ID of UE2/.../UEn as the Located UE ID in the SL-MO-LR request.
  • It is indicated in step 8 that absolute location of UE1 is required.
  • It is indicated in step 15 that Network-assisted SL Positioning is applie.
  • In step 19, the response includes absolute location of UE1.
  • Step 20 and step 23 are skipped.
If the Located UE(s) is not known to the Target UE, 5GC-MO-LR procedure using SL positioning defined in clause 6.20.2 of TS 23.273 is performed.
Up

6.5.3.2  MT-LR Procedure for Network-assisted SL Positioning for UE with NAS connectionp. 41

The procedures defined in this clause apply to Network-assisted SL Positioning for UE with NAS connection, as defined in clause 5.5.4, when the service request is initiated by the AF or LCS Client.
5GC-MT-LR procedure using SL positioning defined in clause 6.20.5 of TS 23.273 is performed.

6.5.4  Procedures for Network-assisted SL Positioning for UE without NAS connectionp. 41

The Procedures for Network-assisted SL Positioning for UE without NAS connection take the Procedures for Network based SL positioning for UE without NAS connection in clause 6.5.2 as baseline with following adaptations based on the functionalities defined in clause 5.5.5:
  • In Step 8: UE1 (Located UE) may indicate that the assistance data or location calculation assistance is needed.
  • The LMF determines the UE based calculation taking the obtained capability of UE in step 10 and step 11 into account.
  • The LMF provides the assistance data to UE1 (Located UE) in step 12~13, and requests the UE1 (Located UE) to return the result to the LMF if the UE1 (Located UE) is the SL location server UE enabled in step14.
  • If the UE1 (Located UE) is not SL server UE enabled, the LMF may select a SL Positioning Server UE to calculate the result, in this case the LMF provides the assistant data and the location of the UE1 (Located UE) to the selected SL Positioning Server UE in step 12-13, and ask for returning the calculation result in step14.
  • The UE1 (Located UE) or a selected SL location server UE retunes the calculation result (i.e. the Target UE's absolute location) to the LMF in step18.
In this Release, Procedures for Network-assisted SL Positioning for UE without NAS connection is not supported.
Up

6.6  Procedure of UE only Sidelink Positioning for Target UE using Located UEp. 42

This procedure is used to acquire absolute location of Target UE using Located UE, where LMF is not involved for SL Positioning/Ranging. The Located UE is assumed to already know its absolute location or can get its absolute location via the legacy 5GC-MO-LR Procedure, and its privacy profile allows its location to be shared with the Target UE.
Procedures for Ranging/Sidelink Positioning control (UE-only operation) defined in clause 6.8 applies with the following adaptations:
  • UE1 is the Target UE, and UEs 2..n are Located UEs.
  • Step 1, the service request from Target UE application layer indicates that absolute location of the Target UE is required
  • Before step 6, target UE sends a scheduled location time (Time T) to each Located UE. If the absolute location of Located UE is not known, 5GC-MO-LR procedure is triggered, as specified in clause 6.2 of TS 23.273, with the Time T included in the 5GC-MO-LR Request. The QoS requirement for Target UE's positioning in step 1, may be used by the Target UE to derive the required QoS for Located UE(s) positioning. Target UE sends the required QoS for Located UE positioning to each Located UE, and the required QoS for Located UE positioning is included in the 5GC-MO-LR Request.
  • Ranging/Sidelink positioning between target UE and each located UE is scheduled with the Time T.
  • Step 8 absolute location of the Target UE is calculated.
Up

Up   Top   ToC