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.554  Word version:  19.3.0

Top   Top   Up   Prev   Next
1…   4…   5…   5.3…   5.5…   6…   7…   8…   8.2…   8.2.7…   8.2.11   8.3…   8.3.5…   8.4…   8.4.3   8.5…   8.6…   8.7…   8.7.2…   8.7.3…   8.7.4…   8.7.5…   8.7.6…   8.8…   8.9…   8.10…   8.11…   9…   9.2…   10…   11… 
8.8 Other MSGin5G messaging related procedures  8.8.0 General  8.8.1 Messaging Topic Subscription  8.8.2 Message delivery based on Messaging Topic  8.8.3 Messaging Topic Unsubscription  8.8.4 Messaging Topic Subscription handling between different MSGin5G Servers  8.8.4.1 General  8.8.4.2 Messaging Topic list subscription  8.8.4.2a Messaging Topic list unsubscription  8.8.4.3 Messaging Topic Subscription between different MSGin5G Servers  8.8.4.4 Messaging Topic Unsubscription between different MSGin5G Servers 
...

 

8.8  Other MSGin5G messaging related procedures  p. 108

8.8.0  General |R18|  p. 108

In order to receive the message with a specific Messaging Topic, a UE or an Application Sever subscribes to this Messaging Topic. The procedures of a MSGin5G Server creating a Messaging Topic and a UE or an Application Sever subscribing/unsubscribing one or more Messaging Topic(s) from an MSGin5G Server are specified in clause 8.8.1 and clause 8.8.3.
When a Messaging Topic(s) has already been created on a different MSGin5G server, an MSGin5G Server needs to learn the available Messaging Topics on the other MSGin5G Server. An MSGin5G Server may use the Messaging Topic list subscription procedure specified in clause 8.8.4.2 to learn the Messaging Topics available on the other MSGin5G Server. The corresponding Messaging Topic list unsubscription procedure is specified in clause 8.8.4.2a.
An MSGin5G Server may subscribe one or more Messaging Topic(s) on the other MSGin5G Server on behalf of the UE(s) and/or Application Sever(s) if the Messaging Topic list are not hosted locally. The procedure of MSGin5G Server subscribing one or more Messaging Topic(s) from the other MSGin5G Server is specified in clause 8.8.4.3 and the corresponding unsubscription procedure is specified in clause 8.8.4.4.
A MSGin5G Server may also forward a subscription request to the MSGin5G Server that already handles the Messaging Topic.
Up

8.8.1  Messaging Topic Subscription  p. 109

An MSGin5G Client or an Application Server can subscribe one or more Messaging Topic(s) on the MSGin5G Server. The Messaging Topic IE will be populated by the Application Client or the Application Server and the content of this IE is out of scope.
When an MSGin5G Client or an Application Server is subscribed to a Messaging Topic, then the MSGin5G Server will deliver messages that contain the same Messaging Topic to the subscribers.
Figure 8.8.1-1 shows the MSGin5G Client/Application Server subscribing to Messaging Topic(s) on the MSGin5G Server.
Pre-conditions:
  1. The MSGin5G Client or Application Server has registered to the MSGin5G Server.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.8.1-1: MSGin5G Service endpoint subscribes to Messaging topic(s)
Figure 8.8.1-1: MSGin5G Service endpoint subscribes to Messaging topic(s)
(⇒ copy of original 3GPP image)
Up
Step 1.
The MSGin5G Client or Application Server sends a Messaging Topic subscription request to the MSGin5G Server. The request includes the information elements listed in Table 8.8.1-1.
Information element Status Description
Originating UE Service ID/AS Service IDMThe service identity of the sending MSGin5G Client or the sending Application Server.
Messaging TopicMA list of Messaging Topic(s) that is to be subscribed. The number of Messaging Topic(s) included in this IE can be one or more.
ExpirationOThe date and time when the subscription expires.
This date and time apply to all Messaging Topic(s) subscribed in this request.
If this IE is included, the value of it should be larger than 0.
If this IE is not included, the expiration time is subject to operator policy.
NOTE:
The content of the Messaging Topic is out of scope of the present document.
Step 2.
The MSGin5G Server validates the Messaging Topic subscription request and checks the locally stored Messaging Topic(s).
  1. If the subscribed Messaging Topic has already been created, the MSGin5G Server checks whether the UE Service ID/AS Service ID of the subscriber is already included in the subscribers list of this Messaging Topic.
    1. If not, the MSGin5G Server adds the UE Service ID/AS Service ID of the subscriber to the subscribers list of this Messaging Topic. The MSGin5G Server sets the validity time of this subscription to the value of the Expire IE or to a default value according to the service policy.
    2. Else, the MSGin5G Server updates the validity time of this subscription.
  2. If the subscribed Messaging Topic has not been already created, the MSGin5G Server creates this Messaging Topic, and adds the UE Service ID/AS Service ID of the subscriber to the subscribers list of this Messaging Topic. The MSGin5G Server sets the validity time of this subscription to the value of the Expire IE or to a default value according to the service policy.
