hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.30 VAL service area delete request
|
Table 9.3.2.30-1 describes the information flow from a VAL server to a location management for delete VAL service area identifiers at the location management server.
Table 9.3.2.30-1: Update VAL service area request
Information element
Status
Description
Identity
M
Indicates the VAL server identity.
List of VAL service IDs
M
List of one or more VAL service area identifiers that shall be deleted.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.31 VAL service area delete response
|
Table 9.3.2.31-1 describes the information flow from a location management server to the VAL server for delete VAL service area identifiers at the location management server.
Table 9.3.2.31-1: Update VAL service area response
Information element
Status
Description
Result
M
Indicates the success or failure for the operation.
VAL service area IDs
O
(see NOTE)
Indicates the list of the deleted VAL service area identifiers.
NOTE: This information element shall be present only if the delete VAL service area identifier(s) is successful.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.32 Location information unsubscribe request
|
Table 9.3.2.32-1 describes the information flow from the VAL server or location management client to the location management server for location information unsubscribe request.
Table 9.3.2.32-1: Location information unsubscribe request
Information element
Status
Description
Requestor ID
M
Identity of the VAL server or VAL UE’s requesting ID.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.33 Location information unsubscribe response
|
Table 9.3.2.33-1 describes the information flow from the location management server to the VAL server or location management client for location information unsubscribe response.
Table 9.3.2.33-1: Location information unsubscribe response
Information element
Status
Description
Request status
M
It indicates the unsubscribe request result
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.34 Monitor location unsubscribe request
|
Table 9.3.2.34-1 describes the information flow from the VAL server to the location management server for monitor location unsubscribe request.
Table 9.3.2.34-1: Monitor location unsubscribe request
Information element
Status
Description
Requestor ID
M
Identity of the VAL server’s requesting ID.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.35 Monitor location unsubscribe response
|
Table 9.3.2.35-1 describes the information flow from location management server to the VAL server for monitor location unsubscribe response.
Table 9.3.2.35-1: Monitor location unsubscribe response
Information element
Status
Description
Request status
M
It indicates the unsubscribe request result
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.36 Location service registration update request
|
Table 9.3.2.36-1 describes the information flow from the location management client to the location management server for update the registered location service.
Table 9.3.2.36-1: Location service registration update 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 service is updated.
Location capability
O
The information of location capability of VAL UE for which the location service is updated.
>Location access type
(NOTE 2)
O
(NOTE 1)
Identifies the updated location access type of the VAL UE. E.g. as described in TS 23.273[50] and TS 29.572[51].
>Positioning method
O
(NOTE 1)
Identifies the updated positioning methods of the VAL UE. E.g. as described in TS 23.273[50] and TS 29.572[51].
List of association IDs
O
(NOTE 3)
Identifies list of associations with other UEs may share the location information when they are at the same location.
NOTE 1: At least one of these rows shall be present.
NOTE 2: The non-3GPP access as defined in TS 23.273[50] and TS 29.572[51] is out of scope of the present specification.
NOTE 3: The association IDs are known to the UE based on offline methods and are out of scope of this specification. The requestor can be part of multiple associations and one association can have two or more UEs.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.37 Location service registration update response
|
Table 9.3.2.37-1 describes the information flow from the location management server to the location management client for the location service registration update response.
Table 9.3.2.37-1: Location service registration update response
Information element
Status
Description
Update status
M
It indicated the update result.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.38 Location service deregistration request
|
Table 9.3.2.38-1 describes the information flow from the location management client to the location management server for deregistration of the location service.
Table 9.3.2.38-1: Location service deregistration request
Information element
Status
Description
Identity
M
Identity of the VAL user or the VAL UE.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.39 Location service deregistration response
|
Table 9.3.2.39-1 describes the information flow from the location management server to the location management client for the location service deregistration response.
Table 9.3.2.39-1: Location service deregistration response
Information element
Status
Description
Deregistration status
M
It indicated the deregistration result.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.40 Location reporting configuration update request
|
Table 9.3.2.40-1 describes the information flow from the location management server to the location management client for the location reporting configuration update when location management server needs to deliver the new or update location reporting configuration to location management client if the location management server received the new requests/parameters from other entities (e.g. the VAL server or other location management client). This information flow may be sent individually addressed or group addressed on unicast or multicast.
Table 9.3.2.40-1: Location reporting configuration update request
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 1)
Identifies what location information is requested
Requested location access type
(see NOTE 2)
O
(see NOTE 1)
Identifies the location access type for which the location information is requested, e.g. as described in TS 23.273 [50] and TS 29.572 [51].
Requested positioning method
O
(see NOTE 1)
Identifies the positioning method for which the location information is requested, e.g. as described in TS 23.273 [50] and TS 29.572 [51].
Velocity requested indication
O
(see NOTE 3)
It indicates whether the velocity of the requested VAL users/UEs is needed.
Triggering criteria
O
(see NOTE 1)
Identifies when the location management client will send the location report as specified in table 9.3.2.4-2. The triggering may be e.g., SAI changes, ECGI changes, RAT changes.
Minimum time between consecutive reports
O
(see NOTE 1)
Defaults to 0 if absent otherwise indicates the time interval between consecutive reports
NOTE 1: If none of the information element is present, this represents a cancellation for location reporting.
NOTE 2: The non-3GPP access as defined in TS 23.273[50] and TS 29.572[51] is out of scope of the present specification.
NOTE 3: The definition of the velocity refers to 3GPP TS 23.271 [60].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.41 Location reporting configuration update response
|
Table 9.3.2.41-1 describes the information flow from the location management client to the location management server for the location reporting configuration update response. This information flow may be sent individually addressed or group addressed on unicast or multicast.
Table 9.3.2.41-1: Location reporting configuration update response
Information element
Status
Description
Update status
M
It indicates the update result.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.42 VAL service area subscription request
|
Table 9.3.2.42-1 describes the information flow from a SEAL server to a location management server to subscribe VAL service area identifier update events or update an existing subscription at the location management server.
Table 9.3.2.42-1: VAL service area subscription request
Information element
Status
Description
Identity
M
Indicates the SEAL server identity (see NOTE).
List of the subscribed events
M
Indicates the list of the requested events.
> Event type
M
Indicates the subscribed event (e.g., update/deletion of the VAL service area ID)
> VAL service area IDs
O
Indicates the list of the VAL service area identifiers. This information element shall be provided when the requested event type is update or delete VAL service area ID.
Notification Target URI
M
Target URI where the VAL server wishes to receive the notifications about VAL service area update events.
Subscription duration
O
It indicates the subscription duration.
NOTE: This information element shall not be updated via the update VAL service area subscription request.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.43 VAL service area subscription response
|
Table 9.3.2.43-1 describes the information flow from a location management server to a SEAL server for VAL service area subscription response or update VAL service area subscription response.
Table 9.3.2.43-1: VAL service area subscription response
Information element
Status
Description
Subscription status
M
It indicates the subscription result.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.44 VAL service area notification
|
Table 9.3.2.44-1 describes the information flow for VAL service area notification from a location management server to a SEAL server.
Table 9.3.2.44-1: VAL service area notification
Information element
Status
Description
List of events
M
Indicates the list of the occurred events.
> Event type
M
Indicates the subscribed event (e.g., update/deletion of the VAL service area ID).
> List of VAL service area information
M
List of one or more VAL service area identifiers.
>> VAL service area ID
M
The VAL service area identifier.
>> Geographical locations list
M
List of one more geographical locations (e.g., co-ordinates) corresponding to the VAL service area ID.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.45 VAL service area unsubscribe request
|
Table 9.3.2.45-1 describes the information flow from a SEAL server to a location management server for VAL service area unsubscribe request.
Table 9.3.2.45-1: VAL service area unsubscribe request
Information element
Status
Description
Identity
M
Indicates the SEAL server identity.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.46 VAL service area unsubscribe response
|
Table 9.3.2.46-1 describes the information flow from the location management server to the SEAL server for VAL service area unsubscribe response.
Table 9.3.2.46-1: Location information unsubscribe response
Information element
Status
Description
Request status
M
It indicates the unsubscribe request result.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.47 Adaptive location reporting configuration provisioning notification request
|
Table 9.3.2.47-1 describes the information flow from the location management server to the VAL server (or authorized SEAL LM client) for adaptive location reporting configuration provisioning.
Table 9.3.2.47-1: Adaptive configuration provisioning request
Information element
Status
Description
Requestor identity
M
Indicates the requestor identity (i.e., SEAL LMS).
UE identity
M
Indicates the VAL UE or VAL User identity
Proposed adaptive configuration
M
Indicates the proposed adaptive location configuration as described in table 9.3.2.4-2.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.48 Adaptive location reporting configuration provisioning notification response
|
Table 9.3.2.48-1 describes the information flow from the VAL server (or authorized SEAL LM client) to the location management server for adaptive location reporting configuration provisioning response.
Table 9.3.2.48-1: Adaptive configuration provisioning notification response
Information element
Status
Description
Result
M
Indicates the VAL server or authorized SEAL LM client decision, e.g., accept or reject.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.49 Location tracing configuration request
|
Table 9.3.2.49-1 describes the information flow from the VAL server to the location management server for creating the location tracing configuration.
Table 9.3.2.49-1: Location tracing 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 tracing configuration is requested.
Location area
O
Indicates the Geographic area location information where the VAL server wishes to query the UE history location data.
Location QoS
O
Definition of the location Quality of Service for which the location history information is requested.
Trigger condition
O
Indicates the event that trigger the sending of the location history report.
Time duration
O
Indicates the time till when the history location data needs to be stored.
Required positioning method
O
Indicates the requested positoning method to be used for the history location report.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.50 Location tracing configuration response
|
Table 9.3.2.50-1 describes the information flow from the location management server to the VAL server for the location tracing configuration response.
Table 9.3.2.50-1: Location tracing configuration response
Information element
Status
Description
Request status
M
It indicates the location tracing configuration request result.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.51 Location history request
|
Table 9.3.2.51-1 describes the information flow from the VAL server to the location management server for querying the location history information.
Table 9.3.2.51-1: Location history 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 history service is requested.
Requested location history information
O
The information for which the history location data is requested.
> Location area
O
Indicates the Geographic area where the VAL server wishes to query the UE history location data.
> Time
O
Indicates the time when the VAL server wishes to query the UE history location data.
> Time duration
O
Indicates the period during that the VAL server wishes to query the UE history location data.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.52 Location history response
|
Table 9.3.2.52-1 describes the information flow from the location management server to the VAL server for the location history response.
Table 9.3.2.52-1: Location history response
Information element
Status
Description
Identity
M
Identities of requested VAL users or VAL UEs.
Matched UE location history information
M
Identifies of UE location history data that matched the requested location history request from the VAL server.
Timestamp
O
Timestamp of the UE location report
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.53 Location tracing configuration cancel request
|
Table 9.3.2.53-1 describes the information flow from the VAL server to the location management server for cancelling the location tracing configuration.
Table 9.3.2.53-1: Location tracing configuration cancel 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 tracing configuration is requested.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.54 Location tracing configuration cancel response
|
Table 9.3.2.54-1 describes the information flow from the location management server to the VAL server for the location tracing configuration cancel response.
Table 9.3.2.54-1: Location tracing configuration cancel response
Information element
Status
Description
Cancel status
M
It indicates the location tracing configuration cancel request result.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.55 Surrounding UE retrieval request
|
Table 9.3.2.55-1 describes the information flow from the location management server to the location management client for obtaining surrounding UE information.
Table 9.3.2.55-1: Surrounding UE retrieval request
Information element
Status
Description
Identity
M
Identity of the requested VAL user or VAL UE
Surrounding UE retrieval method
O
Identify how to retrieve surrounding UE(s), e.g. ProSe, BT, WiFi
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.56 Surrounding UE retrieval response
|
Table 9.3.2.56-1 describes the information flow from the LM client to the LM server for sending the surrounding UE information.
Table 9.3.2.56-1: Surrounding UE retrieval response
Information element
Status
Description
Result
M
Indicates the success or failure result.
Identity list
O
List of VAL users or VAL UEs whose location is close to the requested VAL user or VAL UE.
Applicable only for the success result.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.57 Verify location sharing request
|
Table 9.3.2.57-1 describes the information flow from the location management server to the location management client to verify if it is sharing the same location with other UEs.
Table 9.3.2.57-1: Verify location sharing request
Information element
Status
Description
Identity
M
Identity of the requested VAL user or VAL UE.
VAL service ID
O
Identity of the VAL service that is requested.
Identity of sharing location
O
Indicates the list of identities of VAL UEs who share the same location with the requested VAL UE.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.58 Verify location sharing response
|
Table 9.3.2.58-1 describes the information flow from the location management client to the location management server to respond if it is sharing the same location with other UEs.
Table 9.3.2.58-1: Verify location sharing response
Information element
Status
Description
Identity
M
Identity of the requesting VAL user or VAL UE.
Request status
M
Indicates the request result.
Validity timer
O
Indicates the time duration when the response will be invalid.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.59 Location reuse request
|
Table 9.3.2.59-1 describes the information flow from the location management client to the location management server for enabling or disabling location reuse.
Table 9.3.2.59-1: Location reuse request
Information element
Status
Description
Identity
M
Identity of the requestor VAL UE.
VAL service ID
O
Identity of the VAL service for which the location service is registered.
Identity of UE-2
M
Identity of the VAL UE-2 who will reuse the location of UE-1.
Location reuse
M
Indicates whether to enable or disable reuse of location
Current location report
O
Location report of the UE-1 (as specified in Table 9.3.2.2-1)
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.60 Location reuse response
|
Table 9.3.2.60-1 describes the information flow from the location management server to the location management client for the location reuse response.
Table 9.3.2.60-1: Location reuse response
Information element
Status
Description
Result
M
Indicates success or failure of the request
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.61 SL positioning management subscription request
|
Table 9.3.2.61-1 describes the information flow from the VAL server to the location management server for SL positioning management subscription request.
Table 9.3.2.61-1: SL positioning management subscription request
Information element
Status
Description
Identity
M
Identity of the requesting VAL server.
VAL service ID
M
Identity of the VAL service (SL positioning service) for which the location information is subscribed.
VAL service area
O
The geographical area /zone or topological area (e.g. cells) for which the subscription applies.
VAL UE/user Identities list
O
List of VAL users or VAL UEs participating at the SL positioning service (reference and target VAL UEs).
VAL UE selection criteria
O
Selection criteria of UEs of different roles (e.g. reference UE).
Reporting configuration
M
It indicates the threshold and interval time between consecutive reports.
> Triggering criteria
O
If reporting is expected to happen based on certain conditions in future instance, this IE provides information on the conditions to trigger reporting.
SL positioning parameters
O
The SL positioning parameters to be reported (e.g. distance, direction or both), their frequency, and the permissions of the VAL UEs in the target service area.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.62 SL positioning management subscription response
|
Table 9.3.2.62-1 describes the information flow from the location management server to the VAL server for SL positioning management subscription response.
Table 9.3.2.62-1: SL positioning management subscription response
Information element
Status
Description
Subscription status
M
It indicates the subscription result which is success or failure.
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.63 SL positioning management notification
|
Table 9.3.2.63-1 describes the information flow from the location management server to the VAL server.
Table 9.3.2.63-1: SL positioning management notification
Information element
Status
Description
Subscription identity
M
Identity of the subscription.
Reference and target UE ID (s) and address
M
Identifies the list of UEs to serve as reference and target UEs.
List of Client UE IDs and addresses
O
The identities of the client UEs which are allowed to get ranging information for other UEs.
Triggering event
O
Identity of the event that triggered the sending of the notification (success or failure).
Reason
O
It indicates the failure reason for the notification report (e.g., "reference UE cannot be found").
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.64 SL positioning configuration command
|
Table 9.3.2.64-1 describes the information flow from the location management server to the location management clients or from LMC to VAL client.
Table 9.3.2.64-1: SL positioning configuration command
Information element
Status
Description
Identity
M
Identity of the requestor SEAL server or the subscriber VAL server
VAL service ID
M
Identity of the VAL service (SL positioning service)
VAL service area
M
The geographical area /zone or topological area (e.g. cells) for which the subscription applies.
VAL UE/user Identities list
M
List of VAL users or VAL UEs participating at the SL positioning service (reference and target VAL UEs).
SL positioning / Ranging configuration parameters
M
The configuration information for the SL positioning service. This includes the roles of the VAL UEs (reference or target) in the SL positioning service.
Reporting configuration
M
Indicates the threshold and interval time between consecutive reports expected from the target VAL UEs.
>Triggering criteria
O
If reporting is expected to happen based on certain conditions in future instance, this IE provides information on the conditions to trigger some reporting.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.65 Short-Range based positioning information request
|
Table 9.3.2.65-1 describes the information flow from the VAL server to the SEAL LMS for the Short-Range based positioning information request.
Table 9.3.2.65-1: Short-Range based positioning information request
Information element
Status
Description
Requestor Identity
M
Identity of the requestor (e.g. VAL server or SEAL LMS)
VAL service ID
O
Identity of the VAL service (ranging/SL positioning service) for which the ranging/SL positioning information is requested.
Requested Short-Range based positioning information
M
Indicates the requested Short-Range based positioning information (e.g. range, direction, relative position, relative velocity, etc.).
UE list
M
A list of reference UE identities that have been configured for ranging/SL positioning operation, including client, target, and reference UEs.
QoS requirement
O
The QoS requirement for the ranging/SL positioning operation.
Reporting events
O
Reporting event triggers as specified in table 9.3.2.4-1.
Expiration
O
The expiration for the Short-Range based positioning information request.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.66 Short-Range based positioning information response
|
Table 9.3.2.66-1 describes the information flow from the SEAL LMS to the VAL server for the Short-Range based positioning information response.
Table 9.3.2.66-1: Short-Range based positioning information response
Information element
Status
Description
Status
M
A status for the request: success, fail. If the status is fail, a failure code can be provided.
Short-Range based positioning information
O
(NOTE)
The Short-Range based positioning information associated with locations of UEs within the field of view of the target UE.
NOTE: This information element is present when the status for the request is success.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.67 Location subscription request
|
Table 9.3.2.67-1 describes the information flow from the location management server to the location management client for location information subscription request or for updating an existing location subscription.
Table 9.3.2.67-1: Location subscription request
Information element
Status
Description
Identity
M
Identity of the requesting VAL server/VAL user or VAL UE (see NOTE 1)
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
Location QoS
O
Definition of the location Quality of Service for which the location information is requested (see NOTE 2).
Requested location type
O
Indicate absolute or relative location information is requested
Requested positioning method
O
Indicates the positioning method for which the location information is requested, e.g., SL/Ranging.
NOTE 1: This information element shall not be updated via location information subscription update procedure in clause 9.3.7a.
NOTE 2: The definition of location QoS has been defined in clause 4.1b of 3GPP TS 23.273 [50] and the clause 6.1.6.2.13 of 3GPP TS 29.572 [51].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.68 Location subscription response
|
Table 9.3.2.68-1 describes the information flow from the location management server to the location management client for location subscription response or location subscription update response.
Table 9.3.2.68-1: Location 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
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.69 Location notification
|
Table 9.3.2.69-1 describes the information flow from the location management client to the location management server.
Table 9.3.2.69-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
Subscription ID
M
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 including e.g., absolute, location or relative location
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.70 Off-network location positioning configuration request
|
Table 9.3.2.70-1 describes the information flow from the LM server to the LM client for location area monitoring subscription request.
Table 9.3.2.70-1: Off-network location positioning configuration request
Information element
Status
Description
Identity
M
Identity of the requesting VAL server, VAL UE or SEAL Server
VAL service ID
O
Identity of the VAL service for which the location is requested (e.g.Geofencing).
Target UE identity(s)
M
Indicate the Identity of the VAL user or identity of the VAL UE whose history location is requested
Requested location type
M
Indicates the location information type (e.g., absolute location or relative location)
Location positioning triggers
M
Indicates the event (e.g., to initiate the off-network positioning
History location report triggers
M
Indicates the event (e.g., Uu connectivity is back) to report the history location result
Location QoS
O
Definition of the location Quality of Service for which the location information is requested
Requested positioning method
O
Indicates the positioning method for which the location information is requested, e.g., SL/Ranging.
Time duration
O
Indicates the time period when the off-network positioning and history location report is expected.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.71 Off-network location positioning configuration response
|
Table 9.3.2.71-1 describes the information flow from the LM client to the LM server for Off-network location positioning configuration response.
Table 9.3.2.71-1: Off-network location positioning configuration 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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.72 Off-network history location result report
|
Table 9.3.2.72-1 describes the information flow from the LM client to the LM server for Off-network history location result report.
Table 9.3.2.72-1: Off-network history location result report
Information element
Status
Description
Subscription identity
M
Identity of the subscription
UE location history information
M
Indicates the history location of the requested VAL UE/VAL user.
Timestamp
O
Timestamp of the UE location report
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.73 Confirm location service subscription request
|
Table 9.3.2.73-1 describes the information elements for the confirm location service subscription request from the VAL Server towards the location management server.
Table 9.3.2.73-1: Confirm location service subscription request
Information element
Status
Description
Identity
M
Identity of the requesting VAL server/VAL user
Application identifier/VAL service id
M
Application identifier for which is the subscription request/ Identity of the VAL service for which the confirm location service is subscribed.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.74 Confirm location service subscription response
|
Table 9.3.2.74-1 describes the information elements for the confirm location service subscription response from the location management server to the VAL Server.
Table 9.3.2.74-1: Confirm location service subscription response
Information element
Status
Description
Identity
M
Identity of the requesting VAL server/VAL user
Subscription status
M
It indicates the subscription result
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.75 Confirm location request
|
Table 9.3.2.75-1 describes the information elements for the confirm location request from the location management client to the location management server.
Table 9.3.2.75-1: Confirm location request
Information element
Status
Description
UE ID
M
The identifier of UE whose location information is to be confirmed
UE provided location
M
UE provided non-3GPP location information taken from functionality within UE (e.g. GNSS). It can include latitude and longitude, accuracy, timestamp.
Cell identifier
O
Cell identification information in the UE (NOTE)
Timestamp
M
Timestamp of the UE provided location
Application ID
M
Application identifier
NOTE: Cell identification information availability in LMC is depending on UE implementation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.76 Confirm location report
|
Table 9.3.2.76-1 describes the information elements for the confirm location request from the location management server to the location management client.
Table 9.3.2.76-1: Confirm location report
Information element
Status
Description
UE ID
M
The identifier of UE whose location information is to be confirmed
Confirm location status
M
unknown, verified, mismatch in the same country, mismatch in other country, roaming country mismatch, error unauthorized, error other (NOTE 1)
Cell identifier status (NOTE 2)
O
Connected to provided cell, not connected to provided cell
Timestamp
M
Timestamp of the confirm location check
Application ID
M
Application identifier
NOTE 1: Confirm location status granularity depends on the network capability.
NOTE 2: Cell identifier status is available when there is cell information provided in the confirm location request.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.77 Confirm location service usage notification
|
Table 9.3.2.77-1 describes the information elements for the confirm location service usage notification from the location management server to the VAL server.
Table 9.3.2.77-1: Confirm location service usage notification
Information element
Status
Description
Identity
M
Identity of the requesting VAL server/VAL user
UE ID
M
The identifier of UE whose location information was confirmed
Timestamp
O
Timestamp of the confirm location service notification
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.3 Event-triggered location reporting procedure
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
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, access RAT 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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.3.4 Update Location reporting configuration
|
The location management server may update the location reporting configuration information and inform the location management client of the update ones at any time by triggering the location reporting configuration update procedure.
Figure 9.3.3.4-1 illustrates the procedure for location reporting configuration update.
Figure 9.3.3.4-1: Location reporting configuration update procedure
1. Based on the local configurations or the location information request from other entities (e.g., another location management client, VAL server) or if the VAL server updates the geographical location information of the existing VAL service area ID and there is triggering criteria corresponding to the updated VAL service area ID, the location management server decides to update the location reporting configuration and informs the updated information to the location management client.
2. The location management server sends location reporting configuration update request message to the location management client(s) which may contain the updated location reporting configuration, e.g. the event triggers, the minimum time between consecutive reports, the requested location access type and positioning methods when VAL UE fetches the UE location report. 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. If the location reporting trigger from VAL server contains the triggering criteria based on the VAL service area ID, then the location management server converts those triggers into geographical area based triggers while sending it to the location management client.
NOTE: Different location management clients may be given different location reporting criteria.
3. The location management client(s) reply with location reporting configuration update response to the location management server with the update result.
4. The location management client stores or updates the new location reporting configuration received in step 2.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
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. If the target VAL UE ID or user ID is not equal to its own VAL UE or VAL User identity, the LM client triggers off-network location management procedures as described in clause 9.5 to obtain target VAL UE location. If the received UE positioning method is PC5 SEAL LM, target VAL UE location information (including velocity) is obtained via off-network procedure as defined in clause 9.5; if the received UE positioning method is non-3GPP (e.g. WiFi, BT), target VAL UE location information (including velocity) is obtained via the corresponding non-3GPP method. If SEAL LM client is unable to find the target VAL UE's location (either the target VAL UE has moved away, or required positioning method is not supported by target VAL UE) then SEAL LM client may send the failure message to the SEAL LM server. If the target VAL UE ID or user ID is equal to its own VAL UE or VAL user identity, 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 or the failure reason when the requested UE's location information cannot be obtained.
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
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. The location reporting event triggers as specified in table 9.3.2.4-1, e.g. minimum time between consecutive reports, SAI changes, access RAT changes, or ECGI changes for reporting the location of the VAL UE, are included.
NOTE: Step 1 can be performed when location management client 2 or VAL server require to update the location reporting trigger corresponding to location management client 1.
2. Location management server checks whether location management client 2 or VAL server is authorized to send a location reporting trigger. If the immediate report indicator is included or the triggering criteria is periodical reporting in step 1 and there is valid location report of the target UE (i.e. the timer for the stored location report is not expired), the location management server reuses the stored UE location report and sends the report to the location management client 2 or VAL server.
a. If the adaptive reporting is requested in step 1, the location management server interacts with NWDAF (e.g., UE mobility analytics as defined in clause 6.7.2 of 3GPP TS 23.288 [34]) to obtain the location management client 1 moving statistic and prediction
i. If "DIRECT UPDATE" is requested, the location management server determines the reporting configuration based on VAL service ID, VAL server ID, and the retrieved location management client 1 moving statistic and prediction. In order to adapt the configuration, the location management server may determine, for example, whether to increase or decrease the frequency of the report based on the UE's mobility pattern, or update location change condition (e.g., to change the location accuracy).
ii. If "SUGGESTIVE UPDATE" is requested, the location management server initially uses the configuration provided by VAL server and later dynamically adjusts the reporting configuration to determine adaptive location configuration based on VAL service ID, VAL server ID, and by analysing the retrieved location management client 1 moving statistic and prediction and received location information. In order to adapt the configuration, the location management server may determine, for example, whether to increase or decrease the frequency of the report based on the UE's mobility pattern, or update the location change condition (e.g., to change the location accuracy).
b. If the valid location report is not available, depending on the information specified by the location reporting trigger or determined reporting configuration (if "DIRECT UPDATE" is requested), 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.
Further, if adaptive reporting is enabled by the VAL server with "SUGGESTIVE UPDATE", the location management server dynamically adjusts the reporting configuration as specified above (in step 2.a.ii).
Once location configuration is adjusted and if it is required to update the triggers to the SEAL client, the SEAL LMS may suggest the adaptive location configuration to the VAL server (or authorized SEAL location management client) as specified in clause 9.3.19. If VAL server accepts the suggested adaptive location configuration, then the 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. If VAL server rejects the suggested adaptive location configuration, then the location management server will discard the updated configuration.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
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 initiating tracking a UE's location. The procedure considers target UE location information provided by its surrounding UEs, the procedure can improve location accuracy and can be used also for target UE temporarily out of 3GPP radio coverage. Location management client 1 is used as example in the figure as target UE that the VAL server is interested to know its location information.
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, the location QoS which contains the location accuracy, response Time and QoS class as defined in clause 4.1b of TS 23.273 [50], the velocity information of target UEs, and an indication whether the statistic of target UE location is needed per e.g., temporal/spatial granularity. If the indication whether the statistic of target UE location is needed, the corresponding time/location information should also be included. In addition, the VAL server may request velocity information of the VAL UEs/Users in step 1.
2. The location management server shall check if the VAL server is authorized to initiate the location information subscription request and may retrieve the available and proper location access type and positioning methods (e.g. as described in TS 23.273 [50] and TS 29.572 [51]) for the target VAL UE based on the received location QoS. Further, the location management server may initiate location reporting configuration optionally including the retrieved location access type and positioning methods 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 and/or the 3rd party location management server.
If the velocity information of target UE is requested in step 1, the location management server asks the location management client or 3GPP core network to report the target UE location data with the requested velocity information.
NOTE 1: How the location management server obtains the UE location from the 3rd party location management server is out of scope of this specification.
4. The location management server determines the UE location information of the UE as received in steps 2 and 3 and checks if it meets the location QoS requirements (if any) or not.
If the indication whether the statistic of target UE location is included in step 1, the location management server performs the following actions based on different granularity.
If the indication whether the statistic of target UE location is needed per temporal granularity is included in step 1, the location management server calculates the UE location data received in step 3 per the temporal granularity with the requested time condition.
If the indication whether the statistic of target UE location is needed per spatial granularity is included in step 1, the location management server calculates the UE location data received in step 3 per the spatial granularity with the requested location information.
5. The location management server may optionally request the UE location from its surrounding UEs (as described in step 5 to 9). The location management server decides how to retrieve surrounding UEs which may be based on location management client 1 registered positioning method in location service registration. If the location management server decides to use UE-assisted surrounding UE retrieval, step 6 is executed; otherwise, NW-assisted surrounding UE retrieval is used as described in step 7.
6. The location management server requests the location management client 1 with an optional surrounding UE retrieval method (e.g. ProSe, BT, WiFi) to provide its surrounding UEs and the location management client 1 responds the location management server with VAL UE/User ID of discovered UEs as described in clause 9.3.x;
NOTE 2: For ProSe capable UE, the User Info ID defined in 3GPP TS 23.586 [57] can represent VAL user ID. For Bluetooth capable UE, the Bluetooth MAC address can represent VAL UE ID. For WiFi Direct capable UE, the WiFi MAC address can represent VAL UE ID.
7a. The location management server derives an appropriate location area (where UE to UE communication is possible) internally using the location information of UE 1 (determined in step 4) as reference location. If the UE 1 location is last known UE location, the location management server uses UE mobility analytics service from 3GPP CN to derive UE location estimation for UE 1.
7b. The location management server uses 3GPP CN service (NEF service of Number of UEs present in a geographical area) to obtain all UEs within the derived location area in step 6.
8. The location management server selects a set of UEs (location management client 2..n) from UEs obtained in step 5 or step 7 based on registered location service information (e.g. positioning method) from location management client 2..n. Then location management server sends location request to location management client 2..n using On-demand location reporting procedure (as defined in clause 9.3.4) to obtain UE 1 location including an optional UE positioning method (e.g. PC5 SEAL LM, BT, WiFi) to be used to retrieve location.
NOTE 3: The location management server can, based on local policy, select an UE without LM registration and trigger location request to the UE. If so, the request can be ignored by the UE (e.g., if SEAL LM-UU service is not supported) or the UE can reject the request (if the required positioning method is not supported).
9. The location management server akes the location information of UE 1 reported by location management client 2..n into consideration to calibrate UE 1 location determined in step 4.
NOTE 4: It is assumed that different location information collected over different positioning method may have differences in accuracy. How location management server processes calibration is implementation specific.
10. 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).
NOTE 5: The VAL server can use obtained UE location and velocity in application specific ways (e.g. traffic monitoring in V2X).
9.3.7a Location information subscription update procedure
Figure 9.3.7a-1 illustrates the high level procedure for allowing a VAL server update an existing subscription about location information at the location management server.
Pre-conditions:
- the VAL server has an active location information subscription at the location management server.
Figure 9.3.7a-1: Location information subscription update procedure
1. When the VAL server decides to update an active location information subscription, it sends a location information subscription update request to the location management server including the information specified in table 9.3.2.5-1.
2. The location management server shall check if the VAL server is authorized to update the subscription.
3. If the VAL server is authorized to update the subscription, the location management server updates the location information subscription.
4. The location management server sends a location information subscription update response to the VAL server including the information as specified in table 9.3.2.6-1.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
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 and/or the 3rd party location management server network. If the indication for supplementary location information is included in the subscription, then UE location information is obtained from the 3GPP core network and/or the 3rd party location management server. If the velocity information of target UE is requested, the location management server asks the location management client or 3GPP core network to report the target UE location data with the requested velocity information.
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). The location management server may report the location to the VAL server considering the location information received via non-3GPP positioning technologies (e.g. GNSS, Bluetooth), for instance, to improve the location accuracy. The location management server may reuse the stored and valid UE location information (if any) to report to the VAL server/location management client to reduce the response time when the trigger condition is time-based (the triggering criteria is periodical reporting). And the LM server may interact with NWDAF to obtain the target UE’s prediction location as defined in clause 6.7.2 of 3GPP TS 23.288 [34] to report to the VAL server during the periodic time interval.
If the indication whether the statistic of target UE location is included in the request from the VAL server/location management client, the location management server calculates the received UE location data per temporal/spatial granularity as requested and then expose them to the VAL server/location management client for the valued-added location information.
4. Same as step 5-9 of Figure 9.3.7-1.
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. In addition, velocity of the requested VAL UEs may be included as part of the location information report.
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
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.
Pre-condition:
- The LM Server has confirmed the target UE is associated with other UEs and they are sharing the same location.
- The LM Server has obtained the UE’s location who is associated with the target 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 to request locations for one or more VAL UEs or VAL user(s) which may include the location QoS that contains the location accuracy, response Time and QoS class as defined in clause 4.1b of TS 23.273 [50].
2. The location management server checks if there is stored and valid UE location report (e.g. the timer for the stored UE location report is not expired) for the target UE. If available, it reuses the stored UE location information and reports it to the VAL server. If there isn’t, it 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, and checks if the obtained location of the VAL UE could meet the location QoS requirements (if any).
If the LM Server identified that target UE is associated with other UE(s) and they are sharing the same location as specified in clause of 9.3.23.2 or 9.3.23.3, it determines to reuse the associated UE's location data instead of obtaining the target UE's location data directly. The LM Server may select the associated UE(s) based on the requested LCS QoS, and the operator's policies, etc. But if the LM Server doesn’t store the associated UE's location data or the stored location data is invalid (e.g. the valid timer for the confirmation of sharing location information is expired, or the verify location sharing response is negative), the LM Server will ask the target UE to report the UE location data as described in clause 9.3.4.
3. Then, location management server immediately sends the location information report including the latest location information of associated UE(s) or acquired of target one or more VAL users or VAL UEs. The location management server may report the location to the VAL server considering the location information received via non-3GPP positioning technologies (e.g. GNSS, Bluetooth), for instance, to improve the location accuracy.
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 4 can be skipped if not needed.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
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. This procedure also applies for the Geofencing service that the VAL server may request the UE(s) information when the UE entering the Geofencing location area.
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.
- The location management server has obtained the requested UE location information either from 3GPP CN or the target location management client/VAL UE.
Figure 9.3.10-1: Obtaining UE(s) information at a location
1. The consumer (VAL server or group management server) sends get UE information request to the location management server. The request contains the location information (e.g. geographic area, VAL service area identified by the VAL service area ID, Geofencing location area represented by different types of shape, etc) and application defined proximity range as defined in table 9.3.2.9-1.
2. The location management server authorizes the request and determines the VAL UE(s) or VAL User(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 or Geofencing location area provided in step 1.
3. The location management server sends get UE information response to the VAL server with a list of VAL UE(s) or VAL user(s) and its corresponding location information as determined in step 1.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.11 Monitoring Location Deviation
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
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 location management 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 location management 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. The area of interest can be predefined or mobile where the latter one is used to support dynamic geofencing function.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
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 location management server authorized to consume the 3GPP core network service (Monitoring events provided by NEF 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 location management server including target VAL UE Identifier(s), predetermined or dynamic area of interest information, notification interval and notification URI where the VAL server intends to receive the notifications from LM server regarding target VAL UE's presence in a given area, interested notification information, dynamic geofencing conditions.
- "Area of interest" is the location information, which the VAL server wishes to monitor the target VAL UE's location adherence. This parameter can include an area of interest information and other relevant parameters. In the case of dynamic area of interest, it includes a reference VAL UE Identifier and its proximity range.
- "Notify_Interval" represents the periodic interval in which the location management server needs to notify target VAL UE's location information to the VAL server. When the target VAL UE moves away from the "Area of interest", then the location management server ignores the "Notify_Interval" and sends the location notification to the VAL server immediately.
- "dynamic geofencing conditions" includes a temporal condition(s) (e.g. time of day and day of week), connectivity condition(s) (e.g. operator information, roaming status, access type) and/or a spatial condition(s) (e.g. location area(s)), VAL UE capability (e.g. battery power), consent (e.g. to serve as reference VAL UE for a time period) for the reference VAL UE. For instance, the monitoring is valid when a reference VAL UE is served by operator A without using satellite in location area X from 7:00am to 9:00am on working days.
2. If dynamic area of interest information and dynamic geofencing conditions are received, the location management server requests 3GPP CN (e.g. NEF service for location, access type and roaming status monitoring as specified in 3GPP TS 23.502 [11]) to monitor the reference VAL UE location change, access type change and roaming status change, in order to determine spatial dynamicity in area of interest related to the target UE(s). If spatial condition is received, the location management server also requests 3GPP CN (i.e. NEF service for area of interest monitoring as specified in 3GPP TS 23.502 [11]) to know whether the reference VAL UE is in the VAL server's predetermined area (e.g. PLMN x). The location management server will process the monitoring considering the received dynamic geofencing conditions for the reference UE.
3. If dynamic area of interest information is received, the location management server requests 3GPP CN (i.e. NEF service for loss of connectivity as specified in 3GPP TS 23.502 [11]) for both target UE(s) and reference UE.
4a. Location management server processes the Area of interest information in the request, and then subscribes to target VAL UE location monitoring as specified in 3GPP TS 23.502 [11] with appropriate parameters mapping. Based on the subscription, the location management server receives the target VAL UE location information periodically from the 3GPP core network. The LM server also invokes NEF service for Area of Interest monitoring as specified in clause 5.3.3 of 3GPP TS 23.256 [52] to know whether the target VAL UE is in the VAL server's predetermined or dynamic area of interest.
4b. LM server shall use the Location information procedures as specified in clause 9.3.7 and clause 9.3.10 to periodically obtain the target VAL UE location information. Based on the geographic information from the VAL server, the LM server may determine to additionally include the positioning methods in SEAL LMS procedures to obtain location information.
4c. LMS may periodically obtain the target VAL UE location information from the 3rd party location management server based on the geographic information from the VAL server.
4d. LM server may configure the off-network position and report policy to the target VAL UE and/or reference VAL UE as described in clause 9.3.21.4.1 when they still have connectivity. This is to initiate the UE-only Operation SL/Ranging as described in 3GPP TS 23.586 [57], cache the location, and report the location result when the connectivity is back. Time duration is included if the dynamic geofencing conditions is specified in step 1.
NOTE 1: How the LMS obtains the target VAL UE location from the 3rd party location management server is out of scope of this specification.
NOTE 2: Step 4a to 4d are performed for each target VAL UE if multiple target VAL UE identifiers are provided by the VAL server.
5. Location management server, after successful subscription according to steps 2~4, sends Monitor Location Subscription response, indicating that the location management server accepts the VAL server's request and will monitor the location of the target VAL UE(s) to verify if the target VAL UE(s) is in the area of interest.
NOTE 3: Either step 6 or step 7 is performed if it is notified about loss of connectivity for the reference VAL UE and target VAL UE(s).
6. The location management server requests the target VAL UE to obtain the reference UE's location information (i.e., the absolute location or the relative location).
NOTE 4: In this figure, it assumes the reference VAL UE lost connectivity and the target VAL UE still has the connectivity. If the target VAL UE lost connectivity and the reference VAL UE has the connectivity, location management server requests the reference VAL UE to obtain the target VAL UE's location information.
6a. The location management server determines the reference VAL UE lost connectivity and the target VAL UE still has the connectivity, the location management server sends location subscription request to the target VAL UE. The reference VAL UE identity and the Ranging/SL positioning method, location type (i.e., the absolute location or the relative location) are included. The location management client in the target VAL UE returns a location subscription response.
6b. The target VAL UE initiates the Ranging/SL based MO-LR procedure as described in clause 6.20 of 3GPP TS23.273 [50] to obtain the reference VAL UE location information. The target VAL UE obtains the reference UE's location information.
6c. The target VAL UE sends the location notification with the reference UE's location information.
7. Alternatively, the LM server requests the target UE's location information from the core network. The core network initiates the Ranging/SL based MT-LR procedure as described in clause 6.20 of 3GPP TS 23.273 [50] and obtains the target VAL UE location information.
8. Location management server processes the location information received from SEAL Location Information procedures, the 3GPP core network and/or the 3rd party location management server, and validates the information. If the location information is matching, then the Location management server shall check if the VAL UE's current location is within the predetermined or dynamic area of interest received in step 1.
NOTE 5: The location information received from the 3GPP core network and from location management client does not necessarily be exactly the same, the location management server can aggregate the location information if there is no big deviation.
Location management server verifies its determined target VAL UE location status (i.e. presence or absence with regard to the predetermined area of interest) with the retrieved 3GPP core network result from the NEF monitoring service for Area of Interest. The location management server will continue with step 7, step 8 and step 9 as applicable.
9a. If the location information received from location management client, the 3GPP core network and/or the 3rd party location management server do not match or the NEF reported Area of Interest monitoring result does not match with the determined target VAL UE location status (present/absence) in location management server, then the location management server shall consider the target VAL UE as outside from its specified area of interest and shall notify ("Notify Mismatch Location" message) the VAL server of the same, including target VAL UE ID and the location information from location management server, the 3GPP core network and/or the 3rd party location management server in the notification message.
9b. If the target VAL UE's current location is from location management client, the 3GPP core network and/or the 3rd party location management server matches, and either not in the predetermined area of interest received from VAL server in Monitor Location Subscription Request message or not within the proximity range of the reference UE, and such out of area of interest result is also aligned with the NEF reported area of interest monitoring result, then the location management server considers the target VAL UE as outside from its specified area of interest and shall notify the VAL server that the target VAL UE's current location is outside of area of interest and target VAL UE ID in "Notify Absence" message.
If either the target VAL UE or the reference VAL UE lost connectivity, the location management server determines the target VAL UE is outside the predetermined area of interest or dynamic area of interest as follows.
- If the target VAL UE lost connectivity, and the target VAL UE's current absolute location is obtained in step 6 or step 7, the LMS server determines the target VAL UE is outside the predetermined area of interest according to the target VAL UE's absolute location. The location management server determines the target VAL UE is not within the proximity range of the reference VAL UE based on the reference UEs' location obtained in step 4 and the target VAL UE's absolute location in step 6 or step 7.
- If the target VAL UE lost connectivity, and target VAL UE's current relative location is obtained in step 6, the LM server determines the target VAL UE is not in the predetermined area of interest or not within the proximity range of the reference VAL UE based on the reference VAL UEs' location obtained in step 4 and the target VAL UE's absolute location in step 6 or step 7.
- If the reference VAL UE lost connectivity, and the reference VAL UE's absolute location or relative location is obtained instep 6 or step 7, the location management server determines the target VAL UE is not within the proximity range of the reference VAL UE based on the reference VAL UEs' location obtained in step 4 and the target VAL UE's absolute location in step 6 or step 7.
The LM server notifies the VAL server "Notify Absence" message.
9c. When the target VAL UE's current location is either in the predetermined area of interest or in the proximity range of the reference UE, and such in area of interest result is also aligned with the NEF reported area of interest monitoring result, then the LM server 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 target VAL UE is within the area of interest, along with target VAL UE's current location information.
If either the target VAL UE or the reference VAL UE lost connectivity, the LM server determines the target VAL UE is within the predetermined area of interest or dynamic area of interest as follows.
- If the target VAL UE lost connectivity, and the target VAL UE's current absolute location is obtained in step 6 or step 7, the LMS server determines the target VAL UE is within the predetermined area of interest according to the target VALUE’s absolute location. The LM server determines the target VAL UE is within the proximity range of the reference VAL UE based on the reference VAL UEs' location obtained in step 4 and the target VAL UE’s absolute location in step 6 or step 7.
- If the target VAL UE lost connectivity, and target VAL UE's current relative location is obtained in step 6 or step 7, the LM server determines the target VAL UE is within the predetermined area of interest or within the proximity range of the reference VAL UE based on the reference VAL UEs’ location obtained in step 4 and the target UE's absolute location in step 6 or step 7.
- If the reference VAL UE lost connectivity, and the reference VAL UE's absolute location or relative location is obtained in step 6 or step 7, the LM server determines the target VAL UE is within the proximity range of the reference VAL UE based on the reference VAL UEs’ location obtained in step 4 and the target VAL UE's absolute location in step 6 or step 7.
And the location management server shall notify the VAL server "Notify Presence" message.
9d. If the location management server is notified by the 3GPP CN about loss of connectivity for the reference VAL UE and target VAL UE(s), or fails to obtains the target VAL UE's location or the reference UE' location in step 6 or step 7 (e.g., due to the target VAL UE and reference VAL UE are beyond the Ranging/SL range) or fails to select an alternative reference VAL UE in case of dynamic geofencing, considering the location of the target VAL UEs, then the location management server notifies ("Notify Unknown" message with detailed reason) the VAL server indicating that the location management server does not know whether the target VAL UE/reference VAL UE is "Presence" or “Absence", therefore the dynamic geofencing monitoring for the impacted target UE(s) is suspended.
NOTE 6: Upon "Notify Unknown", the VAL server can remind end user to check status for the reference/target UE, which is out of 3GPP scope.
NOTE 7: Notifications in step 9 can be subject to explicit notification indication from the VAL server, for instance, the VAL server can be interested to know only "Notify Absence" and "Notify Unknown".
NOTE 8: How the location management server selects an alternative reference UE in case of dynamic geofencing, in case of loss of connectivity of the initial reference VAL UE is out of scope of the current release of the specification.
10. If both the target VAL UE and/or reference VAL UE lost the connectivity, the off-network target VAL UE and/or reference VAL UE initiate the UE-only Operation SL/Ranging as described in 3GPP TS 23.586 [57] or the procedure as defined in clause 9.5.3 and clause 9.5.4, and cache the location result as configured in step 4d.
11. If the connectivity is back, the target VAL UE and/or reference VAL UE check whether it is still within the valid duration if configured. If yes, the the target UE and/or reference VAL UE report the cached history location to the location management server as described in clause 9.3.21.4.2.
12. The location management server may use the cached history location e.g., to notify the VAL server about the history target VAL UE location status during the loss of connectivity.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.12 Location area monitoring information procedure
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.12.1 Location area monitoring subscription 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 subscription request can be for a reference UE for which the subscriber is authorized to monitor location information.
The procedure is also applied for Geofencing service which initiated via VAL server to subscribe to the location management server to report the Geofencing monitoring events.
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.
If the VAL server initiates the subscription for the Geofencing service, the Geofencing monitoring events (i.e. the UEs moving in/out of the pre-defined location area, the number of UEs moving in/out of the pre-defined location area, the time period of UEs enter/leave the pre-defined location area) may be included in the request message as specified in Table 9.3.2.14-1.
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.12.2 Location area monitoring subscription modify procedure
|
Figure 9.3.12.2-1 illustrates the high level procedure of location area monitoring subscription 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.
The procedure is also applied for Geofencing service that the VAL server modifies the subscription to the location management server to report the Geofencing monitoring events.
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 or the Geofencing monitoring events. 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 modify 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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
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.
The procedure is also applied for Geofencing service that the VAL server unsubscribes to the location management server to report the Geofencing monitoring events.
Figure 9.3.12.3-1: Location area monitoring unsubscribe procedure
1. The VAL server sends a location area monitoring unsubscribe 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 or the Geofencing monitoring events. 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 unsubscribe 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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
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.
The procedure is also applied for Geofencing service which requests the location management server to report the Geofencing monitoring events.
Figure 9.3.12.4-1: Location area 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 the received UEs 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.
When the Geofencing service is triggered, the location management server also checks whether the UE is inside/outside the area based on the location information criteria as defined in Table 9.3.2.14-1 and the received UE location data. Further, the LM Server statistics and reports the Geofencing monitoring events (e.g. the list of UEs moving in/out of the location area, the number of UEs moving in/out of the location area, the time period of UEs enter/leave the location area, etc.) to the VAL server.
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.
If the location management server didn't obtain any UE location information due to UE issues or network issues in step 1, it informs the VAL server with the proper reason (e.g., "UE cannot be connected") in the notification report.
3. After received the Geofencing information report from the location management server, the VAL server may take some actions to inform the VAL UE (e.g. send the alarms or warnings to the UE).
NOTE: The step 3 is out of 3GPP scope.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.13 VAL Service Area configuration
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.13.1 General
|
The VAL service area refers to the geographical area(s) (e.g., coordinates, civic addresses, network areas) served by a VAL server. The VAL service area is identified by the VAL service area identifier (ID). 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 are assigned with a unique VAL service area identifier. When the VAL service area configurations are 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(s) associated with the VAL service area 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 are being used.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.13.2 Configure VAL service area identifier procedure
|
Figure 9.3.13.2-1 illustrates the high level procedure of the VAL service area identifier configuration.
Figure 9.3.13.2-1: Configure VAL service area identifier procedure
1. The VAL server sends the VAL service area configuration request to the location management server to configure a new VAL service area identifier. In the request message, the VAL server includes the information as specified in table 9.3.2.21-1.
2. The location management server shall check if the VAL server is authorized to initiate VAL service area identifier configuration request.
3. If the VAL server is authorized to configure the VAL service area identifiers, the VAL server checks the consistency of the provided identifiers (e.g., all VAL service area identifiers shall be unique) and configures the provided VAL service area identifiers.
4. the location management server sends the VAL service area configuration response with the information as specified in table 9.3.2.22-1.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.13.3 Obtain VAL service area identifier procedure
|
Figure 9.3.13.3-1 illustrates the high level procedure of the VAL service area retrieval.
Figure 9.3.13.3-1: Obtain VAL service area procedure
1. The VAL server sends the VAL service area obtain request to the location management server to retrieve the VAL service area identifiers. In the request message, the VAL server includes the information as specified in table 9.3.2.26-1.
2. The location management server shall check if the VAL server is authorized to initiate VAL service area obtain request.
3. If the VAL server is authorized to obtain the VAL service area identifiers, the location management server sends the VAL service area obtain response with the information as specified in table 9.3.2.27-1.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.13.4 Update VAL service area identifier procedure
|
Figure 9.3.13.4-1 illustrates the high level procedure of the VAL service area update.
Figure 9.3.13.4-1: Update VAL service area procedure
1. The VAL server sends the VAL service area update request to the location management server to update the VAL service area identifier(s) configured by the VAL server. In the request message, the VAL server includes the information as specified in table 9.3.2.28-1.
2. The location management server shall check if the VAL server is authorized to initiate VAL service area update request.
3. The location management server checks whether the VAL service area IDs exist and then updates the VAL service area identifier(s).
4. The location management server sends the VAL service area update response with the information as specified in table 9.3.2.29-1.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.13.5 Delete VAL service area identifier procedure
|
Figure 9.3.13.5-1 illustrates the high level procedure of the VAL service area delete.
Figure 9.3.13.5-1: Delete VAL service area procedure
1. The VAL server sends the VAL service area delete request to the location management server to delete the VAL service area identifier(s) configured by the VAL server. In the request message, the VAL server includes the information as specified in table 9.3.2.30-1.
2. The location management server shall check if the VAL server is authorized to initiate VAL service area delete request.
3. The location management server checks whether the VAL service area IDs exist and then deletes the VAL service area identifier(s).
NOTE: An deletion of the VAL service area ID(s) does not affect the existing subscriptions in the SEAL layer.
4. The location management server sends the VAL service area delete response with the information as specified in table 9.3.2.31-1.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.13.6 VAL service area identifier subscribe procedure
|
Figure 9.3.13.6-1 illustrates the high level procedure of the subscribe VAL service area update events.
Figure 9.3.13.6-1: Subscribe VAL service area procedure
1. The SEAL server sends the VAL service area subscription request to the location management server to subscribe for the VAL service area identifier(s) update events. In the request message, the SEAL server includes the information as specified in table 9.3.2.42-1.
2. The location management server shall check if the SEAL server is authorized to susbcribe for the VAL service area identifier(s) update event(s).
3. if the SEAL server is authorized to subscribe for the VAL service area identifier(s) update events, the location management server creates the subscription based on the provided parameters in the request.
4. The location management server sends the VAL service area subscription response with the information as specified in table 9.3.2.43-1.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.13.7 VAL service area identifier notify procedure
|
Figure 9.3.13.7-1 illustrates the high level procedure for notification of a SEAL server about the VAL service area identifier update events at the location management server.
Pre-conditions:
- the SEAL server has an active VAL service area subscription at the location management server; and
- the subscribed event has occurred.
Figure 9.3.13.7-1: Notify VAL service area procedure
1. The location management server identifies the list of the occurred events for which the SEAL server subscribed.
2. The location management server sends a VAL service area notification to the SEAL server. In the notification message, the location management server includes the information as specified in table 9.3.2.44-1.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.13.8 VAL service area identifier unsubscribe procedure
|
Figure 9.3.13.8-1 illustrates the high level procedure for a SEAL server to unsubscribe the notifications about the VAL service area identifier update events at the location management server.
Pre-conditions:
- the SEAL server has an active VAL service area subscription at the location management server.
Figure 9.3.13.8-1: Unsubscribe VAL service area procedure
1. When the SEAL server decides to terminate a VAL service area subscription, it sends a VAL service area unsubscribe request to the location management server. In the request message, the SEAL server includes the information as specified in table 9.3.2.45-1.
2. If the SEAL server is authorized to terminate the subscription, the location management server terminates the VAL service area subscription.
3. The location management server sends a VAL service area unsubscribe response to the SEAL server, the location management server includes the information as specified in table 9.3.2.46-1.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.13.9 VAL service area identifier subscription update procedure
|
Figure 9.3.13.9-1 illustrates the high level procedure of the update subscription for the VAL service area update events.
Figure 9.3.13.9-1: VAL service area identifier subscription update procedure
1. The SEAL server sends the VAL service area subscription update request to the location management server to update the existing subscription for the VAL service area identifier(s) update events. In the request message, the SEAL server includes the information as specified in table 9.3.2.42-1.
2. The location management server shall check if the SEAL server is authorized to update the subscription for the VAL service area identifier(s) update event(s).
3. if the SEAL server is authorized, the location management server checks whether the target susbcription exists and then updates the subscription for the VAL service area identifier(s) update events.
4. The location management server sends the VAL service area subscription update response with the information as specified in table 9.3.2.43-1.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.14 Location profiling for supporting location service enablement
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.14.1 Location profiling
|
The location management server enhanced with the Fuse Location Function(FLF) supports the creation of location profiles for location service at the application enablement layer and the mapping of location profiles to one or more vertical applications. Location profiling is based on the vertical driven hybrid positioning requirements and policies.
The example of attributes that can be used for the location profiles is specified in Annex D.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.14.2 Procedure of Location profiling for location service
|
The procedure includes the translation of the vertical request to a location profile and the derivation of the requested location information report.
Pre-condition: The location management server has configured a set of location service profiles.
Figure 9.3.14.2-1: Location profiling for location derivation and exposure
1. The location management server receives a location reporting trigger from VAL server and activates a location reporting procedure as defined in clause 9.3.5.
2. The fused location function determines a mapping of the vertical location services to a location service profile based on the location request information, the location profiles and the location capability of VAL UE which registered to the location management server before.
3a. The location management server requests from the LMC the location information of the target VAL UE optionally with the requested location information (the access type, positioning method) based on the determined location profiles in location management server obtained in step 2.
3b. The location management client responds to the location management server the location report based on the request.
4. The location management server performs a location information request to one or more of the following (based on the location profile):
- to GMLC directly or via NEF (as defined in TS 23.273 [50]), acting as AF.
- to 3rd party location servers.
5. The fused location function calculates the location information based on combined location reports from step 3~4 and checks whether the location reports fulfil the location profile requirements.
6-7. If the requirements are not fulfilled, the location management server will repeat the step 3~5 iteratively to request location information and re-check whether the requirements are met or not.
8. If the requirements are fulfilled, the location management server sends the location information report to the VAL server.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.15 Location service registration procedure
|
Before the location management server requesting the location information for the target UE, the location management client may register the available location services to the location management server to report the UE's location capabilities.
Figure 9.3.15-1 illustrates the procedure of client-triggered location service registration.
Figure 9.3.15-1: Location service registration procedure
1. The location management client of a VAL UE sends location service registration request to the location management server, with the identifier of the UE (e.g. GPSI) and UE-based location capabilities, the associated ID with other UEs, etc.
2. The location management server checks authorization for the VAL UE's registration request.
3. After successful authorization, location management server sends location service registration response to the location management client and stores the UE's information received in step 1.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.16 Location information unsubscribe procedure
|
Figure 9.3.16-1 illustrates the high level procedure of location information unsubscribe request. The same procedure can be applied for the location management client and other entities that would like to unsubscribe to the VAL UE's location information.
Figure 9.3.16-1: Location information unsubscribe procedure
1. The VAL server sends location information unsubscribe request to the location management server to unsubscribe the subscription to the VAL UE's location information.
2. The location management server replies with location information unsubscribe response indicating the unsubscribe status.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.17 Monitor location unsubscribe procedure
|
Figure 9.3.17-1 illustrates the high level procedure of location monitoring unsubscribe request. The same procedure can be applied for other entities that would like to unsubscribe the subscription to monitor the VAL UE's location in a given area of interest.
Figure 9.3.17-1: Monitor location unsubscribe procedure
1. The VAL server sends Monitor location unsubscribe request to the location management server to unsubscribe the subscription to monitor the VAL UE's location in a given area of interest.
2. The location management server replies with Monitor location unsubscribe response indicating the unsubscribe status.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.18 Location service registration update procedure
|
Figure 9.3.18-1 illustrates the procedure of client-triggered location service registration update. The location management client may update its supported location capabilities (e.g. location access type, position methods) which has registered to the location management server before.
Pre-condition:
The location management client has registered to the location management server.
Figure 9.3.18-1: Location service registration update procedure
1. The location management client decides to trigger the registration update request to location management server to update the location capabilities which have registered to the location management server before.
2. The location management client sends location service registration update request to the location management server with the identifier of the VAL UE, the VAL service ID and updated location capabilities.
3. The location management server checks the authorization for the VAL UE's registration update request. If the authorization is successful, the location management server will update the UE's location capabilities received in step 2.
4. The location management server sends location service registration update response to the location management client.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.19 Location service deregistration procedure
|
Figure 9.3.19-1 illustrates the procedure of client-triggered location service deregistration. By deregistration, the location management client may deregister the available location services which have registered to the location management server before.
Pre-condition:
The location management client has registered to the location management server.
Figure 9.3.19-1: Location service deregistration procedure
1. The location management client decides to trigger the deresgistration request to location management server to deregister the location services which have registered to the location management server before.
2. The location management client sends location service deregistration request to the location management server with the identifier of the UE.
3. The location management server sends location service deregistration response to the location management client and removes all registration information of the UE.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.20 SEAL location management server provides adaptive configuration
|
Figure 9.3.20-1 illustrates procedure for SEAL LMS to provide adaptive location configuration suggestion to the VAL server for the VAL UE for which VAL server has requested for adaptive reporting (as specified in clause 9.3.5).
NOTE: The procedure is applicable to SEAL location management client-2 (as specified in above clause 9.3.5) if SEAL location management client-2 has requested adaptive reporting.
Pre-conditions:
1. The VAL server has requested to SEAL LMS to suggest adaptive configuration for VAL UE;
2. The VAL server has provided endpoint information in the Location reporting trigger to the SEAL LMS.
3. The SEAL LMS has received location reports from SEAL client and based on the different information the SEAL LMS as determined the new/adaptive location configuration.
Figure 9.3.20-1: Adaptive location reporting configuration provisioning
1. The SEAL LMS sends a message to the VAL server (or authorized SEAL location management client). The message includes UE identity and suggested updates for location reporting trigger configuration.
2. Upon receiving the request from the SEAL LMS, the VAL server (or authorized SEAL location management client) sends a response message. The response message includes whether the VAL server accepts or rejects the updated location reporting configuration suggestion or not. If the VAL server accepts the location reporting configuration as suggested by the SEAL LMS, then the SEAL LMS updates the location reporting configuration to the SEAL location management client of the target UE.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.21 Location history querying procedure
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.21.1 Location tracing configuration create procedure
|
Figure 9.3.21.1-1 illustrates the high level procedure of creating location tracing configuration from VAL server to the location management server.
Figure 9.3.21.1-1: Location tracing configuration procedure
1. The VAL server sends a location tracing configuration request to the location management server to configure the location tracing service in advance. The location tracing configuration request may contain the geographical area for history location tracing, events/conditions for triggering the location history report, location QoS, the identities for the UE and service, the time till when the SEAL LM needs to store the location history data and the required positioning method(s) , etc.
NOTE: Step 1 can be also performed when the VAL server requires updating the location tracing configuration corresponding to location management server.
2. The location management server checks whether the VAL server is authorized to request the location tracing configuration service. If the request is approved, the location management server stores the configuration received in step 1. If the request includes multiple UEs, the location management server creates and stores the contexts for each UE.
3. The location management server sends the location tracing configuration responses to the VAL server.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.21.2 Location history request procedure
|
Figure 9.3.21.2-1 illustrates the high level procedure of location history request which the VAL server triggers to query the history location data for some specific UEs in some specific conditions.
Pre-conditions:
1. The location management server has obtained the UE location data from multiple sources as defined in clause 9.3.3 and clause 9.3.5 periodically based on the event triggers or conditions received in the request of step 1 in clause 9.3.21.1.
Figure 9.3.21.2-1: Location history request procedure
1. The VAL server sends a location history request to the location management server with the specific conditions (e.g. the given location area, time/period, etc.) to query the history location data for a single UE or multiple UEs.
2. The location management server checks the authorization for the request. If the request is authorized, the location management server matches the obtained UE location data with the location history request. Before the match, the location management server may transform the obtained UE location data into the same format of the location area information received in step 1 if needed.
3. The location management server sends a location history response to the VAL server with the matched UE location information. If there is no matched UE location data, the failure reason can be included.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.21.3 Location tracing configuration cancel procedure
|
Figure 9.3.21.3-2 illustrates the high level procedure of location tracing configuration cancel request which the VAL server triggers to cancel the location tracing configuration for a single UE or multiple UEs.
Figure 9.3.21.3-2: Location tracing configuration cancel procedure
1. If the VAL server decides to stop the location tracing services for the UE(s), it sends a location tracing configuration cancel request to the location management server with the UE identities.
2. The location management server stops getting the UE's location and deletes the stored UE location data and the location tracing configuration for the service.
3. The location management server sends location tracing configuration cancel response to the VAL server.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.21.4 Off-network history location result retrieve
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.21.4.1 Off-network location positioning configuration
|
Figure 9.3.21.4.1-1 illustrates the high level procedure of provisioning the off-network location positioning and report configuration from location management server to the location management client. This procedure is also used to update the configuration.
Figure 9.3.21.4.1-1: Off-network location positioning configuration
1. The location management server sends an Off-network location positioning and report configuration request to the location management client to configure the off-network location positioning and report policy to be used later. The request includes events/conditions for triggering the location history report, requested location type (i.e., absolute location or relative location), location QoS, the required positioning mechanism (i.e., UE-only Operation SL/Ranging), time duration for the off-networking positioning and report.
NOTE: Step 1 can be also performed when the LM server requires updating the configuration corresponding to location management client.
2. The location management client checks whether the VAL server is authorized to configure off-network location positioning and report policy. If the request is approved, the location management client stores the configuration received in step 1.
3. The location management server sends the Off-network location positioning and report configuration response to the location management server.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.21.5.2 Off-network history location result report
|
Figure 9.3.21.5.2-1 illustrates the high level procedure of reporting the cached history location result to the location management server.
Pre-condition:
- The location management client is configured with the off-networking location positioning and report policy.
Figure 9.3.21.5.2-1: Off-network history location result report
1. The Off-network location positioning trigger is met, e.g., the reference VAL UE which hosts the location management client detects it is in off-network and the target VAL UE identified by the target UE identity is also in off-network.
2. The location management client checks whether it is within the valid period as indicated by the time duration if configured. If yes, the location management client initiates the UE-only Operation SL/Ranging as described in 3GPP TS 23.586 [57], obtains its own location or the target VAL UE location, and caches the location result with time stamp. This step may be performed periodically as configured.
3. When the connectivity is back and it is within the valid period as indicated by the time duration, the location management client sends the Off-network history location result to the location management server.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.22 Surrounding UEs retrieval procedure
|
Figure 9.3.22-1 illustrates the procedure of surrounding UE(s) retrieval. The location management server can use this procedure to know how many UE(s) are close to the requested UE hosting the location management client, and their identities.
Figure 9.3.22-1: Surrounding UE(s) retrieval procedure
1. The location management server decides to Surrounding UE retrieval request to the location management client. The request may include surrounding UE retrieval method.
2. The location management client obtains UE(s) close to itself. The location management client considers the surrounding UE retrieval method (if received) during the obtaining procedure.
3. The location management client sends its surrounding UE(s) to the location management server in Surrouding UE retrieval response.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.23 Optimization location service for multiple UEs that sharing the same location
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.23.1 General
|
If multiple VAL UEs share the same location area with each other, when the VAL server requests the location information for each UE among them, the location management server will select one or several of them to obtain the location data instead of triggering all of UE's positioning procedure, which could reduce the signaling messages, save energy and power consumption, etc.
The following are the procedures to describe the related functions for such scenario.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.23.2 Procedure of LM Server identifying if the UEs sharing the same location
|
Figure 9.3.23.2-1 describes the procedure that how location management server identifies the UEs that sharing the same location.
Pre-condition:
- The VAL UE1 and VAL UE2 are associated and may belong to the same user or different users.
- The location management client 1(in VAL UE1) and location management client 2(in VAL UE2) have reported the location capabilities (e.g. associated ID) for VAL UE1 and VAL UE2 to location management server respectively as defined in clause 9.3.15.
NOTE: The associated ID for VAL UE1 and VAL UE2 is same.
Figure 9.3.23.2-1: Procedure of LM Server identifying the UEs that sharing the same location
1. The location management server identifies the registered location management client1 and location management server client 2 are associated and may share the same location with each other based on the received location service registration information (e.g. same associated ID as defined in clause 9.3.15). Then it further verifies if they are sharing the same location at present.
2. The location management server initiates the verify location sharing request to the location management server client 1 with the user ID of location management client 2 to verify if they are sharing the same location.
NOTE: The step 2 may occur after the location management server receives the location request to the location management client 2 from the VAL server.
3. The location management client 1 checks if the location management client 2 is close enough and shares the same location via the following ways.
- The location management client 1 may trigger the location reporting to the location management client 2 via some positioning capabilities (e.g., Prose) and receive off-network location report from the location management client 2 and determines that the VAL UE2 is within allowed proximity range of the VAL UE1 as specified in step 1 of clause 9.3.23.3.
- The location management client 1 may ask the VAL user to check if VAL UE1 and VAL UE2 are in the same location. If the answer is yes, the VAL user may inform the location management client 1 that the VAL UE1 and VAL UE2 are in the same location area.
4. The location management server client 1 sends the verify location sharing response to the location management server with the confirmation of sharing same location with location management client 2, and the validity timer is also included to indicate the valid duration for the confirmation.
Before the validity timer expired, if the location management client 1 discovers the location management client 2 is far away from itself and they are not able to share the same location, the location management client 1 will inform the location management server they are no long sharing the same location as specified in step 2(disable) of clause 9.3.23.3.
If the response is negative (e.g. the location management client 1 confirms the location management client 2 is not close with location management client 1 or the location management client 1 can't confirm whether both of UEs are closing enough), the location management server will not reuse the stored UE1's location for UE2.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.23.3 Location reuse request
|
Figure 9.3.23.3-1 illustrates the procedure of client-triggered enable location reuse request.
Pre-condition:
1. All UEs in the association are registered to share the location.
2. UE has configured other UEs in the association to received offline location reports as specified in clause 9.5.3.
3. The VAL UE1 and VAL UE2 are associated and may belong to the same user or different users.
4. The LM Client 1(in VAL UE1) and LM Client 2(in VAL UE2) have reported the location capabilities (e.g. associated ID) for VAL UE1 and VAL UE2 to LM server respectively as defined in clause 9.3.15.
Figure 9.3.23.3-1: Location reuse procedure
1. The SEAL LMC-1 (in UE-1) receives off-network location report from the SEAL LMC-2 (in UE-2). Based on location report, if UE-2 is within certain range of UE-1, the SEAL LMC-1 determines that the UE-2 is within allowed proximity range of the UE-1 (i.e. UE-1 and UE-2 are close enough) and so UE-1's location can be used by SEAL LMS instead of UE-2's location.
Based on location report, if UE-2 is out of certain range of UE-1, the SEAL LMC-1 determines that the UE-2 is outside allowed proximity range of the UE-1 (i.e. UE-1 and UE-2 are not close enough) and so UE-1's location can not be used by SEAL LMS instead of UE-2's location.
2. The SEAL LMC-1 (in UE-1) sends location reuse request message to the SEAL LMS to enable reuse of location of UE-1 for UE-2. If both UE1 and UE2 are close enough (i.e. within allowed proximity range), the request includes indication to enable reuse of location of UE-1 for UE-2. If both UE1 and UE2 are not close enough (i.e. outside allowed proximity range), the request includes indication to disable reuse of location of UE-1 for UE-2. The request message also includes VAL user’s identity, identity of VAL UE-1, identity of UE-2 and latest location report of UE-1.
3. The SEAL LMS authenticates and authorizes the user. If authorized, the SEAL LMS identifies that if SEAL LMC-1 and SEAL LMC-2 are associated (e.g. same associated ID) or not based on the received registration information of SEAL LMC-1 and SEAL LMC-2, and if reusing of location is allowed of not.
4. If both UE-1 and UE-2 are assocaited and reusing of location is allowed (as determined in step-3), then the SEAL LMS stores the location of UE-1. If the request includes indication to enable reuse of location of UE-1, the SEAL LMS enables reuse of location of UE-1 for UE-2. If the request includes indication to disable reuse of location of UE-1, the SEAL LMS disables reuse of location of UE-1 for UE-2. The SEAL LMS sends response back to the SEAL LMC-1.
When location reuse is enabled, if location request for UE-2 is received from VAL server, the SEAL LMS reuses and provides the location of UE-1 (instead of location of UE-2) to the VAL server. When location reuse is disable, if location request for UE-2 is received from VAL server, the SEAL LMS provides the location of UE-2 only (instead of reusing location of UE-1) to the VAL server.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.24 Support for sidelink positioning / ranging management
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.