Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.434  Word version:  18.1.0

Top   Top   Up   Prev   Next
0…   4…   6…   6.4…   6.5…   7…   8…   8.2.2…   9…   9.3…   9.3.6…   9.4…   10…   10.3…   10.3.2.22…   10.3.3…   10.3.7…   10.4…   11…   11.3…   12…   13…   14…   14.3…   14.3.3…   14.3.3.3…   14.3.4…   14.3.4.6…   14.4…   15…   A…

 

9.3  Procedures and information flows for Location management (on-network)p. 43

9.3.1  Generalp. 43

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 informationp. 43

9.3.2.0  Location reporting configuration requestp. 43

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
IdentityMIdentity of the VAL user or identity of the VAL UE
VAL service IDOIdentity of the VAL service for which the location reporting configuration is requested.
Up

9.3.2.1  Location reporting configuration responsep. 43

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
IdentityMIdentity of the VAL user or VAL group to which the location reporting configuration is targeted or identity of the VAL UE
Requested location informationO
(see NOTE)
Identifies what location information is requested
Triggering criteriaO
(see NOTE)
Identifies when the location management client will send the location report
Minimum time between consecutive reportsO
(see NOTE)
Defaults to 0 if absent otherwise indicates the time interval between consecutive reports
NOTE:
If none of the information element is present, this represents a cancellation for location reporting.
Up

9.3.2.2  Location information reportp. 44

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 identitiesMSet of identities of the reporting VAL users or VAL UEs
Triggering eventMIdentity of the event that triggered the sending of the report
Location InformationMLocation information
TimestampOTimestamp of the location report
Up

9.3.2.3  Location information requestp. 44

Table 9.3.2.3-1 describes the information flow from the VAL server to the location management server and from the location management server to the location management client for requesting an immediate location information report.
Information Element Status Description
Identity listMList of VAL users or VAL UEs whose location information is requested
VAL service IDOIdentity of the VAL service for which the location information is requested.
Up

9.3.2.4  Location reporting triggerp. 44

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
IdentityM
(see NOTE 1)
Identity of the requesting authorized VAL user or VAL UE
IdentityM
(see NOTE 1)
Identity of the requested VAL user or VAL UE
VAL service IDOIdentity of the VAL service for which the location reporting trigger is set.
Immediate Report IndicatorO
(see NOTE 2)
Indicates whether an immediate location report is required
Requested location informationO
(see NOTE 2)
Identifies what location information is requested
Triggering criteriaO
(see NOTE 2)
Identifies when the requesting client/VAL server is expecting to receive the location report from the requested VAL user/ VAL UE
Minimum time between consecutive reportsO
(see NOTE 2)
Defaults to 0 if absent otherwise indicates the interval time between consecutive reports
Endpoint informationOInformation of the endpoint of the requesting VAL server to which the location report notification has to be sent. It is provided if Immediate Report Indicator is set to required.
NOTE 1:
The identity of the requesting VAL user/UE and the requested VAL user/UE should belong to the same VAL service.
NOTE 2:
At least one of these rows shall be present.
Up

9.3.2.5  Location information subscription requestp. 45

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.
Information Element Status Description
IdentityMIdentity of the requesting VAL server/VAL user or VAL UE
Identities listMList of VAL users or VAL UEs whose location information is requested
VAL service IDOIdentity of the VAL service for which the location information is subscribed.
Time between consecutive reportsMIt indicates the interval time between consecutive reports
Up

9.3.2.6  Location information subscription responsep. 45

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.
Information Element Status Description
IdentityMIdentity of the requesting VAL server/VAL user or VAL UE
Subscription statusMIt indicates the subscription result
Up

9.3.2.7  Location information notificationp. 45

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 listMList of the VAL users or VAL UEs whose location information needs to be notified
IdentityMIdentity of the VAL user or VAL UE subscribed to location of another VAL user or VAL UE (NOTE)
Triggering eventMIdentity of the event that triggered the sending of the notification
Location InformationMLocation information
TimestampOTimestamp of the location report
NOTE:
This is only used for location management server sends location information notification to the VAL user or VAL UE who has subscribed the location.
Up

9.3.2.8  Location reporting configuration cancel requestp. 46

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.
Information Element Status Description
IdentityMIdentity of the requesting authorized VAL user or VAL UE
IdentityMIdentity of the requested VAL user or VAL UE
VAL service IDOIdentity of the VAL service for which the location reporting configuration is requested to be canceled.
Up

