Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.280  Word version:  19.0.1

Top   Top   Up   Prev   Next
1…   5…   5.2.8…   6   7…   7.3.2   7.4…   7.4.3…   7.5…   8…   9…   9.2.2…   9.2.2.2…   9.3…   10…   10.1.2…   10.1.3…   10.1.4.3…   10.1.4.5…   10.1.5…   10.1.6…   10.2…   10.2.3…   10.2.4.2…   10.2.4.3…   10.2.5…   10.2.7…   10.3…   10.6…   10.7…   10.7.3…   10.7.3.4…   10.7.3.7…   10.7.3.7.3   10.7.3.8…   10.7.3.10…   10.8…   10.8.4…   10.8.5…   10.9…   10.9.3…   10.9.3.5…   10.9.3.8…   10.9.3.9…   10.9.3.9.3…   10.9.3.9.4…   10.9.3.10…   10.9.3.10.4…   10.9.3.10.6…   10.10…   10.10.1.2.3…   10.10.2…   10.10.3…   10.10.3.3…   10.10.3.4…   10.11…   10.11.5…   10.12…   10.13…   10.13.3…   10.13.7…   10.13.10…   10.14…   10.15…   10.15.3…   10.15.3.3…   10.15.3.4…   10.16…   10.16.3…   11…   11.3…   11.5…   11.5.2…   11.5.3…   11.5.3.3.2A…   11.5.4…   A…   B…   C…

 

10.9.3  Procedurep. 196

10.9.3.1  Event-triggered location reporting procedurep. 196

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. The conditions could include, for example, 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 alert, emergency call or imminent peril calls. The location report can include information described as time of measurement, accuracy, longitude, latitude, speed, bearing, altitude, ECGI, MBMS SAIs.
Reproduction of 3GPP TS 23.280, Fig. 10.9.3.1-1: Event-triggered location reporting procedure
Up
Step 1.
The location management server sends location reporting configuration message to the location management client(s) containing the initial configuration (or a subsequent update) for reporting the location of the MC service 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 2.
A location reporting event occurs, triggering step 3.
Step 3.
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 4.
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. If the location information report contains an optional MC service UE label, the location management server stores it together with the location information for the reporting location management client.
Up

10.9.3.2  On-demand location reporting procedurep. 197

The location management server can request MC service 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.280, Fig. 10.9.3.2-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 of an authorized user, MC service server), location management server initiates the immediate request of location information to be sent from the location management client.
Step 2.
The location management server sends a location information request to the location management client.
Step 3.
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 4.
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, the location management server just stores the reporting location information for that location management client. If the location information report contains an optional MC service UE label, the location management server stores it together with the location information for the reporting location management client.
Up

10.9.3.3  Client-triggered location reporting procedurep. 198

Figure 10.9.3.3-1 illustrates the high level procedure of client-triggered location reporting.
Reproduction of 3GPP TS 23.280, Fig. 10.9.3.3-1: Client-triggered location reporting procedure
Up
Step 1.
Location management client 2 (authorized MC service user) 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 is authorized to send a location reporting trigger for location management client 1's location information. 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.
Up

10.9.3.4  Location reporting cancel procedurep. 199

The location reporting cancel procedure reuses the information flow of location reporting configuration.
Pre-conditions:
  • The location management client has been provided with location reporting configuration information.
Reproduction of 3GPP TS 23.280, Fig. 10.9.3.4-1: Location reporting cancel procedure
Up
Step 1.
The location management server sends location reporting configuration without any information element to the location management client to stop location reporting from the MC service UE.
Step 2.
The location management client stops sending location information reports to the location management server.

Up   Top   ToC