hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.35 Subscribe for notification request
|
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.
Table 7.13.3.1.35-1: Subscribe for notification request
Information element
Status
Description
MCData ID
M
The identity of the MCData client initiating the request
Callback URL
M
The URL where to send the notification message
Validity duration
M
How long the subscription to notification will last (i.e. subscription lifetime); this value shall be the returned value in the create notification channel response
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.36 Subscribe for notification response
|
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.
Table 7.13.3.1.36-1: Subscribe for notification response
Information element
Status
Description
MCData ID
M
The identity of the MCData client initiating the request
Validity duration
M
How long the subscription of notification will last (i.e. subscription lifetime) as granted by the server
Result
M
Indicates if the subscription is success or failure
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.37 MCData search folder request
|
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.
Table 7.13.3.1.37-1: MCData search folder request
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Search criteria
M
Any 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
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.38 MCData search folder response
|
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.
Table 7.13.3.1.38-1: MCData search folder response
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Folder identifier(s)
M
The folder(s) that meets the search criteria. This information element shall be returned as empty if there is no folder matching the search criteria
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.39 MCData retrieve folder content request
|
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.
Table 7.13.3.1.39-1: MCData retrieve folder content request
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Folder identifier
M
The identifier of the folder its content is requested to be returned
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.40 MCData retrieve folder content response
|
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.
Table 7.13.3.1.40-1: MCData retrieve folder content response
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Folder content
M
The 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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.41 MCData retrieve file to store locally request
|
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.
Table 7.13.3.1.41-1: MCData retrieve file to store locally request
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Object identifier
M
The object identifier of the FD communication object stored in the MCData message store
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.42 MCData retrieve file to store locally response
|
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.
Table 7.13.3.1.42-1: MCData retrieve file to store locally response
Information element
Status
Description
MCData ID
M
The identity of the MCData user
Result
M
Indicates success or failure of MCData update FD object with file content request
Content reference
O
URL reference to the file content stored in the MCData user's storage area
NOTE: Content reference shall be present if the content stored into the MCData user's storage area successfully.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.43 Update notification channel request
|
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.
Table 7.13.3.1.43: Update notification channel request
Information element
Status
Description
MCData ID
M
The identity of the MCData client initiating the request
Validity duration
M
How long the notification channel will last (i.e. channel lifetime) as requested by the Message notification client.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.44 Update notification channel response
|
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.
Table 7.13.3.1.44: Update notification channel response
Information element
Status
Description
MCData ID
M
The identity of the MCData client initiating the request
Validity duration
M
How long the notification channel will last (i.e. channel lifetime) as granted by the MCData notification server
Result
M
Indicates if the update is success or failure
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.45 Update notification subscription request
|
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.
Table 7.13.3.1.45: Update notification subscription request
Information element
Status
Description
MCData ID
M
The identity of the MCData client initiating the request
Validity duration
M
How long the notification channel will last (i.e. notification subscription lifetime). This value should be the returned value in the update notification channel response
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.46 Update notification subscription response
|
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.
Table 7.13.3.1.46: Update notification subscription response
Information element
Status
Description
MCData ID
M
The identity of the MCData client initiating the request
Validity duration
M
How long the notification channel will last (i.e. notification subscription lifetime) as granted by the MCData message store
Result
M
Indicates if the update is success or failure
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.47 Delete notification channel request
|
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.
Table 7.13.3.1.47: Delete notification channel request
Information element
Status
Description
MCData ID
M
The identity of the MCData client initiating the request
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.48 Delete notification channel response
|
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.
Table 7.13.3.1.48: Delete notification channel response
Information element
Status
Description
MCData ID
M
The identity of the MCData client initiating the request
Result
M
Indicates if deletion of notification channel is success or failure
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.49 Delete notification subscription request
|
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.
Table 7.13.3.1.49: Delete notification subscription request
Information element
Status
Description
MCData ID
M
The identity of the MCData client initiating the request
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.50 Delete notification subscription response
|
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.
Table 7.13.3.1.50: Delete notification subscription response
Information element
Status
Description
MCData ID
M
The identity of the MCData client initiating the request
Result
M
Indicates if deletion of notification subscription is success or failure
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.1.51 Notification message
|
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.
Table 7.13.3.1.51-1: Notification message
Information element
Status
Description
Event-data
M
The 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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.2 Retrieve a stored object
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.2.1 General
|
A stored object can be retrieved from the MCData message store with the known object identifier that is generated by the MCData message store when the object was deposited.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.2.2 Procedure
|
The procedure in figure 7.13.3.2.2-1 describes the case when a message store client retrieves a stored object from the MCData message store using the known object identifier.
Pre-conditions:
1. A successful authentication and authorization have been performed between the message store client and the MCData message store.
2. The message store client knows the object identifier of the stored object.
Figure 7.13.3.2.2-1: Retrieve a stored object
1. 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.
2. The MCData message store returns the stored object that is identified by the object identifier in the MCData retrieve a stored object response.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.3 Search stored objects
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.3.1 General
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.3.2 Procedure
|
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:
1. A successful authentication and authorization have been performed between the message store client and the MCData message store.
Figure 7.13.3.3.2-1: Search stored objects
1. 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.
2. The MCData message store looks up all stored objects that meet the search criteria and returns them in the MCData search objects response.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.4 Update a stored object
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.4.1 General
|
The message store client can update the metadata of a stored object (such as mark a stored object as "flagged").
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.4.2 Procedure
|
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:
1. A successful authentication and authorization have been performed between the message store client and the MCData message store.
2. The message store client knows the object identifier of the stored object.
Figure 7.13.3.4.2-1: Update a stored object
1. 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.
2. 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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.5 Delete a stored object
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.5.1 General
|
The message store client of an authorized user can delete a stored object in the MCData message store.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.5.2 Procedure
|
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:
1. A successful authentication and authorization have been performed between the message store client and the MCData message store.
2. The message store client knows the object identifierof the stored object.
3. The MCData user is authorized to delete the stored object.
Figure 7.13.3.5.2-1: Delete a stored object
1. 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.
2. 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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.6 Synchronization
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.6.1 General
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.6.2 Procedure
|
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:
1. A successful authentication and authorization have been performed between the message store client and the MCData message store.
Figure 7.13.3.6.2-1: Synchronization
1. 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.
2. 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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.7 Create a user account
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.7.1 General
|
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.
NOTE: Another possible way to create a user account on the MCData message store is through service provisioning which is out of the scope of the present document.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.7.2 Procedure
|
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:
1. A successful authentication and authorization has been performed between the MCData server and the MCData message store.
2. No storage area in the MCData message store has been allocated for the MCData user; i.e. no user account has been created.
3. The MCData server is authorized to create user accounts on the MCData message store.
Figure 7.13.3.7.2-1: Create a user account
1. 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.
2. 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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.8 Deposit an object
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.8.1 General
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.8.2 Procedure
|
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:
1. A successful authentication and authorization has been performed between the MCData server and the MCData message store.
2. The MCData user has been allocated a secured storage area in the MCData message store.
3. The configuration to store the MCData communication in MCData message store is enabled for the MCData user.
4. 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.
Figure 7.13.3.8.2-1: Deposit an object
1. 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.
2. 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.
3. 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.
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.9 Copy a stored object
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.9.1 General
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.9.2 Procedure
|
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:
1. The MCData user has an account in 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 knows the object identifier of the stored object and the destination folder identifier.
Figure 7.13.3.9.2-1: Copy a stored object
1. 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.
2. The MCData message store copies the object to the target location.
3. The MCData message store returns the result of the request in the MCData copy a stored object response.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.10 Move a stored object
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.10.1 General
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.10.2 Procedure
|
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:
1. The MCData user has an account in 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 knows the object identifier of the stored object and the destination folder identifier.
Figure 7.13.3.10.2-1: Move a stored object
1. 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.
2. The MCData message store moves the object to the target location.
3. The MCData message store returns the result of the request in the MCData move a stored object response.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.11 Folder create operation
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.11.1 General
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.11.2 Procedure
|
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:
1. The MCData user has an account in the MCData message store.
2. A successful authentication and authorization have been performed between the message store client and the MCData message store.
Figure 7.13.3.11.2-1: Create a new user folder
1. 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.
2. 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.
3. The MCData message store returns the result in the MCData create folder response. The identifier of the new folder is returned in the response.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.12 Folder delete operation
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.12.1 General
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.12.2 Procedure
|
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:
1. The MCData user has an account in the MCData message store.
2. A successful authentication and authorization have been performed between the message store client and the MCData message store.
Figure 7.13.3.12.2-1: Delete a user folder
1. 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.
2. 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.
3. The MCData message store returns the result in the MCData delete folder response.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.13 Folder copy operation
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.13.1 General
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.13.2 Procedure
|
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:
1. The MCData user has an account in the MCData message store.
2. A successful authentication and authorization have been performed between the message store client and the MCData message store.
Figure 7.13.3.13.2-1: Copy a user folder
1. 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.
2. 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.
3. The MCData message store returns the result in the MCData copy folder response. The identifier of the new folder is returned in the response.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.14 Folder move operation
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.14.1 General
|
A user can move an existing folder in his user account to a different location. All the child folders and objects stored in that folder will be moved to the new folder. The name of the new folder will be the same as the folder it moves 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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.14.2 Procedure
|
The procedure in figure 7.13.3.14.2-1 describes the case when a MCData user moves an existing folder in the MCData message store.
Pre-conditions:
1. The MCData user has an account in the MCData message store.
2. A successful authentication and authorization have been performed between the message store client and the MCData message store.
Figure 7.13.3.14.2-1: Move a user folder
1. The MCData user would like to move an existing folder in his user account in the MCData message store to a new location, the message store client initiates a MCData move 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.
2. The MCData message store move 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 moved to the new folder.
3. The MCData message store returns the result in the MCData move folder response. The identifier of the new folder is returned in the response.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.15 Folder list operation
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.15.1 General
|
A user can view the folder structure in his user account in the MCData message store. The target folder hierarchy structure will be presented to the user; i.e. the folder and all its child folders. This operation is only meaningful when the user account in the MCData message store is structured in the folder hierarchy.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.15.2 Procedure
|
The procedure in figure 7.13.3.15.2-1 describes the case when a MCData user lists an existing folder's hierarchy structure in the MCData message store.
Pre-conditions:
1. The MCData user has an account in the MCData message store.
2. A successful authentication and authorization have been performed between the message store client and the MCData message store.
Figure 7.13.3.15.2-1: Folder list operation
1. The MCData user would like to view the folder strcture of a targeted folder in his user account in the MCData message store, the message store client initiates a MCData list folder request toward the MCData message store. The folder identifier of the target folder is included in the request.
2. The MCData message store retrieves the target folder and all its child folders. If no target folder name is provided in the request, the MCData message store will use the root folder as the target folder.
3. The MCData message store returns the result in the MCData list folder response.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.16 Upload objects
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.16.1 General
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.16.2 Procedure
|
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.
Figure 7.13.3.16.2-1: Upload objects
1. The message store client would like to upload new objecs in its local message store to the MCData message store. It initiates the MCData upload objects request toward the MCData message store. The uploaded objects and the target folder identifier where the objects will be stored are included in the request.
2. The MCData message store stores the uploaded objects to the target folder. If the target folder doesn't exist, the MCData message store will create it.
3. The MCData message store returns the result in the MCData upload objects response.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.17 Notify client to synchronize
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.17.1 General
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.17.2 Procedure using in-band connection
|
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.
Figure 7.13.3.17.2-1: Notify client to synchronize using in-band connection
1. The MCData message store receives new objects for the MCData user and decides to send a notification to inform the MCData user.
NOTE: How MCData message store determines if a notification needs to be sent to the message store client is out of scope of the present specification.
2. The MCData message store sends the MCData synchronization notification to the message store client.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.17.3 Procedure using MCData notification server
|
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.
Figure 7.13.3.17.3-1: Notify client to synchronize through MCData notification server
1. The Message notification client wants to create notification channels (i.e. endpoint URLs) to be used by the MCData message store to send notification messages and sends a Create notification channel request to the MCData notification server. The desired validity duration for the channels to be used and the notification channel type (PUSH or PULL) are included in the request.
2. The MCData notification server authenticates the Message notification client and authorizes its request.
3. The MCData notification server sends the Message notification client the Create notification channel response with the endpoint URLs that will be used by the MCData message store to send the notification messages and the Message notification client to receive the notification messages. The MCData notification server also includes what is the valid duration for these endpoint URLs to be used in the response.
4. If the notification type is PULL method, the message notification client sends the Open notification channel to the MCData notification server to start receiving the notification message. For certain PUSH method notification type (such as WebSockets) the message notification client requests the MCData notification server to start the PUSH notification service with its specific protocol that is outside the scope of this specification.
5. The message store client sends the Subscribe for notification request to the MCData message store asking to be notified if there are changes to its message store account. The callback URL returned from the MCData notification server in step 3 is included in the request for the MCData message store to use to send notification messages.
6. The MCData message store sends the Subscribe for notification response to the message store client to acknowledge the request.
7. The MCData user's message store account has changed and the MCData message store generates a notification message.
8. Using the callback URL, the MCData message store sends the notification message to the MCData notification server.
9. If the delivery method is PULL, the MCData notification server sends the notification message to the message notification client over the opened notification channel. If the delivery method is PUSH, the MCData notification server sends the notification message to the PUSH Enabler server (not shown in the figure) to deliver to the message notification client.
NOTE: The PUSH Enabler server is implementation specific and outside the scope of this specification.
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.
Figure 7.13.3.17.3-2: Update a notification channel
1. The message notification client sends the Update notification channel request, including the desired new validity duration, to the MCData notification server.
2. The MCData notification server grants the request and sends the Update notification channel response to the message notification client. The new validity duration is included in the response.
3. The message store client sends the Update notification subscription request to the MCData message store with the new validity duration received from the MCData notification server in step 2.
4. The MCData message store sends the Update notification subscription response to the message store client and confirms the new validity duration.
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.
Figure 7.13.3.17.3-3: Delete a notification channel
1. The message store client decides to stop receiving notifications from the MCData message store and sends the Delete notification subscription request to the MCData message store.
2. The MCData message store acknowledges the request and sends the Delete notification subscription response to the message store client.
3. The message notification client sends the Delete notification channel request to the MCData notification server.
4. The MCData notification server acknowledges the request and sends the Delete notification channel response to the message notification client.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.18 Search folder
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.18.1 General
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.18.2 Procedure
|
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.
Figure 7.13.3.18.2-1: Search folder
1. The message store client wants to retrieve message store folder(s) that meet certain criteria (such as when the folder(s) was created, certain keywords etc.) and initiates a MCData search folder request toward the MCData message store. The search criteria are included in the request.
2. The MCData message store identifies all folders that match the search criteria and returns them in the MCData search folder response.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.19 Retrieve folder content
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.19.1 General
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.19.2 Procedure
|
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.
Figure 7.13.3.19.2-1: retrieve folder content
1. The message store client wants to retrieve the content of a specific folder and initiates a MCData retrieve folder content request toward the MCData message store. The requested folder identifier is included in the request.
2. The MCData message store locates the requested folder and returns the content of the folder (e.g. objects and subfolders) in the MCData retrieve folder content response.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.20 Store file contents distributed using HTTP
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.20.1 General
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.3.20.2 Procedure for storing the file – receiver side
|
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.
Figure 7.13.3.20.3-1: store file contents distributed using HTTP – receiver side
1. The Message store client initiates MCData retrieve file to store locally request towards the MCData message store. The object identifier corresponding to the stored MCData FD communication is included in the request.
2. The MCData message store retrieves the file URL from the stored object and fetches the file content from the MCData content server.
3. 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.
4. The MCData message store provides the MCData retrieve file to store locally response to the message store client. This response includes the URL of the file being stored in the MCData user's storage area.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.4 Generic outgoing SDS procedure with MCData message store
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.4.1 General
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.4.2 Procedure
|
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.
Figure 7.13.4.2-1 Generic outgoing SDS procedure with MCData message store
1. MCData client initiates an MCData SDS service request; this service request can be a private or group communication.
2. MCData server checks and authorizes the service request and if authorized stores the communication as an object to the MCData user account in the MCData message store.
3. MCData server continues the service request toward the targeted recipient(s) as described in subclause 7.4.2.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.5 Generic incoming SDS procedure with MCData message store
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.5.1 General
|
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 procedures in subclause 7.4.2 when the MCData user requests to store the MCData communication.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.5.2 Procedure
|
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.
3. 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.
Figure 7.13.5.2-1 Generic incoming SDS procedure with MCData message store
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.
2. MCData server checks and authorizes the service request and if authorized stores the communication as an object to the MCData user account in the MCData message store.
3. MCData server delivers the service request to MCData user as described in subclause 7.4.2.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.6 Interconnection and migration with MCData message store
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.6.1 Interconnection
|
There is no interconnection of MCData message stores, as there are no defined reference points providing connection between message stores in different MCData systems.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.13.6.2 Migration
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.14 IP connectivity
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.14.1 General
|
IP data shall be exchanged between two or more data hosts. The MCData client as the link between data host and MC system enables the exchange of IP Data. For addressing the corresponding MCData users either MCData ID or the functional alias can be used independently of each other. The MCData server provides the mechanisms to establish the association between MCData ID and corresponding functional alias.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.14.2 IP connectivity for on-network
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.14.2.1 Information flows for IP connectivity
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.14.2.1.1 MCData IPcon point-to-point request
|
Table 7.14.2.1.1-1 describes the information flow of the MCData IPcon point-to-point request sent from the MCData client to the MCData server.
Table 7.14.2.1.1-1: MCData IPcon point-to-point request (MCData client to MCData server)
Information element
Status
Description
MCData ID
M
The MCData identity of the originator MCData user;
Functional alias
O
The associated functional alias of the originator MCData user;
MCData ID
O
(NOTE 2)
The MCData identity of the target MCData client IP connectivity is requested.
Functional alias
O
(NOTE 2)
The functional alias of the target MCData client.
SDP offer
M
Offered media parameters describing the requested characteristics of the IP tunnel between the MCData UEs.
Requested Priority
(NOTE 3)
O
Application priority level requested for this communication.
Location Information
O
(NOTE 1)
Actual location information of the originating MCData user;
Time Limit
O
Proposed time limit of the requested IP connectivity (1min- infinite);
Establishment reason
O
IP connectivity establishment reason
Application data (see NOTE 4)
O
Application specific information that is communicated to the recipient
NOTE 1: This information contains the latest available location information of the requesting MCData user that may be different to the latest available location information in the MC system.
NOTE 2: At least one identity shall be present. If both are present the MCData ID shall be used to route the request and the functional alias is just for information.
NOTE 3: The predefined priority of the MC service user is applied by the MCData server if the requested priority is not present or not accepted by the MCData server.
NOTE 4: How the MCData client gets the content of this information element is outside the scope of the present document.
Table 7.14.2.1.1-2: MCData IPcon point-to-point request (MCData server to MCData client)
Information element
Status
Description
MCData ID
M
The MCData identity of the originator MCData user;
MCData ID
M
The MCData identity of the target MCData client IP connectivity is requested.
SDP offer
M
Offered media parameters describing the requested characteristics of the IP tunnel between the MCData UEs.
Location Information
O
(NOTE 1)
Actual location information of the originating MCData user;
Time Limit
O
Proposed time limit of the requested IP connectivity (1min- infinite);
Establishment reason
O
IP connectivity establishment reason
Application data (see NOTE 2)
O
Application specific information that is communicated to the recipient
NOTE 1: This information contains the latest available location information of the requesting MCData user.
NOTE 2: How the MCData client gets the content of this information element is outside the scope of the present document.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.14.2.1.2 MCData IPcon point-to-point response
|
Table 7.14.2.1.2-1 describes the information content of the MCData IPcon point-to-point response as answer to MCData IPcon point-to-point request.
Table 7.14.2.1.2-1: MCData IPcon point-to-point response
Information element
Status
Description
MCData ID
M
The MCData identity of the targeted MCData user.
MCData ID
M
The MCData identity of the requesting MCData user.
SDP
O
Media parameters selected. This shall be present if the IP connectivity establishment result is successful.
Time Limit
O
Negotiated time (1 min – infinite)
IP connectivity status
M
IP connectivity establishment result
Application data (see NOTE)
O
Application specific information that is communicated to the recipient
NOTE: How the MCData client gets the content of this information element is outside the scope of the present document.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.14.2.1.3 MCData remote IPcon point-to-point request
|
Table 7.14.2.1.3-1 describes the information flow of the MCData remote IPcon point-to-point request sent from the remote MCData client to the MCData server and from the MCData server to the asked MCData client.
Table 7.14.2.1.3-1: MCData remote IPcon point-to-point request
Information element
Status
Description
MCData ID remote
M
The MCData identity of the remote MCData client that requests another MCData user to establish an IP connectivity point-to-point session.
Functional alias remote
O
The associated functional alias of the remote MCData user.
MCData ID asked
M
The MCData identity of the MCData client that is required to establish an IP connectivity point-to-point session.
Functional alias asked
O
The functional alias associated with the MCData identity of the MCData client that is required to establish an IP connectivity point-to-point session.
MCData ID targeted (NOTE 1)
O
The MCData identity of the MCData client that is the target of the requested IP connectivity point-to-point session.
Functional alias targeted (NOTE 1)
O
The functional alias associated with the MC MCData identity of the MCData client that is the target of the requested IP connectivity point-to-point session.
Requested Priority
(NOTE 2)
O
Application priority level requested for this call.
Time Limit
O
Proposed time limit of the requested IP connectivity (1min- infinite).
Establishment reason
O
IP connectivity establishment reason
NOTE 1: At least one identity shall be present. If both are present the MCData ID shall be used to route the request and the functional alias is just for information.
NOTE 2: The predefined priority of the MC service user is applied by the MCData server if the requested priority is not present or not accepted by the MCData server.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.14.2.1.4 MCData remote IPcon point-to-point response
|
Table 7.14.2.1.4-1 describes the information content of the MCData remote IPcon point-to-point response as answer to MCData remote IPcon point-to-point request.
Table 7.14.2.1.4-1: MCData remote IPcon point-to-point response
Information element
Status
Description
MCData ID asked
M
The MCData identity of the asked MCData client in the request message;
MCData ID targeted
M
The MCData identity of the targeted MCData client in the request message;
IP connectivity status
M
The status information about the IP connectivity session to the remote MCData user.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.14.2.1.5 MCData remote IPcon point-to-point tear down request
|
Table 7.14.2.1.5-1 describes the information flow of the MCData remote IPcon point-to-point tear down request sent from the remote MCData client to the MCData server and from the MCData server to the asked MCData client.
Table 7.14.2.1.5-1: MCData remote IPcon point-to-point tear down request
Information element
Status
Description
MCData ID remote
M
The MCData identity of the remote MCData client that requests another MCData user to tear down an IP connectivity point-to-point session.
Functional alias remote
O
The associated functional alias of the remote MCData user;
MCData ID asked
M
The MCData identity of the MCData client that is asked to tear down an IP connectivity point-to-point session.
MCData ID targeted
M
The MCData identity of the MCData client that is the target to be tear down from the IP connectivity point-to-point session.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.14.2.1.6 MCData remote IPcon point-to-point tear down response
|
Table 7.14.2.1.6-1 describes the information content of the MCData remote IPcon point-to-point tear down response as answer to MCData remote IPcon point-to-point tear down request.
Table 7.14.2.1.6-1: MCData remote IPcon point-to-point tear down response
Information element
Status
Description
MCData ID asked
M
The MCData identity of the asked MCData client in the request message.
MCData ID targeted
M
The MCData identity of the targeted MCData client in the request message.
Tear down status
M
The status information about the IP connectivity tear down status information
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.14.2.1.7 MCData remote IPcon point-to-point application priority change request
|
Table 7.14.2.1.7-1 describes the information flow of the MCData remote IPcon point-to-point application priority change request sent from the remote MCData client to the MCData server and from the MCData server to the asked MCData client.
Table 7.14.2.1.7-1: MCData remote IPcon point-to-point application priority change request
Information element
Status
Description
MCData ID remote
M
The MCData identity of the remote MCData client that requests to change the application priority of an IP connectivity point-to-point session.
Functional alias remote
O
The associated functional alias of the remote MCData user;
MCData ID
M
The first MCData identity of the MCData client that is involved in the IP connectivity point-to-point session.
MCData ID
M
The second MCData identity of the MCData client that is involved in the IP connectivity point-to-point session.
Requested Priority
M
Contains the required application priority for the IP data communication between both MCData clients.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.14.2.1.8 MCData remote IPcon point-to-point application priority change response
|
Table 7.14.2.1.8-1 describes the information content of the MCData remote IPcon point-to-point application priority change response as answer to MCData remote IPcon point-to-point application priority change request.
Table 7.14.2.1.8-1: MCData remote IPcon point-to-point application priority change response
Information element
Status
Description
MCData ID
M
The MCData identity of the first MCData client involved in the IP connectivity point-to-point session.
MCData ID
M
The MCData identity of the second MCData client involved in the IP connectivity point-to-point session.
Requested priority change status
M
The status information about the application priority of the addressed IP connectivity session.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.14.2.2 IP connectivity point-to-point MCData transport service
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.14.2.2.1 General
|
IP connectivity service capabilities enables MCData unaware data hosts to use usual MCData service capabilities, e.g. data communication between them. This subclause describes the establishment of a point-to-point connection between two IP connectivity clients using the media plane for IP Data transmission. The target MCData user may be addressed using the functional alias that can be shared by multiple MCData users.
In order not to violate the point-to-point principle when a functional alias is shared, only two MCData user can participate to a point-to-point IP connectivity session. If the MCData server detects that the functional alias used as the target of the MCData FD request is simultaneously active for multiple MCData users, then the MCData server can proceed by selecting an appropriate MCData ID based on some selection criteria. The selection of an appropriate MCData ID is left to implementation. These selection criteria can include rejection of the IP connectivity request, if no suitable MCData ID is selected.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.14.2.2.2 Procedure
|
The procedure in figure 7.14.2.2.2-1 describes the case where an IP connectivity capable MCData client is initiating a point-to-point IP connectivity with another IP connectivity capable MCData client.
Pre-conditions:
- The total data volume limit, e.g. daily time limit or total data volume per day does not restrict the establishment of an IP connectivity IP data exchange.
- MCData clients are linked with individual data hosts.
- MCData clients belong to the same MCData system.
- The data hosts linked with the MCData clients already have an IP address allocated.
- MCData clients have IP connectivity capabilities.
- The linked data hosts are authorized to use the MCData clients to establish an IP connectivity.
NOTE: How the data host is authorized to use the MCData client is out of the scope of the present document.
- The MCData server has subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates.
- MCData client 1 understands the correspondence between the IP addresses of target data hosts and MCData client 2. How this relationship is determined is out of scope of the present document.
- Optionally, the MCData clients may have activated a functional alias to be used.
Figure 7.14.2.2.2-1: Establishment of a point-to-point IP connectivity
1. MCData client 1 has IP Data to send to MCData client 2 and initiates an IP connectivity point-to-point request.
2. MCData client 1 sends a MCData IPcon point-to-point request towards the MCData server. The MCData IPcon point-to-point request contains either the MCData ID of MCData client 2 or its associated functional alias. MCData user at MCData client 1 may include its associated functional alias. The MCData client 1 may include additional application specific information in the request.
3. MCData server checks whether MCData user at MCData client 1 is authorized to send an MCData IPcon point-to-point request and checks if MCData client 2 is authorised to receive the IP connectivity service. If a functional alias is used to address the target MCData user, the MCData server resolves the functional alias to the corresponding MCData ID(s) for which the functional alias is active and proceed with step 4 otherwise proceed with step 6.
4. The MCData server responds back to MCData client 1 with a functional alias resolution response message that contains the resolved MCData ID.
5. If the MCData server replies with a MCData functional alias resolution response message, the MCData client 1 assumes the MCData IPcon point-to-point request in step 2 is rejected and sends a new MCData IPcon point-to-point request towards the resolved MCData ID.
6. MCData server initiates the MCData IPcon point-to-point request towards the determined MCData client 2.
NOTE: MCData client 2 corresponds to the MCData user(s) after resolution of the functional alias.
7. MCData client 2 sends a MCData IPcon point-to-point response to the MCData server that contains the information if the request is accepted or the reason of rejection. If accepted, the MCData client 2 may include following information elements:
i) the data transmission time limit.
ii) application data.
8. MCData server forwards the MCData IPcon point-to-point response of MCData client 2 to MCData client 1.
9. The MCData server applies transmission and reception control and the necessary policy to ensure that appropriate data is transmitted between the MCData clients.
10. MCData client 1 and MCData Client 2 have successfully established media plane for data communication and MCData client 1 and MCData client 2 exchange IP Data.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.14.2.3 Remote initiated point-to-point IP connectivity
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.