9.3.2.9  Get UE(s) information request |R17|p. 46

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 informationMLocation information around which the UE(s) information is requested.
Application defined proximity range informationMDescription of the range information over which the UE(s) information is required.
Up

9.3.2.10  Get UE(s) information response |R17|p. 46

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
ResultMResult from the VAE server in response to subscription request indicating success or failure
List of UEs information (see NOTE)OThe information of the UEs which were detected in the application defined proximity range. The list can be empty.
> UE IDMThe identifier of UE
> Location informationMLocation information of UE within the application defined proximity range
NOTE:
This IE shall be included when the Result indicates success.
Up

9.3.2.11  Monitor Location Subscription Request |R17|p. 47

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).
Information Element Status Description
IdentityMIdentifier of the VAL users or VAL UE whose location monitoring is requested to be monitored in a given location.
Area of InterestMGeographic area location information where the VAL server wishes to monitor the VAL UE's location adherence.
Notify IntervalMPeriodic time interval in which the LM server needs to notify the VAL UE's location information to the VAL server.
Notification Target URIMTarget URI where the VAL server wishes to receive the notifications about VAL UE's location.
TimeoutOA timeout period when subscription response is not received.
Up

9.3.2.12  Monitor Location Subscription Response |R17|p. 47

Table 9.3.2.12-1 describes the information flow from LM server to the VAL server for Monitor Location Subscription Response.
Information Element Status Description
Subscription statusMIt indicates the subscription result
Up

9.3.2.13  Notify Location Monitoring Event |R17|p. 47

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
EventM Information of the event to be reported. The event shall be one of the following:
"Notify_Mismatch_Location" - When the location information of the VAL UE, from the location management client and the core network do not match.
"Notify_Absence" - When the VAL UE's current location is deviating from the VAL server's area of interest information.
"Notify_Presence" - When the VAL UE's current location is within the VAL server's area of interest information.
IdentityMIdentifier of the VAL UE whose location information is reported.
LocationMCurrent location of the VAL UE.
Up

9.3.2.14  Location area monitoring subscription request |R17|p. 48

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
IdentityMIdentity of the requesting VAL server, VAL UE or SEAL Server
Location Information criteriaMLocation information to be monitored.
It includes the geographic location information or a reference UE along with the application defined proximity range from the reference UE.
Time between consecutive reportsOIt indicates the interval time between consecutive reports
Immediate Report IndicatorOIndicates whether an immediate location report is required
Triggering eventsOIdentifies when the server will send the notification (e.g. distance travelled)
Up

9.3.2.15  Location area monitoring subscription response |R17|p. 48

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 statusMIt indicates the subscription result
Subscription identityO
(see NOTE)
If subscription is successful, identifies the subscription
NOTE:
This IE shall be present if subscription status is set to success.
Up

9.3.2.16  Location area monitoring notification |R17|p. 48

Table 9.3.2.16-1 describes the information flow from the location management server to the VAL server.
Information Element Status Description
Subscription identityMIdentity of the subscription
UEs currently present
(see NOTE)
OList of the identities of all VAL UEs who are currently present in the given location area
UEs moved in/out
(see NOTE)
OList of UEs either moved in to the location area or moved out of the location area
>> UEs moved inOList of the identities of the VAL UEs who moved in to the given location area since previous notification.
>> UEs moved outOList of the identities of the VAL UEs who moved out of the given location area since previous notification.
Triggering eventOIdentity of the event that triggered the sending of the notification
NOTE:
Any one of these shall be present.
Up

9.3.2.17  Location area monitoring subscription modify request |R17|p. 48

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
IdentityMIdentity of the requesting VAL server, VAL UE or SEAL Server
Subscription identityMIdentifies the subscription
Location Information criteriaMLocation information to be monitored. It includes the geographic location information or a reference UE along with the application defined proximity range from the reference UE.
Time between consecutive reportsOIt indicates the interval time between consecutive reports
Immediate Report IndicatorOIndicates whether an immediate location report is required
Triggering eventsOIdentifies when the server will send the notification (e.g. distance travelled)
Up

9.3.2.18  Location area monitoring subscription modify response |R17|p. 49

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 statusMIt indicates the request result
Up

