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.2.1.12 MCData group standalone FD request (using media plane)
7.5.2.1.13 MCData group standalone FD response (using media plane)
7.5.2.1.14 MCData remove file request by user
7.5.2.1.15 MCData remove file response by user
7.5.2.1.18 MCData remove file notify
7.5.2.1.19 MCData file retrieve request
7.5.2.1.20 MCData file retrieve response
7.5.2.1.21 MCData group standalone FD over MBMS request
7.5.2.1.22 MCData one-to-one FD upgrade request
7.5.2.1.23 MCData one-to-one FD upgrade response
7.5.2.1.24 MCData group FD upgrade request
7.5.2.1.25 MCData group FD upgrade response
7.5.2.1.26 MCData group FD in-progress priority state cancel request
7.5.2.1.27 MCData group FD in-progress priority state cancel response
7.5.2.1.28 MCData file upload request
7.5.2.1.29 MCData file upload response
7.5.2.1.30 MCData file upload completion status
7.5.2.1.31 MCData file download request
7.5.2.1.32 MCData file download response
7.5.2.1.33 MCData file availability request
7.5.2.1.34 MCData file availability response
...
...
7.5.2.1.12 MCData group standalone FD request (using media plane) p. 103
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.
| 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 data 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 (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 3) | M | Media parameters offered |
| Requested priority | O | Application priority level requested for this communication session |
| 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.
NOTE 3:
Includes file metadata.
|
||
| 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 data 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 (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 3) | M | Media parameters offered |
| Requested priority | O | Application priority level requested for this communication session |
| 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.
NOTE 3:
Includes file metadata.
|
||
7.5.2.1.13 MCData group standalone FD response (using media plane) p. 104
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.
| 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 |
| SDP answer | M | Media parameters selected |
7.5.2.1.14 MCData remove file request by user |R16| p. 104
Table 7.5.2.1.14-1 describes the information flow for the MCData remove file request by user 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.
| Information Element | Status | Description |
|---|---|---|
| MCData ID (see NOTE 1) | O | The identity of the MCData user removing file |
| Partner MCData system identity (see NOTE 2) | O | The identity of the partner MCData system where the file has also been downloaded |
| Content reference | M | URL of the content to be removed |
|
NOTE 1:
The identity of the MCData user removing the file is present when sent from MCData client to MCData content server
NOTE 2:
The identity of the partner MCData system is present when sent from MCData content server to MCData content server.
|
||
7.5.2.1.15 MCData remove file response by user |R16| p. 105
Table 7.5.2.1.15-1 describes the information flow for the MCData remove file response by user 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.
| Information Element | Status | Description |
|---|---|---|
| MCData ID (see NOTE 1) | O | The identity of the MCData user removing file |
| Partner MCData system identity (see NOTE 2) | O | The identity of the partner MCData system where the file has also been downloaded |
| Result | M | Indicates the success or failure of the file removal |
|
NOTE 1:
The identity of the MCData user removing the file is present when sent from MCData content server to MCData client
NOTE 2:
The identity of the partner MCData system is present when sent from MCData content server to MCData content server.
|
||
7.5.2.1.16 Void
7.5.2.1.17 Void
7.5.2.1.18 MCData remove file notify |R16| p. 105
Table 7.5.2.1.18-1 describes the information flow for the MCData remove file notify sent from the MCData server to the MCData client that the shared file has been removed.
| Information Element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user uploaded the file |
| Content reference | M | URL of the content that has been removed |
| Reason | O | The reason the file is removed |
7.5.2.1.19 MCData file retrieve request |R16| p. 105
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.
| Information Element | Status | Description |
|---|---|---|
| Content reference | M | URL reference to the content to download |
7.5.2.1.20 MCData file retrieve response |R16| p. 106
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.
| Information Element | Status | Description |
|---|---|---|
| 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 file retrieve request indicates success.
|
||
7.5.2.1.21 MCData group standalone FD over MBMS request |R16| p. 106
Table 7.5.2.1.21-1 describes the information flow for the MCData group standalone FD request (in subclause 7.5.2.6.2) sent from the MCData server to another MCData client.
| Information Element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the 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 | M | 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 |
| MBMS user service id | M | Id of the MBMS user service delivering the file |
| MBMS content URI | M | URI upon which the content is delivered in the MBMS user service |
7.5.2.1.22 MCData one-to-one FD upgrade request |R16| p. 106
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.
| Information Element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user sending data (when initiated by MCData client); The identity of the MCData user receiving data (when initiated by MCData server). |
| Functional alias | O | The associated functional alias of the MCData user sending data or receiving data. |
| Conversation Identifier | M | Identifies the conversation |
| Emergency indicator | M | Indicates that the data request is for MCData emergency communication |
7.5.2.1.23 MCData one-to-one FD upgrade response |R16| p. 106
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.
| Information Element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user sending data (when initiated by MCData client); The identity of the MCData user receiving data (when initiated by MCData server). |
| Conversation Identifier | M | Identifies the conversation |
7.5.2.1.24 MCData group FD upgrade request |R16| p. 107
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.
| Information Element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user sending the upgrade request |
| Functional alias | O | The associated functional alias of the MCData user sending data or receiving data. |
| MCData group ID | M | The MCData group ID on which the emergency upgrade request is made |
| Conversation Identifier | M | Identifies the conversation |
| 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.
|
||
| Information Element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user sending the upgrade request |
| Functional alias | O | The associated functional alias of the MCData user sending data or receiving data. |
| MCData group ID | M | The MCData group ID on which the emergency upgrade request is made |
| MCData ID | M | The identity of the MCData user receiving the upgrade request |
| Conversation Identifier | M | Identifies the conversation |
| 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.25 MCData group FD upgrade response |R16| p. 108
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.
| Information Element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user sending data (when initiated by MCData client); The identity of the MCData user receiving data (when initiated by MCData server). |
| MCData group ID | M | The MCData group ID on which the emergency upgrade request is made |
| Conversation Identifier | M | Identifies the conversation |
7.5.2.1.26 MCData group FD in-progress priority state cancel request |R16| p. 108
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.
| Information Element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the cancelling MCData User |
| MCData group ID | M | The MCData group ID on which the MCData in-progress emergency state is to be cancelled. |
| 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 |
| Conversation Identifier | M | Identifies the conversation |
|
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.
|
||
| Information Element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the cancelling MCData User |
| MCData group ID | M | The MCData group ID on which the MCData in-progress emergency state is to be cancelled. |
| MCData ID | M | The identity of the MCData user receiving the cancel request |
| 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 |
| Conversation Identifier | M | Identifies the conversation |
|
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.27 MCData group FD in-progress priority state cancel response |R16| p. 108
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.
| Information Element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the cancelling party |
| MCData group ID | M | The MCData group ID on which the MCData in-progress emergency in-progress is to be cancelled. |
| Conversation Identifier | M | Identifies the conversation |
7.5.2.1.28 MCData file upload request |R17| p. 109
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.
| Information element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user uploading the file |
| Transaction Identifier | M | Identifies the MCData transaction |
| Access information | M | Provides access resource details to be used by the MCData client for the file upload, e.g. IP address and port |
| MCData content server information | M | Provides information about the target MCData content server, where the file is intended to be uploaded, e.g. URI or IP address, and port (e.g. standard port 80 for HTTP) |
| Emergency indicator | O | Indicates that the request is for an MCData emergency communication |
7.5.2.1.29 MCData file upload response |R17| p. 109
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.
| Information element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user requesting to upload the file |
| Transaction Identifier | M | Identifies the MCData transaction |
| File upload confirmation | M | Indicates whether the file upload to the MCData content server can proceed or not |
7.5.2.1.30 MCData file upload completion status |R17| p. 109
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.
| Information element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user uploading the file |
| Transaction Identifier | M | Identifies the MCData transaction |
| File upload status | M | Indicates the file upload to the MCData content server is completed |
7.5.2.1.31 MCData file download request |R17| p. 109
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.
| Information element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user downloading the file |
| Transaction Identifier | M | Identifies the MCData transaction |
| Access information | M | Provides access resource details to be used by the MCData client for the file download, e.g. IP address and port |
| MCData content server information | M | Provides information about the target MCData content server, where the file is intended to be downloaded from, e.g. URI or IP address, and port (e.g. standard port 80 for HTTP) |
| Content reference | M | URL reference to the content to download |
| Emergency indicator | O | Indicates that the request is for an MCData emergency communication |
7.5.2.1.32 MCData file download response |R17| p. 110
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.
| Information element | Status | Description |
|---|---|---|
| MCData ID | M | The identity of the MCData user requesting to dowload the file |
| Transaction Identifier | M | Identifies the MCData transaction |
| File download confirmation | M | Indicates whether the file download from the MCData content server can proceed or not |
7.5.2.1.33 MCData file availability request |R17| p. 110
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.
| Information element | Status | Description |
|---|---|---|
| Content reference | M | URL reference of the file required to check its availability in the MCData content server |
7.5.2.1.34 MCData file availability response |R17| p. 110
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.
| Information element | Status | Description |
|---|---|---|
| Content reference | M | URL reference of the file required to check its availability in the MCData content server |
| Result | M | Indicates whether the file is available or not |