Step 3.
The MSGin5G Server sends a Messaging Topic Subscription response to the originator of the request. The response includes the information listed in Table 8.8.1-2.
Information element Status Description
Subscription statusMIndicates whether the subscription was successfully added or deleted on the MSGin5G Server.
ExpirationOThe validity date and time of this subscription set by the MSGin5G Server.
Up

8.8.2  Message delivery based on Messaging Topic  p. 110

If an MSGin5G Client or an Application Server is in the subscribers list of a Messaging Topic, the MSGin5G Server delivers messages that contain this Messaging Topic to it.
Figure 8.8.2-1 shows the Message delivery to a subscribing service endpoint based on Messaging Topic.
Pre-conditions:
  1. The MSGin5G Client or Application Server subscribed to a Messaging Topic with the MSGin5G Server. A Messaging Topic with the UE Service ID/AS Service ID of the subscriber has been created.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.8.2-1: Message delivery to subscribing service endpoint based on Messaging Topic
Figure 8.8.2-1: Message delivery to subscribing service endpoint based on Messaging Topic
(⇒ copy of original 3GPP image)
Up
Step 1.
The MSGin5G Server receives an MSGin5G message request or an API message request corresponding to step 2 in Figure 8.3.2-1 or Figure 8.3.2-2 which includes the IEs as listed in Table 8.3.2-1. The MSGin5G message request or API message request contains a Messaging Topic IE corresponding to the Messaging Topic for which subscription(s) exist.
Step 2.
The MSGin5G Server uses the procedure described in clause 8.3.3 to deliver the message to all subscriber(s) of this Messaging Topic. In each message, the UE Service ID/AS Service ID of subscriber should be added as the Recipient UE Service ID/AS Service ID IE specified in Table 8.3.3-1.
Up

8.8.3  Messaging Topic Unsubscription  p. 111

Corresponding to message topic subscription, an MSGin5G Client or an Application Server can unsubscribe from one or more Messaging Topic(s) on the MSGin5G Server.
Figure 8.8.3-1 shows the MSGin5G Client/Application Server unsubscribing to Messaging Topic(s) on the MSGin5G Server.
Pre-condition
  1. The MSGin5G Client or Application Server has subscribed one or more message topic(s) on the MSGin5G Server.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.8.3-1: MSGin5G Service endpoint unsubscribes to Messaging topic(s)
Figure 8.8.3-1: MSGin5G Service endpoint unsubscribes to Messaging topic(s)
(⇒ copy of original 3GPP image)
Up
Step 1.
The MSGin5G Client or Application Server sends a Messaging Topic unsubscription request to the MSGin5G Server. The request includes the information listed in Table 8.8.3-1.
Information element Status Description
Originating UE Service ID/AS Service IDMThe service identity of the sending MSGin5G Client or the sending Application Server.
Messaging Topic(s)MA list of Messaging Topic(s) that is to be unsubscribed. The number of Messaging Topic(s) included in this IE can be one or more.
Step 2.
The MSGin5G Server validates the Messaging Topic unsubscription request and checks the locally stored Messaging Topic(s). If the UE Service ID/AS Service ID is included in the subscribers list of this Messaging Topic, the MSGin5G Server removes the UE Service ID/AS Service ID from the subscribers list of this Messaging Topic.
Step 3.
The MSGin5G Server sends a Messaging Topic Unsubscription response to the originator of the request. The response includes the information listed in Table 8.8.3-2.
Information element Status Description
subscription statusMIndicates whether the subscription was successfully deleted on the MSGin5G Server.
Up

8.8.4  Messaging Topic Subscription handling between different MSGin5G Servers |R18|  p. 112

8.8.4.1  General  p. 112

When a Messaging Topic(s) is handled between different MSGin5G Servers, the MSGin5G Server 1 may work in the following models, when the subscription for the Messaging Topic exists on Server 2:
  1. Mod.A: the MSGin5G UE/Application Server served by MSGin5G Server 1 subscribes to Messaging Topic(s) and the MSGin5G Server 1 forwards Messaging Topic subscription request from the MSGin5G UE/Application Server to MSGin5G Server 2 or
  2. Mod.B: the MSGin5G UE/Application Server served by MSGin5G Server 1 subscribes to Messaging Topic(s) and the MSGin5G Server 1 subscribes to the Messaging Topic(s) on Server 2 on behalf of all MSGin5G UE/Application Server served by it.
