hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.4.3.3.2 Procedure
| Figure 7.4.3.3.2-1 describes procedures for an off-network MCData client 1 initiating one-to-one MCData data communication for sending standalone SDS data to other MCData client, with or without disposition request. Standalone refers to sending unidirectional data in one transaction. The SDS data size is assumed to be ... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.4.3.4 Group standalone short data service using signalling control plane
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.4.3.4.1 General
| The initiation of a group standalone SDS to a selected group results in off-network MCData group members receiving the SDS data.
|
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.4.3.4.2 Procedure
| Figure 7.4.3.4.2-1 describes procedures for an off-network MCData client 1 initiating group MCData data communication for sending SDS data to a MCData group, with or without disposition request. The SDS data size limit is pre-configured.
Pre-conditions:
1. MCData user 1 has initiated group communication for sending ... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.4.3.5 Void
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.4.3.6 Group standalone short data service with MCData message store
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.4.3.6.1 General
| A MCData user's off-network communication needs to be part of his communication history when the MCData user has an account in the MCData message store.
|
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.4.3.6.2 Procedure
| Figure 7.4.3.6.2-1 describes procedures of a MCData user, MCData user 2, that has an account in MCData message store and how his off-network SDS group communication is stored in his account in the MCData message store. All other MCData clients in the figure follow the procedures described in subclause 7.4.3.4.
Pre-con... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5 File distribution
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.1 General
| File distribution (mandatory and non-mandatory download) is enabled for both one-to-one and group.
|
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2 File distribution for on-network
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1 Information flows for file distribution
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.1 MCData upload data request
| Table 7.5.2.1.1-1 describes the information flow for the MCData upload data request sent from the media storage client to the MCData content server.
Table 7.5.2.1.1-1: MCData upload data request
Information element
Status
Description
MCData ID
M
The identity of the MCData user uploading data
Content (see NOTE)
... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.2 MCData upload data response
| Table 7.5.2.1.2-1 describes the information flow for the MCData upload data response sent from the MCData content server to the media storage client.
Table 7.5.2.1.2-1: MCData upload data response
Information element
Status
Description
MCData ID
M
The identity of the MCData user requesting to upload data
Upload... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.3 MCData download data request
| Table 7.5.2.1.3-1 describes the information flow for the MCData download data request sent from the MCData media storage client to the MCData content server.
Table 7.5.2.1.3-1: MCData download data request
Information element
Status
Description
MCData ID
M
The identity of the MCData user downloading data
Conten... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.4 MCData download data response
| Table 7.5.2.1.4-1 describes the information flow for the MCData download data response sent from the MCData content server to the media storage client.
Table 7.5.2.1.4-1: MCData download data response
Information element
Status
Description
MCData ID
M
The identity of the MCData user requesting to download data
... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.5 MCData FD request (using HTTP)
| Table 7.5.2.1.5-1 describes the information flow for the MCData FD request (in subclause 7.5.2.4.2) sent from the MCData client to the MCData server.
Table 7.5.2.1.5-1: MCData FD request (using HTTP) from MCData client to MCData server
Information element
Status
Description
MCData ID
M
The identity of the MCData... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.6 MCData FD response (using HTTP)
| Table 7.5.2.1.6-1 describes the information flow for the MCData FD response (in subclause 7.5.2.4.2) sent from the MCData client to the MCData server, from the MCData server to another MCData client and from an MCData server to a partner MCData server.
Table 7.5.2.1.6-1: MCData FD response (using HTTP)
Information el... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.7 MCData download completed report
| Table 7.5.2.1.7-1 describes the information flow for the MCData download completed report sent from the MCData client to the MCData server, from the MCData server to another MCData client and from an MCData server to a partner MCData server.
Table 7.5.2.1.7-1: MCData download completed report
Information element
Sta... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.8 MCData FD request (using media plane)
| Table 7.5.2.1.8-1 describes the information flow for the MCData FD request (in subclause 7.5.2.5.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client.
Table 7.5.2.1.8-1: MCData FD request (using media plane/MCData client to MCData server)
Information element
Status
... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.9 MCData FD response (using media plane)
| Table 7.5.2.1.9-1 describes the information flow for the MCData FD response (in subclause 7.5.2.5.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client.
Table 7.5.2.1.9-1: MCData FD response (using media plane)
Information element
Status
Description
MCData ID
M
T... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.10 MCData group standalone FD request (using HTTP)
| Table 7.5.2.1.10-1 describes the information flow for the MCData group standalone FD request (in subclause 7.5.2.6.2) sent from the MCData client to the MCData server.
Table 7.5.2.1.10-1: MCData group standalone FD request (using HTTP) from MCData client to MCData server
Information element
Status
Description
MCDa... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.11 MCData group standalone FD response (using HTTP or MBMS download delivery method)
| Table 7.5.2.1.11-1 describes the information flow for the MCData group standalone FD response (in subclause 7.5.2.6.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client.
Table 7.5.2.1.11-1: MCData group standalone FD response (using HTTP)
Information element
Status
... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.12 MCData group standalone FD request (using media plane)
| Table 7.5.2.1.12-1 describes the information flow for the MCData group standalone FD request (in subclause 7.5.2.7.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client.
Table 7.5.2.1.12-1: MCData group standalone FD request (using media plane/MCData client to MCData s... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.13 MCData group standalone FD response (using media plane)
| Table 7.5.2.1.13-1 describes the information flow for the MCData group standalone FD response (in subclause 7.5.2.7.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client.
Table 7.5.2.1.13-1: MCData group standalone FD response (using media plane)
Information element
... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.14 MCData remove file request
| Table 7.5.2.1.14-1 describes the information flow for the MCData remove file request sent from the media storage client to the media storage function of the MCData content server, and from the MCData content server to another MCData content server in a partner MCData system.
Table 7.5.2.1.14-1: MCData remove file requ... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.15 MCData remove file response
| Table 7.5.2.1.15-1 describes the information flow for the MCData remove file response sent from the media storage function of the MCData content server to the media storage client, and from the MCData content server to another MCData content server in a partner MCData system.
Table 7.5.2.1.15-1: MCData remove file res... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.16 Void
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.17 Void
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.18 Void
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.19 MCData file retrieve request
| Table 7.5.2.1.19-1 describes the information flow for the MCData file retrieve request sent from an MCData content server in a partner MCData system to an MCData content server in the primary MCData system of the source of the content.
Table 7.5.2.1.19-1: MCData file retrieve request
Information element
Status
Desc... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.20 MCData file retrieve response
| Table 7.5.2.1.20-1 describes the information flow for the MCData file retrieve response sent from the MCData content server in the primary MCData system of the source of the content to an MCData content server in a partner MCData system.
Table 7.5.2.1.20-1: MCData file retrieve response
Information element
Status
D... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.21 MCData group standalone FD over MBMS request
| Table 7.5.2.1.21-1 describes the information flow for the MCData group standalone FD over MBMS request (in subclause 7.5.2.10.2) sent from the MCData server to another MCData client.
Table 7.5.2.1.21-1: MCData group standalone FD over MBMS request
Information element
Status
Description
MCData ID
M
The identity o... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.22 MCData one-to-one FD upgrade request
| Table 7.5.2.1.22-1 describes the information flow for the MCData one-to-one FD upgrade request sent from the MCData client to the MCData server and from the MCData server to another MCData client.
Table 7.5.2.1.22-1: MCData one-to-one FD upgrade request
Information element
Status
Description
MCData ID
M
The iden... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.23 MCData one-to-one FD upgrade response
| Table 7.5.2.1.23-1 describes the information flow for the MCData one-to-one FD upgrade response sent from the MCData client to the MCData server and from the MCData server to another MCData client.
Table 7.5.2.1.23-1: MCData one-to-one FD upgrade response
Information element
Status
Description
MCData ID
M
The id... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.24 MCData group FD upgrade request
| Table 7.5.2.1.24-1 describes the information flow for the MCData group FD upgrade request sent from the MCData client to the MCData server and from the MCData server to another MCData client.
Table 7.5.2.1.24-1: MCData group FD upgrade request (MCData client to MCData server)
Information element
Status
Description
... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.25 MCData group FD upgrade response
| Table 7.5.2.1.25-1 describes the information flow for the MCData group FD upgrade response sent from the MCData client to the MCData server and from the MCData server to another MCData client.
Table 7.5.2.1.25-1: MCData group FD upgrade response
Information element
Status
Description
MCData ID
M
The identity of ... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.26 MCData group FD in-progress priority state cancel request
| Table 7.5.2.1.26-1 describes the information for the MCData group FD in-progress priority state cancel request sent from the MCData client to the MCData server and from the MCData server to another MCData client.
Table 7.5.2.1.26-1: MCData group FD in-progress priority state cancel request (MCData client to MCData ser... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.27 MCData group FD in-progress priority state cancel response
| Table 7.5.2.1.27-1 describes the information flow for the MCData group FD in-progress priority state cancel response sent from the MCData server to the MCData client.
Table 7.5.2.1.27-1: MCData group FD in-progress priority state cancel response information elements
Information Element
Status
Description
MCData I... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.28 MCData file upload request
| Table 7.5.2.1.28-1 describes the information flow for the MCData file upload request sent from the MCData client to the MCData server.
Table 7.5.2.1.28-1: MCData file upload request
Information element
Status
Description
MCData ID
M
The identity of the MCData user uploading the file
Transaction Identifier
M
I... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.29 MCData file upload response
| Table 7.5.2.1.29-1 describes the information flow for the MCData file upload response sent from the MCData server to the MCData client.
Table 7.5.2.1.29-1: MCData file upload response
Information element
Status
Description
MCData ID
M
The identity of the MCData user requesting to upload the file
Transaction Ide... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.30 MCData file upload completion status
| Table 7.5.2.1.30-1 describes the information flow for the MCData file upload completion status sent from the MCData client to the MCData server.
Table 7.5.2.1.30-1: MCData file upload completion status
Information element
Status
Description
MCData ID
M
The identity of the MCData user uploading the file
Transact... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.31 MCData file download request
| Table 7.5.2.1.31-1 describes the information flow for the MCData file download request sent from the MCData client to the MCData server.
Table 7.5.2.1.31-1: MCData file download request
Information element
Status
Description
MCData ID
M
The identity of the MCData user downloading the file
Transaction Identifier... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.32 MCData file download response
| Table 7.5.2.1.32-1 describes the information flow for the MCData file download response sent from the MCData server to the MCData client.
Table 7.5.2.1.32-1: MCData file download response
Information element
Status
Description
MCData ID
M
The identity of the MCData user requesting to dowload the file
Transactio... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.33 MCData file availability request
| Table 7.5.2.1.33-1 describes the information flow for the MCData file availability request sent from the MCData server to the MCData content server.
Table 7.5.2.1.33-1: MCData file availability request
Information element
Status
Description
Content reference
M
URL reference of the file required to check its avai... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.1.34 MCData file availability response
| Table 7.5.2.1.34-1 describes the information flow for the MCData file availability response sent from the MCData content server to the MCData server.
Table 7.5.2.1.34-1: MCData file availability response
Information element
Status
Description
Content reference
M
URL reference of the file required to check its av... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.2 File upload using HTTP
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.2.1 General
| The media storage client uses HTTP for a standalone data file upload towards the MCData content server.
|
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.2.2 Procedure for uploading the file residing in the local storage of the MCData UE without QoS
| The procedure in figure 7.5.2.2.2-1 describes the case where an MCData user is uploading a file to media storage function on the MCData content server.
Pre-conditions:
1. The MCData user on the media storage client is registered for receiving MCData service.
2. The MCData content server has the ability to verify if ... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.2.3 Procedure for uploading the file residing in the MCData message store
| The procedure in figure 7.5.2.2.3-1 describes the case where an MCData user is uploading a file to media storage function on the MCData content server from his or her MCData message store account.
Pre-conditions:
1. The Media storage client knows the URL of the file residing in the MCData message store account of the... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.2.4 Procedure for file upload including request of network resources with required QoS
| The procedure in figure 7.5.2.2.4-1 describes the case where an MCData client sends a request to the MCData server for the upload of a file from the media storage client on the MCData client to the media storage function on the MCData content server. The MCData server can, therefore, request network resources with the ... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.3 File download using HTTP
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.3.1 General
| The media storage client uses HTTP for a standalone data file download from the MCData content server.
|
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.3.2 Procedure for file download from the MCData content server without QoS
| The procedure in figure 7.5.2.3.2-1 describes the case where an MCData user is downloading a file from the media storage function of the MCData content server.
Pre-conditions:
1. The MCData user on the media storage client is registered for receiving MCData service.
Figure 7.5.2.3.2-1: File download using HTTP
1.... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.3.3 Procedure for file download including request of network resources with required QoS
| The procedure in figure 7.5.2.3.3-1 describes the case where an MCData client sends a request to the MCData server for the download of a file from the media storage client on the MCData client to the media storage function on the MCData content server. The MCData server can, therefore, request network resources with th... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.4 One-to-one file distribution using HTTP
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.4.1 General
| The MCData client uses HTTP file distribution to download a file that is uploaded by another MCData client. The procedure is appropriate for both mandatory and non-mandatory download cases. The target MCData user may be addressed using the functional alias that can be shared with other MCData users.
|
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.4.2 Procedure for single MCData system
| The procedure in figure 7.5.2.4.2-1 describes the case where a MCData user is initiating one-to-one data communication for sending file to the other MCData user, with or without download completed report request.
Pre-conditions:
1. The MCData users on the MCData client 1 and the MCData client 2 are already registered... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.4.3 Procedure with interconnection between MCData systems
| The procedure in figure 7.5.2.4.3-1 describes the case where a MCData user initiates a one-to-one data communication for sending a file to another MCData user where that other MCData user is receiving MCData service on a partner MCData system, and where interconnection is in use between the two MCData systems. In this ... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.5 One-to-one file distribution using media plane
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.5.1 General
| The MCData client uses the media plane for a standalone data file download from another MCData client. The procedure is appropriate for both mandatory and non-mandatory download cases. The target MCData user may be addressed using the functional alias that can be shared with other MCData users.
|
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.5.2 Procedure
| The procedure in figure 7.5.2.5.2-1 describes the case where an MCData user is initiating one-to-one data communication for sending file to the other MCData user, with or without download completed report request.
Pre-conditions:
1. The MCData users on the MCData client 1 and the MCData client 2 are already registere... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.6 Group standalone file distribution using HTTP
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.6.1 General
| The initiation of a group standalone FD using HTTP to a selected group, results in affiliated group members receiving the file data.
|
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.6.2 Procedure
| The procedure in figure 7.5.2.6.2-1 describes the case where a MCData user is initiating group standalone data communication for sending a file to multiple MCData users, with or without download completed report request from the MCData user.
Pre-conditions:
1. The MCData users on the MCData clients 1 to n belong to t... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.7 Group standalone file distribution using media plane
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.7.1 General
| The initiation of a group standalone FD using media plane to a selected group, results in affiliated group members receiving the file data.
|
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.7.2 Procedure
| The procedure in figure 7.5.2.7.2-1 describes the case where an MCData user is initiating group standalone data communication for sending file to multiple MCData users, with or without download completed report request.
Pre-conditions:
1. The MCData users on the MCData client 1 to n belong to the same group and are a... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.8 File removal using HTTP by authorized user
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.8.1 General
| The media storage client uses HTTP to remove a file that was previously uploaded to the MCData content server.
|
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.8.2 Procedure for single MCData system
| The procedure in figure 7.5.2.8.2-1 describes the case where a MCData user is removing the file that was previously uploaded to the MCData content server.
Pre-conditions:
1. The MCData user on the media storage client is registered for receiving MCData service.
2. The file has been successfully uploaded by the MCDat... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.8.3 Procedure for interconnection between MCData systems
| The procedure in figure 7.5.2.8.3-1 describes the case where an MCData user removes the file that was previously uploaded to the primary MCData system MCData content server, and where the file has been made available in the partner MCData system MCData content server.
Pre-conditions:
1. The MCData user on the media s... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.9 Void
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.10 Group standalone file distribution using the MBMS download delivery method
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.10.1 General
| The initiation of a group standalone FD to a selected group results in affiliated group members receiving the file data over MBMS.
The first steps of the procedure are identical to the procedure Group standalone file distribution using HTTP (7.5.2.6). Based on the density and distribution of target group members, the... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.10.2 Procedure
| The procedure in figure 7.5.2.10.2-1 describes the case where a MCData user is initiating group standalone data communication for sending a file to multiple MCData users, with or without download completed report request.
Pre-conditions:
1. The MCData users on the MCData client 1 to n belong to the same group and are... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.11 One-to-one FD communication upgrade to an emergency FD communication
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.11.1 General
| This clause is for adding procedures related to upgrading an existing one-to-one FD communication to an emergency one-to-one FD communication.
|
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.11.2 Procedure
| The procedure in figure 7.5.2.11.2-1 describes the case where an authorized MCData user is upgrading a MCData one-to-one FD communication to a MCData emergency one-to-one FD communication. This procedure is applicable only when MCData one-to-one file distribution communication is established as described in subclause 7... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.12 Group FD communication upgrade to an emergency group FD communication
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.12.1 General
| This clause is for adding procedures related to upgrading an existing MCData group FD communication to an MCData emergency group FD communication.
|
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.12.2 Procedure
| The procedure in figure 7.5.2.12.2-1 describes the case where an authorized MCData user is upgrading an onging MCData group FD communication to an MCData emergency group FD communication. This procedure is applicable only when group MCData FD communication is established as described in subclause 7.5.2.7 "Group standal... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.13 Group FD communication in-progress emergency group state cancel
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.13.1 General
| This clause describes procedures related to an MCData in-progress emergency group state cancel. The emergency state of the group can also be cancelled by the group SDS in-progress emergency state cancellation procedure in subclause 7.4.2.10.2, or by the emergency alert cancellation procedure specified in 3GPP TS 23.280... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.13.2 Procedure
| The procedure in figure 7.5.2.13.2-1 describes the case where an authorized MCData user cancels MCData group's in-progress emergency.
Pre-conditions:
1. The MCData group is previously defined on the group management server with MCData client 1, MCData client 2 and MCData client 3 affiliated to that MCData group.
2.... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.14 Group FD communication upgrade to an imminent peril group FD communication
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.14.1 General
| This clause is for adding procedures related to an imminent peril group FD communication.
|
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.14.2 Procedure
| This procedure is applicable only when group MCData communication is established as described in subclause 7.5.2.7 "Group standalone file distribution using media plane". The MCData service shall support the procedures and related information flows as specified in subclause 7.5.2.12 "Group FD communication upgrade to a... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.15 Group FD communication in-progress imminent peril group state cancel
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.15.1 General
| This clause is for adding procedures related to an imminent peril group state cancel.
|
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.2.15.2 Procedure
| The MCData service shall support the procedures and related information flows as specified in subclause 7.5.2.13 "Group FD communication in-progress emergency group state cancel" with the following clarifications:
- In step 2), the MCData client 1 sets the imminent peril indicator; and
- In step 5), MCData users are ... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.3 File distribution for off-network
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.3.1 General
| Off-network file distribution communications are based on ProSe capabilities as described in clause 7.16.
|
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.3.2 Information flows for file distribution
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.3.2.1 MCData FD request (using media plane)
| Table 7.5.3.2.1-1 describes the information flow for the MCData FD request sent from the MCData client to another MCData client.
Table 7.5.3.2.1-1: MCData FD request (using media plane)
Information element
Status
Description
MCData ID
M
The identity of the MCData user sending the file
MCData ID
M
The identity... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.3.2.2 MCData FD response (using media plane)
| Table 7.5.3.2.2-1 describes the information flow for the MCData FD response sent from the MCData client to another MCData client.
Table 7.5.3.2.2-1: MCData FD response (using media plane)
Information element
Status
Description
MCData ID
M
The identity of the MCData user sending FD request
MCData ID
M
The iden... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.3.2.3 MCData download completed report
| Table 7.5.3.2.3-1 describes the information flow for the MCData download completed report sent from the MCData client to another MCData client.
Table 7.5.3.2.3-1: MCData download completed report
Information element
Status
Description
MCData ID
M
The identity of the MCData user sending FD request
MCData ID
M
... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.3.2.4 MCData group standalone FD request (using media plane)
| Table 7.5.3.2.4-1 describes the information flow for the MCData group standalone FD request sent from the MCData client to another MCData client.
Table 7.5.3.2.4-1: MCData group standalone FD request (using media plane)
Information element
Status
Description
MCData ID
M
The identity of the MCData user sending th... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.3.2.5 MCData group standalone FD response (using media plane)
| Table 7.5.3.2.5-1 describes the information flow for the MCData group standalone FD response sent from the MCData client to another MCData client.
Table 7.5.3.2.5-1: MCData group standalone FD response (using media plane)
Information element
Status
Description
MCData ID
M
The identity of the MCData user sending ... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 7.5.3.3 One-to-one standalone file distribution using media plane
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.