Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑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… 
10.9.3.10.4 Location information subscription procedure  10.9.3.10.5 Location information cancel subscription procedure 
...

 

10.9.3.10.4  Location information subscription procedure  p. 213
The location management client in the partner MC system provides, based on configuration, event triggered location information, which will be also forwarded to the subscribed entities.
Figure 10.9.3.10.4-1 illustrates the high level procedure of subscription to location information between interconnected MC systems.
Reproduction of 3GPP TS 23.280, Fig. 10.9.3.10.4-1: Location information subscription procedure
Figure 10.9.3.10.4-1: Location information subscription procedure
Up
Step 1.
The MC service server or the location management client in the primary MC system request subscription to event-triggered location information of MC service users in the partner MC system by sending a location information subscription request to the location management server in the primary MC system, according to the described information flows in clause 10.9.2.5.
Step 2.
The location management server in the primary MC system checks if the provided information along with the configuration permit the request to proceed.
Step 3.
The location management server in the primary MC system determines that the request has a target in a different MC system.
Step 4.
The location management server in the primary MC system sends the location information subscription request to the location management server in the partner MC system, according to the described information flow in clause 10.9.2.5.
Step 5.
The location management server in the partner MC system checks if the provided information along with the configuration permit the request to proceed.
Step 6.
The location management server in the partner MC system applies the subscription.
Step 7.
The location management server in the partner MC system sends the location information subscription response to the location management server in the primary MC system.
Step 8.
The location management server in the primary MC system sends the location information subscription response to the requesting entity in the primary MC system, according to the described information flow in clause 10.9.2.6.
Up
10.9.3.10.5  Location information cancel subscription procedure  p. 215
The location management client in the primary MC system receives location information updates according to the subscriptions requested in the partner MC system. Those subscriptions can be cancelled anytime from the primary MC system.
Figure 10.9.3.10.5-1 illustrates the high level procedure of the subscription cancellation to location information between interconnected MC systems.
Reproduction of 3GPP TS 23.280, Fig. 10.9.3.10.5-1: Location information cancel subscription procedure
Figure 10.9.3.10.5-1: Location information cancel subscription procedure
Up
Step 1.
The MC service server or the location management client in the primary MC system request the cancellation of subscriptions to event-triggered location information of MC service users in the partner MC system by sending location information cancel subscription requests to the location management server in the primary MC system, according to the described information flows in clause 10.9.2.8.
Step 2.
The location management server in the primary MC system checks if the provided information along with the configuration permit the request to proceed.
Step 3.
The location management server in the primary MC system determines that the request has a target in a different MC system.
Step 4.
The location management server in the primary MC system sends the location information cancel subscription request to the location management server in the partner MC system, according to the described information flow in clause 10.9.2.8.
Step 5.
The location management server in the partner MC system checks if the provided information along with the configuration permit the request to proceed.
Step 6.
The location management server in the partner MC system cancels the subscription.
Step 7.
The location management server in the partner MC system sends the location information cancel subscription response to the location management server in the primary MC system.
Step 8.
The location management server in the primary MC system sends the location information cancel subscription response to the requesting entity in the primary MC system, according to the described information flow in clause 10.9.2.9.
Up

Up   Top   ToC