Content for TS 23.434 Word version: 19.3.0
0…
4…
5
6…
6.4…
6.5…
6.5.3…
7…
8…
8.2.2…
9…
9.3…
9.3.2.21…
9.3.3…
9.3.6…
9.3.11…
9.3.13…
9.3.14…
9.4…
9.4.6…
9.5…
10…
10.3…
10.3.2.22…
10.3.3…
10.3.7…
10.3.10…
10.4…
11…
11.3…
11.3.3…
11.4…
12…
12.3…
13…
14…
14.2.2.2…
14.3…
14.3.2.20…
14.3.2.40…
14.3.3…
14.3.3.3…
14.3.4…
14.3.4.6
14.3.4.7…
14.3.4A…
14.3.4A.3…
14.3.4A.4…
14.3.4A.6…
14.3.4A.8…
14.3.4A.9…
14.3.4A.10…
14.3.5…
14.3.6…
14.3.9…
14.3.12…
14.4…
15…
16…
17…
18…
A
B…
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.2.0 Location reporting configuration request
9.3.2.1 Location reporting configuration response
9.3.2.2 Location information report
9.3.2.3 Location information request
9.3.2.4 Location reporting trigger
9.3.2.5 Location information subscription request
9.3.2.6 Location information subscription response
9.3.2.7 Location information notification
9.3.2.8 Location reporting configuration cancel request
9.3.2.9 Get UE(s) information request
9.3.2.10 Get UE(s) information response
9.3.2.11 Monitor Location Subscription Request
9.3.2.12 Monitor Location Subscription Response
9.3.2.12a Monitor location subscription update procedure
9.3.2.13 Notify Location Monitoring Event
9.3.2.14 Location area monitoring subscription request
9.3.2.15 Location area monitoring subscription response
9.3.2.16 Location area monitoring notification
9.3.2.17 Location area monitoring subscription modify request
9.3.2.18 Location area monitoring subscription modify response
9.3.2.19 Location area monitoring unsubscribe request
9.3.2.20 Location area monitoring unsubscribe response
...
...
9.3 Procedures and information flows for Location management (on-network) p. 51
9.3.1 General p. 51
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. 51
9.3.2.0 Location reporting configuration request p. 51
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. 51
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:
The non-3GPP access as defined in 23.273[50] and TS 29.572 is out of scope of the present specification.
|
||
9.3.2.2 Location information report p. 52
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. |
| Timestamp | O | Timestamp of the location report |
9.3.2.3 Location information request p. 52
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 LM 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). |
|
NOTE 1:
This element is only applicable for request sent from the LM server to the LM 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:
|
||
9.3.2.4 Location reporting trigger p. 52
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. 54
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). |
| Velocity information | O | Identifies the velocity of the target UE for which the location information is requested. |
| 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. 55
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. 55
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. |
| Velocity information | O | Velocity information. |
| Timestamp | O | Timestamp of the location report |
|
NOTE 1:
This is only used for location management server sends location information notification to the VAL user or VAL UE who has subscribed the location.
NOTE 2:
Either Identity or Subscription ID shall be included.
|
||
9.3.2.7a Void
9.3.2.8 Location reporting configuration cancel request p. 56
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. 56
Table 9.3.2.9-1 describes the information flow for a VAL server to get UE(s) information at the LM 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. 57
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. 57
Table 9.3.2.11-1 describes the information flow from the VAL server to the LM server for monitoring the location deviation of the VAL UE(s) 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 LM 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. 57
Table 9.3.2.12-1 describes the information flow from LM 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. 58
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. 58
Table 9.3.2.13-1 describes the information flow from LM 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 LM server determined area of interest result based on LM 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 LM 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. 59
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. |
| Geofencing monitoring events | O | It indicates the Geofencing events to be monitored. |
| > 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/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. |
| Triggering events | O | Identifies when the server will send the notification (e.g. distance travelled). |
| 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. 60
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. 60
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 | 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 LM 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. 61
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. |
| Geofencing monitoring events | O | It indicates the Geofencing events to be monitored. |
| > 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 | Indicatse 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/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. |
| Triggering events | O | Identifies when the server will send the notification (e.g. distance travelled). |
| 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. 62
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. 62
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. 62
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 |