If the subscription for the Messaging Topic already exists on Server 1, or if the subscription does not exist either on Server 1 or on Server 2, the procedure in clause 8.8.1 applies.
The MSGin5G Server may work in one model based on the service policy. The MSGin5G Server 1 and MSGin5G Server 2 can be located in the same PLMN or different PLMNs.
To enable the message delivery based on Messaging Topic between different MSGin5G Servers, an MSGin5G Server shall subscribe the Messaging Topic list from other MSGin5G Servers as specified in clause 8.8.4.2. If the Messaging Topic is created or deleted on an MSGin5G Server, and if there are Messaging Topic list subscriptions from other MSGin5G Server(s), the MSGin5G Server shall send a Messaging Topic list notification to the corresponding MSGin5G Server(s) as specified in clause 8.8.4.2. When an MSGin5G Server receives a Messaging Topic subscription or unsubscription from an MSGin5G Client, it shall handle the Messaging Topic subscription or unsubscription request as specified in clause 8.8.4.3 or clause 8.8.4.4.
Up

8.8.4.2  Messaging Topic list subscription  p. 112

Before the subscribing of Messaging Topic(s), the MSGin5G Server 1 should obtain the available Messaging Topic list on the MSGin5G Server 2 to determine whether to forward the Messaging Topic subscription request to MSGin5G Server 2, to subscribe to the Messaging Topic on behalf of all MSGin5G UE/Application Server served by it on MSGin5G Server 2, or to create the subscription on Server 1 as specified in clause 8.8.1 if the subscription does not exist on Server 2.
Figure 8.8.4.2-1 shows the MSGin5G Server 1 subscribing to Messaging Topic list on the MSGin5G Server 2.
Pre-conditions:
  1. MSGin5G Server 1 and MSGin5G Server 2 have established a secured connection.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.8.4.2-1: MSGin5G Server 1 subscribes to Messaging Topic list on the MSGin5G Server 2
Figure 8.8.4.2-1: MSGin5G Server 1 subscribes to Messaging Topic list on the MSGin5G Server 2
(⇒ copy of original 3GPP image)
Up
Step 1.
The MSGin5G Server 1 sends a Messaging Topic list subscription request to the MSGin5G Server 2. The request includes the information elements listed in Table 8.8.4.2-1.
Information element Status Description
Originating MSGin5G Server IDMThe MSGin5G Server which requests the Messaging Topic list.
Recipient MSGin5G Server IDMThe MSGin5G Server which holds the Messaging Topic list.
Security credentialsOSecurity information required by the MSGin5G Server 2 and is left for implementation.
ExpirationOThe date and time when the subscription expires.
If this IE is included, the value of it should be larger than 0.
If this IE is not included, the expiration time is subject to operator policy.
Step 2.
Upon receiving the Messaging Topic list subscription request, the MSGin5G Server 2 validates this request and may verify the security credentials.
Step 3.
The MSGin5G Server 2 checks the locally stored Messaging Topic list subscription(s).
  1. If the MSGin5G Server 1's subscription has already been created, the MSGin5G Server 2 updates the validity time of this subscription.
  2. If the MSGin5G Server 1's subscription has not been created, the MSGin5G Server 2 creates the subscription.
