Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.282  Word version:  19.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.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.13.3.1.19 MCData create folder request  7.13.3.1.20 MCData create folder response  7.13.3.1.21 MCData delete folder request  7.13.3.1.22 MCData delete folder response  7.13.3.1.23 MCData copy folder request  7.13.3.1.24 MCData copy folder response  7.13.3.1.25 MCData move folder request  7.13.3.1.26 MCData move folder response  7.13.3.1.27 MCData list folder request  7.13.3.1.28 MCData list folder response  7.13.3.1.29 MCData upload objects request  7.13.3.1.30 MCData upload objects response  7.13.3.1.31 MCData synchronization notification  7.13.3.1.32 Create notification channel request  7.13.3.1.33 Create notification channel response  7.13.3.1.34 Open notification channel  7.13.3.1.35 Subscribe for notification request  7.13.3.1.36 Subscribe for notification response  7.13.3.1.37 MCData search folder request  7.13.3.1.38 MCData search folder response  7.13.3.1.39 MCData retrieve folder content request  7.13.3.1.40 MCData retrieve folder content response  7.13.3.1.41 MCData retrieve file to store locally request  7.13.3.1.42 MCData retrieve file to store locally response  7.13.3.1.43 Update notification channel request  7.13.3.1.44 Update notification channel response  7.13.3.1.45 Update notification subscription request  7.13.3.1.46 Update notification subscription response  7.13.3.1.47 Delete notification channel request  7.13.3.1.48 Delete notification channel response  7.13.3.1.49 Delete notification subscription request  7.13.3.1.50 Delete notification subscription response  7.13.3.1.51 Notification message 
...

 

