9 Location management
23.4343GPPFunctional architecture and information flowsRelease 18Service Enabler Architecture Layer for Verticals (SEAL)TS
9.1 General
The location management is a SEAL service that offers the location management related capabilities to one or more vertical applications.
9.2 Functional model for location management
9.2.1 General
The functional model for the location 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 location management aspects for vertical applications. The on-network and off-network functional model is specified in this clause.
9.2.2 On-network functional model description
Figure 9.2.2-1 illustrates the generic on-network functional model for location management.
Figure 9.2.2-1: On-network functional model for location management
The location management client communicates with the location management server over the LM-UU reference point. The location management client provides the support for location management functions to the VAL client(s) over LM‑C reference point. The VAL server(s) communicate with the location management server over the LM-S reference point.
The location management server communicates with the SCEF via T8 reference point to obtain location information from the underlying 3GPP network system. The location management server obtains location information from the NEF via N33 reference point by mechanism defined in clause 5.2.6.2 of 3GPP TS 23.502 [11].
NOTE: Location information from LCS of 4G system is not exposed by SCEF.
Editor’s note: Use of Le interface for acquiring location information provided by PLMN is FFS.
9.2.3 Off-network functional model description
Figure 9.2.3-1 illustrates the off-network functional model for location management.
Figure 9.2.3-1: Off-network functional model for location management
The location management client of the UE1 communicates with the location management client of the UE2 over the LM-PC5 reference point.
9.2.4 Functional entities description
9.2.4.1 General
The functional entities for location management SEAL service are described in the following subclauses.
9.2.4.2 Location management client
The location management client functional entity acts as the application client for location management functions. It interacts with the location management server. The location management client also supports interactions with the corresponding location management client between the two UEs.
9.2.4.3 Location management server
The location management server is a functional entity that receives and stores user location information and provides user location information to the vertical application server. The location management server may also acquire location information provided by PLMN operator via T8 reference point. The location management server acts as CAPIF’s API exposing function as specified in 3GPP TS 23.222 [8]. The location management server also supports interactions with the corresponding location management server in distributed SEAL deployments.
NOTE: The accuracy of location information acquired from 4G system via T8 reference point is not higher than at cell level (ECGI) for E-UTRAN.
9.2.5 Reference points description
9.2.5.1 General
The reference points for the functional model for location management are described in the following subclauses.
9.2.5.2 LM-UU
The interactions related to location management functions between the location management client and the location management server are supported by LM-UU reference point. This reference point utilizes Uu reference point as described in 3GPP TS 23.401 [9] and 3GPP TS 23.501 [10].
LM-UU reference point provides a means for the location management server to receive location information report from the location management client. The LM-UU reference point shall use SIP-1 and SIP-2 reference points for subscription/notification related signalling. And for transport and routing of location management related signalling LM-UU reference point uses the HTTP-1 and HTTP-2 signalling control plane reference points.
9.2.5.3 LM-PC5
The interactions related to location management functions between the location management clients located in different VAL UEs are supported by LM-PC5 reference point. This reference point utilizes PC5 reference point as described in 3GPP TS 23.303 [12].
9.2.5.4 LM-C
The interactions related to location management functions between the VAL client(s) and the location management client within a VAL UE are supported by LM-C reference point.
9.2.5.5 LM-S
The interactions related to location management functions between the VAL server(s) and the location management server are supported by LM-S reference point. This reference point is an instance of CAPIF-2 reference point as specified in 3GPP TS 23.222 [8].
LM-S reference point is used by the VAL server to request and receive location information from location management server. The LM-S reference point shall use SIP-1 and SIP-2 reference points for subscription/notification related signalling. And for transport and routing of location management related signalling LM-S reference point uses the HTTP-1 and HTTP-2 signalling control plane reference points.
9.2.5.6 LM-E
The interactions related to location management functions between the location management servers in a distributed deployment are supported by LM-E reference point.
Editor’s Note: The functions enabled over LM-E reference point is FFS.
9.2.5.7 T8
The reference point T8 supports the interactions between the location management server and the SCEF and is specified in 3GPP TS 23.682 [13]. The functions related to location management of T8 are supported by the location management server.
9.3 Procedures and information flows for Location management (on-network)
9.3.1 General
Location information of VAL service user shall be provided by the location management client to the location management server. The location information reporting triggers are based on the location reporting configuration. Different type of location information can be provided.
Editor’s note: The security and privacy aspects related to VAL server obtaining UE’s location information are to be addressed by SA3.
9.3.2 Information flows for location information
9.3.2.0 Location reporting configuration request
Table 9.3.2.0-1 describes the information flow from the location management client to the location management server for requesting the location reporting configuration.
Table 9.3.2.0-1: Location reporting configuration request
Information element |
Status |
Description |
Identity |
M |
Identity of the VAL user or identity of the VAL UE. |
VAL service ID |
O |
Identity of the VAL service for which the location reporting configuration is requested. |
9.3.2.1 Location reporting configuration response
Table 9.3.2.1-1 describes the information flow from the location management server to the location management client for the location reporting configuration. This information flow may be sent individually addressed or group addressed on unicast or multicast.
Table 9.3.2.1-1: Location reporting configuration response
Information element |
Status |
Description |
Identity |
M |
Identity of the VAL user or VAL group to which the location reporting configuration is targeted or identity of the VAL UE. |
Requested location information |
O (see NOTE) |
Identifies what location information is requested |
Triggering criteria |
O (see NOTE) |
Identifies when the location management client will send the location report |
Minimum time between consecutive reports |
O (see NOTE) |
Defaults to 0 if absent otherwise indicates the time interval between consecutive reports |
NOTE: If none of the information element is present, this represents a cancellation for location reporting. |
9.3.2.2 Location information report
Table 9.3.2.2-1 describes the information flow from the location management client to the location management server for the location information reporting or from the location management server to the requesting location management client or VAL server to report location information.
Table 9.3.2.2-1: Location information report
Information element |
Status |
Description |
Set of identities |
M |
Set of identities of the reporting VAL users or VAL UEs |
Triggering event |
M |
Identity of the event that triggered the sending of the report |
Location Information |
M |
Location information |
Timestamp |
O |
Timestamp of the location report |
9.3.2.3 Location information request
Table 9.3.2.3-1 describes the information flow from the VAL server to the location management server and from the location management server to the location management client for requesting an immediate location information report.
Table 9.3.2.3-1: Location information request
Information element |
Status |
Description |
Identity list |
M |
List of VAL users or VAL UEs whose location information is requested |
VAL service ID |
O |
Identity of the VAL service for which the location information is requested. |
Editor’s Note: It’s FFS whether and how the LMS need to identify the VAL service when the VAL UE ID is used for location request.
Editor’s Note: It’s FFS the security aspects for LM-Uu and LM-S in relation to the VAL service ID that need to be coordinated with SA3.
9.3.2.4 Location reporting trigger
Table 9.3.2.4-1 describes the information flow from the location management client or VAL server to the location management server for triggering a location reporting procedure.
Table 9.3.2.4-1: Location reporting trigger
Information element |
Status |
Description |
Identity |
M (see NOTE 1) |
Identity of the requesting authorized VAL user or VAL UE or VAL server |
Identity |
M (see NOTE 1) |
Identity of the requested VAL user or VAL UE |
VAL service ID |
O |
Identity of the VAL service for which the location reporting trigger is set. |
Immediate Report Indicator |
O (see NOTE 2) |
Indicates whether an immediate location report is required |
Requested location information |
O (see NOTE 2) |
Identifies what location information is requested |
Triggering criteria |
O (see NOTE 2) |
Identifies when the requesting client/VAL server is expecting to receive the location report from the requested VAL user/ VAL UE. It may include VAL service Area ID based criteria when this information flow is from VAL server to the location management server. |
Minimum time between consecutive reports |
O see (NOTE 2) |
Defaults to 0 if absent otherwise indicates the interval time between consecutive reports |
Endpoint information |
O |
Information of the endpoint of the requesting VAL server to which the location report notification has to be sent. It is provided if Immediate Report Indicator is set to required. |
NOTE 1: The identity of the requesting VAL user/UE/VAL server and the requested VAL user/UE should belong to the same VAL service. NOTE 2: At least one of these rows shall be present. |
9.3.2.5 Location information subscription request
Table 9.3.2.5-1 describes the information flow from the VAL server or location management client to the location management server for location information subscription request.
Table 9.3.2.5-1: Location information subscription request
Information element |
Status |
Description |
Identity |
M |
Identity of the requesting VAL server/VAL user or VAL UE |
Identities list |
M |
List of VAL users or VAL UEs whose location information is requested. |
VAL service ID |
O |
Identity of the VAL service for which the location information is subscribed. |
Time between consecutive reports |
M |
It indicates the interval time between consecutive reports |
9.3.2.6 Location information subscription response
Table 9.3.2.6-1 describes the information flow from the location management server to the VAL server or location management client for location information subscription response.
Table 9.3.2.6-1: Location information subscription response
Information element |
Status |
Description |
Identity |
M |
Identity of the requesting VAL server/VAL user or VAL UE |
Subscription status |
M |
It indicates the subscription result |
9.3.2.7 Location information notification
Table 9.3.2.7-1 describes the information flow from the location management server to the VAL server or the location management client.
Table 9.3.2.7-1: Location information notification
Information element |
Status |
Description |
Identities list |
M |
List of the VAL users or VAL UEs whose location information needs to be notified |
Identity (see NOTE 2) |
O |
Identity of the VAL user or VAL UE subscribed to location of another VAL user or VAL UE (see NOTE 1) |
Subscription ID (see NOTE 2) |
O |
Subscription identity related to VAL server subscription with Location management server for location information notification. |
Triggering event |
M |
Identity of the event that triggered the sending of the notification |
Location Information |
M |
Location information |
Timestamp |
O |
Timestamp of the location report |
NOTE 1: This is only used for location management server sends location information notification to the VAL user or VAL UE who has subscribed the location. NOTE 2: Either Identity or Subscription ID shall be included. |
9.3.2.8 Location reporting configuration cancel request
Table 9.3.2.8-1 describes the location reporting configuration cancel request information flow from the location management client or VAL server to the location management server.
Table 9.3.2.8-1: Location reporting configuration cancel request
Information element |
Status |
Description |
Identity |
M |
Identity of the requesting authorized VAL user or VAL UE or VAL server |
Identity |
M |
Identity of the requested VAL user or VAL UE |
VAL service ID |
O |
Identity of the VAL service for which the location reporting configuration is requested to be canceled. |
9.3.2.9 Get UE(s) information request
Table 9.3.2.9-1 describes the information flow for a VAL server to get UE(s) information at the LM server.
Table 9.3.2.9-1: Get UE(s) information request
Information element |
Status |
Description |
Location information |
M |
Location information around which the UE(s) information is requested (e.g. geographic area or VAL service area ID). |
Application defined proximity range information |
M |
Description of the range information over which the UE(s) information is required. |
9.3.2.10 Get UE(s) information response
Table 9.3.2.10-1 describes the information flow for a LM server to respond with UE(s) information to the VAL server.
Table 9.3.2.10-1: Get UE(s) information response
Information element |
Status |
Description |
Result |
M |
Result from the VAE server in response to subscription request indicating success or failure |
List of UEs information (see NOTE) |
O |
The information of the UEs which were detected in the application defined proximity range. The list can be empty. |
>UE ID |
M |
The identifier of UE |
>Location information |
M |
Location information of UE within the application defined proximity range |
NOTE: This IE shall be included when the Result indicates success. |
9.3.2.11 Monitor Location Subscription Request
Table 9.3.2.11-1 describes the information flow from the VAL server to the LM server for monitoring the location deviation of the VAL UE(s).
Table 9.3.2.11-1: Monitor Location Subscription Request
Information element |
Status |
Description |
Identity |
M |
Identifier of the VAL users or VAL UE whose location monitoring is requested to be monitored in a given location. |
Area of Interest |
M |
Geographic area location information where the VAL server wishes to monitor the VAL UE’s location adherence. This could be geographical co-ordinates or VAL service area identified by the VAL service area ID. |
Notify Interval |
M |
Periodic time interval in which the LM server needs to notify the VAL UE’s location information to the VAL server. |
Notification Target URI |
M |
Target URI where the VAL server wishes to receive the notifications about VAL UE’s location. |
Timeout |
O |
A timeout period when subscription response is not received. |
9.3.2.12 Monitor Location Subscription Response
Table 9.3.2.12-1 describes the information flow from LM server to the VAL server for Monitor Location Subscription Response.
Table 9.3.2.12-1: Monitor Location Subscription Response
Information element |
Status |
Description |
Subscription status |
M |
It indicates the subscription result |
9.3.2.13 Notify Location Monitoring Event
Table 9.3.2.13-1 describes the information flow from LM server to the VAL server for notification of location monitoring events.
Table 9.3.2.13-1: Notify Location Monitoring Event message
Information element |
Status |
Description |
Event |
M |
Information of the event to be reported. The event shall be one of the following: "Notify_Mismatch_Location" – When the location information of the VAL UE, from the location management client and the core network do not match. "Notify_Absence" – When the VAL UE’s current location is deviating from the VAL server’s area of interest information. "Notify_Presence" – When the VAL UE’s current location is within the VAL server’s area of interest information. |
Identity |
M |
Identifier of the VAL UE whose location information is reported. |
Location |
M |
Current location of the VAL UE. |
Editor’s note: It is FFS how the VAL Server’s area of interest information is related with the Area of Interest within 3GPP system defined by SA2.
9.3.2.14 Location area monitoring subscription request
Table 9.3.2.14-1 describes the information flow from the VAL server to the location management server for location area monitoring subscription request.
Table 9.3.2.14-1: Location information monitoring subscription request
Information element |
Status |
Description |
Identity |
M |
Identity of the requesting VAL server, VAL UE or SEAL Server |
Location Information criteria |
M |
Location information to be monitored. It includes the geographic location information or a VAL service area identified by the VAL service area ID or a reference UE along with the application defined proximity range from the reference UE. |
Time between consecutive reports |
O |
It indicates the interval time between consecutive reports |
Immediate Report Indicator |
O |
Indicates whether an immediate location report is required |
Triggering events |
O |
Identifies when the server will send the notification (e.g. distance travelled) |
9.3.2.15 Location area monitoring subscription response
Table 9.3.2.15-1 describes the information flow from the location management server to the VAL server for location area monitoring subscription response.
Table 9.3.2.15-1: Location area monitoring subscription response
Information element |
Status |
Description |
Subscription status |
M |
It indicates the subscription result |
Subscription identity |
O (see NOTE) |
If subscription is successful, identifies the subscription |
NOTE: This IE shall be present if subscription status is set to success. |
9.3.2.16 Location area monitoring notification
Table 9.3.2.16-1 describes the information flow from the location management server to the VAL server.
Table 9.3.2.16-1: Location area monitoring notification
Information element |
Status |
Description |
Subscription identity |
M |
Identity of the subscription |
UEs currently present (see NOTE) |
O |
List of the identities of all VAL UEs who are currently present in the given location area |
UEs moved in/out (see NOTE) |
O |
List of UEs either moved in to the location area or moved out of the location area |
>> UEs moved in |
O |
List of the identities of the VAL UEs who moved in to the given location area since previous notification. |
>> UEs moved out |
O |
List of the identities of the VAL UEs who moved out of the given location area since previous notification. |
Triggering event |
O |
Identity of the event that triggered the sending of the notification |
NOTE: Any one of these shall be present. |
9.3.2.17 Location area monitoring subscription modify request
Table 9.3.2.17-1 describes the information flow from the VAL server to the location management server for location area monitoring subscription modify request.
Table 9.3.2.17-1: Location information monitoring subscription modify request
Information element |
Status |
Description |
Identity |
M |
Identity of the requesting VAL server, VAL UE or SEAL Server |
Subscription identity |
M |
Identifies the subscription |
Location Information criteria |
M |
Location information to be monitored. It includes the geographic location information or a VAL service area ID or a reference UE along with the application defined proximity range from the reference UE. |
Time between consecutive reports |
O |
It indicates the interval time between consecutive reports |
Immediate Report Indicator |
O |
Indicates whether an immediate location report is required |
Triggering events |
O |
Identifies when the server will send the notification (e.g. distance travelled) |
9.3.2.18 Location area monitoring subscription modify response
Table 9.3.2.18-1 describes the information flow from the location management server to the VAL server for location area monitoring subscription modify response.
Table 9.3.2.18-1: Location area monitoring subscription modify response
Information element |
Status |
Description |
Subscription modification status |
M |
It indicates the request result |
9.3.2.19 Location area monitoring unsubscribe request
Table 9.3.2.19-1 describes the information flow from the VAL server to the location management server for location area monitoring unsubscribe request.
Table 9.3.2.19-1: Location information monitoring unsubscribe request
Information element |
Status |
Description |
Identity |
M |
Identity of the requesting VAL server, VAL UE or SEAL Server |
Subscription identity |
M |
Identifies the subscription |
9.3.2.20 Location area monitoring unsubscribe response
Table 9.3.2.20-1 describes the information flow from the location management server to the VAL server for location area monitoring unsubscribe response.
Table 9.3.2.20-1: Location area monitoring unsubscribe response
Information element |
Status |
Description |
Subscription status |
M |
It indicates the request result |
9.3.2.21 VAL service area configuration request
Table 9.3.2.21-1 describes the information flow from the the VAL server to the location management server for VAL service area configuration request.
Table 9.3.2.21-1: VAL service area configuration request
Information element |
Status |
Description |
Identity |
M |
Identity of the requesting VAL server |
VAL service area ID list |
M |
List of one or more VAL service area identifers |
Geographical co-ordinates list |
M |
List of one more more geographical co-ordinates corresponding to each VAL service area ID |
9.3.2.22 VAL service area configuration response
Table 9.3.2.22-1 describes the information flow from the location management server to the VAL server for VAL service area configuration response.
Table 9.3.2.22-1: VAL service area configuration response
Information element |
Status |
Description |
VAL Service area configuration status |
M |
It indicates the result of VAL service area configuration request. |
9.3.3 Event-triggered location reporting procedure
9.3.3.1 General
The location management server provides location reporting configuration to the location management clients, indicating what information the location management server expects and what events will trigger the sending of this information to the location management server. The decision to report location information can be triggered at the location management client by different conditions, e.g., the reception of the location reporting configuration, initial registration, distance travelled, elapsed time, cell change, MBMS SAI change, MBMS session change, leaving a specific MBMS bearer service area, tracking area change, PLMN change, call initiation, or other types of events such as emergency. The location report can include information described as ECGI, MBMS SAIs, geographic coordinates and other location information.
9.3.3.2 Fetching location reporting configuration
Figure 9.3.3.2-1 illustrates the procedure for fetching location reporting configuration.
Pre-condition:
– If multicast delivery mode is used, the MBMS bearer being used is activated by the location management server.
– The location management client is aware that the location reporting configuration is available at the location management server.
Figure 9.3.3.2-1: Fetching location reporting configuration procedure
1. The location management client sends location reporting configuration request message to the location management server.
2. The location management server sends location reporting configuration message to the location management client(s) containing the initial location reporting event triggers configuration (or a subsequent update) , e.g. minimum time between consecutive reports, SAI changes, or ECGI changes for reporting the location of the VAL UE. This message can be sent over a unicast bearer to a specific location management client or as a group message over an MBMS bearer to update the location reporting configuration for multiple location management clients at the same time.
NOTE 1: The location reporting configuration information can be made part of the user profile, in which case the sending of the message is not necessary.
NOTE 2: Different location management clients may be given different location reporting criteria.
3. The location management client stores or updates the location reporting event triggers configuration. A location reporting event occurs, triggering step 3.
9.3.3.3 Location reporting
Figure 9.3.3.3-1 illustrates the procedure for location reporting.
Figure 9.3.3.3-1: Location reporting procedure
1. The location management client sends a location information report to the location management server, containing location information identified by the location management server and available to the location management client.
2. Upon receiving the report, the location management server updates location of the reporting location management client. If the location management server does not have location information of the reporting location management client before, then just stores the reporting location information for that location management client.
9.3.4 On-demand location reporting procedure
The location management server can request UE location information at any time by sending a location information request to the location management client, which may trigger location management client to immediately send the location report.
Figure 9.3.4-1: On-demand location information reporting procedure
1. Based on configurations such as periodical location information timer, or location information request from other entities (e.g., another location management client, VAL server), location management server initiates the immediately request location information from the location management client.
2. The location management server sends a location information request to the location management client.
3. VAL user or VAL UE is notified and asked about the permission to share its location. VAL user can accept or deny the request
4. The location management client immediately responds to the location management server with a report containing location information identified by the location management server and available to the location management client.
5. Upon receiving the report, the location management server updates location of the reporting location management client. If the location management server does not have location information of the reporting location management client before, then just stores the reporting location information for that location management client.
9.3.5 Client-triggered or VAL server-triggered location reporting procedure
Figure 9.3.5-1 illustrates the high level procedure of client-triggered or VAL server-triggered location reporting.
Figure 9.3.5-1: Client-triggered location reporting procedure
1. Location management client 2 (authorized VAL user or VAL UE) or VAL server sends a location reporting trigger to the location management server to activate a location reporting procedure for obtaining the location information of location management client 1.
NOTE: Step 1 can be performed when Location management client 2 or VAL server require to update the location reporting trigger.
2. Location management server checks whether location management client 2 or VAL server is authorized to send a location reporting trigger. Depending on the information specified by the location reporting trigger, location management server initiates an on-demand location reporting procedure or an event-triggered location reporting procedure for the location of location management client 1.
3. Once the location information of the location management client 1 is available in the location management server by the on-demand location reporting procedure, a location information report is sent to the location management client 2 or VAL server.
9.3.6 Location reporting triggers configuration cancel
Figure 9.3.6-1 illustrates the procedure used for cancelling the location reporting triggers configuration at the target Location management client.
Pre-conditions:
1. The location management server has subscribed the location management client 2 location with the location reporting event triggers.
2. If multicast delivery mode is used, the MBMS bearer being used is activated by the location management server.
Figure 9.3.6-1: Location reporting triggers configuration cancel
1. The location management client 1 (authorized VAL user or VAL UE) or VAL server sends a location reporting configuration cancel request to the location management server (1a). The location management server sends the location reporting configuration cancel request to the location management client 2 to stop receiving the UE location information (1b). This message can be sent via unicast or multicast.
NOTE: Step 1b can be initiated without step 1a.
2. The location management client invalidates the location reporting triggers configuration and no longer reports its location to the location management server.
3. The location management client 2 sends the location reporting configuration cancel response to the location management server (3a) as an acknowledgement. The location management server sends the location reporting configuration cancel response to the location management client 1 (3b) as an acknowledgement.
9.3.7 Location information subscription procedure
Figure 9.3.7-1 illustrates the high level procedure of location information subscription request. The same procedure can be applied for location management client and other entities that would like to subscribe to VAL user or VAL UE location information. This procedure is also used for intiating tracking a UE’s location.
Figure 9.3.7-1: Location information subscription request procedure
1. The VAL server sends a location information subscription request to the location management server to subscribe location information of one or more VAL users or VAL UEs. The request may include an indication for supplementary location information.
2. The location management server shall check if the VAL server is authorized to initiate the location information subscription request. Further, the location management server may initiate location reporting configuration with the location management client of the UE for immediate reporting.
3. The location management server may optionally subscribe for UE location information from 3GPP core network for the UE. If the indication for supplementary location information is included in step 1, then UE location information is obtained from the 3GPP core network.
4. The location management server determines the UE location information of the UE as received in steps 3 and 4.
5. The location management server replies with a location information subscription response indicating the subscription status and if immediate reporting was requested, the location information of the VAL UE(s).
9.3.8 Event-trigger location information notification procedure
Figure 9.3.8-1 illustrates the high level procedure of event-trigger usage of location information. The same procedure can be applied for location management client and other entities that would like to subscribe to location information of VAL user or VAL UE. This procedure is also used for obtaining latest UE’s location for tracking purpose.
Figure 9.3.8-1: Event-trigger usage of location information procedure
1. The location management server receives the latest location information of the UE as per the location report procedure described in clause 9.3.3.3.
2. The location management server may optionally receive the location information of the UE from 3GPP core network. If the indication for supplementary location information is included in the subscription, then UE location information is obtained from the 3GPP core network.
3. Based on the configurations, e.g., subscription, periodical location information timer, location management server is triggered to report the latest user location information to VAL server. The location management server determines the location information of UE as received in steps 1 and 2, including the supplementary location information (if indicated).
4. The location management server sends the location information report including the latest location information of one or more VAL users or VAL UEs to the VAL server or to the location management client that has previously configured.
5. VAL server may further share this location information to a group or to another VAL user or VAL UE.
NOTE: For other entities, the step 5 can be skipped if not needed.
9.3.9 On-demand usage of location information procedure
The VAL server can request UE location information at any time by sending a location information request to the location management server, which may trigger location management server to immediately send the location report.
Figure 9.3.9-1 illustrates the high level procedure of on demand usage of location information. The same procedure can be applied for location management client and other entities that would like to subscribe to location information of VAL user or VAL UE.
Figure 9.3.9-1: On-demand usage of location information procedure
1. VAL server sends a location information request to the location management server.
2. The location management server acquires the latest location of the UEs being requested, by triggering an on-demand location report procedure as described in subclause 9.3.4, or from PLMN operator.
3. Then, location management server immediately sends the location information report including the latest location information acquired of one or more VAL users or VAL UEs.
4. VAL server may further share this location information to a group or to another VAL user or VAL UE.
NOTE: For other entities, the step 3 can be skipped if not needed.
9.3.10 Obtaining UE(s) information at a location
Figure 9.3.10-1 describes the procedure for obtaining UE(s) information at a location.
Pre-condition:
– The VAL server has a jurisdiction over a geographical area for which the location management server is configured to operate.
– The UE(s) in the geographical area have provided its location information to the location management server.
Figure 9.3.10-1: Obtaining UE(s) information at a location
1. The VAL server sends get UE information request to the location management server. The request contains a location information or VAL service area identified by the VAL service area ID and application defined proximity range.
2. The location management server determines the UE(s) whose location are within the application defined proximity range of the location information or VAL service area identified by the VAL service area ID provided in step 1.
3. The location management server sends get UE information response to the VAL server with a list of UE(s) and its corresponding location information as determined in step 1.
9.3.11 Monitoring Location Deviation
9.3.11.1 General
The VAL server requests the Location Management Server to monitor the location of the VAL UE in relation to an area of interest. The LMS fetches the VAL UE’s location information periodically from 3GPP core network as specified in 3GPP TS 23.502 [11] and also, using the Location Information procedures specified in clause 9.3.7 and clause 9.3.10. With the periodic location information of the UE from 3GPP core network and SEAL procedures, the LMS server evaluates the current location of the VAL UE in relation to the area of interest configured by the VAL server. If subscribed, the VAL server is notified by the LMS server when the VAL UE relationship (e.g. inside or outside) to the area of interest changes along with current location information of the VAL UE.
9.3.11.2 Monitoring Location Deviation procedure
Figure 9.3.11.2-1 describes the procedure for monitoring the VAL UE’s location in a given area of interest.
Pre-condition:
– The LMS server authorized to consume the 3GPP core network service (Monitoring events as specified in 3GPP TS 23.502 [11]).
Figure 9.3.11.2-1: Monitoring VAL UE’s location at a given location
1. The VAL server sends Monitor Location Subscription Request to LMS server including VAL UE Identifier, predetermined area of interest information, notification interval and notification URI where the VAL server intends to receive the notifications from LMS server regarding VAL UE’s presence in a given area.
– "Area of interest" is the location information, which the VAL server wishes to monitor the VAL UE’s location adherence. This parameter can include an area of interest information and other relevant parameters.
– "Notify_Interval" represents the periodic interval in which the LMS server needs to notify VAL UE’s location information to the VAL server. When the VAL UE moves away from the " Area of interest", then the LMS server ignores the "Notify_Interval" and sends the location notification to the VAL server immediately.
2. LMS processes the Area of interest information in the request, and then subscribes to UE location monitoring as specified in 3GPP TS 23.502 [11] with appropriate parameters mapping. Based on the subscription, the LMS receives the VAL UE location information periodically from the 3GPP core network.
Editor’s note: How the LMS’s processing of Area of Interest information and the subscription of UE location monitoring based on Area of Interest are related with procedures in 3GPP TS 23.502 and 3GPP TS 23.256 are FFS.
3. LMS shall use the Location information procedures as specified in clause 9.3.7 and clause 9.3.10, to periodically obtain the VAL UE location information. Based on the geographic information from the VAL server, the LMS server may determine to additionally include the positioning methods in SEAL LMS procedures to obtain location information.
4. LMS server, after successful subscription according to steps 2 and 3, sends Monitor Location Subscription response, indicating that the LMS server accepts VAL server’s request and will monitor the location of the VAL UE to verify if the VAL UE is in the area of interest.
5a and 5b. LMS server processes the location information received from SEAL Location Information procedures and the core network, and validates the information. If the location information is matching, then the LMS shall check if the VAL UE’s current location is within the area of interest received in step 1. The LMS will continue with step 6, step 7 and step 8 as applicable.
6. If the location information received from Location management client and the core network do not match, then the LMS server shall consider the VAL UE as outside from its specified area of interest and shall notify ("Notify Mismatch Location" message) the VAL server of the same, including VAL UE ID and the location information from LMS and the core network in the notification message.
7. If the VAL UE’s current location is from Location management client and the core network matches, and not in the area of interest received from VAL server in Monitor Location Subscription Request message, then the LMS considers the VAL UE as outside from its specified area of interest and shall notify the VAL server that the VAL UE’s current location is outside of area of interest and VAL UE ID in "Notify Absence" message.
8. When the VAL UE’s current location is in area of interest, then the LMS shall notify ("Notify Presence" message) the VAL server periodically, according to the "Notify_Interval" value in "Monitor Location Subscription Request" message, indicating the VAL server that the VAL UE is within the area of interest, along with VAL UE’s current location information.
9.3.12 Location area monitoring information procedure
9.3.12.1 Location area monitoring subscribe procedure
Figure 9.3.12.1-1 illustrates the high level procedure of location area monitoring subscription request. The same procedure can be applied for location management client and other SEAL servers that would like to subscribe to the list of UEs moving in or moving out of the specific location area. The subscribe request can be for a reference UE for which the subscriber is authorized to monitor location information.
Figure 9.3.12.1-1: Location area monitoring subscription procedure
1. The VAL server sends a location area monitoring subscription request to the location management server to subscribe to the list of UEs moving in or moving out of the specific location area. In the request message, the VAL server includes the information as specified in Table 9.3.2.14-1. The location information criteria may include the geographic location information or the VAL service area identified by the VAL service area ID where the UEs moving in or moving out to be monitored, or it may include reference UE information where in the UEs moving in or moving out of given application defined proximity range from the reference UE (target UE) to be monitored. The reference UE information may include VAL UE ID.
2. The location management server shall check if the VAL server is authorized to initiate the location area monitoring subscription request.
3. The location management server replies with a location area monitoring subscription response indicating the subscription status. In the response message, the location management server includes the information as specified in Table 9.3.2.15-1.
9.3.12.2 Location area monitoring subscribe modify procedure
Figure 9.3.12.2-1 illustrates the high level procedure of location area monitoring subscribe modify request. The same procedure can be applied for location management client and other SEAL servers that would like to modify the subscription to the list of UEs moving in or moving out of the specific location area. The subscribe modify request can be for a reference UE for which the subscriber is authorized to monitor location information.
Figure 9.3.12.2-1: Location area monitoring subscription modify procedure
1. The VAL server sends a location area monitoring subscription modify request to the location management server to modify the subscription to the list of UEs moving in or moving out of the specific location area. In the request message, the VAL server includes the information as specified in Table 9.3.2.17-1.
2. The location management server shall check if the VAL server is authorized to initiate the location area monitoring subscription modification request.
3. The location management server replies with a location area monitoring subscription modify response indicating the subscription status. In the response message, the location management server includes the information as specified in Table 9.3.2.18-1.
9.3.12.3 Location area monitoring unsubscribe procedure
Figure 9.3.12.3-1 illustrates the high level procedure of location area monitoring unsubscribe request. The same procedure can be applied for location management client and other SEAL servers that would like to unsubscribe to the list of UEs moving in or moving out of the specific location area. The unsubscribe request can be for a reference UE for which the subscriber is authorized to monitor location information.
Figure 9.3.12.3-1: Location area monitoring unsubscribe procedure
1. The VAL server sends a location area monitoring unsubscrbe request to the location management server to unsubscribe to the subscription to the list of UEs moving in or moving out of the specific location area. In the request message, the VAL server includes the information as specified in Table 9.3.2.19-1.
2. The location management server replies with a location area monitoring unsubscrbe response indicating the subscription status. In the response message, the location management server includes the information as specified in Table 9.3.2.20-1.
9.3.12.4 Location area monitoring notification procedure
Figure 9.3.12.4-1 illustrates the high level procedure of location area monitoring notification. The same procedure can be applied for location management client and other SEAL servers who have subscribe to the list of the UEs moving in or moving out of the specific location area.
Figure 9.3.12.4-1: Location are monitoring notification procedure
1. One of the events occurs at the location management server as specified in the subscribe request. The location management server identifies the UEs which are moved into the area or moved out of the area based on their location data and time stamp of the location. The LMS may report the list of all UEs in the given location or UEs moved in and moved out.
2. The location management server sends a location area monitoring notification to the VAL server. In the notification message, the location management server includes the information as specified in Table 9.3.2.16-1.
9.3.13 VAL Service Area configuration
9.3.13.1 General
The VAL service area refers to the geographical area served by a VAL server. The VAL server may have more than one VAL service area defined. These VAL service areas are configured by the VAL server to the location management server and and are assigned with the unique identifier. When the VAL service area configurations in place the VAL server may use the VAL service area ID as part of the location information in the SEAL APIs requiring location information. These configurations can be updated by the VAL server in-order to modify the geographical area associated with the VAL service area ID and when is updated, the SEAL internally manage the updates without requiring the VAL server to re-invoke the APIs where the updated VAL service area ID are being used.
9.3.13.2 Managing VAL service area configuration
Editor’s note: It is FFS how the updates to the VAL Service area ID are being handled by the SEAL layer.
9.4 SEAL APIs for location management
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 |
VAL server |
Request /Response |
SS_LocationInfoEvent |
Subscribe_Location_Info |
VAL server |
Subscribe/Notify |
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 |
Notify_Location_Monitoring_Events |
VAL server |
9.4.2 SS_LocationReporting API
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.
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.
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.
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.8
See subclause 9.3.6 for the details of usage of this API operation.
9.4.3 SS_LocationInfoEvent API
9.4.3.1 General
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
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
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
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.
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.
9.4.5 SS_LocationAreaInfoRetrieval API
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.
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.
9.4.6 SS_LocationMonitoring API
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.
9.4.6.2 Subscribe_Location_Monitoring
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.
9.4.6.3 Notify_Location_Monitoring_Events
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
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.
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.
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.
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.
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.
9.4.8 SS_VALServiceAreaConfiguration API
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 LM server.
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: 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)
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.
Editor’s note: Adding architecture requirement(s) for off-network location management is FFS.
Editor’s note: Charging aspects for off-network location management is FFS.
9.5.2 Information flows for off network location management
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. |
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. |
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.
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 |
Acknowledgement Required |
O |
If present, indicate the recipient of the message to acknowledge the message. |
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. |
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 |
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 |
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 |
9.5.3 Event-triggered location reporting procedure
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.
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.
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.
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