Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.434  Word version:  19.4.2

Top   Top   Up   Prev   Next
0…   6…   8…   9…   9.3…   9.3.3…   9.3.8…   9.3.13…   9.3.20…   9.3.23…   9.4…   10…   10.3…   10.3.3…   10.3.7…   10.4…   11…   12…   13…   14…   14.3…   14.3.3   14.3.4   14.3.4A…   14.3.4A.5…   14.3.4A.8…   14.3.5…   14.3.9…   14.4…   15…   17…   18…   A… 
9.4 SEAL APIs for location management  9.4.1 General  9.4.2 SS_LocationReporting API  9.4.3 SS_LocationInfoEvent API  9.4.4 SS_LocationInfoRetrieval API  9.4.5 SS_LocationAreaInfoRetrieval API  9.4.6 SS_LocationMonitoring API  9.4.7 SS_LocationAreaMonitoring API  9.4.8 SS_VALServiceAreaConfiguration API  9.4.9 SS_LocationHistoryInfoEvent API  9.4.10 SS_SLPositioningManagement API  9.4.11 SS_ SRPositioningInformation API  9.4.12 SS_ConfirmLocation API  9.5 Procedures and information flows for location management (Off-network)  9.5.1 General  9.5.2 Information flows for off network location management  9.5.3 Event-triggered location reporting procedure  9.5.4 On-demand location reporting procedure 
...

 

9.4  SEAL APIs for location management  p. 119

9.4.1  General  p. 119

Table 9.4.1-1 illustrates the SEAL APIs for location management.
API Name API Operations Known Consu­mer(s) Communi­cation Type
SS_LocationReporting Create_Trigger_Location_ReportingVAL serverSubscribe/Notify
Update_Trigger_Location_Reporting
Cancel_Trigger_Location_Reporting
Notify_Trigger_Location_Reporting
Notify_Adaptive_Configuration
SS_LocationInfoEvent Subscribe_Location_Info VAL serverSubscribe/Notify
Unsubscribe_Location_Info
Update_Location_Info_Subscription
Notifiy_Location_Info
SS_LocationInfoRetrieval Obtain_Location_InfoVAL serverRequest/Response
SS_LocationAreaInfoRetrieval Obtain_UEs_InfoVAL serverRequest/Response
SS_LocationMonitoring Subscribe_Location_MonitoringVAL serverSubscribe/Notify
Unsubscribe_Location_Monitoring
Update_Location_Monitoring_Subscription
Notify_Location_Monitoring_Events
SS_Location_Area_Monitoring Subscribe_Location_Area_MonitoringVAL serverSubscribe/Notify
Notify_Location_Area_Monitoring_Events
Update_Location_Area_Monitoring_Subscribe
Unsubscribe_Location_Area_Monitoring
SS_VALServiceAreaConfiguration Configure_VAL_Service_AreaVAL serverRequest/Response
Obtain_VAL_Service_Area
Update_VAL_Service_Area
Delete_VAL_Service_Area
Subscribe_VAL_Service_Area_Change_EventSEAL serverSubscribe/Notify
Notify_VAL_Service_Area_Change_Event
Unsubscribe_VAL_Service_Area_Change_Event
Update_Subscription_VAL_Service_Area_Change_Event
SS_LocationHistoryInfoEvent Create_Location_Tracing_ConfigurationVAL serverRequest/Response
Update_Location_Tracing_ConfigurationVAL server
Delete_Location_Tracing_ConfigurationVAL server
Obtain_history_Location_InfoVAL server
SS_SLPositioningManagement Subscribe_SLPositioningManagementVAL serverSubscribe/Notify
Notify_SLPositioningManagementVAL server
SS_SRPositioningInformation SR_Positioning_InformationVAL serverRequest/Response
SS_ConfirmLocation Confirm_LocationLMCRequest/Response
ConfirmLocationServiceSubscriptionVAL serverRequest/Response
Notify_ConfirmLocationServiceUsage (NOTE)VAL serverSubscribe/Notify
NOTE:
The subscribe operation is part of ConfirmLocationServiceSubscription.
Up

9.4.2  SS_LocationReporting API  p. 120

9.4.2.1  General  p. 120

API description:
This API enables the VAL server to trigger reporting of location information to the location management server over LM-S.

9.4.2.2  Create_Trigger_Location_Reporting operation  p. 120

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.

9.4.2.3  Update_Trigger_Location_Reporting operation  p. 121

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.

