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.4.2.1.10  MCData group session standalone data request (MCData client - MCData server)p. 61
Table 7.4.2.1.10-1 describes the information flow for the MCData group session standalone data request (in subclause 7.4.2.6.2) sent from the MCData client to the MCData server.
Information Element Status Description
MCData IDMThe identity of the MCData user sending data
Functional aliasOThe associated functional alias of the MCData user sending data.
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
Transaction typeMStandalone transaction
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
Disposition TypeOIndicates the disposition type expected from the receiver (i.e., delivered or read or both)
Payload Destination TypeMIndicates whether the payload is for application consumption or MCData user consumption
LocationOLocation of the Originating MCData user sending the SDS message
Application identifier (see NOTE 3)OIdentifies the application for which the payload is intended (e.g. text string, port address, URI, attached data hosts)
Application metadata containerOImplementation specific information that is communicated to the recipient
SDP offerMMedia parameters offered
Requested priorityOApplication priority level requested for this communication session
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 2:
The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption or IP data in IP connectivity sessions are for data host consumption.
Up
7.4.2.1.11  MCData group session standalone data request (MCData server - MCData client)p. 62
Table 7.4.2.1.11-1 describes the information flow for the MCData group session standalone data request (in subclause 7.4.2.6.2) sent from the MCData server to the MCData client.
Information Element Status Description
MCData IDMThe identity of the MCData user sending data
Functional aliasOThe associated functional alias of the MCData user sending data.
MCData group IDMThe MCData group ID to which the data is to be sent
MCData IDMThe identity of the MCData user towards which the data is 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
Transaction typeMStandalone transaction
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
Disposition TypeOIndicates the disposition type expected from the receiver (i.e., delivered or read or both)
Payload Destination TypeMIndicates whether the payload is for application consumption or MCData user consumption
LocationOLocation of the Originating MCData user sending the SDS message
Application identifier (see NOTE 3)OIdentifies the application for which the payload is intended (e.g. text string, port address, URI, attached data hosts)
Application metadata containerOImplementation specific information that is communicated to the recipient
SDP offerMMedia parameters offered
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:
The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption or IP data in IP connectivity sessions are for data host consumption.
Up
7.4.2.1.12  MCData group session standalone data responsep. 62
Table 7.4.2.1.12-1 describes the information flow for the MCData group standalone data response (in subclause 7.4.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 IDMThe identity of the MCData user receiving data
MCData group IDMThe MCData group ID to which the data is to be sent
MCData IDMThe identity of the MCData user sent data
Conversation IdentifierMIdentifies the conversation
SDP answerMMedia parameters selected
Up
7.4.2.1.13  MCData group data request (MCData client - MCData server)p. 62
Table 7.4.2.1.13-1 describes the information flow for the MCData group data request sent from the MCData client to the MCData server.
Information Element Status Description
MCData IDMThe identity of the MCData user sending data
Functional aliasOThe associated functional alias of the MCData user sending data.
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
Transaction typeMSession based transactions
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
Disposition TypeOIndicates the disposition type expected from the receiver (i.e., delivered or read or both)
Payload Destination TypeMIndicates whether the SDS payload is for application consumption or MCData user consumption
LocationOLocation of the Originating MCData user sending the SDS message
Application identifier (see NOTE 3)OIdentifies the application for which the payload is intended (e.g. text string, port address, URI)
Application metadata containerOImplementation specific information that is communicated to the recipient
SDP offerMMedia parameters offered
Requested priorityOApplication priority level requested for this communication session
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:
The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption.
Up
7.4.2.1.14  MCData group data request (MCData server - MCData client)p. 63
Table 7.4.2.1.14-1 describes the information flow for the MCData group data request sent from the MCData server to the MCData client.
Information Element Status Description
MCData IDMThe identity of the MCData user sending data
Functional aliasOThe associated functional alias of the MCData user sending data.
MCData group IDMThe MCData group ID to which the data is to be sent
MCData IDMThe identity of the recipient MCData user
Conversation IdentifierMIdentifies the conversation
Transaction IdentifierMIdentifies the MCData transaction
Reply IdentifierOIdentifies the original MCData transaction to which the current transaction is a reply to
Transaction typeMSession based transactions
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
Disposition TypeOIndicates the disposition type expected from the receiver (i.e., delivered or read or both)
Payload Destination TypeMIndicates whether the SDS payload is for application consumption or MCData user consumption
LocationOLocation of the Originating MCData user sending the SDS message
Application identifier (see NOTE 3)OIdentifies the application for which the payload is intended (e.g. text string, port address, URI)
Application metadata containerOImplementation specific information that is communicated to the recipient
SDP offerMMedia parameters offered
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:
The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption.
Up
7.4.2.1.15  MCData group data responsep. 64
Table 7.4.2.1.15-1 describes the information flow for the MCData group data response 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 receiving data
MCData group IDMThe MCData group ID to which the data is to be sent
MCData IDMThe identity of the MCData user sent data
Conversation IdentifierMIdentifies the conversation
SDP answerMMedia parameters selected
Up
7.4.2.1.16  MCData one-to-one SDS communication upgrade request |R16|p. 64
Table 7.4.2.1.16-1 describes the information flow for the MCData one-to-one SDS communication 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.4.2.1.17  MCData one-to-one SDS communication upgrade response |R16|p. 65
Table 7.4.2.1.17-1 describes the information flow for the MCData one-to-one SDS communication 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.4.2.1.18  MCData group SDS communication upgrade request |R16|p. 65
Table 7.4.2.1.18-1 describes the information flow for the MCData group SDS communication 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 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 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.4.2.1.19  MCData group SDS communication upgrade response |R16|p. 66
Table 7.4.2.1.19-1 describes the information flow for the MCData group SDS communication 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.4.2.1.20  MCData group SDS communication in-progress priority state cancel request |R16|p. 66
Table 7.4.2.1.20-1 describes the information for the MCData group SDS communication 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 party
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 party
MCData group IDMThe MCData group ID on which the MCData in-progress emergency state is to be cancelled.
MCData IDMThe identity of the recipient MCData user
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.4.2.1.21  MCData group SDS communication in-progress priority state cancel response |R16|p. 67
Table 7.4.2.1.21-1 describes the information flow for the MCData group SDS communication 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.4.2.1.22  MCData functional alias resolution response |R17|p. 67
Table 7.4.2.1.22-1 describes the information flow MCData functional alias resolution response from the MCData server to the MCData client.
Information Element Status Description
MCData IDMThe identity of the MCData user sending the data
MCData IDMThe corresponding MCData ID of the functional alias resolved by MCData server
Up

Up   Top   ToC