Content for TS 23.434 Word version: 19.4.2
0…
6…
8…
9…
9.3…
9.3.3…
9.3.8…
9.3.13…
9.3.20…
9.3.23…
9.4…
10…
10.3…
10.3.3…
10.3.7…
10.4…
11…
12…
13…
14…
14.3…
14.3.3
14.3.4
14.3.4A…
14.3.4A.5…
14.3.4A.8…
14.3.5…
14.3.9…
14.4…
15…
17…
18…
A…
9.3 Procedures and information flows for Location management (on-network)
9.3.1 General
9.3.2 Information flows for location information
...
...
9.3 Procedures and information flows for Location management (on-network) p. 52
9.3.1 General p. 52
Location information of VAL service user shall be provided by the location management client to the location management server. The location information reporting triggers are based on the location reporting configuration. Different type of location information can be provided.
9.3.2 Information flows for location information p. 52
9.3.2.0 Location reporting configuration request p. 52
Table 9.3.2.0-1 describes the information flow from the location management client to the location management server for requesting the location reporting configuration.
| Information Element | Status | Description |
|---|---|---|
| Identity | M | Identity of the VAL user or identity of the VAL UE |
| VAL service ID | O | Identity of the VAL service for which the location reporting configuration is requested. |
9.3.2.1 Location reporting configuration response p. 52
Table 9.3.2.1-1 describes the information flow from the location management server to the location management client for the location reporting configuration. This information flow may be sent individually addressed or group addressed on unicast or multicast.
| 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 and TS 29.572. |
| 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 and TS 29.572. |
| Requested velocity information | O
(see NOTE 1) | Identifies the velocity of the target UE for which the location information is requested. |
| 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 12:
|
||
9.3.2.2 Location information report p. 53
Table 9.3.2.2-1 describes the information flow from the location management client to the location management server for the location information reporting or from the location management server to the requesting location management client or VAL server to report location information.
| Information Element | Status | Description |
|---|---|---|
| Set of identities | M | Set of identities of the reporting VAL users or VAL UEs |
| Triggering event | M | Identity of the event that triggered the sending of the report. The triggering event may be e.g., SAI changes, ECGI changes, RAT changes. |
| Location Information | M | Location information. For LM-UU reference point, it may include UE location information via non-3GPP positioning technologies (e.g. GNSS, Sensor, TBS, WLAN, Bluetooth) as described in TS 37.355. |
| Velocity information | O
(NOTE 1) | Velocity information of the reporting VAL users or VAL UEs. |
| Failure Reason | O
(NOTE 2) | Indicates the failure reason when the LM Client cannot obtain the requested UE's location information (e.g. the target VAL UE has moved away, or required positioning method is not supported by target VAL UE). |
| Timestamp | O | Timestamp of the location report |
|
NOTE 1:
The definition of the velocity refers to TS 23.271.
NOTE 2:
This element is only applicable when the Location information IE is null.
|
||
9.3.2.3 Location information request p. 53
Table 9.3.2.3-1 describes the information flow from the VAL server to the location management server and/or from the location management server to the location management client for requesting an immediate location information report.
| Information Element | Status | Description |
|---|---|---|
| Identity list | M | List of VAL users or VAL UEs whose location information is requested |
| VAL service ID | O | Identity of the VAL service for which the location information is requested. |
| Requested location information | O | Identifies what location information is requested |
| Requested location access type
(NOTE 4) | O
(NOTE 1) | Identifies the location access type for which the location information is requested, e.g. as described in TS 23.273 and TS 29.572. |
| Requested positioning method | O
(NOTE 1) | Identifies the positioning method for which the location information is requested, e.g. as described in TS 23.273 and TS 29.572. If the requested VAL user/UE is not the receiving VAL user/UE hosting the location management client, the UE positioning method includes PC5 SEAL LM, BT, WiFi. |
| Location QoS | O
(NOTE 3) | Definition of the location Quality of Service for which the location information is requested (see NOTE 2). |
| Velocity requested indication | O
(NOTE 5) | It indicates whether the velocity of the requested VAL users/UEs is needed. |
| List of association IDs | O
(NOTE 6) | Identifies list of associations with other UEs may share the location information when they are at the same location. |
|
NOTE 1:
This element is only applicable for request sent from the location management server to the location management client.
NOTE 2:
The definition of location QoS has been defined in clause 4.1b of TS 23.273 and the clause 6.1.6.2.13 of TS 29.572.
NOTE 3:
The element is only applicable for the information flow from the VAL server to the location management server.
NOTE 4:
The non-3GPP access as defined in TS 23.273 and TS 29.572 is out of scope of the present specification.
NOTE 5:
The definition of the velocity refers to TS 23.271.
NOTE 6:
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.
|
||
9.3.2.4 Location reporting trigger p. 54
Table 9.3.2.4-1 describes the information flow from the location management client or VAL server to the location management server for triggering a location reporting procedure.
| Information Element | Status | Description |
|---|---|---|
| Requestor Identity | M
(see NOTE 1) | Identity of the requesting authorized VAL user or VAL UE or VAL server |
| Identity | M
(see NOTE 1) | Identity of the requested VAL user or VAL UE |
| VAL service ID | O | Identity of the VAL service for which the location reporting trigger is set. |
| Immediate Report Indicator | O
(see NOTE 2) | Indicates whether an immediate location report is required |
| Requested location information | O
(see NOTE 2) | Identifies what location information is requested. This information element may be represented as VAL service area ID(s) when this information flow from VAL server to the location management server. |
| Triggering criteria | O
(see NOTE 2) | Identifies when the requesting client/VAL server is expecting to receive the location report from the requested VAL user/ VAL UE as specified in Table 9.3.2.4-2. |
| Minimum time between consecutive reports | O
(see NOTE 2) | Defaults to 0 if absent otherwise indicates the interval time between consecutive reports |
| Endpoint information | O | Information of the endpoint of the requesting VAL server to which the location report notification has to be sent. It is provided if Immediate Report Indicator is set to required. |
| Adaptive reporting | O |
It indicates the request for an adaptive location reporting by dynamically adjusting the configuration. Following are possible values:
|
|
NOTE 1:
The identity of the requesting VAL user/UE/VAL server and the requested VAL user/UE should belong to the same VAL service.
NOTE 2:
At least one of these rows shall be present.
|
||
| Information element | Status | Description |
|---|---|---|
| Frequency of reporting | O | It indicates the requested frequency of reporting. The reporting frequency may be periodic or event-triggered. |
| Reporting periodicity | O | If the Frequency of reporting is periodic, the reporting periodicity shall be provided. |
| Location change condition | O
(see NOTE) | It indicates the location change condition when the reporting shall occur, e.g., VAL user or VAL UE changes a cell, NodeB, TA, RA, WLAN access network, civic address, GPS coordinates, SAI, ECGI, RAT, VAL service area. If the Frequency of reporting is event-triggered, this IE shall be provided. |
| Inside or outside indication | O
(see NOTE) | It indicates the condition when the reporting shall occur, i.e., the VAL user or VAL UE is inside or outside the locations represented by the VAL service area ID(s). |
| Reporting schedule | O | It indicates the requested reporting schedule, e.g., days of the week and/or time period for the location reporting. |
|
NOTE:
Triggering criteria based on the VAL service area represented by the VAL service area ID(s) may be provided when this information flow is from the VAL server to the location management server.
|
||
9.3.2.5 Location information subscription request p. 56
Table 9.3.2.5-1 describes the information flow from the VAL server or location management client to the location management server for location information subscription request or for updating an existing location information subscription.
| Information Element | Status | Description |
|---|---|---|
| Identity | M | Identity of the requesting VAL server/VAL user or VAL UE (see NOTE 3). |
| 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. |
| Supplementary location information indication | O | Indicates that supplementary location information is required. |
| Location QoS | O
(NOTE 2) | Definition of the location Quality of Service for which the location information is requested (see NOTE 1). |
| Indication for the location data statistic | O | It indicates whether the statistic/calculation of target UE location data is needed per e.g. time/location. |
| Requested time information | O
(NOTE 4) | It indicates the time information when the target UE location data is calculated per time. |
| Requested location information | O
(NOTE 4) | It indicates the location information when the target UE location data is calculated per location. |
| Velocity indication | O | It indicates whether velocity of the requested VAL users/UEs is needed. |
|
NOTE 1:
The definition of location QoS has been defined in clause 4.1b of TS 23.273 and the clause 6.1.6.2.13 of TS 29.572.
NOTE 2:
The element is only applicable for the information flow from the VAL server to the location management server.
NOTE 3:
This information element shall not be updated via location information subscription update procedure in clause 9.3.2.7a.
NOTE 4:
This information element only applies when the indication for the statistic of target UE location data is included.
|
||
9.3.2.6 Location information subscription response p. 57
Table 9.3.2.6-1 describes the information flow from the location management server to the VAL server or location management client for location information subscription response or location information subscription update response.
| Information Element | Status | Description |
|---|---|---|
| Identity | M | Identity of the requesting VAL server/VAL user or VAL UE |
| Subscription status | M | It indicates the subscription result |
9.3.2.7 Location information notification p. 57
Table 9.3.2.7-1 describes the information flow from the location management server to the VAL server or the location management client.
| Information Element | Status | Description |
|---|---|---|
| Identities list | M | List of the VAL users or VAL UEs whose location information needs to be notified |
| Identity (see NOTE 2) | O | Identity of the VAL user or VAL UE subscribed to location of another VAL user or VAL UE (see NOTE 1) |
| Subscription ID (see NOTE 2) | O | Subscription identity related to VAL server subscription with location management server for location information notification. |
| Triggering event | M | Identity of the event that triggered the sending of the notification |
| Location Information | M | Location information |
| Velocity information | O | Indicates the velocity of the target UE for which the location information is requested. |
| Statistic of location data | O | Indicates the statistic result of target UE location data per temporal/spatial granularity as requested. |
| Timestamp | O | Timestamp of the location report |
|
NOTE 1:
This is only used for location management server sends location information notification to the VAL user or VAL UE who has subscribed the location.
NOTE 2:
Either Identity or Subscription ID shall be included.
|
||
9.3.2.7a Void
9.3.2.8 Location reporting configuration cancel request p. 58
Table 9.3.2.8-1 describes the location reporting configuration cancel request information flow from the location management client or VAL server to the location management server or from the location management server to the location management client.
| Information Element | Status | Description |
|---|---|---|
| Identity | M | Identity of the requesting authorized VAL user or VAL UE or VAL server |
| Identity | M | Identity of the requested VAL user or VAL UE |
| VAL service ID | O | Identity of the VAL service for which the location reporting configuration is requested to be cancelled. |
9.3.2.9 Get UE(s) information request |R17| p. 58
Table 9.3.2.9-1 describes the information flow for a VAL server to get UE(s) information at the location management server.
| Information Element | Status | Description |
|---|---|---|
| Location information | M | Location information around which the UE(s) information is requested (e.g. geographic area or VAL service area ID). The information is also used for Geofencing service. |
| > Shape type | O | It includes the Geofencing location area represented by different types of shape (e.g., polygon or circle) as defined in TS 29.572. |
| > Area Coordinates | O | Geographical coordinates of shape as defined in TS 29.572. |
| Application defined proximity range information | M | Description of the range information over which the UE(s) information is required. |
9.3.2.10 Get UE(s) information response |R17| p. 59
Table 9.3.2.10-1 describes the information flow for a LM server to respond with UE(s) information to the VAL server.
| Information Element | Status | Description |
|---|---|---|
| Result | M | Result from the VAE server in response to subscription request indicating success or failure |
| List of UEs information (see NOTE) | O | The information of the UEs which were detected in the application defined proximity range. The list can be empty. |
| > UE ID | M | The identifier of VAL UE or VAL user. |
| > Location information | M | Location information of UE within the application defined proximity range |
| > VAL service ID | O | Indicates the VAL service identified associated with UE ID information flow. |
|
NOTE:
This IE shall be included when the Result indicates success.
|
||
9.3.2.11 Monitor Location Subscription Request |R17| p. 59
Table 9.3.2.11-1 describes the information flow from the VAL server to the location management server for monitoring the location deviation of the VAL UE(s) or for updating an existing monitor location subscription.
| Information Element | Status | Description |
|---|---|---|
| Target Identity | M | Identifier of the target VAL users or VAL UEs whose location monitoring is requested to be monitored in a given location (see NOTE). |
| Area of Interest | M | Geographic area location information where the VAL server wishes to monitor the VAL UE's location adherence. This could be geographical co-ordinates or VAL service area identified by the VAL service area ID. Alternatively, it includes identifier of the reference VAL user or VAL UE and its proximity range. |
| Notify Interval | M | Periodic time interval in which the location management server needs to notify the target VAL UE's location information to the VAL server. |
| Notification Target URI | M | Target URI where the VAL server wishes to receive the notifications about target VAL UE's location. |
| Timeout | O | A timeout period when subscription response is not received. |
| Interested notification information | O | One or more interested notification events (e.g. Notify Absence, Notify Presence, Notify Mismatch Location and Notify Unknown) the VAL server can subscribe to. |
| Dynamic geofencing conditions | O | Temporal, connectivity and/or spatial conditions for the reference VAL UE. |
|
NOTE:
This information element shall not be updated via monitor location subscription update procedure in clause 9.3.2.12a.
|
||
9.3.2.12 Monitor Location Subscription Response |R17| p. 59
Table 9.3.2.12-1 describes the information flow from location management server to the VAL server for Monitor Location Subscription Response or monitor location subscription update response.
| Information Element | Status | Description |
|---|---|---|
| Subscription status | M | It indicates the subscription result |
9.3.2.12a Monitor location subscription update procedure |R18| p. 60
Figure 9.3.2.12a-1 illustrates the high level procedure for allowing a VAL server update an existing monitor location subscription at the location management server.
Pre-conditions:
- the VAL server has an active monitor location subscription at the location management server.
Step 1.
When the VAL server decides to update an active monitor location subscription, it sends a monitor location subscription update request to the location management server including the information specified in Table 9.3.2.11-1.
Step 2.
The location management server shall check if the VAL server is authorized to update the subscription.
Step 3.
If the VAL server is authorized to update the subscription, the location management server updates the monitor location subscription.
Step 4.
The location management server sends a monitor location subscription update response to the VAL server including the information as specified in Table 9.3.2.12-1.
9.3.2.13 Notify Location Monitoring Event |R17| p. 60
Table 9.3.2.13-1 describes the information flow from location management server to the VAL server for notification of location monitoring events.
| Information Element | Status | Description |
|---|---|---|
| Event | M | Information of the event to be reported. The event shall be one of the following: "Notify_Mismatch_Location" - When the location information of the target VAL UE, from the location management client and the core network do not match, or when the location management server determined area of interest result based on location management client location and the core network reported area of interest result do not match. "Notify_Absence" - When the VAL UE's current location is deviating from the target VAL server's area of interest information. "Notify_Presence" - When the VAL UE's current location is within the target VAL server's area of interest information. "Notify_Unknown" - When the location management server cannot determine whether the target VAL UE's current location is within the VAL server's dynamic area of interest information or not. |
| Identity | M | Identifier of the VAL UE whose location information is reported. |
| Location | M | Current location of the target VAL UE. |
9.3.2.14 Location area monitoring subscription request |R17| p. 61
Table 9.3.2.14-1 describes the information flow from the VAL server to the location management server for location area monitoring subscription request.
| 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 VAL server requests (e.g.Geofencing). |
| Location Information criteria | M | Location information to be monitored. It includes the geographic location information or a VAL service area identified by the VAL service area ID or a reference UE along with the application defined proximity range from the reference UE. This information also applies for Geofencing service. |
| Triggering events | O | It indicates the triggering events to be monitored and identifies when the server will send the notification (e.g. distance travelled). This information also applies for Geofencing service. |
| > UEs moved in/out | O | It indicates to monitor the UE(s) moving in/out of the area as defined in location information criteria. |
| > Numbers of UEs moved in/out | O | Indicates the numbers of UE(s) moving in/out of the area as defined in location information criteria are to be monitored. |
| > Time of UEs moved in/out | O | Indicates the time stamp/time duration of UE(s) moving in/out of the area as defined in location information criteria is to be monitored. |
| Time between consecutive reports | O | It indicates the interval time between consecutive reports. |
| Immediate Report Indicator | O | Indicates whether an immediate location report is required. |
| Notification Target URI | M | Target URI where the VAL server wishes to receive the notifications about location area monitoring. |
9.3.2.15 Location area monitoring subscription response |R17| p. 62
Table 9.3.2.15-1 describes the information flow from the location management server to the VAL server for location area monitoring subscription response.
| Information Element | Status | Description |
|---|---|---|
| Subscription status | M | It indicates the subscription result |
| Subscription identity | O
(see NOTE) | If subscription is successful, identifies the subscription |
|
NOTE:
This IE shall be present if subscription status is set to success.
|
||
9.3.2.16 Location area monitoring notification |R17| p. 62
Table 9.3.2.16-1 describes the information flow from the location management server to the VAL server.
| Information Element | Status | Description |
|---|---|---|
| Subscription identity | M | Identity of the subscription |
| UEs currently present
(see NOTE) | O | List of the identities of all VAL UEs who are currently present in the given location area |
| UEs moved in/out
(see NOTE) | O | List of UEs either moved in to the location area or moved out of the location area |
| > UEs moved in | O | List of the identities of the VAL UEs who moved in to the given location area since previous notification. |
| > UEs moved out | O | List of the identities of the VAL UEs who moved out of the given location area since previous notification. |
| Number of UEs moved in/out | O | Number of the VAL UE(s) who moved in/out the given location area in a given time period. |
| > Number of UEs moved in | O | Number of the VAL UE(s) who moved in the given location area in a given time period. |
| > Number of UEs moved out | O | Number of the VAL UE(s) who moved out the given location area in a given time period. |
| Time of UEs moved in/out | O | The timestamp and time period of UEs either moved in the location area or moved out of the location area. |
| > Time stamp and time duration of UE moved in | O | The timestamp and time period of UEs who moved in the given location area since previous notification. |
| > Time stamp and time duration of UE moved out | O | The timestamp and time period of UEs who moved out the given location area since previous notification. |
| Triggering event | O | Identity of the event that triggered the sending of the notification |
| Reason | O | It indicates the failure reason for the notification report (e.g., "UE cannot be connected") when the location management server can't obtain the UE location data. |
|
NOTE:
Any one of these shall be present.
|
||
9.3.2.17 Location area monitoring subscription modify request |R17| p. 63
Table 9.3.2.17-1 describes the information flow from the VAL server to the location management server for location area monitoring subscription modify request.
| 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 VAL server requests (e.g., Geofencing). |
| Subscription identity | M | Identifies the subscription |
| Location Information criteria | M | Location information to be monitored. It includes the geographic location information or a VAL service area ID or a reference UE along with the application defined proximity range from the reference UE. This information also applies for Geofencing service. |
| Triggering events | O | It indicates the triggering events to be monitored and identifies when the server will send the notification (e.g. distance travelled). This information also applies for Geofencing service. |
| > UEs moved in/out | O | It indicates to monitor the UE(s) moving in/out of the area as defined in location information criteria. |
| > Numbers of UEs moved in/out | O | Indicates the numbers of UE(s) moving in/out of the area as defined in location information criteria are to be monitored. |
| > Time of UEs moved in/out | O | Indicates the time stamp/time duration of UE(s) moving in/out of the area as defined in location information criteria is to be monitored. |
| Time between consecutive reports | O | It indicates the interval time between consecutive reports. |
| Immediate Report Indicator | O | Indicates whether an immediate location report is required. |
| Notification Target URI | M | Target URI where the VAL server wishes to receive the notifications about location area monitoring. |
9.3.2.18 Location area monitoring subscription modify response |R17| p. 64
Table 9.3.2.18-1 describes the information flow from the location management server to the VAL server for location area monitoring subscription modify response.
| Information Element | Status | Description |
|---|---|---|
| Subscription modification status | M | It indicates the request result |
9.3.2.19 Location area monitoring unsubscribe request |R17| p. 64
Table 9.3.2.19-1 describes the information flow from the VAL server to the location management server for location area monitoring unsubscribe request.
| Information Element | Status | Description |
|---|---|---|
| Identity | M | Identity of the requesting VAL server, VAL UE or SEAL Server |
| Subscription identity | M | Identifies the subscription |
9.3.2.20 Location area monitoring unsubscribe response |R17| p. 64
Table 9.3.2.20-1 describes the information flow from the location management server to the VAL server for location area monitoring unsubscribe response.
| Information Element | Status | Description |
|---|---|---|
| Request status | M | It indicates the request result |
9.3.2.21 VAL service area configuration request |R18| p. 65
Table 9.3.2.21-1 describes the information flow from the VAL server to the location management server for VAL service area configuration request.
| Information element | Status | Description |
|---|---|---|
| Identity | M | Identity of the requesting VAL server |
| 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 location list | M | List of one more geographical locations (e.g., co-ordinates) corresponding to the VAL service area ID. |
9.3.2.22 VAL service area configuration response |R18| p. 65
Table 9.3.2.22-1 describes the information flow from the location management server to the VAL server for VAL service area configuration response.
| Information element | Status | Description |
|---|---|---|
| VAL Service area configuration status | M | It indicates the result of VAL service area configuration request. |
| List of VAL service area IDs | O | List of VAL service area IDs. |
|
NOTE:
This IE shall be present only if the configuration status is set to success.
|
||
9.3.2.23 Location service registration request |R18| p. 65
Table 9.3.2.23-1 describes the information flow from the location management client to the location management server for registration of the location service.
| 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 registered. |
| Location capability | O | The information of location capability of VAL UE for which the location service is registered. |
| >Location access type
(NOTE 2) | O
(NOTE 1) | Identifies the available location access type of the VAL UE. E.g. as described in TS 23.273 and TS 29.572. |
| >Positioning method | O
(NOTE 1) | Identifies the available positioning methods of the VAL UE. E.g. as described in TS 23.273 and TS 29.572. |
| 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 and TS 29.572 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.
|
||
9.3.2.24 Location service registration response |R18| p. 66
Table 9.3.2.24-1 describes the information flow from the location management server to the location management client for the location service registration response.
| Information element | Status | Description |
|---|---|---|
| Registration status | M | It indicated the registration result. |
9.3.2.25 Location reporting configuration cancel response |R18| p. 66
Table 9.3.2.25-1 describes the location reporting configuration cancel response information flow from the location management server to the location management client or from the location management client to the location management server.
| Information element | Status | Description |
|---|---|---|
| Cancel status | M | It indicates the cancelled result. |
9.3.2.26 VAL service area obtain request |R18| p. 66
Table 9.3.2.26-1 describes the information flow from a VAL server to a location management server for obtain VAL service area identifiers at the location management server.
| Information element | Status | Description |
|---|---|---|
| Identity | M | Indicates the VAL server identity. |
| VAL service area IDs | M | Indicates the list of the requested VAL service area identifiers. |
9.3.2.27 VAL service area obtain response |R18| p. 67
Table 9.3.2.27-1 describes the information flow from a location management server to the VAL server for obtain VAL service area identifiers at the location management server.
| Information element | Status | Description |
|---|---|---|
| Result | M | Indicates the success or failure for the operation. |
| List of VAL service area information | O
(see NOTE) | 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. |
|
NOTE:
This information element shall be present only if the obtain VAL service area identifier(s) is successful.
|
||
9.3.2.28 VAL service area update request |R18| p. 67
Table 9.3.2.28-1 describes the information flow from a VAL server to a location management for update VAL service area identifiers at the location management server.
| Information element | Status | Description |
|---|---|---|
| Identity | M | Indicates the VAL server identity. |
| List of VAL service area information | M | List of one or more VAL service area identifiers that shall be updated. |
| > VAL service area ID | M | Indicates the VAL service area identifier. |
| > Geographical locations | M | Indicates the list of the updated geographical locations (e.g., the geographical coordinates) corresponding to the VAL service area ID. |
9.3.2.29 VAL service area update response |R18| p. 67
Table 9.3.2.29-1 describes the information flow from a location management server to the VAL server for update VAL service area identifiers at the location management server.
| 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 updated VAL service area identifiers. |
|
NOTE:
|
||
9.3.2.30 VAL service area delete request |R18| p. 67
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.
| 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. |
9.3.2.31 VAL service area delete response |R18| p. 68
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.
| 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.
|
||
9.3.2.32 Location information unsubscribe request |R18| p. 68
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.
| Information element | Status | Description |
|---|---|---|
| Requestor ID | M | Identity of the VAL server or VAL UE's requesting ID. |
9.3.2.33 Location information unsubscribe response |R18| p. 68
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.
| Information element | Status | Description |
|---|---|---|
| Request status | M | It indicates the unsubscribe request result. |
9.3.2.34 Monitor location unsubscribe request |R18| p. 68
Table 9.3.2.34-1 describes the information flow from the VAL server to the location management server for monitor location unsubscribe request.
| Information element | Status | Description |
|---|---|---|
| Requestor ID | M | Identity of the VAL server's requesting ID. |
9.3.2.35 Monitor location unsubscribe response |R18| p. 68
Table 9.3.2.35-1 describes the information flow from location management server to the VAL server for monitor location unsubscribe response.
| Information element | Status | Description |
|---|---|---|
| Request status | M | It indicates the unsubscribe request result. |
9.3.2.36 Location service registration update request |R18| p. 69
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.
| 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 and TS 29.572. |
| > Positioning method | O
(NOTE 1) | Identifies the updated positioning methods of the VAL UE. E.g. as described in TS 23.273 and TS 29.572. |
| 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 and TS 29.572 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.
|
||
9.3.2.37 Location service registration update response |R18| p. 69
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.
| Information element | Status | Description |
|---|---|---|
| Update status | M | It indicated the update result. |
9.3.2.38 Location service deregistration request |R18| p. 69
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.
| Information element | Status | Description |
|---|---|---|
| Identity | M | Identity of the VAL user or the VAL UE. |
9.3.2.39 Location service deregistration response |R18| p. 69
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.
| Information element | Status | Description |
|---|---|---|
| Deregistration status | M | It indicated the deregistration result. |
9.3.2.40 Location reporting configuration update request |R18| p. 70
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.
| 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 and TS 29.572. |
| 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 and TS 29.572. |
| 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 and TS 29.572 is out of scope of the present specification.
NOTE 3:
The definition of the velocity refers to TS 23.271.
|
||
9.3.2.41 Location reporting configuration update response |R18| p. 70
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.
| Information element | Status | Description |
|---|---|---|
| Update status | M | It indicates the update result. |
9.3.2.42 VAL service area subscription request |R18| p. 70
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.
| 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.
|
||
9.3.2.43 VAL service area subscription response |R18| p. 71
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.
| Information element | Status | Description |
|---|---|---|
| Subscription status | M | It indicates the subscription result. |
9.3.2.44 VAL service area notification |R18| p. 71
Table 9.3.2.44-1 describes the information flow for VAL service area notification from a location management server to a SEAL server.
| 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. |
9.3.2.45 VAL service area unsubscribe request |R18| p. 71
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.
| Information element | Status | Description |
|---|---|---|
| Identity | M | Indicates the SEAL server identity. |
9.3.2.46 VAL service area unsubscribe response |R18| p. 72
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.
| Information element | Status | Description |
|---|---|---|
| Request status | M | It indicates the unsubscribe request result. |
9.3.2.47 Adaptive location reporting configuration provisioning notification request |R19| p. 72
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.
| 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. |
9.3.2.48 Adaptive location reporting configuration provisioning notification response |R19| p. 72
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.
| Information element | Status | Description |
|---|---|---|
| Result | M | Indicates the VAL server or authorized SEAL LM client decision, e.g., accept or reject. |
9.3.2.49 Location tracing configuration request |R19| p. 72
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.
| 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. |
9.3.2.50 Location tracing configuration response |R19| p. 73
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.
| Information element | Status | Description |
|---|---|---|
| Request status | M | It indicates the location tracing configuration request result. |
9.3.2.51 Location history request |R19| p. 73
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.
| 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. |
9.3.2.52 Location history response |R19| p. 73
Table 9.3.2.52-1 describes the information flow from the location management server to the VAL server for the 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. |
9.3.2.53 Location tracing configuration cancel request |R19| p. 73
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.
| 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. |
9.3.2.54 Location tracing configuration cancel response |R19| p. 74
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.
| Information element | Status | Description |
|---|---|---|
| Cancel status | M | It indicates the location tracing configuration cancel request result. |
9.3.2.55 Surrounding UE retrieval request |R19| p. 74
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.
| 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. |
9.3.2.56 Surrounding UE retrieval response |R19| p. 74
Table 9.3.2.56-1 describes the information flow from the LM client to the LM server for sending the surrounding UE information.
| 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. |
9.3.2.57 Verify location sharing request |R19| p. 74
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.
| 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. |
9.3.2.58 Verify location sharing response |R19| p. 74
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.
| 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. |
9.3.2.59 Location reuse request |R19| p. 75
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.
| 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). |
9.3.2.60 Location reuse response |R19| p. 75
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.
| Information element | Status | Description |
|---|---|---|
| Result | M | Indicates success or failure of the request. |
9.3.2.61 SL positioning management subscription request |R19| p. 75
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.
| 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. |
9.3.2.62 SL positioning management subscription response |R19| p. 76
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.
| 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.
|
||
9.3.2.63 SL positioning management notification |R19| p. 76
Table 9.3.2.63-1 describes the information flow from the location management server to the VAL server.
| 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"). |
9.3.2.64 SL positioning configuration command |R19| p. 76
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.
| 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. |
9.3.2.65 Short-Range based positioning information request |R19| p. 77
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.
| 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. |
9.3.2.66 Short-Range based positioning information response |R19| p. 77
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.
| 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.
|
||
9.3.2.67 Location subscription request |R19| p. 78
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.
| 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 TS 23.273 and the clause 6.1.6.2.13 of TS 29.572.
|
||
9.3.2.68 Location subscription response |R19| p. 78
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.
| Information element | Status | Description |
|---|---|---|
| Identity | M | Identity of the requesting VAL server/VAL user or VAL UE. |
| Subscription status | M | It indicates the subscription result. |
9.3.2.69 Location notification |R19| p. 78
Table 9.3.2.69-1 describes the information flow from the location management client to the location management server.
| 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. |
9.3.2.70 Off-network location positioning configuration request |R19| p. 79
Table 9.3.2.70-1 describes the information flow from the LM server to the LM client for location area monitoring subscription 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. |
9.3.2.71 Off-network location positioning configuration response |R19| p. 79
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.
| Information element | Status | Description |
|---|---|---|
| Subscription status | M | It indicates the subscription result. |
| Subscription identity | O
(see NOTE) | If subscription is successful, identifies the subscription. |
|
NOTE:
This IE shall be present if subscription status is set to success.
|
||
9.3.2.72 Off-network history location result report |R19| p. 79
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.
| 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. |
9.3.2.73 Confirm location service subscription request |R19| p. 79
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.
| 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. |
9.3.2.74 Confirm location service subscription response |R19| p. 80
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.
| Information element | Status | Description |
|---|---|---|
| Identity | M | Identity of the requesting VAL server/VAL user. |
| Subscription status | M | It indicates the subscription result. |
9.3.2.75 Confirm location request |R19| p. 80
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.
| 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.
|
||
9.3.2.76 Confirm location report |R19| p. 80
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.
| 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.
|
||
9.3.2.77 Confirm location service usage notification |R19| p. 81
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.
| 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. |
