Content for TS 23.180 Word version: 18.0.0
10.6 MCData service p. 49
10.6.1 IOPS short data service (IP connectivity functionality) p. 49
10.6.1.1 General p. 49
The support of the MCData short data service (SDS) based on the IP connectivity functionality in the IOPS mode of operation enables that the service is provided by the MCData clients over the IOPS MC connectivity function. The IOPS MC connectivity function provides IP connectivity for the communication among MCData users.
10.6.1.2 Information flows p. 49
10.6.1.2.1 IOPS MCData standalone data request p. 49
Table 10.6.1.2.1-1 describes the information flow for the IOPS MCData standalone data request from one MCData client to another MCData client. The packet(s) carrying the IOPS MCData standalone data request are transmitted from the sending MCData client to the IOPS MC connectivity function for distribution to the target MCData client.
| Information Element | Status | Description |
|---|---|---|
| IOPS MCData ID | M | The identity of the MCData user sending data |
| IOPS MCData ID | M | The identity of the MCData user towards which the data is sent |
| Conversation Identifier | M | Identifies the conversation |
| Transaction Identifier | M | Identifies the MCData transaction |
| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to |
| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) |
| Payload Destination Type | M | Indicates whether the payload is for application consumption or MCData user consumption |
| Application identifier (see NOTE) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) |
| Payload | M | SDS content |
|
NOTE:
The application identifier shall be included only if the payload destination type indicates that the payload is for application consumption.
|
||
10.6.1.2.2 IOPS MCData data disposition notification p. 50
Table 10.6.1.2.2-1 describes the information flow for the IOPS MCData data disposition notification from one MCData client to another MCData client. The packet(s) carrying the IOPS MCData data disposition notification are transmitted from the sending MCData client to the IOPS MC connectivity function for distribution to the target MCData client.
| Information Element | Status | Description |
|---|---|---|
| IOPS MCData ID | M | The identity of the MCData user towards which the notification is sent |
| IOPS MCData ID | M | The identity of the MCData user sending notification |
| Conversation Identifier | M | Identifies the conversation |
| Disposition association | M | Identity of the original MCData transaction |
| Disposition | M | Disposition which is delivered or read or both |
10.6.1.2.3 IOPS MCData group standalone data request p. 50
Table 10.6.1.2.3-1 describes the information flow for the IOPS MCData group standalone data request from one MCData client to other MCData clients. The packet(s) carrying the IOPS MCData group standalone data request are transmitted from the sending MCData client to the IOPS MC connectivity function for distribution to the target MCData clients.
| Information Element | Status | Description |
|---|---|---|
| IOPS MCData ID | M | The identity of the MCData user sending data |
| IOPS MCData group ID | M | The IOPS MCData group ID to which the data is to be sent |
| Conversation Identifier | M | Identifies the conversation |
| Transaction Identifier | M | Identifies the MCData transaction |
| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to |
| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) |
| Payload Destination Type | M | Indicates whether the payload is for application consumption or MCData user consumption |
| Application identifier (see NOTE) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) |
| Payload | M | SDS content |
|
NOTE:
The application identifier shall be included only if the payload destination type indicates that the payload is for application consumption.
|
||
10.6.1.3 IOPS one-to-one standalone SDS using signalling control plane p. 50
10.6.1.3.1 General p. 50
When an MCData user initiates an IOPS standalone SDS data transfer with another MCData user using the signalling control plane based on the IP connectivity functionality, the MCData client retrieves the connectivity information of the target MCData user (i.e. the MCData UE's IP address) from the IOPS connectivity client. Then, the MCData client enables the IOPS SDS data transfer over the IOPS MC connectivity function. The related session packets, i.e. signalling messages, carrying the data are transmitted to the IOPS MC connectivity function addressing the corresponding target MCData UE's IP address.
The IOPS MC connectivity function distributes the received session packets over unicast transmissions to the target MCData client.
10.6.1.3.2 Procedure p. 51
The procedure in Figure 10.6.1.3.2-1 describes the case where an MCData user is initiating an IOPS one-to-one MCData communication for sending standalone SDS data over signalling control plane to another MCData user, with or without disposition request. Standalone refers to sending unidirectional data in one transaction.
Pre-conditions:
- MCData user profile used for the IOPS mode of operation is pre-provisioned in the MCData UEs.
- MCData users have an active PDN connection to the IOPS MC connectivity function for the communication based on the IP connectivity functionality.
- The MCData users are discovered by the IOPS MC connectivity function supporting the IP connectivity functionality.
- MCData clients have retrieved connectivity information from target MCData users.
Figure 10.6.1.3.2-1: IOPS one-to-one standalone SDS using signalling control plane based on the IP connectivity functionality
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
Step 1.
The MCData user at MCData client 1 would like to initiate an IOPS SDS data transfer with the MCData user at MCData client 2 based on the IP connectivity functionality. The MCData client 1 checks whether the MCData user 1 is authorized to send an IOPS MCData standalone data request.
Step 2.
The MCData client 1 retrieves the connectivity information of the target MCData user from the IOPS connectivity client 1 (not shown in Figure) and sends an IOPS MCData standalone data request towards the MCData client 2. The MCData client 1 transmits the session packets carrying the IOPS MCData standalone data request to the IOPS MC connectivity function for distribution to the corresponding target MCData UE 2's IP address.
The IOPS MCData standalone data request contains the data payload, i.e. the SDS content. The request also contains a conversation identifier for message thread indication and may contain a disposition request if indicated by the user at MCData client 1.
Step 3.
The IOPS MC connectivity function receives the session packets addressing the MCData UE 2's IP address. The IOPS MC connectivity function checks if the MCData UE 2's IP address corresponds to a discovered MC user in order to distribute the received session packets. If it does, the IOPS MC connectivity function distributes the received session packets to the target MCData client over unicast transmissions.
Step 4.
The IOPS MC connectivity function distributes the session packets carrying the IOPS MCData standalone data request to the MCData client 2.
Step 5.
Upon the receipt of the IOPS MCData standalone data request, the MCData client 2 checks whether any policy is to be asserted to limit certain types of message or content to certain members due to, for example, location or user privilege. If the policy assertion is positive and the payload is for MCData user consumption (e.g. it is not application data, not command instructions, etc.) then the MCData client 2 notifies the target MCData user.
The actions taken when the payload contains application data or command instructions are based on the payload content. Payload content received by MCData client 2 which is addressed to a known local non-MCData application that is not yet running shall cause the MCData client 2 to start the local non-MCData application (i.e., remote start application) and shall pass the payload content to the just started application.
Step 6.
If MCData data disposition was indicated (for delivery, read or both) within the request sent by the MCData client 1, then the receiving MCData client 2 initiates the corresponding IOPS MCData data disposition notification(s) towards the MCData client 1, i.e. addressing the MCData UE 1's IP address.
Step 7.
The IOPS MC connectivity function receives the session packets addressing the MCData UE 1's IP address. The IOPS MC connectivity function checks if the MCData UE 1's IP address corresponds to a discovered MC user in order to distribute the received session packets. If it does, the IOPS MC connectivity function distributes the received session packets to the target MCData client over unicast transmissions.
Step 8.
The IOPS MC connectivity function distributes the session packets carrying the IOPS MCData data disposition notification to the MCData client 1.
10.6.1.4 IOPS group standalone SDS using signalling control plane p. 52
10.6.1.4.1 General p. 52
IOPS group standalone SDS using signalling control plane based on the IP connectivity functionality can use pre-configured information provided to MCData clients prior to initiating the data service. When an MCData client initiates an IOPS group standalone SDS based on the IP connectivity functionality it uses the pre-configured IOPS group IP multicast address associated to the target IOPS MCData group ID. The related group session packets, i.e. signalling messages, carrying the data are transmitted to the IOPS MC connectivity function for distribution to the corresponding discovered MC users of the target IOPS MCData group.
The IOPS MC connectivity function can distribute the group session packets to the discovered MC users over MBMS bearers as described in clause 10.4.5.
The IOPS MC connectivity function can also replicate and distribute the group session packets over unicast transmissions to MCData UEs associated to the target IOPS MCData group. MCData UEs receiving the group session packets are associated to discovered MC users that included the target IOPS MCData group ID within the IOPS discovery request, as described in clause 10.5.2.3.
10.6.1.4.2 Procedure p. 53
The procedure in Figure 10.6.1.4.2-1 describes the case where an MCData user is initiating an IOPS group MCData communication for sending standalone SDS data over signalling control plane to an IOPS MCData group, with or without disposition request. Standalone refers to sending unidirectional data in one transaction.
Pre-conditions:
- MCData user profile used for the IOPS mode of operation is pre-provisioned in the MCData UEs.
- The IOPS MCData group ID and its associated IOPS group IP multicast address are pre-configured in the MCData clients.
- MCData users have an active PDN connection to the IOPS MC connectivity function for the communication based on the IP connectivity functionality.
- MCData users affiliated to the target IOPS MCData group are discovered by the IOPS MC connectivity function supporting the IP connectivity functionality.
- The IOPS MC connectivity function may have established an MBMS bearer and announced it to the MCData clients.
- MCData client 1 may have retrieved group connectivity information from the IOPS connectivity client related to the target IOPS MCData group.
- MCData clients 1, 2 … n are configured within the same IOPS MCData group.
Figure 10.6.1.4.2-1: IOPS group standalone SDS using signalling control plane based on the IP connectivity functionality
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
Step 1.
The MCData user at MCData client 1 would like to initiate an IOPS SDS data transfer with a specific IOPS MCData group based on the IP connectivity functionality. The MCData client 1 checks whether the MCData user 1 is authorized to send an IOPS MCData group standalone data request.
Step 2.
The MCData client 1 sends an IOPS MCData group standalone data request to the target IOPS MCData group. The MCData client 1 transmits the group session packets carrying the IOPS MCData group standalone data request to the IOPS MC connectivity function for distribution to the corresponding IOPS group IP multicast address.
The IOPS MCData group standalone data request contains the data payload, i.e. the SDS content. The request also contains a conversation identifier for message thread indication and may contain a disposition request if indicated by the user at MCData client 1.
Step 3.
The IOPS MC connectivity function determines that the received packets correspond to a group session targeting a specific IOPS MCData group. The IOPS MC connectivity function decides distributing the received group session packets to the target MCData clients over MBMS and/or unicast transmissions.
Step 4.
The IOPS MC connectivity function distributes the group session packets carrying the IOPS MCData group standalone data request to the discovered MCData clients from the target IOPS MCData group.
Step 5.
The MCData clients receiving the IOPS MCData group standalone data request check whether any policy is to be asserted to limit certain types of message or content to certain members due to, for example, location or user privilege. If the policy assertion is positive and the payload is for MCData user consumption (e.g. it is not application data, not command instructions, etc.) then the MCData clients notify the target MCData users.
The actions taken when the payload contains application data or command instructions are based on the payload content. Payload content received by an MCData client which is addressed to a known local non-MCData application that is not yet running shall cause the MCData client to start the local non-MCData application (i.e., remote start application) and shall pass the payload content to the just started application.
Step 6.
If MCData data disposition was indicated (for delivery, read or both) within the request sent by the MCData client 1, then the receiving MCData clients initiate the corresponding IOPS MCData data disposition notification(s) towards the MCData client 1, i.e. addressing the MCData UE 1's IP address.
Step 7.
The IOPS MC connectivity function receives the session packets addressing the MCData UE 1's IP address. The IOPS MC connectivity function checks if the MCData UE 1's IP address corresponds to a discovered MC user in order to distribute the received session packets. If it does, the IOPS MC connectivity function distributes the received session packets to the target MCData client over unicast transmissions.
Step 8.
The IOPS MC connectivity function distributes the session packets carrying the IOPS MCData data disposition notification to the MCData client 1.