9.3.2.19  Location area monitoring unsubscribe request |R17|p. 49

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
IdentityMIdentity of the requesting VAL server, VAL UE or SEAL Server
Subscription identityMIdentifies the subscription
Up

9.3.2.20  Location area monitoring unsubscribe response |R17|p. 49

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
Subscription statusMIt indicates the request result
Up

9.3.3  Event-triggered location reporting procedurep. 49

9.3.3.1  Generalp. 49

The location management server provides location reporting configuration to the location management clients, indicating what information the location management server expects and what events will trigger the sending of this information to the location management server. The decision to report location information can be triggered at the location management client by different conditions, e.g., the reception of the location reporting configuration, initial registration, distance travelled, elapsed time, cell change, MBMS SAI change, MBMS session change, leaving a specific MBMS bearer service area, tracking area change, PLMN change, call initiation, or other types of events such as emergency. The location report can include information described as ECGI, MBMS SAIs, geographic coordinates and other location information.
Up

9.3.3.2  Fetching location reporting configurationp. 50

Figure 9.3.3.2-1 illustrates the procedure for fetching location reporting configuration.
Pre-condition:
  • If multicast delivery mode is used, the MBMS bearer being used is activated by the location management server.
  • The location management client is aware that the location reporting configuration is available at the location management server.
Reproduction of 3GPP TS 23.434, Fig. 9.3.3.2-1: Fetching location reporting configuration procedure
Up
Step 1.
The location management client sends location reporting configuration request message to the location management server.
Step 2.
The location management server sends location reporting configuration message to the location management client(s) containing the initial location reporting event triggers configuration (or a subsequent update) , e.g. minimum time between consecutive reports, SAI changes, or ECGI changes for reporting the location of the VAL UE. This message can be sent over a unicast bearer to a specific location management client or as a group message over an MBMS bearer to update the location reporting configuration for multiple location management clients at the same time.
Step 3.
The location management client stores or updates the location reporting event triggers configuration. A location reporting event occurs, triggering step 3.
Up

9.3.3.3  Location reportingp. 50

Figure 9.3.3.3-1 illustrates the procedure for location reporting.
Reproduction of 3GPP TS 23.434, Fig. 9.3.3.3-1: Location reporting procedure
Up
Step 1.
The location management client sends a location information report to the location management server, containing location information identified by the location management server and available to the location management client.
Step 2.
Upon receiving the report, the location management server updates location of the reporting location management client. If the location management server does not have location information of the reporting location management client before, then just stores the reporting location information for that location management client.
Up

9.3.4  On-demand location reporting procedurep. 51

The location management server can request UE location information at any time by sending a location information request to the location management client, which may trigger location management client to immediately send the location report.
Reproduction of 3GPP TS 23.434, Fig. 9.3.4-1: On-demand location information reporting procedure
Up
Step 1.
Based on configurations such as periodical location information timer, or location information request from other entities (e.g., another location management client, VAL server), location management server initiates the immediately request location information from the location management client.
Step 2.
The location management server sends a location information request to the location management client.
Step 3.
VAL user or VAL UE is notified and asked about the permission to share its location. VAL user can accept or deny the request
Step 4.
The location management client immediately responds to the location management server with a report containing location information identified by the location management server and available to the location management client.
Step 5.
Upon receiving the report, the location management server updates location of the reporting location management client. If the location management server does not have location information of the reporting location management client before, then just stores the reporting location information for that location management client.
Up

9.3.5  Client-triggered or VAL server-triggered location reporting procedurep. 52

Figure 9.3.5-1 illustrates the high level procedure of client-triggered or VAL server-triggered location reporting.
Reproduction of 3GPP TS 23.434, Fig. 9.3.5-1: Client-triggered location reporting procedure
Up
Step 1.
Location management client 2 (authorized VAL user or VAL UE) or VAL server sends a location reporting trigger to the location management server to activate a location reporting procedure for obtaining the location information of location management client 1.
Step 2.
Location management server checks whether location management client 2 or VAL server is authorized to send a location reporting trigger. Depending on the information specified by the location reporting trigger, location management server initiates an on-demand location reporting procedure or an event-triggered location reporting procedure for the location of location management client 1.
Step 3.
Once the location information of the location management client 1 is available in the location management server by the on-demand location reporting procedure, a location information report is sent to the location management client 2 or VAL server.
Up

Up   Top   ToC