Content for &nbsp; TS 23.282 &nbsp; Word version:&nbsp; 19.4.0

The message store client would like to retrieve a stored object from the MCData message store and initiates a MCData retrieve a stored object request toward the MCData message store. The unique object identifier of the stored object is included in the request.

Figure 7.13.3.3.2-1: Search stored objects

The MCData message store returns the stored object that is identified by the object identifier in the MCData retrieve a stored object response.

7.13.3.3 Search stored objects p. 182

7.13.3.3.1 General p. 182

The message store client can search stored objects in the MCData message store with certain criteria. This procedure allows the message store client to look for stored object(s) without knowing the object identifier(s) of the object. This procedure also allows the message store client to retrieve stored objects that are related to each other; such as all messages and files exchanged in a conversation.

7.13.3.3.2 Procedure p. 182

The procedure in Figure 7.13.3.3.2-1 describes the case when a message store client searches and retrieves relevant stored objects from the MCData message store.

Pre-conditions:

A successful authentication and authorization have been performed between the message store client and the MCData message store.

Reproduction of 3GPP TS 23.282, Fig. 7.13.3.3.2-1: Search stored objects

The message store client would like to retrieve stored objects that meet certain criteria (such as with the same Conversation identifier) and initiates a MCData search objects request toward the MCData message store. The search criteria are included in the request.

Figure 7.13.3.4.2-1: Update a stored object

The MCData message store looks up all stored objects that meet the search criteria and returns them in the MCData search objects response.

7.13.3.4 Update a stored object p. 183

7.13.3.4.1 General p. 183

The message store client can update the metadata of a stored object (such as mark a stored object as "flagged").

7.13.3.4.2 Procedure p. 183

The procedure in Figure 7.13.3.4.2-1 describes the case when a message store client updates metadata of a stored object in the MCData message store.

Pre-conditions:

A successful authentication and authorization have been performed between the message store client and the MCData message store.
The message store client knows the object identifier of the stored object.

Reproduction of 3GPP TS 23.282, Fig. 7.13.3.4.2-1: Update a stored object

The message store client would like to update the metadata of a stored object (such as "flagged") and initiates a MCData update a stored object request toward the MCData message store. The stored object's object identifier and the updated meta data are included in the request.

Figure 7.13.3.5.2-1: Delete a stored object

The MCData message store locates the stored object with the object identifier and updates its metadata as carried in the MCData update a stored object request and communicates the result in the MCData update a stored object response.

7.13.3.5 Delete a stored object p. 184

7.13.3.5.1 General p. 184

The message store client of an authorized user can delete a stored object in the MCData message store.

7.13.3.5.2 Procedure p. 184

The procedure in Figure 7.13.3.5.2-1 describes the case when a stored object in the MCData message store is deleted by the message store client of an authorized MCData user.

Pre-conditions:

A successful authentication and authorization have been performed between the message store client and the MCData message store.
The message store client knows the object identifierof the stored object.
The MCData user is authorized to delete the stored object.

Reproduction of 3GPP TS 23.282, Fig. 7.13.3.5.2-1: Delete a stored object

The message store client would like to delete a stored object in the MCData message store and initiates a MCData delete a stored object request toward the MCData message store. The stored object's object identifier is included in the request.

Figure 7.13.3.6.2-1: Synchronization

The MCData message store locates the stored object with the object identifier and permanently removes it from the MCData message store. It then communicates the result in the MCData delete a stored object response.

7.13.3.6 Synchronization p. 185

7.13.3.6.1 General p. 185

The message store client can synchronize its local message store with the MCData message store. Different level of synchronization shall be supported with a filter in the request.

7.13.3.6.2 Procedure p. 185

The procedure in Figure 7.13.3.6.2-1 describes the case when a message store client synchronizes its local message store with the MCData message store for a MCData user.

Pre-conditions:

A successful authentication and authorization have been performed between the message store client and the MCData message store.

Reproduction of 3GPP TS 23.282, Fig. 7.13.3.6.2-1: Synchronization

The message store client would like to synchronize its local message store with the MCData message store. It initiates the MCData synchronization request toward the MCData message store. The synchronization type and optional filter criteria are included in the request to indicate the type of synchronization (such as full synchronization, partial synchronization etc.) is requested.

Figure 7.13.3.7.2-1: Create a user account

The MCData message store returns all the stored objects, based on the synchronization filter criteria, to the message store client in the MCData synchronization response.

7.13.3.7 Create a user account p. 186