9.4.2.4  Cancel_Trigger_Location_Reporting operation  p. 121

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.

9.4.2.5  Notify_Trigger_Location_Reporting operation  p. 121

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.

9.4.2.6  Notify_Adaptive_Configuration operation |R19|  p. 121

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.

9.4.3  SS_LocationInfoEvent API  p. 122

9.4.3.1  General  p. 122

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.

9.4.3.2  Subscribe_Location_Info operation  p. 122

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.

9.4.3.3  Notify_Location_Info operation  p. 122

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.

9.4.3.4  Unsubscribe_Location_Info operation |R18|  p. 122

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.

9.4.3.5  Update_Location_Info_Subscription |R18|  p. 122

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.

9.4.4  SS_LocationInfoRetrieval API  p. 123

9.4.4.1  General  p. 123

API description:
This API enables the VAL server to obtain UEs location information from the location management server over LM-S.

9.4.4.2  Obtain_Location_Info operation  p. 123

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.

9.4.5  SS_LocationAreaInfoRetrieval API |R17|  p. 123

9.4.5.1  General  p. 123

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.

9.4.5.2  Obtain_UEs_Info operation  p. 123

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.

9.4.6  SS_LocationMonitoring API |R17|  p. 123

9.4.6.1  General  p. 123

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.

9.4.6.2  Subscribe_Location_Monitoring operation  p. 123

API operation name:
Subscribe_Location_Monitoring
Description:
Subscription to location monitoring.
Known Consumers:
VAL server.
Inputs:
See subclause 9.3.2.11
Outputs:
See subclause 9.3.2.12.
See subclause 9.3.11.2 for the details of usage of this API operation.

9.4.6.3  Notify_Location_Monitoring_Events operation  p. 124

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.

9.4.6.4  Unsubscribe_Location_ Monitoring operation |R18|  p. 124

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.

9.4.6.5  Update_Location_Monitoring_Subscription |R18|  p. 124

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.

9.4.7  SS_LocationAreaMonitoring API |R17|  p. 124

9.4.7.1  General  p. 124

API description:
This API enables the VAL server to monitor the list of UEs moving in or moving out of the specific location area.

9.4.7.2  Subscribe_Location_Area_Monitoring  p. 124

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.

9.4.7.3  Notify_Location_Area_Monitoring_Events  p. 125

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.

9.4.7.4  Update_Location_Area_Monitoring_Subscribe  p. 125

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.

9.4.7.5  Unsubscribe_Location_Area_Monitoring  p. 125

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.

9.4.8  SS_VALServiceAreaConfiguration API |R18|  p. 125

9.4.8.1  General  p. 125

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.

9.4.8.2  Configure_VAL_Service_Area  p. 125

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.

9.4.8.3  Obtain_VAL_Service_Area  p. 126

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.

9.4.8.4  Update_VAL_Service_Area  p. 126

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.

9.4.8.5  Delete_VAL_Service_Area  p. 126

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.

9.4.8.6  Subscribe_VAL_Service_Area_Change_Event  p. 126

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.

9.4.8.7  Notify_VAL_Service_Area_Change_Event  p. 126

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.

9.4.8.8  Unsubscribe_VAL_Service_Area_Change_Event  p. 127

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.

9.4.8.9  Update_Subscription_VAL_Service_Area_Change_Event  p. 127

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.

9.4.9  SS_LocationHistoryInfoEvent API |R19|  p. 127

9.4.9.1  General  p. 127

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.

9.4.9.2  Create_Location_Tracing_Configuration operation  p. 127

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.

9.4.9.3  Update_Location_Tracing_Configuration operation  p. 127

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.

9.4.9.4  Cancel_Location_Tracing_Configuration operation  p. 128

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.

9.4.9.5  Obtain_history_Location_Info operation  p. 128

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.

9.4.10  SS_SLPositioningManagement API |R19|  p. 128

9.4.10.1  General  p. 128

API description:
This API enables the VAL server to subscribe to SEAL LMS for configuring VAL UEs for a SL positioning / ranging service.

9.4.10.2  Subscribe_ SLPositioningManagement  p. 128

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.

9.4.10.3  Notify_SLPositioningManagement  p. 128

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.

9.4.11  SS_ SRPositioningInformation API |R19|  p. 129

9.4.11.1  General  p. 129

API description:
This API enables a VAL server to obtain Short-range based positioning information from a location management server over LM-S.

9.4.11.2  SR_Positioning_Information operation  p. 129

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.

