hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.5.1 Description | |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.5.1.1 General | This solution addresses the key issue #4: Enhancement to support location information exposure.
After obtained different level UE location information from different sources, the LMS could statistic and calculate these UE location data per the temporal/spatial granularity and expose the value-added UE location data wit... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.5.1.2 Procedure of LMS supporting to expose value-added UE location data | Figure 6.5.1.2-1: Procedure of LMS supporting to expose value-added UE location data
1. The VAL server sends a location information subscription request to the location management server to subscribe location information of one or more VAL users or VAL UEs. The request may include the velocity information of target UEs... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.5.2 Solution evaluation | This solution addresses the key issue #4.
Based on this solution, the LMS could statistic and calculate the received UE location data per the temporal/spatial granularity and expose the value-added UE location data with different granularity (e.g., frequency) as well as additional information (e.g., velocity) to the VA... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.6 Solution #6: Reduce response time for LCS QoS | |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.6.1 Description | |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.6.1.1 General | This solution addresses the key issue #3: Location QoS improvement.
According to 3GPP TS 23.273 [5], the LCS Quality of Service is characterized by 3 key attributes: LCS QoS Class, Accuracy, and Response time. And this solution improves the LCS QoS mainly by reducing the response time.
The way how to reduce the respons... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.6.1.2 Procedure of LMS checking if the stored UE location data can be reused | Figure 6.6.1.2-1: Procedure of LMS checking if the stored UE location data can be reused
1. The VAL server may request the target UE location.
2. The LMS will check if there is stored and valid UE location data for the target UE. If yes, LMS will reuse the stored UE location information and report it to the VAL server ... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.6.2 Solution evaluation | This solution addresses the key issue #3 and improves the LCS QoS mainly by reducing the response time.
The LMS can reuse the stored UE location information to report to the VAL server to reduce the response time.
The impacted entities are LM servers. |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.7 Solution #7: Support for SL positioning/ranging enablement | |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.7.1 SL positioning management in SEAL LMS | This solution provides a mechanism for configuring and provisioning via application layer information on the entities to be used and their responsibilities for a ranging / SL positioning service. This solution assumes that the VAL UEs of different capabilities and potential roles (reference, target, client) have instan... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.7.2 Subscription for leveraging UE positioning and ranging operations | This procedure may follow the procedure in 6.7.1.
Figure 6.7.2-1: Support for leveraging UE positioning and ranging operations
1. The VAL server sends a subscription request to LMS to initiate ranging operation for the target and reference UEs. The request includes the client, target and reference UEs, the SL positioni... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.7.3 Solution evaluation | Solution #7 introduces an SL positioning management procedure which enables provisioning of UEs with SL ranging /positioning configuration information.
A complementary procedure enables VAL servers to subscribe to receive SEAL LMS notifications with information about UEs in the field of view of a target UE. This functi... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.8.1 General | The following clauses specify procedures, information flows and APIs for KI#5 to support new ADAE analytics on collision detection among UEs by using ranging/sidelink positioning information exposured from 5GC, the location information of devices from SEAL LM server, LM client, and/or 3rd party LM server.
Different fro... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.8.2 Procedure | Pre-conditions:
- Information about environment, e.g. static devices, are available from the 3rd party LM server.
- The location information about the UEs is available at SEAL LM server and/or LM client.
- The Ranging/Sidelink Positioning information exposure of the UEs is allowed at 5GC. |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.8.2.1 Subscribe-notify model | Figure 6.8.2.1-1: ADAES support for collision detection analytics
1. The analytics consumer (e.g. VAL Server, LM server, UAE server, UAS application specific server) sends analytics subscription request for collision detection analytics to ADAE server. The Analytics ID in the request message is set to "Collision detect... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.8.2.2 Request-response model | Pre-conditions:
- ADAE Server already have the analytics data derived from steps 3-6 in the procedure introduced in clause 6.8.2.1.
Figure 6.8.2.2-1: ADAES support for collision detection analytics
1. The analytics consumer (e.g. VAL Server, LM Server, UAE server, UAS application specific server) sends a request messag... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.8.3 Information flows | |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.8.3.1 General | The following information flows are specified for collision detection analytics based on clause 6.8.2. |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.8.3.2 Collision detection analytics subscription request | Table 6.8.3.2-1 describes the information flow from the consumer (e.g. VAL Server, LM Server, UAE server, UAS application specific server) as a request or update request for the collision detection analytics.
Table 6.8.3.2-1: Collision detection analytics subscription request
Information element
Status
Description
Requ... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.8.3.3 Collision detection analytics subscription response | Table 6.8.3.3-1 describes the information elements for the collision detection analytics subscription response from the ADAE server to the consumer.
Table 6.8.3.3-1: Collision detection analytics subscription response
Information element
Status
Description
Result
M
The result of the analytics subscription request (posi... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.8.3.4 Collision detection analytics notification | Table 6.8.3.4-1 describes the information flow from the ADAES to the consumer (e.g. VAL Server, LM Server, UAE server, UAS application specific server) as a response for the collision detection analytics.
Table 6.8.3.4-1: Collision detection analytics notification
Information element
Status
Description
Analytics ID
M
T... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.8.3.5 Ranging/SL positioning data and location information collection subscription request | Table 6.8.3.5-1 describes information elements for the Ranging/SL positioning data and location information collection subscription request from the ADAE server to the Data Producer, e.g. 5GC NFs (e.g. GMLC, NWDAF), ADAE Client, LM server, LM client, 3rd party LM server, A-ADRF for historical data.
Table 6.8.3.5-1: Dat... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.8.3.6 Ranging/SL positioning data and location information collection subscription response | Table 6.8.3.6-1 describes information elements for the Data collection subscription response from the Data Producer, e.g. 5GC NFs (e.g. GMLC, NWDAF), ADAE Client, LM server, LM client, 3rd party LM server, A-ADRF for historical data.
Table 6.8.3.6-1: Data collection subscription response
Information element
Status
Desc... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.8.3.7 Data Notification | Table 6.8.3.7-1 describes information elements for the Data Notification from the Data Producer to the ADAE server.
Table 6.8.3.7-1: Data notification
Information element
Status
Description
Data Collection Event ID
M
The identifier of the data collection event.
Data Producer ID
M
The identity of Data Producer.
Analytic... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.8.3.8 Get analytics data request | Table 6.8.3.8-1 describes information elements for the collision detection analytics request from the analytics consumer to the ADAE server.
Table 6.8.3.8-1: Get analytics data request
Information element
Status
Description
Requestor ID
M
The identifier of the consumer.
Analytics ID
O
The identifier of the analytics ev... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.8.3.9 Get analytics data response | Table 6.8.3.9-1 describes information elements for the Get collision detection analytics response from the ADAE server to the consumer.
Table 6.8.3.9-1: Get analytics response
Information element
Status
Description
Analytics ID
O
The identifier of the analytics event. This ID can be for example "Collision Detection ana... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.8.4 Solution evaluation | This solution addresses KI#5 about ranging information exposure to support application layer analytics on collision detection among UEs based on ranging/sidelink positioning information.
The impacted entities are VAL server, ADAE server and data producers (e.g. ADAE client, LM server).
6.9 Solution #9: New ADAE Analyti... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.9.1 General | The application enabler related to location should support to statistic the location information based on time/area domain and then expose them to the vertical applications. Also, predicted UE location exposure such as predicted time duration for UE(s) to stay in an area, expected UE group route prediction, UE group me... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.9.2 Procedure | Pre-conditions:
- The location information about the UEs is available at SEAL LM server.
- The location information of the UEs exposure is allowed at 5GC. |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.9.2.1 Subscribe-notify model | Figure 6.9.2.1-1: ADAES support for location-related UE group analytics
1. The analytics consumer (i.e. LMS) sends analytics subscription request for location-related UE group analytics to ADAE server. The Analytics ID in the request message is set to "UE(s) staying time duration analytics", "UE group route analytics",... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.9.2.2 Request-response model | Pre-conditions:
- ADAE Server already has the analytics data derived from steps 3-6 in the procedure introduced in clause 6.9.2.1.
Figure 6.9.2.2-1: ADAES support for location-related UE group analytics
1. The analytics consumer (i.e. LMS) sends a request message to the ADAE server to receive analytics data for locatio... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.9.3 Information flows | |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.9.3.1 General | The following information flows are specified for location-related UE group analytics based on clause 6.9.2. |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.9.3.2 Location-related UE group analytics subscription request | Table 6.9.3.2-1 describes the information flow from the consumer (LMS) as a request or update request for the location-related UE group analytics.
Table 6.X.3.2-1: Location-related UE group analytics subscription request
Information element
Status
Description
Requestor ID
M
(NOTE)
The identifier of the consumer.
Analyt... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.9.3.3 Location-related UE group analytics subscription response | Table 6.9.3.3-1 describes the information elements for the location-related UE group analytics subscription response from the ADAE server to the consumer.
Table 6.9.3.3-1: Location-related UE group analytics subscription response
Information element
Status
Description
Result
M
The result of the analytics subscription r... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.9.3.4 Location-related UE group analytics notification | Table 6.9.3.4-1 describes the information flow from the ADAES to the consumer (LM Server) as a response for the location-related UE group analytics.
Table 6.9.3.4-1: Location-related UE group analytics notification
Information element
Status
Description
Analytics ID
M
The identifier of the analytics event. This ID can ... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.9.3.5 Location information collection subscription request | Table 6.9.3.5-1 describes information elements for the Ranging/SL positioning data and location information collection subscription request from the ADAE server to the Data Producer, e.g. 5GC NFs (e.g. GMLC, NWDAF), ADAE Client, LM server, A-ADRF for historical data.
Table 6.9.3.5-1: Data collection subscription reques... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.9.3.6 Location information collection subscription response | Table 6.9.3.6-1 describes information elements for the Data collection subscription response from the Data Producer, e.g. 5GC NFs (e.g. GMLC, NWDAF), ADAE Client, LM server, A-ADRF for historical data.
Table 6.9.3.6-1: Data collection subscription response
Information element
Status
Description
Result
M
The result of t... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.9.3.7 Data Notification | Table 6.9.3.7-1 describes information elements for the Data Notification from the Data Producer to the ADAE server.
Table 6.9.3.7-1: Data notification
Information element
Status
Description
Data Collection Event ID
M
The identifier of the data collection event.
Data Producer ID
M
The identity of Data Producer.
Analytic... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.9.3.8 Get analytics data request | Table 6.9.3.8-1 describes information elements for the location-related UE group analytics request from the analytics consumer to the ADAE server.
Table 6.9.3.8-1: Get analytics data request
Information element
Status
Description
Requestor ID
M
The identifier of the consumer.
Analytics ID
M
The identifier of the analyt... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.9.3.9 Get analytics data response | Table 6.9.3.9-1 describes information elements for the Get location-related UE group analytics response from the ADAE server to the consumer.
Table 6.9.3.9-1: Get analytics response
Information element
Status
Description
Analytics ID
M
The identifier of the analytics event. This ID can be for example "UE(s) staying tim... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.9.4 Solution evaluation | This solution addresses the key issue #4 and introduces a new ADAE analytics on location-related UE group, e.g., statistics/predictions on time duration of UE(s) staying at an area, UE group route, UE density, and UE group member deviation. The solution supports location information exposure and the new analytics can b... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.10 Solution #10: Support location services for multiple USIMs/UEs that sharing the same location | |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.10.1 Description | |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.10.1.1 General | This solution addresses the key issue #6: Support of location services for multiple USIMs/UEs sharing the same location.
The solution is based on the following assumption and principles as depicted in figure 6.10.1.1-1:
- The VAL UE1 (i.e. mobile phone) and the VAL UE2 (i.e. iwatch) have separated USIM (i.e. USIM1 and ... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.10.1.2 Procedure of LMS identifying multiple UEs that sharing the same location data | The procedure is applicable to the UEs belonging to same user or different users.
Pre-condition:
1) SEAL LMC-1 (in UE-1) can connect to SEAL LMC-2 (in UE-2) to receive location reports.
2) VAL UE1 and VAL UE2 may belong to the same user or different users.
NOTE 1: Both UE-1 and UE-2 are connected to the access network ... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.10.1.3 Procedure of LMS select the proper UE among multiple UEs to obtain the UE location data | Pre-condition:
- The VAL server is aware of VAL UE1 and VAL UE2 and their associated ID (e.g. group ID).
Figure 6.10.1.3-1: Procedure of LMS select the proper UE among multiple UEs to obtain the UE location data
1. The VAL UE1 and VAL UE2 have registered their location capabilities to the LMS as the Step 1~4 of clause ... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.10.2 Solution evaluation | This solution addresses the key issue #6 to support the location services for multiple USIMs/UEs that sharing the same location.
Based on this solution, the LMS could identify which UEs are associated via the associated ID and verify if they share the same location information via the sharing location indicator reporte... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.11 Solution #11: Support for adaptive location configuration and reporting | |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.11.1 Architecture Impacts | This solution is based on architecture of SEAL as described in 3GPP TS 23.434 [9]. |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.11.2 Solution description | The typical reporting configuration for location services includes the reporting type (e.g., periodic or event-triggered), the reporting periodicity for the periodic reporting and trigging events for the event triggered reporting.
The typical reporting configuration require the application to foresee the required situa... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.11.2.1 Impact to existing SEAL location management procedures | The SEAL procedures and information flows in 3GPP TS 23.434 [9] can be enhanced (highlighted in bold italics) as follows.
9.3.2.4 Location reporting trigger
Table 9.3.2.4-1 describes the information flow from the location management client or VAL server to the location management server for triggering a location report... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.11.2.2 SEAL location management server provides adaptive configuration | Figure 6.11.2.2-1 illustrates procedure for SEAL LMS to provide adaptive location configuration suggestion to the VAL server for the VAL UE for which VAL server has requested for adaptive reporting (as specified in above clause).
NOTE 1: The procedure is applicable to SEAL LMC-2 (as specified in above clause 9.3.5) if ... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.11.3 Solution evaluation | This solution addresses KI#4 about whether and how to expose the location data information per the e.g. time/area/space granularity in application enabled layer.
This solution proposes enhancements to the SEAL Location Management service to provide the assistance to the VAL server in the location reporting configuratio... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.12 Solution #12: Verify UE location | |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.12.1 Description | This solution addresses the key issue #4: Enhancement to support location information exposure. Verify UE location could be used by multiple applications that need confirmed location to provide their service. The UE application logic would first confirm customer location before accepting customer requests for service i... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.12.2 Procedures | |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.12.2.1 Confirm location service subscription | The application is running on a VAL server. The application would like to use confirm location service and subscribes to LMS for it using the following procedure:
Figure 6.12.2.1-1: Procedure of confirm location service subscription
1. The VAL server subscribes to LMS to receive notification every time UE using specifi... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.12.2.2 Confirm location verification | The location management client (LMC)/application in the UE gets from non-3GPP positioning (e.g. GNSS) in the UE its location. The application in the UE wants to check if this is really the correct location.
Pre-conditions:
1. The LMC is authorized to discover and to use Confirm Location API provided by the LMS;
2. LMS ... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.12.3 Information flows | |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.12.3.1 General | The following information flows are specified for confirm location service based on clause 6.12.2. |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.12.3.2 Confirm location service subscription request | Table 6.12.3.2-1 describes the information elements for the confirm location service subscription request from the VAL Server towards the location management server.
Table 6.12.3.2-1: Confirm location service subscription request
Information element
Status
Description
Identity
M
Identity of the requesting VAL server/VA... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.12.3.3 Confirm location service subscription response | Table 6.12.3.3-1 describes the information elements for the confirm location service subscription response from the location management server to the VAL Server.
Table 6.12.3.3-1: Confirm location service subscription response
Information element
Status
Description
Identity
M
Identity of the requesting VAL server/VAL u... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.12.3.4 Confirm location request | Table 6.12.3.4-1 describes the information elements for the confirm location request from the location management client to the location management server.
Table 6.12.3.4-1: Confirm location request
Information element
Status
Description
UE ID
M
The identifier of UE whose location information is to be confirmed
UE prov... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.12.3.5 Confirm location report | Table 6.12.3.5-1 describes the information elements for the confirm location request from the location management server to the location management client.
Table 6.12.3.5-1: Confirm location report
Information element
Status
Description
UE ID
M
The identifier of UE whose location information is to be confirmed
Confirm ... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.12.3.6 Confirm location service usage notification | Table 6.12.3.6-1 describes the information elements for the confirm location service usage notification from the location management server to the VAL server.
Table 6.12.3.6-1: Confirm location service usage notification
Information element
Status
Description
Identity
M
Identity of the requesting VAL server/VAL user
UE... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.12.4 Solution evaluation | This solution addresses KI#4 about whether and how to expose the location data information per the e.g. area/space granularity in application enabled layer.
This solution proposes enhancements to the SEAL Location Management service to provide the VAL server application with subscription for verification service and su... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 7 Overall Evaluation | |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 7.1 General evaluation | The following clauses contain an overall evaluation for all of the solutions presented in this technical report, including their applicability to the identified key issues and possible dependencies to other groups. |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 7.2 Solution evaluation | |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 7.2.1 General | All of the key issues and their corresponding solutions specified in this technical report are listed in Table 7.2.1-1. This table includes the mapping of the key issues to the solutions, and possible dependencies to other groups.
Table 7.2.1-1 Key issues and solutions
Key issues
Solution
Dependency on other working gr... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 7.2.2 Overall evaluation of key issue#1 | The KI#1 mainly studies the following open issues:
1) How to provision/update/revoke the Geofencing services.
2) How to trigger the location alert or push notification to VAL UEs/users.
3) How to provide more UE status in Geofencing service.
4) How to support dynamic Geofencing.
5) How to support the above identified f... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 7.2.3 Overall evaluation of key issue#2 | The KI#2 mainly studies the following open issues:
1) How to provision/update/revoke the history tracing request/playback service.
2) Whether and how the existing application enablers support the above functions.
Solution #3 addresses KI#2 and provides the location history tracing query based on current SEAL-LM archite... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 7.2.4 Overall evaluation of key issue#3 | The open issue for KI#3 includes:
1) How to provide more accurate UE location reports and/or reduce the service latency (service response time) to VAL server utilizing the existing positioning methods.
2) How to improve the LCS QoS based on the procedures and functions as defined in the current SEAL-LM architecture and... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 7.2.5 Overall evaluation of key issue#4 | The KI#4 mainly studies the following open issues:
1) Whether and how to expose the location data information per the e.g. time/area/space granularity in application enabled layer.
2) Whether and how to expose the location data in one area of interest with additional parameters from the requirements of the VAL server, ... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 7.2.6 Overall evaluation of key issue#5 | The open issue for KI#5 includes:
1) How to support the selection and configuration of VAL UEs acting as reference UEs
2) Whether and how the enabler layer can support exposing ranging information to 3rd party consumers
There are two solutions that address the above open issues for KI#5.
Solution #7 introduces an SL ra... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 7.2.7 Overall evaluation of key issue#6 | The open issue for KI#6 includes:
1) How to identify the multiple UEs with standalone USIMs could share the same location data in the application enabled layer.
2) How to select the proper UE among multiple UEs to obtain the UE location data to expose to the VAL server.
3) Whether and how the existing application enabl... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 8 Conclusions | |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 8.1 General conclusions | This technical report fulfils the objectives of the study on enhanced application layer support for location services.
The report main includes the following contents:
1. Definition of terms and abbreviations used in the study (clause 3);
2. Architectural assumption and requirements (clause 4);
3. Key issues identified... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 8.2 Conclusions of key issues | The following is sub-conclusion for each key issue based on the solution evaluation in clause 7.2 which can be considered for the normative work. |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 8.2.1 Conclusions of KI#1 | Solution #2 and Solution#4 addressing the KI#1 can be considered in the normative work to realize the different functions. The related function and procedure will be specified in 3GPP TS 23.434 [9] to support the two solutions, and the detailed APIs and information flows can be discussed in the normative phase. |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 8.2.2 Conclusions of KI#2 | Solution #3 addressing the KI#2 can be considered in the normative work. Whether the procedure of location history tracing service can reuse the current SEAL-LM procedure will be determined in normative phase. And the detailed APIs and information flows can also be discussed in the normative phase. |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 8.2.3 Conclusions of KI#3 | Solution #1 and Solution#6 addressing the KI#3 can be considered in the normative work. The related function and procedure will be specified in 3GPP TS 23.434 [9] to support both of solutions, and the detailed APIs and information flows can be discussed in the normative phase. |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 8.2.4 Conclusions of KI#4 | Solution #5, #9, #11 and #12 addressing the KI#4 can be considered in the normative work to realize the different functions for SEAL-LM enabler and ADAE enabler seperately. The related function and procedure will be specified in 3GPP TS 23.434 [9] and 3GPP TS 23.436 [15] to support the solutions, the detailed APIs and ... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 8.2.5 Conclusions of KI#5 | Solution #7 and Solution#8 addressing the KI#5 can be considered in the normative work. The difference is the Solution#7 is based on the SEAL-LM architecture and the Solution#8 is based on the ADAE architecture.The related function and procedure will be specified in 3GPP TS 23.434 [9] and 3GPP TS 23.436 [15] to support... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 8.2.6 Conclusions of KI#6 | Solution #10 addressing the KI#6 can be considered in the normative work. The related function and procedure will be specified in 3GPP TS 23.434 [9] to support the solution. And the detailed APIs and information flows can be discussed in the normative phase. Annex A: Change history Change history Date Meeting TDoc CR R... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 1 Scope | The scope of this Technical Report is to study solutions addressing MPS priority for SMS and MPS priority for messaging services based on IMS within the 3GPP system. For IMS, the scope is limited to MPS priority by the 3GPP system when SIP is used to support the messaging service.
The study will investigate the followi... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- Fo... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 3 Definitions of terms and abbreviations | |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 3.1 Terms | For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
MPS for messaging service: Any of the following network supported messaging technologies delivered w... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
DRMP Diameter Routing Message Priority
DTS Data Transport Service
MPS Multi... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 4 Architectural Assumptions and Requirements | - Solutions shall build on the EPS, 5GS, and IMS architectures as in TS 23.204 [3], TS 23.228 [4], TS 23.401 [6], TS 23.501 [7], TS 23.502 [8], TS 23.040 [2], Annex C of TS 23.272 [5], TS 23.540 [9].
- Solutions for MPS priority for messaging via WLAN are based on existing MPS support for Non-3GPP WLAN.
- MPS priority ... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 5 Key Issues | |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 5.1 Key Issue 1: MPS Priority support for Messaging over IMS | |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 5.1.1 General description | This key issue investigates needed enhancements to support MPS priority for Messaging over IMS. A UE with MPS for messaging activated, will receive priority treatment in the presence of overload or congestion in IMS, EPS or 5GS for:
- Immediate Messaging as defined in clause 5.16.1 of TS 23.228 [4]; and
- Session-based... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 5.2 Key Issue 2: Priority support for SMS over IP based on MPS subscription | |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 5.2.1 General description | This key issue investigates needed enhancements to support priority handling for SMS over IP based on the UE's MPS subscription. A UE with MPS for messaging will receive priority treatment in the presence of overload or congestion in EPS or 5GS for:
- mobile originated SMS over IP from the UE; and
- mobile terminated S... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 5.3 Key Issue 3: Priority support for SMS over NAS based on MPS subscription | |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 5.3.1 General description | This key issue investigates needed enhancements to support priority handling for SMS over NAS based on the UE's MPS subscription. A UE with MPS for messaging will receive priority treatment in the presence of overload or congestion in EPS or 5GS for:
- mobile originated SMS over NAS from the UE; and
- mobile terminated... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.