Step 4.
The MSGin5G Server 2 sends a Messaging Topic list Subscription response to MSGin5G Server 1. The response includes the information listed in Table 8.8.4.2-2.
Information element Status Description
Subscription statusMIndicates whether the subscription was successfully added or deleted on the MSGin5G Server 2.
ExpirationOThe validity date and time of this Messaging Topic list subscription set by the MSGin5G Server 2.
Step 5.
The MSGin5G Server 2 checks whether Messaging Topic list notification is needed, e.g. whether the MSGin5G Server 1 subscribes the Messaging Topic list on MSGin5G Server 2 for the first time, or the local Messaging Topic(s) on the MSGin5G Server 2 are updated, e.g. new Messaging Topic(s) has been created or existing Messaging Topic(s) has been deleted.
Step 6.
If Messaging Topic list notification is needed, the MSGin5G Server 2 sends a Messaging Topic list notification to MSGin5G Server 1. The notification includes the information listed in Table 8.8.4.2-3.
Information element Status Description
ExpirationOThe new validity date and time of this subscription set by the MSGin5G Server 2.
> Messaging Topic listMA list of Messaging Topic(s) that exists on the MSGin5G Server 2.
If the MSGin5G Server 1 subscribes the Messaging Topic list on MSGin5G Server 2 for the first time, the MSGin5G Server 2 should include all Messaging Topic(s) that exist on the MSGin5G Server 2 in this Messaging Topic list, else the MSGin5G Server 2 includes the deviation of Messaging Topic(s) since the last notification,
Each element in this list contains information as specified in Table 8.8.4.2-4.
Based on service policy, the MSGin5G Server 2 may only include a part of Messaging Topic(s) in the notification which are allowed to be subscribed by MSGin5G Server 1.
Information element Status Description
Messaging TopicMUnique identifier of this Messaging Topic.
Update statusMIdentifies the Messaging Topic is newly created on the MSGin5G Server 2, or newly deleted on the MSGin5G Server 2.
Step 7.
Upon receiving the Messaging Topic list notification, the MSGin5G Server 1 updates the locally stored Messaging Topic list:
  1. if the Update status of a Messaging Topic is Created, the MSGin5G Server 1 adds the Messaging Topic to the locally stored Messaging Topic list; and
  2. if the Update status of a Messaging Topic is Deleted,
    1. if the Messaging Topic exists on MSGin5G Server 1, the MSGin5G Server 1 removes the Messaging Topic from the locally stored Messaging Topic list; and
    2. if the Messaging Topic does not exist on MSGin5G Server 1, the MSGin5G Server 1 ignores this Messaging Topic update.
Up

8.8.4.2a  Messaging Topic list unsubscription  p. 115

Corresponding to message topic list subscription, the MSGin5G Server 1 can unsubscribe the available Messaging Topic list on the MSGin5G Server 2 if it decides to stop to forward the Messaging Topic subscription request to MSGin5G Server 2, or to subscribe to the Messaging Topic on behalf of all MSGin5G UE/Application Server served by it on MSGin5G Server 2, based on decision of service provider.
Figure 8.8.4.2a-1 shows theMSGin5G Server 1 unsubscribing to Messaging Topic list on the MSGin5G Server2.
Pre-conditions:
  1. MSGin5G Server 1 and MSGin5G Server 2 have established a secured connection.
  2. The MSGin5G Server 1 has subscribed Messaging Topic list on the MSGin5G Server 2.
Copy of original 3GPP image for 3GPP TS 23.554, Fig. 8.8.4.2a-1: MSGin5G Server 1 unsubscribes to Messaging Topic list on the MSGin5G Server 2
Figure 8.8.4.2a-1: MSGin5G Server 1 unsubscribes to Messaging Topic list on the MSGin5G Server 2
(⇒ copy of original 3GPP image)
Up
Step 1.
The MSGin5G Server 1 sends a Messaging Topic list unsubscription request to the MSGin5G Server 2. The request includes the information elements listed in Table 8.8.4.2a-1.
Information element Status Description
Originating MSGin5G Server addressMThe MSGin5G Server which requests the unsubscription of the Messaging Topic list.
Recipient MSGin5G Server addressMThe MSGin5G Server which holds the Messaging Topic list.
Security credentialsOSecurity information required by the MSGin5G Server 2 and is left for implementation.
Step 2.
Upon receiving the Messaging Topic list unsubscription request, the MSGin5G Server 2 validates this request and may verify the security credentials.
Step 3.
The MSGin5G Server 2 checks the locally stored Messaging Topic list subscription(s) and removes previous Message Topic list subscription from MSGin5G Server 1.
Step 4.
The MSGin5G Server 2 sends a Messaging Topic list unsubscription response to MSGin5G Server 1. The response includes the information listed in Table 8.8.4.2a-2.
Information element Status Description
Subscription statusMIndicates whether the subscription was successfully deleted on the MSGin5G Server.
Up

8.8.4.3  Messaging Topic Subscription between different MSGin5G Servers  p. 116

