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