Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.280  Word version:  19.3.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.17…   10.17.3…   10.17.5…   11…   11.3…   11.5…   11.5.2…   11.5.3…   11.5.3.3.2A…   A…   B…   C…   E…

 

11.5.2  3GPP access network related location information management |R19|p. 340

11.5.2.1  Generalp. 340

The MC clients residing on the non-3GPP devices may receive the location reporting configuration from the location management server containing the trigger criteria related to 3GPP access network related location parameters and the requested location information may contain the 3GPP access network related location information. The procedures defined in this subclause enables the MC clients residing on the non-3GPP devices to request the MC gateway UE to handle these triggers on its behalf and to request the required location information (3GPP access network related) from MC gateway UE.
Up

11.5.2.2  Information flowsp. 341

11.5.2.2.1  MC GW location reporting configurationp. 341
Table 11.5.2.2.1-1 describes the information flow from the MC client, which resides on a non-3GPP device, to the MC gateway UE for the location reporting configuration.
Information element Status Description
GW MC service IDMThe GW MC service ID of the requesting MC service user
Requested location informationO (see NOTE 1)Identifies what location information is requested
Triggering criteriaO (see NOTE 1)Identifies when the location management client will send the location report (see NOTE 2)
Minimum time between consecutive reportsO (see NOTE 1)Defaults to 0 if absent
NOTE 1:
If none of the information elements is present, this represents a cancellation for location reporting, if configured.
NOTE 2:
The triggering criteria contains only the events related to the 3GPP access network.
Up
11.5.2.2.2  MC GW location information reportp. 341
Table 11.5.2.2.2-1 describes the information flow from the MC gateway UE to the MC client residing on a non-3GPP device for the location information reporting.
Information element Status Description
GW MC service IDMThe GW MC service ID of the requesting MC service user
Triggering eventOIdentity of the event that triggered the sending of the report
Location information
(see NOTE)
OLocation information of the MC gateway UE
NOTE:
The following location information elements which are related to 3GPP access network shall be present (configurable): Serving and neighbouring ECGI, MBMS SAIs, MBMSfnArea, PLMN ID.
Up
11.5.2.2.3  MC GW location information requestp. 341
Table 11.5.2.2.3-1 describes the information flow from the MC client residing on a non-3GPP device to the MC gateway UE for requesting an immediate location information report.
Information element Status Description
GW MC service IDMThe GW MC service ID of the requesting MC service user
Up

11.5.2.3  Proceduresp. 341

11.5.2.3.1  Event triggered location reporting procedurep. 341
The procedure for how the MC clients residing on non-3GPP devices handling the location reporting configuration containing the trigger criteria related to the 3GPP access network related location information is shown in the Figure 11.5.2.3.1-1.
Pre-conditions
  • The MC service user wishes to have access to MC services by using a non-3GPP device.
  • The MC client successfully completed service authorization via MC gateway UE.
Reproduction of 3GPP TS 23.280, Fig. 11.5.2.3.1-1: Event-triggered location reporting procedure
Up
Step 1.
MC client receives the location reporting configuration request from LMS which contains the triggering criteria of 3GPP access network related location information changes.
Step 2.
MC client sends the MC GW location reporting configuration to the MC gateway UE containing the 3GPP access network related location information triggers and the requested location information. MC Gateway UE stores the location reporting configuration and starts monitoring for the triggers as received in the MC GW location reporting configuration.
Step 3.
A location reporting event occurs, triggering step 4.
Step 4.
MC gateway UE sends the MC GW Location information report containing the location information requested by the MC client.
Step 5.
MC client updates the locally available location information with the location information received from the MC gateway UE.
Step 6.
The MC client sends a location information report to the location management server, containing location information identified by the location management server and available to the MC client.
Up
11.5.2.3.2  On-demand location reporting procedurep. 342
The MC client may need to immediately send the location report to the location management sometimes and the requested location information may be related to the 3GPP access network. Under these circumstances the MC client can request the MC gateway UE to report its location information as described in the Figure 11.5.2.3.2-1.
Pre-conditions
  • The MC service user wishes to have access to MC services by using a non-3GPP device.
  • The MC client successfully completed service authorization via MC Gateway UE.
Reproduction of 3GPP TS 23.280, Fig. 11.5.2.3.2-1: On-demand location reporting procedure
Up
Step 1.
MC client receives the location information request from LMS to send the location information immediately or any other events where it has to send the location report to the location management server immediately like initial login, group call etc. Requested location information includes the location information related to 3GPP access network.
Step 2.
MC service user is notified and asked for permission to share location information. MC service user can accept or deny the request.
Step 3.
MC client sends the MC GW Location information request to the MC gateway requesting for the location information related to the 3GPP access network of the MC gateway UE.
Step 4.
MC gateway UE sends the MC GW Location information report containing the location information requested by the MC client.
Step 5.
MC client updates the locally available location information with the location information received from the MC gateway UE.
Step 6.
The MC client sends a location information report to the location management server, containing location information identified by the location management server and available to the MC client.
Up
11.5.2.3.3  Location reporting cancel procedurep. 343
The location reporting cancel procedure reuses the information flow of location reporting configuration as defined in the subclause 11.5.2.3.1 as described in the Figure 11.5.2.3.3-1.
Pre-conditions
  • The MC service user wishes to have access to MC services by using a non-3GPP device.
  • The MC client successfully completed service authorization via MC gateway UE.
  • The MC client no longer needs the location information report from MC gateway UE.
Reproduction of 3GPP TS 23.280, Fig. 11.5.2.3.3-1: On-demand location reporting procedure
Up
Step 1.
The location management client sends MC GW location reporting configuration without any information element to the MC gateway UE to stop location reporting from the MC gateway UE.
Step 2.
The MC gateway UE stops sending location information reports to the MC client.

Up   Top   ToC