hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.1.3 MCData communication release request (group communication using media plane)
|
Table 7.7.2.1.3-1 describes the information flow for the MCData communication release request (in subclause 7.7.2.2.2.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client.
Table 7.7.2.1.3-1: MCData communication release request (group communication using media plane)
Information element
Status
Description
MCData ID
M
The identity of the MCData user uploading data
MCData group ID
M
MCData group ID on which the communication is to be released
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.1.4 MCData communication release response (group communication using media plane)
|
Table 7.7.2.1.4-1 describes the information flow for the MCData communication release response (in subclause 7.7.2.2.2.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client.
Table 7.7.2.1.4-1: MCData communication release response (group communication using media plane)
Information element
Status
Description
MCData ID
M
The identity of the MCData user requesting to upload data
MCData group ID
M
MCData group ID on which the communication is released
Release confirmation
M
Communication released or not indication
7.7.2.1.5 Void
7.7.2.1.6 Void
7.7.2.1.7 Void
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.1.8 MCData server communication release request (one-to-one communication using media plane)
|
Table 7.7.2.1.8-1 describes the information flow for MCData server communication release request (in subclause 7.7.2.3.2.2) sent from the MCData server to the MCData clients involved in one-to-one communication.
Table 7.7.2.1.8-1: MCData server communication release request (one-to-one communication using media plane)
Information element
Status
Description
MCData ID
M
The identity of the MCData user to which communication is released
Conversation Identifier
M
Identifies the conversation
Release Reason
M
Indicates reason for the release
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.1.9 MCData server communication release response (one-to-one communication using media plane)
|
Table 7.7.2.1.9-1 describes the information flow for the MCData server communication release response (in subclause 7.7.2.3.2.2) sent from the MCData client to the MCData server.
Table 7.7.2.1.9-1: MCData server communication release response (one-to-one communication using media plane)
Information element
Status
Description
MCData ID
M
MCData ID to which the communication is released
Conversation Identifier
M
Identifies the conversation
Release confirmation
M
Communication released or not indication
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.1.10 MCData server communication release request (group communication using media plane)
|
Table 7.7.2.1.10-1 describes the information flow for MCData server communication release request (in subclause 7.7.2.3.2.2) sent from the MCData server to the MCData clients involved in group communication.
Table 7.7.2.1.10-1: MCData server communication release request (group communication using media plane)
Information element
Status
Description
MCData ID
M
The identity of the MCData user to which communication is released
MCData group ID
M
MCData group ID on which the communication is released
Conversation Identifier
M
Identifies the conversation
Release Reason
M
Indicates reason for the release
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.1.11 MCData server communication release response (group communication using media plane)
|
Table 7.7.2.1.11-1 describes the information flow for the MCData server communication release response (in subclause 7.7.2.3.2.2) sent from the MCData client to the MCData server.
Table 7.7.2.1.11-1: MCData server communication release response (group communication using media plane)
Information element
Status
Description
MCData ID
M
MCData ID to which the communication is released
MCData group ID
M
MCData group ID on which the communication is released
Conversation Identifier
M
Identifies the conversation
Release confirmation
M
Communication released or not indication
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.1.12 Void
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.1.13 MCData release intent request (one-to-one communication using media plane)
|
Table 7.7.2.1.13-1 describes the information flow for MCData release intent request (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the MCData server to the MCData client.
Table 7.7.2.1.13-1: MCData release intent request (one-to-one communication using media plane)
Information element
Status
Description
MCData ID
M
The identity of the MCData user who is originator of the one-to-one communication
Conversation Identifier
M
Identifies the conversation
Request for more info
O
Indicates what MCData server needs more information (e.g. to know the remaining data volume to transmit) about the communication which has been identified to be released
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.1.14 MCData more information response (one-to-one communication using media plane)
|
Table 7.7.2.1.14-1 describes the information flow for MCData more information response (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the MCData client to the MCData server and from MCData server to authorized MCData user.
Table 7.7.2.1.14-1: MCData more information response (one-to-one communication using media plane)
Information element
Status
Description
MCData ID
M
The identity of the MCData user who is originator of the one-to-one communication
Conversation Identifier
M
Identifies the conversation
More info
M
Information as requested by MCData server
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.1.15 MCData release intent request (group communication using media plane)
|
Table 7.7.2.1.15-1 describes the information flow for MCData release intent request (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the MCData server to the MCData client.
Table 7.7.2.1.15-1: MCData release intent request (group communication using media plane)
Information element
Status
Description
MCData ID
M
The identity of the MCData user who is the originator of the group communication
Conversation Identifier
M
Identifies the conversation
MCData group ID
M
MCData group ID on which the communication is released
Request for more info
O
Indicates what MCData server needs more information about the communication which has been identified to be released
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.1.16 MCData more information response (group communication using media plane)
|
Table 7.7.2.1.16-1 describes the information flow for MCData more information response (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the MCData client to the MCData server and from MCData server to authorized MCData user.
Table 7.7.2.1.16-1: MCData more information response (group communication using media plane)
Information element
Status
Description
MCData ID
M
The identity of the MCData user who is originator of the group communication
Conversation Identifier
M
Identifies the conversation
MCData group ID
M
MCData group ID on which the communication is released
More info
M
Information as requested by MCData server
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.1.17 MCData auth user communication release request (one-to-one communication using media plane)
|
Table 7.7.2.1.17-1 describes the information flow for MCData auth user communication release request (in subclause 7.7.2.5.2, 7.7.2.6.2) sent from the authorized MCData user to the MCData server.
Table 7.7.2.1.17-1: MCData auth user communication release request (one-to-one communication using media plane)
Information element
Status
Description
Conversation Identifier
M
Identifies the conversation
Request for more info
O
Indicates what MCData server needs more information about the communication which has been identified to be released
Release Reason
M
Indicates reason for the release
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.1.18 MCData auth user communication release response (one-to-one communication using media plane)
|
Table 7.7.2.1.18-1 describes the information flow for the MCData server communication release response (in subclause 7.7.2.5.2, 7.7.2.6.2) sent from the MCData server to the authorized MCData user.
Table 7.7.2.1.18-1: MCData auth user communication release response (one-to-one communication using media plane)
Information element
Status
Description
Conversation Identifier
M
Identifies the conversation
Release confirmation
M
Communication released or not indication
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.1.19 MCData auth user communication release request (group communication using media plane)
|
Table 7.7.2.1.19-1 describes the information flow for MCData auth user communication release request (in subclause 7.7.2.5.2, 7.7.2.6.2) sent from the authorized MCData user to the MCData server.
Table 7.7.2.1.19-1: MCData auth user communication release request (group communication using media plane)
Information element
Status
Description
Conversation Identifier
M
Identifies the conversation
MCData group ID
M
MCData group ID on which the communication is to be released
Request for more info
O
Indicates what MCData server needs more information about the communication which has been identified to be released
Release Reason
M
Indicates reason for the release
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.1.20 MCData auth user communication release response (group communication using media plane)
|
Table 7.7.2.1.20-1 describes the information flow for the MCData server communication release response (in subclause 7.7.2.5.2, 7.7.2.6.2) sent from the MCData server to the authorized MCData user.
Table 7.7.2.1.20-1: MCData auth user communication release response (group communication using media plane)
Information element
Status
Description
Conversation Identifier
M
Identifies the conversation
MCData group ID
M
MCData group ID on which the communication is to be released
Release confirmation
M
Communication released or not indication
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.1.21 MCData request for extension
|
Table 7.7.2.1.21-1 describes the information flow for the MCData request for extension (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the MCData client to the MCData server and from MCData server to authorized MCData user.
Table 7.7.2.1.21-1: MCData request for extension
Information element
Status
Description
Conversation Identifier
M
Identifies the conversation
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.1.22 MCData response for extension
|
Table 7.7.2.1.22-1 describes the information flow for the MCData response for extension (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the authorized MCData user to the MCData server and MCData client to the MCData server and from MCData server to MCData client.
Table 7.7.2.1.22-1: MCData response for extension
Information element
Status
Description
Conversation Identifier
M
Identifies the conversation
Extension response
M
Indicates whether request for extension has been accepted or not
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.2 MCData user initiated communication release
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.2.1 General
|
During MCData communication, a transmitting participant can at any time indicate to stop transmission to the MCData server.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.2.2 Release of MCData communication using media plane
|
7.7.2.2.2.1 General
The subclause describes the procedure for MCData user initiated MCData communication release where MCData communication is established as SDS using media plane or SDS session or file distribution using media plane.
NOTE: The release of MCData communication over MBMS is out of scope of the current specification.
7.7.2.2.2.2 Procedure
The procedure in figure 7.7.2.2.2.2-1 describes signalling control plane procedure for the case where MCData communication is ongoing and transmitting participant initiates MCData communication release. The procedure is applicable for one-to-one and group MCData communications.
Pre-conditions:
1. MCData users on MCData client 1 and client 2 are already registered for receiving MCData service.
2. MCData communication is established between MCData client 1 and MCData client 2 and MCData client1 is the initiator of the MCData communication.
Figure 7.7.2.2.2.2-1: Release of MCData communication using media plane
1. MCData user at MCData client 1 requests to release ongoing MCData communication.
2. MCData client 1 sends MCData communication release request towards MCData server, for tearing down the communication with the other MCData client(s).
3. MCData server sends MCData communication release request to all the participants of the MCData communication.
4. Recipient MCData clients notifies respective MCData user about the release of MCData communication.
5. MCData clients receiving the MCData communication release request provide communication release response back towards MCData server.
6. MCData server sends MCData communication release response back to MCData client 1.
7. All participants of the MCData communication have successfully released the media plane resources associated with the MCData communication that is released.
8. MCData client 1 notifies the MCData user about the communication release.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.2.3 Release of MCData communication using HTTP
|
NOTE: The backward compatibility handling of this procedure is outside the scope of the present document.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.3 MCData server initiated communication release without prior indication
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.3.1 General
|
MCData server initiates the release of an ongoing MCData communication, since at least one of the communication release conditions are met e.g. lack of bearer capacity, limit for the maximum amount of data or time that a participant transmits from a single request to transmit exceeded. Based on the configuration, MCData server either pre-empts the MCData communication without giving prior indication to MCData client or notifies the intent of release to the MCData client initiating communication. Latter scenario allows the MCData user to request for extension of MCData communication and defer the communication release.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.3.2 Release of MCData communication using media plane
|
7.7.2.3.2.1 General
The subclause describes the procedure for MCData server initiated MCData communication release without prior indication, where MCData communication is established as SDS using media plane or file distribution using media plane.
NOTE: The release of MCData communication over MBMS is out of scope of the current specification.
7.7.2.3.2.2 Procedure
The procedure in figure 7.7.2.3.2.2-1 describes signalling control plane procedure for the case where during an ongoing MCData communication, based on communication release conditions, MCData server initiates the communication release. The procedure is applicable for one-to-one and group communication.
Pre-conditions:
1. MCData users on MCData client 1, client 2 and client 3 are already registered for receiving MCData service.
2. A MCData administrator has configured the limits for the maximum amount of data and time that a participant transmits from a single request to transmit.
3. A MCData communication is ongoing between MCData client 1, client 2 and client 3.
Figure 7.7.2.3.2.2-1: MCData server initiated release of MCData communication using media plane
1. MCData server would like to release the ongoing MCData communication, identified by conversation identifier, since at least one of the release conditions are met e.g. lack of capacity, limit for the maximum amount of data or time that a participant transmits from a single request to transmit exceeded. Based on configuration, MCData server decides to pre-empt the MCData communication without giving prior indication to MCData client 1.
2. MCData server identifies the participants of the ongoing MCData communication and generates communication release request to release ongoing MCData communication.
3. MCData server sends server MCData communication release request towards each participant of the MCData communication.
4. MCData users are notified about the release of the MCData communication.
5. MCData client at each MCData communication participant sends server MCData communication release response towards the MCData server.
6. All participants of the MCData communication have successfully released the media plane resources associated with the MCData communication that is released.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.3.3 Void
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.4 MCData server initiated communication release with prior indication
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.4.1 General
|
The subclause describes the procedure for MCData server initiated MCData communication release with prior indication, where MCData communication is established as SDS using media plane or file distribution using media plane or file distribution using HTTP.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.4.2 Procedure
|
The procedure in figure 7.7.2.4.2-1 describes signalling control plane procedure for the case where during an ongoing MCData communication, based on communication release conditions, MCData server initiates communication release. As a result of configuration check, MCData server notifies the intent to release MCData communication, optionally requesting for more information (e.g. to know the remaining data volume to transmit) from the MCData client initiating MCData communication.
Pre-conditions:
1. MCData user on MCData client 1 is already registered for receiving MCData service.
2. MCData administrator has configured the limits for the maximum amount of data and time that a participant transmits from a single request to transmit.
3. MCData communication may be ongoing between MCData participants and MCData client 1 is the initiator of the communication.
4. MCData administrator has configured the time for which MCData server needs to wait for extension request from the MCData user.
Figure 7.7.2.4.2-1: MCData server initiates communication release with prior indication
1. MCData server releases the ongoing MCData communication, identified by the conversation identifier, since at least one of the release conditions are met e.g. lack of capacity, limit for the maximum amount of data or time that a participant transmits from a single request to transmit exceeded. Based on the configuration, MCData server notifies the intent to release MCData communication.
2. MCData server sends the MCData release intent request towards the communication initiating MCData client 1. MCData server may include request for more information (e.g. to know the remaining data volume to transmit).
3. MCData client 1 informs MCData user about the intent to release communication.
4. If request for more information is included in the received MCData release intent request, MCData client 1 sends MCData more information response including the remaining amount of data to transmit. Upon receiving more information response from MCData client 1, MCData server may wait for the request for extension until the time configured by the MCData administrator. If MCData server does not receive MCData request for extension within the configured timeout, the MCData server releases MCData communication as described in subclause 7.7.2.3. Otherwise, continue with remaining steps.
5. MCData user at MCData client 1 requests for extension of the ongoing MCData communication.
6. MCData client 1 sends MCData request for extension of the MCData communication.
7. Upon receiving the MCData request for extension of MCData communication from the MCData client 1, MCData server asserts policies to accept or reject the request for extension.
8. MCData server sends MCData response for extension with success or failure result to MCData client 1. MCData communication will continue if MCData server accepted the request for extension from MCData client 1. Otherwise, MCData communication is released according to procedures described in subclause 7.7.2.3.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.5 Authorized MCData user initiated communication release without prior indication
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.5.1 General
|
An authorized MCData user at any time during an ongoing MCData communication decides to release communication. The authorized user may decide to release MCData communication without prior indication to the initiator MCData client.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.5.2 Procedure
|
The procedure in figure 7.7.2.5.2-1 describes signalling control plane procedure for the case where during an ongoing MCData communication, authorized MCData user initiates MCData communication release without prior indication to the initiator MCData client. An authorized MCData user is part of the ongoing MCData communication.
Pre-conditions:
1. An authorized MCData user on MCData client is already registered for receiving MCData service.
2. A MCData communication is ongoing between MCData participants and authorized MCData user is keeping track of which participants are receiving communication e.g. through "message delivered" and/or "message read" indications for the MCData communication.
Figure 7.7.2.5.2-1: An authorized MCData user initiates communication release without prior indication
1. An authorized MCData user requests to release the ongoing MCData communication, without providing prior indication to the initiator of the MCData communication, MCData client 1.
2. An authorized MCData client sends MCData auth user communication release request towards MCData server identifying the MCData communication to release. The request also includes indication to the MCData server to release MCData communication without prior indication to the initiator of the MCData communication, MCData client 1.
3. MCData server validates the user from whom the MCData communication release request is received and checks whether the requesting MCData user is authorized to release communication or not.
4. If the user is authorized to release communication, then MCData server releases the ongoing MCData communication according to procedures described in subclause 7.7.2.3.
5. MCData server sends MCData auth user communication release response containing the result of MCData communication release back to authorized MCData client 1.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.6 Authorized MCData user initiated communication release with prior indication
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.6.1 General
|
An authorized MCData user at any time during an ongoing MCData communication decides to release communication. The authorized user may decide to release MCData communication with prior indication to the initiator MCData client. A prior indication allows initiator MCData client to request for extension for the MCData communication.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.7.2.6.2 Procedure
|
The procedure in figure 7.7.2.6.2-1 describes signalling control plane procedure for the case where during an ongoing MCData communication, authorized MCData user initiates MCData communication release with prior indication to the initiator MCData client. An authorized MCData user is part of the ongoing MCData communication. An initiator MCData user optionally decides to request for the extension of the ongoing communication.
Pre-conditions:
1. An authorized MCData user on MCData client is already registered for receiving MCData service.
2. A MCData communication is ongoing between MCData participants and authorized MCData user is keeping track of which participants are receiving communication e.g. through "message delivered" and/or "message read" indications for the MCData communication
3. MCData client 1 is the initiator of the MCData communication.
Figure 7.7.2.6.2-1: An authorized MCData user initiates communication release with prior indication
1. An authorized MCData user requests to release the ongoing MCData communication by providing prior indication to the initiator of MCData communication, MCData client 1.
2. An authorized MCData client sends MCData auth user communication release request towards MCData server including the communication identifier identifying the MCData communication to release. Authorized MCData client may include request for more information (e.g. to know the remaining data volume to transmit). The request also includes indication to MCData server to release MCData communication with prior indication to the initiator MCData client.
3. MCData server validates the user from whom the communication release request is received and checks whether the requesting user is authorized to release communication or not.
4. If the user is authorized to release communication, then the MCData server sends MCData release intent request, may be including the reason for the release. MCData server may include request for more information as received in the request from the authorized MCData client.
5. MCData client informs MCData user about the intent to release communication by the authorized MCData user.
6. If request for more information is included in the received MCData release intent request, MCData client 1 sends MCData more information response including the remaining amount of data to transmit.
7. MCData server forwards the MCData more information response to the authorized MCData client.
NOTE: Upon receiving more information response from MCData client 1, MCData server may wait for the request for extension until the time configured by the MCData administrator. If MCData server does not receive request for extension within the configured timeout, the MCData server releases MCData communication as described in subclause 7.7.2.3. Otherwise, continue with remaining steps.
8. MCData user at MCData client 1 decides to request for extension of the ongoing MCData communication.
9 and 10. MCData client sends MCData request for extension towards MCData server. And MCData server forwards the MCData request for extension towards the authorized MCData client.
11. Authorized MCData client notifies the authorized user about the incoming request for extension. An authorized MCData user decides to accept or reject the request for extension.
12 and 13. Authorized MCData user decision is sent in MCData response for extension request towards the MCData server. MCData server forwards the MCData response for extension request to MCData client 1.
14. MCData communication will continue if the authorized user accepted the request for extension from MCData client 1. Otherwise, MCData communication will be released according to procedures described in subclause 7.7.2.3.
15. After MCData communication is released, MCData server sends the MCData auth user communication release response back to the authorized MCData client.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.8 Conversation management
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.8.2 Conversation management for on-network
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.8.2.2 One-to-one conversation management
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.8.2.3 Group conversation management
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.8.3 Conversation management for off-network
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.8.3.1 One-to-one conversation management
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.8.3.2 Group conversation management
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.9 Enhanced status
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.9.1 General
|
Enhanced status corresponds to information specific to the activities performed by the mission critical service users during their operation(s) e.g. available, in operation on site, going to the operation site, or just arrived.
Enhanced status for on-network is described in clause 7.9.3 and for off-network in clause 7.9.4. Off-network enhanced status is based on ProSe capabilities as described in clause 7.16.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.9.2 Preset values for enhanced status
|
The enhanced status information i.e. the set of possible values corresponding to the activities of the MCData user, shall be configured by the MCData administrator. The configuration of status values is applicable on a per-group basis, and therefore shall be part of the MCData group configuration data as described in Annex A.4.
The configuration mechanism shall allow the MCData administrator to configure a minimum of 32 possible values and allow up to 65536 separate values. The set of values may be divided into a fixed set of values defined by 3GPP standards which are common across all MCData systems, and a set which may be freely configured for any purpose.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.9.3 Enhanced status for on-network
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.9.3.1 Sharing enhanced status information
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.9.3.1.1 Procedure
|
The procedure for an MCData user to share the enhanced status information to the members of the selected group is illustrated in figure 7.9.3.1.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.
3. The MCData group is pre-configured with the possible values for enhanced status information.
Figure 7.9.3.1.1-1: Sharing enhanced status information
1. The user at MCData client 1 selects the MCData group to share the enhanced status information. The user also selects the value of the status information to be shared from the list of pre-configured status values available for the MCData group.
2. The procedure of group standalone SDS using signalling control plane as described in subclause 7.4.2.5, is used to deliver the enhanced status information.
3. The MCData users at MCData client 2 and n are notified of the enhanced status information.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.9.4 Enhanced status for off-network
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.9.4.1 Sharing enhanced status information
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.9.4.1.1 Procedure
|
The procedure for an MCData user to share the enhanced status information to the members of the selected group is illustrated in figure 7.9.4.1.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, 2 and n are members of the same MCData group.
3. The MCData group is pre-configured with the possible values for enhanced status information.
Figure 7.9.4.1.1-1: Sharing enhanced status information
1. The user at MCData client 1 selects the MCData group to share the enhanced status information. The user also selects the value of the status information to be shared from the list of pre-configured status values available for the MCData group.
2. The procedure of off-network group standalone SDS using signalling control plane as described in subclause 7.4.3.4, is used to deliver the enhanced status information.
3. The MCData users at MCData client 2 and n are notified of the enhanced status information.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.10 MCData emergency alert (on-network and off-network)
|
The MCData service shall support the procedures and related information flows as specified in subclause 10.10 of 3GPP TS 23.280 [5] with the following clarifications:
- The MC service client is the MCData client;
- The MC service server is the MCData server;
- The MC service group ID is the MCData Group ID; and
- The MC service user profile index is the MCData user profile index.
7.10a MCData ad hoc group emergency alert (on-network)
The MCData service shall support the procedures and related information flows as specified in subclause 10.10.3 of 3GPP TS 23.280 [5] with the following clarifications:
- The MC service client is the MCData client;
- The MC service server is the MCData server;
- The MC service group ID is the MCData Group ID; and
- The MC service user profile index is the MCData user profile index.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.11 User authentication and authorization for MCData service
|
NOTE: Flow 7.11-1 is a high level user authentication and authorization flow. 3GPP TS 33.180 [13] defines the specific user authentication and authorization architecture required by the MCData service in order to realize the MCData user authentication and authorization requirements as defined in 3GPP TS 22.280 [2].
A procedure for user authentication is illustrated in figure 7.11-1. The user authentication is performed based on the procedure specified in subclause 10.6 of 3GPP TS 23.280 [5].
Figure 7.11-1: MCData user authentication and registration, single domain
1. The user authentication is performed as per the general user authentication procedure specified in subclause 10.6 of 3GPP TS 23.280 [5].
2. MCData client performs the MCData service authorization for the user. Step 2 utilizes the results of step 1.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.12 MCData resource management (on-network)
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.12.1 General
|
Procedures for resource management are defined in subclause 10.11 of 3GPP TS 23.280 [5].
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.12.2 Void
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13 Operations on MCData message store
|
The MCData message store allows an MCData user to deposit his MCData communication information (i.e. messages or files) securely and permanently for later retrieval. During an active MCData communication, a message or a file with its associated metadata is deposited as an object in the MCData message store with an object identifier; this object identifier enabling a direct access to that object. The objects in the MCData message store are managed from both the MCData server and the message store client.
Each MCData user is allocated a dedicated and secured storage area (i.e. with a user account) in the MCData message store. All MCData communications of a MCData user can be stored in his dedicated storage area. The access to this secured storage area is possible only after successful authentication and authorization procedures. A message store client can create a local copy of the stored objects into the device by synchronizing with the MCData message store for the MCData user using the device.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.1 MCData message store structure
|
MCData message store supports a tree like architecture to securely store MCData communications for the MCData users. Figure 7.13.1 below illustrates the high-level structure of a MCData message store:
Figure 7.13.1 Message store structure
As illustrated in Figure 7.13.1 all MCData user storage areas are accessed only through the common root. The authorized MCData user shall only have the access to the MCData user's storage area after the successful authentication and authorization procedures. A MCData user shall not be able to access objects stored for other MCData users.
The MCData user shall manage his stored objects using message store client through the MCData-7 reference point. The MCData server shall use the MCData-8 reference point to deposit MCData communication information, during an active MCData communication, into the designated MCData user's storage area in the MCData message store.
One way to manage user stored objects is using folder hierarchy structure like the popular email system today. Annex D provides a simple example of how it will look like in deployment. When the user account is created in the MCData message store, a default folder (such as Inbox) is also created to capture all the objects during an active communication. To group relevant stored objects together and provide easier navigation interactively, a MCData user can create folders in his user account. Each folder is identified by its unique folder identifier that is composed with the location of the folder and the name of the folder. A folder may have child folders to further group the stored objects in more meaningful ways. For example, the folder identifier of the default Inbox folder is /MCDatamessagestore /MCDatauser1/Inbox. The folder identifier /MCDatamessagestore/MCDatauser1/Squad1/20190225 points to a folder named 20190225 which is a child folder of Squad1 folder in the MCData user1 user account.
NOTE: The details of how the objects are stored in the MCData message store is out of scope of the present document.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.2 Authentication and authorization
|
The MCData message store shall authenticate the credential of MCData server or the authorized MCData user before authorizing access to the MCData user's storage area. The success of authentication and authorization shall allow access to that MCData user's storage area only.
NOTE: The authentication and authorization aspects of MCData message store access and its operational supports are the responsibility of SA3 and thus outside the scope of the present document.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3 Manage MCData message store
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1 Information flows for managing MCData message store
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.1 MCData retrieve a stored object request
|
Table 7.13.3.1.1-1 describes the information flow for the MCData retrieve a stored object request sent from the message store client to the MCData message store.
Table 7.13.3.1.1-1: MCData retrieve a stored object request
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Object identifier
M
The object identifier of the object stored in the MCData message store
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.2 MCData retrieve a stored object response
|
Table 7.13.3.1.2-1 describes the information flow for the MCData retrieve a stored object response sent from the MCData message store to the message store client.
Table 7.13.3.1.2-1: MCData retrieve a stored object response
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Stored object
M
The stored object identified by the object identifier in the request. This information element shall be returned as empty when there is no stored object can be identified by the object identifier in the request
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.3 MCData search stored objects request
|
Table 7.13.3.1.3-1 describes the information flow for the MCData search stored objects request sent from the message store client to the MCData message store.
Table 7.13.3.1.3-1: MCData search stored objects request
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Search criteria
M
Any part of the stored object can be the search criteria. Linking multiple parts of a stored object as the search criteria is possible
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.4 MCData search stored objects response
|
Table 7.13.3.1.4-1 describes the information flow for the MCData search stored objects response sent from the MCData message store to the message store client.
Table 7.13.3.1.4-1: MCData search stored objects response
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Stored object(s)
M
The stored object(s) that meets the search criteria. This information element shall be returned as empty when there is no stored object can be identified by the search criteria in the request
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.5 MCData update a stored object request
|
Table 7.13.3.1.5-1 describes the information flow for the MCData update a stored object request sent from the message store client to the MCData message store.
Table 7.13.3.1.5-1: MCData update a stored object request
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Object identifier
M
The object identifier of the object stored in the MCData message store
Metadata
M
The metadata that will be updated
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.6 MCData update a stored object response
|
Table 7.13.3.1.6-1 describes the information flow for the MCData update a stored object response sent from the MCData message store to the message store client.
Table 7.13.3.1.6-1: MCData update a stored object response
Information element
Status
Description
MCData ID
M
The identity of the MCData user storage area in the MCData message store
Result
M
The result if the update is success or failure
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.7 MCData delete a stored object request
|
Table 7.13.3.1.7-1 describes the information flow for the MCData delete a stored object request sent from the message store client to the MCData message store.
Table 7.13.3.1.7-1: MCData delete a stored object request
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Object identifier
M
The object identifier of the object stored in the MCData message store
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.8 MCData delete a stored object response
|
Table 7.13.3.1.8-1 describes the information flow for the MCData delete a stored object response sent from the MCData message store to the message store client.
Table 7.13.3.1.8-1: MCData delete a stored object response
Information element
Status
Description
MCData ID
M
The identity of the MCData user storage area in the MCData message store
Result
M
The result if the delete is success or failure
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.9 MCData synchronization request
|
Table 7.13.3.1.9-1 describes the information flow for the MCData synchronization request sent from the message store client to the MCData message store.
Table 7.13.3.1.9-1: MCData synchronization request
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Synchronization type
M
Indicates the type of synchronization is requested. It can be a full or partial synchronization
Filter criteria (see NOTE)
O
The filter criteria indicate what kind of stored objects needs to be synchronized to the device local message store
NOTE: Filter criteria information element shall be presented if the Synchronization type is partial.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.10 MCData synchronization response
|
Table 7.13.3.1.10-1 describes the information flow for the MCData synchronization response sent from the MCData message store to the message store client.
Table 7.13.3.1.10-1: MCData synchronization response
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Stored objects
M
The stored objects that need to be synchronized with the device local message store. Empty information element means no stored objects need to be synchronized
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.11 MCData create a user account request
|
Table 7.13.3.1.11-1 describes the information flow for the MCData create a user account request sent from the MCData server to the MCData message store.
Table 7.13.3.1.11-1: MCData create a user account request
Information element
Status
Description
MCData ID
M
The identity of the MCData user
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.12 MCData create a user account response
|
Table 7.13.3.1.12-1 describes the information flow for the MCData create a user account response sent from the MCData message store to the MCData server.
Table 7.13.3.1.12-1: MCData create a user account response
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Result
M
The result if the account creation is success or failure
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.13 MCData deposit an object request
|
Table 7.13.3.1.13-1 describes the information flow for the MCData deposit an object request sent from the MCData server to the MCData message store.
Table 7.13.3.1.13-1: MCData deposit an object request
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Retrieve file indication
O
Flag to instruct the MCData message store to retrieve the file to locally store in the MCData user's account
Object
M
The object needs to be stored
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.14 MCData deposit an object response
|
Table 7.13.3.1.14-1 describes the information flow for the MCData deposit an object response sent from the MCData message store to the MCData server.
Table 7.13.3.1.14-1: MCData deposit an object response
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Object Identifier
M
The object identifier that will be used to retrieve this object in the MCData message store directly. If this information element is empty it means the object is not stored
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.15 MCData copy a stored object request
|
Table 7.13.3.1.15-1 describes the information flow for the MCData copy a stored object request sent from the message store client to the MCData message store.
Table 7.13.3.1.15-1: MCData copy a stored object request
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Object identifier
M
The object identifier of the object stored in the MCData message store
Destination folder identifier
M
Indicates where the object will be copied to
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.16 MCData copy a stored object response
|
Table 7.13.3.1.16-1 describes the information flow for the MCData copy a stored object response sent from the MCData message store to the message store client.
Table 7.13.3.1.16-1: MCData copy a stored object response
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Result
M
The result if the operation is success or failure
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.17 MCData move a stored object request
|
Table 7.13.3.1.17-1 describes the information flow for the MCData move a stored object request sent from the message store client to the MCData message store.
Table 7.13.3.1.17-1: MCData move a stored object request
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Object identifier
M
The object identifier of the object stored in the MCData message store
Destination folder identifier
M
Indicates where the object will be moved to.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.18 MCData move a stored object response
|
Table 7.13.3.1.18-1 describes the information flow for the MCData move a stored object response sent from the MCData message store to the message store client.
Table 7.13.3.1.18-1: MCData move a stored object response
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Result
M
The result if the operation is success or failure
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.19 MCData create folder request
|
Table 7.13.3.1.19-1 describes the information flow for the MCData create folder request sent from the message store client to the MCData message store.
Table 7.13.3.1.19-1: MCData create folder request
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Parent folder identifier
O
The parent folder identifier of the created folder
Folder name
O
Indicates the name of the new folder
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.20 MCData create folder response
|
Table 7.13.3.1.20-1 describes the information flow for the MCData create folder response sent from the MCData message store to the message store client.
Table 7.13.3.1.20-1: MCData create folder response
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Result
M
The result if the operation is success or failure
Folder identifier
O
The identifier of the folder that is created
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.21 MCData delete folder request
|
Table 7.13.3.1.21-1 describes the information flow for the MCData delete folder request sent from the message store client to the MCData message store.
Table 7.13.3.1.21-1: MCData delete folder request
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Folder identifier
M
The identifier of the folder to be deleted
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.22 MCData delete folder response
|
Table 7.13.3.1.22-1 describes the information flow for the MCData delete folder response sent from the MCData message store to the message store client.
Table 7.13.3.1.22-1: MCData delete folder response
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Result
M
The result if the operation is success or failure
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.23 MCData copy folder request
|
Table 7.13.3.1.23-1 describes the information flow for the MCData copy folder request sent from the message store client to the MCData message store.
Table 7.13.3.1.23-1: MCData copy folder request
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Source folder identifier
M
The identifier of the folder to copy from
Destination folder identifier
M
The identifier of the folder to copy to
New folder name (see NOTE)
O
Indicates the name of the new folder
NOTE: If no new folder nameinformation element is provided, the new folder name will be the same as the source folder name.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.24 MCData copy folder response
|
Table 7.13.3.1.24-1 describes the information flow for the MCData copy folder response sent from the MCData message store to the message store client.
Table 7.13.3.1.24-1: MCData copy folder response
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Result
M
The result if the operation is success or failure
New folder identifier
M
Indicates the identifier of the new folder
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.25 MCData move folder request
|
Table 7.13.3.1.25-1 describes the information flow for the MCData move folder request sent from the message store client to the MCData message store.
Table 7.13.3.1.25-1: MCData move folder request
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Source folder identifier
M
The identifier of the folder to be moved
Destination folder identifier
M
The identifier of the folder to move to
New folder name (see NOTE)
O
Indicates the name of the new folder
NOTE: If no new folder name information element is provided, the new folder name will be the same as the source folder name.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.26 MCData move folder response
|
Table 7.13.3.1.26-1 describes the information flow for the MCData move folder response sent from the MCData message store to the message store client.
Table 7.13.3.1.26-1: MCData move folder response
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Result
M
The result if the operation is success or failure
New folder identifier
M
Indicates the identifier of the new folder
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.27 MCData list folder request
|
Table 7.13.3.1.27-1 describes the information flow for the MCData list folder request sent from the message store client to the MCData message store.
Table 7.13.3.1.27-1: MCData list folder request
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Folder identifier
O
The identifier of the folder to be listed
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.28 MCData list folder response
|
Table 7.13.3.1.28-1 describes the information flow for the MCData list folder response sent from the MCData message store to the message store client.
Table 7.13.3.1.28-1: MCData list folder response
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Result (see NOTE)
M
The result of the list operation
NOTE: If no folder identifier information element is provided in the request, the MCData message store returns folders from the root of the user account. If folder identifier information element is provided in the request, the MCData message store returns the child folders from that folder identifier provided.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.29 MCData upload objects request
|
Table 7.13.3.1.29-1 describes the information flow for the MCData upload objects request sent from the message store client to the MCData message store.
Table 7.13.3.1.29-1: MCData upload objects request
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Targeted folder identifier
M
The folder where the uploaded objects will be stored
Uploaded objects
M
The objects in the client that need to be uploaded to the MCData message store
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.30 MCData upload objects response
|
Table 7.13.3.1.30-1 describes the information flow for the MCData upload objects response sent from the MCData message store to the message store client.
Table 7.13.3.1.30-1: MCData upload objects response
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Object upload result
M
Indicates if the objects upload is successful or not
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.31 MCData synchronization notification
|
Table 7.13.3.1.31-1 describes the information flow for the MCData synchronization notification sent from the MCData message store to the message store client.
Table 7.13.3.1.31-1: MCData synchronization notification
Information element
Status
Description
MCData ID
M
The identity of the MCData user that the notification is for
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.32 Create notification channel request
|
Table 7.13.3.1.32-1 describes the information flow for the create notification channel request sent from the message notification client to the MCData notification server.
Table 7.13.3.1.32-1: Create notification channel request
Information element
Status
Description
MCData ID
M
The identity of the MCData client initiating the request
Validity duration
O
How long the notification channel is intended to be used (see NOTE)
Channel Type
M
Indicates if PULL (e.g. long-polling method) or PUSH method will be used to deliver notification messages
NOTE: If this element not present, a default validity duration shall be provided by the server in response
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.33 Create notification channel response
|
Table 7.13.3.1.33-1 describes the information flow for the create notification channel response sent from the MCData notification server to the message notification client.
Table 7.13.3.1.33-1: Create notification channel response
Information element
Status
Description
MCData ID
M
The identity of the MCData client initiating the request
Validity duration
M
How long the notification channel will last (i.e. channel lifetime) as granted by the MCData notification server
Notification URL
O
The URL to receive the notification message if a Pull method is requested . For some PUSH method implementation (such as WebSockets) this URL is used to start the PUSH notification service from the MCData notification server
Callback URL
M
The URL used by the Message notification client to subscribe to MCData message store notifications
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.34 Open notification channel
|
Table 7.13.3.1.34-1 describes the information flow for the open notification channel sent from the message notification client to the MCData notification server.
Table 7.13.3.1.34-1: Open notification channel request
Information element
Status
Description
MCData ID
M
The identity of the MCData client initiating the request
Notification URL
M
The URL to receive the notification message
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.