Content for TS 23.282 Word version: 19.1.0
1…
5…
6…
6.6…
7…
7.4…
7.4.2.1.10…
7.4.2.2…
7.4.2.5…
7.4.2.8…
7.4.3…
7.5…
7.5.2.1.12…
7.5.2.2…
7.5.2.4…
7.5.2.6…
7.5.2.8…
7.5.2.11…
7.5.2.14…
7.5.3…
7.6
7.7…
7.7.2.1.13…
7.7.2.2…
7.8…
7.9…
7.13…
7.13.3.1.19…
7.13.3.2…
7.13.3.8…
7.13.3.16…
7.13.4…
7.14…
7.14.2.2…
7.17…
7.17.2.13…
7.17.3…
7.17.3.1.4…
7.17.3.2…
7.17.3.2.4…
7.17.3.2.6…
7.17.4…
7.17.6…
A…
B…
7.5 File distribution
7.5.1 General
7.5.2 File distribution for on-network
7.5.2.1 Information flows for file distribution
7.5.2.1.1 MCData upload data request
7.5.2.1.2 MCData upload data response
7.5.2.1.3 MCData download data request
7.5.2.1.4 MCData download data response
7.5.2.1.5 MCData FD request (using HTTP)
7.5.2.1.6 MCData FD response (using HTTP)
7.5.2.1.7 MCData download completed report
7.5.2.1.7A MCData aggregated download completed report
7.5.2.1.8 MCData FD request (using media plane)
7.5.2.1.9 MCData FD response (using media plane)
7.5.2.1.10 MCData group standalone FD request (using HTTP)
7.5.2.1.11 MCData group standalone FD response (using HTTP or MBMS download delivery method)
...
...
7.5 File distribution p. 96
7.5.1 General p. 96
File distribution (mandatory and non-mandatory download) is enabled for both one-to-one and group.
7.5.2 File distribution for on-network p. 96
7.5.2.1 Information flows for file distribution p. 96
7.5.2.1.1 MCData upload data request p. 96
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.
| Information Element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user uploading data |
| Content (see NOTE) | O | Content to upload |
| Content reference (see NOTE) | O | URL reference of the content stored in the MCData message store account of the MCData user |
| Emergency indicator | O | Indicates that the data request is for MCData emergency communication |
|
NOTE:
Either the Content or the Content reference must be present.
|
||
7.5.2.1.2 MCData upload data response p. 96
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.
| Information Element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user requesting to upload data |
| Upload confirmation | M | An indication whether the upload to the content storage is successful or not |
| Content reference | O | URL reference of the content stored (see NOTE). |
|
NOTE:
Content reference shall be present when the upload confirmation is successful.
|
||
7.5.2.1.3 MCData download data request p. 97
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.
| Information Element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user downloading data |
| Content reference | M | URL reference to the content to download |
| Emergency indicator | O | Indicates that the data request is for MCData emergency communication |
7.5.2.1.4 MCData download data response p. 97
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.
| Information Element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user requesting to download data |
| Content (see NOTE) | O | Requested content to download |
| Result | M | Indicates success or failure of MCData download data request |
|
NOTE:
Content shall be present when the result of the MCData download data request indicates success.
|
||
7.5.2.1.5 MCData FD request (using HTTP) p. 97
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.
| Information Element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user sending the file |
| Functional alias | O | The functional alias associated with MCData user sending the file |
| MCData ID (see NOTE) | O | The identity of the MCData user receiving the file |
| Functional alias (see NOTE) | O | The associated functional alias of the MCData user identity towards which the data is sent. |
| Conversation Identifier | M | Identifies the conversation |
| Transaction Identifier | M | Identifies the MCData transaction |
| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to |
| Disposition indication | O | Indicates whether file download completed report is expected or not |
| Download indication | O | Indicates mandatory download |
| Application metadata container | O | Implementation specific information that is communicated to the recipient |
| Content reference | M | URL reference to the content and file metadata information |
| Emergency indicator | O | Indicates that the data request is for MCData emergency communication |
| Deposit file indication | O | Indicates whether the file to be stored into the MCData message store account of the MCData user |
| Location Information | O | Location Information of the Originating MCData user sending the FD message |
|
NOTE:
Either the MCData ID or the functional alias must be present.
|
||
Table 7.5.2.1.5-2 describes the information flow for the MCData FD request (in clause 7.5.2.4.2) sent from an MCData server to a partner MCData server.
| Information Element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user sending the file |
| Functional alias | O | The associated functional alias of the MCData user sending the file. |
| MCData ID | M | The identity of the MCData user receiving the file |
| Conversation Identifier | M | Identifies the conversation |
| Transaction Identifier | M | Identifies the MCData transaction |
| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to |
| Disposition indication | O | Indicates whether file download completed report is expected or not |
| Download indication | O | Indicates mandatory download |
| Application metadata container | O | Implementation specific information that is communicated to the recipient |
| Content reference | M | URL reference to the content and file metadata information |
| Emergency indicator | O | Indicates that the data request is for MCData emergency communication |
| Location Information | O | Location information of the Originating MCData user sending the FD message |
Table 7.5.2.1.5-3 describes the information flow for the MCData FD request (in clause 7.5.2.4.2) sent from the MCData server to the MCData client.
| Information element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user sending the file |
| Functional alias | O | The associated functional alias of the MCData user sending the file |
| MCData ID | M | The identity of the MCData user receiving the file |
| Conversation Identifier | M | Identifies the conversation |
| Transaction Identifier | M | Identifies the MCData transaction |
| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to |
| Disposition indication | O | Indicates whether file download completed report is expected or not |
| Download indication | O | Indicates mandatory download |
| Application metadata container | O | Implementation specific information that is communicated to the recipient |
| Content reference | M | URL reference to the content and file metadata information |
| Emergency indicator | O | Indicates that the data request is for MCData emergency communication |
| Location Information | O | Location information of the Originating MCData user sending the FD message |
7.5.2.1.6 MCData FD response (using HTTP) p. 98
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.
| Information Element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user sending FD request |
| MCData ID | M | The identity of the MCData user sending response |
| Conversation Identifier | M | Identifies the conversation |
| Result | O | Indicates if the request is accepted or not |
7.5.2.1.7 MCData download completed report p. 99
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.
| Information Element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user sending FD request |
| MCData ID | M | The identity of the MCData user sending response |
| Conversation Identifier | M | Identifies the conversation |
| Transaction Identifier | M | Identifies the MCData transaction |
| Reply Identifier | M | Identifies the original MCData transaction to which the current transaction is a reply to |
| Disposition confirmation | M | An indication that the client has completed downloading file |
7.5.2.1.7A MCData aggregated download completed report |R17| p. 99
Table 7.5.2.1.7A-1 describes the information flow for the MCData aggregated download completed report sent from the MCData server to the MCData client, indicating the result of a request for a file delivery to an MCData group.
| Information element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user that sent the FD request |
| Number of Aggregated Reports | M | Total number of received individual completed reports |
| Number of Successful Deliveries | O | Number of received individual completed reports indicating success |
| Conversation Identifier | M | Identifies the conversation |
| Transaction Identifier | M | Identifies the MCData transaction |
| Reply Identifier | M | Identifies the original MCData transaction which the current transaction is a reply to |
| Successful MCData ID list | O (NOTE) | List, partial or full, of MCData users who successfully received the file delivery |
| Unsuccessful MCData ID list | O (NOTE) | List, partial or full, of MCData users who reported failure to fully receive the file delivery successfully |
|
NOTE:
No more than one of these information elements may be present.
|
||
7.5.2.1.8 MCData FD request (using media plane) p. 99
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.
| Information Element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user sending the file |
| Functional alias | O | The functional alias associated with MCData user sending the file |
| MCData ID (see NOTE 1) | O | The identity of the MCData user receiving the file |
| Functional alias (see NOTE 1) | O | The associated functional alias of the MCData user identity towards which the data is sent. |
| Conversation Identifier | M | Identifies the conversation |
| Transaction Identifier | M | Identifies the MCData transaction |
| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to |
| Disposition indication | O | Indicates whether file download completed report is expected or not |
| Download indication | O | Indicates mandatory download. (i.e. auto accept this media plane setup request) |
| Application metadata container | O | Implementation specific information that is communicated to the recipient |
| SDP offer (see NOTE 2) | M | Media parameters offered |
| Requested priority | O | Application priority level requested for this communication session |
| Emergency indicator | O | Indicates that the data request is for MCData emergency communication |
|
NOTE 1:
Either the MCData ID or the functional alias must be present.
NOTE 2:
Includes file metadata.
|
||
| Information Element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user sending the file |
| Functional alias | O | The associated functional alias of the MCData user identity sending the file |
| MCData ID | M | The identity of the MCData user receiving the file |
| Functional alias | O | The associated functional alias of the MCData user identity towards which the data is sent. |
| Conversation Identifier | M | Identifies the conversation |
| Transaction Identifier | M | Identifies the MCData transaction |
| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to |
| Disposition indication | O | Indicates whether file download completed report is expected or not |
| Download indication | O | Indicates mandatory download (i.e. auto accept this media plane setup request) |
| Application metadata container | O | Implementation specific information that is communicated to the recipient |
| SDP offer (see NOTE) | M | Media parameters offered |
| Requested priority | O | Application priority level requested for this communication session |
| Emergency indicator | O | Indicates that the data request is for MCData emergency communication |
|
NOTE:
Includes file metadata.
|
||
| Information Element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user sending the file |
| Functional alias | O | The associated functional alias of the MCData user identity sending the file. |
| MCData ID | M | The identity of the MCData user receiving the file |
| Conversation Identifier | M | Identifies the conversation |
| Transaction Identifier | M | Identifies the MCData transaction |
| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to |
| Disposition indication | O | Indicates whether file download completed report is expected or not |
| Download indication | O | Indicates mandatory download (i.e. auto accept this media plane setup request) |
| Application metadata container | O | Implementation specific information that is communicated to the recipient |
| SDP offer (see NOTE) | M | Media parameters offered |
| Requested priority | O | Application priority level requested for this communication session |
| Emergency indicator | O | Indicates that the data request is for MCData emergency communication |
|
NOTE:
Includes file metadata.
|
||
7.5.2.1.9 MCData FD response (using media plane) p. 101
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.
| Information Element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user sending FD request |
| MCData ID | M | The identity of the MCData user sending response |
| Conversation Identifier | M | Identifies the conversation |
| SDP answer | M | Media parameters selected |
| Establishment reason | O | Reason for establishment or rejection |
7.5.2.1.10 MCData group standalone FD request (using HTTP) p. 101
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.
| Information Element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user sending the file |
| Functional alias | O | The functional alias associated with MCData user sending the file |
| MCData group ID | M | The MCData group ID to which the file is to be sent |
| Conversation Identifier | M | Identifies the conversation |
| Transaction Identifier | M | Identifies the MCData transaction |
| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to |
| Disposition indication | O | Indicates whether file download completed report is expected or not |
| Download indication | O | Indicates mandatory download |
| Application metadata container | O | Implementation specific information that is communicated to the recipient |
| Content reference | M | URL reference to the content and file metadata information |
| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication |
| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent |
| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication |
|
NOTE 1:
If used, only one of these information elements shall be present.
NOTE 2:
This information element may be present only when Emergency indicator is present.
|
||
Table 7.5.2.1.10-2 describes the information flow for the MCData group standalone FD request (in subclause 7.5.2.6.2) sent from the MCData server to the MCData client.
| Information Element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user sending the file |
| Functional alias | O | The functional alias associated with MCData user sending the file |
| MCData group ID | M | The MCData group ID to which the file is to be sent |
| MCData ID | M | The identity of the MCData user receiving the file |
| Conversation Identifier | M | Identifies the conversation |
| Transaction Identifier | M | Identifies the MCData transaction |
| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to |
| Disposition indication | O | Indicates whether file download completed report is expected or not |
| Download indication | O | Indicates mandatory download |
| Application metadata container | O | Implementation specific information that is communicated to the recipient |
| Content reference | M | URL reference to the content and file metadata information |
| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication |
| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent |
| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication |
|
NOTE 1:
If used, only one of these information elements shall be present.
NOTE 2:
This information element may be present only when Emergency indicator is present.
|
||
7.5.2.1.11 MCData group standalone FD response (using HTTP or MBMS download delivery method) p. 103
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.
| Information Element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user sending FD request |
| MCData group ID | M | The MCData group ID to which the file is to be sent |
| MCData ID | M | The identity of the MCData user sending response |
| Conversation Identifier | M | Identifies the conversation |
| Result | M | Indicates if the request is accepted or not |
