Tech-invite   3GPPspecs   RFCs   Search in Tech-invite

Gen21222324252627282931323334353637384‑5x
FsNEsRPsSBIsIDs Ti+
Top   in Index   Prev   Next

TR 23.744 (SA6) ☆ (Rel-16 draft)
Study on Location enhancements
for Mission Critical Services

use "3GPP‑Page" to get the Word version
for a better overview, the Table of Contents (ToC) is reproduced
V1.0.0 (Wzip)  2019/05  31 p.

Rapporteur:  Mr. Lazara, Dominic

The present document identifies the impact of location requirements from stage 1 that have yet to be realized within the stage 2 MC services architecture, and to propose solutions and enhancements where needed to fulfil these requirements.
Based on any gaps found between stage 1 service level requirements and existing MC location architecture, the present document consists of a technical report that includes: identification of key issues and gaps with the existing location architecture; associated solutions for enhancements to existing MC location architecture; and corresponding evaluations and conclusions.
The location enhancements considered in the present document are limited to MC services over EPS.

full Table of Contents for  TR 23.744  Word version:   1.0.0

this ToC is filtered in order to show the essential title levels only

 

Here   Top

 

1  ScopeWord-p. 7
2  ReferencesWord-p. 7
3  Definitions and abbreviationsWord-p. 8
4  Use casesWord-p. 8
4.1  Use case #1: Location information - TimestampWord-p. 8
4.2  Use case #2: Location information - Speed and bearingWord-p. 8
4.3  Use case #3: Location information - AccuracyWord-p. 8
4.4  Use case #4: Location information - AltitudeWord-p. 8
4.5  Use case #5: Location History ReportingWord-p. 9
4.6  Use case #6: Location triggering criteria for emergency stateWord-p. 9
4.7  Use case #7: Location information - individual receiving UEWord-p. 9
4.8  Use case #8: Location information - individual addressable UEWord-p. 9
4.9  Use case #9: Sharing of location informationWord-p. 9
4.10  Use case #10: Location information of unauthenticated userWord-p. 10
4.11  Use case #11: Location information in off-network operationWord-p. 10
5  Key IssuesWord-p. 10
5.1  Key Issue 1: Information in the location reportWord-p. 10
5.2  Key Issue 2: Location History ReportingWord-p. 11
5.3  Key Issue 3: Handling of triggering criteria in emergency casesWord-p. 11
5.4  Key Issue 4: Location mechanism compatibility for MCPTTWord-p. 11
5.5  Key Issue 5: Sharing of location informationWord-p. 12
5.6  Key Issue 6: Individual UE addressingWord-p. 12
5.7  Key Issue 7: Location information of unauthenticated userWord-p. 13
5.8  Key Issue 8: Location information in off-network operationWord-p. 13
6  SolutionsWord-p. 14
6.1  Solution 1: Additional details within the location information reportWord-p. 14
6.2  Solution 2: Additional details within the location information notificationWord-p. 15
6.3  Solution 3: Adjusting the location reporting procedureWord-p. 16
6.4  Solution 4: Handling of triggering criteria in emergency casesWord-p. 16
6.5  Solution 5: Location management mechanism backward compatibility for MCPTTWord-p. 19
6.6  Solution 6: Off-network storing of event-triggered location informationWord-p. 19
6.7  Solution 7: On-demand location history reportingWord-p. 20
6.8  Solution 8: Triggered location history reportingWord-p. 23
6.9  Solution 9: Adding a UE label to Initial MC service UE configurationWord-p. 24
6.10  Solution 10: Associate a user profile per MC service UEWord-p. 25
6.11  Solution 11: MC UE identity (new ID)Word-p. 25
6.12  Solution 12: Obtaining location of UE in "limited MC service" stateUpWord-p. 27
6.13  Solution 13: Sharing location information across MC service UEsWord-p. 27
7  Overall EvaluationWord-p. 31
8  ConclusionsWord-p. 31
A  Change historyWord-p. 31

Up   Top