Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 23.282  Word version:  17.5.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.13  Operations on MCData message store |R16|

The MCData message store allows an MCData user to deposit his MCData communication information (i.e. messages or files) securely and permanently for later retrieval. During an active MCData communication, a message or a file with its associated metadata is deposited as an object in the MCData message store with an object identifier; this object identifier enabling a direct access to that object. The objects in the MCData message store are managed from both the MCData server and the message store client.
Each MCData user is allocated a dedicated and secured storage area (i.e. with a user account) in the MCData message store. All MCData communications of a MCData user can be stored in his dedicated storage area. The access to this secured storage area is possible only after successful authentication and authorization procedures. A message store client can create a local copy of the stored objects into the device by synchronizing with the MCData message store for the MCData user using the device.
Up

7.13.1  MCData message store structureWord‑p. 157
MCData message store supports a tree like architecture to securely store MCData communications for the MCData users. Figure 7.13.1 below illustrates the high-level structure of a MCData message store:
(not reproduced yet)
Figure 7.13.1: Message store structure
Up
As illustrated in Figure 7.13.1 all MCData user storage areas are accessed only through the common root. The authorized MCData user shall only have the access to the MCData user's storage area after the successful authentication and authorization procedures. A MCData user shall not be able to access objects stored for other MCData users.
The MCData user shall manage his stored objects using message store client through the MCData‑7 reference point. The MCData server shall use the MCData‑8 reference point to deposit MCData communication information, during an active MCData communication, into the designated MCData user's storage area in the MCData message store.
One way to manage user stored objects is using folder hierarchy structure like the popular email system today. Annex D provides a simple example of how it will look like in deployment. When the user account is created in the MCData message store, a default folder (such as Inbox) is also created to capture all the objects during an active communication. To group relevant stored objects together and provide easier navigation interactively, a MCData user can create folders in his user account. Each folder is identified by its unique folder identifier that is composed with the location of the folder and the name of the folder. A folder may have child folders to further group the stored objects in more meaningful ways. For example, the folder identifier of the default Inbox folder is /MCDatamessagestore/MCDatauser1/Inbox. The folder identifier /MCDatamessagestore/MCDatauser1/Squad1/20190225 points to a folder named 20190225 which is a child folder of Squad1 folder in the MCData user1 user account.
Up

7.13.2  Authentication and authorization

The MCData message store shall authenticate the credential of MCData server or the authorized MCData user before authorizing access to the MCData user's storage area. The success of authentication and authorization shall allow access to that MCData user's storage area only.

7.13.3  Manage MCData message storeWord‑p. 158

7.13.3.1  Information flows for managing MCData message store

