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 d... |
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... |
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, advocate... |
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
Conver... |
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... |
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 d... |
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 fun... |
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 perm... |
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... |
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. ... |
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 e... |
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 pl... |
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 ... |
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)
... |
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... |
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)... |
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
D... |
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)
Inform... |
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
Desc... |
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
... |
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)... |
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
T... |
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)
Inf... |
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)
Informati... |
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)
Informa... |
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 el... |
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 ... |
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
Conve... |
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
Inform... |
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 MCDa... |
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, MCDat... |
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 specific... |
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:... |
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 co... |
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 commu... |
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 co... |
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 communic... |
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.... |
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 managem... |
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 th... |
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 ... |
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 MCDat... |
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 ... |
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 A... |
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 MCDa... |
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 ... |
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
- T... |
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 ... |
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 obje... |
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 ... |
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 a... |
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.