Content for TS 23.554 Word version: 18.2.0
1…
4…
5…
5.5…
6…
7…
8…
8.2…
8.2.3…
8.2.5…
8.3…
8.3.4…
8.4…
8.5…
8.6…
8.7…
8.7.2…
8.7.3…
8.7.4…
8.7.5…
8.8…
8.9…
8.9.3…
8.10…
8.11…
9…
10…
8.8 Other MSGin5G messaging related procedures
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 handling between different MSGin5G Servers
...
...
8.8 Other MSGin5G messaging related procedures p. 101
8.8.1 Messaging Topic Subscription p. 101
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 subscriber.
Figure 8.8.1-1 shows the MSGin5G Client/Application Server subscribing to Messaging Topic(s) on the MSGin5G Server.
Pre-conditions:
- The MSGin5G Client or Application Server has registered to the MSGin5G Server.
Figure 8.8.1-1: MSGin5G Service endpoint subscribes to Messaging topic(s)
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
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 ID | M | The service identity of the sending MSGin5G Client or the sending Application Server. |
| Messaging Topic | M | A 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. |
| Expiration | O | The 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 local stored Messaging Topic(s).
Step 3.
-
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.
- 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.
- Else, the MSGin5G Server updates the validity time of this subscription.
- 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.
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 status | M | Indicates whether the subscription was successfully added or deleted on the MSGin5G Server. |
| Expiration | O | The validity date and time of this subscription set by the MSGin5G Server. |
8.8.2 Message delivery based on Messaging Topic p. 102
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:
- 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.
Figure 8.8.2-1: Message delivery to subscribing service endpoint based on Messaging Topic
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
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 the subscription exists.
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 outbound 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.
8.8.3 Messaging Topic Unsubscription p. 103
Corresponding to message topic unsubscription, an MSGin5G Client or an Application Server can unsubscribe 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-conditions:
- The MSGin5G Client or Application Server has subscribed one or more message topic(s) on the MSGin5G Server.
Figure 8.8.3-1: MSGin5G Service endpoint unsubscribes to Messaging topic(s)
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
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 ID | M | The service identity of the sending MSGin5G Client or the sending Application Server. |
| Messaging Topic(s) | M | A 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. |
Step 2.
The MSGin5G Server validates the Messaging Topic unsubscription request and checks the local stored Messaging Topic(s). If the subscribed Messaging Topic has already been created and if the UE Service ID/AS Service ID of the subscriber is already 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 status | M | Indicates whether the subscription was successfully deleted on the MSGin5G Server |
8.8.4 Messaging Topic handling between different MSGin5G Servers |R18| p. 104
8.8.4.1 General p. 104
When Messaging Topic(s) is handled between different MSGin5G Servers, the MSGin5G Server 1 may work in the following models:
- Mod.A: the MSGin5G UE/Application Server served by MSGin5G Server 1 subscribes Messaging Topic(s) on MSGin5G Server 2 directly. In this case, the MSGin5G Server 1 forwards Messaging Topic subscription request from the MSGin5G UE/Application Server served by it to MSGin5G Server 2 or
- Mod.B: the MSGin5G Server 1 subscribes the Messaging Topic(s) on behalf of all MSGin5G UE/Application Server served by it.
8.8.4.2 Messaging Topic list subscription p. 105
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 forwards the Messaging Topic subscription request to MSGin5G 2, or subscribes Messaging Topic on behalf of all MSGin5G UE/Application Server served by it on MSGin5G 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:
- MSGin5G Server 1 and MSGin5G Server 2 have established a secured connection.
Figure 8.8.4.2-1: MSGin5G Server 1 subscribes to Messaging Topic list on the MSGin5G Server 2
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
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 |
|---|---|---|
| MSGin5G Server address | M | The MSGin5G Server which subscribes the Messaging Topic list. |
| Security credentials | O | Security information required by the MSGin5G Server 2. If the MSGin5G Server 1 and MSGin5G Server 2 are located in the same PLMN, this information element is not mandatory. This is a placeholder for SA3 security information. |
| Expiration | O | The 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 verifies the security credentials.
Step 3.
The MSGin5G Server 2 checks the local stored Messaging Topic list subscription (s).
Step 4.
- If the MSGin5G Server 1's subscription has already been created, the MSGin5G Server 2 updates the validity time of this subscription.
- If the MSGin5G Server 1's subscription has not been created, the MSGin5G Server 2 creates the subscription.
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 status | M | Indicates whether the subscription was successfully added or deleted on the MSGin5G Server 2. |
| Expiration | O | The 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 request to MSGin5G Server 1. The request includes the information listed in Table 8.8.4.2-3.
| Information element | Status | Description |
|---|---|---|
| Expiration | O | The new validity date and time of this subscription set by the MSGin5G Server 2. |
| >Messaging Topic list | M | A list of Messaging Topic(s) that is(are) existing 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 is(are) existing on the MSGin5G Server 2 in this Messaging Topic list notification, 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 the service, the MSGin5G Server 2 may only choose a part of Messaging Topic(s) which are allowed to be subscribe by MSGin5G Server 1 in the notification. |
| Information element | Status | Description |
|---|---|---|
| Messaging Topic | M | Unique identifier of this Messaging Topic. |
| Update status | M | Identifies 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 local stored Messaging Topic list:
- if the Update status of a Messaging Topic is created, the MSGin5G Server 1 adds the Messaging Topic to thelocal stored Messaging Topic list; and
-
if the Update status of a Messaging Topic is deleted,
- if the Messaging Topic is existed on MSGin5G Server 1,the MSGin5G Server 1 removes the Messaging Topic from thelocal stored Messaging Topic list; and
- if the Messaging Topic is existed on MSGin5G Server 1,the MSGin5G Server 1 ignores this Messaging Topic.
8.8.4.3 Messaging Topic Subscription between different MSGin5G Servers p. 107
If the MSGin5G Server 1 works in Mod.A, 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.1.
If the MSGin5G Server 1 works in Mod.B, 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:
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) | O | The service identity of the sending MSGin5G Client or the sending Application Server. This IE should 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) | O | The MSGin5G Server which subscribes the Messaging Topic(s). This IE should be included if MSGin5G Server 1 subscribe the Messaging Topic on behalf of all MSGin5G UE/Application Server served by it. |
| Security credentials | O | Security information required by the MSGin5G Server 2. If the MSGin5G Server 1 and MSGin5G Server 2 are located in the same PLMN, this information element is not mandatory. This is a placeholder for SA3 security information. |
| Messaging Topic (see NOTE 2) | M | A 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. |
| Expiration | O | The 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 the present document.
|
||
Step 2.
Upon receiving the Messaging Topic subscription request, the MSGin5G Server 2 validates this request and verifies 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.
8.8.4.4 Messaging Topic Unsubscription between different MSGin5G Servers p. 108
If the MSGin5G Server 1 works in Mod.A, upon receiving a Messaging Topic unsubscription 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 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, it may also unsubscribe one or more Messaging Topic(s) from the Messaging Topic list by using the procedure specified in clause 8.8.3 with the clarification listed below:
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) | O | The service identity of the sending MSGin5G Client or the sending Application Server. This IE should 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) | O | The MSGin5G Server which unsubscribes the Messaging Topic(s). This IE should be included if MSGin5G Server 1 subscribe the Messaging Topic on behalf of all MSGin5G UE/Application Server served by it. |
| Security credentials | O | Security information required by the MSGin5G Server 2. If the MSGin5G Server 1 and MSGin5G Server 2 are located in the same PLMN, this information element is not mandatory. This is a placeholder for SA3 security information. |
| Messaging Topic | M | A 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 verifies 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.