9.4.12  SS_ConfirmLocation API |R19|  p. 129

9.4.12.1  General  p. 129

API description:
This API enables the VAL server to subscribe for Confirm Location Service and the LMC to use Confirm location service.

9.4.12.2  Confirm Location  p. 129

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.

9.4.12.3  Confirm Location Service Subscription  p. 129

API operation name:
ConfirmLocationServiceSubscription
Description:
Subscription for the Confirm Location Service.
Known Consumers:
VAL server.
Inputs:
See subclause 9.3.2.73
Outputs:
See subclause 9.3.2.74
See subclause 9.3.26.2 for the details of usage of this API operation.

9.4.12.4  Notify Confirm Location Service  p. 129

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.

9.5  Procedures and information flows for location management (Off-network) |R17|  p. 130

9.5.1  General  p. 130

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.

9.5.2  Information flows for off network location management  p. 130

9.5.2.1  Off-network location reporting trigger configuration  p. 130

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.
Information Element Status Description
IdentityMIdentity of the VAL user to which the location reporting configuration is targeted or identity of the VAL UE.
Requested location informationMIdentifies what location information is requested
List of triggering criteria(s)MOne 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 reportsODefaults to 0 if absent otherwise indicates the time interval between consecutive reports
Life Time of the configurationOTime till when location report configurations are valid.
Up

9.5.2.2  Off-network location reporting trigger configuration response  p. 130

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.
Information Element Status Description
ResultMIndicates the success or failure for the operation
CauseOProvides reason for the failure.
Up

9.5.2.3  Off-network location management ack  p. 130

The Off-network location management ack message is sent from the message receiver location management client-2 to message originator location management client-1.

9.5.2.4  Off-network location report  p. 131

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.
Information Element Status Description
Triggering eventMIdentity of the event that triggered the sending of the report.
Location InformationMLocation information shared by VAL client e.g. retrieved from non-3GPP source, obtained via Sidelink positioning/Ranging method, etc.
Acknowledgement RequiredOIf present, indicate the recipient of the message to acknowledge the message.
Up

9.5.2.5  Off-network location reporting trigger cancel  p. 131

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.
Information Element Status Description
IdentityMIdentity of the VAL user to which the location reporting trigger cancel is targeted or identity of the VAL UE.
Up

9.5.2.6  Off-network location reporting trigger cancel response  p. 131

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.
Information Element Status Description
ResultMIndicates the success or failure for the operation
Up

9.5.2.7  Off-network location request  p. 131

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.
Information Element Status Description
IdentityMIdentity of the VAL user to which the location request is targeted or identity of the VAL UE.
Requested location informationMIdentifies what location information is requested
Velocity indicationOIt indicates whether velocity of the requested VAL users/UEs is needed.
Up

9.5.2.8  Off-network location response  p. 131

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.
Information Element Status Description
ResultMIndicates the success or failure for the operation.
Location InformationMLocation information shared by VAL client e.g. retrieved from non-3GPP source, obtained via Sidelink positioning/Ranging method, etc.
Velocity informationOVelocity information.
Up

9.5.3  Event-triggered location reporting procedure  p. 132

9.5.3.1  Location reporting trigger configuration  p. 132

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.
Reproduction of 3GPP TS 23.434, Fig. 9.5.3.1-1: Location reporting trigger configuration
Figure 9.5.3.1-1: Location reporting trigger configuration
Up
Step 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.
Step 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.
Step 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.
Up

9.5.3.2  Location reporting  p. 132

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.
Reproduction of 3GPP TS 23.434, Fig. 9.5.3.2-1: Location reporting
Figure 9.5.3.2-1: Location reporting
Up
Step 1.
The location management client-2 is monitoring the location reporting triggers and one of the event is triggered.
Step 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.
Step 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.
Up

9.5.3.3  Location reporting trigger cancel  p. 133

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.
Reproduction of 3GPP TS 23.434, Fig. 9.5.3.3-1: Location reporting trigger cancel
Figure 9.5.3.3-1: Location reporting trigger cancel
Up
Step 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.
Step 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.
Step 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.
Up

9.5.4  On-demand location reporting procedure  p. 134

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.
Reproduction of 3GPP TS 23.434, Fig. 9.5.4-1: Location reporting trigger cancel
Figure 9.5.4-1: Location reporting trigger cancel
Up
Step 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.
Step 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
Step 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.
Step 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.
Up

Up   Top   ToC