7.13.3.1.19  MCData create folder request  p. 174
Table 7.13.3.1.19-1 describes the information flow for the MCData create folder request sent from the message store client to the MCData message store.
Information Element Status Description
MCData IDMThe identity of the MCData user
Parent folder identifierOThe parent folder identifier of the created folder
Folder nameOIndicates the name of the new folder
Up
7.13.3.1.20  MCData create folder response  p. 174
Table 7.13.3.1.20-1 describes the information flow for the MCData create folder response sent from the MCData message store to the message store client.
Information Element Status Description
MCData IDMThe identity of the MCData user
ResultMThe result if the operation is success or failure
Folder identifierOThe identifier of the folder that is created
Up
7.13.3.1.21  MCData delete folder request  p. 174
Table 7.13.3.1.21-1 describes the information flow for the MCData delete folder request sent from the message store client to the MCData message store.
Information Element Status Description
MCData IDMThe identity of the MCData user
Folder identifierMThe identifier of the folder to be deleted
Up
7.13.3.1.22  MCData delete folder response  p. 174
Table 7.13.3.1.22-1 describes the information flow for the MCData delete folder response sent from the MCData message store to the message store client.
Information Element Status Description
MCData IDMThe identity of the MCData user
ResultMThe result if the operation is success or failure
Up
7.13.3.1.23  MCData copy folder request  p. 174
Table 7.13.3.1.23-1 describes the information flow for the MCData copy folder request sent from the message store client to the MCData message store.
Information Element Status Description
MCData IDMThe identity of the MCData user
Source folder identifierMThe identifier of the folder to copy from
Destination folder identifierMThe identifier of the folder to copy to
New folder name (see NOTE)OIndicates the name of the new folder
NOTE:
If no new folder nameinformation element is provided, the new folder name will be the same as the source folder name.
Up
7.13.3.1.24  MCData copy folder response  p. 175
Table 7.13.3.1.24-1 describes the information flow for the MCData copy folder response sent from the MCData message store to the message store client.
Information Element Status Description
MCData IDMThe identity of the MCData user
ResultMThe result if the operation is success or failure
New folder identifierMIndicates the identifier of the new folder
Up
7.13.3.1.25  MCData move folder request  p. 175
Table 7.13.3.1.25-1 describes the information flow for the MCData move folder request sent from the message store client to the MCData message store.
Information Element Status Description
MCData IDMThe identity of the MCData user
Source folder identifierMThe identifier of the folder to be moved
Destination folder identifierMThe identifier of the folder to move to
New folder name (see NOTE)OIndicates the name of the new folder
NOTE:
If no new folder name information element is provided, the new folder name will be the same as the source folder name.
Up
7.13.3.1.26  MCData move folder response  p. 175
Table 7.13.3.1.26-1 describes the information flow for the MCData move folder response sent from the MCData message store to the message store client.
Information Element Status Description
MCData IDMThe identity of the MCData user
ResultMThe result if the operation is success or failure
New folder identifierMIndicates the identifier of the new folder
Up
7.13.3.1.27  MCData list folder request  p. 175
Table 7.13.3.1.27-1 describes the information flow for the MCData list folder request sent from the message store client to the MCData message store.
Information Element Status Description
MCData IDMThe identity of the MCData user
Folder identifierOThe identifier of the folder to be listed
Up
7.13.3.1.28  MCData list folder response  p. 176
Table 7.13.3.1.28-1 describes the information flow for the MCData list folder response sent from the MCData message store to the message store client.
Information Element Status Description
MCData IDMThe identity of the MCData user
Result (see NOTE)MThe result of the list operation
NOTE:
If no folder identifier information element is provided in the request, the MCData message store returns folders from the root of the user account. If folder identifier information element is provided in the request, the MCData message store returns the child folders from that folder identifier provided.
Up
7.13.3.1.29  MCData upload objects request  p. 176
Table 7.13.3.1.29-1 describes the information flow for the MCData upload objects request sent from the message store client to the MCData message store.
Information Element Status Description
MCData IDMThe identity of the MCData user
Targeted folder identifierMThe folder where the uploaded objects will be stored
Uploaded objectsMThe objects in the client that need to be uploaded to the MCData message store
Up
7.13.3.1.30  MCData upload objects response  p. 176
Table 7.13.3.1.30-1 describes the information flow for the MCData upload objects response sent from the MCData message store to the message store client.
Information Element Status Description
MCData IDMThe identity of the MCData user
Object upload resultMIndicates if the objects upload is successful or not
Up
7.13.3.1.31  MCData synchronization notification  p. 176
Table 7.13.3.1.31-1 describes the information flow for the MCData synchronization notification sent from the MCData message store to the message store client.
Information Element Status Description
MCData IDMThe identity of the MCData user that the notification is for
Up
7.13.3.1.32  Create notification channel request |R17|  p. 177
Table 7.13.3.1.32-1 describes the information flow for the create notification channel request sent from the message notification client to the MCData notification server.
Information Element Status Description
MCData IDMThe identity of the MCData client initiating the request
Validity durationOHow long the notification channel is intended to be used (see NOTE)
Channel TypeMIndicates if PULL (e.g. long-polling method) or PUSH method will be used to deliver notification messages
NOTE:
If this element not present, a default validity duration shall be provided by the server in response
Up
7.13.3.1.33  Create notification channel response |R17|  p. 177
Table 7.13.3.1.33-1 describes the information flow for the create notification channel response sent from the MCData notification server to the message notification client.
Information Element Status Description
MCData IDMThe identity of the MCData client initiating the request
Validity durationMHow long the notification channel will last (i.e. channel lifetime) as granted by the MCData notification server
Notification URLOThe URL to receive the notification message if a Pull method is requested . For some PUSH method implementation (such as WebSockets) this URL is used to start the PUSH notification service from the MCData notification server
Callback URLMThe URL used by the Message notification client to subscribe to MCData message store notifications
Up
7.13.3.1.34  Open notification channel |R17|  p. 177
Table 7.13.3.1.34-1 describes the information flow for the open notification channel sent from the message notification client to the MCData notification server.
Information Element Status Description
MCData IDMThe identity of the MCData client initiating the request
Notification URLMThe URL to receive the notification message
Up
7.13.3.1.35  Subscribe for notification request |R17|  p. 177
Table 7.13.3.1.35-1 describes the information flow for the subscribe for notification request sent from the message store client to the MCData message store.
Information Element Status Description
MCData IDMThe identity of the MCData client initiating the request
Callback URLMThe URL where to send the notification message
Validity durationMHow long the subscription to notification will last (i.e. subscription lifetime); this value shall be the returned value in the create notification channel response
Up
7.13.3.1.36  Subscribe for notification response |R17|  p. 178
Table 7.13.3.1.36-1 describes the information flow for the subscribe for notification response sent from the MCData message store to the message store client.
Information Element Status Description
MCData IDMThe identity of the MCData client initiating the request
Validity durationMHow long the subscription of notification will last (i.e. subscription lifetime) as granted by the server
ResultMIndicates if the subscription is success or failure
Up
7.13.3.1.37  MCData search folder request |R17|  p. 178
Table 7.13.3.1.37-1 describes the information flow for the MCData search folder request sent from the message store client to the MCData message store.
Information Element Status Description
MCData IDMThe identity of the MCData user
Search criteriaMAny part of the folder information (such as metadata) can be used as the search criteria. Linking multiple parts of the folder information as the search criteria is possible
Up
7.13.3.1.38  MCData search folder response |R17|  p. 178
Table 7.13.3.1.38-1 describes the information flow for the MCData search folder response sent from the MCData message store to the message store client.
Information Element Status Description
MCData IDMThe identity of the MCData user
Folder identifier(s)MThe folder(s) that meets the search criteria. This information element shall be returned as empty if there is no folder matching the search criteria
Up
7.13.3.1.39  MCData retrieve folder content request |R17|  p. 178
Table 7.13.3.1.39-1 describes the information flow for the MCData retrieve folder content request sent from the message store client to the MCData message store.
Information Element Status Description
MCData IDMThe identity of the MCData user
Folder identifierMThe identifier of the folder its content is requested to be returned
Up
7.13.3.1.40  MCData retrieve folder content response |R17|  p. 178
Table 7.13.3.1.40-1 describes the information flow for the MCData retrieve folder content response sent from the MCData message store to the message store client.
Information Element Status Description
MCData IDMThe identity of the MCData user
Folder contentMThe content of the requested folder; such as objects and subfolders. This information element shall be returned as empty if the requested folder is not found.
Up
7.13.3.1.41  MCData retrieve file to store locally request |R17|  p. 179
Table 7.13.3.1.41-1 describes the information flow for the MCData retrieve file to store locally request sent from the message store client to the MCData message store and from the MCData server to the MCData message store.
Information Element Status Description
MCData IDMThe identity of the MCData user
Object identifierMThe object identifier of the FD communication object stored in the MCData message store
Up
7.13.3.1.42  MCData retrieve file to store locally response |R17|  p. 179
Table 7.13.3.1.42-1 describes the information flow for the MCData retrieve file to store locally response sent from the MCData message store to the message store client and the MCData server.
Information Element Status Description
MCData IDMThe identity of the MCData user
ResultMIndicates success or failure of MCData update FD object with file content request
Content referenceOURL reference to the file content stored in the MCData user's storage area
Up
7.13.3.1.43  Update notification channel request |R17|  p. 179
Table 7.13.3.1.43 describes the information flow for the update notification channel request sent from the message notification client to the MCData notification server.
Information element Status Description
MCData IDMThe identity of the MCData client initiating the request
Validity durationMHow long the notification channel will last (i.e. channel lifetime) as requested by the Message notification client.
Up
7.13.3.1.44  Update notification channel response |R17|  p. 179
Table 7.13.3.1.44 describes the information flow for the update notification channel response sent from the MCData notification server to the message notification client.
Information element Status Description
MCData IDMThe identity of the MCData client initiating the request
Validity durationMHow long the notification channel will last (i.e. channel lifetime) as granted by the MCData notification server
ResultMIndicates if the update is success or failure
Up
7.13.3.1.45  Update notification subscription request |R17|  p. 180
Table 7.13.3.1.45 describes the information flow for the update notification subscription request sent from the message store client to the MCData message store.
Information element Status Description
MCData IDMThe identity of the MCData client initiating the request
Validity durationMHow long the notification channel will last (i.e. notification subscription lifetime). This value should be the returned value in the update notification channel response
Up
7.13.3.1.46  Update notification subscription response |R17|  p. 180
Table 7.13.3.1.46 describes the information flow for the update notification subscription response sent from the MCData message store to the message store client.
Information element Status Description
MCData IDMThe identity of the MCData client initiating the request
Validity durationMHow long the notification channel will last (i.e. notification subscription lifetime) as granted by the MCData message store
ResultMIndicates if the update is success or failure
Up
7.13.3.1.47  Delete notification channel request |R17|  p. 180
Table 7.13.3.1.47 describes the information flow for the delete notification channel request sent from the message notification client to the MCData notification server.
Information element Status Description
MCData IDMThe identity of the MCData client initiating the request
Up
7.13.3.1.48  Delete notification channel response |R17|  p. 180
Table 7.13.3.1.48 describes the information flow for the delete notification channel response sent from the MCData notification server to the message notification client.
Information element Status Description
MCData IDMThe identity of the MCData client initiating the request
ResultMIndicates if deletion of notification channel is success or failure
Up
7.13.3.1.49  Delete notification subscription request |R17|  p. 181
Table 7.13.3.1.49 describes the information flow for the delete notification subscription request sent from the message store client to the MCData message store.
Information element Status Description
MCData IDMThe identity of the MCData client initiating the request
Up
7.13.3.1.50  Delete notification subscription response |R17|  p. 181
Table 7.13.3.1.50 describes the information flow for the delete notification subscription response sent from the MCData message store to the message store client.
Information element Status Description
MCData IDMThe identity of the MCData client initiating the request
ResultMIndicates if deletion of notification subscription is success or failure
Up
7.13.3.1.51  Notification message |R18|  p. 181
Table 7.13.3.1.51-1 describes the information flow for the notification message sent from the MCData message store to the MCData notification server and from the MCData notification server to the MCData notification client.
Information element Status Description
Event-dataMThe specific information carried in the notification message to inform the MCData client of changes to the MCData message store. (see NOTE)
NOTE:
MCData client uses the event information for actions such as updating its local message store or uses the event as a trigger for inquiring the Message store for desired changes.
Up

Up   Top   ToC