7.8 Conversation management

23.2823GPPFunctional architecture and information flows to support Mission Critical Data (MCData)Release 18Stage 2TS

7.8.1 General

Conversation management is a collection of related MCData transmissions for a given activity. Conversation management associates SDS and FD communication transmission and present them as a single thread to the user.

Conversation management for on-network is described in clause 7.8.2 and for off-network in clause 7.8.3. Off-network conversation management is based on ProSe capabilities as described in clause 7.16.

7.8.2 Conversation management for on-network

7.8.2.1 Information flows for conversation management

The information flow parameters related to conversation management are as described in the subclauses 7.4.2.1 and subclauses 7.5.2.1.5, 7.5.2.1.6, 7.5.2.1.7, 7.5.2.1.8, 7.5.2.1.9, 7.5.2.1.10, 7.5.2.1.11, 7.5.2.1.12, and 7.5.2.1.13.

7.8.2.2 One-to-one conversation management

7.8.2.2.1 Procedure

The procedure for an MCData user to associate multiple MCData transmissions between a pair of users for a given activity is illustrated in figure 7.8.2.2.1-1.

Pre-conditions:

1. MCData user(s) on MCData client 1 and 2 are registered for receiving MCData service.

Figure 7.8.2.2.1-1: One-to-one conversation management

1. The user at MCData client 1 initiates conversation. A universally unique conversation identifier is generated to identify new conversation. Conversation identifier is used in procedures mentioned in step 2. If the intent of the user at MCData client 1 is to transmit within an existing conversation, then corresponding conversation identifier is used in procedures mentioned in step 2. To allow multiple parallel conversations for the same pair of users, different conversation identifier is used for each conversation. The MCData users can view the MCData conversation at any time after the first MCData transaction is initiated within the conversation.

2. The procedure of one-to-one SDS or one-to-one FD or combination of both these procedures can be executed.

7.8.2.3 Group conversation management

7.8.2.3.1 Procedure

The procedure for an MCData user to associate multiple MCData transmissions between users of a group for a given activity is illustrated in figure 7.8.2.3.1-1.

Pre-conditions:

1. MCData user(s) on MCData client 1, 2, and n are registered for receiving MCData service.

2. The MCData users 1, 2 and n are members of the same MCData group and affiliated to the MCData service.

Figure 7.8.2.3.1-1: Group conversation management

1. The user at MCData client 1 initiates conversation. A unique conversation identifier is generated to identify new conversation. Conversation identifier is used in procedures mentioned in step 2. If the intent of the user at MCData client 1 is to transmit within an existing conversation, then corresponding conversation identifier is used in procedures mentioned in step 2. To allow multiple parallel conversations for the same group of users, different conversation identifier is used for each conversation. The MCData users can view the MCData conversation at any time after the first MCData transaction is initiated within the conversation.

2. The procedure of group SDS or group FD or combination of both these procedures can be executed.

7.8.3 Conversation management for off-network

7.8.3.1 One-to-one conversation management

7.8.3.1.1 Procedure

The procedure for an MCData user to associate multiple off-network MCData transmissions between a pair of users is illustrated in figure 7.8.3.1.1-1.

Pre-conditions:

1. MCData client 1 and MCData client 2 are members of the same ProSe Discovery group and are ProSe 1:1 direct communication capable.

2. MCData client 1 has discovered MCData client 2 in proximity, associated with MCData user B, using ProSe Discovery procedures.

Figure 7.8.3.1.1-1: One-to-one conversation management

1. The user at MCData client 1 initiates conversation. A universally unique conversation identifier is generated to identify the new conversation. Conversation identifier is used in the procedures mentioned in step 2. If the intent of the user at MCData client 1 is to transmit within an existing conversation, then corresponding conversation identifier from the existing conversation is used in the procedures mentioned in step 2. To allow multiple parallel conversations for the same pair of users, different conversation identifier is used for each conversation. The MCData users can view the MCData conversation at any time after the first MCData transaction is initiated within the conversation.

2. The procedure of one-to-one SDS or one-to-one FD or a combination of these can be executed.

7.8.3.2 Group conversation management

7.8.3.2.1 Procedure

The procedure for an MCData user to associate multiple off-network MCData transmissions between users of a group is illustrated in figure 7.8.3.2.1-1.

Pre-conditions:

1. Information for ProSe direct communications corresponding to the MCData group and its mapping to ProSe Layer-2 Group ID are pre-configured in MCData client 1.

2. MCData client 1 to MCData client N are members of the same MCData group.

Figure 7.8.3.2.1-1: Group conversation management

1. The user at MCData client 1 initiates conversation. A universally unique conversation identifier is generated to identify the new conversation. Conversation identifier is used in the procedures mentioned in step 2. If the intent of the user at MCData client 1 is to transmit within an existing conversation, then corresponding conversation identifier from the existing conversation is used in the procedures mentioned in step 2. To allow multiple parallel conversations for the same group of users, different conversation identifier is used for each conversation. The MCData users can view the MCData conversation at any time after the first MCData transaction is initiated within the conversation.

2. The procedure of group SDS or group FD or combination of both can be executed.