hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.24.1 Procedure of SL positioning /ranging management service
|
The procedure provides a mechanism for configuring and provisioning information on the entities to be used and their responsibilities for a SL positioning / ranging service. In this procedure, an SL positioning enabler capability at LMS is authorized / delegated by SL positioning server to support the provisioning/delivery of ranging services in an area.
Figure 9.3.24.1-1 shows a high-level procedure with the details.
Figure 9.3.24.1-1: Support for SL positioning procedure
1. The VAL server (SL Positioning / Ranging Server) sends an SL positioning management subscription request to SEAL LMS to provision and manage SL positioning / ranging operation and configurations.
2. The SEAL LMS authorizes the VAL subscription request.
3. The SEAL LMS sends an SL positioning management subscription response to the requestor VAL Server.
4. The SEAL LMS discovers all the SEAL LMCs in the target service area, and categorizes them by their capabilities as target UE, Reference UEs, or even Located UEs (if Reference UE location is known or for out of coverage scenarios). The identification of UEs in a target area happens via existing SEAL LMS procedures (as in clauses 9.3.10 and 9.3.12).
5. The SEAL LMS after getting all UE information at the target area, calculates the relative distances among them, and may request/receive HDMaps (e.g., from other VAL servers) for the target area.
Then, SEAL LMS evaluates the need of reference UE (based the information in step 4), and if reference UE is needed (e.g. in NLoS situation), the SEAL LMS selects the appropriate VAL UE to serve as reference and configures the VAL UEs (target, reference, client) with configuration information (thresholds, reporting configurations).
The LMS may also leverage analytics services (e.g. NWDAF) to obtain VAL UE location related predictions (e.g. UE location prediction, relative distance prediction) to discover reference UEs.
NOTE: The selection of UE as reference UEs can be based on their capabilities and the selection criteria specified by the VAL server.
6. The SEAL LMS sends a SL positioning management notify message to the VAL server to indicate the roles of the VAL UEs and acknowledging that the SL positioning provisioning is performed.
7. The SEAL LMS configures the SEAL LMCs with the configuration information applicable to the corresponding VAL UEs based on step 5, and in particular the expected role (acting as reference UE, target UE) in relation ranging/SL positioning service. Based on this configuration, the LM clients interacts each other using off-network location management procedures as described in clause 9.5.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.25 Short-Range based positioning information
|
Figure 9.3.25-1 describes a procedure to expose Short-Range based positioning information to third parties.
Pre-condition:
1. Target and reference UEs are configured and provisioned for SL positioning management service as described in clause 9.3.24.
Figure 9.3.25-1: Short-Range based positioning information procedure
1. A VAL server sends a Short-Range based positioning information request to SEAL LMS to initiate ranging/SL positioning operation for target and reference UEs. The request includes the VAL service identifier, the reference UE list (client, target and reference UEs), the requested Short-Range based positioning information (e.g. range, direction, relative position, relative velocity, etc.), reporting events, QoS requirement, and expiration of the Short-Range based positioning information request.
2. The SEAL LMS sends a request to the Client UE to initiate the Short-Range based positioning information procedure between the target and reference UEs using the information provided in step 1.
3. The Client UE initiates the Ranging/SL positioning operation as described in 3GPP TS 23.586 [57] or in off network location reporting as specified in clause 9.5. Either UE-only operation or Network-based operation is performed when using procedure in 3GPP TS 23.586 [57].
4. The Client UE sends the Short-Range based positioning information results to the SEAL LMS, which uses the Short-Range based positioning information results to derive a field of view for the target UE. The SEAL LMS uses the range and direction between the target UE and reference UEs to determine UEs that are within a field of view of the target UE.
5. The SEAL LMS sends a response to the VAL server with the requested Short-Range based positioning information and exposes location information of UEs within a field of view of the target UE.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.26 Verify UE location procedure
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.26.1 General
|
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 in a specific location.
This procedure provides the VAL server application with subscription for verification service and supports verification of UE provided location by the LMS. Only UEs using application with such subscription can use the confirm location verification from LMS. Sharing of UE location to the network is only possible with user consent. The network provided location is not directly shared but only verification is provided to the requesting LM client. The verified location is for internal UE usage.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.26.2 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 9.3.26.2-1: Procedure of confirm location service subscription
1. The VAL server subscribes to LMS to receive notification every time UE using specific application is requesting confirmation of location.
2. The LMS shall check if the VAL server is authorized to subscribe for the confirm location service notifications for a specific application identifier.
3. If the VAL server and specific application are authorized to subscribe for confirm location service, the LMS creates subscription based on provided parameters in the request.
4. The LMS sends to VAL server confirm location service subscription response.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.26.3 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 is authorized to use Nnef Event Exposure API, based on SLA with NEF/5GS of MNO;
3. It is assumed there is user consent given in the UE for exposing location information from UE to LMS.
Figure 9.3.26.3-1: Procedure of confirm location verification
1. The UE sends Confirm Location request from the LMC towards LMS. It contains the location measured from the UE (non-3GPP location information, e.g. GNSS). It contains latitude and longitude, accuracy, timestamp, carrier name, cell id (known to the UE from the network signalling), application identifier.
2. The LMS shall check if there is subscription (based on VAL subscription in clause 6.12.2.1) for confirm location service with the specific application identifier received in step1. If subscription is present, step 3 is performed. If subscription is not present the LMS replies back to LMC with confirm location status unknown (step 4).
3. LMS requests UE location from 5GC/LMF via NEF (LMS send determine Location operation via NEF (N33 interface) and using Nlmf_Location API defined in 3GPP TS 29.572 [8] – parameters available from the location reporting are described in the TS). It also requests accuracy to be a parameter present in the response. LMS can also perform a location information request to GMLC directly or via NEF (as defined in 6.1. of 3GPP TS 23.273 [5]), acting as AF. LMS can also perform a location information request to 3rd party location servers via LM-3P interface. LMS can also use the T8 interface to obtain UE location. Or the LMS can have already the UE location based on the methods described in 3GPP TS 23.434 [9]. The received response contains the UE location from the network. LMS compares the location provided from the network with the location provided from the LMC. LMS can use event exposure using NEF according to table 4.15.3.1-1 of TS 23.502 to obtain user location information from AMF.
4. LMS sends confirm location report to LMC.
5. The LMS sends notification towards the VAL server with the UE identifier and application using the service.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4 SEAL APIs for location management
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.1 General
|
Table 9.4.1-1 illustrates the SEAL APIs for location management.
Table 9.4.1-1: List of SEAL APIs for location management
API Name
API Operations
Known Consumer(s)
Communication Type
SS_LocationReporting
Create_Trigger_Location_Reporting
Update_Trigger_Location_Reporting
Cancel_Trigger_Location_Reporting
Notify_Trigger_Location_Reporting
Notify_Adaptive_Configuration
VAL server
Subscribe/Notify
SS_LocationInfoEvent
Subscribe_Location_Info
VAL server
Subscribe/Notify
Unsubscribe_Location_Info
VAL server
Update_Location_Info_Subscription
VAL server
Notifiy_Location_Info
VAL server
SS_LocationInfoRetrieval
Obtain_Location_Info
VAL server
Request /Response
SS_LocationAreaInfoRetrieval
Obtain_UEs_Info
VAL server
Request/Response
SS_LocationMonitoring
Subscribe_Location_Monitoring
VAL server
Subscribe/Notify
Unsubscribe_Location_Monitoring
VAL server
Update_Location_Monitoring_Subscription
VAL server
Notify_Location_Monitoring_Events
VAL server
Subscribe_Location_Area_Monitoring
VAL server
Subscribe/Notify
Notify_Location_Area_Monitoring_Events
Update_Location_Area_Monitoring_Subscribe
Unsubscribe_Location_Area_Monitoring
SS_VALServiceAreaConfiguration
Configure_VAL_Service_Area
VAL server
Request/Response
Obtain_VAL_Service_Area
VAL server
Update_VAL_Service_Area
VAL server
Delete_VAL_Service_Area
VAL server
Subscribe_VAL_Service_Area_Change_Event
SEAL server
Subscribe/Notify
Notify_VAL_Service_Area_Change_Event
SEAL server
Unsubscribe_VAL_Service_Area_Change_Event
SEAL server
Update_Subscription_VAL_Service_Area_Change_Event
SEAL server
SS_LocationHistoryInfoEvent
Create_Location_Tracing_Configuration
VAL server
Request/Response
Update_Location_Tracing_Configuration
VAL server
Delete_Location_Tracing_Configuration
VAL server
Obtain_history_Location_Info
VAL server
SS_SLPositioningManagement
Subscribe_SLPositioningManagement
VAL server
Subscribe/Notify
Notify_SLPositioningManagement
VAL server
SS_SRPositioningInformation
SR_Positioning_Information
VAL server
Request/Response
SS_ConfirmLocation
Confirm_Location
LMC
Request/Response
ConfirmLocationServiceSubscription
VAL server
Request/Response
Notify_ConfirmLocationServiceUsage (NOTE)
VAL server
Subscribe/Notify
NOTE: The subscribe operation is part of ConfirmLocationServiceSubscription
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.2 SS_LocationReporting API
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.2.1 General
|
API description: This API enables the VAL server to trigger reporting of location information to the location management server over LM-S.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.2.2 Create_Trigger_Location_Reporting operation
|
API operation name: Create_Trigger_Location_Reporting
Description: Creates the trigger to report location information.
Known Consumers: VAL server.
Inputs: Refer subclause 9.3.2.4
Outputs: Refer subclause 9.3.2.4
See subclause 9.3.5 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.2.3 Update_Trigger_Location_Reporting operation
|
API operation name: Update_Trigger_Location_Reporting
Description: Updates the trigger to report location information.
Known Consumers: VAL server.
Inputs: Refer subclause 9.3.2.4
Outputs: Refer subclause 9.3.2.4
See subclause 9.3.5 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.2.4 Cancel_Trigger_Location_Reporting operation
|
API operation name: Cancel_Trigger_Location_Reporting
Description: Cancels the trigger to report location information.
Known Consumers: VAL server.
Inputs: Refer subclause 9.3.2.8
Outputs: Refer subclause 9.3.2.25
See subclause 9.3.6 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.2.5 Notify_Trigger_Location_Reporting operation
|
API operation name: Notify_Trigger_Location_Reporting
Description: Notification for location report based on the location trigger.
Known Consumers: VAL server.
Inputs: Refer subclause 9.3.2.7
Outputs: None
See subclause 9.3.5 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.2.6 Notify_Adaptive_Configuration operation
|
API operation name: Notify_Adaptive_Configuration
Description: Provisioning of the adaptive location configuration.
Known Consumers: VAL server.
Inputs: Refer subclause 9.3.2.47
Outputs: Refer subclause 9.3.2.48
See subclause 9.3.20 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.3 SS_LocationInfoEvent API
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.3.1 General
|
API description: This API enables the VAL server to subscribe, receive and unsubscribe the UEs location information from the location management server over LM-S, as well as modify an active subscription.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.3.2 Subscribe_Location_Info operation
|
API operation name: Subscribe_Location_Info
Description: Subscription to the location information.
Known Consumers: VAL server.
Inputs: Refer subclause 9.3.2.5
Outputs: Refer subclause 9.3.2.6
See subclause 9.3.7 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.3.3 Notify_Location_Info operation
|
API operation name: Notify_Location_Info
Description: Location information notification to the existing subscription.
Known Consumers: VAL server.
Inputs: Refer subclause 9.3.2.7
Outputs: Refer subclause 9.3.2.7
See subclause 9.3.8 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.3.4 Unsubscribe_Location_Info operation
|
API operation name: Unsubscribe_Location_Info
Description: Unsubscribe to the location information.
Known Consumers: VAL server.
Inputs: Refer subclause 9.3.2.32
Outputs: Refer subclause 9.3.2.33
See subclause 9.3.16 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.3.5 Update_Location_Info_Subscription
|
API operation name: Update_Location_Info_Subscription
Description: Updating an active subscription about the UEs location information.
Known Consumers: VAL server.
Inputs: See subclause 9.3.2.5
Outputs: See subclause 9.3.2.6
See subclause 9.3.7a for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.4 SS_LocationInfoRetrieval API
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.4.1 General
|
API description: This API enables the VAL server to obtain UEs location information from the location management server over LM-S.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.4.2 Obtain_Location_Info operation
|
API operation name: Obtain_Location_Info
Description: Request UEs location information.
Known Consumers: VAL server.
Inputs: Refer subclause 9.3.2.3
Outputs: Refer subclause 9.3.2.2
See subclause 9.3.9 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.5 SS_LocationAreaInfoRetrieval API
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.5.1 General
|
API description: This API enables the VAL server to obtain UE(s) information in an application defined proximity range of a location from the location management server over LM-S.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.5.2 Obtain_UEs_Info operation
|
API operation name: Obtain_UEs_Info
Description: Request UEs information in an application defined proximity range of a location.
Known Consumers: VAL server.
Inputs: Refer subclause 9.3.2.9
Outputs: Refer subclause 9.3.2.10
See subclause 9.3.10 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.6 SS_LocationMonitoring API
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.6.1 General
|
API description: This API enables the VAL server to monitor the VAL UE's location in a given area of interest, from the location management server over LM-S.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.6.2 Subscribe_Location_Monitoring operation
|
API operation name: Subscribe_Location_Monitoring
Description: Subscription to location monitoring.
Known Consumers: VAL server.
Inputs: See subclause 9.3.2.11
Outputs: 9.3.2.12.
See subclause 9.3.11.2 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.6.3 Notify_Location_Monitoring_Events operation
|
API operation name: Notify_Location_Monitoring_Events
Description: Notifying the VAL server with the location monitoring events related to VAL UE.
Known Consumers: VAL server.
Inputs: See subclause 9.3.2.13
Outputs: None.
See subclause 9.3.11.2 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.6.4 Unsubscribe_Location_ Monitoring operation
|
API operation name: Unsubscribe_Location_Monitoring
Description: Unsubscribe to the location Monitoring request.
Known Consumers: VAL server.
Inputs: Refer subclause 9.3.2.34
Outputs: Refer subclause 9.3.2.35
See subclause 9.3.17 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.6.5 Update_Location_Monitoring_Subscription
|
API operation name: Update_Location_Monitoring_Subscription
Description: Updating an active monitor location subscription.
Known Consumers: VAL server.
Inputs: See subclause 9.3.2.11
Outputs: See subclause 9.3.2.12
See subclause 9.3.2.12a for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.7 SS_LocationAreaMonitoring API
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.7.1 General
|
API description: This API enables the VAL server to monitor the list of UEs moving in or moving out of the specific location area.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.7.2 Subscribe_Location_Area_Monitoring
|
API operation name: Subscribe_Location_Area_Monitoring
Description: Subscription to location area monitoring.
Known Consumers: VAL server.
Inputs: See subclause 9.3.2.14
Outputs: 9.3.2.15.
See subclause 9.3.12.1 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.7.3 Notify_Location_Area_Monitoring_Events
|
API operation name: Notify_Location_Area_Monitoring_Events
Description: Notifying the VAL server with the list of UEs moved in or moved out of the specific location area.
Known Consumers: VAL server.
Inputs: See subclause 9.3.2.16
Outputs: None.
See subclause 9.3.12.4 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.7.4 Update_Location_Area_Monitoring_Subscribe
|
API operation name: Update_Location_Area_Monitoring_Subscribe
Description: Updates subscription to location area monitoring.
Known Consumers: VAL server.
Inputs: See subclause 9.3.2.17
Outputs: See subclause 9.3.2.18
See subclause 9.3.12.2 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.7.5 Unsubscribe_Location_Area_Monitoring
|
API operation name: Unsubscribe_Location_Area_Monitoring
Description: Unsubscribing from location area monitoring.
Known Consumers: VAL server.
Inputs: See subclause 9.3.2.19
Outputs: See subclause 9.3.2.20
See subclause 9.3.12.3 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.8 SS_VALServiceAreaConfiguration API
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.8.1 General
|
API description: This API enables the VAL server to configure the list of VAL service area identifiers and the corresponding geographical co-ordinates with SEAL location management server.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.8.2 Configure_VAL_Service_Area
|
API operation name: Configure_VAL_Service_Area
Description: Configuration of VAL service area identifiers.
Known Consumers: VAL server.
Inputs: See subclause 9.3.2.21
Outputs: See subclause 9.3.2.22.
See subclause 9.3.13.2 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.8.3 Obtain_VAL_Service_Area
|
API operation name: Obtain_VAL_Service_Area
Description: Retrieval of VAL service area identifiers.
Known Consumers: VAL server.
Inputs: See subclause 9.3.2.26
Outputs: See subclause 9.3.2.27
See subclause 9.3.13.3 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.8.4 Update_VAL_Service_Area
|
API operation name: Update_VAL_Service_Area
Description: Update of the VAL service area identifier.
Known Consumers: VAL server.
Inputs: See subclause 9.3.2.28
Outputs: See subclause 9.3.2.29
See subclause 9.3.13.4 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.8.5 Delete_VAL_Service_Area
|
API operation name: Delete_VAL_Service_Area
Description: Unsubscribing from VAL service area identifier update events.
Known Consumers: VAL server.
Inputs: See subclause 9.3.2.30
Outputs: See subclause 9.3.2.31
See subclause 9.3.13.5 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.8.6 Subscribe_VAL_Service_Area_Change_Event
|
API operation name: Subscribe_VAL_Service_Area_Change_Event
Description: Subscription to the VAL service area identifiers change events.
Known Consumers: SEAL server.
Inputs: See subclause 9.3.2.42
Outputs: See subclause 9.3.2.43.
See subclause 9.3.13.6 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.8.7 Notify_VAL_Service_Area_Change_Event
|
API operation name: Notify_VAL_Service_Area_Change_Event
Description: Notifying the SEAL server about the VAL service area identifier change events.
Known Consumers: SEAL server.
Inputs: See subclause 9.3.2.44
Outputs: None.
See subclause 9.3.13.7 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.8.8 Unsubscribe_VAL_Service_Area_Change_Event
|
API operation name: Unsubscribe_VAL_Service_Area_Change_Event
Description: Unsubscribing from VAL service area identifier change events.
Known Consumers: SEAL server.
Inputs: See subclause 9.3.2.21
Outputs: See subclause 9.3.2.22.
See subclause 9.3.13.8 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.8.9 Update_Subscription_VAL_Service_Area_Change_Event
|
API operation name: Update_Subscription_VAL_Service_Area_Change_Event
Description: Subscription update for the VAL service area identifiers change events.
Known Consumers: SEAL server.
Inputs: See subclause 9.3.2.42.
Outputs: See subclause 9.3.2.43.
See subclause 9.3.13.9 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.9 SS_LocationHistoryInfoEvent API
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.9.1 General
|
API description: This API enables the VAL server to configure a list of location tracing parameters to the SEAL LM server and obtain the UE history location information over LM-S.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.9.2 Create_Location_Tracing_Configuration operation
|
API operation name: Create_Location_Tracing_Configuration
Description: Creates the location tracing configuration.
Known Consumers: VAL server.
Inputs: Refer subclause 9.3.2.49
Outputs: Refer subclause 9.3.2.50
See subclause 9.3.21.1 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.9.3 Update_Location_Tracing_Configuration operation
|
API operation name: Update_Location_Tracing_Configuration
Description: Updates the location tracing configuration.
Known Consumers: VAL server.
Inputs: Refer subclause 9.3.2.49
Outputs: Refer subclause 9.3.2.50
See subclause 9.3.21.1 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.9.4 Cancel_Location_Tracing_Configuration operation
|
API operation name: Cancel_Location_Tracing_Configuration
Description: Cancels the location tracing configuration.
Known Consumers: VAL server.
Inputs: Refer subclause 9.3.2.53
Outputs: Refer subclause 9.3.2.54
See subclause 9.3.21.3 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.9.5 Obtain_history_Location_Info operation
|
API operation name: Obtain_history_Location_Info
Description: Request UEs history location information.
Known Consumers: VAL server.
Inputs: Refer subclause 9.3.2.51
Outputs: Refer subclause 9.3.2.52
See subclause 9.3.21.2 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.10 SS_SLPositioningManagement API
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.10.1 General
|
API description: This API enables the VAL server to subscribe to SEAL LMS for configuring VAL UEs for a SL positioning / ranging service.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.10.2 Subscribe_ SLPositioningManagement
|
API operation name: Subscribe_ SL_Positioning_Management
Description: Subscription to SL positioning management.
Known Consumers: VAL server.
Inputs: See subclause 9.3.2.61
Outputs: 9.3.2.62.
See subclause 9.3.24.1 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.10.3 Notify_SLPositioningManagement
|
API operation name: Notify_ SL_Positioning_Management
Description: Notifying the VAL server about the success or failure of the SL positioning service configuration.
Known Consumers: VAL server.
Inputs: See subclause 9.3.2.63
Outputs: None.
See subclause 9.3.24.1 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.11 SS_ SRPositioningInformation API
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.11.1 General
|
API description: This API enables a VAL server to obtain Short-range based positioning information from a location management server over LM-S.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.11.2 SR_Positioning_Information operation
|
API operation name: SR_Positioning_Information
Description: Request Short-range based positioning information for a target UE.
Known Consumers: VAL server.
Inputs: Refer subclause 9.3.2.65
Outputs: Refer subclause 9.3.2.66
See subclause 9.3.25 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.12 SS_ConfirmLocation API
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.12.1 General
|
API description: This API enables the VAL server to subscribe for Confirm Location Service and the LMC to use Confirm location service.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.12.2 Confirm Location
|
API operation name: Confirm_Location
Description: Confirm location service.
Known Consumers: LMC.
Inputs: See subclause 9.3.2.75
Outputs: See subclause 9.3.2.76.
See subclause 9.3.26.3 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.12.3 Confirm Location Service Subscription
|
API operation name: ConfirmLocationServiceSubscription
Description: Subscription for the Confirm Location Service.
Known Consumers: VAL server.
Inputs: See subclause 9.3.2.73x
Outputs: See subclause 9.3.2.74
See subclause 9.3.26.2 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.4.12.4 Notify Confirm Location Service
|
API operation name: Notify_ConfirmLocationService
Description: Notification about usage of the Confirm Location Service.
Known Consumers: VAL server.
Inputs: See subclause 9.3.2.77
Outputs: None
See subclause 9.3.26.3 for the details of usage of this API operation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.5 Procedures and information flows for location management (Off-network)
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.5.1 General
|
Location information of VAL service user shall be provided by the location management client of one UE to the location management client of another UE. The location information reporting triggers are based on the location reporting configuration. Different type of location information can be provided e.g. retrieved from non-3GPP source.
NOTE: VAL clients sharing location information directly at vertical enabler layer is outside the scope of this specification.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.5.2 Information flows for off network location management
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.5.2.1 Off-network location reporting trigger configuration
|
Table 9.5.2.1-1 describes the information flow from the location management client-1 to the location management client-2 for the off-network location reporting configuration.
Table 9.5.2.1-1: Off-network location reporting trigger configuration
Information element
Status
Description
Identity
M
Identity of the VAL user to which the location reporting configuration is targeted or identity of the VAL UE.
Requested location information
M
Identifies what location information is requested
List of triggering criteria(s)
M
One or more triggering criteria that identifies when the location management client will send the location report. Each triggering criteria is identified by trigger-id.
Minimum time between consecutive reports
O
Defaults to 0 if absent otherwise indicates the time interval between consecutive reports
Life Time of the configuration
O
Time till when location report configurations are valid.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.5.2.2 Off-network location reporting trigger configuration response
|
Table 9.5.2.2-1 describes the information flow from the location management client-2 to the location management client-1 for the off-network location reporting configuration response. The Off-network location reporting trigger configuration response acts as an acknowledgement to the location management client-1.
Table 9.5.2.2-1: Off-network location reporting trigger configuration response
Information element
Status
Description
Result
M
Indicates the success or failure for the operation
Cause
O
Provides reason for the failure.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.5.2.3 Off-network location management ack
|
The Off-network location management ack message is sent from the message receiver location management client-2 to message originator location management client-1.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.5.2.4 Off-network location report
|
Table 9.5.2.4-1 describes the information flow from the location management client-2 to the location management client-1 for the off-network location report.
Table 9.5.2.4-1: Off-network location report
Information element
Status
Description
Triggering event
M
Identity of the event that triggered the sending of the report
Location Information
M
Location information shared by VAL client e.g. retrieved from non-3GPP source, obtained via Sidelink positioning/Ranging method, etc.
Acknowledgement Required
O
If present, indicate the recipient of the message to acknowledge the message.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.5.2.5 Off-network location reporting trigger cancel
|
Table 9.5.2.5-1 describes the information flow from the location management client-1 to the location management client-2 for the off-network location reporting trigger cancel.
Table 9.5.2.5-1: Off-network location reporting trigger cancels
Information element
Status
Description
Identity
M
Identity of the VAL user to which the location reporting trigger cancel is targeted or identity of the VAL UE.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.5.2.6 Off-network location reporting trigger cancel response
|
Table 9.5.2.6-1 describes the information flow from the location management client-2 to the location management client-1 for the off-network location reporting cancel response. The Off-network location reporting trigger cancel response acts as an acknowledgement to the location management client-1.
Table 9.5.2.6-1: Off-network location reporting trigger cancel response
Information element
Status
Description
Result
M
Indicates the success or failure for the operation
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.5.2.7 Off-network location request
|
Table 9.5.2.7-1 describes the information flow from the location management client-1 to the location management client-2 for the off-network location request.
Table 9.5.2.7-1: Off-network location request
Information element
Status
Description
Identity
M
Identity of the VAL user to which the location request is targeted or identity of the VAL UE.
Requested location information
M
Identifies what location information is requested
Requested velocity indication
O
It indicates whether the velocity of the requested VAL users/UEs is needed.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.5.2.8 Off-network location response
|
Table 9.5.2.8-1 describes the information flow from the location management client-2 to the location management client-1 for the off-network location response. The Off-network location response acts as an acknowledgement to the location management client-1.
Table 9.5.2.8-1: Off-network location response
Information element
Status
Description
Result
M
Indicates the success or failure for the operation
Location Information
M
Location information shared by VAL client e.g. retrieved from non-3GPP source, obtained via Sidelink positioning/Ranging method, etc.
Velocity information
O
Velocity information
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.5.3 Event-triggered location reporting procedure
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.5.3.1 Location reporting trigger configuration
|
Figure 9.5.3.1-1 illustrates the procedure for configuring location reporting triggers from the location management client-1 residing in UE-1 to the location management client-2 residing in UE-2.
Pre-condition:
- The UE-1 and UE-2 are within PC5 communication range of each other, and aware of Layer-2 ID of each other.
- The VAL service user in UE-1 is authorized to configure location reporting trigger to the UE-2.
- The VAL service user in UE-1 requests to configure location reporting triggers to the UE-2.
Figure 9.5.3.1-1: Location reporting trigger configuration
1. The location management client-1 in UE-1 sends off network location reporting trigger configuration message to the location management client-2 in UE-2 containing the initial location reporting event triggers configuration (or a subsequent update) for reporting the location of the VAL UE. The message includes information elements as specified in Table 9.5.2.1-1.
2. The location management client-2 stores the location reporting configuration, and sends off network location reporting trigger configuration response to the location management client-1. The message includes information elements as specified in Table 9.5.2.2-1.
3. Upon receiving the off network location reporting trigger configuration response message, the location management client-1 sends off-network location management ack messages. The message includes information elements as specified in clause 9.5.2.3.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.5.3.2 Location reporting
|
Figure 9.5.3.2-1 illustrates the procedure for sending off-network location report from the location management client-2 residing in UE-2 to the location management client-1 residing in UE-1.
Pre-condition:
- The UE-1 and UE-2 are within PC5 communication range of each other, and aware of Layer-2 ID of each other.
- The location management client-1 has previously configured off-network location reporting triggers to the location management client-2 as specified in clause 9.5.3.1.
Figure 9.5.3.2-1: Location reporting
1. The location management client-2 is monitoring the location reporting triggers and one of the event is triggered.
2. The location management client-2 sends the off-network location report message. The message includes information elements as specified in Table 9.5.2.4-1.
3. Upon receiving the off network location report message, the location management client-1 sends the off-network location management ack message if requested in the received message. The message includes information elements as specified in clause 9.5.2.3.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.5.3.3 Location reporting trigger cancel
|
Figure 9.5.3.3-1 illustrates the procedure for sending off-network location reporting trigger cancel from the location management client-1 residing in UE-1 to the location management client-2 residing in UE-2.
Pre-condition:
- The UE-1 and UE-2 are within PC5 communication range of each other, and aware of Layer-2 ID of each other.
- The location management client-1 has previously configured location reporting triggers to the location management client-2 as specified in clause 9.5.3.1.
Figure 9.5.3.3-1: Location reporting trigger cancel
1. The location management client-1 in UE-1 sends off network location reporting trigger cancel message to the location management client-2 in UE-2 to cancel the location reporting trigger configuration. The message includes information elements as specified in Table 9.5.2.5-1.
2. The location management client-2 clears the location reporting configuration, and sends off network location reporting trigger cancel response to the location management client-1. The message includes information elements as specified in Table 9.5.2.6-1.
3. Upon receiving the off network location reporting trigger configuration response message, the location management client-1 sends off-network location management ack message. The message includes information elements as specified in clause 9.5.2.3.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.5.4 On-demand location reporting procedure
|
Figure 9.5.4-1 illustrates the procedure for on-demand location report from the location management client-1 residing in UE-1 to the location management client-2 residing in UE-2.
Pre-condition:
- The UE-1 and UE-2 are within PC5 communication range of each other, and aware of Layer-2 ID of each other.
- The VAL service user in UE-1 is authorized to request location report from the UE-2.
- The VAL service user in UE-1 requests immediate location reporting to the UE-2.
Figure 9.5.4-1: Location reporting trigger cancel
1. Based on configurations such as periodical location information timer the location management client-1 initiates the immediately request location information from the location management client-2. The location management client sends an off-network location request to the location management client-2. The message includes information elements as specified in Table 9.5.2.7-1.
2. VAL user or VAL UE is notified and asked about the permission to share its location. VAL user can accept or deny the request
3. The location management client-2 immediately responds to the location management client-1. If permission is received from the VAL user, the location management client-2 includes a report containing location information identified by the location management client-1 and available to the location management client-2. The message includes information elements as specified in Table 9.5.2.8-1.
4. Upon receiving the off network location reporting trigger configuration response message, the location management client-1 sends off-network location management ack message. The message includes information elements as specified in clause 9.5.2.3
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
10 Group management
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
10.1 General
|
The group management is a SEAL service that offers the group management related capabilities to one or more vertical applications.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
10.2 Functional model for group management
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
10.2.1 General
|
The functional model for the group management is based on the generic functional model specified in clause 6. It is organized into functional entities to describe a functional architecture which addresses the support for group management aspects for vertical applications. The on-network and off-network functional model is specified in this clause.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
10.2.2 On-network functional model description
|
Figure 10.2.2-1 illustrates the generic on-network functional model for group management.
Figure 10.2.2-1: On-network functional model for group management
The group management client communicates with the group management server over the GM-UU reference point. The group management client provides the support for group management functions to the VAL client(s) over GM‑C reference point. The VAL server(s) communicate with the group management server over the GM-S reference point.
The group management server interacts with the NEF of the underlying 3GPP network system via N33 reference point to perform group management procedures for 5G Virtual Network (5GVN) groups.
Figure 10.2.2-2 exhibits the service-based interfaces for providing and consuming group management services. The group management server could provide service to VAL server and group management client through interface Sgm.
Figure 10.2.2-2: Architecture for group management – Service based representation
Figure 10.2.2-3 illustrates the service-based representation for utilization of the 5GS network services based on the 5GS SBA specified in 3GPP TS 23.501 [10].
Figure 10.2.2-3: Architecture for group management utilizing the 5GS network services based on the 5GS SBA – Service based representation
Figure 10.2.2-4 illustrates the service-based representation for utilization of the Core Network northbound APIs via CAPIF.
Figure 10.2.2-4: Utilization of Core Network Northbound APIs via CAPIF – service based representation
The Group management server acts as authorized API invoker to consume services from the Core Network northbound API entities like NEF which act as API Exposing Function as specified in 3GPP TS 23.222 [6].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
10.2.3 Off-network functional model description
|
Figure 10.2.3-1 illustrates the off-network functional model for group management.
Figure 10.2.3-1: Off-network functional model for group management
The group management client of the UE1 communicates with the group management client of the UE2 over the GM‑PC5 reference point.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
10.2.4 Functional entities description
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
10.2.4.1 General
|
The functional entities for group management SEAL service are described in the following subclauses.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
10.2.4.2 Group management client
|
The group management client functional entity acts as the application client for management of groups. A VAL system maintains groups corresponding to one or more vertical applications. The group management client interacts with the group management server. The group management client also supports interactions with the corresponding group management client between the two UEs.
The group management client functional entity is supported by the signalling user agent and HTTP client functional entities of the signalling control plane.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
10.2.4.3 Group management server
|
The group management server functional entity provides for management of groups supported within the vertical application layer. The group management server acts as CAPIF's API exposing function as specified in 3GPP TS 23.222 [8]. The group management server also supports interactions with the corresponding group management server in distributed SEAL deployments.
The group management server functional entity is supported by the SIP AS and HTTP server functional entities of the signalling control plane.
All the group management clients supporting users belonging to a single group are required to use the same group management server for that group. A group management client supporting a user involved in multiple groups can have relationships with multiple group management servers.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
10.2.5 Reference points description
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
10.2.5.1 General
|
The reference points for the functional model for group management are described in the following subclauses.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
10.2.5.2 GM-UU
|
The interactions related to group management functions between the group management client and the group management server are supported by GM-UU reference point. This reference point utilizes Uu reference point as described in 3GPP TS 23.401 [9] and 3GPP TS 23.501 [10].
GM-UU reference point is used for VAL service signalling for VAL service data management of the VAL service. The GM-UU reference point supports:
- Configuration of group related data at the group management client by the group management server; and
- Configuration of group related data at the group management server by the group management client.
The GM-UU reference point uses the HTTP-1/HTTP-2 reference points for transport and routing of group management related signalling. The GM-UU reference point uses the SIP-1/SIP-2 reference points for subscription/notification related signalling.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
10.2.5.3 GM-PC5
|
The interactions related to group management functions between the group management clients located in different VAL UEs are supported by GM-PC5 reference point. This reference point utilizes PC5 reference point as described in 3GPP TS 23.303 [12].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
10.2.5.4 GM-C
|
The interactions related to group management functions between the VAL client(s) and the group management client within a VAL UE are supported by GM-C reference point.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
10.2.5.5 GM-S
|
The interactions related to group management functions between the VAL server(s) and the group management server are supported by GM-S reference point. This reference point is an instance of CAPIF-2 reference point as specified in 3GPP TS 23.222 [8].
GM-S reference point supports the VAL server to obtain group information corresponding to the VAL service. The GM-S reference point uses HTTP-1/HTTP-2 reference points for transport and routing of group management related signalling. The GM-S reference point uses SIP-2 reference point for subscription/notification related signalling.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
10.2.5.6 GM-E
|
The interactions related to group management functions between the group management servers in a distributed deployment are supported by GM-E reference point.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.