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.3.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…   7.17.7…   A…   B… 
7.13.4 Generic outgoing SDS procedure with MCData message store  7.13.5 Generic incoming SDS procedure with MCData message store  7.13.6 Interconnection and migration with MCData message store 
...

 

7.13.4  Generic outgoing SDS procedure with MCData message store  p. 203

7.13.4.1  General  p. 203

When a MCData user is supported with MCData message store all his outgoing communications shall be stored in his account in the MCData message store when he has requested. This generic SDS procedure applies to all procedures in subclause 7.4.2 when the MCData user requests to store the MCData communication.

7.13.4.2  Procedure  p. 203

The procedure in Figure 7.13.4.2-1 describes the generic SDS service where MCData message store is supported.
Pre-conditions:
  1. MCData user has an account created with 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.
Reproduction of 3GPP TS 23.282, Fig. 7.13.4.2-1: Generic outgoing SDS procedure with MCData message store
Figure 7.13.4.2-1: Generic outgoing SDS procedure with MCData message store
Up
Step 1.
MCData client initiates an MCData SDS service request; this service request can be a private or group communication.
Step 2.
MCData server stores the communication as an object to the MCData user account in the MCData message store.
Step 3.
MCData server checks and authorizes the service request and continue the service request toward the targeted recipient(s) as described in subclause 7.4.2.

7.13.5  Generic incoming SDS procedure with MCData message store  p. 204

7.13.5.1  General  p. 204

When a MCData user is supported with MCData message store all his incoming communications shall be stored in his account in the MCData message store when he has requested. This generic SDS procedure applies to all prcedures in subclause 7.4.2 when the MCData user requests to store the MCData communication.

7.13.5.2  Procedure  p. 204

The procedure in Figure 7.13.5.2-1 describes the generic SDS service where MCData message store is supported.
Pre-conditions:
  1. MCData user has an account created with 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.
Reproduction of 3GPP TS 23.282, Fig. 7.13.5.2-1: Generic incoming SDS procedure with MCData message store
Figure 7.13.5.2-1: Generic incoming SDS procedure with MCData message store
Up
Step 1.
The MCData server receives an incoming MCData SDS service request for the MCData user. This service request can be a response to an earlier service request sent by the MCData user or a new service request coming from any sender.
Step 2.
MCData server stores the communication as an object to the MCData user account in the MCData message store.
Step 3.
MCData server delivers the service request to MCData user as described in subclause 7.4.2.
Up

7.13.6  Interconnection and migration with MCData message store  p. 205

7.13.6.1  Interconnection  p. 205

There is no interconnection of MCData message stores, as there are no defined reference points providing connection between message stores in different MCData systems.

7.13.6.2  Migration  p. 205

A migrated MCData user may be provided with access to a local message store by the partner MCData system of the migrated MCData user. The MCData user is identified by the MCData ID used in the partner MCData system by that migrated MCData user in order to access the message store. There is no connection between this message store in the partner MCData system of the migrated MCData user and any message store that the MCData user has access to in the primary MCData system of that MCData user, and therefore access to a message store in the partner MCData system does not provide a means of accessing stored content in the primary MCData system of the migrated MCData user.
A migrated MCData user may be provided with a means of access to the message store in the primary MCData system of that MCData user, e.g. by providing the MCData user with a suitable APN and appropriate IP routing, or by use of the MCData IP connectivity service. Such access is outside the scope of the present document.
Up

Up   Top   ToC