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  Short data servicep. 53

7.4.1  Generalp. 53

There are several procedures how an SDS message can be transported from the sender to the recipient. All of the following factors are used by MCData client for selecting appropriate SDS procedures:
  • Whether the data to transfer is within or outside the SDS data size limit to transport over signalling control plane;
  • Whether the MCData user has only one SDS transaction or multiple SDS transactions;
  • Whether MCData user, optionally using its associated and activated functional alias, is targeting SDS transaction to another MCData user or MCData group;
  • Whether MCData UE is on-network or off-network; and
  • Security reasons.
Up

7.4.2  Short data service for on-networkp. 54

The procedures described in the following subclauses are limited to single MCData system only.

7.4.2.1  Information flows for short data servicep. 54

7.4.2.1.1  MCData standalone data requestp. 54
Table 7.4.2.1.1-1 describes the information flow for the MCData standalone data 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 data
Functional aliasOThe associated functional alias of the MCData user sending data.
MCData ID (see NOTE 1)OThe identity of the MCData user towards which the data is sent
Functional alias (see NOTE 1)OThe associated functional alias of the MCData user identity 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 Emergency indicator O Indicates that the data request is for MCData emergency 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 2)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
PayloadMSDS content
NOTE 1:
Either the MCData ID or the functional alias must be present.
NOTE 2:
The application identifier shall be included only if the payload destination type indicates that the payload is for application consumption.
Information Element Status Description
MCData IDMThe identity of the MCData user sending data
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
Emergency indicatorOIndicates that the data request is for MCData emergency 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 client consumption
LocationOLocation of the Originating MCData user sending the SDS message
Application identifier (see NOTE)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
PayloadMSDS content
NOTE:
The application identifier shall be included only if the payload destination type indicates that the payload is for application consumption.
Up
7.4.2.1.2  MCData data disposition notificationp. 55
Table 7.4.2.1.2-1 describes the information flow for the MCData data disposition notification sent from the MCData client to the MCData server.
Information Element Status Description
MCData IDMThe identity of the MCData user towards which the notification is sent
MCData IDMThe identity of the MCData user sending notification
Conversation IdentifierMIdentifies the conversation
Disposition associationMIdentity of the original MCData transaction
DispositionMDisposition which is delivered or read or both
Up
7.4.2.1.3  MCData standalone session data requestp. 55
Table 7.4.2.1.3-1 describes the information flow for the MCData standalone session data 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 data
Functional aliasOThe associated functional alias of the MCData user sending data.
MCData ID (see NOTE 1)OThe identity of the MCData user towards which the data is sent
Functional alias (see NOTE 1)OThe associated functional alias of the MCData user identity 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 indicatorOIndicates that the data request is for MCData emergency 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 2)OIdentifies the application for which the payload is intended (e.g. text string, port address, URI)
Requested PriorityOApplication priority level requested for this communication.
Application metadata containerOImplementation specific information that is communicated to the recipient
SDP offerMMedia parameters offered
NOTE 1:
Either the MCData ID or the functional alias must be present.
NOTE 2:
The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption.
Information Element Status Description
MCData IDMThe identity of the MCData user sending data
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
Emergency indicatorOIndicates that the data request is for MCData emergency communication
Transaction typeMStandalone transaction
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)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:
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.4  MCData standalone session data responsep. 57
Table 7.4.2.1.4-1 describes the information flow for the MCData standalone session 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 IDMThe identity of the MCData user sent data
Conversation IdentifierMIdentifies the conversation
SDP answerMMedia parameters selected
Establishment reasonMReason for establishment or rejection
Up
7.4.2.1.5  MCData session data requestp. 57
Table 7.4.2.1.5-1 describes the information flow for the MCData session data 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 data
Functional aliasOThe associated functional alias of the MCData user sending data.
MCData ID (see NOTE 1)OThe identity of the MCData user towards which the data is sent
Functional alias (see NOTE 1)OThe associated functional alias of the MCData user identity 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 typeMSession based transactions
Emergency indicatorOIndicates that the data request is for MCData emergency 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 2)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:
Either the MCData ID or the functional alias must be present.
NOTE 2:
The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption.
Information Element Status Description
MCData IDMThe identity of the MCData user sending data
MCData IDOThe 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 typeMSession based transactions
Emergency indicatorOIndicates that the data request is for MCData emergency communication
Disposition TypeOIndicates the disposition type expected from the receiver (i.e., delivered or read or both)
LocationOLocation of the Originating MCData user sending the SDS message
Payload Destination TypeMIndicates whether the SDS payload is for application consumption or MCData user consumption
Application identifier (see NOTE)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:
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.6  MCData session data responsep. 58
Table 7.4.2.1.6-1 describes the information flow for the MCData session 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 IDMThe identity of the MCData user sent data
Conversation IdentifierMIdentifies the conversation
SDP answerMMedia parameters selected
Up
7.4.2.1.7  MCData group standalone data request (MCData client - MCData server)p. 58
Table 7.4.2.1.7-1 describes the information flow for the MCData group standalone data request (in subclause 7.4.2.5.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
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)
MCData ID list (see NOTE 4)OThe specified MCData users who should send a disposition notification message.
Payload Destination TypeMIndicates whether the payload is for application consumption or MCData user consumption
LocationOLocation of the Originating MCData user sending the SDS
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
PayloadMSDS content
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.
NOTE 4:
If Disposition Type IE is not present, this IE shall not be present. If Disposition Type IE is present but this IE is not, which indicates that all receivers shall respond with disposition notification message.
Up
7.4.2.1.8  MCData group standalone data request (MCData server - MCData client)p. 59
Table 7.4.2.1.8-1 describes the information flow for the MCData group standalone data request (in subclause 7.4.2.5.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
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)
MCData ID list (see NOTE 4)OThe specified MCData users who should send a disposition notification message.
Payload Destination TypeMIndicates whether the payload is for application consumption or MCData user consumption
LocationOLocation of the Originating MCData user sending the SDS
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
PayloadMSDS content
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 payload is for application consumption.
NOTE 4:
If Disposition Type IE is not present, this IE shall not be present. If Disposition Type IE is present but this IE is not, which indicates that all receivers shall respond with disposition notification message.
Up
7.4.2.1.9  MCData data disposition notification (MCData server - MCData client)p. 60
Table 7.4.2.1.9-1 describes the information flow for the MCData data disposition notification(s) sent from the MCData server to the MCData client.
Information Element Status Description
MCData IDMThe identity of the MCData user towards which the notification is sent
MCData IDMThe identity of the MCData user sending notification
Conversation IdentifierMIdentifies the conversation
Disposition associationMIdentity of the original MCData transaction
DispositionMDisposition which is delivered or read or both
Up
7.4.2.1.9A  MCData aggregated data disposition notification |R17|p. 60
Table 7.4.2.1.9A-1 describes the information flow for the MCData aggregated data disposition notification sent from the MCData server to the MCData client, indicating the result of a request for an SDS delivery to an MCData group.
Information element Status Description
MCData IDMThe identity of the MCData user towards which the notification is sent
Number of Aggregated NotificationsMTotal number of received individual notifications
Number of "Read" Notifications O Number of MCData users who only reported the "read" disposition
Number of "Delivered" Notifications O Number of MCData users who only reported the "delivered" disposition
Conversation IdentifierMIdentifies the conversation
Disposition associationMIdentity of the original MCData transaction
"Read" MCData ID list O List, partial or full, of MCData users who only reported the "read" disposition
"Delivered" MCData ID list O List, partial or full, of MCData users who only reported the "delivered" disposition
Up

Up   Top   ToC