7.13.3.1.1  MCData retrieve a stored object request
Table 7.13.3.1.1-1 describes the information flow for the MCData retrieve a stored object request sent from the message store client to the MCData message store.
Information Element Status Description
MCData IDMThe identity of the MCData user
Object identifierMThe object identifier of the object stored in the MCData message store
Up
7.13.3.1.2  MCData retrieve a stored object response
Table 7.13.3.1.2-1 describes the information flow for the MCData retrieve a stored object response sent from the MCData message store to the message store client.
Information Element Status Description
MCData IDMThe identity of the MCData user
Stored objectMThe stored object identified by the object identifier in the request. This information element shall be returned as empty when there is no stored object can be identified by the object identifier in the request
Up
7.13.3.1.3  MCData search stored objects request
Table 7.13.3.1.3-1 describes the information flow for the MCData search stored objects 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 stored object can be the search criteria. Linking multiple parts of a stored object as the search criteria is possible
Up
7.13.3.1.4  MCData search stored objects response
Table 7.13.3.1.4-1 describes the information flow for the MCData search stored objects response sent from the MCData message store to the message store client.
Information Element Status Description
MCData IDMThe identity of the MCData user
Stored object(s)MThe stored object(s) that meets the search criteria. This information element shall be returned as empty when there is no stored object can be identified by the search criteria in the request
Up
7.13.3.1.5  MCData update a stored object requestWord‑p. 159
Table 7.13.3.1.5-1 describes the information flow for the MCData update a stored object request sent from the message store client to the MCData message store.
Information Element Status Description
MCData IDMThe identity of the MCData user
Object identifierMThe object identifier of the object stored in the MCData message store
MetadataMThe metadata that will be updated
Up
7.13.3.1.6  MCData update a stored object response
Table 7.13.3.1.6-1 describes the information flow for the MCData update a stored object response sent from the MCData message store to the message store client.
Information Element Status Description
MCData IDMThe identity of the MCData user storage area in the MCData message store
ResultMThe result if the update is success or failure
Up
7.13.3.1.7  MCData delete a stored object request
Table 7.13.3.1.7-1 describes the information flow for the MCData delete a stored object request sent from the message store client to the MCData message store.
Information Element Status Description
MCData IDMThe identity of the MCData user
Object identifierMThe object identifier of the object stored in the MCData message store
Up
7.13.3.1.8  MCData delete a stored object response
Table 7.13.3.1.8-1 describes the information flow for the MCData delete a stored object response sent from the MCData message store to the message store client.
Information Element Status Description
MCData IDMThe identity of the MCData user storage area in the MCData message store
ResultMThe result if the delete is success or failure
Up
7.13.3.1.9  MCData synchronization request
Table 7.13.3.1.9-1 describes the information flow for the MCData synchronization request sent from the message store client to the MCData message store.
Information Element Status Description
MCData IDMThe identity of the MCData user
Synchronization typeMIndicates the type of synchronization is requested. It can be a full or partial synchronization
Filter criteria (see NOTE)OThe filter criteria indicate what kind of stored objects needs to be synchronized to the device local message store
Up
7.13.3.1.10  MCData synchronization responseWord‑p. 160
Table 7.13.3.1.10-1 describes the information flow for the MCData synchronization response sent from the MCData message store to the message store client.
Information Element Status Description
MCData IDMThe identity of the MCData user
Stored objectsMThe stored objects that need to be synchronized with the device local message store. Empty information element means no stored objects need to be synchronized
Up
7.13.3.1.11  MCData create a user account request
Table 7.13.3.1.11-1 describes the information flow for the MCData create a user account request sent from the MCData server to the MCData message store.
Information Element Status Description
MCData IDMThe identity of the MCData user
Up
7.13.3.1.12  MCData create a user account response
Table 7.13.3.1.12-1 describes the information flow for the MCData create a user account response sent from the MCData message store to the MCData server.
Information Element Status Description
MCData IDMThe identity of the MCData user
ResultMThe result if the account creation is success or failure
Up
7.13.3.1.13  MCData deposit an object request
Table 7.13.3.1.13-1 describes the information flow for the MCData deposit an object request sent from the MCData server to the MCData message store.
Information Element Status Description
MCData IDMThe identity of the MCData user
Retrieve file indicationOFlag to instruct the MCData message store to retrieve the file to locally store in the MCData user's account
ObjectMThe object needs to be stored
Up
7.13.3.1.14  MCData deposit an object responseWord‑p. 161
Table 7.13.3.1.14-1 describes the information flow for the MCData deposit an object response sent from the MCData message store to the MCData server.
Information Element Status Description
MCData IDMThe identity of the MCData user
Object IdentifierMThe object identifier that will be used to retrieve this object in the MCData message store directly. If this information element is empty it means the object is not stored
Up
7.13.3.1.15  MCData copy a stored object request
Table 7.13.3.1.15-1 describes the information flow for the MCData copy a stored object request sent from the message store client to the MCData message store.
Information Element Status Description
MCData IDMThe identity of the MCData user
Object identifierMThe object identifier of the object stored in the MCData message store
Destination folder identifierMIndicates where the object will be copied to
Up
7.13.3.1.16  MCData copy a stored object response
Table 7.13.3.1.16-1 describes the information flow for the MCData copy a stored object 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.17  MCData move a stored object request
Table 7.13.3.1.17-1 describes the information flow for the MCData move a stored object request sent from the message store client to the MCData message store.
Information Element Status Description
MCData IDMThe identity of the MCData user
Object identifierMThe object identifier of the object stored in the MCData message store
Destination folder identifierMIndicates where the object will be moved to
Up
7.13.3.1.18  MCData move a stored object response
Table 7.13.3.1.18-1 describes the information flow for the MCData move a stored object 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


Up   Top   ToC