Tech-
invite
3GPP
space
IETF
RFCs
SIP
Quick
21
22
23
24
25
26
27
28
29
31
32
33
34
35
36
37
38
4‑5x
Content for
TR 23.891
Word version: 9.0.0
1…
4…
4
Overall Requirements
5
Architectural Requirements and Considerations
6
Architectural Alternatives
7
Other Considerations
8
Comparison of Architectural Alternatives
9
Conclusions
$
Change history
4
Overall Requirements
4.1
Solution Characteristics
5
Architectural Requirements and Considerations
Word‑p. 8
5.1
Basic Assumptions
5.1.1
Types of Location Request
5.1.1.1
Immediate Location Request
5.1.1.2
Deferred Location Request
5.1.1.2.1
Types of event
5.2
Architectural Requirements
Word‑p. 9
5.3
Session Scenarios
Word‑p. 10
5.3.1
Mobile Terminating Location Request
5.3.2
Network Originating Location Request
5.3.3
Network Induced Location Request
6
Architectural Alternatives
6.1
Architectural Alternative #1
6.1.1
Objectives
6.1.2
Architectural Details
6.1.2.1
Architecture for NI-LR
6.1.2.2
Architecture for MT-LR and MO-LR
Word‑p. 11
6.1.2.3
Provision of MME Address to GMLC for an NI-LR
6.1.3
Information Flows and Protocols
Word‑p. 12
6.1.3.1
Location Support for IMS Emergency Calls
6.1.3.2
Location Procedure between the GMLC and E-SMLC
Word‑p. 13
6.1.3.3
Network Based Positioning Procedure
Word‑p. 15
6.1.3.4
UE Assisted and UE Based Positioning Procedure
Word‑p. 17
6.1.3.5
Location Continuity for Handover in the PS Domain
Word‑p. 18
6.1.3.5.1
Support of Intra E-UTRAN E-Node B Handover using X2 Interface
6.1.3.5.2
Support of Intra E-UTRAN E-Node B Handover using S1 Interface
Word‑p. 19
6.1.3.5.3
Variant 1: Target MME/SGSN notification of MME/SGSN Relocation
Word‑p. 20
6.1.3.5.4
Variant 2: Source MME/SGSN notification of MME/SGSN Relocation
Word‑p. 23
6.1.3.6
Location Continuity for Emergency Call Handover between PS and CS Domains
Word‑p. 26
6.1.3.7
MT-LR Procedure
6.1.3.8
Support of an MO-LR
Word‑p. 27
6.1.3.8.1
NAS Protocol Support
6.1.3.8.2
MO-LR Procedure
Word‑p. 28
6.1.4
Evaluation
6.2
Architectural Alternative #2
Word‑p. 29
6.2.1
Objectives
6.2.2
Architectural Details
6.2.2.1
Architecture for NI-LR
6.2.2.2
Architecture for MT-LR and MO-LR
Word‑p. 30
6.2.2.3
Provision of MME Address to GMLC for an NI-LR
6.2.3
Information Flows and Protocols
Word‑p. 31
6.2.3.1
Location Support for IMS Emergency Calls
6.2.3.2
Location Procedure between the GMLC, MME and E-SMLC
6.2.3.3
Network Based Positioning Procedure
Word‑p. 33
6.2.3.4
UE Assisted and UE Based Positioning Procedure
Word‑p. 34
6.2.3.5
Location Continuity for Handover in the PS Domain
Word‑p. 35
6.2.3.5.1
Support of Intra E-UTRAN E-Node B Handover using X2 Interface
6.2.3.5.2
Support of Intra E-UTRAN E-Node B Handover using S1 Interface
6.2.3.5.3
Variant 1: Target MME/SGSN notification of MME/SGSN Relocation
6.2.3.5.4
Variant 2: Source MME/SGSN notification of MME/SGSN Relocation
Word‑p. 36
6.2.3.6
Location Continuity for Emergency Call Handover between PS and CS Domains
Word‑p. 39
6.2.3.7
MT-LR Procedure
6.2.3.8
Support of an MO-LR
6.2.3.8.1
NAS Protocol Support
6.2.3.8.2
MO-LR Procedure
Word‑p. 40
6.2.4
Evaluation
6.2.5
User Plane interworking
Word‑p. 41
6.2.5.1
Objectives
6.2.5.2
Architectural Details
6.2.5.3
Information Flows and Protocols
Word‑p. 42
6.2.5.3.1
Network Based Positioning Procedure
6.3
Architectural Alternative #3
Word‑p. 43
6.3.1
Objectives
6.3.2
Architectural Details
6.3.2.1
Architecture for NI-LR
6.3.2.2
Architecture for MT-LR and MO-LR
6.3.2.3
Provision of MME Address to GMLC for an NI-LR
Word‑p. 44
6.3.3
Information Flows and Protocols
6.3.3.1
Location Support for IMS Emergency Calls
6.3.3.2
Location Procedure between the GMLC, MME, eNodeB and E-SMLC
6.3.3.3
Network Based Positioning Procedure
Word‑p. 46
6.3.3.4
UE Assisted and UE Based Positioning Procedure - Variant 1
Word‑p. 47
6.3.3.5
UE Assisted and UE Based Positioning Procedure - Variant 2
6.3.3.6
Location Continuity for Emergency Call Handover in the PS Domain
Word‑p. 48
6.3.3.7
Location Continuity for Emergency Call Handover between PS and CS Domains
Word‑p. 49
6.3.3.8
MT-LR Procedure
6.3.3.9
Support of an MO-LR
6.3.3.9.1
NAS Protocol Support
6.3.3.9.2
MO-LR Procedure
6.3.4
Evaluation
Word‑p. 50
6.4
Architectural Alternative #4
6.4.1
Objectives
6.4.2
Architectural Details
Word‑p. 51
6.4.3
Information Flows and Protocols
6.4.4
Evaluation
Word‑p. 52
6.5
Architectural Alternative #5
6.5.1
Objectives
6.5.2
Architectural Details
6.5.2.1
Architecture for NI-LR
6.5.2.2
Architecture for MT-LR and MO-LR
Word‑p. 53
6.5.2.3
Provision of MME Address to GMLC for an NI-LR
6.5.3
Information Flows and Protocols
Word‑p. 54
6.5.3.1
Location Support for IMS Emergency Calls
6.5.3.2
Location Procedure between the GMLC, MME and E-SMLC
6.5.3.3
MT-LR Network Based Positioning Procedure
Word‑p. 55
6.5.3.4
NI-LR Network Based Positioning Procedure
Word‑p. 56
6.5.3.5
UE Assisted and UE Based Positioning Procedure for emergency session positioning
Word‑p. 57
6.5.3.6
Location Continuity for Emergency Call Handover in the PS Domain
Word‑p. 58
6.5.3.6.1
Support of Intra E-UTRAN E-Node B Handover using X2 interface
6.5.3.6.2
Support of Intra E-UTRAN E-Node B Handover using S1 interface
6.5.3.6.3
Support of Intra E-UTRAN MME Relocation
6.5.3.6.4
UTRAN to E-UTRAN Relocation (Emergency Location Only)
6.5.3.6.5
E-UTRAN to UTRAN Relocation (Emergency Location Only)
6.5.3.6.6
Variant2: Source MME/SGSN notification of MME/SGSN Relocation
6.5.3.7
Location Continuity for Emergency Call Handover between PS and CS Domains
Word‑p. 59
6.5.3.8
MT-LR Procedure
6.5.3.9
Support of an MO-LR
6.5.3.9.1
NAS Protocol Support
6.5.3.9.2
MO-LR Procedure
6.5.4
Evaluation
Word‑p. 60
6.5.5
User Plane interworking
6.5.5.1
Objectives
6.5.5.2
Architectural Details
Word‑p. 61
6.5.5.3
Information Flows and Protocols
6.5.5.3.1
Network Based Positioning Procedure
7
Other Considerations
Word‑p. 62
7.1
QoS
7.2
Privacy
7.3
Lawful Intercept ion
7.4
Location Service Continuity between Radio Access Technologies
8
Comparison of Architectural Alternatives
9
Conclusions
Word‑p. 63
$
Change history
Word‑p. 64