Tech-invite  3GPPspace  IETF RFCs  SIP
index  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:  18.3.0

Top   Top   Up   Prev   Next
0…   4…   6…   6.4…   6.5…   7…   8…   8.2.2…   9…   9.3…   9.3.6…   9.3.11…   9.4…   10…   10.3…   10.3.2.22…   10.3.3…   10.3.7…   10.3.10…   10.4…   11…   11.3…   12…   13…   14…   14.3…   14.3.3…   14.3.3.3…   14.3.4…   14.3.4.6   14.3.4.7…   14.3.4A…   14.3.4A.4…   14.3.4A.6…   14.3.4A.8…   14.3.4A.9…   14.3.4A.10…   14.3.5…   14.4…   15…   16…   17…   19…   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.5 Procedures and information flows for Location management (Off-network) 
...

 

9.4  SEAL APIs for location management  p. 65

9.4.1  General  p. 65

Table 9.4.1-1 illustrates the SEAL APIs for location management.
API Name API Operations Known Consumer(s) Communication Type
SS_LocationReportingCreate_Trigger_Location_Reporting
Update_Trigger_Location_Reporting
Cancel_Trigger_Location_Reporting		VAL serverRequest /Response
SS_LocationInfoEventSubscribe_Location_InfoVAL serverSubscribe/Notify
Notify_Location_InfoVAL server
SS_LocationInfoRetrievalObtain_Location_InfoVAL serverRequest /Response
SS_LocationMonitoringSubscribe_Location_MonitoringVAL serverSubscribe/Notify
Notify_Location_Monitoring_EventsVAL server
Up

9.4.2  SS_LocationReporting API  p. 66

9.4.2.1  General  p. 66

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. 66

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. 66

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. 66

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.8
See subclause 9.3.6 for the details of usage of this API operation.

9.4.3  SS_LocationInfoEvent API  p. 66

9.4.3.1  General  p. 66

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

9.4.3.2  Subscribe_Location_Info operation  p. 66

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. 67

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.4  SS_LocationInfoRetrieval API  p. 67

9.4.4.1  General  p. 67

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. 67

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. 67

9.4.5.1  General  p. 67

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. 67

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. 68

9.4.6.1  General  p. 68

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  p. 68

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  p. 68

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.7  SS_LocationAreaMonitoring API |R17|  p. 68

9.4.7.1  General  p. 68

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. 68

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. 68

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. 69

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. 69

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. 69

9.4.8.1  General  p. 69

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 LM server.

9.4.8.2  Configure_VAL_Service_Area  p. 69

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.1 for the details of usage of this API operation.

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

9.5.1  General  p. 70

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.
Up

9.5.2  Information flows for off network location management  p. 70

9.5.2.1  Off-network location reporting trigger configuration  p. 70

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. 70

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. 70

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. 71

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
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. 71

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. 71

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. 71

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
Up

9.5.2.8  Off-network location response  p. 71

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
Up

9.5.3  Event-triggered location reporting procedure  p. 72

9.5.3.1  Location reporting trigger configuration  p. 72

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. 72

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. 73

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. 74

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