Content for TR 23.700-96 Word version: 18.0.0
5 Key issues p. 9
5.1 Key issue #1: Architecture enhancement of application enablement for location p. 9
5.2 Key issue #2: Support of LCS QoS p. 10
5.3 Key issue #3: Location service differentiation p. 10
5.4 Void
5.5 Key issue #5: Initialization and configuration for fused location service p. 10
6 Void
7 Solutions p. 12
7.0 Mapping of solutions to key issues p. 12
7.1 Solution #1: Standalone functional architecture for fused location service p. 12
7.1.1 Solution description p. 12
7.1.1.1 Functional architecture p. 12
7.1.1.2 Functional components and reference points p. 13
7.1.1.3 Merged Architecture to support interaction between FLS and SEAL LMS p. 14
7.1.2 Solution evaluation p. 15
7.2 Solution #2: Support of both LCS and SUPL at Fused Location Function p. 15
7.3 Solution #3: Functional architecture for fused location service leveraging SEAL location management p. 16
7.3.1 Solution description p. 16
7.3.1.1 Functional architecture p. 16
7.3.1.2 Functional components and reference points p. 17
7.3.1.3 Deployment models p. 18
7.3.2 Solution evaluation p. 19
7.4 Solution #4: Location service registration p. 19
7.4.1 Solution description p. 19
7.4.2 Solution evaluation p. 20
7.5 Solution #5: Location profiling for supporting fused location service enablement p. 20
7.5.1 Solution description p. 20
7.5.1.1 General p. 20
7.5.1.2 Procedure p. 21
7.5.2 Solution evaluation p. 23
7.6 Solution #6: Location service configuration p. 23
7.6.1 Solution description p. 23
7.6.2 Solution evaluation p. 25
7.7 Solution #7: Location QoS based location sources and positioning methods selection p. 25
7.7.1 Solution description p. 25
7.7.2 Solution evaluation p. 26
7.8 Solution #8: Architecture for fused location service p. 27
8 Overall evaluation p. 28
9 Conclusions p. 31
$ Change history p. 34
