Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TR 23.731  Word version:  16.0.0

Top   Top   Up   Prev   None
1…   5…

 

5  Key Issuesp. 13

5.1  Key Issue 1: Enhancement to LCS Architecturep. 13

5.2  Key Issue 2: Positioning via user plane transmissionp. 14

5.3  Key Issue 3: Support of low latency and high performance LCSp. 14

5.4  Key Issue 4: Reduce overhead for repetitive non-successful privacy verificationp. 15

5.5  Key Issue 5: Slicing dependent location servicep. 15

5.6  Key Issue 6: Scalabilityp. 16

5.7  Key Issue 7: Location service exposurep. 16

5.8  Key Issue 8: Support of IoT UEsp. 17

5.9  Key Issue 9: Support EUTRAN positioning methodsp. 17

5.10  Key Issue 10: Support NR positioning methodsp. 17

5.11  Key Issue 11: Coordination of Positioning Signalling Transmitted via Control Plane Path and User Plane Pathp. 17

5.12  Key Issue 12: LCS support for Non-3GPP accessp. 18

5.13  Key Issue 13: Support of Flexible and Efficient Periodic and Triggered Locationp. 18

5.14  Key Issue 14: Positioning Access selection for LCS servicep. 18

5.15  Key Issue 15: Location continuity supportp. 19

5.16  Key Issue 16: Distribution Positioning Assistance Datap. 19

6  Solutionsp. 20

6.1  Solution 1: 5GS LCS Functionality and Allocation to 5GS elements - Option 1 and Option 2p. 20

6.2  Solution 2: LMF Based Location Solutionp. 25

6.3  Solution 3: Enhancement to LCS architecturep. 52

6.4  Solution 4: Positioning operations considering different LMF deployment scenariosp. 54

6.5  Solution 5: Privacy Check with UE privacy settingp. 60

6.6  Solution 6: User Privacy Setting send via AMFp. 65

6.7  Solution 7: User Privacy Setting send via LMFp. 68

6.8  Solution 8: slice dependent LMF selectionp. 70

6.9  Solution 9: Solution for position service exposurep. 72

6.10  Solution 10: Solution for LDR type service exposure via NEFp. 78

6.11  Solution 11: Solution for Location Service exposure to NG-RANp. 84

6.12  Solution 12: LCS support for non-3GPP accessp. 85

6.13  Solution 13: LCS support for non-3GPP accessp. 89

6.14  Solution 14: Reuse R15 existing location service architecture for commercial use casesp. 97

6.15  Solution 15: Enhancement to LCS architecturep. 112

6.16  Solution 16: Solution for position via user plane transmissionp. 117

6.17  Solution 17: Solution for Flexible and Efficient Periodic and Triggered Locationp. 119

6.18  Solution #18: UDM based Positioning Access selection for LCS servicep. 122

6.19  Solution #19: Distribution of Positioning Assistance Informationp. 124

6.20  Solution 20: LMF selection in GMLCp. 128

6.21  Solution 21: Solution for Low Power Periodic and Triggered Locationp. 132

6.22  Solution 22: LCS continuity Support for N26 based Handoverp. 136

6.23  Solution #23: Unified NEF Location Service Exposurep. 140

6.24  Solution #24: GMLC based Positioning Access selection for LCS servicep. 146

6.25  Solution #25: Coordination of Positioning Signalling Transmitted via Control Plane Path and User Plane Pathp. 148

6.26  Solution 26: Local LCS architecturep. 149

6.27  Solution #27: Bulk operation of LCS service request targeting to multiple UEsp. 153

6.28  Solution #28: Enhanced NG-RAN to support high accuracy location estimationp. 156

7  Evaluationp. 158

8  Conclusionsp. 161

A  Supported positioning methodsp. 164

B  Evaluation tables for Key Issuesp. 167

$  Change Historyp. 170


Up   Top