7.13.3.7.1 General p. 186

When the MCData server is ready to deposit an object into the MCData user's storage area in the MCData message store the MCData user's storage area (i.e. user account) needs to be created already. If the user account is not created, the MCData server shall create the user account (i.e. allocate the MCData user's storage area in the MCData message store) first and then deposit the subsequent MCData communications.

7.13.3.7.2 Procedure p. 186

The procedure in Figure 7.13.3.7.2-1 describes how the MCData server creates a user account (allocate MCData user storage area) in the MCData message store.

Pre-conditions:

A successful authentication and authorization has been performed between the MCData server and the MCData message store.
No storage area in the MCData message store has been allocated for the MCData user; i.e. no user account has been created.
The MCData server is authorized to create user accounts on the MCData message store.

Reproduction of 3GPP TS 23.282, Fig. 7.13.3.7.2-1: Create a user account

The MCData server would like to create a MCData user account in the MCData message store to store the MCData communication for that MCData user and initiates a MCData create a user account request toward the MCData message store. The MCData ID of the MCData user is included in the request.

Figure 7.13.3.8.2-1: Deposit an object

The MCData message store creates a user account (i.e. allocate dedicated and secured storage area) for the MCData user as specified in the request and communicates the result back to the MCData server in the MCData create a user account response.

7.13.3.8 Deposit an object p. 187

7.13.3.8.1 General p. 187

MCData server needs to store the communication information (i.e. an object) for a MCData user during an active MCData communication. If there is a file URL in the object for file distribution in the communication, the MCData server may instruct the MCData message store to retrieve a copy of the file to store locally in the MCData user's account.

7.13.3.8.2 Procedure p. 187

The procedure in Figure 7.13.3.8.2-1 describes how the MCData server deposit an object into the MCData message store during an active MCData communication.

Pre-conditions:

A successful authentication and authorization has been performed between the MCData server and the MCData message store.
The MCData user has been allocated a secured storage area in the MCData message store.
The configuration to store the MCData communication in MCData message store is enabled for the MCData user.
MCData user has requested to store his MCData communication and also store the distributed file content into his MCData message store account if the MCData communication is for file distribution through URL.

Reproduction of 3GPP TS 23.282, Fig. 7.13.3.8.2-1: Deposit an object

The MCData server would like to deposit a MCData communication information (i.e. object) to the MCData user's storage area in the MCData message store and initiates a MCData deposit an object request toward the MCData message store. The object is constructed by the MCData server and is included in the request. If the object is a message that carries a URL for file distribution, the MCData server may instruct the MCData message store to retrieve a copy of the file and store locally in the MCData user's account by setting the retrieve file indication information element to true.

The MCData message store deposits the object into the MCData user's storage area. If the retrieve file indication is set in the MCData deposit an object request the MCData message store retrieves the file URL from the stored object and fetches the file content from the MCData content server.

Figure 7.13.3.9.2-1: Copy a stored object

The MCData message store stores the file content into the MCData user's storage area and update the object with the URL referencing the file content stored in the MCData user's storage area.

Step 4.

The MCData message store communicates the result back to the MCData server in the MCData deposit an object response. The object identifier of the stored object is returned.

7.13.3.9 Copy a stored object p. 188

7.13.3.9.1 General p. 188

A stored object in the MCData message store can be copied to another location (i.e. folder) in the same MCData user account where there is no such object stored. After the successful object copy operation, the object will exist in both the original and destination locations. This operation is only meaningful when the user account in the MCData message store is structured in the folder hierarchy.

7.13.3.9.2 Procedure p. 188

The procedure in Figure 7.13.3.9.2-1 describes the case when a stored object is copied to a different location in the same MCData user account.

Pre-conditions:

The MCData user has an account in the MCData message store.
A successful authentication and authorization have been performed between the message store client and the MCData message store.
The message store client knows the object identifier of the stored object and the destination folder identifier.

Reproduction of 3GPP TS 23.282, Fig. 7.13.3.9.2-1: Copy a stored object

The message store client would like to copy a stored object in the MCData message store to a destination folder and initiates a MCData copy a stored object request toward the MCData message store. The uniqe identifier of the stored object and the destination folder are included in the request.

The MCData message store copies the object to the target location.

Figure 7.13.3.10.2-1: Move a stored object

The MCData message store returns the result of the request in the MCData copy a stored object response.

7.13.3.10 Move a stored object p. 189

7.13.3.10.1 General p. 189

A stored object in the MCData message store can be moved to a different location (i.e. folder) in the same MCData user account. After the successful object move operation the object will only exist in the new location. This operation is only meaningful when the user account in the MCData message store is structured in the folder hierarchy.

7.13.3.10.2 Procedure p. 189

The procedure in Figure 7.13.3.10.2-1 describes the case when a stored object is moved to a different location in the same MCData user account.

Pre-conditions:

The MCData user has an account in the MCData message store.
A successful authentication and authorization have been performed between the message store client and the MCData message store.
The message store client knows the object identifier of the stored object and the destination folder identifier.

Reproduction of 3GPP TS 23.282, Fig. 7.13.3.10.2-1: Move a stored object

The message store client would like to move a stored object in the MCData message store to a destination folder and initiates a MCData move a stored object request toward the MCData message store. The uniqe object identifier of the stored object and the destination folder are included in the request.

The MCData message store moves the object to the target location.

Figure 7.13.3.11.2-1: Create a new user folder

The MCData message store returns the result of the request in the MCData move a stored object response.

7.13.3.11 Folder create operation p. 190

7.13.3.11.1 General p. 190

A user can create a new folder in his user account n the MCData message store. This operation is only meaningful when the user account in the MCData message store is structured in the folder hierarchy.

7.13.3.11.2 Procedure p. 190

The procedure in Figure 7.13.3.11.2-1 describes the case when a MCData user creates a new folder in the MCData message store.

Pre-conditions:

The MCData user has an account in the MCData message store.
A successful authentication and authorization have been performed between the message store client and the MCData message store.

Reproduction of 3GPP TS 23.282, Fig. 7.13.3.11.2-1: Create a new user folder

The MCData user would like to create a new folder in his user account in the MCData message store, the message store client initiates a MCData create folder request toward the MCData message store. The parent folder identifier and the folder name are included in the request to indicate where the new folder will be created.

The MCData message store creates the user folder in the location specified in the request. If the folder name is provided in the request, the MCData message store creates the folder with the provided folder name. If the provided folder name has a conflict or no folder name is provided in the request, the MCData message store assigns a name for the new user folder.

Figure 7.13.3.12.2-1: Delete a user folder

The MCData message store returns the result in the MCData create folder response. The identifier of the new folder is returned in the response.

7.13.3.12 Folder delete operation p. 191

7.13.3.12.1 General p. 191

A user can delete an existing folder in his user account in the MCData message store. All the child folders and objects stored in that folder will be deleted. This operation is only meaningful when the user account in the MCData message store is structured in the folder hierarchy.

7.13.3.12.2 Procedure p. 191

The procedure in Figure 7.13.3.12.2-1 describes the case when a MCData user deletes an existing folder in the MCData message store.

Pre-conditions:

The MCData user has an account in the MCData message store.
A successful authentication and authorization have been performed between the message store client and the MCData message store.

Reproduction of 3GPP TS 23.282, Fig. 7.13.3.12.2-1: Delete a user folder

The MCData user would like to delete an existing folder in his user account in the MCData message store, the message store client initiates a MCData delete folder request toward the MCData message store. The folder identifier of the folder to be deleted is included in the request.

The MCData message store identifies the target folder and deletes it from the user account. All the child folders and objects stored in this folder are also deleted.

Figure 7.13.3.13.2-1: Copy a user folder

The MCData message store returns the result in the MCData delete folder response.

7.13.3.13 Folder copy operation p. 192

7.13.3.13.1 General p. 192

A user can copy an existing folder in his user account to a different location. All the child folders and objects stored in that folder will be copied to the new folder. The name of the new folder will be the same as the folder it copies from or the name provided in the request. This operation is only meaningful when the user account in the MCData message store is structured in the folder hierarchy.

7.13.3.13.2 Procedure p. 192

The procedure in Figure 7.13.3.13.2-1 describes the case when a MCData user copies an existing folder in the MCData message store.

Pre-conditions:

The MCData user has an account in the MCData message store.
A successful authentication and authorization have been performed between the message store client and the MCData message store.

Reproduction of 3GPP TS 23.282, Fig. 7.13.3.13.2-1: Copy a user folder

The MCData user would like to copy an existing folder in his user account in the MCData message store, the message store client initiates a MCData copy folder request toward the MCData message store. The folder identifiers of the source and destination folders and the new folder name are included in the request.

The MCData message store copy the source folder to the destination with the new folder name. If no new folder name is provided in the request, the source folder name will be used. All the child folders and objects stored in this folder are also copied to the new folder.