Content for  TS 23.282  Word version:  19.3.0

A MCData user, with an account in the MCData message store, involved in an off-network communication will store the communication as objects in a specific folder in the local message store on his UE. These objects can be uploaded to his user account in the MCData message store once he is connected to the network with MC data service again.

The procedure in Figure 7.13.3.16.2-1 describes the case when a message store client uploads new objects in its local message store to the MCData message store for a MCData user. Pre-conditions:

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

MCData message store will send a notification to the MCData user when there are new objects in the MCData message store that need to be synchronized with his local message store.

The procedure in Figure 7.13.3.17.2-1 describes how the MCData message store notifies the message store client that there are new objects in the MCData message store need to be synchronized. Pre-conditions:

1. The MCData user has an account with the MCData message store.
2. A successful authentication and authorization have been performed between the message store client and the MCData message store.
3. The Message store client is in an ongoing session with the MCData message store.

The procedure in Figure 7.13.3.17.3-1 describes how the MCData message store notifies the message notification client, using a MCData notification server, that there are new objects in the MCData message store needing to be synchronized. This procedure uses a web base notification mechanism in wide deployment today. The Message notification client requests the notification service from the MCData notification server and the MCData notification server returns with two URLs; one used by the service client to inform the service server where to send notification messages and the other one to use by the service client to PULL notification messages from the MCData notification server. Pre-conditions:

1. The MCData user has an account with the MCData message store.
2. A successful authentication and authorization have been performed between the message store client and the MCData message store.
3. The Message store client doesn't have an ongoing session with the MCData message store.
4. The trust relationship between the MCData notification server and the MCData message store has been established.
5. The MCData notification server has a trust relationship and connection with the PUSH Enabler server.

The procedure in Figure 7.13.3.17.3-2 describes how the message notification client updates the validity duration of a notification channel and subscription to avoid its expiration, i.e. to extend its lifetime. Pre-conditions:

1. A notification channel has already been requested and established between the message notification client and MCData notification server.
2. The message store client has a successful notification subscription with the MCData message store.
3. The validity duration of the notification channel is about to expire.

The procedure in Figure 7.13.3.17.3-3 describes how the message notification client delete a notification channel and subscription that is no longer needed. Pre-conditions:

1. A notification channel has already been requested and established between the message notification client and MCData notification server.
2. The message store client has a successful notification subscription with the MCData message store.
3. The MCData user no longer wants to receive notifications from the MCData message store.

The message store client can search stored folder(s) with certain criteria. This procedure allows the message store client to look for folder(s) that meet certain criteria such as when the folder is created. This procedure provides the message store client the ability to locate a specific folder(s) matching the search criteria to perform further operations.

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

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

An MCData user can retrieve the content of a folder in the user's message store account. This procedure allows the message store client to retrieve the specific folder's content from the MCData message store.

The procedure in Figure 7.13.3.19.2-1 describes the case when a message store client retrieves the content of a specific folder in the MCData message store. Pre-conditions:

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

An MCData user can store the received file content in his message store account. This procedure allows the message store client to request the MCData message store to retrieve the file from the media storage function of MCData content server and store into MCData message store account of the user.

The procedure in Figure 7.13.3.20.3-1 describes the case when a message store client requests the MCData message store to retrieve the file from media storage function of MCData content server and store into MCData message store account of the user. Pre-conditions:

1. A successful authentication and authorization have been performed between the message store client and the MCData message store.
2. The configuration to store the MCData communication in MCData message store is enabled for the MCData user.
3. MCData user has requested to store his MCData communication.
4. The message store client knows the object identifier of the stored object.