Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.282  Word version:  18.2.0

Top   Top   Up   Prev   Next
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.3…   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…   A…   B…

 

7.5.2.1.12  MCData group standalone FD request (using media plane)p. 102
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 IDMThe identity of the MCData user sending the file
Functional aliasOThe functional alias associated with MCData user sending the file
MCData group IDMThe MCData group ID to which the data is to be sent
Conversation IdentifierMIdentifies the conversation
Transaction IdentifierMIdentifies the MCData transaction
Reply IdentifierOIdentifies the original MCData transaction to which the current transaction is a reply to
Disposition indicationOIndicates whether file download completed report is expected or not
Download indicationOIndicates mandatory download (i.e. auto accept this media plane setup request)
Application metadata containerOImplementation specific information that is communicated to the recipient
SDP offer (see NOTE 3)MMedia parameters offered
Requested priorityOApplication priority level requested for this communication session
Emergency indicator (see NOTE 1)OIndicates that the data request is for MCData emergency communication
Alert indicator (see NOTE 2)OIndicates whether an emergency alert is to be sent
Imminent peril indicator (see NOTE 1)OIndicates 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 IDMThe identity of the MCData user sending the file
Functional aliasOThe functional alias associated with MCData user sending the file
MCData group IDMThe MCData group ID to which the data is to be sent
MCData IDMThe identity of the MCData user receiving the file
Conversation IdentifierMIdentifies the conversation
Transaction IdentifierMIdentifies the MCData transaction
Reply IdentifierOIdentifies the original MCData transaction to which the current transaction is a reply to
Disposition indicationOIndicates whether file download completed report is expected or not
Download indicationOIndicates mandatory download (i.e. auto accept this media plane setup request)
Application metadata containerOImplementation specific information that is communicated to the recipient
SDP offer (see NOTE 3)MMedia parameters offered
Requested priorityOApplication priority level requested for this communication session
Emergency indicator (see NOTE 1)OIndicates that the data request is for MCData emergency communication
Alert indicator (see NOTE 2)OIndicates whether an emergency alert is to be sent
Imminent peril indicator (see NOTE 1)OIndicates 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.
Up
7.5.2.1.13  MCData group standalone FD response (using media plane)p. 103
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 IDMThe identity of the MCData user sending FD request
MCData group IDMThe MCData group ID to which the file is to be sent
MCData IDMThe identity of the MCData user sending response
Conversation IdentifierMIdentifies the conversation
SDP answerMMedia parameters selected
Up
7.5.2.1.14  MCData remove file request by user |R16|p. 103
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)OThe identity of the MCData user removing file
Partner MCData system identity (see NOTE 2)OThe identity of the partner MCData system where the file has also been downloaded
Content referenceMURL 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.
Up
7.5.2.1.15  MCData remove file response by user |R16|p. 104
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)OThe identity of the MCData user removing file
Partner MCData system identity (see NOTE 2)OThe identity of the partner MCData system where the file has also been downloaded
ResultMIndicates 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.
Up
7.5.2.1.16Void
7.5.2.1.17Void
7.5.2.1.18  MCData remove file notify |R16|p. 104
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 IDMThe identity of the MCData user uploaded the file
Content referenceMURL of the content that has been removed
ReasonOThe reason the file is removed
Up
7.5.2.1.19  MCData file retrieve request |R16|p. 104
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 referenceMURL reference to the content to download
Up
7.5.2.1.20  MCData file retrieve response |R16|p. 105
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)ORequested content to download
ResultMIndicates success or failure of MCData download data request
NOTE:
Content shall be present when the result of the MCData file retrieve request indicates success.
Up
7.5.2.1.21  MCData group standalone FD over MBMS request |R16|p. 105
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 IDMThe identity of the MCData user sending the file
MCData group IDMThe MCData group ID to which the file is to be sent
Conversation IdentifierMIdentifies the conversation
Transaction IdentifierMIdentifies the MCData transaction
Reply IdentifierOIdentifies the original MCData transaction to which the current transaction is a reply to
Disposition indicationOIndicates whether file download completed report is expected or not
Download indicationMIndicates mandatory download
Application metadata containerOImplementation specific information that is communicated to the recipient
Content referenceMURL reference to the content and file metadata information
MBMS user service idMId of the MBMS user service delivering the file
MBMS content URIMURI upon which the content is delivered in the MBMS user service
Up
7.5.2.1.22  MCData one-to-one FD upgrade request |R16|p. 105
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 IDM 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 aliasOThe associated functional alias of the MCData user sending data or receiving data.
Conversation IdentifierMIdentifies the conversation
Emergency indicatorMIndicates that the data request is for MCData emergency communication
Up
7.5.2.1.23  MCData one-to-one FD upgrade response |R16|p. 105
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 IDM 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 IdentifierMIdentifies the conversation
Up
7.5.2.1.24  MCData group FD upgrade request |R16|p. 106
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 IDMThe identity of the MCData user sending the upgrade request
Functional aliasOThe associated functional alias of the MCData user sending data or receiving data.
MCData group IDMThe MCData group ID on which the emergency upgrade request is made
Conversation IdentifierMIdentifies the conversation
Emergency indicator (see NOTE 1)OIndicates that the data request is for MCData emergency communication
Alert indicator (see NOTE 2)OIndicates whether an emergency alert is to be sent
Imminent peril indicator (see NOTE 1)OIndicates 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 IDMThe identity of the MCData user sending the upgrade request
Functional aliasOThe associated functional alias of the MCData user sending data or receiving data.
MCData group IDMThe MCData group ID on which the emergency upgrade request is made
MCData IDMThe identity of the MCData user receiving the upgrade request
Conversation IdentifierMIdentifies the conversation
Emergency indicator (see NOTE 1)OIndicates that the data request is for MCData emergency communication
Alert indicator (see NOTE 2)OIndicates whether an emergency alert is to be sent
Imminent peril indicator (see NOTE 1)OIndicates 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.
Up
7.5.2.1.25  MCData group FD upgrade response |R16|p. 107
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 IDM 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 IDMThe MCData group ID on which the emergency upgrade request is made
Conversation IdentifierMIdentifies the conversation
Up
7.5.2.1.26  MCData group FD in-progress priority state cancel request |R16|p. 107
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 IDMThe identity of the cancelling MCData User
MCData group IDMThe MCData group ID on which the MCData in-progress emergency state is to be cancelled.
Emergency indicator (see NOTE 1)OIndicates that the data request is for MCData emergency communication
Alert indicator (see NOTE 2)OIndicates whether an emergency alert is to be sent
Imminent peril indicator (see NOTE 1)OIndicates that the data request is for MCData imminent peril communication
Conversation IdentifierMIdentifies 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 IDMThe identity of the cancelling MCData User
MCData group IDMThe MCData group ID on which the MCData in-progress emergency state is to be cancelled.
MCData IDMThe identity of the MCData user receiving the cancel request
Emergency indicator (see NOTE 1)OIndicates that the data request is for MCData emergency communication
Alert indicator (see NOTE 2)OIndicates whether an emergency alert is to be sent
Imminent peril indicator (see NOTE 1)OIndicates that the data request is for MCData imminent peril communication
Conversation IdentifierMIdentifies 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.
Up
7.5.2.1.27  MCData group FD in-progress priority state cancel response |R16|p. 107
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 IDMThe identity of the cancelling party
MCData group IDMThe MCData group ID on which the MCData in-progress emergency in-progress is to be cancelled.
Conversation IdentifierMIdentifies the conversation
Up
7.5.2.1.28  MCData file upload request |R17|p. 108
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 IDMThe identity of the MCData user uploading the file
Transaction IdentifierMIdentifies the MCData transaction
Access informationMProvides access resource details to be used by the MCData client for the file upload, e.g. IP address and port
MCData content server informationMProvides 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 indicatorOIndicates that the request is for an MCData emergency communication
Up
7.5.2.1.29  MCData file upload response |R17|p. 108
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 IDMThe identity of the MCData user requesting to upload the file
Transaction IdentifierMIdentifies the MCData transaction
File upload confirmationMIndicates whether the file upload to the MCData content server can proceed or not
Up
7.5.2.1.30  MCData file upload completion status |R17|p. 108
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 IDMThe identity of the MCData user uploading the file
Transaction IdentifierMIdentifies the MCData transaction
File upload statusMIndicates the file upload to the MCData content server is completed
Up
7.5.2.1.31  MCData file download request |R17|p. 108
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 IDMThe identity of the MCData user downloading the file
Transaction IdentifierMIdentifies the MCData transaction
Access informationMProvides access resource details to be used by the MCData client for the file download, e.g. IP address and port
MCData content server informationMProvides 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 referenceMURL reference to the content to download
Emergency indicatorOIndicates that the request is for an MCData emergency communication
Up
7.5.2.1.32  MCData file download response |R17|p. 109
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 IDMThe identity of the MCData user requesting to dowload the file
Transaction IdentifierMIdentifies the MCData transaction
File download confirmationMIndicates whether the file download from the MCData content server can proceed or not
Up
7.5.2.1.33  MCData file availability request |R17|p. 109
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 referenceMURL reference of the file required to check its availability in the MCData content server
Up
7.5.2.1.34  MCData file availability response |R17|p. 109
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 referenceMURL reference of the file required to check its availability in the MCData content server
ResultMIndicates whether the file is available or not
Up

Up   Top   ToC