Tech-invite  3GPPspace  IETFspace
◀  ▶  21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x
Top   in Index   Prev   Next

TR 23.744
Study on Location enhancements
for Mission Critical Services

3GPP‑Page   fToC↓   Partial Content →
V17.1.0 (Wzip)  2020/09  53 p.
Rapporteur:
Mr. Negalaguli, Harish
Motorola Solutions UK Ltd.

full Table of Contents for  TR 23.744  Word version:  17.1.0

each clause number in 'red' refers to the equivalent title in the Partial Content
Here   Top
0Introduction  p. 6
1Scope  p. 7
2References  p. 7
3Definitions and abbreviations  p. 8
3.1Definitions  p. 8
3.2Abbreviations  p. 8
4Use cases  p. 8
4.1Use case #1: Location information - Timestamp  p. 8
4.2Use case #2: Location information - Speed and bearing  p. 8
4.3Use case #3: Location information - Accuracy  p. 8
4.4Use case #4: Location information - Altitude  p. 8
4.5Use case #5: Location History Reporting  p. 9
4.6Use case #6: Location triggering criteria for emergency state  p. 9
4.7Use case #7: Location information - individual receiving UE  p. 9
4.8Use case #8: Location information - individual addressable UE  p. 9
4.9Use case #9: Sharing of location information  p. 9
4.10Use case #10: Location information of unauthenticated user  p. 10
4.11Use case #11: Location information in off-network operation  p. 10
4.12Use case #12: Sharing of past location information  p. 10
4.13Use case #13: Location sharing and temporary location configuration between interconnected MC systems  p. 10
5Key Issues  p. 11
5.1Key Issue 1: Information in the location report  p. 11
5.1.1Description  p. 11
5.1.2Architectural Requirements  p. 11
5.2Key Issue 2: Location History Reporting  p. 11
5.2.1Description  p. 11
5.2.2Architectural Requirements  p. 11
5.3Key Issue 3: Handling of triggering criteria in emergency cases  p. 11
5.3.1Description  p. 11
5.4Key Issue 4: Location mechanism compatibility for MCPTT  p. 11
5.4.1Description  p. 11
5.4.2Architectural Requirements  p. 12
5.5Key Issue 5: Sharing of location information  p. 12
5.5.1Description  p. 12
5.5.2Architectural Requirements  p. 13
5.6Key Issue 6: Individual UE addressing  p. 13
5.6.1Description  p. 13
5.6.2Architectural Requirements  p. 13
5.7Key Issue 7: Location information of unauthenticated user  p. 13
5.7.1Description  p. 13
5.7.2Architectural Requirements  p. 14
5.8Key Issue 8: Location information in off-network operation  p. 14
5.8.1Description  p. 14
5.9Key Issue 9: Sharing of past location information  p. 14
5.9.1Description  p. 14
5.9.2Architectural Requirements  p. 14
6Solutions  p. 15
6.1Solution 1: Additional details within the location information report  p. 15
6.1.1Description  p. 15
6.1.2Impacts on existing nodes and functionality  p. 15
6.1.2.1Location information report  p. 15
6.1.3Solution Evaluation  p. 16
6.2Solution 2: Additional details within the location information notification  p. 16
6.2.1Description  p. 16
6.2.2Impacts on existing nodes and functionality  p. 16
6.2.2.1Location information notification  p. 16
6.2.3Solution Evaluation  p. 17
6.3Solution 3: Adjusting the location reporting procedure  p. 17
6.3.1Description  p. 17
6.3.2Impacts on existing nodes and functionality  p. 17
6.3.2.1Event-triggered location reporting procedure  p. 17
6.3.3Solution Evaluation  p. 17
6.4Solution 4: Handling of triggering criteria in emergency cases  p. 17
6.4.1Description  p. 17
6.4.2Impacts on existing nodes and functionality  p. 18
6.4.2.1Location reporting configuration  p. 18
6.4.2.2Location reporting trigger  p. 19
6.4.3Solution Evaluation  p. 19
6.5Solution 5: Location management mechanism backward compatibility for MCPTT  p. 20
6.5.1Description  p. 20
6.5.2Impacts on existing nodes and functionality  p. 20
6.5.3Solution Evaluation  p. 20
6.6Solution 6: Off-network storing of event-triggered location information  p. 20
6.6.1Description  p. 20
6.6.2Impacts on existing nodes and functionality  p. 20
6.6.2.1Off-network storing of event-triggered location information procedure  p. 20
6.6.3Solution Evaluation  p. 21
6.7Solution 7: On-demand location history reporting  p. 22
6.7.1Description  p. 22
6.7.2Impacts on existing nodes and functionality  p. 22
6.7.2.1Location information history request  p. 22
6.7.2.2On-demand location history reporting procedure  p. 22
6.7.2.3Location information report  p. 23
6.7.3Solution Evaluation  p. 24
6.8Solution 8: Triggered location history reporting  p. 24
6.8.1Description  p. 24
6.8.2Impacts on existing nodes and functionality  p. 24
6.8.2.1Triggered location history reporting procedure  p. 24
6.8.2.2Location information report  p. 25
6.8.3Solution Evaluation  p. 25
6.9Solution 9: Adding a UE label to Initial MC service UE configuration  p. 25
6.9.1Description  p. 25
6.9.2Impacts on existing nodes and functionality  p. 26
6.9.3Solution Evaluation  p. 26
6.10Solution 10: Associate a user profile per MC service UE  p. 26
6.10.1Description  p. 26
6.10.2Impacts on existing nodes and functionality  p. 26
6.10.3Solution Evaluation  p. 26
6.11Solution 11: MC UE identity (new ID)  p. 27
6.11.1Description  p. 27
6.11.2Impacts on existing nodes and functionality  p. 27
6.11.2.1MC UE ID part of location information report  p. 27
6.11.2.2MC UE ID part of location information request  p. 27
6.11.2.3Definition  p. 27
6.11.2.4MC service UE configuration data  p. 28
6.11.3Solution Evaluation  p. 28
6.12Solution 12: Obtaining location of UE in "limited MC service" state  p. 28
6.12.1Description  p. 28
6.12.2Impacts on existing nodes and functionality  p. 28
6.13Solution 13: Sharing location information across MC service UEs  p. 28
6.13.1Description  p. 28
6.13.2Impacts on existing nodes and functionality  p. 28
6.13.2.1Location information client subscription request  p. 29
6.13.2.2Location information client subscription response  p. 29
6.13.2.3Location information client notification  p. 29
6.13.2.4Location information client subscription procedure  p. 29
6.13.2.5Event-triggered location information notification procedure  p. 30
6.13.2.6On-demand request of location information procedure  p. 31
6.13.3Solution Evaluation  p. 31
6.14Solution 14: Functional model for sharing location information across MC systems  p. 32
6.14.1Description  p. 32
6.14.2Impacts on existing nodes and functionality  p. 32
6.14.2.1On-network functional model  p. 32
6.14.2.2Reference point CSC-23 (between location management servers in different MC systems)  p. 33
6.14.2.3Reference point CSC-22 (between location management server and MC gateway server)  p. 33
6.14.2.4Reference point CSC-21 (between MC gateway servers in different MC systems)  p. 34
6.14.2.5Information flows  p. 34
6.14.3Solution Evaluation  p. 34
6.15Solution 15: Sharing location information for interconnected MC system  p. 34
6.15.1Description  p. 34
6.15.2Impacts on existing nodes and functionality  p. 34
6.15.2.1General  p. 34
6.15.2.2Location information subscription request  p. 34
6.15.2.3Location information subscription response  p. 35
6.15.2.4Location information notification  p. 35
6.15.2.5Location information subscription procedure  p. 35
6.15.2.6Event-triggered location information notification procedure  p. 36
6.15.2.7Location information request  p. 37
6.15.2.8Location information report  p. 37
6.15.2.9On-demand request of location information procedure  p. 38
6.15.2.10Authorization to share location information  p. 39
6.15.2.11Location information cancel subscription request  p. 39
6.15.2.12Location information cancel subscription response  p. 40
6.15.2.13Location information cancel subscription procedure  p. 40
6.15.2.14Location reporting temporary configuration request  p. 41
6.15.2.15Location reporting temporary configuration response  p. 41
6.15.2.16Location reporting temporary configuration procedure  p. 41
6.15.3Solution Evaluation  p. 42
6.16Solution 16: Sharing of past location information  p. 43
6.16.1Description  p. 43
6.16.2Impacts on existing nodes and functionality  p. 43
6.16.2.1Location information request  p. 43
6.16.2.2Providing past location information from the location management server  p. 43
6.16.2.3Identifying past location information  p. 44
6.16.2.4Time period to retain past location information  p. 44
6.16.2.5Authorization to request past location information  p. 44
6.16.3Solution Evaluation  p. 45
6.17Solution 17: Location information in off-network mode operation  p. 45
6.17.1Description  p. 45
6.17.2Impacts on existing nodes and functionality  p. 45
6.17.2.1Location information report (off-network mode)  p. 45
6.17.2.2Location information report procedure (off-network mode)  p. 46
6.17.2.3Location information request (off-network mode)  p. 46
6.17.2.4Location information request procedure (off-network mode)  p. 46
6.17.3Solution Evaluation  p. 47
7Overall Evaluation  p. 47
7.1General  p. 47
7.2Solution evaluation  p. 47
7.3Key issues with security implications  p. 52
8Conclusions  p. 52
$Change history  p. 53

Up   Top