hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.5.3.3.2 Procedure
| Figure 7.5.3.3.2-1 describes procedures for an off-network MCData client 1 initiating one-to-one MCData data communication for sending standalone FD data to other MCData client, with or without download completed report request.
Pre-conditions:
1. MCData user 1 has initiated communication for sending standalone FD data to other MCData user 2.
2. MCData client 1 and MCData client 2 are members of the same ProSe Discovery group and are ProSe 1:1 direct communication capable.
3. MCData client 1 has discovered MCData client 2 in proximity, associated with MCData user 2, using ProSe Discovery procedures.
Figure 7.5.3.3.2-1: One-to-one standalone file distribution using media plane
1. MCData client 1 sends a MCData FD request towards the MCData client 2. File metadata information is included in the SDP. The MCData FD request contains one MCData user for one-to-one data communication as selected by the user at MCData client 1. The MCData FD request contains conversation identifier for message thread indication. The MCData FD request may include additional implementation specific information in the application metadata container. MCData FD request may contain mandatory download indication. The MCData FD request may contain download completed report indication if selected by the user at MCData client 1.
2. On receiving a MCData FD request, the MCData client 2 checks whether any policy is to be asserted to limit certain types of message or content to certain members, for example, due to location or user privilege.
3. The receiving MCData client 2 notifies the user about the incoming MCData FD request which may be either accepted or rejected or ignored. MCData user may not be sought consent if the request includes mandatory download indication in the MCData FD request and instead only notify the MCData user about file downloading.
4. If the target MCData user 2 provides a response (accept or reject) to the notification, then the MCData client 2 sends the MCData FD response to the MCData client 1. MCData client 2 automatically sends accepted MCData FD response when the incoming request included mandatory download indication.
5. MCData client 1 distributes the file over the established media plane to MCData client 2.
6. The MCData client 2 records file download completed and notifies MCData user 2. MCData client 2 initiates a MCData download completed report for reporting file download completed, if requested by the user at MCData client 1.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.5.3.4 Group standalone file distribution using media plane
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.5.3.4.1 General
| The initiation of a group standalone FD to a selected group results in off-network MCData group members receiving the file data.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.5.3.4.2 Procedure
| Figure 7.5.3.4.2-1 describes procedures for an off-network MCData client 1 initiating group MCData data communication for sending FD data to a MCData group, with or without download completed report request.
Pre-conditions:
1. MCData user 1 has initiated group communication for sending FD data to the MCData group.
2. 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.
3. MCData client 1 to MCData client N are members of the same MCData group.
Figure 7.5.3.4.2-1: Group standalone file distribution using media plane
1. MCData client 1 sends a MCData group standalone FD request towards the MCData group. File metadata information is included in the SDP. The MCData group standalone FD request contains MCData group ID as selected by the user at MCData client 1. The MCData group standalone FD request contains conversation identifier for message thread indication. The MCData group standalone FD request may include additional implementation specific information in the application metadata container. MCData group standalone FD request may contain mandatory download indication. The MCData group standalone FD request may contain download completed report indication if selected by the user at MCData client 1.
2. On receiving a MCData group standalone FD request, the MCData clients check whether any policy is to be asserted to limit certain types of message or content to certain members, for example, due to location or user privilege.
3. If the policy assertion is positive, the receiving MCData clients 2 to n notifies the user about the incoming MCData group standalone FD request which may be either accepted or rejected or ignored. MCData user may not be sought consent if the request includes mandatory download indication in the MCData group standalone FD request and instead only notify the MCData user about file downloading.
4. If the target MCData user on MCData clients 2 to n provides a response (accept or reject) to the notification, then the respective MCData client sends the MCData group standalone FD response to the MCData client 1. MCData client 2 to n automatically sends accepted MCData group standalone FD response when the incoming request included mandatory download indication.
5. MCData client 1 and MCData client 2 to n have successfully established media plane for file transmission and the MCData client 1 transmits the file data.
6. The MCData client 2 to n successfully receiving the file, records file download completed and notifies MCData users.
7. MCData client 2 to n initiate a MCData download completed report for reporting file download completed, if requested by the user at MCData client 1.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.6 Transmission and reception control
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.6.1 General
| Based on the configurations (available in MCData user profile, group configuration and service configuration), the MCData transmission and reception control provides a necessary capability for an authorized user of the MCData service to transmit, receive notification messages due to various trigger conditions, advocates reception mode and terminate transmission when there is no longer a need to transmit. The subclauses below describe the transmission and reception control procedures using signalling control plane.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.6.2 Transmission and reception control for on-network
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.6.2.1 Information flows for transmission and reception control
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.6.2.1.1 MCData control indication
| Table 7.6.2.1.1-1 describes the information flow for the MCData control indication sent from the MCData server to the MCData client.
Table 7.6.2.1.1-1: MCData control indication
Information element
Status
Description
MCData ID
M
The identity of the MCData user towards which the control indication is sent
Conversation Identifier
M
Identifies the conversation
Transaction Identifier
M
Identifies the MCData transaction
Control indication type
M
One of the following:
- No permission to transmit data
- No affiliated members found to the selected MCData group
- Rejected due to exceeding data transmit size
- Rejected due to exceeding data transmit time
- Request to transmit is queued
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.6.2.1.2 MCData indication
| Table 7.6.2.1.2-1 describes the information flow for the MCData indication sent from the MCData server to the MCData client.
Table 7.6.2.1.2-1: MCData indication
Information element
Status
Description
MCData ID
M
The identity of the MCData user towards which the MCData indication is sent
Conversation Identifier
M
Identifies the conversation
Transaction Identifier
M
Identifies the MCData transaction
Deferred data list
M
List of references to deferred data awaiting download
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.6.2.1.3 MCData get deferred list request
| Table 7.6.2.1.3-1 describes the information flow for the MCData get deferred list request sent from the MCData client to the MCData server.
Table 7.6.2.1.3-1: MCData get deferred list request
Information element
Status
Description
MCData ID
M
The identity of the MCData user requesting deferred list
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.6.2.1.4 MCData get deferred list response
| Table 7.6.2.1.4-1 describes the information flow for the MCData get deferred list response sent from the MCData server to the MCData client.
Table 7.6.2.1.4-1: MCData get deferred list response
Information element
Status
Description
MCData ID
M
The identity of the MCData user requesting deferred list
Deferred data list
M
List of references to deferred data awaiting download
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.6.2.2 Automatic transmission for SDS
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.6.2.2.1 General
| When SDS message is sent, the data is transferred from the sending MCData client to the receiving MCData client without any request/grant procedure or any explicit actions on the part of the receiving MCData client.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.6.2.2.2 Procedure
| The procedure in figure 7.6.2.2.2-1 describes the case where MCData SDS is automatically transmitted to the selected recipient user or affiliated members of the selected MCData group.
Pre-conditions:
1. MCData user is configured with permission to transmit data.
2. Optionally, MCData client may have an activated functional alias to be used.
3. The MCData server may have subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates.
Figure 7.6.2.2.2-1: Automatic transmission for SDS
1. MCData user selects the data to transmit and the recipient MCData user or MCData group. The MCData user at MCData client 1 may include a functional alias used within the SDS data transmission.
2. MCData client checks for MCData user's permission to transmit data and checks if the data size is less than the maximum data size for SDS. MCData client calculates the total transmission request size and determines to select one of the appropriate procedures described in subclause 7.4.2.2, 7.4.2.3, 7.4.2.5 or 7.4.2.6.
3. Transmission control on the MCData server verifies if the MCData user is authorized to transmit and the data size in the received transmission request does not exceed the maximum data size for SDS. MCData server verifies whether the provided functional alias, if present, can be used and has been activated for the MCData user.
4. MCData server may send one of the following MCData control indications:
a) If the MCData user does not have permission to transmit data to another MCData user or MCData group then the "No permission to transmit data" control indication is sent.
b) If the selected transmission is for a MCData group and there are no affiliated group members, then the transmission control on MCData server sends the "No affiliated members found to the selected MCData group" control indication.
c) MCData server may queue the data transmit request for later transmission with control indication "Request to transmit is queued".
Otherwise continue with step 5.
5. MCData server automatically transmits the data and, if available, the functional alias of the originating MCData client 1 to the selected MCData user or the affiliated members or all group members (in the case of lossless communication) of the selected MCData group according to the procedures selected in step 2.
6. The MCData server may store the data in temporary storage (e.g. if the recipient is not available at the time of data delivery or network congestion or data deferred by the user) and may send MCData indication to notify the recipient of available data for retrieval:
a) If the timer expired for periodic announcement with the list of available recently invited data communications, the recipient MCData client waiting to receive the temporarily stored data receives MCData indication with the list of available temporarily stored data waiting to download in the Deferred data list .
b) If the temporarily stored data is expired, the data may be purged from the temporary store and the recipient MCData user may be informed in MCData indication with "Data expired and not available to download anymore" in the Deferred data list.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.6.2.3 Send data with mandatory download
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.6.2.3.1 General
| The mandatory download procedure allows a sending MCData client to send data to a receiving MCData client, where the receiving MCData client is compelled to download the data.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.6.2.3.2 Procedure
| The procedure in figure 7.6.2.3.2-1 describes the case where MCData user is using FD. The FD is subjected to transmission control prior to transmitting data to the selected recipient user or affiliated members of the selected MCData group for mandatory download.
Pre-conditions:
1. MCData user is configured with permission to transmit data.
2. MCData administrator has configured maximum data size for FD.
3. Maximum amount of data that a MCData user can transmit in a single request is configured.
4. Maximum amount of time that a MCData user can transmit in a single request is configured.
5. Optionally, MCData client may have an activated functional alias to be used.
6. The MCData server may have subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates.
Figure 7.6.2.3.2-1: Send data with mandatory download
1. MCData user selects the data to transmit, the recipient MCData user or MCData group and the indication for mandatory download. The MCData user at MCData client 1 may include a functional alias used within the FD data transfer.
2. MCData client has checked for MCData user's permission to transmit data. MCData client calculates the total transmission request size and determines to select one of the appropriate procedures described in subclause 7.5.2.4, 7.5.2.5, 7.5.2.6 or 7.5.2.7 and including the mandatory download indication.
3. Transmission control on the MCData server verifies if the MCData user is authorized to transmit, the data size in the received transmission request is within the maximum size allowed for FD transmission and is within the maximum amount of time that a MCData user can transmit in a single request. MCData server verifies whether the provided functional alias, if present, can be used and has been activated for the MCData user.
4. MCData server may send one of the following MCData control indications:
a) If the MCData user does not have permission to transmit data to another MCData user or MCData group then the "No permission to transmit data" control indication is sent.
b) If the data size requested to be transmitted is more than the maximum amount of data that an MCData user can transmit in a single request, the transmission control on MCData server rejects the data transmission request and sends the rejection control indication "Rejected due to exceeding data transmit size".
c) If the data transmission time exceeds the maximum amount of time that an MCData user can transmit in a single request, the transmission control on MCData server rejects the data transmission request and sends the rejection control indication "Rejected due to exceeding data transmit time".
d) If the selected transmission is for a MCData group and there are no affiliated group members, then the transmission control on MCData server sends the "No affiliated members found to the selected MCData group" control indication.
e) MCData server may queue the data transmit request for later transmission with control indication "Request to transmit is queued".
Otherwise continue with step 5.
5. MCData server transmits the data and, if available, the functional alias of the originating MCData client 1 to the selected MCData user or the affiliated members or all group members (in the case of lossless communication) of the selected MCData group according to the procedures selected in step 2 (where the recipient MCData client receives the data automatically).
6. The MCData server may store the data in temporary storage (e.g. if the recipient is not available at the time of data delivery or network congestion or data deferred by the user) and may send MCData indication to notify the recipient of available data for retrieval:
a) If the timer expired for periodic announcement with the list of available recently invited data communications, the recipient MCData client waiting to receive the temporarily stored data receives MCData indication with the list of available temporarily stored data waiting to download in the Deferred data list .
b) If the temporarily stored data is expired, the data may be purged from the temporary store and the recipient MCData user may be informed in MCData indication with "Data expired and not available to download anymore" in the Deferred data list.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.6.2.4 Send data without mandatory download
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.6.2.4.1 General
| The send data without mandatory download procedure allows the receiving MCData client to accept download, defer download (i.e. no response) or refuse (e.g. by the user deleting the notification item) the data sent from the sending MCData client.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.6.2.4.2 Procedure
| The procedure in figure 7.6.2.4.2-1 describes the case where MCData user selected data is subjected to transmission control prior to transmitting data to the selected recipient user or affiliated members of the selected MCData group for downloading with recipient MCData user consent.
Pre-conditions:
1. MCData user is configured with permission to transmit data.
2. Maximum amount of data or time that an MCData user can transmit in a single request is configured.
3. Time limit for the temporarily stored data waiting to be delivered to a receiving user is configured.
4. Optionally, MCData client may have an activated functional alias to be used.
5. The MCData server may have subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates.
Figure 7.6.2.4.2-1: Send data without mandatory download
1. MCData user selects the data to transmit and the recipient MCData user or MCData group and does not select the mandatory download indication. The MCData user at MCData client 1 may include a functional alias used within the data transmission.
2. MCData client has checked for MCData user's permission to transmit data and the data size is within the maximum data size allowed. The MCData client calculates the total transmission request size and determines to select procedure described in subclause 7.5.2.4, 7.5.2.5, 7.5.2.6 or 7.5.2.7 and without including the mandatory download indication.
3. Transmission control on the MCData server verifies if the MCData user is authorized to transmit, the data size in the received transmission request is within the maximum data size allowed and is within the maximum amount of time that a MCData user can transmit in a single request. MCData server verifies whether the provided functional alias, if present, can be used and has been activated for the MCData user.
4. MCData server may send one of the following control indications:
a) If the MCData user does not have permission to transmit data to another MCData user or MCData group then the "No permission to transmit data" control indication is sent.
b) If the selected transmission is for a MCData group and there are no affiliated group members, then the transmission control on MCData server sends the "No affiliated members found to the selected MCData group" control indication.
c) If the data size requested to be transmitted is more than the maximum amount of data that an MCData user can transmit in a single request, the transmission control on MCData server rejects the data transmission requests and sends the rejection control indication "Rejected due to exceeding data transmit size".
d) If the data transmission time exceeds the maximum amount of time that an MCData user can transmit in a single request (applies to DS only), the transmission control on MCData server rejects the data transmission request and sends the rejection control indication "Rejected due to exceeding data transmit time".
e) MCData server may queue the data transmit request for later transmission with a control indication "Request to transmit is queued".
Otherwise, continue with step 5.
5. MCData server transmits the data and, if available, the functional alias of the originating MCData client 1 to the selected MCData user or the affiliated members or all group members (in the case of lossless communication) of the selected MCData group according to the procedures selected in step 2 (where the recipient MCData client may receive the data automatically).
6. The MCData server may store the data in temporary storage (e.g. if the recipient is not available at the time of data delivery or network congestion or data deferred by the user) and may send MCData indication to notify the recipient of available data for retrieval:
a) If the timer expired for periodic announcement with the list of available recently invited data communications, the recipient MCData client waiting to receive the temporarily stored data receives MCData indication with the list of available temporarily stored data waiting to download in the Deferred data list .
b) If the temporarily stored data is expired, the data may be purged from the temporary store and the recipient MCData user may be informed in MCData indication with "Data expired and not available to download anymore" in the Deferred data list.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.6.2.5 Accessing list of deferred data group communications
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.6.2.5.1 General
| This procedure allows an MCData client to obtain a list of deferred data communications.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.6.2.5.2 Procedure
| The procedure in figure 7.6.2.5.2-1 describes the case where the recipient MCData client receives the list of available temporarily stored data waiting to download for the deferred data group communications.
Pre-conditions:
1. MCData server has temporarily stored data for the deferred data group communications e.g. due to recipient MCData client deferred to download.
Figure 7.6.2.5.2-1: Accessing list of deferred data group communications
1. MCData user initiates the request to get the list of temporarily stored data for the deferred data group communications on the MCData server e.g. due to recipient MCData client deferred to download.
2. MCData client sends a MCData get deferred list request to the MCData server.
3. MCData server generates the list of temporarily stored data for the affiliated group(s), available to download for the requesting MCData client and sends the list in the MCData get deferred list response.
4. MCData client notifies the list of temporarily stored data for the deferred data group communications, upon which the MCData user may decide to retrieve the corresponding data.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.7 Communication release
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.7.1 General
| The subclauses below describe the MCData communication release procedures, which may be initiated either by the sender or the MCData server or the authorized MCData user. The one-to-one communication in this clause refers to the SDS one-to-one communication established in clause 7.4 or the FD one-to-one communication established in clause 7.5. The group communication in this clause refers to the SDS group communication established in clause 7.4 or the FD group communication established in clause 7.5.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.7.2 Communication release for on-network
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.7.2.1 Information flows for communication release
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.7.2.1.1 MCData communication release request (one-to-one communication using media plane)
| Table 7.7.2.1.1-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.1-1: MCData communication release request (one-to-one communication using media plane)
Information element
Status
Description
MCData ID
M
The identity of the MCData user uploading data
MCData ID
M
MCData ID on which the communication is to be released
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.7.2.1.2 MCData communication release response (one-to-one communication using media plane)
| Table 7.7.2.1.2-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.2-1: MCData communication release response (one-to-one communication using media plane)
Information element
Status
Description
MCData ID
M
The identity of the MCData user requesting to upload data
MCData ID
M
MCData ID on which the communication is released
Release confirmation
M
Communication released or not indication
|
30497b4d3b4268dfe046b8ed41cd63fb | 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
|
30497b4d3b4268dfe046b8ed41cd63fb | 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
|
30497b4d3b4268dfe046b8ed41cd63fb | 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
|
30497b4d3b4268dfe046b8ed41cd63fb | 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
|
30497b4d3b4268dfe046b8ed41cd63fb | 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
|
30497b4d3b4268dfe046b8ed41cd63fb | 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
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.7.2.1.12 Void
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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
|
30497b4d3b4268dfe046b8ed41cd63fb | 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
|
30497b4d3b4268dfe046b8ed41cd63fb | 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
|
30497b4d3b4268dfe046b8ed41cd63fb | 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
|
30497b4d3b4268dfe046b8ed41cd63fb | 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
|
30497b4d3b4268dfe046b8ed41cd63fb | 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
|
30497b4d3b4268dfe046b8ed41cd63fb | 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
|
30497b4d3b4268dfe046b8ed41cd63fb | 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
|
30497b4d3b4268dfe046b8ed41cd63fb | 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
|
30497b4d3b4268dfe046b8ed41cd63fb | 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
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.7.2.2 MCData user initiated communication release
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.7.2.2.2 Release of MCData communication using media plane
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.7.2.3 MCData server initiated communication release without prior indication
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.7.2.3.2 Release of MCData communication using media plane
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 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 MCData server 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 MCData server 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.7.2.3.3 Void
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.7.2.4 MCData server initiated communication release with prior indication
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.7.2.5 Authorized MCData user initiated communication release without prior indication
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.7.2.6 Authorized MCData user initiated communication release with prior indication
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.8 Conversation management
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.8.2 Conversation management for on-network
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.8.2.2 One-to-one conversation management
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.8.2.3 Group conversation management
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.8.3 Conversation management for off-network
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.8.3.1 One-to-one conversation management
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.8.3.2 Group conversation management
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.9 Enhanced status
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.9.3 Enhanced status for on-network
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.9.3.1 Sharing enhanced status information
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.9.4 Enhanced status for off-network
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.9.4.1 Sharing enhanced status information
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.12 MCData resource management (on-network)
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.12.1 General
| Procedures for resource management are defined in subclause 10.11 of 3GPP TS 23.280 [5].
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.12.2 Void
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.13.3 Manage MCData message store
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.13.3.1 Information flows for managing MCData message store
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.