If the MSGin5G Server 1 works in Mod.A (see clause 8.8.4.1), upon receiving a Messaging Topic subscription request from MSGin5G Client or Application Server, if the Messaging Topic is included in the Messaging Topic list of MSGin5G Server 2, the MSGin5G Server 1 forwards the Messaging Topic subscription request to MSGin5G Server 2. Otherwise, the MSGin5G Server 1 handles the Messaging Topic subscription request as specified in clause 8.8.3.
If the MSGin5G Server 1 works in Mod.B (see clause 8.8.4.1), upon receiving a Messaging Topic subscription request from MSGin5G Client or Application Server, if the Messaging Topic is not included in the Messaging Topic list of MSGin5G Server 2, the MSGin5G Server 1 handles the Messaging Topic subscription request as specified in clause 8.8.1. Otherwise, it may subscribe one or more Messaging Topic(s) from the Messaging Topic list by using the procedure specified in clause 8.8.1 with the clarification listed below.
The procedure for the Messaging Topic subscription for both Mod. A and Mod. B. between MSGin5G Servers is as follows:
Step 1.
The MSGin5G Server 1 includes the information elements listed in Table 8.8.4.3-1 instead of the information elements listed in Table 8.8.1-1.
Information element Status Description
Originating UE Service ID/AS Service ID (see NOTE 1)OThe service identity of the sending MSGin5G Client or the sending Application Server.
This IE shall be included if MSGin5G Server 1 forwards Messaging Topic subscription request from the MSGin5G UE/Application Server served by it to MSGin5G Server 2.
MSGin5G Server address (see NOTE 1)OThe MSGin5G Server which subscribes the Messaging Topic(s).
This IE shall be included if MSGin5G Server 1 subscribe the Messaging Topic on behalf of all MSGin5G UE/Application Server served by it.
Security credentialsOSecurity information required by the MSGin5G Server 2 and is left for implementation.
Messaging Topic (see NOTE 2)MA list of Messaging Topic(s) that is to be subscribed. The number of Messaging Topic(s) included in this IE can be one or more.
ExpirationOThe date and time when the subscription expires.
This date and time apply to all Messaging Topic(s) subscribed in this request.
If this IE is included, the value of it should be larger than 0.
If this IE is not included, the expiration time is subject to operator policy.
NOTE 1:
Only one of these IEs shall be included.
NOTE 2:
The content of the Messaging Topic is out of scope of 3GPP specifications.
Step 2.
Upon receiving the Messaging Topic subscription request, the MSGin5G Server 2 validates this request and may verify the security credentials.
Step 3.
The MSGin5G Server 2 handles the Originating UE Service ID/AS Service ID or MSGin5G Server address included in the Messaging Topic subscription request as the UE Service ID/AS Service ID included in Table 8.8.1-1.
Up

8.8.4.4  Messaging Topic Unsubscription between different MSGin5G Servers  p. 117

If the MSGin5G Server 1 works in Mod.A (see clause 8.8.4.1), and upon receiving a Messaging Topic unsubscription request from MSGin5G Client or Application Server, and if the Messaging Topic is included in the Messaging Topic list of MSGin5G Server 2, the MSGin5G Server 1 forwards the Messaging Topic unsubscription request to MSGin5G Server 2. Otherwise, the MSGin5G Server 1 handles the Messaging Topic unsubscription request as specified in clause 8.8.1.
If the MSGin5G Server 1 works in Mod.B (see clause 8.8.4.1), it may also unsubscribe one or more Messaging Topic(s) from the Messaging Topic list held on MSGin5G Server 2 by using the procedure specified in clause 8.8.3 with the clarification listed below.
The procedure for the Messaging Topic unsubscription for both Mod. A and Mod. B. between MSGin5G Servers is as follows:
Step 1.
The MSGin5G Server 1 includes the information elements listed in Table 8.8.4.4-1 instead of the information elements listed in Table 8.8.3-1.
Information element Status Description
Originating UE Service ID/AS Service ID (see NOTE 1)OThe service identity of the sending MSGin5G Client or the sending Application Server.
This IE shall be included if MSGin5G Server 1 forwards Messaging Topic unsubscription request from the MSGin5G UE/Application Server served by it to MSGin5G Server 2.
MSGin5G Server address (see NOTE 1)OThe MSGin5G Server which unsubscribes the Messaging Topic(s).
This IE shall be included if MSGin5G Server 1 subscribe the Messaging Topic on behalf of all MSGin5G UE/Application Server served by it.
Security credentialsOSecurity information required by the MSGin5G Server 2 and is left for implementation.
Messaging TopicMA list of Messaging Topic(s) that is to be unsubscribed. The number of Messaging Topic(s) included in this IE can be one or more.
NOTE 1:
Only one of these IEs shall be included.
Step 2.
Upon receiving the Messaging Topic unsubscription request, the MSGin5G Server 2 validates this request and may validate the security credentials.
Step 3.
The MSGin5G Server 2 handles the Originating UE Service ID/AS Service ID or MSGin5G Server address included in the Messaging Topic unsubscription request as the UE Service ID/AS Service ID included in Table 8.8.3-1.
Up

Up   Top   ToC