hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.13.3.18 Search folder
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.13.3.19 Retrieve folder content
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.13.3.20 Store file contents distributed using HTTP
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.13.4 Generic outgoing SDS procedure with MCData message store
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.13.5 Generic incoming SDS procedure with MCData message store
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.13.6 Interconnection and migration with MCData message store
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14 IP connectivity
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2 IP connectivity for on-network
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.1 Information flows for IP connectivity
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.1.1 MCData IPcon point-to-point request (MCData client to MCData server)
| 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.
7.14.2.1.1a MCData IPcon point-to-point request (MCData server to MCData client)
Table 7.14.2.1.1a-1 describes the information flow of the MCData IPcon point-to-point request sent from the MCData server to the MCData client.
Table 7.14.2.1.1a-1: 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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
|
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.2 IP connectivity point-to-point MCData transport service
| |
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 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.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.3 Remote initiated point-to-point IP connectivity
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.3.1 General
| The MCData service shall support mechanisms that allow an authorized MCData user to trigger remotely the establishment of a point-to-point IP connectivity service. This encompasses the procedure of a remote MCData user that addresses the establishment of an IP connectivity between the requested MCData client and the destination MCData client.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.3.2 Procedure
| The procedure in figure 7.14.2.3.2-1 describes the case where an authorised MCData user triggers remotely the establishment of a point-to-point IP connectivity connection between two other MCData users, required MCData user that establish IP connectivity session to the targeted MCData user.
Pre-conditions:
- The 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 clients understands the correspondence between the IP addresses of target data hosts and MCData client 3. 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.
- MCData client 1 is authorized to establish remote initiated point-to-point IP connectivity sessions.
Figure 7.14.2.3.2-1: Establishment of a remote point-to-point IP connectivity
1. MCData client 1 would like to establish a remote point-to-point IP connectivity to allow IP Data exchange between two other MCData clients, the asked MCData client 2 and the targeted MCData client 3.
2. The MCData client 1 sends an MCData remote IPcon point-to-point request towards the MCData server. The MCData IPcon point-to-point request contains the MCData ID and optionally the corresponding functional aliases of MCData client 2 and either the MCData ID or the functional alias of MCData client 3. MCData user at MCData client 1 may include its associated functional alias.
3. MCData server checks whether MCData user at MCData client 1 is authorized to send a remote MCData IPcon point-to-point request and if MCData client 2 and 3 are authorized to receive the IP connectivity service.
4. MCData server sends the MCData remote IPcon point-to-point request towards the MCData client 2.
5. MCData client 2 considers the provided targeted MCData ID or targeted functional alias to establish the point-to-point IP connectivity to MCData client 3 according to clause 7.14.2.2. The IP connectivity status shall be forwarded by MCData client 2 to MCData client 1.
6. MCData client 2 send an MCData remote IPcon point-to-point response to the MCData server encompassing the IP connectivity status of the point-to-point IP connectivity session between MCData client 2 and MCData client 3.
7. The MCData server forwards the MCData remote IPcon point-to-point response to the remote MCData client 1.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.4 MCData user remote initiated tear down point-to-point IP connectivity
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.4.1 General
| The MCData service shall support mechanisms that allow an authorized MCData user to tear down remotely an established point-to-point IP connectivity. This encompasses the procedure of a remote MCData user that addresses the tear down of an IP connectivity between the requested MCData client and the destination MCData client.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.4.2 Procedure
| The procedure in figure 7.14.2.4.2-1 describes the case where an authorised MCData user triggers remotely the tear down of a point-to-point IP connectivity connection between two other MCData users, the asked MCData user that tear down IP connectivity session to the targeted MCData user.
Pre-conditions:
- The point-to-point IP connectivity has been established between MCData client 2 and MCData client 3.
- Optionally, the MCData client 1 may have activated a functional alias to be used.
- MCData client 1 is authorized to tear down point-to-point IP connectivity sessions.
Figure 7.14.2.4.2-1: Remote initiated tear down of a point-to-point IP connectivity
1. MCData client 1 would like to tear down a point-to-point IP connectivity between two other MCData clients, the asked MCData client 2 and the targeted MCData client 3.
2. The MCData client 1 sends an MCData remote IPcon point-to-point tear down request towards the MCData server. The MCData remote IPcon point-to-point tear down request contains the MCData IDs of MCData client 2 and MCData client 3. MCData user at MCData client 1 may include its associated functional alias.
3. MCData server checks whether MCData user at MCData client 1 is authorized to send MCData remote IPcon point-to-point tear down request and checks if the asked MCData client 2 is allowed to tear down an IP connectivity point-to-point session.
4. MCData server sends the MCData remote IPcon point-to-point tear down request towards the MCData client 2.
5. MCData client 2 considers the provided targeted MCData ID to tear down the point-to-point IP connectivity to MCData client 3. The status of the IP connectivity tear down request shall be forwarded by MCData client 2 to remote MCData client 1.
6. MCData client 2 sends MCData remote IPcon point-to-point tear down response to the MCData server encompassing the tear down IP connectivity status between MCData client 2 and MCData client 3.
7. The MCData server forwards the MCData remote IPcon point-to-point tear down response to the remote MCData client 1.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.5 Remote initiated point-to-point IP connectivity application priority change
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.5.1 General
| The MCData service shall support mechanisms that allow an authorized MCData user to trigger remotely the adaptation of a point-to-point IP connectivity data bearer service priority. This encompasses the procedure of a remote MCData user that addresses the priority change of a point-to-point IP connectivity between the requested MCData clients.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.5.2 Procedure
| The procedure in figure 7.14.2.5.2-1 describes the case where an authorised MCData user triggers remotely the priority change of a point-to-point IP connectivity connection between two other MCData users.
Pre-conditions:
- Optionally, the MCData client 1 may have activated a functional alias to be used.
- A point-to-point IP connectivity is established between MCData client 2 and MCData client 3.
- MCData client 1 is authorized to change remotely communication priority of a point-to-point IP connectivity session.
Figure 7.14.2.5.2-1: Point-to-point IP connectivity application priority change request by a remote MCData client
1. MCData client 1 would like to change the priority that corresponds to an established point-to-point IP connectivity between MCData client 2 and MCData client 3.
2. The MCData client 1 sends a remote MCData IPcon point-to-point application priority change request towards the MCData server. The MCData IPcon point-to-point application priority change request contains the MCData IDs of MCData client 2 and MCData client 3. MCData user at MCData client 1 may include its associated functional alias.
3. MCData server checks whether MCData user at MCData client 1 is authorized to send a remote MCData IPcon point-to-point application priority change request.
4. MCData server applies the requested priority to the point-to-point IP connectivity between MCData client 2 and MCData client 3.
NOTE: Necessary adjustments in the relevant transport system can be included.
5. MCData server sends the remote MCData IPcon point-to-point application priority change response to MCData client 1 encompassing the priority status of the point-to-point IP connectivity between MCData client 2 and MCData client 3.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.6 Group standalone IP connectivity using media plane
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.6.1 General
| IP connectivity service capabilities enables authorized MCData unaware data host to use usual MCData service capabilities, e.g. data communication among them. This subclause describes the establishment of a group standalone IP connectivity to a selected MCData group results in affiliated group members exchanging IP data.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.6.2 Procedure
| The procedure in figure 7.14.2.6.2-1 describes the case where an IP connectivity capable MCData client is initiating group standalone MCData IP connectivity communication session with an MCData group for exchanging IP Data between group participants using MCData IPcon-2 reference point.
Pre-conditions:
- MCData client 1 to MCData client n belong to the same MCData group, are registered for receiving MCData service and are affiliated to the corresponding MCData group.
- 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 MCData transmission.
- MCData client 1 to MCData client n are linked with individual data hosts.
- MCData client 1 to MCData client n 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 1: 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 clients understand the correspondence between the IP addresses of target data hosts and MCData clients. How this relationship is determined is out of scope of the present document.
- MCData clients understand the relationship between the addressing of IP packets which are intended to be sent to the group and the MCData group address.
NOTE 2: The allocation of IP addresses for group addressed communication is outside the scope of the present document.
Figure 7.14.2.6.2-1: Establishment of IPcon group standalone communication session
1. MCData client 1 receives an IP packet from the IP data host which is addressed to an IP address that signifies an MCData group destination.
2. MCData client 1 uses the MCData group standalone short data service using media plane procedure in accordance with clause 7.4.2.6 to establish IPcon group standalone communication session to the MCData user that are members of the corresponding MCData group with the following scope:
- IP Data exchange
- The application identifier is used to indicate about the use of a group communication in the IP connectivity context
- Payload destination indicates the consumption by the linked data host
- The use of disposition shall be discarded for the use of IP connectivity
3. MCData clients 2-n recognize that the payload is for IP connectivity service and forward the received IP data to the linked data hosts.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.15 Location information (on-network)
| The MCData system makes use of all of the procedures for location management as specified in 3GPP TS 23.280 [5], utilising the CSC-14 reference point between the location management client and location management server and the CSC‑15 reference point between the MCData server and location management server.
- The MC service client is the MCData client;
- The MC service server is the MCData server;
- The MC service group is the MCData group;
- The MC service ID is the MCData ID; and
- The MC service group ID is the MCData group ID.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.16 Use of ProSe capabilities in off-network MCData communications
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.16.1 General
| When an MCData user using a ProSe-enabled UE wants to communicate with a specific MCData group or MCData user using ProSe capabilities, the MCData client enables the use of the ProSe layer procedures for public safety, as specified in 3GPP TS 23.303 [7].
For an off-network MCData group communication, the MCData client obtains configuration data such as the user info ID of the MCData user sending data and the ProSe Group IP multicast address and ProSe Layer-2 Group ID associated to the target MCData group (as described in clause 8.1.3.2 in 3GPP TS 23.280 [5]), and provides it to the ProSe layer. The ProSe Layer-2 Group ID of the target MCData group may be used by the ProSe layer as the target group info and the discovery group ID (defined in 3GPP TS 23.303 [7]).
Prior to initiating an off-network MCData group communication, a group member discovery procedure may be initiated to identify whether other members of the target MCData group are in the proximity of the MCData user sending data, as described in the ProSe direct discovery for public safety use procedure in 3GPP TS 23.303 [7]. The off-network MCData group communication using the ProSe capability is based on the one-to-many ProSe direct communication procedure for public safety use described in 3GPP TS 23.303 [7].
For an off-network one-to-one MCData communication, the MCData client obtains configuration data such as the ProSe discovery group ID and user info ID of the target MCData user from the "List of MCData users this MCData user is authorized to initiate a one to-one communication" in the MCData user profile and requests the IP address of the MCData UE associated with the target MCData user from the ProSe layer.
The MCData client enables the ProSe layer to determine the IP address for the communication with the target MCData UE by providing the ProSe discovery group ID and user info ID (as defined in 3GPP TS 23.303 [7]) associated to the target MCData user. This may trigger the ProSe direct discovery for public safety use procedure to identify whether the target MCData user is in the proximity of the MCData user sending data. The user info ID of the target MCData user is used by the ProSe layer as the target info (as defined in 3GPP TS 23.303 [7]).
The ProSe layer can then provide the IP address related to the target MCData user to the MCData client to initiate the off-network one-to-one MCData communication based on the one-to-one ProSe direct communication procedure described in 3GPP TS 23.303 [7].
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.16.2 Procedures
| The off-network MCData communication procedures using the ProSe capabilities are described within the corresponding clauses of each MCData capability, e.g. SDS procedures for off-network are described in clause 7.4.3 and file distribution procedures for off-network are described in clause 7.5.3.
7.17 Ad hoc group data communication
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.1 General
| This subclause contains procedures for ad hoc group data communication across a single MCData system for both SDS and FD services, and associated functions such as emergency data communication, Imminent peril data communication and others.
The ad hoc group data communications can use the participants list provided by either an initiator of the data communication or MCData server. The MCData server can use the criteria provided by the initiator of the data communication to determine the participants list along with its own criteria or local policies. The resulting ad hoc group uses the configuration of a separate preconfigured MCData group.
NOTE 1: A preconfigured group which is intended only to provide configuration for the ad hoc group is identified by a parameter in the group configuration described in 3GPP TS 23.280 [5].
The preconfigured MCData group that provides the configuration is not used for the MCData group communication, it only provides configuration for one or more adhoc group data communications. The MCData group ID of the ad hoc group data communication is provided by the MCData server when the ad hoc group data communication is originated. In order to establish security context for the end-to-end secured ad hoc group data communication, the security related information is used from this preconfigured group.
NOTE 2: The configurations defined for the adhoc group data communication in user profile and service configuration document as described in the Annex A.3 and A.5 is applicable only for single MCData system.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.2 Common Information flows
| 7.17.2.1 Ad hoc group data session request (MCData client – MCData server)
Table 7.17.2.1-1 describes the information flow ad hoc group data session request from the MCData client to the MCData server.
Table 7.17.2.1-1: Ad hoc group data session request information elements
Information Element
Status
Description
MCData ID
M
The identity of the MCData user sending data
Functional alias
O
The associated functional alias of the MCData user sending data.
MCData ad hoc group ID (see NOTE 1)
O
The MCData group ID to be associated with the ad hoc group data communication
Encryption supported (see NOTE 2)
O
Indicates whether this ad hoc group data communication supports end-to-end encryption
MCData ID list (see NOTE 3, NOTE 5, NOTE 6)
O
MCData IDs of the participants being invited for the ad hoc group data communication
SDP offer
M
Offered media parameters
Imminent peril indicator (see NOTE 4)
O
Indicates that the ad hoc group data communication request is for ad hoc group imminent peril data communication
Emergency Indicator (see NOTE 4)
O
Indicates that the ad hoc group data communication request is for ad hoc group emergency data communication
Broadcast indicator
(see NOTE 4)
O
Indicates that the ad hoc group data communication request is for a broadcast ad hoc group data communication
MCData ID list (see NOTE 3)
O
List of participants required to acknowledge the ad hoc group data communication before start of the data transmission
Location information
O
Location of the of the MCData user sending data.
Criteria for determining the participants (see NOTE 5)
O
Carries the details of criteria or meaningful label identifying the criteria or the combination of both which will be used by the MCData server for determining the participants e.g., it can be a location based criteria to invite participants in a particular area
Requested priority
O
Application priority level requested for this ad hoc group data communication
NOTE 1: If this information element is not included, the MCData server assigns an MCData ad hoc group ID to be used for the ad hoc group data communication. This information element is returned to the MCData user who is sending the data to use in the ad hoc group data communication. If the request follows an ad hoc group for emergency alert, then this element must be present.
NOTE 2: This information element is present and set to true only if this ad hoc group data communication is encrypted. When the ad hoc group data communication is initiated with participants provided by the initiator this acts as an indicator that subsequent requests follow targeting the individual participants and carrying the relevant key material. If this information element is set to false or not present, then this ad hoc group data communication is unencrypted.
NOTE 3: This element is included only when the data communication initiating client sends the list of participants.
NOTE 4: If used, only one of these information elements is present.
NOTE 5: Only one of these information elements is present.
NOTE 6: If the request follows an ad hoc group for emergency alert, then this element is not present.
7.17.2.2 Ad hoc group data session request return (MCData server – MCData client)
Table 7.17.2.2-1 describes the information flow ad hoc group data session request return from the MCData server to the MCData client. This response could be intermediate response to provide the server assigned MCData ad hoc group ID.
Table 7.17.2.2-1 Ad hoc group data session request return information elements
Information Element
Status
Description
MCData ID
M
The identity of the MCData user sending data
MCData ad hoc group ID
O
The MCData group ID to be associated with the ad hoc group data communication which is either provided by the group data session initiator or assigned by the MCData server. This information element shall be present if the authorization result is success.
Preconfigured MCData group ID
O
Group identity whose configuration is to be applied for this ad hoc group data communication. This information element shall be present if the authorization result is success.
Authorization result
M
Indicate if authorization is success or failure
7.17.2.3 Ad hoc group data session request (MCData server – MCData server)
Table 7.17.2.3-1 describes the information flow ad hoc group data session request between the MCData servers.
Table 7.17.2.3-1: Ad hoc group data session request information elements
Information Element
Status
Description
MCData ID
M
The identity of the MCData user sending data
Functional alias
O
The associated functional alias of the MCData user sending data.
MCData ad hoc group ID
M
The MCData group ID to be associated with the ad hoc group data communication
MCData ID list
(see NOTE 1, NOTE 3)
O
MCData IDs of the participants being invited for the ad hoc group data communication
SDP offer
M
Media parameters of MCData server
Broadcast indicator
(see NOTE 2)
O
Indicates that the ad hoc group data communication request is for a broadcast ad hoc group data communication
Imminent peril indicator (see NOTE 2)
O
Indicates that the ad hoc group data communication request is for ad hoc group imminent peril data communication
Emergency Indicator (see NOTE 2)
O
Indicates that the ad hoc group data communication request is for ad hoc group emergency data communication
Preconfigured MCData group ID
O
Group identity whose configuration is to be applied for this ad hoc group data communication.
Criteria for determining the participants (see NOTE 3)
O
Carries the details of criteria or meaningful label identifying the criteria or the combination of both which will be used by the MCData server for determining the participants e.g., it can be a location based criteria to invite participants in a particular area
Requested priority
O
Application priority level requested for this group data communication
NOTE 1: This element is included only when the data communication initiating client sends the list of participants.
NOTE 2: If used, only one of these information elements is present.
NOTE 3: Only one of these information elements is present.
7.17.2.4 Ad hoc group data session request (MCData server – MCData client)
Table 7.17.2.4-1 describes the information flow ad hoc group data session request from the MCData server to the MCData client.
Table 7.17.2.4-1: Ad hoc group data session request information elements
Information Element
Status
Description
MCData ID
M
The identity of the MCData user sending data
MCData ID
M
The identity of the MCData user towards which the request is sent
Functional alias
O
The associated functional alias of the MCData user sending data.
MCData ad hoc group ID
M
The MCData group ID associated with the ad hoc group data communication
SDP offer
M
Media parameters of MCData server
Broadcast indicator
(see NOTE)
O
Indicates that the ad hoc group data communication request is for a broadcast ad hoc group data communication
Imminent peril indicator (see NOTE)
O
Indicates that the ad hoc group data communication request is for ad hoc group imminent peril data communication
Emergency Indicator (see NOTE)
O
Indicates that the ad hoc group data communication request is for ad hoc group emergency data communication
Preconfigured MCData group ID
O
Group identity whose configuration is to be applied for this ad hoc group data communication.
Location information
O
Location of the MCData user sending data.
Call resulting criteria for determining the participants
O
Carries the details of criteria or meaningful label identifying the criteria or the combination of both that the MCData server used for determining the participants e.g., it can be a location based criteria to invite participants in a particular area
NOTE: If used, only one of these information elements is present.
7.17.2.5 Ad hoc group data session response (MCData server – MCData client)
Table 7.17.2.5-1 describes the information flow ad hoc group data session response from the MCData server to the MCData client.
Table 7.17.2.5-1: Ad hoc group data session response information elements
Information Element
Status
Description
MCData ID
M
The identity of the MCData user sending data
Functional alias
O
The associated functional alias of the MCData user sending data.
MCData ad hoc group ID
M
The MCData group ID associated with the ad hoc group data communication
SDP answer
O
Media parameters selected and present if the Result is success.
Result
M
Result of the group data communication request (success or failure)
Call resulting criteria for determining the participants
O
Carries the details of criteria or meaningful label identifying the criteria or the combination of both that the MCData server used for determining the participants e.g., it can be a location based criteria to invite participants in a particular area
7.17.2.6 Ad hoc group data session response (MCData server – MCData server)
Table 7.17.2.6-1 describes the information flow ad hoc group data session response between the MCData servers.
Table 7.17.2.6-1: Ad hoc group data session response information elements
Information Element
Status
Description
MCData ID
M
The identity of the MCData user receiving data
Functional alias
O
The functional alias of the MCData user receiving data
MCData ad hoc group ID
M
The MCData group ID associated with the ad hoc group data communication
SDP answer
O
Media parameters selected and present if the Result is success.
Result
M
Result of the ad hoc group data communication request (success or failure)
7.17.2.7 Ad hoc group data session response (MCData client – MCData server)
Table 7.17.2.7-1 describes the information flow ad hoc group data session response from the MCData client to the MCData server.
Table 7.17.2.7-1: Ad hoc group data session response information elements
Information Element
Status
Description
MCData ID
M
The identity of the MCData user receiving data
Functional alias
O
The functional alias of the MCData user receiving data
MCData ad hoc group ID
M
The MCData group ID associated with the ad hoc group data communication
SDP answer
O
Media parameters selected and present if the Result is success.
Result
M
Result of the ad hoc group data communication request (success or failure)
7.17.2.8 Ad hoc group data session release request (MCData server – MCData client)
Table 7.17.2.8-1 describes the information flow ad hoc group data session release request from the MCData server to the MCData client.
Table 7.17.2.8-1: Ad hoc group data session release request information elements
Information Element
Status
Description
MCData ID
M
The MCData ID of the ad hoc group data communication participant
Functional alias
O
The functional alias of the ad hoc group data communication participant
MCData ad hoc group ID
M
The MCData group ID of the ad hoc group data communication on which data communication is released
7.17.2.8a Ad hoc group data session release request (MCData client – MCData server)
Table 7.17.2.8a-1 describes the information flow ad hoc group data session release request from the MCData client to the MCData server.
Table 7.17.2.8a-1: Ad hoc group data session release request information elements
Information Element
Status
Description
MCData ID
M
The MCData ID of the user authorized to release the ad hoc group data communication
Functional alias
O
The functional alias of the authorized user requesting to release the ad hoc group call
MCData ad hoc group ID
M
The MCData group ID of the ad hoc group data communication on which data communication is released
7.17.2.8b Ad hoc group data session release request (MCData server – MCData server)
Table 7.17.2.8b-1 describes the information flow ad hoc group data session release request between MCData servers.
Table 7.17.2.8b-1: Ad hoc group data session release request information elements
Information Element
Status
Description
MCData ID
M
The MCData ID of the user authorized to release the ad hoc group data communication
Functional alias
O
The functional alias of the authorized user requesting to release the ad hoc group call
MCData ad hoc group ID
M
The MCData group ID of the ad hoc group data communication on which data communication is released
7.17.2.9 Ad hoc group data session release response (MCData client – MCData server)
Table 7.17.2.9-1 describes the information flow ad hoc group data session release response from the MCData client to the MCData server.
Table 7.17.2.9-1: Ad hoc group data session release response information elements
Information Element
Status
Description
MCData ID
M
The MCData ID of the ad hoc group data communication participant
Functional alias
O
The functional alias of the ad hoc group data communication participant
MCData ad hoc group ID
M
The MCData group ID of the ad hoc group data communication on which data communication is released
7.17.2.9a Ad hoc group data session release response (MCData server – MCData client)
Table 7.17.2.9a-1 describes the information flow ad hoc group data session release response from the MCData server to the MCData client.
Table 7.17.2.9a-1: Ad hoc group data session release response information elements
Information Element
Status
Description
MCData ID
M
The MCData ID of the user authorized to release the ad hoc group data communication
Functional alias
O
The functional alias of the authorized user requesting to release the ad hoc group data communication
MCData ad hoc group ID
M
The MCData group ID of the ad hoc group data communication on which data communication is released
7.17.2.9b Ad hoc group data session release response (MCData server – MCData server)
Table 7.17.2.9b-1 describes the information flow ad hoc group data session release response between MCData servers.
Table 7.17.2.9b-1: Ad hoc group data session release response information elements
Information Element
Status
Description
MCData ID
M
The MCData ID of the user authorized to release the ad hoc group data communication
Functional alias
O
The functional alias of the authorized user requesting to release the ad hoc group data communication
MCData ad hoc group ID
M
The MCData group ID of the ad hoc group data communication on which data communication is released
7.17.2.10 Ad hoc group data session notify (MCData server – MCData client)
Table 7.17.2.10-1 describes the information flow ad hoc group data session notify from MCData server to MCData client.
Table 7.17.2.10-1: Ad hoc group data session notify
Information element
Status
Description
MCData ID
M
The MCData ID of the ad hoc group data communication participant
Functional alias
O
The associated functional alias of the MCData user of the ad hoc group data communication participant
MCData ad hoc group ID
M
The MCData group ID associated with the ad hoc group data communication
MCData ID list
O
The list of the invited MCData users who did not acknowledged the ad hoc group data communication request within a configured time or the list of the invited MCData users who acknowledged the ad hoc group data communication request and joined or the list of the MCData users who joined or left the ongoing MCData ad hoc group data communication.
Call resulting criteria for determining the participants
O
Carries the details of criteria or meaningful label identifying the criteria or the combination of both that the MCData server used for determining the participants e.g., it can be a location based criteria to invite participants in a particular area
7.17.2.11 Modify ad hoc group data session participants request (MCData client – MCData server)
Table 7.17.2.11-1 describes the information flow Modify ad hoc group data session participants request from the MCData client to the MCData server.
Table 7.17.2.11-1: Modify ad hoc group data session participants request
Information element
Status
Description
MCData ID
M
The MCData ID of the requesting MCData user who is authorized to modify the ad hoc group data session participants
Functional alias
O
The functional alias of the requesting MCData user who is authorized to modify the ad hoc group data session participants
MCData ad hoc group ID
M
The MCData group ID of ad hoc group data communication whose participants needs to be modified
MCData ID list (see NOTE)
O
List of additional MCData users to be added to the on-going ad hoc group data communication
MCData ID list (see NOTE)
O
List of MCData users to be removed from the on-going ad hoc group data communication
NOTE: Either one or both of these information elements is present
7.17.2.12 Modify ad hoc group data session participants response (MCData server – MCData client)
Table 7.17.2.12-1 describes the information flow Modify ad hoc group data session participants response from the MCData server to the MCData client.
Table 7.17.2.12-1: Modify Ad hoc group data session participants response information elements
Information Element
Status
Description
MCData ID
M
The MCData ID of the requesting MCData user who is authorized to modify the ad hoc group data session participants
Functional alias
O
The functional alias of the requesting MCData user who is authorized to modify the ad hoc group data session participants
MCData ad hoc group ID
M
The MCData group ID of ad hoc group data communication whose participants needs to be modified
Result
M
Result of the modify ad hoc group data communication participants request (success or failure)
MCData ID list
O
List of MCData users who are not allowed to be added to the on-going ad hoc group data communication. This list is provided if the operation is partially success.
7.17.2.13 Ad hoc group data session leave request (MCData server – MCData client)
Table 7.17.2.13-1 describes the information flow ad hoc group data session leave request from the MCData server to the MCData client.
Table 7.17.2.13-1: Ad hoc group data session leave request information elements
Information Element
Status
Description
MCData ID
M
The MCData ID of the ad hoc group data communication participant leaving the ad hoc group data communication
MCData ad hoc group ID
M
The MCData group ID of ad hoc group data communication
Reason to leave
O
Carries the reason of why the MCData client is being asked to leave the ongoing ad hoc group data communication
7.17.2.13a Ad hoc group data session leave request (MCData client – MCData server)
Table 7.17.2.13a-1 describes the information flow ad hoc group data session leave request from the MCData client to the MCData server.
Table 7.17.2.13a-1: Ad hoc group data session leave request information elements
Information Element
Status
Description
MCData ID
M
The MCData ID of the ad hoc group data communication participant leaving the ad hoc group data communication`
MCData ad hoc group ID
M
The MCData group ID of ad hoc group data communication on which data session is ongoing
Reason to leave
M
Carries the reason of why the MCData client is leaving ongoing ad hoc group data communication (e.g. Due to migration).
7.17.2.13b Ad hoc group data session leave request (MCData server – MCData server)
Table 7.17.2.13b-1 describes the information flow ad hoc group data session leave request between MCData servers.
Table 7.17.2.13b-1: Ad hoc group data session leave request information elements
Information Element
Status
Description
MCData ID
M
The MCData ID of the ad hoc group data communication participant leaving the ad hoc group data communication`
MCData ad hoc group ID
M
The MCData group ID of ad hoc group data communication on which data session is ongoing
Reason to leave
(see NOTE)
O
Carries the reason of why the MCData client is leaving ongoing ad hoc group data communication (e.g. Due to migration).
NOTE: This element is only mandatory when originally sent from client to server (see 7.17.2.13a)
7.17.2.14 Ad hoc group data session leave response (MCData client – MCData server)
Table 7.17.2.14-1 describes the information flow Ad hoc group data session leave response from the MCData client to the MCData server.
Table 7.17.2.14-1: Ad hoc group data session leave response information elements
Information Element
Status
Description
MCData ID
M
The MCData ID of the ad hoc group data communication participant leaving the ad hoc group data communication
MCData ad hoc group ID
M
The MCData group ID of ad hoc group data communication
7.17.2.14a Ad hoc group data session leave response (MCData server – MCData client)
Table 7.17.2.14a-1 describes the information flow Ad hoc group data session leave response from the MCData server to the MCData client.
Table 7.17.2.14a-1: Ad hoc group data session leave response information elements
Information Element
Status
Description
MCData ID
M
The MCData ID of the ad hoc group data communication participant leaving the ad hoc group data communication
MCData ad hoc group ID
M
The MCData group ID of ad hoc group data communication on which data session is ongoing
Result
M
Result of the ad hoc group communication leave request – success or failure.
7.17.2.14b Ad hoc group data session leave response (MCData server – MCData server)
Table 7.17.2.14b-1 describes the information flow Ad hoc group data session leave response between MCData servers.
Table 7.17.2.14b-1: Ad hoc group data session leave response information elements
Information Element
Status
Description
MCData ID
M
The MCData ID of the ad hoc group data communication participant leaving the ad hoc group data communication
MCData ad hoc group ID
M
The MCData group ID of ad hoc group data communication on which data session is ongoing
Result
(See NOTE)
O
Result of the ad hoc group communication leave request – success or failure.
NOTE: This element is only included when originally sent from server to a client (see 7.17.2.14a)
7.17.2.15 Ad hoc group data session get userlist (MCData server – MCData server)
Table 7.17.2.15-1 describes the information flow ad hoc group data session get userlist from one MCData server to another MCData server.
Table 7.17.2.15-1: Ad hoc group data session get userlist
Information element
Status
Description
MCData ad hoc group ID
M
The MCData group ID associated with the ad hoc group communication
Criteria for determining the participants
M
Carries the details of criteria or meaningful label identifying the criteria or the combination of both which will be used by the MCData server for determining the participants e.g., it can be a location based criteria to invite participants in a particular area
7.17.2.16 Ad hoc group data session get userlist response (MCData server – MCData server)
Table 7.17.2.16-1 describes the information flow ad hoc group data session get userlist response from one MCData server to another MCData server.
Table 7.17.2.16-1: Ad hoc group data session get userlist response
Information element
Status
Description
MCData ad hoc group ID
M
The MCData group ID associated with the ad hoc group communication
MCData ID list
M
List of MCData IDs meeting the criteria specified in the ad hoc group data session get userlist
7.17.2.17 Ad hoc group data session add user notification (MCData server – MCData server)
Table 7.17.2.17-1 describes the information flow Ad hoc group data session add user notification from one MCData server to another MCData server. This notification is to provide the list of MCData IDs meeting the criteria specified in the ad hoc group data session get userlist request from one MCData server to another MCData server.
Table 7.17.2.17-1: Ad hoc group data session add user notification information elements
Information Element
Status
Description
MCData ad hoc group ID
M
The MCData group ID associated with the ad hoc group communication
MCData ID list
M
List of MCData IDs meeting the criteria specified in the ad hoc group data session get userlist
7.17.2.18 Ad hoc group data session remove user notification (MCData server – MCData server)
Table 7.17.2.18-1 describes the information flow Ad hoc group data session remove user notification from one MCData server to another MCData server. This notification is to provide the list of MCData IDs no longer meeting the criteria specified in the ad hoc group data session get userlist request from one MCData server to another MCData server.
Table 7.17.2.18-1: Ad hoc group data session remove user notification information elements
Information Element
Status
Description
MCData ad hoc group ID
M
The MCData group ID associated with the ad hoc group communication
MCData ID list
M
List of MCData IDs no longer meeting the criteria specified in the ad hoc group data session get userlist
7.17.2.19 Ad hoc group data session release notification (MCData server – MCData server)
Table 7.17.2.19 -1 describes the information flow Ad hoc group data session release notification from one MCData server to another MCData server. This notification is to indicate to stop evaluating the criteria to determine the participants list if another MCData server is having the criteria specified in the ad hoc group data session get userlist request.
Table 7.17.2.19-1: Ad hoc group data session release notification information elements
Information Element
Status
Description
MCData ad hoc group ID
M
The MCData group ID associated with the ad hoc group communication
7.17.2.20 Modify ad hoc group data session criteria request (MCData client – MCData server)
Table 7.17.2.20-1 describes the information flow Modify ad hoc group data session criteria request from the MCData client to the MCData server.
Table 7.17.2.20-1: Modify ad hoc group data session criteria request
Information element
Status
Description
MCData ID
M
The MCData ID of the requesting MCData user who is authorized to modify the ad hoc group criteria
Functional alias
O
The functional alias of the MCData user who is authorized to modify the ad hoc group criteria
MCData ad hoc group ID
M
The MCData group ID of ad hoc group data communication whose participants list needs to be modified
Criteria to determine the list of participants
O
Carries the details of criteria or meaningful label identifying the criteria or the combination of both which will be used by the MCData server for determining the participants e.g., it can be a location-based criteria to invite participants in a particular area
7.17.2.20a Modify ad hoc group data session criteria request (MCData server – MCData server)
Table 7.17.2.20a-1 describes the information flow Modify ad hoc group data session criteria request from the MCData server to the MCData server.
Table 7.17.2.20a-1: Modify ad hoc group data session criteria request
Information element
Status
Description
MCData ID
M
The MCData ID of the MCData user who is requesting for modification of ad hoc group data session participants
Functional alias
O
The associated functional alias of the MCData user who is requesting for modification of ad hoc group data session participants
MCData ad hoc group ID
M
The MCData group ID of ad hoc group data data session whose participants list needs to be modified
Criteria to determine the list of participants
O
Carries the details of criteria or meaningful label identifying the criteria or the combination of both which will be used by the MCData server for determining the participants e.g., it can be a location-based criteria to invite participants in a particular area
7.17.2.21 Modify ad hoc group data session criteria response (MCData server – MCData client)
Table 7.17.2.21-1 describes the information flow Modify ad hoc group data session criteria response from the MCData server to the MCData client.
Table 7.17.2.21-1: Modify Ad hoc group data session criteria response information elements
Information Element
Status
Description
MCData ID
M
The MCData ID of the requesting MCData user who is authorized to modify the ad hoc group criteria
Functional alias
O
The functional alias of the requesting MCData user who is authorized to modify the ad hoc group criteria
MCData ad hoc group ID
M
The MCData group ID of ad hoc group data communication whose participants list needs to be modified
Result
M
Result of the modify ad hoc group data communication participants request (success or failure)
7.17.2.21a Modify ad hoc group data session criteria response (MCData server – MCData server)
Table 7.17.2.21a-1 describes the information flow Modify ad hoc group data session criteria response from the MCData server to the MCData server.
Table 7.17.2.21a-1: Modify Ad hoc group data session criteria response information elements
Information Element
Status
Description
MCData ID
M
The MCData ID of the MCData user who is requesting for modification of ad hoc group data session participants
Functional alias
O
The associated functional alias of the MCData user who is requesting for modification of ad hoc group data session participants
MCData ad hoc group ID
M
The MCData group ID of ad hoc group data data session whose participants list needs to be modified
Result
M
Result of the modify ad hoc group data data session participants request (success or failure)
Call resulting criteria for determining the participants
O
Carries the details of criteria or meaningful label identifying the criteria or the combination of both that the MCData server used for determining the participants e.g., it can be a location based criteria to invite participants in a particular area
7.17.3 Common Ad hoc group data communication procedures
7.17.3.1 Ad hoc group data communication procedures in single MCData system
7.17.3.1.1 Ad hoc group data communication setup
Figure 7.17.3.1.1-1 below illustrates the ad hoc group data communication setup procedure initiated by an authorized user.
Pre-conditions:
1. The authorized user at MCData client 1 wants to invite MCData users at MCData client 2, MCData client 3 and MCData client 4 for the ad hoc group data communication or to invite the ad hoc group member if the ad hoc group call follows an ad hoc group emergency alert, the MCData client 1 is aware of the ad hoc group ID.
2. Number of participants being invited for the ad hoc group data communication is within the limit.
3. End-to-End encryption is supported for this ad hoc group data communication.
4. MCData client 1 is aware of the MCData IDs of the participants.
NOTE 1: Selection of MCData IDs of the participants can be manual or from the user profile configuration data or by any other means. This is left for the implementation.
5. The pre-configured group identity and pre-configured group configuration to be used for an ad hoc group have been preconfigured in MCData client and other participants of ad hoc group have also received the relevant security related information to allow them to communicate in an ad hoc group communication.
Figure 7.17.3.1.1-1: Ad hoc group data communication setup
1. User at MCData client 1 would like to initiate an ad hoc group data communication. The MCData client 1 initiates the ad hoc group data communication by sending the ad hoc group data session request containing the list of participants or an ad hoc group ID from an ad hoc group emergency alert to the MCData server. Encryption supported information element shall be set to true since end-to-end encryption is supported. An SDP offer containing the MCData client media parameters is included. If the MCData user of MCData client 1 has selected a functional alias, then the ad hoc group data session request contains that functional alias.
If the MCData user at MCData client 1 initiates an MCData emergency ad hoc group data communication or the MCData emergency state is already set for the MCData client 1 (due to a previously triggered MCData emergency alert):
i. the MCData ad hoc group data session request shall contain an emergency indicator;
ii. if the MCData emergency state is not set already, MCData client 1 sets its MCData emergency state. The MCData emergency state of MCData client 1 is retained until explicitly cancelled by the user of MCData client 1.
2. If the ad hoc group communication is supported, the MCData server verifies whether the user at MCData client 1 is authorized to initiate an ad hoc group data session request. If not authorized, the MCData server rejects the ad hoc group data session request as specified in the step 3. The MCData server accepts the ad hoc group data session request if the ad hoc group data communication is supported and authorized. If authorised, it validates whether the number of invited participants is within the configured limit before proceeding with the data communication setup.
If functional alias is present, the MCData server checks whether the provided functional alias allowed to be used and has been activated for the user.
If location information was included in the ad hoc group data session request, the MCData server checks the privacy policy of the MCData user to decide if the location information of MCData client 1 can be provided to other users on the ad hoc group data communication (refer to Annex A.3 "Authorisation to provide location information to other MCData users on a data communication when talking").
If an emergency indicator is present in the received MCData ad hoc group data session request, the MCData ad hoc group is considered to be in the in-progress emergency state until this ad hoc group data communication is terminated; and
If an imminent peril indicator is present in the received MCData ad hoc group data session request, the MCData ad hoc group is considered to be in the in-progress imminent peril state until this ad hoc group data communication is terminated.
If the information received in the request in step 1 does not contain an ad hoc group ID from an ad hoc group emergency alert, the MCData server forms the ad hoc group by using received information, and determines the preconfigured group to be used for the configuration of the ad hoc group. The MCData server assigns a MCData group ID for the newly formed ad hoc group.
The MCData server considers the ad hoc group data communication participants as implicitly affiliated to the ad hoc group.
3. The MCData server shall send the ad hoc group data session request return message to MCData client 1 containing the below:
i. The MCData ad hoc group ID, either generated by the MCData server, if not included in the ad hoc group call request of step 1, or if the provided MCData ad hoc group ID is not accepted by the MCData server; or provided by the MCData client 1 if the ad hoc group ID is from an ad hoc group emergency alert;
ii. The group ID of the pre-configured group to be used for the ad hoc group communication (only included when the ad hoc group data session is authorized); and
iii. Result of whether the ad hoc group data session request is authorized or not
If the ad hoc group data session request is not authorized, the MCData server and MCData client 1 shall not proceed with the rest of the steps.
4a-4c. The MCData server sends the ad hoc group data session requests towards the MCData clients of the invited users based on step 1. While sending the ad hoc group data session requests, the MCData server shall remove the information elements that are not required to be conveyed to the target MCData clients (e.g. MCData ID list of the users who are required to acknowledge)
5a-5c. The receiving MCData clients notify their corresponding MCData user about the incoming ad hoc group data session request with the information of the MCData group ID for the ad hoc group.
6a-6c. The receiving MCData clients may accept or reject the ad hoc group data session requests and send ad hoc group data session responses to the MCData server. The response may also contain a functional alias of the responding MCData user, which is verified (valid and activated for the user) by the MCData server.
7. The MCData server sends the ad hoc group data session response to MCData client 1 through the signalling path to inform about successful data communication establishment.
NOTE 2: Steps 5 to step 7 can start to occur before all of step 4 is completed since the MCData server do not require to wait for the previous ad hoc group data session request to complete before sending the ad hoc group data session request to another participant.
8. If the initiating MCData user requires the acknowledgement from the invited MCData users, and the required MCData users do not acknowledge the data session setup within a configured time (the "acknowledged data communication setup timeout"), then the MCData server may proceed with or abandon the data session and then notify the initiating MCData user that the acknowledgements did not include all required members according to ad hoc group data communication policy from the user profile configuration. The MCData server may notify the initiating MCData user of all MCData users who did not acknowledge the ad hoc group data session request within the configured time. This notification may be sent to the initiating MCData user by the MCData server more than once during the data communication when MCData users join or leave the MCData ad hoc group data communication.
9. MCData client 1, MCData client 2, MCData client 3 and MCData client 4 establish media plane for data communication.
NOTE 3: Step 9 can occur any time following step 7 if the conditions to proceed with the data communication are met.
7.17.3.1.2 Release ad hoc group data communication by the MCData server
The procedure focuses on the case where the MCData server releases an ongoing MCData ad hoc group data communication for all the participants of that ad hoc group data communication, since at least one of the release conditions are met e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving.
Figure 7.17.3.1.2-1 below illustrates the signalling control plane procedure for the MCData server initiating termination of an ongoing ad hoc group data communication.
Figure 7.17.3.1.2-1: Release ad hoc group data communication by the MCData server
1. It is assumed that MCData users on MCData client 1, client 2 and client 3 are already part of the ongoing ad hoc group data communication.
2. MCData server would like to release the MCData ad hoc group data communication which is ongoing e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving.
3. MCData server identifies the participants of the ongoing ad hoc group data communication and generates ad hoc group data session release request to release ongoing data communication. The MCData server cancels the in-progress emergency state or in-progress imminent peril state of the ad hoc group if the ad hoc group data communication is an emergency or imminent peril data communication respectively.
4. MCData server sends ad hoc group data session release request via SIP core towards each participant of the ongoing ad hoc group data communication.
5. MCData users are notified about the release of the ad hoc group data communication.
6. MCData client(s) receiving ad hoc group data session release request, acknowledge towards the MCData server by sending an ad hoc group data session release response.
NOTE: If the initiator of the ad hoc group data communication does not supply the participants list, the MCData client(s) may choose to store the list of participants for easy re-initiation of another ad hoc group data communication with the same participants.
7. MCData client 1, client 2 and client 3 have successfully released the media plane resources associated with the ad hoc group data communication that is terminated and the ad hoc group ceases to exist (i.e., further data communication is not possible over the same ad hoc group), otherwise if the ad hoc group data communication follows an ad hoc group emergency alert the ad hoc group continues to exist (i.e., further data communication is possible over the same ad hoc group).
7.17.3.1.2a Release ad hoc group data communication by an authorized user
The procedure focuses on the case where an authorized user releases an ongoing MCData ad hoc group data communication for all the participants of that ad hoc group data communication.
Figure 7.17.3.1.2a-1 below illustrates the signalling control plane procedure for the MCData client initiating termination of an ongoing ad hoc group data communication.
Figure 7.17.3.1.2a-1: Release ad hoc group data communication by an authorized user
1. It is assumed that MCData users on MCData client 1, client 2 and client 3 are already part of the ongoing ad hoc group data communication.
2. The authorized MCData user on MCData client 1 would like to release the MCData ad hoc group data communication which is ongoing and sends an ad hoc group data session release request to the MCData server.
3. MCData server checks whether the MCData user on MCData client 1 is authorized to release the ad hoc group data communication and generates ad hoc group data session release request to release ongoing session. The MCData server cancels the in-progress emergency state or in-progress imminent peril state of the ad hoc group if the ad hoc group data communication is an emergency or imminent peril data communication respectively.
4. The MCData server sends ad hoc group data session release request via SIP core towards MCData client 2 and MCData client 3.
5. MCData users on MCData client 2 and MCData client 3 are notified about the release of the ad hoc group data communication.
6. MCData client 2 and MCData client 3 acknowledge the ad hoc group data communication release request towards the MCData server by sending an ad hoc group data session release response.
7. The MCData server sends ad hoc group data session release response to MCData client 1.
8. MCData user on MCData client 1 is notified about the release of the ad hoc group data communication.
9. MCData client 1, client 2 and client 3 have successfully released the floor control and media plane resources associated with the ad hoc group data communication that is terminated and the ad hoc group ceases to exist (i.e., further data communication is not possible over the same ad hoc group, otherwise if the ad hoc group data communication follows an ad hoc group emergency alert the ad hoc group continues to exist (i.e., further data communications over the same ad hoc group are possible).
7.17.3.1.3 Ad hoc group data communication setup with MCData server determining the participants lists
Figure 7.17.3.1.3-1 below illustrates the ad hoc group data communication setup procedure initiated by the MCData user and MCData client 1 wherein the list of participants is determined by the MCData server based on the criteria received from the MCData client.
Pre-conditions:
1. The MCData user at MCData client 1 is authorized to initiate ad hoc group data communication.
2. The MCData user at MCData client 1 wants to invite MCData users who are satisfying certain criteria for the ad hoc group data communication.
Figure 7.17.3.1.3-1: Ad hoc group data communication participants determined by MCData server
1. User at MCData client 1 would like to initiate an ad hoc group data communication in-order to invite the participants satisfying specific criteria. The MCData client 1 initiates the ad hoc group data communication by sending the ad hoc group data session request containing the details of the criteria to be applied by the MCData server for determining the participants list. If end-to-end encryption is supported, the Encryption supported information element shall be set to true and pre-configured MCData group whose configuration is to be applied is included. An SDP offer containing the MCData client media parameters is included. If the MCData user of MCData client 1 has selected a functional alias, then the ad hoc group data session request contains that functional alias.
If the MCData user at MCData client 1 initiates an MCData emergency ad hoc group data communication or the MCData emergency state is already set for the MCData client 1 (due to a previously triggered MCData emergency alert):
i. the MCData ad hoc group data session request shall contain an emergency indicator;
ii. if the MCData emergency state is not set already, MCData client 1 sets its MCData emergency state. The MCData emergency state of MCData client 1 is retained until explicitly cancelled by the user of MCData client 1.
2. If the ad hoc group data communication is supported, the MCData server verifies whether the user at MCData client 1 is authorized to initiate an ad hoc group data communication. If not authorized, the MCData server rejects the ad hoc group data session request as specified in the step 3. The MCData server accepts the ad hoc group data session request if the ad hoc group data communication is supported and authorized.
If functional alias is present, the MCData server checks whether the provided functional alias is allowed to be used and has been activated for the user.
If location information was included in the ad hoc group data session request, the MCData server checks the privacy policy of the MCData user to decide if the location information of MCData client 1 can be provided to other users on the data communication (refer to Annex A.3 "Authorisation to provide location information to other MCData users on a data communication when talking").
If an emergency indicator is present in the received MCData ad hoc group data session request, the MCData ad hoc group is considered to be in the in-progress emergency state until this ad hoc group data communication is terminated;
If an imminent peril indicator is present in the received MCData ad hoc group data session request, the MCData ad hoc group is considered to be in the in-progress imminent peril state until this ad hoc group data communication is terminated. and
If the information received in the request in step 1 does not contain an ad hoc group ID from an ad hoc group emergency alert, the MCData server forms the ad hoc group by using received information, and determines the preconfigured group to be used for the configuration of the ad hoc group. The MCData server assigns a MCData group ID for the newly formed ad hoc group. Further, the ad hoc group participants are included to ad hoc group once determined as specified in the step 4.
3. The MCData server shall send the ad hoc group data session request return message to MCData client 1 containing the below:
i. The MCData ad hoc group ID, either generated by the MCData server, if not included in the ad hoc group call request of step 1, or if the provided MCData ad hoc group ID is not accepted by the MCData server, or provided by the MCData client 1 if the ad hoc group ID is from an ad hoc group emergency alert;
ii. The group ID of the pre-configured group to be used for the ad hoc group communication (only included when the ad hoc group data session is authorized); and
iii. Result of whether the ad hoc group data session request is authorized or not
If the ad hoc group data session request is not authorized, the MCData server and MCData client 1 shall not proceed with the rest of the steps.
4. The MCData server determines the list of participants to be invited for the ad hoc group data communication based on the information present in the information element Criteria for determining the participants. This information element could carry either criteria or indicator identifying pre-defined criteria or a combination of both. Depending on the criteria provided and based on local policy, the MCData server may modify the content of the criteria received in step 1 to determine the list of participants.
NOTE 1: The content of the Criteria information element, the details of the pre-defined criteria, and the way how their MCData server determines the list of participants are left to implementation.
5. The MCData server sends the ad hoc group data session requests towards the MCData clients 2 and 3. While sending the ad hoc group data session requests, the MCData server shall remove the information elements that are not required to be conveyed to the target MCData clients. This request carries the pre-configured group ID whose configuration is to be applied for this ad hoc group data communication if end-to-end encryption is requested. The MCData server considers the ad hoc group data communication participants as implicitly affiliated to the ad hoc group.
6. The receiving MCData clients notify their corresponding MCData user about the incoming ad hoc group data communication.
7. The receiving MCData clients may accept or reject the ad hoc group data session requests and send ad hoc group data session responses to the MCData server. The response may also contain a functional alias of the responding MCData user, which is verified (valid and activated for the user) by the MCData server.
8. The MCData server sends the ad hoc group data session response to MCData client 1 through the signalling path to inform about successful data communication establishment. The ad hoc group data session response contains the call resulting criteria used by the MCData server to determine the list of participants to be invited.
9. The MCData server may notify the initiating MCData user of all MCData users who acknowledged the ad hoc group data session request and joined the ad hoc group data communication. This notification may be sent to the initiating MCData user by the MCData server more than once during the data communication when MCData users join or leave the MCData ad hoc group data communication. If the authorized users (not shown in figure) are configured to receive the participants information of ad hoc group data communication, the MCData server provides ad hoc group data session notify about all MCData users who acknowledged the ad hoc group data session request and joined the ad hoc group data communication, and when MCData users joins or leaves the MCData ad hoc group data communication. All ad hoc group data session notify messages contain the call resulting criteria used by the MCData server to determine the list of participants to be invited.
NOTE 2: The authorized user can learn who is currently affiliated to the current adhoc group data communication.
10. MCData client 1, MCData client 2 and MCData client 3 establish media plane resources.
The MCData server continuously checks whether other MCData users meet the criteria in order to add them to the ongoing ad hoc group communication, or whether any of the participating MCData users no longer meet the criteria in order to remove them from the ongoing ad hoc group communication, according to clause 7.17.3.15.
7.17.3.1.4 Modification of ad hoc group data communication participants by an authorized user
Figure 7.17.3.1.4-1 below illustrates the modification of ad hoc group data communication participants procedure by an authorized user.
Pre-conditions:
1. An MCData ad hoc group data communication which is setup with participants list provided by the initiating MCData user as described in clause 7.17.3.1.1 or based on the criteria provided by the initiating MCData user as described in clause 7.17.3.1.3 is already in progress.
2. The participants of the MCData ad hoc group call belong to the single MCData system.
3. The MCData users on MCData client 1, MCData client 3 to MCData client n are on an ongoing ad hoc group data communication.
4. The MCData user at MCData client 1 determines to remove the user of MCData client 3 from the ad hoc group data communication and add user of MCData client 2 into the on-going ad hoc group data communication.
Figure 7.17.3.1.4-1: Modification of ad hoc group data communication participants by an authorized user
1. The MCData user at the MCData client 1 is authorized and requests to modify ad hoc group data communication participants. The MCData client 1 sends the modify ad hoc group data session participants request to the MCData server in order to remove MCData client 3 from the ongoing ad hoc group data communication and add MCData client 2 into it.
2. The MCData server verifies whether the MCData client 1 is authorized to add or remove (modify) the participants of the on-going ad hoc group data communication regardless of the original group call setup parameters. When the group participants were initially determined by the MCData server with criteria and MCData users are to be removed, the MCData server removes MCData clients and marks them so that the MCData server will not add them back to the ad hoc group call based on the criteria. Participants to be added shall be marked and kept in the ad hoc group call and shall not be removed by the MCData server even if they do not meet the call criteria.
NOTE 1: In the above case participants being removed can be added back and the participants being added can be removed by the authorized user via the modify ad hoc group call participants request.
3. The MCData server sends modify ad hoc group data session participants response to the MCData client 1.
4. The MCData server sends the ad hoc group data session leave request to the MCData client 3 in order to remove it from the on-going ad hoc group data communication.
5. The MCData client 3 notifies the user of the ad hoc group data session leave request.
6. The MCData client 3 sends the ad hoc group data session leave response to the MCData server.
7. The MCData server sends the ad hoc group data session request towards MCData client 2.
NOTE 2: Steps 8 to 10 can occur at any time following step 3.
8. The receiving MCData client 2 notifies the user about the incoming ad hoc group data communication.
9. The MCData client 2 accepts the ad hoc group data session request and send ad hoc group data session responses to the MCData server. The response may also contain a functional alias of the responding MCData user, which is verified (valid and activated for the user) by the MCData server. The MCData server considers the MCData user as implicitly affiliated to the ad hoc group.
10. The MCData server may notify the initiating MCData user of all the users who are added to the on-going ad hoc group data communication. This notification may be sent to the initiating MCData user by the MCData server more than once during the data communication when MCData users join or leave the ad hoc group data communication.
11. The MCData server may notify the participants about the change in the participants of on-going ad hoc group data communication.
7.17.3.1.5 Modification of ad hoc group data communication participants by the MCData server
Figure 7.17.3.1.5-1 below illustrates the modification of ad hoc group data communication participants procedure by the MCData server.
Pre-conditions:
1. The MCData client 1 is the initiator of the ad hoc group data communication.
2. MCData server determined the participants for the ad hoc group data communication based on the criteria specified by the MCData client 1 while initiating the ad hoc group data communication.
3. MCData server continuously evaluates the criteria to monitor the list of users who meets or not meets the criteria for participating in the on-going ad hoc group data communication.
4. The MCData server detects that the MCData client 5 satisfies the criteria and MCData client 4 stops to meet the criteria specified by the MCData client 1.
Figure 7.17.3.1.5-1: Modification of ad hoc group data communication participants by the MCData server
1. The ad hoc group data communication is established and on-going with the participants MCData client 1, MCData client 2, MCData client 3 and MCData client 4. The participants list is determined by the MCData server based on the criteria specified by the MCData client 1 while initiating the data communication.
2. The MCData server detects that the MCData client 5 satisfies the criteria specified by the MCData client 1 and checks whether it has been previously removed by an authorized user as described in clause 7.17.3.1.4. If MCData client 5 has already been removed by an authorized user, the MCData server does not add it back to the ad hoc group call and it skips step 3 to step 6. If MCData client 5 has not been already removed by an authorized user, the procedure continues with step 3..
3. The MCData server sends the ad hoc group data session request to the MCData client 5.
4. The MCData client 5 notifies the user about the incoming ad hoc group data communication.
5. The MCData client 5 accepts the ad hoc group data session request and sends the ad hoc group data session response to the MCData server.
6. The on-going ad hoc group data communication is updated by adding MCData client 5 which satisfies the criteria specified by the MCData client 1.
7. The MCData server detects that the MCData client 4 is no more satisfying the criteria to be the participant of the ad hoc group data communication and checks whether it has been previously added by an authorized user as described clause 10.17.3.1.4. If MCData client 4 has already been added by an authorized user, the MCData server does not remove it from the ad hoc group call and skips step 8 to step 11. If MCData client 4 has not been already added by an authorized user, the procedure continues with step 8.
8. The MCData server sends the ad hoc group data communication leave request to the MCData client 4 and removes it from the on-going ad hoc group data communication.
9. The MCData client 4 notifies the user of the ad hoc group data session leave request.
10. The MCData client 4 sends the ad hoc group data session leave response to the MCData server.
11. The on-going ad hoc group data communication is updated by removing MCData client 4, which no more satisfies the criteria specified by the MCData client 1.
7.17.3.1.6 Modification of ad hoc group data communication criteria by an authorized user
Figure 7.17.3.1.6-1 below illustrates the modification of ad hoc group data communication criteria procedure by an authorized user.
Pre-conditions:
1. The MCData user 1 at the MCData client 1 is authorized to modify the criteria.
2. Both the MCData server and the MCData client 1 are aware of the criteria related to the ongoing ad hoc group data communication.
Figure 7.17.3.1.6-1: Modification of ad hoc group data communication criteria by an authorized user
1. The MCData user at the MCData client 1 is authorized and requests to modify the criteria for determining the list of participants. The MCData client 1 sends the modify ad hoc group data session criteria request to the MCData server which contains an updated criteria to determine the list of participants.
2. The MCData server verifies whether the MCData client 1 is authorized to modify the criteria which determines the list of participants during on-going ad hoc group data communication. The MCData server determines the list of ad hoc group call participants based on the criteria provided and the added/removed participant by the authorized user as marked in clause 7.17.3.1.4.
If MCData client 3 satisfies the new criteria to be removed and
- has already been added by an authorized user, the MCData server does not remove it from the call and skips the step 4 to step 6.
- has not been already added by an authorized user, the procedure continues with step 4.
If MCData client 2 satisfies the new criteria to be added and
- is the removed participant from the authorized user, the MCData server does not add it back to the call and skips the step 7 to step 9.
- is not the removed participant from the authorized user, the procedure continues with step 4.
Depending on the criteria provided and based on local policy, the MCData server may modify the content of the criteria received in step 1 to determine the list of participants.
3. The MCData server sends modify ad hoc group data session criteria response containing the call resulting criteria used by the MCData server to determine the list of participants to be invited to the MCData client 1.
4. The MCData server sends the ad hoc group data session leave request to the MCData client 3 in order to remove it from the on-going ad hoc group data communication.
5. The MCData client 3 notifies the user of the ad hoc group data session leave request.
6. The MCData client 3 sends the ad hoc group data session leave response to the MCData server.
7. The MCData server sends the ad hoc group data session request towards MCData client 2.
NOTE 1: Steps 7 to 9 can occur at any time following step 3.
8. The receiving MCData client 2 notifies the user about the incoming ad hoc group data communication. The MCData server considers the MCData user as implicitly affiliated to the ad hoc group.
9. The MCData client 2 accepts the ad hoc group data session request and send ad hoc group data session responses to the MCData server. The response may also contain a functional alias of the responding MCData user, which is verified (valid and activated for the user) by the MCData server.
10. The MCData server may notify the initiating MCData user of all the users who are added to the on-going ad hoc group data communication. This notification may be sent to the initiating MCData user by the MCData server more than once during the data communication when MCData users join or leave the ad hoc group data communication. All ad hoc group data session notify messages contain the call resulting criteria used by the MCData server to determine the list of participants to be invited.
11. The MCData server may notify the authorized participants about the change in the participants list of on-going ad hoc group data communication. All ad hoc group data session notify messages contain the call resulting criteria used by the MCData server to determine the list of participants to be invited.
The MCData server continuously checks whether other MCData clients meet or if participating MCData clients no longer meet the criteria for the ad hoc group emergency call.
NOTE 2: If the ad hoc group call is associated with an ad hoc group emergency alert and the change of criteria caused the modification of ad hoc group call participant list then the ongoing ad hoc group emergency alert is modified accordingly.
7.17.3.2 Ad hoc group data communication involving multiple MC systems
7.17.3.2.1 Procedure for ad hoc group data communication setup – Participants list provided by the Initiator
Figure 7.17.3.2.1-1 illustrates the procedure for ad hoc group data communication setup procedure initiated by an authorized user wherein either a list of participants or an ad hoc group ID from an ad hoc group emergency alert is provided by the authorised user and the determined MCData users are from multiple MCData systems.
Pre-conditions:
1. The security aspects of sharing the user information between primary and partner MC systems shall be governed as per the service provider agreement between them. In this case, it is considered that the partner MC system shares their users' information to the primary MC system.
2. The authorized MCData user/dispatcher belongs to the primary MC system.
3. The MCData server of the primary MC system is where the authorized MCData user/dispatcher creates the ad hoc group.
4. Some users of the ad hoc group belong to partner MC systems.
5. The preconfigured group identity and preconfigured group configuration (e.g. security related information) to be used for an ad hoc group have been preconfigured in the MCData client and other participants of ad hoc group have also received the relevant security related information to allow them to communicate in an ad hoc group communication.
6. If an ad hoc group ID from an ad hoc group emergency alert is used to invite the ad hoc group members, MCData client is aware of the ad hoc group ID.
Figure 7.17.3.2.1-1: Ad hoc group data communication setup
1. The MCData client of the authorized user initiates an ad hoc group data communication with multiple users from primary and partner MC systems. An ad hoc group data session request message with the information of the participants MCData IDs or an ad hoc group ID if the ad hoc group data session follows an ad hoc group emergency alert is routed to the MCData server of the primary MC system.
2. If the ad hoc group data session is supported, the MCData server of the primary MC system verifies whether the user at MCData client is authorized to initiate an ad hoc group communication. If not authorized, the MCData server of the primary MC system rejects the ad hoc group data session request as specified in the step 3.
If the information received in the request in step 1 does not contain an ad hoc group ID from an ad hoc group emergency alert, the MCData server of the primary MC system forms the ad hoc group by using information received in step 1 and further determines the preconfigured group to be used for the configuration (e.g. security related information). The MCData server assigns an MCData ad hoc group ID for the newly formed ad hoc group.
If no MCData ad hoc group ID was included in the ad hoc group data session request of step 1, or if the provided MCData ad hoc group ID is not accepted by the MCData server, the MCData server assigns a MCData group ID for the newly formed ad hoc group. The MCData server considers the ad hoc group communication participants as implicitly affiliated to the ad hoc group.
NOTE 1: The newly formed ad hoc group information including the MCData group ID and the list of users is held in dynamic data in the MCData server.
3. The MCData server shall send the ad hoc group data session request return message to MCData client containing the below:
i. The MCData ad hoc group ID either generated by the MCData server or provided by the MCData client if the ad hoc group ID is from an ad hoc group emergency alert (only included when the ad hoc group data session request is authorized);
ii. The group ID of the pre-configured group to be used for the ad hoc group data communication (only included when the ad hoc group data session request is authorized); and
iii. Result of whether the ad hoc group data session request is authorized or not.
If the ad hoc group data session request is not authorized, MCData client 1 shall not proceed with the rest of the steps.
4. The MCData server of the primary MC system sends the ad hoc group data session request to the group members of the ad hoc group belonging to the primary MC system. While sending the ad hoc group data session requests, the MCData server shall remove the information elements that are not required to be conveyed to the target MCData clients (e.g. MCData ID list of the users who are required to acknowledge).
5a-5b. The MCData clients receive in the ad hoc group data session request with the information of the MCData group ID for the ad hoc group and further notify their corresponding MCData user. The group members of the ad hoc group of the primary MC system may accept or reject the ad hoc group data session requests and respond with the ad hoc group data session responses.
6. The primary MCData server further initiates an ad hoc group data session request message to the MCData users of the partner MC system. The ad hoc group data session request message is routed to the MCData users via the MCData server of the partner MC system.
7a-7b. The MCData clients receive in the ad hoc group data session request the information of the MCData group ID for the ad hoc group and further notify their corresponding MCData user. The MCData users upon receipt of the invitation may accept or reject the ad hoc group data session requests, and respond with the ad hoc group data session responses. The ad hoc group data session response message is routed to the MCData server of the primary MC system via the MCData server of the partner MC system.
8. The MCData server of the primary MC system provides an ad hoc group data session response message to the MCData client of the authorized MCData user upon receiving response to the corresponding ad hoc group data session request in step 1. The ad hoc group data session response will consist of the success or failure result and/or detailed reason information in case of failure.
NOTE 2: The ad hoc group data session response messages may be used by The MCData client of the authorized user to determine if the ad hoc group communication will proceed.
9. Upon successful ad hoc group data session setup, a group data communication is established amongst the group members from primary and partner MC systems. The media plane resources for data communication are established.
7.17.3.2.2 Procedure for ad hoc group data communication release by MCData server – Participants list provided by the Initiator
This procedure focuses on the case where an MCData server initiates the termination of an ongoing MCData ad hoc group data communication for all the participants of that group data communication, since at least one of the termination conditions are met e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or minimum number of affiliated MCData group members are not present.
Procedures in figure 7.17.3.2.2-1 are the signalling control plane procedures for the MCData server initiating termination of an ongoing MCData ad hoc group data communication.
Pre-condition:
- The MCData client 1 and MCData client 2 belong to primary MC system. The MCData client 3 belongs to partner MC system.
- The MCData users on MCData client 1, client 2 and client 3 are already part of the ongoing ad hoc group data communication (e.g. as a result of ad hoc group data communication setup as specified in clause 7.17.3.2.1).
Figure 7.17.3.2.2-1: Ad hoc group data communication release
1. The MCData server determines to release the ongoing ad hoc group data communication e.g., due to a hang timer expiry, last participant leaving, second last participant leaving, initiator leaving, or a minimum number of affiliated MCData group members not present.
2. The MCData server identifies the participants of the ongoing ad hoc group data communication and generates ad hoc group data session release request to release ongoing data communication.
3. The MCData server sends an ad hoc group data session release request to each participant of the ongoing group data communication. If the participants belong to the partner MC system, then the ad hoc group data session release request is routed to the MCData clients of the partner MC system via the partner MCData server.
4. The MCData users are notified about the release of the ad hoc group data communication.
5. The MCData client(s), send an acknowledgment to the MCData server by sending an ad hoc group data session release response. The ad hoc group data session release response message is routed to the MCData server of the primary MC system via the MCData server of the partner MC system.
6. The MCData client 1, client 2 and client 3 have successfully released media plane resources associated with the ad hoc group data communication that is terminated. The primary MCData server removes the ad hoc group information from the dynamic data and thus the ad hoc group ceases to exist.
7.17.3.2.3 Ad hoc group data communication setup – Participants list determined by the MCData server
Figure 7.17.3.2.3-1 below illustrates the ad hoc group data communication setup procedure initiated by an authorized user wherein the list of participants is determined by the MCData server based on the criteria received from the MCData client and determined MCData users are from multiple MCData systems.
Pre-conditions:
1. The security aspects of sharing the user information between primary and partner MC systems shall be governed as per the service provider agreement between them. In this case, it is considered that the partner MC system share their users' information to the primary MC system.
2. The authorized MCData user/dispatcher belongs to the primary MC system.
3. The MCData server 1 of the primary MC system is where the authorized MCData user/dispatcher creates the ad hoc group.
4. Some users of the ad hoc group may belong to MCData server 2 of the partner MC systems.
5. The pre-configured group identity and pre-configured group configuration to be used for an ad hoc group have been preconfigured in MCData client and other participants of ad hoc group have also received the relevant security related information to allow them to communicate in an ad hoc group communication.
Figure 7.17.3.2.3-1: Ad hoc group data communication setup involving multiple MCData systems
1-3. Same as described in subclause 7.17.3.1.1.
4. The MCData server 1 determines the list of participants from the primary MC system and determines the partner MC system to be involved in the ad hoc group data communication based on the information present in the information element Criteria for determining the participants. This information element carries the criteria, indicator identifying pre-defined criteria, or a combination of both. Depending on the criteria provided and based on local policy, the MCData server may modify the content of the criteria received in step 1 to determine the list of participants.
NOTE 1: The content of the Criteria information element, the details of the pre-defined criteria, and the way how the MCData server determines the list of participants are left to implementation.
5. The MCData server 1 needs to involve the partner MC system based on the agreement and based on the criteria for determining the participants list, it sends the ad hoc group data session get userlist request to the MCData server 2. This request carries the data session resulting criteria to be used by the partner MC system as determined in step 4.
6. MCData server 2 evaluates the criteria and determines the participants satisfying the criteria (i.e. MCData client 3 and MCData client 4) and sends the response containing the list of MCData users satisfying the criteria. The MCData server 2 may apply local policies if any while determining the participants satisfying the criteria.
7. The MCData server 1 compiles the list of participants to be invited for the ad hoc group data communication including the participants from both primary and partner MC system.
8a-8b. The MCData server 1 sends the ad hoc group data session request towards the MCData client 3 and MCData client 4 via MCData server 2. While sending the ad hoc group data session request, the MCData server shall remove the information elements that are not required to be conveyed to the target MCData clients. This request carries the pre-configured group ID whose configuration is to be applied for this ad hoc group data communication if end-to-end encryption is requested. The MCData server 1 considers the ad hoc group communication participants as implicitly affiliated to the ad hoc group.
9. The MCData server 1 sends the ad hoc group data session request towards the MCData client 2. While sending the ad hoc group data session request, the MCData server shall remove the information elements that are not required to be conveyed to the target MCData clients. This request carries the pre-configured group ID whose configuration is to be applied for this ad hoc group data communication if end-to-end encryption is requested.
10a-10c. The MCData clients receive incoming ad hoc group data communication and further notify their corresponding MCData users.
11. The MCData client 2 accepts the ad hoc group data session request, and sends ad hoc group data session response to the MCData server 1.
12. The MCData client 3 accepts the ad hoc group data session request, and sends ad hoc group data session response to the MCData server 1 via MCData server 2.
13. The MCData client 4 accepts the ad hoc group data session request, and sends ad hoc group data session response to the MCData server 1 via MCData server 2.
14. The MCData server 1 sends the ad hoc group data session response to MCData client 1 through the signalling path to inform about result of the participants responses. The ad hoc group data session response contains the data session resulting criteria used by the MCData server to determine the list of participants to be invited.
15. The MCData server 1 may notify the initiating MCData user of all MCData users who acknowledged the ad hoc group data session request and joined the ad hoc group data communication. The MCData server 1 more than once during the data communication may send this notification to the initiating MCData user whenever an MCData user joins or leaves the MCData ad hoc group data communication. If the authorized users (not shown in figure) are configured to receive the participants information of ad hoc group data communication, the MCData server provides ad hoc group data session notify about all MCData users who acknowledged the ad hoc group data session request and joined the ad hoc group data communication, and when MCData users joins or leaves the MCData ad hoc group data communication. All ad hoc group data session notify messages contain the data session resulting criteria used by the MCData server to determine the list of participants to be invited.
16. The MCData client 1, MCData client 2, MCData client 3 and MCData client 4 establish media plane resources for data communication.
The MCData server at the primary MC system and MCData server at the partner MC system continuously check whether other MCData users in the primary MC system and MCData users in the partner MC system, respectively, meet the criteria in order to add them to the ongoing ad hoc group communication, or whether any of the participating MCData users in the primary MC system and MCData users in the partner MC system, respectively, no longer meet the criteria in order to remove them from the ongoing ad hoc group communication, according to clause 7.17.3.2.4.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.3.2.4 Modifying of ad hoc group data communication participants by the MCData server
| Figure 7.17.3.2.4-1 below illustrates the MCData server modifying the ad hoc group data communication participants procedure involving multiple MCData systems.
Pre-conditions:
1. The MCData user at MCData client 1 is authorized to initiate ad hoc group data communication.
2. The MCData server 1 of the primary and MCData server 2 of the partner MCData systems determined the participants for the ad hoc group data communication based on the criteria specified by the MCData client 1 while initiating the ad hoc group data communication.
3. The ad hoc group data communication is established and on-going with the participants MCData client 1, MCData client 2, and MCData client 4. The participants list is determined by both primary and partner MC systems.
4. The MCData server 1 of the primary and MCData server 2 of the partner MCData systems continuously evaluates the criteria to monitor the list of users who meets or not meets the criteria for participating in the on-going ad hoc group data communication.
5. The MCData server 1 of the primary MCData system detects that the MCData client 3 meets the criteria and MCData client 2 stops to meet the criteria specified by the MCData client 1.
6. The MCData server 2 of the partner MCData system detects that the MCData client 5 meets the criteria and MCData client 4 stops to meet the criteria specified by the MCData client 1.
Figure 7.17.3.2.4-1: Modification of ad hoc group data communication participants by the MCData server
1. The MCData server 1 detects that MCData client 3 now meets criteria and successfully added to group data communication.
2. The MCData server 1 detects that MCData client 2 does not meet criteria any more and successfully removed from a group data communication.
3. The MCData server 2 detects that the MCData client 5 meets the criteria specified by the MCData client 1.
4. The MCData server 2 sends the notification to MCData server 1 of the primary MCData system to add the MCData user at MCData client 5 to on-going ad hoc group data communication.
5. The MCData server 1 sends the ad hoc group data session request to the MCData client 5 via MCData server 2.
6. The MCData client 5 notifies the user about the incoming ad hoc group data communication.
7. The MCData client 5 accepts the ad hoc group data session request and sends the ad hoc group data session response to the MCData server 1 via MCData server 2.
8. The on-going ad hoc group data communication is updated by adding MCData client 5 which meets the criteria specified by the MCData client 1.
9. The MCData server 2 detects that the MCData client 4 is no longer satisfying the criteria to be the participant of the ad hoc group data communication.
10. The MCData server 2 sends the notification to MCData server 1 of the primary MCData system to remove the MCData user at MCData client 4 from on-going ad hoc group data communication.
11. The MCData server 1 sends the ad hoc group data session leave request to the MCData client 4 and removes it from the on-going ad hoc group data communication via MCData server 2.
12. The MCData client 4 notifies the user of the ad hoc group data session leave request.
13. The MCData client 4 sends the ad hoc group data session leave response to the MCData server 1 via MCData server 2.
14. The on-going ad hoc group data communication is updated by removing MCData client 4, which no longer meets the criteria specified by the MCData client 1.
7.17.3.2.5 Release ad hoc group data communication and stop determining the ad hoc group data communication participants by partner MCData system – Participants list determined by the MCData server
Figure 7.17.3.2.5-1 below illustrates the release of ad hoc group data communication and stopping of MCData server at the partner MC system from determining the ad hoc group data communication participants’ procedure once involving multiple MCData systems. This procedure, in particular describes about how the partner MC system is notified about ad hoc group data communication release to cease the determining of the participants by the partner MC system.
Pre-conditions:
1. The MCData user at MCData client 1 is authorized to initiate ad hoc group data communication.
2. The ad hoc group data communication is established and on-going with the participants MCData client 1, MCData client 2, MCData client 3, and MCData client 4.
3. The MCData server 1 of the primary and MCData server 2 of the partner MCData systems determined the participants for the ad hoc group data communication based on the criteria specified by the MCData client 1 while initiating the ad hoc group data communication.
4. The MCData server 1 of the primary and MCData server 2 of the partner MCData systems continuously evaluates the criteria to monitor the list of users who meets or not meets the criteria for participating in the on-going ad hoc group data communication.
Figure 7.17.3.2.5-1: MCData server releases an ad hoc group data communication and stops the determination of ad hoc group data communication participants involving multiple MCData systems
1. The MCData server 1 detects that the ad hoc group data communication which is ongoing is to be released e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or minimum number of affiliated MCData group members are not present.
2. The MCData server 1 sends the ad hoc group data session release notification to MCData server 2 of the partner MCData system about the ad hoc group data communication release to stop determining the participants list by MCData server 2 of the partner MCData system.
3a-3d. The MCData server 1 sends ad hoc group data session release request to all the participants of the ad hoc group data communication. MCData client 3/MCData client 4 which belong to the partner MCData system, receive the ad hoc group data session release request via the partner MCData server 2 from MCData server 1 of the primary MCData system.
4a-4d. The MCData clients notifies the user about the release of the ad hoc group data communication.
5a-5d. All the participants of the ad hoc group data communication receive the ad hoc group data session release request and send the ad hoc group data session release response to the MCData server 1 of the primary MCData server. MCData client 3/MCData client 4 which belong to the partner MCData system, send the ad hoc group data session release response via the partner MCData server 2 to the MCData server 1 of the primary MCData system.
7.17.3.2.6 Modification of ad hoc group data communication participants by an authorized user
Figure 7.17.3.2.6-1 below illustrates the MCData user modifying the ad hoc group data communication participants procedure involving multiple MCData systems.
Pre-conditions:
1. An MCData ad hoc group data communication is already in progress the participants list provided by the originating MCData user while initiating the MCData ad hoc group data communication.
2. The participants of the MCData ad hoc group data communication belongs to the multiple MCData system.
3. The MCData user at MCData client 1 determines that the MCData client 3 needs to be invited to on-going ad hoc group data communication and MCData client 2 needs to be removed from the on-going ad hoc group data communication from the primary MCData system.
4. The MCData user at MCData client 1 determines that the MCData client 5 needs to be invited to on-going ad hoc group data communication and MCData client 4 needs to be removed from the on-going ad hoc group data communication from the partner MCData system.
Figure 7.17.3.2.6-1: Modification of ad hoc group data communication participants by an authorized user
1. The MCData client 1 sends the modify ad hoc group data session participants request to the MCData server 1 to remove both MCData client 2 and MCData client 4 from the on-going ad hoc group data communication and to add both MCData client 3 and MCData client 5 into on-going ad hoc group data communication.
2. The MCData server 1 verifies whether the MCData client 1 is authorized to add or remove (modify) the participants of the on-going ad hoc group data communication.
3. The MCData server 1 sends modify ad hoc group data session participants response to the MCData client 1.
4. The MCData server 1 determines that MCData client 1 has requested that MCData client 3 from the primary MC system be invited to an on-going ad hoc group data communication and successfully added to the data communication according to the procedure defined in clause 7.17.3.1.4.
5. The MCData server 1 determines that MCData client 1 has requested that MCData client 2 from the primary MC system be removed from the on-going ad hoc group data communication and successfully removed from data communication according to the procedure defined in clause 7.17.3.1.4.
6. The MCData server 1 determines that MCData client 1 has requested that MCData client 5 from the partner MC system be invited to an on-going ad hoc group data communication. The MCData server 1 sends the ad hoc group data session request to the MCData client 5 via MCData server 2.
7. The MCData client 5 notifies the user about the incoming ad hoc group data communication.
8. The MCData client 5 accepts the ad hoc group data session request and sends the ad hoc group data session response to the MCData server 1 via MCData server 2.
9. The on-going ad hoc group data communication is updated by adding MCData client 5 which is based on the modify participant list provided by the MCData client 1.
10. The MCData server 1 determines that MCData client 1 has requested that MCData client 4 from the partner MC system be removed from the on-going ad hoc group data communication. The MCData server 1 sends the ad hoc group data session leave request to the MCData client 4 via MCData server 2.
11. The MCData client 4 notifies the user of the ad hoc group data session leave request.
12. The MCData client 4 sends the ad hoc group data session leave response to the MCData server 1 via MCData server 2.
13. The on-going ad hoc group data communication is updated by removing MCData client 4, which is based on the modify participant list provided by the MCData client 1.
14. The MCData server 1 may notify the initiating MCData user of all the users who are added to the on-going ad hoc group data communication. This notification may be sent to the initiating MCData user by the MCData server more than once during the data communication when MCData users join or leave the ad hoc group data communication.
15. The MCData server 1 may notify the authorized participants about the change in the participants list of on-going ad hoc group data communication.
7.17.3.2.7 Modification of ad hoc group data session criteria by an authorized user
Figure 7.17.3.2.7-1 illustrates the modification of ad hoc group data session criteria procedure by the initiator of the ad hoc group data session between multiple MC systems.
Preconditions:
- The MCData user at the MCData client 1 is authorized to modify the criteria.
- The MCData server A and MCData server B are aware of the criteria related to the ongoing ad hoc group data session.
- MC system A and MC system B are interconnected.
Figure 7.17.3.2.7-1: Modifying the criteria for determining the participants during an ongoing ad hoc group data session between multiple MC systems
1. An ad hoc group data session has been established based on criteria sent by an authorized MCData client upon initiating the ad hoc group data session.
2. The MCData user at the MCData client 1 is authorized and wishes to modify the criteria for determining the list of ad hoc group data session participants.
3a. MCData client 1 sends a modify ad hoc group data session criteria request to MCData server A.
3b. MCData server A determines that the modify ad hoc group data session criteria request received in step 3a has impact on users in MCData server B. Depending on the criteria provided and based on local policy, the MCData server may modify the content of the criteria received in step 3a to determine the list of participants before sending it to MCData server B.
3c. MCData server A sends a modify ad hoc group data session criteria request to MCData server B containing the data session resulting criteria to be used by MCData server B.
NOTE 1: If MCData server A identifies that the criteria require to add participants from another MC system then MCData server A sends an ad hoc group data session request to the MCData server in that MC system.
4a/b. The MCData server A receives the ad hoc group data session criteria modify response and forwards the response to MCData client 1 in MC system A
5. MCData server B detects that MCData client 3 meets the criteria for the ongoing ad hoc group data session initiated at MC system A.
5a. MCData server B sends an ad hoc group data session add user notification message towards MCData server A.
5b. MCData server A sends an ad hoc group data session request towards MCData client 3 via MCData server B.
5c. The MCData user 3 is notified of entering an ongoing ad hoc group data session.
5d. MCData client 3 sends an ad hoc group data session response towards MCData server A via MCData server B.
5e. MCData server B sends an ad hoc group data session remove user notification message towards MCData server A.
5f. MCData server A sends an ad hoc group data session leave request towards MCData client 4 via MCData server B.
5g. The MCData user 4 is notified of leaving an ongoing ad hoc group data session.
5h. MCData client 4 sends an ad hoc group data session leave response towards MCData server A via MCData server B.
6. The MCData server A may notify the authorised MCData user of all the users who are added to the on-going ad hoc group data session. This notification may be sent to the authorised MCData user by the MCData server A more than once during the data session when MCData users join or leave the ad hoc group data session. All ad hoc group data session notify messages contain the call resulting criteria used by the MCData server to determine the list of participants to be invited.
7. The MCData server A adds MCData client 3 to the ad hoc group data session and removes MCData client 4 from the ad hoc group data session.
The MCData servers continuously check whether other MCData clients meet or if participating MCData clients no longer meet the criteria for the ad hoc group data session.
NOTE 2: If the ad hoc group data session is associated with an ad hoc group emergency alert and the change of criteria caused the modification of the ad hoc group data session participant list then the ongoing ad hoc group emergency alert is modified accordingly.
7.17.4 Ad hoc group short data service data communication procedures
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.4.1 General
| This subclause contains procedures for ad hoc group short data service data communication across a single MCData system, and uses the common procedures defined in the subclause 7.17.3 in conjuction with the procedures defined in this subclause. Other common procedures specified in the 7.17.3 are used at any time after Ad hoc group short data service data communication establishment based on the need of it. These procedures are applicable for Group standalone short data service using media plane and Group short data service session as specified in the subclause 7.4.2.6 and subclause 7.4.2.7 respectively.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.4.2 Information flows for short data service specific
| Table 7.17.4.2-1 describes the information elements that are specific to short data service and are used along with the common information flows defined in the subclause 7.17.2 for the Ad hoc group short data service data communication. These information elements are included when an Ad hoc group data session request sent from the MCData client to the MCData server, between the MCData servers, and from the MCData server to the MCData client.
Table 7.17.4.2-1: short data service specific
Information element
Status
Description
Conversation Identifier
M
Identifies the conversation
Transaction Identifier
M
Identifies the MCData transaction
Reply Identifier
O
Identifies the original MCData transaction to which the current transaction is a reply to
Transaction type
M
Session based transactions
Disposition Type
O
Indicates the disposition type expected from the receiver (i.e., delivered or read or both)
Payload Destination Type
M
Indicates whether the SDS payload is for application consumption or MCData user consumption
Application identifier (see NOTE 1)
O
Identifies the application for which the payload is intended (e.g. text string, port address, URI)
Application metadata container
O
Implementation specific information that is communicated to the recipient
NOTE 1: The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption.
7.17.4.3 Ad hoc group short data service data communication procedures in single MCData system
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.4.3.1 General
| The initiation of Ad hoc group SDS session results in ad hoc group participants exchanging SDS data.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.4.3.2 Procedure
| The procedure in figure 7.17.4.3.2-1 describes the case where an MCData user is initiating SDS data communication session with an MCData ad hoc group for exchanging SDS data transactions between the ad hoc group participants, with or without disposition request.
Pre-conditions:
1. As defined in the subclause 7.17.3.1.1.
Figure 7.17.4.3.2-1: Ad hoc group SDS data communication session
1. User at MCData client 1 initiate an ad hoc group data communication as specified in the subclause 7.17.3.1.1.
2. MCData client 1 and the ad hoc group data session request accepted clients have successfully established media plane for data communication and either MCData client can transmit SDS data. The MCData data request may contain disposition request if indicated by the client sending data. If the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the SDS data receiving MCData users may be notified, otherwise those MCData users shall not be notified.
3. If MCData data disposition was requested by the user, then the SDS data receiving MCData client initiates a MCData data disposition notification for delivery, read reports to the disposition requesting user. The MCData data disposition notification from the receiving MCData clients may be stored by the MCData server for disposition history interrogation from authorized users.
4. Based on the MCData user action or conditions to release, the established media plane for SDS data exchange is released as specified in the subclause 7.17.3.1.2.
7.17.4.4 Ad hoc group short data service data communication procedures involving multiple MC systems
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.4.4.1 General
| The initiation of Ad hoc group SDS session results in ad hoc group participants exchanging SDS data.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.4.4.2 Procedure
| The procedure in figure 7.17.4.4.2-1 describes the case where an MCData user is initiating SDS data communication session with an MCData ad hoc group for exchanging SDS data transactions between the ad hoc group participants, with or without disposition request.
Pre-conditions:
1. As defined in the Common Ad hoc group data communication procedures of subclause 7.17.3.2.1 or subclause 7.17.3.2.3.
Figure 7.17.4.4.2-1: Ad hoc group SDS data communication session
1. User at MCData client 1 initiate an ad hoc group data communication as specified in the subclause 7.17.3.2.1 or subclause 7.17.3.2.3.
2. MCData client 1 and the ad hoc group data session request accepted clients have successfully established media plane for data communication and either MCData client can transmit SDS data. The MCData data request may contain disposition request if indicated by the client sending data. If the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the SDS data receiving MCData users may be notified, otherwise those MCData users shall not be notified.
3. If MCData data disposition was requested by the user, then the SDS data receiving MCData client initiates a MCData data disposition notification for delivery, read reports to the disposition requesting user. The MCData data disposition notification from the receiving MCData clients may be stored by the MCData server for disposition history interrogation from authorized users.
4. Based on the MCData user action or conditions to release, the established media plane for SDS data exchange is released as specified in the subclause 7.17.3.2.2 or subclause 7.17.3.2.5.
7.17.5 Ad hoc group file distribution communication procedures
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.5.1 General
| This subclause contains procedures for ad hoc group file distribution communication across a single MCData system, and uses the common procedures defined in the subclause 7.17.3 in conjuction with the procedures defined in this subclause. Other common procedures specified in the 7.17.3 are used at any time after Ad hoc group file distribution communication establishment based on the need of it.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.5.2 Information flows for file distribution specific
| Table 7.17.5.2-1 describes the information elements that are specific to file distribution and are used along with the common information flows defined in the subclause 7.17.2 for the Ad hoc group short data service data communication. These information elements are included when an Ad hoc group data session request sent from the MCData client to the MCData server, between the MCData servers, and from the MCData server to the MCData client.
Table 7.17.5.2-1: file distribution specific
Information element
Status
Description
Conversation Identifier
M
Identifies the conversation
Transaction Identifier
M
Identifies the MCData transaction
Reply Identifier
O
Identifies the original MCData transaction to which the current transaction is a reply to
Disposition indication
O
Indicates whether file download completed report is expected or not
Download indication
O
Indicates mandatory download (i.e. auto accept this media plane setup request)
Application metadata container
O
Implementation specific information that is communicated to the recipient
7.17.5.3 Ad hoc group file distribution communication procedures in single MCData system
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.5.3.1 General
| The initiation of Ad hoc group standalone FD using media plane results in ad hoc group participants exchanging SDS data.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.5.3.2 Procedure
| The procedure in figure 7.17.5.3.2-1 describes the case where an MCData user is initiating ad hoc group standalone data communication for sending file to multiple MCData users, with or without download completed report request.
Pre-conditions:
1. As defined in the Common Ad hoc group data communication procedures of subclause 7.17.3.1.1.
Figure 7.17.5.3.2-1: Ad hoc group SDS data communication session
1. User at MCData client 1 initiate an ad hoc group data communication as specified in the subclause 7.17.3.1.1.
2. MCData client 1 and MCData server have successfully established media plane for file transmission and the MCData client 1 transmits the file data. MCData server distributes the file received from MCData client 1 to MCData clients 2 to n over the established media plane. Distribution of file can be via unicast or via MBMS bearer(s).
3. The dispositions notifications are handled as specified in the subclause 7.5.2.7.
4. Based on the MCData user action or conditions to release, the established media plane for FD communication is released as specified in the subclause 7.17.3.1.2.
7.17.5.4 Ad hoc group file distribution communication procedures involving multiple MC systems
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.5.4.1 General
| The initiation of Ad hoc group standalone FD using media plane results in ad hoc group participants exchanging FD data.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.5.4.2 Procedure
| The procedure in figure 7.17.5.4.2-1 describes the case where an MCData user is initiating ad hoc group standalone data communication for sending file to multiple MCData users, with or without download completed report request.
Pre-conditions:
1. As defined in the Common Ad hoc group data communication procedures of subclause 7.17.3.2.1 or subclause 7.17.3.2.3.
Figure 7.17.5.4.2-1: Ad hoc group FD data communication session
1. User at MCData client 1 initiate an ad hoc group data communication as specified in the subclause 7.17.3.2.1 or subclause 7.17.3.2.3.
2. MCData client 1 and MCData server have successfully established media plane for file transmission and the MCData client 1 transmits the file data. MCData server distributes the file received from MCData client 1 to MCData clients 2 to n over the established media plane. Distribution of file can be via unicast or via MBMS bearer(s).
3. The dispositions notifications are handled as specified in the subclause 7.5.2.7.
4. Based on the MCData user action or conditions to release, the established media plane for FD communication is released as specified in the subclause 7.17.3.2.2 or subclause 7.17.3.2.5.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.6 Ad hoc group standalone short data service using signalling control plane
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.6.1 Information flows
| 7.17.6.1.1 Determine ad hoc group request (MCData client – MCData server)
Table 7.17.6.1.1-1 describes the information flow for the Determine ad hoc group request sent from the MCData client to the MCData server.
Table 7.17.6.1.1-1: Determine ad hoc group request (MCData client – MCData server)
Information element
Status
Description
MCData ID
M
The identity of the MCData user sending the request
Functional alias
O
The associated functional alias of the MCData user sending request.
Encryption supported
M
Indicates whether ad hoc group data transfer support requires end-to-end encryption.
MCData ID list (see NOTE 1, NOTE 2)
O
MCData IDs for the ad hoc group standalone short data service.
Criteria for determining the participants (see NOTE 2)
O
Carries the details of criteria or meaningful label identifying the criteria or the combination of both which will be used by the MCData server for determining the list of MCData users e.g., it can be a location based criteria to SDS data transfer in a particular area.
NOTE 1: This element is included only when the the ad hoc group standalone short data service initiating client sends the list of MCData users.
NOTE 2: Only one of these information elements is present.
7.17.6.1.2 Determine ad hoc group response (MCData server – MCData client)
Table 7.17.6.1.2-1 describes the information flow Determine ad hoc group response from the MCData server to the MCData client. This response to provide the server assigned MCData ad hoc group ID and preconfigured group identity of preconfigured group from which the configurations to be used (e.g. security related information).
Table 7.17.6.1.2-1: Determine ad hoc group response information elements
Information Element
Status
Description
MCData ID
M
The identity of the MCData user sending the request`
MCData ad hoc group ID (see NOTE 1)
O
The MCData group ID to be associated with the ad hoc group standalone short data service which is generated and assigned by the MCData server.
Preconfigured MCData group ID (see NOTE 2)
O
Group identity whose configuration is to be applied for ad hoc group standalone short data service.
Result
M
Result of the Determine ad hoc group request (success or failure)
Call resulting criteria for determining the participants (see NOTE 3)
O
Carries the details of criteria or meaningful label identifying the criteria or the combination of both that the MCData server used for determining the participants e.g., it can be a location based criteria to invite participants in a particular area
NOTE 1: If the result is success then this IE shall be included
NOTE 2: If the result is success and the end-to-end encryption is required, then this IE shall be included.
NOTE 3: This IE shall be present if the ad hoc group data communication is based on criteria.
7.17.6.1.3 Ad hoc group standalone data request (MCData client – MCData server)
Table 7.17.6.1.3-1 describes the information flow for the Ad hoc group standalone data request sent from the MCData client to the MCData server.
Table 7.17.6.1.3-1: Ad hoc group standalone data request (MCData client – MCData server)
Information element
Status
Description
MCData ID
M
The identity of the MCData user sending data
Functional alias
O
The associated functional alias of the MCData user sending data.
MCData ad hoc group ID (see NOTE 1)
M
The MCData group ID to be associated with the ad hoc group standalone short data service
Preconfigured MCData group ID (see NOTE 2)
O
Group identity whose configuration is to be applied for ad hoc group standalone short data service.
Conversation Identifier
M
Identifies the conversation
Transaction Identifier
M
Identifies the MCData transaction
Emergency indicator (see NOTE 3)
O
Indicates that the data request is for emergency ad hoc group standalone short data service
Imminent peril indicator (see NOTE 3)
O
Indicates that the data request is for imminent peril ad hoc group standalone short data service
Disposition Type
O
Indicates the disposition type expected from the receiver (i.e., delivered or read or both)
MCData ID list (see NOTE 4)
O
The specified MCData users who should send a disposition notification message.
Payload Destination Type
M
Indicates whether the payload is for application consumption or MCData user consumption
Location
O
Location of the Originating MCData user sending the SDS
Application identifier (see NOTE 5)
O
Identifies the application for which the payload is intended (e.g. text string, port address, URI)
Application metadata container
O
Implementation specific information that is communicated to the recipient
Payload
M
SDS content
Time to live
O
Indicates how long the ad hoc group is persisted and members can respond to the data transfer (e.g. duration for 5 mins or till certain future time).
NOTE 1: The MCData ad hoc group ID is determined prior to by using the Determine ad hoc group request.
NOTE 2: If end-to-end encryption is required, then this element is included and the value is determined prior to by using the Determine ad hoc group request.
NOTE 3: If used, only one of these information elements shall be present.
NOTE 4: If Disposition Type IE is not present, this IE shall not be present. If Disposition Type IE is present but this IE is not, which indicates that all receivers shall respond with disposition notification message.
NOTE 5: The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption.
7.17.6.1.4 Ad hoc group standalone data request (MCData server – MCData client)
Table 7.17.6.1.4-1 describes the information flow for the Ad hoc group standalone data request sent from the MCData server to the MCData client.
Table 7.17.6.1.4-1: Ad hoc group standalone data request (MCData server – MCData client)
Information element
Status
Description
MCData ID
M
The identity of the MCData user sending data
Functional alias
O
The associated functional alias of the MCData user sending data.
MCData ad hoc group ID
M
The MCData group ID associated with ad hoc group standalone short data service
Preconfigured MCData group ID (see NOTE 1)
O
Group identity whose configuration is to be applied for this ad hoc group standalone short data service.
MCData ID
M
The identity of the MCData user towards which the data is sent
Conversation Identifier
M
Identifies the conversation
Transaction Identifier
M
Identifies the MCData transaction
Emergency indicator (see NOTE 2)
O
Indicates that the data request is for emergency ad hoc group standalone short data service
Imminent peril indicator (see NOTE 2)
O
Indicates that the data request is for imminent peril ad hoc group standalone short data service
Disposition Type
O
Indicates the disposition type expected from the receiver (i.e., delivered or read or both)
Payload Destination Type
M
Indicates whether the payload is for application consumption or MCData user consumption
Location
O
Location of the Originating MCData user sending the SDS
Application identifier (see NOTE 3)
O
Identifies the application for which the payload is intended (e.g. text string, port address, URI)
Application metadata container
O
Implementation specific information that is communicated to the recipient
Payload
M
SDS content
Time to live
O
Indicates how long the ad hoc group is persisted and members can respond to the data transfer.
Call resulting criteria for determining the participants (see NOTE 4
O
Carries the details of criteria or meaningful label identifying the criteria or the combination of both that the MCData server used for determining the participants e.g., it can be a location based criteria to invite participants in a particular area
NOTE 1: If end-to-end encryption is required, then this element is included.
NOTE 2: If used, only one of these information elements shall be present.
NOTE 3: The application identifier shall be included only if the payload destination type indicates that the payload is for application consumption.
NOTE 4: This IE shall be present if the ad hoc group data communication is based on criteria.
7.17.6.1.5 Ad hoc group standalone data get userlist (MCData server – MCData server)
Table 7.17.6.1.5-1 describes the information flow Ad hoc group standalone data get userlist from one MCData server to another MCData server.
Table 7.17.6.1.5-1: Ad hoc group standalone data get userlist
Information element
Status
Description
MCData ad hoc group ID
M
The MCData group ID associated with the ad hoc group standalone short data service
Criteria for determining the participants
M
Carries the details of criteria or meaningful label identifying the criteria or the combination of both which will be used by the MCData server for determining the list of MCData users e.g., it can be a location based criteria to SDS data transfer in a particular area
7.17.6.1.6 Ad hoc group standalone data get userlist response (MCData server – MCData server)
Table 7.17.6.1.6-1 describes the information flow Ad hoc group standalone data get userlist response from one MCData server to another MCData server.
Table 7.17.6.1.6-1: Ad hoc group standalone data get userlist response
Information element
Status
Description
MCData ad hoc group ID
M
The MCData group ID associated with the ad hoc group standalone short data service
MCData ID list
M
List of MCData IDs meeting the criteria specified in the Ad hoc group standalone data get userlist
7.17.6.2 Ad hoc group standalone short data service using signalling control plane common procedure
7.17.6.2.1 Determine the ad hoc group and preconfigured group for end-to-end encryption
The procedure in figure 7.17.6.2.1-1 describes about determining the MCData ad hoc group ID and preconfigured group identity of preconfigured group from which the configurations to be used (e.g. security related information).
Pre-conditions:
1. The MCData users belong to primary MCData system and partner MCData system and already registered for receiving MCData service.
NOTE 1: Selection of MCData IDs of the ad hoc group members receiving the SDS data can be manual or from the user profile configuration data or by any other means. This is left for the implementation.
2. Number of ad hoc group members receiving the SDS data should be within the configured limit.
Figure 7.17.6.2.1-1: Determine ad hoc group and preconfigured group
1. The user at MCData client 1 wants to initiate an SDS data transfer to multiple MCData users with/without end-to-end encryption supported, and either by providing the list of MCData users in the request or by providing the certain criteria in the request.
2. The MCData client 1 sends a Determine ad hoc group request towards the MCData server of the primary MCData system. The Determine ad hoc group request contains either the criteria to be applied by the MCData server of the primary MCData system for determining the list of MCData users or the list of MCData users as selected by the user at MCData client 1. The request may also contain the indicator for data transfer is for emergency, imminent peril and the application identifier for which the data transfer is intended.
3. If the ad hoc group communication is supported, the MCData server of the primary MCData system checks whether the MCData user at MCData client 1 is authorized to initiate a Determine ad hoc group request. If not authorized, the MCData server rejects the Determine ad hoc group request as specified in the step 9. If the request contains the list of MCData users as selected by the user at MCData client 1, the MCData server of the primary MCData system validates whether the number of MCData users provided in the request are within the configured limit. If not within the configured limit, the MCData server rejects the Determine ad hoc group request as specified in the step 9.
4. If the request contains the criteria, the MCData server of primary MCData system determines the list of MCData users for ad hoc group standalone short data service from the primary MCData system and determines the partner MCData system to be involved in the ad hoc group standalone short data service based on the criteria and according to local policy if required. This information element to determine the ad hoc group member contains the criteria, indicator identifying pre-defined criteria, or a combination of both.
NOTE 1: The values of criteria, indicator identifying pre-defined criteria and determining the list of participants using these values by MCData server is left to implementation.
5. The MCData server of primary MCData system involves the partner MCData system based on the agreement, based on the criteria for determining the list of MCData users, and according to local policy if required. It sends the ad hoc group standalone data get userlist request to the MCData server of partner MCData system. This request carries the criteria received in the Determine ad hoc group request.
6. The MCData server of partner MCData system determines the list of MCData users satisfying the criteria and sends the response containing the list of MCData users satisfying the criteria. The MCData server of partner MCData system may apply local policies if any while determining the participants satisfying the criteria. The determination of list of MCData users is performed only once.
7. The MCData server of primary MCData system compiles the list of MCData users for ad hoc group standalone short data service from primary MCData system and from partner MCData system, if requested.
NOTE 2: The step 4 to step 7 are applicable if the request contains the criteria for determining the ad hoc group members from primary system and may be from partner system.
8. The MCData server of the primary MCData system forms the ad hoc group by using MCData users' information received in the Determine ad hoc group request and list of MCData users to be part of ad hoc group. The MCData server further determines the preconfigured group to be used for the configuration (e.g. security related information) of the ad hoc group if end-to-end encryption is required. The MCData server selects an MCData ad hoc group ID for the newly formed ad hoc group and optionally assign the time to live value. The ad hoc group members can communicate in the ad hoc group until the time to live value is expired. The MCData server ensure the list of MCData users determined in the step 7 are within the configured limit.
NOTE 3: How the MCData server decides list of participants is implementation specific.
9. The MCData server of the primary MCData system send the Determine ad hoc group response message to MCData client 1 containing the below:
i. The MCData ad hoc group ID (only included when the Determine ad hoc group request is succesful);
ii. The MCData group ID of the pre-configured group whose configuration is to be applied for this Ad hoc group standalone short data service if end-to-end encryption is required (only included when the Determine ad hoc group request is succesful); and
iii. Result of whether the Determine ad hoc group request successful or failure.
If the Determine ad hoc group request not authorized or result not succesful, the MCData client 1 shall not proceed with remaining steps for the data transfer as specified in the clause 7.17.6.3 and 7.17.6.4.
7.17.6.3 Ad hoc group standalone short data service using signalling control plane involving single MCData system
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.6.3.1 General
| The initiation of Ad hoc group standalone short data service using signalling control plane results in ad hoc group members from single MCData system receiving the SDS data. The SDS payload data size is assumed to be below the configured maximum payload data size for SDS over signalling control plane.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.6.3.2 Procedure
| The procedure in figure 7.17.6.3.2-1 describes the case where an MCData user is initiating ad hoc group standalone short data service using signalling control plane with or without disposition request.
Pre-conditions:
1. MCData users on MCData clients 1 to n belong to the same MCData system and are already registered for receiving MCData service.
2. Number of ad hoc group members receiving the SDS data is within the configured limit.
3. The preconfigured group identity and preconfigured group configuration (e.g. security related information) to be used for an ad hoc group have been preconfigured in the MCData client and other MCData users of ad hoc group have also received the relevant security related information.
Figure 7.17.6.3.2-1: Ad hoc group standalone short data service involving single MCData system
1. The user at MCData client 1 wants initiates an SDS data transfer to ad hoc group members from primary MCData system.
2. The MCData client 1 shall determine the preconfigured group if end-to-end encryption is required and an ad hoc group by executing the procedures as described in the clause 7.17.6.2.
3. MCData client 1 sends an Ad hoc group standalone data request towards the MCData server. The request shall contain the MCData ad hoc group ID as determined in the step 2, the conversation identifier for message thread indication, may include additional implementation specific information in the application metadata container, may contain disposition request if indicated by the user at MCData client 1 and may include associated functional alias of the user at MCData client 1. If end-to-end encryption is required, the request shall contain the Preconfigured MCData group ID as determined in the step 2. If the end-to-end encryption is not required then include the payload without encryption and if required then include the payload with encryption based on the Preconfigured MCData group ID as determined in the step 2.
If the MCData user at MCData client 1 initiates an emergency ad hoc group standalone short data service or the MCData emergency state is already set for the MCData client 1 (due to a previously triggered MCData emergency alert):
i) the Ad hoc group standalone data request shall contain an emergency indicator;
ii) if the MCData emergency state is not set already, MCData client 1 sets its MCData emergency state. The MCData emergency state is retained until explicitly cancelled; and
iii) once an emergency SDS data transfer has been initiated, the ad hoc group is considered to be in an in-progress emergency state until SDS data transfer is completed and the time to live value of ad hoc group expires.
If the MCData user at MCData client 1 initiates an imminent peril ad hoc group standalone short data service:
i) the Ad hoc group standalone data request shall contain imminent peril indicator; and
ii) once an emergency SDS data transfer has been initiated, the ad hoc group is considered to be in an in-progress imminent peril state until SDS data transfer is completed and the time to live value of ad hoc group expires.
4. If the ad hoc group communication is supported, the MCData server checks whether the MCData user at MCData client 1 is authorized to send Ad hoc group standalone data request. If not authorized, the MCData server rejects the Ad hoc group standalone data request as specified in the step 9. The MCData server checks whether any policy is to be asserted to limit certain types of message or content to certain members, for example, to location or user privilege. The MCData server also verifies whether the provided functional alias can be used and has been activated for the user.
5. The MCData server considers the the ad hoc group memebers as implicitly affiliated to the ad hoc group.
i) If an emergency indicator is present in the received Ad hoc group standalone data request and if the ad hoc group is not in the in-progress emergency state, the ad hoc group is considered to be in the in-progress emergency state until SDS data transfer is completed and the time to live value of ad hoc group expires; and
ii) If an imminent peril indicator is present in the received Ad hoc group standalone data request and if the ad hoc group is not in the in-progress imminent peril state, the ad hoc group is considered to be in the in-progress imminent peril state until SDS data transfer is completed and the time to live value of ad hoc group expires; and
6. The MCData server initiates a Ad hoc group standalone data request towards each of the target MCData users. While sending the Ad hoc group standalone data request, the MCData server shall remove the information elements that are not required to be conveyed to the target MCData clients (e.g. MCData ID list). The request should contain the ad hoc group ID, pre-configured group if end-to-end encryption is required and time to live value for the ad hoc group. The primary MCData server removes the ad hoc group information from the dynamic data once the time to live value is expired and thus the ad hoc group ceases to exist then the procedure stops.
7. If the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the MCData user of MCData clients 2 to n may be notified. Otherwise if the payload is not for MCData user consumption, then the MCData user of MCData clients 2 to n shall not be notified. The action taken when the payload contains application data or command instructions are specific based on the contents of the payload. Payload content received by MCData client 2 which is addressed to a known local non-MCData application that is not yet running shall cause the MCData client 2 to start the local non-MCData application (i.e., remote start application) and shall pass the payload content to the just started application.
8. If the MCData data disposition for delivery was requested by the user at MCData client 1, then the receiving MCData client(s) initiates a MCData data disposition notification for delivery report as described in the step 6 to step 9 of clause 7.4.2.5.2.
7.17.6.4 Ad hoc group standalone short data service using signalling control plane involving multiple MCData system
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.6.4.1 General
| The initiation of Ad hoc group standalone short data service using signalling control plane results in ad hoc group members from multiple MCData system receiving the SDS data. The SDS payload data size is assumed to be below the configured maximum payload data size for SDS over signalling control plane.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.6.4.2 Procedure
| The procedure in figure 7.17.6.4.2-1 describes the case where an MCData user is initiating ad hoc group standalone short data service using signalling control plane with or without disposition request.
Pre-conditions:
1. The security aspects of sharing the user information between primary and partner MCData systems shall be governed as per the service provider agreement between them. In this case, it is considered that the partner MCData system share their users' information to the primary MCData system.
2. MCData users on MCData clients 1 to M belong to the primary MCData system and MCData users on MCData clients 1 to N belong to the partner MCData system and are already registered for receiving MCData service.
3. The MCData server of the primary MCData system is where the authorized MCData user/dispatcher creates the ad hoc group.
4. Number of ad hoc group members receiving the SDS data is within configured limit.
5. The preconfigured group identity and preconfigured group configuration (e.g. security related information) to be used for an ad hoc group have been preconfigured in the MCData client and other MCData users of ad hoc group have also received the relevant security related information.
Figure 7.17.6.4.2-1: Ad hoc group standalone short data service involving multiple MCData system
1. The user at MCData client 1 of the primary MCData system wants initiates an SDS data transfer to ad hoc group members from primary and partner MCData systems.
2-5. Same steps as described in the steps 2 to 5 of clause 7.17.6.3.2.
6-6a. The MCData server of the primary MCData system initiates an Ad hoc group standalone data request towards each of the target MCData users in the primary MCData system and the partner MCData system. While sending the Ad hoc group standalone data requests, the MCData server of the primary MCData system shall remove the information elements that are not required to be conveyed to the target MCData clients (e.g. MCData ID list). The request should contain the ad hoc group ID, pre-configured group if end-to-end encryption is required and time to live value for the ad hoc group. The primary MCData server removes the ad hoc group information from the dynamic data once the time to live value is expired and thus the ad hoc group ceases to exist then the procedure stops.
7-7a. If the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the MCData user of MCData clients 2 to M and MCData clients 1 to N may be notified. Otherwise if the payload is not for MCData user consumption, then the MCData user of MCData clients 2 to M and MCData clients 1 to N shall not be notified. The action taken when the payload contains application data or command instructions are specific based on the contents of the payload. Payload content received by MCData clients 2 to M and MCData clients 1 to N which is addressed to a known local non-MCData application that is not yet running shall cause the clients 2 to M and MCData clients 1 to N to start the local non-MCData application (i.e., remote start application) and shall pass the payload content to the just started application.
8. If the MCData data disposition for delivery was requested by the user at MCData client 1 of the primary MCData system, then the receiving MCData client(s) initiates a MCData data disposition notification for delivery report as described in the step 6 to step 9 of clause 7.4.2.5.2.
7.17.7 Ad hoc group standalone file distribution using HTTP procedures
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.7.1 Information flows
| 7.17.7.1.1 Ad hoc group standalone FD request (MCData client – MCData server)
Table 7.17.7.1.1-1 describes the information flow for the Ad hoc group standalone FD request sent from the MCData client to the MCData server.
Table 7.17.7.1.1-1: Ad hoc group standalone FD request
Information element
Status
Description
MCData ID
M
The identity of the MCData user sending the FD request
Functional alias
O
The associated functional alias of the MCData user sending the FD request
MCData ad hoc group ID (see NOTE 1)
M
The MCData group ID of the ad hoc group to which the file is to be sent
Preconfigured MCData group ID (see NOTE 2)
O
The identity of the MCData group whose configuration (e.g. security related information) is to be applied for ad hoc group file distribution.
Conversation Identifier
M
Identifies the conversation
Transaction Identifier
M
Identifies the MCData transaction
Emergency indicator (see NOTE 3)
O
Indicates that the standalone file distribution request is for emergency ad hoc group standalone file distribution service
Imminent peril indicator (see NOTE 3)
O
Indicates that the standalone file distribution request is for imminent peril ad hoc group standalone file distribution service
Disposition indication
O
Indicates whether file download completed report is expected or not
Download indication
O
Indicates mandatory download
Location
O
Location of the Originating MCData user sending the file
Payload Destination Type
M
Indicates whether the payload is for application consumption or MCData user consumption
Application identifier (see NOTE 4)
O
Identifies the application for which the payload is intended (e.g. text string, port address, URI)
Application metadata container
O
Implementation specific information that is communicated to the recipient
Content reference
M
URL reference to the content and file metadata information
Deposit file indication
O
Indicates whether the file to be stored into the MCData message store account of the MCData user
NOTE 1: The MCData ad hoc group ID is determined prior to by using the Determine ad hoc group request.
NOTE 2: If end-to-end encryption is required, then this element is included and the value is determined prior to by using the Determine ad hoc group request.
NOTE 3: If used, only one of these information elements shall be present.
NOTE 4: The application identifier shall be included only if the payload destination type indicates that the FD message is for application consumption.
Editor's note: Use of Application ID to target the FD to a specific application use is FFS.
7.17.7.1.2 Ad hoc group standalone FD request (MCData server – MCData client)
Table 7.17.7.1.2-1 describes the information flow for the Ad hoc group standalone FD request sent from the MCData server to the MCData client.
Table 7.17.7.1.2-1: Ad hoc group standalone FD request
Information element
Status
Description
MCData ID
M
The identity of the MCData user sending the FD request
Functional alias
O
The associated functional alias of the MCData user sending the FD request
MCData ad hoc group ID
M
The MCData group ID of the ad hoc group to which the file is to be sent
Preconfigured MCData group ID (see NOTE 1)
O
The identity of the MCData group whose configuration (e.g. security related information) is to be applied for ad hoc group file distribution.
MCData ID
M
The identity of the MCData user towards which the FD request is sent
Conversation Identifier
M
Identifies the conversation
Transaction Identifier
M
Identifies the MCData transaction
Emergency indicator (see NOTE 2)
O
Indicates that the standalone file distribution request is for emergency ad hoc group standalone file distribution service
Imminent peril indicator (see NOTE 2)
O
Indicates that the standalone file distribution request is for imminent peril ad hoc group standalone file distribution service
Disposition indication
O
Indicates whether file download completed report is expected or not
Download indication
O
Indicates mandatory download
Location
O
Location of the Originating MCData user sending the file
Payload Destination Type
M
Indicates whether the payload is for application consumption or MCData user consumption
Application identifier (see NOTE 3)
O
Identifies the application for which the payload is intended (e.g. text string, port address, URI)
Application metadata container
O
Implementation specific information that is communicated to the recipient
Content reference
M
URL reference to the content and file metadata information
Time to live
O
Indicates how long the ad hoc group is persisted and members can respond to the file distribution (e.g. duration for 5 mins or until certain future time).
NOTE 1: If end-to-end encryption is required, then this element is included.
NOTE 2: If used, only one of these information elements shall be present.
NOTE 3: The application identifier shall be included only if the payload destination type indicates that the FD message is for application consumption.
7.17.7.1.3 Ad hoc group standalone FD request return (MCData server – MCData client)
Table 7.17.7.1.3-1 describes the information flow Ad hoc group standalone FD request return from the MCData server to the MCData client.
Table 7.17.7.1.3-1 Ad hoc group standalone FD request return information elements
Information Element
Status
Description
MCData ID
M
The identity of the MCData user sending the FD request
Functional alias
O
The associated functional alias of the MCData user sending the FD request
Authorization result
M
Indicate if authorization is success or failure
7.17.7.1.4 Ad hoc group standalone FD response (MCData client – MCData server, MCData server – MCData client)
Table 7.17.7.1.4-1 describes the information flow for the Ad hoc group standalone FD response sent from the MCData client to the MCData server and from the MCData server to another MCData client.
Table 7.17.7.1.4-1: Ad hoc group standalone FD response
Information element
Status
Description
MCData ad hoc group ID
M
The MCData group ID of the ad hoc group to which the file is to be sent
MCData ID
M
The identity of the MCData user sending FD response
Conversation Identifier
M
Identifies the conversation
Time to live
O
Indicates how long the ad hoc group is persisted and members can respond to the file distribution (e.g. duration for 5 mins or until certain future time).
Result
M
Indicates if the request is accepted or not
7.17.7.2 Ad hoc group standalone file distribution using HTTP involving single MCData system
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.7.2.1 General
| The initiation of Ad hoc group standalone file distribution using HTTP results in ad hoc group members from single MCData system receiving the file data.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.7.2.2 Procedure
| The procedure in figure 7.17.7.2.2-1 describes the case where an MCData user is initiating ad hoc group standalone file distribution to multiple MCData users, with or without download completed report request from the MCData user.
Pre-conditions:
1. The MCData users on MCData clients 1 to n belong to the same MCData system and are already registered for receiving MCData service.
2. Number of ad hoc group members receiving the file data is within the configured limit.
3. The MCData client 1 may have an activated functional alias to be used.
4. The file to be distributed is uploaded to the media storage function on the MCData content server using the procedures defined in subclause 7.5.2.2. The ad hoc group identity and preconfigured group identity of preconfigured group from which the configurations to be used (e.g. security related information) are determined using the procedures defined in subclause 7.17.6.2.1
5. The preconfigured group identity and preconfigured group configuration (e.g. security related information) to be used for an ad hoc group have been preconfigured in the MCData client 1 and other MCData clients of ad hoc group have also received the relevant security related information.
Figure 7.17.7.2.2-1: Ad hoc group standalone file distribution involving single MCData system
1. The user at MCData client 1 wants to initiate ad hoc standalone file distribution to ad hoc group members from primary MCData system.
2. The MCData client 1 sends an Ad hoc group standalone FD request towards the MCData server. The request shall contain the MCData ad hoc group ID as determined in the subclause 7.17.6.2.1, the conversation identifier for message thread indication, may include additional implementation specific information in the application metadata container, and may include associated functional alias of the user at MCData client 1. If end-to-end encryption is required, the request shall contain the Preconfigured MCData group ID as determined in the subclause 7.17.6.2.1. The request contains content payload in the form of file URL and may contain the file metadata information. If MCData user at MCData client 1 has requested to mandatory download at the recipient side, then the request contains mandatory download indication. The request may contain a download completed report indication if selected by the user at MCData client 1. If the MCData user at MCData client 1 has requested to deposit the file content into his/her MCData message store account, then the request contains deposit file indication set.
If the MCData user at MCData client 1 initiates an emergency ad hoc group standalone file distribution or the MCData emergency state is already set for the MCData client 1 (due to a previously triggered MCData emergency alert):
i) the Ad hoc group standalone FD request shall contain an emergency indicator;
ii) if the MCData emergency state is not set already, MCData client 1 sets its MCData emergency state. The MCData emergency state is retained until explicitly cancelled; and
iii) once an emergency file distribution has been initiated, the ad hoc group is considered to be in an in-progress emergency state until file distribution is completed and the time to live value of ad hoc group expires.
If the MCData user at MCData client 1 initiates an imminent peril ad hoc group standalone file distribution:
i) the Ad hoc group standalone FD request shall contain imminent peril indicator; and
ii) once an emergency file distribution has been initiated, the ad hoc group is considered to be in an in-progress imminent peril state until file distribution is completed and the time to live value of ad hoc group expires.
3. If the ad hoc group communication is supported, the MCData server checks whether the MCData user at MCData client 1 is authorized to send Ad hoc group standalone FD request. The MCData server checks whether any policy is to be asserted to limit certain types of message or content to certain members, for example, to location or user privilege. The MCData server also verifies whether the provided functional alias can be used and has been activated for the user.
4. The MCData server sends the Ad hoc group standalone FD request return to the MCData user at MCData client 1 containing the result of whether the Ad hoc group standalone FD request is authorized or not. If the Ad hoc group standalone FD request is not authorized, the MCData server and the MCData client 1 shall not proceed with the rest of the steps.
5. The MCData server considers the ad hoc group members as implicitly affiliated to the ad hoc group.
i) If an emergency indicator is present in the received Ad hoc group standalone FD request and if the ad hoc group is not in the in-progress emergency state, the ad hoc group is considered to be in the in-progress emergency state until file distribution is completed and the time to live value of ad hoc group expires; and
ii) If an imminent peril indicator is present in the received Ad hoc group standalone FD request and if the ad hoc group is not in the in-progress imminent peril state, the ad hoc group is considered to be in the in-progress imminent peril state until file distribution is completed and the time to live value of ad hoc group expires.
6. The MCData server may verify whether the corresponding file is available in the MCData content server (not shown in the figure) via the MCData-FD-5 reference point using the received file URL in the request. For that, the MCData server sends an MCData file availability request to the MCData content server. Upon the receipt of the request, the MCData content server provides an MCData file availability response to the MCData server. If the MCData server identifies that the file is not available in the MCData content server, the MCData server provides a response to the MCData client 1 indicating that the file distribution request cannot proceed due to the unavailability of the file in the MCData content server and skip rest of the steps. If the deposit file indication information element is set to true in the received request, the MCData server shall follow the procedure as defined in the subclause 7.13.3.8 with the retrieve file indication element set to true while depositing this MCData communication to the MCData message store account of the user at MCData client 1.
NOTE: If the group communication is end-to-end encrypted the MCData server cannot check if the file is available on the MCData content server.
7. The MCData server initiates the Ad hoc group standalone FD request towards each of the target MCData users. While sending the Ad hoc group standalone FD request, the MCData server shall remove the information elements that are not required to be conveyed to the target MCData clients (e.g. MCData ID list). The request should contain the ad hoc group ID, pre-configured group if end-to-end encryption is required and time to live value for the ad hoc group. The primary MCData server removes the ad hoc group information from the dynamic data once the time to live value is expired and thus the ad hoc group ceases to exist then the procedure stops. If the deposit file indication information element is set to true in the received MCData FD request, MCData server shall follow the procedure as defined in the subclause 7.13.3.8 with the retrieve file indication element set to true while depositing this MCData communication to the MCData message store account of the user at MCData client 1.
8. The receiving MCData clients 2 to n notify the user about the incoming Ad hoc group standalone FD request (including file metadata, if present) which may be either accepted or rejected or ignored.
9. If the target MCData user on MCData clients 2 to n provides a response (accept or reject) to the notification, then respective MCData client sends the Ad hoc group standalone FD response to the MCData server. The MCData client 2 to n automatically sends accepted Ad hoc group standalone FD response when the incoming request included mandatory download indication.
10. The MCData server forwards the Ad hoc group standalone FD response to the MCData client 1.
11. The receiving MCData clients 2 to n download the file followed by providing download completed reports for reporting file download completed using the procedure as described in the step 9 to step 12 of subclause 7.5.2.6.
12. On receiving download completed reports from MCData clients 2 to n or time to live value is expired, the MCData server removes the ad hoc group information from the dynamic data held in the MCData server and the ad hoc group ceases to exist.
7.17.7.3 Ad hoc group standalone file distribution using HTTP involving multiple MCData system
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.7.3.1 General
| The initiation of Ad hoc group standalone file distribution using HTTP results in ad hoc group members from multiple MCData system receiving the file data.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.7.3.2 Procedure
| The procedure in figure 7.17.7.3.2-1 describes the case where an MCData user is initiating ad hoc group standalone file distribution to multiple MCData users, with or without download completed report request from the MCData user.
Pre-conditions:
1. The security aspects of sharing the user information between primary and partner MCData systems shall be governed as per the service provider agreement between them. In this case, it is considered that the partner MCData system share their users' information to the primary MCData system.
2. MCData users on MCData clients 1 to M belong to the primary MCData system and MCData users on MCData clients 1 to N belong to the partner MCData system and are already registered for receiving MCData service.
3. The MCData server of the primary MCData system is where the authorized MCData user/dispatcher creates the ad hoc group.
4. Number of ad hoc group members receiving the file data is within the configured limit.
5. The file to be distributed is uploaded to the media storage function on the MCData content server using the procedures defined in subclause 7.5.2.2. The ad hoc group identity and preconfigured group identity of preconfigured group from which the configurations to be used (e.g. security related information) are determined using the procedures defined in subclause 7.17.6.2.1.
6. The preconfigured group identity and preconfigured group configuration (e.g. security related information) to be used for an ad hoc group have been preconfigured in the MCData client and other MCData users of ad hoc group have also received the relevant security related information.
Figure 7.17.7.3.2-1: Ad hoc group standalone file distribution involving multiple MCData system
1. The user at MCData client 1 of the primary MCData system wants initiate ad hoc standalone file distribution to ad hoc group members from primary and partner MCData systems.
2-6. Same steps as described in the steps 2 to 6 of subclause 7.17.7.2.2.
7a-7b. The MCData server of the primary MCData system initiates an Ad hoc group standalone FD request towards each of the target MCData users in the primary MCData system and the partner MCData system. While sending the Ad hoc group standalone FD requests, the MCData server of the primary MCData system shall remove the information elements that are not required to be conveyed to the target MCData clients (e.g. MCData ID list). The request should contain the ad hoc group ID, pre-configured group if end-to-end encryption is required and time to live value for the ad hoc group. The primary MCData server removes the ad hoc group information from the dynamic data once the time to live value is expired and thus the ad hoc group ceases to exist then the procedure stops.
8a-8b. The receiving MCData clients 2 to M and MCData clients 1 to N notify the user about the incoming Ad hoc group standalone FD request (including file metadata, if present) which may be either accepted or rejected or ignored.
9a-9b. If the target MCData user on MCData clients 2 to M and MCData clients 1 to N provides a response (accept or reject) to the notification, then respective MCData clients send the Ad hoc group standalone FD response to the MCData server. The MCData clients 2 to M and MCData clients 1 to N automatically sends accepted Ad hoc group standalone FD response when the incoming request included mandatory download indication.
10a-10b. The MCData server forwards the Ad hoc group standalone FD response to the MCData client 1.
11a-11d. The receiving MCData clients 2 to M and MCData clients 1 to N download the file followed by providing download completed reports for reporting file download completed using the procedure as described in the step 9 to step 12 of subclause 7.5.2.6.
Annex A (normative):
MCData related configuration data
A.1 General
This Annex provides information about the static data needed for configuration for the MCData service, which belongs to one of the following categories:
- MCData UE configuration data (see subclause A.2);
- MCData user profile configuration data (see subclause A.3);
- MCData related group configuration data (see subclause A.4); and
- MCData service configuration data (see subclause A.5).
For each configuration category, data is split between configuration data that is applicable to both on network and off network, configuration data that is applicable to on-network only, and configuration data that is applicable to off-network only. The configuration data in each configuration category corresponds to a single instance of the category type i.e. the MCData UE, MCData group, MCData user and MCData service configuration data refers to the information that will be stored against each MCData UE, MCData group, MCData user and MCData service. This means that the three separate tables (on-network and off-network, on-network only, off-network only) for each configuration category represent the complete set of data for each configuration data category element.
The columns in the tables have the following meanings:
- Reference: the reference of the corresponding requirement in 3GPP TS 22.282 [3] or 3GPP TS 22.280 [2] or the corresponding subclause from either the present document or the referenced document.
- Parameter description: A short definition of the semantics of the corresponding item of data, including denotation of the level of the parameter in the configuration hierarchy.
- When it is not clear to which functional entities the parameter is configured, then one or more columns indicating this are provided where the following nomenclature is used:
- "Y" to denote "Yes" i.e. the parameter denoted for the row needs to be configured to the functional entity denoted for the column.
- "N" to denote "No" i.e. the parameter denoted for the row does not need to be configured to the functional entity denoted for the column.
Parameters within a set of configuration data have a level within a hierarchy that pertains only to that configuration data. The hierarchy of the configuration data is common across all three tables of on-network and off-network, on network only and off network only. The level of a parameter within the hierarchy of the configuration data is denoted by use of the character ">" in the parameter description field within each table, one per level. Parameters that are at the top most level within the hierarchy have no ">" character. Parameters that have one or more ">" characters are child parameters of the first parameter above them that has one less ">" character. Parent parameters are parameters that have one or more child parameters. Parent parameters act solely as a "grouping" of their child parameters and therefore do not contain an actual value themselves i.e. they are just containers for their child parameters.
Each parameter that can be configured online shall only be configured through one online reference point. Each parameter that can be configured offline shall only be configured through one offline reference point. The most recent configuration data made available to the MCData UE shall always overwrite previous configuration data, irrespective of whether the configuration data was provided via the online or offline mechanism.
A.2 MCData UE configuration data
The general aspects of UE configuration are specified in 3GPP TS 23.280 [5]. Data in tables A.2-1 and A.2-2 have to be known by the MCData UE after MCData authorization.
Data in table A.2-1 can be configured offline using the CSC-11 reference point. Table A.2-1 contains the UE configuration required to support the use of off-network MCData service.
Table A.2-1: UE configuration data (on and off network)
Reference
Parameter description
Short data service
[R-5.4.2-002] of 3GPP TS 22.280 [2]
> Maximum number of simultaneous SDS transactions (Nc4)
[R-5.4.2-004] of 3GPP TS 22.280 [2]
> Requested presentation priority of SDS messages received (see NOTE)
File distribution
[R-5.4.2-002] of 3GPP TS 22.280 [2]
> Maximum number of simultaneous file distribution transactions (Nc4)
Transmission control
[R-5.4.2-002] of 3GPP TS 22.280 [2]
> Maximum number of simultaneous data transmissions (Nc4)
[R-5.4.2-003] of 3GPP TS 22.280 [2]
> Maximum number of data transmissions (Nc5) in a group
Reception control
[R-5.4.2-002] of 3GPP TS 22.280 [2]
> Maximum number of simultaneous data receptions (Nc4)
[R-5.4.2-003] of 3GPP TS 22.280 [2]
> Maximum number of data receptions (Nc5) in a group
NOTE: Priority of SDS messages includes enhanced status updates, since enhanced status updates utilise the SDS mechanism.
Table A.2-2: UE configuration data (on network)
Reference
Parameter description
Subclause 5.2.3 of 3GPP TS 23.280 [6]
Relay service (Y/N)
Subclause 5.2.3 of 3GPP TS 23.280 [6]
List of allowed relayed MCData groups and their relay service code (as specified in 3GPP TS 23.303 [7]) (optional) (see NOTE)
> MCData group ID
> Relay service code (as specified in 3GPP TS 23.303 [7])
NOTE: When the value of the parameter Relay service is N, this parameter and its child parameters are not needed.
A.3 MCData user profile configuration data
The general aspects of MC service user profile configuration data are specified in 3GPP TS 23.280 [5]. The MCData user profile configuration data is stored in the MCData user database. The MCData server obtains the MCData user profile configuration data from the MCData user database (MCData-2).
Tables A.3-1 and A.3-2 contain the MCData user profile configuration required to support the use of on-network MCData service. Tables A.3-1 and A.3-3 contain the MCData user profile configuration required to support the use of off-network MCData service. Data in table A.3-1 and A.3-3 can be configured offline using the CSC-11 reference point.
Table A.3-1: MCData user profile configuration data (on and off network)
Reference
Parameter description
MCData UE
MCData Server
Configuration management server
MCData user database
Subclause 8.1.2 of 3GPP TS 23.280 [5]
MCData identity (MCData ID)
Y
Y
Y
Y
3GPP TS 33.180 [13]
KMSUri for security domain of MCData ID (see NOTE 1)
Y
Y
Y
Y
Subclause 5.2.4 of 3GPP TS 23.280 [5]
Pre‑selected MCData user profile indication (see NOTE 2)
Y
Y
Y
Y
Subclause 5.2.4 of 3GPP TS 23.280 [5]
MCData user profile index
Y
Y
Y
Y
Subclause 5.2.4 of 3GPP TS 23.280 [5]
MCData user profile name
Y
Y
Y
Y
[R-5.17-007],
[R-6.13.4-002] of 3GPP TS 22.280 [2]
User profile status (enabled/disabled)
Y
Y
Y
[R-5.7-001],
[R-6.9-003] of 3GPP TS 22.280 [2]
Authorised to create and delete aliases of an MCData user and its associated user profiles.
Y
Y
[R-5.7-002],
[R-6.9-003] of 3GPP TS 22.280 [2]
Alphanumeric aliases of user
Y
Y
Y
Y
[R-5.1.1-005],
[R-5.9-001] of 3GPP TS 22.280 [2]
Participant type of the user
Y
Y
Y
Y
[R-5.1.8-006],
[R-5.3-002],
[R-5.9-001],
[R-5.16.2-001],
[R-5.16.2-002] of 3GPP TS 22.280 [2]
User's Mission Critical Organization (i.e. which organization a user belongs to)
Y
Y
Y
Y
[R-5.2.2-003] and [R6.6.3-002] of 3GPP TS 22.280 [2]
Authorisation to create a group-broadcast group (see NOTE 7)
Y
Y
[R-5.2.2-003] and [R6.6.3-002] of 3GPP TS 22.280 [2]
Authorisation to create a user-broadcast group (see NOTE 7)
Y
Y
[R-5.6.2.4.1-002] of 3GPP TS 22.280 [2]
Authorised to activate MCData emergency alert
Y
Y
Y
Y
[R-5.6.2.4.1-013] of 3GPP TS 22.280 [17]
Automatically trigger a MCData emergency communication after initiating the MCData emergency alert
Y
Y
Y
Y
[R-5.6.2.4.1-004]
[R-5.6.2.4.1-008]
[R-5.6.2.4.1-012] of 3GPP TS 22.280 [2]
Group used on initiation of an MCData emergency group communication (see NOTE 3)
[R-5.6.2.4.1-004], [R-5.6.2.4.1-008], [R-5.6.2.4.1-012] of 3GPP TS 22.280 [17]
Recipient for an MCData emergency private communication (see NOTE 3)
> MCData ID
Y
Y
Y
Y
3GPP TS 33.180 [19]
> KMSUri for security domain of MCData ID (see NOTE 1)
Y
Y
Y
Y
[R-5.6.2.4.2-002] of 3GPP TS 22.280 [2]
Authorisation to cancel an MCData emergency alert
Y
Y
Y
Y
[R-6.15.6.2-002] of 3GPP TS 22.280 [2]
Authorised to activate an MCData ad hoc group emergency alert
Y
Y
Y
Y
[R-6.15.6.2-006] of 3GPP TS 22.280 [2]
Authorisation to cancel an MCData ad hoc group emergency alert
Y
Y
Y
Y
[R-6.15.6.2-007] of 3GPP TS 22.280 [2]
Authorised to set up an MCData group communication using the ad hoc group used for the alert
Y
Y
Y
Y
Authorised to receive the participants information of an MCData ad hoc group emergency alert
N
Y
Y
Y
Authorised to modify the list of participants and criteria for an MCData ad hoc group emergency alert
Y
Y
Y
Y
[R-6.1.1.2-005],
[R-6.1.1.2-006],
[R-6.1.1.2-007] of 3GPP TS 22.282 [3]
Individual conversation hang time
Y
Y
Y
Y
One-to-one communication
[R-6.3.1.2-007] of 3GPP TS 22.282 [3] and 3GPP TS 33.180 [13]
> List of MCData users this MCData user is authorized to initiate a one‑to-one communication
>> MCData ID
Y
N
Y
Y
>> Discovery Group ID
Y
N
Y
Y
>> User info ID (as specified in 3GPP TS 23.303 [7])
Y
N
Y
Y
>> KMSUri for security domain of MCData ID (see NOTE 1)
Y
Y
Y
Y
[R-6.7.3-007] of 3GPP TS 22.280 [2]
Authorised to make one-to-one communications towards users not included in "list of MCData user(s) this MCData user is authorized to initiate a one‑to-one communication"
Y
Y
Y
Y
File distribution
[R-5.3.2-010] of 3GPP TS 22.282 [3] and 3GPP TS 33.180 [13]
> List of MCData users this MCData user is allowed to cancel distribution of files being sent or waiting to be sent
>> MCData ID
Y
Y
Y
Y
>> KMSUri for security domain of MCData ID (see NOTE 1)
Y
Y
Y
Y
Transmission and reception control
[R-6.2.2.1-001] of 3GPP TS 22.282 [3]
> Whether the MCData user is permitted to transmit data
Y
Y
Y
Y
[R-6.2.3-005] of 3GPP TS 22.282 [3]
> Maximum amount of data that the MCData user can transmit in a single request during one-to-one communication
Y
Y
Y
Y
[R-6.2.3-005] and [R‑6.3.1.2-008] of 3GPP TS 22.282 [3]
> Maximum amount of time that the MCData user can transmit in a single request during one-to-one communication
Y
Y
Y
Y
[R-6.2.3-001] of 3GPP TS 22.282 [3]
> List of MCData users this MCData user is allowed to request the release of an ongoing transmission that this MCData user is participating in
>> MCData ID
Y
Y
Y
Y
[R-5.1.7-002] and
[R-6.8.7.2-007] and [R-6.8.7.2-008] of 3GPP TS 22.280 [2]
Priority of the user (see NOTE 4)
Y
Y
Y
Lossless communication for private communication
Y
Y
Y
Y
Store communication in Message Store (see NOTE 5)
Y
Y
Y
Y
Store private communication in Message Store (see NOTE 6)
Y
Y
Y
Y
NOTE 1: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [5].
NOTE 2: As specified in 3GPP TS 23.280 [5], for each MCData user's set of MCData user profiles, only one MCData user profile shall be indicated as being the pre‑selected MCData user profile.
NOTE 3: This parameter is used for the emergency communication and also used as a target of the emergency alert request. At most one of them is configured; i.e. emergency communication will go to either a group or a user. If both are not configured the MCData user's currently selected group will be used.
NOTE 4: The use of the parameter is left to implementation.
NOTE 5: This is the top-level control parameter to determine whether MCData communications will be stored or not. When this parameter is set; the second level control parameter is used to determine whether a specific MCData communication (private or which group) will be stored and MCData user can request for all or selected of his/her MCData communication shall be stored in the MCData message store or not.
NOTE 6: This is the second level control parameter to determine whether a private communication will be stored when the Store communication in Message Store top level control parameter is set.
NOTE 7: This parameter applies to temporary broadcast groups built from regrouping mechanism. This authorisation automatically sets the originator of the temporary group as the only transmitting party.
Table A.3-2: MCData user profile configuration data (on network)
Reference
Parameter description
MCData UE
MCData Server
Configuration management server
MCData user database
[R-5.1.5-001],
[R-5.1.5-002],
[R-5.10-001],
[R-6.4.7-002],
[R-6.8.1-008],
[R-6.7.4-002] of 3GPP TS 22.280 [2]
List of on-network MCData groups for use by an MCData user
> MCData Group ID
Y
Y
Y
Y
> Store group communication in Message Store (see NOTE 11)
Y
Y
Y
Y
> Application plane server identity information of group management server where group is defined
>> Server URI
Y
Y
Y
Y
> Application plane server identity information of identity management server which provides authorization for group (see NOTE 1)
>> Server URI
Y
Y
Y
Y
3GPP TS 33.180 [13]
> KMSUri for security domain of group (see NOTE 2)
Y
Y
Y
Y
> Presentation priority of the group relative to other groups and users (see NOTE 3)
Y
N
Y
Y
> Transmission and reception control
>> Whether MCData user is permitted to transmit data in the group
Y
Y
Y
Y
>> Maximum amount of data that the MCData user can transmit in a single request during group communication
Y
Y
Y
Y
>> Maximum amount of time that the MCData user can transmit in a single request during group communication
Y
Y
Y
Y
Subclause 5.2.5 of 3GPP TS 23.280 [5]
List of groups user implicitly affiliates to after MCData service authorization for the user
> MCData Group ID
Y
Y
Y
Y
[R-6.4.2-006] of 3GPP TS 22.280 [2]
Authorisation of an MCData user to request a list of which MCData groups a user has affiliated to
Y
Y
Y
[R-6.4.6.1-002],
[R-6.4.6.1-003] of 3GPP TS 22.280 [2]
Authorisation to change affiliated groups of other specified user(s)
Y
Y
Y
[R-6.4.6.2-001],
[R-6.4.6.2-002] of 3GPP TS 22.280 [2]
Authorisation to recommend to specified user(s) to affiliate to specific group(s)
Y
Y
Y
[R-6.6.1-004] of 3GPP TS 22.280 [2]
Authorisation to perform regrouping
Y
Y
Y
Y
[R-6.7.2-001] of 3GPP TS 22.280 [2]
Presence status is available/not available to other users
Y
Y
Y
Y
[R-6.7.1-002],
[R-6.7.2-002] of 3GPP TS 22.280 [2]
List of MCData users that MCData user is authorised to obtain presence of
> MCData IDs
Y
Y
Y
Y
[R-6.8.7.4.2-001],
[R-6.8.7.4.2-002] of 3GPP TS 22.280 [2]
Authorisation of a user to cancel an emergency alert on any MCData UE of any user
Y
Y
Y
[R-6.13.4-001] of 3GPP TS 22.280 [2]
Authorisation for an MCData user to enable/disable an MCData user
Y
Y
Y
[R-6.13.4-003],
[R-6.13.4-005],
[R-6.13.4-006],
[R-6.13.4-007] of 3GPP TS 22.280 [2]
Authorisation for an MCData user to (permanently /temporarily) enable/disable a UE
Y
Y
Y
[R-7.14-002],
[R-7.14-003] of 3GPP TS 22.280 [2]
Authorization for manual switch to off-network while in on-network
Y
Y
Y
Y
[R-5.1.5-004] of 3GPP TS 22.280 [2]
Limitation of number of affiliations per user (N2)
N
Y
Y
Y
[R-6.4.6.1-001],
[R-6.4.6.1-004] of 3GPP TS 22.280 [2]
List of MCData users whose selected groups are authorized to be remotely changed
> MCData ID
Y
Y
Y
Y
[R-6.7.3-007a] of 3GPP TS 22.280 [2] and 3GPP TS 33.180 [13]
List of MCData users this MCData user is authorized to receive a one‑to-one communication
> MCData ID
Y
Y
Y
Y
> KMSUri for security domain of MCData ID
Y
Y
Y
Y
Conversation management
[R-6.1.1.2-009] of 3GPP TS 22.282 [3].
> List of MCData users to be sent message delivered disposition notifications in addition to the message sender
N
Y
Y
Y
>> MCData ID
N
Y
Y
Y
[R-6.1.1.2-009] of 3GPP TS 22.282 [3].
> List of MCData users to be sent message read disposition notifications in addition to the message sender
N
Y
Y
Y
>> MCData ID
N
Y
Y
Y
3GPP TS 23.283 [18]
Authorised to use LMR E2EE for interworking
Y
Y
Y
Y
3GPP TS 23.283 [18]
> List of supported LMR technology types
3GPP TS 23.283 [18]
>> LMR technology type (P25, TETRA etc.)
Y
N
Y
Y
3GPP TS 23.283 [18]
>> URI of LMR key management functional entity (see NOTE 4 )
Y
N
Y
Y
3GPP TS 23.283 [18]
>> LMR specific identity (RSI for P25 or ITSI for TETRA) (see NOTE 5)
Y
N
Y
Y
3GPP TS 23.283 [18]
>> LMR specific security information (see NOTE 5)
Y
N
Y
Y
List of servers used in the private and group communications
> MCData content server where the HTTP FD file is uploaded
>> Server URI
Y
Y
Y
Y
> MCData message store where the communication history stores
>> Server URI
Y
Y
Y
Y
Subclause 5.2.9 of 3GPP TS 23.280 [16]
List of partner MCData systems in which this profile is valid for use during migration
Subclause 5.2.9 of 3GPP TS 23.280 [16]
> Identity of partner MCData system
Y
Y
Y
Y
Subclause 10.1.1 of 3GPP TS 23.280 [16]
> Access information for partner MCData system (see NOTE 6)
Y
Y
Y
[R-5.9a-012] of 3GPP TS 22.280 [2]
[R-5.9a-013] of 3GPP TS 22.280 [2]
Authorised to request information query of the association between active functional alias(es) and the MCData ID(s)
Y
Y
Y
[R-6.6.4.2-002a] and [R-6.6.4.2-002b] of 3GPP TS 22.280 [2]
List of groups the client affiliates/de-affiliates when criteria is met
> MCData Group ID
Y
Y
Y
Y
>> Criteria for affiliation (see NOTE 7)
Y
Y
Y
Y
>> Criteria for de-affiliation (see NOTE 7)
Y
Y
Y
Y
>> Manual de-affiliation is not allowed if criteria for affiliation are met
Y
Y
Y
Y
[R-6.6.4.2-002] of 3GPP TS 22.280 [2]
List of groups the client affiliates after receiving an emergency alert
> MCData Group ID
Y
Y
Y
Y
>> Manual de-affiliation is not allowed if criteria for affiliation are met
Y
Y
Y
Y
List of functional alias(es) of the MCData user
[R-5.9a-005] of 3GPP TS 22.280 [2]
> Functional alias
Y
Y
Y
Y
[R-5.9a-018] of 3GPP TS 22.280 [2]
>> Trigger criteria for activation by the MCData server (see NOTE 8)
N
Y
Y
Y
[R-5.9a-017], [R-5.9a-018] of 3GPP TS 22.280 [2]
>> Trigger criteria for de-activation by the MCData server (see NOTE 8)
N
Y
Y
Y
[R-5.9a-019] of 3GPP TS 22.280 [2]
>> Trigger criteria for activation by the MCData client (see NOTE 8)
Y
Y
Y
Y
[R-5.9a-019] of 3GPP TS 22.280 [2]
>> Trigger criteria for de-activation by the MCData client (see NOTE 8)
Y
Y
Y
Y
>> Manual de-activation is not allowed if the criteria are met (see NOTE 8)
Y
Y
Y
Y
[R-5.9a-012] of 3GPP TS 22.280 [2]
Authorised to take over a functional alias from another MCData user
Y
Y
Y
Authorised to participate in an IP connectivity session
Y
Y
Y
Y
[R-5.5.2-003],
[R-5.5.2-004] 3GPP TS 22.282 [3]
>List of MCData users which can be included in IP connectivity sessions.
>> MCData ID
Y
Y
Y
Y
3GPP TS 33.180 [13]
>> KMSUri for security domain of the MCData ID
Y
Y
Y
Y
>>List of associated data host IP information
>>>IP information (see NOTE 9)
Y
Y
Y
Y
[R-5.5.2-003] 3GPP TS 22.282 [3]
Authorised to initiate remote point-to-point IP connectivity sessions
N
Y
Y
Y
>List of MCData users which can be addressed in a remote initiated IP connectivity session;
>> MCData ID
N
Y
Y
Y
[R-5.5.2-003] 3GPP TS 22.282 [3]
Authorised to tear down point-to-point IP connectivity sessions
N
Y
Y
Y
>List of MCData users which can be addressed in a remote initiated IP connectivity session tear down;
>> MCData ID
N
Y
Y
Y
[R-5.5.2-006]
3GPP TS 22.282 [3]
Authorised to request remotely application priority modification of established point-to-point IP connectivity sessions;
>List of MCData users which can be addressed remotely to change the application priority of established IP connectivity sessions;
Y
Y
Y
Y
[R-5.10-001b] 3GPP TS 22.280 [2]
Maximum number of successful simultaneous MCData service authorizations for this user (see NOTE 10)
N
Y
Y
Y
ad hoc group data communication authorizations
[R-6.15.5.3-001] of 3GPP TS 22.280 [2]
> Authorised to initiate ad hoc group data communication
Y
Y
Y
Y
R-6.15.5.3-003] of 3GPP TS 22.280 [2]
> Authorised to participate in ad hoc group data communication
Y
Y
Y
Y
> Authorised to initiate emergency ad hoc group data communication
Y
Y
Y
Y
> Authorised to initiate imminent peril ad hoc group data communication
Y
Y
Y
Y
> Authorised to receive the participants information of an ad hoc group data communication
N
Y
Y
Y
> Authorised to modify the list of participants and criteria for an ad hoc group data communication
Y
Y
Y
Y
> Authorised to release ongoing ad hoc group data communications
Y
Y
Y
Y
NOTE 1: If this parameter is not configured, authorization to use the group shall be obtained from the identity management server identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [5].
NOTE 2: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [5].
NOTE 3: The use of this parameter by the MCData UE is outside the scope of the present document.
NOTE 4: The LMR key management functional entity is part of the LMR system and is outside the scope of the present document.
NOTE 5: This is an LMR specific parameter with no meaning within MC services.
NOTE 6: Access information for each partner MCData system comprises the list of information required for initial UE configuration to access an MCData system, as defined in table A.6-1 of 3GPP TS 23.280 [16]
NOTE 7: The criteria may consist conditions such as the location of the MCData user or the active functional alias of the MCData user.
NOTE 8: The criteria may consist of conditions such as MCData user location or time.
NOTE 9: IP information may contain IP addresses, corresponding subnet masks, gateway and DNS settings.
NOTE 10: If configured, this value has precedence over the system level parameter "maximum number of successful simultaneous service authorisations" in table A.5-2. If not configured, the corresponding parameter from table A.5-2 shall be used.
NOTE 11: This is the second level control parameter to determine whether this group communication will be stored in the MCData message store when the Store communication in Message Store top level control parameter is set.
Table A.3-3: MCData user profile configuration data (off network)
Reference
Parameter description
MCData UE
MCData Server
Configuration management server
MCData user database
[R-7.2-003],
[R-7.6-004] of 3GPP TS 22.280 [2]
List of off-network MCData groups for use by this MCData user
> MCData Group ID
Y
N
Y
Y
> Store group communication in Message Store (see NOTE 4)
Y
N
Y
Y
> Application plane server identity information of group management server where group is defined
>> Server URI
Y
N
Y
Y
> Application plane server identity information of identity management server which provides authorization for group (see NOTE 1)
>> Server URI
Y
N
Y
Y
3GPP TS 33.180 [13]
> KMSUri for security domain of group (see NOTE 2)
Y
N
Y
Y
> Presentation priority of the group relative to other groups and users (see NOTE 3)
Y
N
Y
Y
[R-7.12-002],
[R-7.12-003] of 3GPP TS 22.280 [2]
Authorization for off-network services
Y
N
Y
Y
Subclause 7.16.1
User info ID (as specified in 3GPP TS 23.303 [7])
Y
N
Y
Y
NOTE 1: If this parameter is not configured, authorization to use the group shall be obtained from the identity management server identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of TS 23.280 [5].
NOTE 2: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [5].
NOTE 3: The use of this parameter by the MCData UE is outside the scope of the present document.
NOTE 4: This is the second level control parameter to determine whether this group communication will be stored in the MCData message store when the Store communication in Message Store top level control parameter is set.
A.4 MCData related Group configuration data
The general aspects of group configuration are specified in 3GPP TS 23.280 [5].
Parameters specified in table A.4-1 are child parameters of the "MCData configuration" parameter specified in table A.4-1 in 3GPP TS 23.280 [5]. Parameters specified in table A.4-2 are child parameters of the "MCData configuration" parameter specified in table A.4-2 in 3GPP TS 23.280 [5]. Parameters specified in table A.4-3 are child parameters of the "MCData configuration" parameter specified in table A.4-3 in 3GPP TS 23.280 [5].
Table A.4-1: Group configuration data (on and off network)
Reference
Parameter description
MCData UE
MCData Server
Group management server
[R-5.12-001] of 3GPP TS 22.280 [2]
>> Media confidentiality and integrity protection (see NOTE)
Y
Y
Y
[R-5.12-001] of 3GPP TS 22.280 [2]
>> Transmission control confidentiality and integrity protection (see NOTE)
Y
Y
Y
[R-5.12-001] of 3GPP TS 22.280 [2]
>> Group media protection security material (see NOTE)
Y
N
Y
Subclause 5
>> MCData sub-services and features enabled for the group
>>> Short data service enabled
Y
Y
Y
>>> File distribution enabled
Y
Y
Y
>>> IP connectivity enabled
Y
Y
Y
>>> Conversation management enabled
Y
Y
Y
>>> Transmission control enabled
Y
Y
Y
>>> Reception control enabled
Y
Y
Y
>>> Enhanced status enabled
Y
Y
Y
>> Enhanced status
[R-6.1.3.2-002] of 3GPP TS 22.282 [3]
>>> List of operational status values
Y
N
Y
[R-6.1.1.2-011] of 3GPP TS 22.282 [2]
>> Lossless communication
Y
Y
Y
[R-6.1.1.2-007] of 3GPP TS 22.282 [5]
>> Conversation hang time
Y
Y
Y
NOTE: Security mechanisms are specified in 3GPP TS 33.180 [13].
Table A.4-2: Group configuration data (on network)
Reference
Parameter description
MCData UE
MCData Server
Group management server
[R-6.4.5-001],
[R-6.4.5-003] of 3GPP TS 22.280 [2]
>> Authorisation of a user to request a list of affiliated members of a group
Y
Y
Y
[R-5.1.7-002],
[R-6.2.2-001],
[R-6.6.2.2-006],
[R-6.8.7.2-003] of 3GPP TS 22.280 [2]
>> Priority of the group
N
Y
Y
Subclause 6.2.2 of 3GPP TS 22.282 [3]
>> Transmission and reception control
>>> Maximum data size for SDS
Y
Y
Y
>>> Maximum data size for FD
Y
Y
Y
>>> Maximum data size for auto-receive
N
Y
Y
3GPP TS 23.283 [18]
>> Indication whether use of LMR E2EE is permitted on the MCData group
Y
N
Y
3GPP TS 23.283 [18]
>> LMR specific identity for MCData group (see NOTE 1)
Y
N
Y
3GPP TS 23.283 [18]
>> Group to key binding (see NOTE 1)
Y
N
Y
[R-6.2.2.1-001] of 3GPP TS 22.282 [3], [R-5.2.1-001] of 3GPP TS22.280 [2]
>> List of group members which are allowed to transmit data (see NOTE 2)
>>> MCData ID
Y
Y
Y
NOTE 1: This is an LMR specific parameter with no meaning within MC services.
NOTE 2: This parameter sets the authorization to transmit data in pre-arranged groups used in broadcast calls.
Table A.4-3: Group configuration data (off network)
Reference
Parameter description
MCData UE
MCData Server
Group management server
Subclause 10.10 of 3GPP TS 23.280 [5]
>> Default ProSe Per-Packet priority (as specified in 3GPP TS 23.303 [7]) values
>>> MCData group call signalling
Y
N
Y
>>> MCData group call media
Y
N
Y
A.5 MCData service configuration data
The general aspects of MC service configuration are specified in 3GPP TS 23.280 [5]. The MCData service configuration data is stored in the MCData server.
Tables A.5-1 and A.5-2 describe the configuration data required to support the use of on-network MCData service. Tables A.5-1 and A.5-3 describe the configuration data required to support the use of off-network MCData service. Data in tables A.5-1 and A.5-3 can be configured offline using the CSC-11 reference point.
Table A.5-1: MCData service configuration data (on and off network)
Reference
Parameter description
MCData UE
MCData Server
Configuration management server
Table A.5-2: MCData service configuration data (on network)
Reference
Parameter description
MCData UE
MCData Server
Configuration management server
Subclause 6.2.2 of 3GPP TS 22.282 [3]
Transmission and reception control
> Maximum data size for SDS
Y
Y
Y
> Maximum payload data size for SDS over signalling control plane (see NOTE 1)
Y
Y
Y
> Maximum data size for FD
Y
Y
Y
[R-6.2.2.1-002d],
[R-6.2.2.4-003] of 3GPP TS 22.282 [3]
> Time limit for the temporarily stored data waiting to be delivered to a receiving user
N
Y
Y
[R-6.2.2.3-001] of 3GPP TS 22.282 [3]
> Timer for periodic announcement with the list of available recently invited data group communications
N
Y
Y
> Maximum data size for auto-receive
N
Y
Y
List of functional alias identities
[R-5.9a-005] of 3GPP TS 22.280 [17]
> Functional alias
N
Y
Y
[R-5.9a-005] of 3GPP TS 22.280 [17]
>> Limit number of simultaneous activations
N
Y
Y
[R-5.9a-005] of 3GPP TS 22.280 [17]
>> This functional alias can be taken over
N
Y
Y
>> List of users who can activate this functional alias
[R-5.9a-005] of 3GPP TS 22.280 [17]
>>> MCData ID
N
Y
Y
[R-5.9a-016] of 3GPP TS 22.280 [17]
>> Communication priority (see NOTE 2)
N
Y
Y
[R-5.10-001a] of 3GPP TS 22.280 [2]
Maximum number of successful simultaneous service authorizations of clients from a user
N
Y
Y
MCData notification server
> Server URI(s)
Y
Y
Y
Ad hoc group data communication configurations
[R-6.15.5.3-005] of 3GPP TS 22.280 [2]
> Support of ad hoc group data communication (enabled/disabled) (see NOTE 3)
Y
Y
Y
[R-6.15.5.3-002] of 3GPP TS 22.280 [2]
> Maximum number of participants allowed to participate in an ad hoc group data communication
Y
Y
Y
[R-6.15.5.3-004] of 3GPP TS 22.280 [2]
> Hang timer for ad hoc group data communication
N
Y
Y
> Maximum duration for ad hoc group data communication
Y
Y
Y
> List of preferred media codecs for ad hoc group data communication
Y
Y
Y
NOTE 1: The maximum payload data size for SDS over signalling control plane shall be less than or equal to the maximum data size for SDS.
NOTE 2: The usage of this parameter by the MCData server is up to implementation.
NOTE 3: If the support for ad hoc group data communication is disabled by the MC system then all other configurations related to ad hoc group data communication are not applicable
Table A.5-3: MCData service configuration data (off network)
Reference
Parameter description
MCData UE
MCData Server
Configuration management server
Subclause 10.10 of 3GPP TS 23.280 [5]
Default ProSe Per-Packet priority (as specified in 3GPP TS 23.303 [7]) values
> MCData one-to-one call signalling
Y
N
Y
> MCData one-to-one call media
Y
N
Y
Annex B (informative):
Transmission control for MCData
B.1 Overview of transmission control process
The MCData server may receive several simultaneous requests for data transmission, which may be associated with different types of communication e.g. group, private, 1-to-many. For each communication, how the requests are processed may be different. The requests that are not authorized shall be rejected by the transmission control function. For message requests over the signalling control plane, the processing should be immediate and is delivered to the recipients either via unicast or broadcast. However, for message requests over the media plane, transmission control arbitration (see Annex B.2) will be necessary. Subsequent to transmission control arbitration, and subject to the policy e.g. store and forward, the data is either delivered directly to the recipient MCData user or stored in the network repository and a corresponding URL is delivered. The end-to-end transmission control process is illustrated in figure B.1-1.
Figure B.1-1: Transmission control process
B.2 Transmission control arbitration
The transmission control arbitration is a central function of the transmission control process and is implementation specific. In a typical deployment, multiple or simultaneous requests can be received at the transmission control arbitration function. Each of these requests may be categorized into different request types with different queuing priorities, and therefore each request type will be maintained with separate queues. Each request shall not be present in more than one queue at any given time. The queue types and the order of queues may be configured by the MCData administrator, as described below.
- Transmission control queue: It is the primary queue from which the request is processed for transmission e.g. emergency communication requests may result in this queue and processed at the highest priority.
- Communication type queue: This queue may be sorted in the order of the communication type associated with the request. For example, the group communication requests may always take precedence over one-to-many or private communication requests.
- Static attribute queue: This queue may be formed based on the static attributes associated with the request e.g. group priority, user priority, which may be pre-configured by the MCData administrator.
- Dynamic attribute queue: This queue may be formed based on the dynamic attributes associated with the request e.g. location of the sending user, content size, etc.
Annex C: Void
Annex D (informative):
Example of a User Message Storage Area
The figure in subclause 7.13.1 illustrates the high-level structure of the MCData message store where objects are stored in a flat structure in the user storage area. This flat data structure provides maximum flexibility for UI implementation to present stored objects to the user. However, a folder hierarchy structure provides a better visual presentation of the stored objects to the MCData user.
Figure D-1: User message storage area example
In figure D-1 the MCData user 1 message storage area in the MCData message store is constructed in folder hierarchical way. A system default folder, Inbox, is configured to receive all new objects coming from active communications. The MCData user 1 creates Group 1, Group 2 and Group N folders to store communication history for different group communications that he is a member of. Once the Group 1 folder is created the MCData user 1 can then move all the objects related to Group 1 communication from the Inbox to the Group 1 folder. The MCData user 1 can also create child folders in Group 1 folder to further divide the stored objects into different groupings such as with different subjects, Subject 1 and Subject 2. Similarly, the MCData user 1 creates child folders, Date 1 and Date 2, in Group N folder to store communication history in group N occurred in different dates. With this hierarchical folder structure, the MCData user 1 can browse his user account in the MCData message store interactively and navigate to the information he would like to see. For example, the MCData user 1 can start with the top-level root folder and traverse down the folder hierarchy to reach to Date 2 folder and see the communication history of group N in that particular date.
Annex E (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2016-07
Initial version.
0.0.0
2016-08
Update following SA6#12 incorporating the following pCRs:
S6-160810; S6-160875; S6-160876
0.1.0
2016-10
Update following SA6#13 incorporating the following pCRs:
S6-161169; S6-161170; S6-161243; S6-161265; S6-161085; S6-161173; S6-161174; S6-161245; S6-161176; S6-161248; S6-161177; S6-161178; S6-161266; S6-161267; S6-161184
0.2.0
2016-11
Update following SA6#14 incorporating the following pCRs:
S6-161316; S6-161586; S6-161609; S6-161587; S6-161589; S6-161506; S6-161576; S6-161507; S6-161326; S6-161508; S6-161577; S6-161511; S6-161512; S6-161616; S6-161514; S6-161515; S6-161516; S6-161580; S6-161581; S6-161519; S6-161498; S6-161642
0.3.0
2016-11
SA#74
SP-160878
Submitted for Approval at SA#74
1.0.0
2016-12
SA#74
SP-160878
MCC Editorial update for publication after TSG SA approval (SA#74)
14.0.0
2017-03
SA#75
SP-170071
0002
2
F
Alignment of definitions
14.1.0
2017-03
SA#75
SP-170071
0003
2
F
Alignment of group affiliation and de-affiliation requirements
14.1.0
2017-03
SA#75
SP-170071
0004
1
F
Alignment of bearer management
14.1.0
2017-03
SA#75
SP-170071
0005
2
D
Adding descriptive text for the FD procedure section
14.1.0
2017-03
SA#75
SP-170071
0006
2
D
Resolving editor's notes for the short data service feature
14.1.0
2017-03
SA#75
SP-170071
0007
1
D
Adding references for the signalling control plane
14.1.0
2017-03
SA#75
SP-170071
0008
2
D
Adding descriptive text for the transmission and reception control section
14.1.0
2017-03
SA#75
SP-170071
0009
F
MCData correction of reference
14.1.0
2017-03
SA#75
SP-170071
0010
F
Alignment of business relationships, identities, and application of functional model to deployments
14.1.0
2017-03
SA#75
SP-170071
0011
3
F
file download editorials
14.1.0
2017-03
SA#75
SP-170071
0013
1
F
Off-network conversation management
14.1.0
2017-03
SA#75
SP-170071
0014
1
D
Editorial corrections
14.1.0
2017-03
SA#75
SP-170071
0015
1
F
Resolving EN in Scope
14.1.0
2017-03
SA#75
SP-170071
0016
5
F
Resolving EN in Functional model
14.1.0
2017-03
SA#75
SP-170071
0017
1
F
Resolving EN in SDS procedures
14.1.0
2017-03
SA#75
SP-170071
0018
F
Referring generic procedures from CFA
14.1.0
2017-03
SA#75
SP-170071
0020
2
F
Conversation management definitions
14.1.0
2017-03
SA#75
SP-170071
0021
2
F
Disposition alignments and corrections in SDS and FD
14.1.0
2017-03
SA#75
SP-170071
0022
1
F
Tx and Rx control procedure corrections
14.1.0
2017-03
SA#75
SP-170071
0025
1
F
MCData functional model alignment
14.1.0
2017-03
SA#75
SP-170071
0027
1
F
Moving configuration data to on-network only
14.1.0
2017-03
SA#75
SP-170071
0028
3
F
Resolve SDS on-network information flows EN
14.1.0
2017-03
SA#75
SP-170071
0030
1
F
Resolve FD information flows EN
14.1.0
2017-03
SA#75
SP-170071
0031
2
F
Adding end-to-end encryption requirements
14.1.0
2017-03
SA#75
SP-170071
0032
1
F
Resolve transmission control information flows EN
14.1.0
2017-03
SA#75
SP-170071
0033
2
F
Resolve conversation management EN
14.1.0
2017-03
SA#75
SP-170071
0034
1
F
Addition of definition for MCData ID
14.1.0
2017-03
SA#75
SP-170071
0035
F
Addition of definition for MCData ID
14.1.0
2017-03
SA#75
SP-170071
0036
3
F
Off-network information flows for SDS
14.1.0
2017-03
SA#75
SP-170071
0037
1
F
Resolve communication release information flows EN
14.1.0
2017-03
SA#75
SP-170071
0038
1
F
Conditions for using SDS media plane
14.1.0
2017-06
SA#76
SP-170392
0039
2
F
Correction on MCData reference points when using MBMS
14.2.0
2017-06
SA#76
SP-170392
0048
D
Additions to Definition and Abbreviations
14.2.0
2017-06
SA#76
SP-170392
0049
2
F
Clarifications to section 5 Arcitecture requirements
14.2.0
2017-06
SA#76
SP-170392
0051
1
F
Clarifications to section 6.5.1 that SDS Distribution function in MCData server talks to SDS function in MCData client not UE
14.2.0
2017-06
SA#76
SP-170392
0052
F
Clarifications to section 6.5.3.1.2
14.2.0
2017-06
SA#76
SP-170392
0054
1
D
Correct wrong reference in section 7.2
14.2.0
2017-06
SA#76
SP-170392
0056
3
F
Correct the MCData data disposition notification IEs
14.2.0
2017-06
SA#76
SP-170392
0058
1
D
Consistent use of pre-condition in section 7.4.2.2.2
14.2.0
2017-06
SA#76
SP-170392
0059
1
F
Inconsistent use of MCData group ID or list of recipients in request
14.2.0
2017-06
SA#76
SP-170392
0061
3
F
Content reference URL should be a mandatory IE when uploading a file
14.2.0
2017-06
SA#76
SP-170392
0062
5
F
Addition of new configuration and miscellaneous corrections
14.2.0
2017-06
SA#76
SP-170392
0063
5
F
Addition of identity management server address per group
14.2.0
2017-06
SA#76
SP-170392
0064
F
Correction on sending data with mandatory download
14.2.0
2017-06
SA#76
SP-170392
0070
2
F
Inclusion of KMSUri to allow multiple security domains
14.2.0
2017-06
SA#76
SP-170392
0071
4
F
Clarification to Auto-send
14.2.0
2017-06
SA#76
SP-170392
0076
F
Corrections to Group configuration data for all MC services
14.2.0
2017-06
SA#76
SP-170392
0078
2
F
CR to 23.282 on Auto-receive
14.2.0
2017-06
SA#76
SP-170394
0040
4
B
Information flow of File Distribution for off-network
15.0.0
2017-06
SA#76
SP-170394
0041
1
B
Functional model of File Distribution for off-network
15.0.0
2017-06
SA#76
SP-170394
0075
1
C
Functional model of File Distribution for off-network
15.0.0
2017-09
SA#76
SP-170682
0079
2
B
Introduction of SDS application type identifiers
15.1.0
2017-09
SA#76
SP-170685
0080
1
B
Addition of IWF and IWF-2
15.1.0
2017-09
SA#76
SP-170681
0083
1
A
File size check for FD
15.1.0
2017-09
SA#76
SP-170681
0085
1
A
Correction to configuration for Auto-receive parameter
15.1.0
2018-01
SA#78
SP-170891
0087
1
F
SDS location field: Alignment of Stage 2 with Stage 1 & Stage 3
15.2.0
2018-01
SA#78
SP-170891
0088
1
D
Editorial changes to MCData stage 2
15.2.0
2018-01
SA#78
SP-170895
0089
1
F
Adding application identifier in media plane SDSs
15.2.0
2018-01
SA#78
SP-170891
0090
1
F
Off-network Conversation Management clarifications
15.2.0
2018-01
SA#78
SP-170889
0094
2
A
PSI configuration for MCData service
15.2.0
2018-01
SA#78
SP-170891
0095
1
F
Completion of Communication Release
15.2.0
2018-01
SA#78
SP-170894
0096
1
F
MBMS packet recovery
15.2.0
2018-04
SA#79
SP-180148
0099
1
A
Correction of security specification references
15.3.0
2018-04
SA#79
SP-180155
0100
3
B
LMR E2EE user profile and group parameters
15.3.0
2018-04
SA#79
SP-180148
0102
2
A
Payload size limit for standalone SDS over signalling control plane
15.3.0
2018-04
SA#79
SP-180151
0103
1
F
Update of references to stage 1 specifications
15.3.0
2018-04
SA#79
SP-180148
0107
1
A
Duplicated procedure name for MCData Group SDS
15.3.0
2018-06
SA#80
SP-180367
0109
A
Clarification for presentation priority in MCData UE configuration
15.4.0
2018-06
SA#80
SP-180370
0110
3
A
Modify MCData download data response
15.4.0
2018-09
SA#81
SP-180677
0111
2
C
Media storage function in the MCData server
16.0.0
2018-09
SA#81
SP-180677
0113
3
C
Adding the Network base Message Store
16.0.0
2018-12
SA#82
SP-181178
0116
1
F
Corrections on CR implementation errors
16.1.0
2018-12
SA#82
SP-181178
0117
1
F
Configuration parameters to support requirement [R-6.1.1.2-009] are incorrect
16.1.0
2018-12
SA#82
SP-181178
0118
2
F
Corrections to Table A.2-1, Table A.4-2 and Table A.5-2
16.1.0
2018-12
SA#82
SP-181178
0119
4
F
Corrections to "Release of MCData communication using HTTP" procedures
16.1.0
2018-12
SA#82
SP-181178
0120
1
F
Alignment with the MCData content server
16.1.0
2018-12
SA#82
SP-181178
0121
1
F
There is no file download when using media plane for FD
16.1.0
2018-12
SA#82
SP-181178
0122
2
B
Procedures for MCData message store operations
16.1.0
2018-12
SA#82
SP-181178
0123
1
F
Correct misalignment on MCData user usage
16.1.0
2019-03
SA#83
SP-190074
0124
-
F
Correct the location of MCData content server and MCData message store configuration parameters in table A.3-2 configuration table
16.2.0
2019-03
SA#83
SP-190074
0125
-
D
Editorial correction on the term of MCData
16.2.0
2019-03
SA#83
SP-190074
0126
2
B
Additional architecture requirement for MCData message store
16.2.0
2019-03
SA#83
SP-190074
0127
2
B
Generic SDS procedure with MCData message store
16.2.0
2019-03
SA#83
SP-190074
0128
3
B
Providing data for a user entering an ongoing MCData group conversation
16.2.0
2019-03
SA#83
SP-190075
0130
1
B
MCData user profile migration information
16.2.0
2019-03
SA#83
SP-190074
0131
2
F
Message store object and metadata
16.2.0
2019-03
SA#83
SP-190075
0132
1
B
Introduction of gateway MC server for interconnection
16.2.0
2019-03
SA#83
SP-190074
0133
2
B
Example of user storage area with folder hierarchy structure
16.2.0
2019-03
SA#83
SP-190074
0134
2
C
Making data sync between MCData message store and message store client bi-directional
16.2.0
2019-03
SA#83
SP-190074
0135
1
B
Add more operations to the MCData message store
16.2.0
2019-03
SA#83
SP-190074
0136
1
B
Off-network SDS with MCData message store
16.2.0
2019-06
SA#84
SP-190488
0137
1
B
Restricting incoming private communications
16.3.0
2019-06
SA#84
SP-190486
0138
2
B
Interconnection for file distribution
16.3.0
2019-06
SA#84
SP-190486
0139
1
B
Interconnection and migration with message store
16.3.0
2019-06
SA#84
SP-190488
0140
2
B
User configuration for functional alias information query for MCData
16.3.0
2019-06
SA#84
SP-190488
0141
1
B
User requested priority in 23.281
16.3.0
2019-06
SA#84
SP-190488
0142
3
B
Criteria based automatic group affiliation and deaffiliation
16.3.0
2019-06
SA#84
SP-190488
0143
2
B
MCData configuration for functional alias
16.3.0
2019-06
SA#84
SP-190488
0144
4
B
Functional alias support configuration items
16.3.0
2019-06
SA#84
SP-190488
0145
3
B
Functional alias supplements for the MCData transmission and reception control procedures
16.3.0
2019-06
SA#84
SP-190488
0147
2
B
Functional alias support for Short Data Service (SDS)
16.3.0
2019-06
SA#84
SP-190488
0148
3
B
MC Data User IP connectivity service capability– part 1 Functional Architecture
16.3.0
2019-06
SA#84
SP-190488
0149
1
C
MCData transport capabilties for IP connectivity service
16.3.0
2019-06
SA#84
SP-190485
0150
6
B
MCData File Distribution using the MBMS download delivery method
16.3.0
2019-06
SA#84
SP-190485
0151
-
C
Remove the procedure in 7.5.2.9 File removal using HTTP by MCData server
16.3.0
2019-06
SA#84
SP-190485
0152
2
F
Remove the duplicated MCData server URI in UE configuration table
16.3.0
2019-06
SA#84
SP-190485
0153
3
F
Add lossless communication to network group configuration and fix missing configuration parameter
16.3.0
2019-06
SA#84
SP-190485
0154
2
F
Resolution proposals for some Editor's Notes
16.3.0
2019-06
SA#84
SP-190488
0155
B
MCData client performs automatic activation and deactivation of functional aliases based on location
16.3.0
2019-06
SA#84
SP-190488
0156
B
MCData server limits the number of simultaneous successful service authorisations
16.3.0
2019-06
SA#84
SP-190488
0157
3
B
Functional alias support for MCData File Distribution
16.3.0
2019-06
SA#84
SP-190488
0159
3
B
MC Data User IP connectivity service capability– part 2 IP connectivity for Point-to-Point and Group communication
16.3.0
2019-09
SA#85
SP-190729
0161
3
F
Correct the configuration parameters for the MCData emergency alert procedures
16.4.0
2019-09
SA#85
SP-190729
0169
1
F
Fix omission of location services in MCData
16.4.0
2019-09
SA#85
SP-190729
0170
2
B
EPS bearer for emergency
16.4.0
2019-09
SA#85
SP-190729
0171
2
B
Emergency support for one-to-one SDS
16.4.0
2019-09
SA#85
SP-190729
0172
2
B
Emergency and imminent peril support for group SDS
16.4.0
2019-09
SA#85
SP-190729
0173
2
B
Emergency support for off-network SDS
16.4.0
2019-09
SA#85
SP-190729
0174
2
C
Addition of Location infomation to SDS and Enhance Status
16.4.0
2019-09
SA#85
SP-190732
0177
1
F
Fixing the user profile configuration data for criteria triggered functional alias activation and de-activation
16.4.0
2019-09
SA#85
SP-190732
0178
F
Stage 1 requirement reference correction in the user profile data
16.4.0
2019-09
SA#85
SP-190729
0179
2
F
Clarification and corrections to support transmission control
16.4.0
2019-09
SA#85
SP-190729
0180
2
F
Corrections to the transmission and reception control procedures
16.4.0
2019-09
SA#85
SP-190729
0183
1
B
One-to-one SDS Session upgrade to emergency session
16.4.0
2019-09
SA#85
SP-190729
0184
1
B
Group SDS Session upgrade to emergency/imminent-peril session and cancel in-progress emergency/ imminent-peril group state
16.4.0
2019-09
SA#85
SP-190729
0185
2
B
One-to-One Emergency MCData FD
16.4.0
2019-09
SA#85
SP-190729
0186
1
B
Group emergency MCData FD
16.4.0
2019-09
SA#85
SP-190729
0187
1
B
One-to-one FD Session upgrade to emergency session
16.4.0
2019-09
SA#85
SP-190729
0188
1
B
Group FD communication upgrade to emergency/imminent-peril communication and cancel in-progress emergency/imminent-peril group state
16.4.0
2019-09
SA#85
SP-190735
0162
2
B
Point-to-Point IP connectivitity using functional alias to address the target MCData user
17.0.0
2019-09
SA#85
SP-190735
0163
2
B
SDS addressing based on functional alias
17.0.0
2019-09
SA#85
SP-190735
0164
4
B
Remote initiation of Point-to-Point IP connectivity
17.0.0
2019-09
SA#85
SP-190735
0165
4
B
Remote tear down of point-to-point IP connectivity
17.0.0
2019-09
SA#85
SP-190735
0166
1
B
Communication priority for functional aliases
17.0.0
2019-09
SA#85
SP-190735
0181
3
B
File distribution addressing based on functional alias
17.0.0
2019-09
SA#85
SP-190735
0182
2
B
IP connectivity for group communication (unicast)
17.0.0
2019-09
SA#85
SP-190735
0189
3
B
Capability to change remotely the priority of the point-to-point IP connectivity communication
17.0.0
2019-12
SA#86
SP-191113
0190
2
F
Requested Priority in IP connectivity point to point communication
17.1.0
2019-12
SA#86
SP-191113
0191
1
B
Enhancing SDS data requests with application priority capabilities in on-network mode
17.1.0
2019-12
SA#86
SP-191113
0193
2
B
Priority of the user
17.1.0
2019-12
SA#86
SP-191108
0196
A
File repair with the content storage function
17.1.0
2020-03
SA#87-E
SP-200113
0197
2
A
Correction of internal clause references for Enhanced Status transmission
17.2.0
2020-03
SA#87-E
SP-200117
0199
2
C
Corrections and enhancements to IP Connectivity
17.2.0
2020-03
SA#87-E
SP-200113
0200
2
A
Enhancements and clarifications for file repair and file delivery using MBMS
17.2.0
2020-03
SA#87-E
SP-200113
0201
2
A
Clarification on prepending the MCData content server URI
17.2.0
2020-03
SA#87-E
SP-200113
0202
1
A
Local policies at Partner MCData system is not applied
17.2.0
2020-03
SA#87-E
SP-200117
0208
1
F
Clarifications for MCData file distribution over MBMS
17.2.0
2020-04
-
-
-
-
-
MCC editorial correction, adding missing line break in clause 6.6.2
17.2.1
2020-07
SA#88-E
SP-200341
0212
1
B
Add the network MCData notification Server
17.3.0
2020-07
SA#88-E
SP-200341
0213
1
B
Add new "search folder" and "retrieve folder content" operations
17.3.0
2020-07
SA#88-E
SP-200341
0214
F
Pre-emption of EPS bearers by a new MCData bearer
17.3.0
2020-07
SA#88-E
SP-200341
0215
F
Miscellaneous small corrections
17.3.0
2020-07
SA#88-E
SP-200341
0216
1
F
Corrections to the one-to-one SDS information elements
17.3.0
2020-07
SA#88-E
SP-200341
0217
1
F
Minor editorial corrections
17.3.0
2020-07
SA#88-E
SP-200341
0218
F
Corrections to the one-to-one SDS and FD communication upgrade flows
17.3.0
2020-07
SA#88-E
SP-200341
0219
F
Corrections to the MCData group standalone FD request information elements
17.3.0
2020-07
SA#88-E
SP-200341
0220
F
Corrections to the group SDS informational elements
17.3.0
2020-07
SA#88-E
SP-200341
0221
F
Corrections to the group FD upgrade and FD in-progress priority state cancel request
17.3.0
2020-07
SA#88-E
SP-200341
0222
F
MCData corrections in off-network SDS procedures
17.3.0
2020-09
SA#89-E
SP-200843
0226
1
B
Limit the number of simultaneous logins on per user basis
17.4.0
2020-09
SA#89-E
SP-200839
0227
1
A
Removal of content reference IE from the FD requests using media plane
17.4.0
2020-09
SA#89-E
SP-200845
0228
1
F
Functional alias handling for 1-1 FD requests
17.4.0
2020-09
SA#89-E
SP-200845
0229
1
F
Functional alias handling for one-one session SDS requests
17.4.0
2020-09
SA#89-E
SP-200845
0230
1
F
Functional alias handling for one-one standalone SDS requests
17.4.0
2020-09
SA#89-E
SP-200845
0231
1
F
Functional alias handling for IPCon
17.4.0
2020-09
SA#89-E
SP-200845
0232
1
B
Providing stored files in MCData content server for FD over MBMS
17.4.0
2020-09
SA#89-E
SP-200845
0233
1
C
Enhancement of MBMS user service usage procedures
17.4.0
2020-09
SA#89-E
SP-200845
0234
1
C
Enhancement of Group standalone FD using MBMS
17.4.0
2020-09
SA#89-E
SP-200845
0236
1
F
MCData emergency group communication clarifications
17.4.0
2020-09
SA#89-E
SP-200845
0237
1
F
MCData one-to-one emergency communication clarifications
17.4.0
2020-09
SA#89-E
SP-200845
0238
1
F
Clarifications on the use of ProSe in off-network MCData communications
17.4.0
2020-09
SA#89-E
SP-200845
0239
1
F
Apply transmission and reception control to all FD HTTP procedures consistently
17.4.0
2020-09
SA#89-E
SP-200845
0240
F
Functional alias handling for 1-1 FD requests using HTTP
17.4.0
2020-12
SA#90-E
SP-200989
0242
1
A
Align Annex B with changes to "auto-send"
17.5.0
2020-12
SA#90-E
SP-200989
0243
2
A
Correction to the transmission control configuration parameters
17.5.0
2020-12
SA#90-E
SP-200996
0246
F
Various corrections
17.5.0
2020-12
SA#90-E
SP-200989
0248
A
IP connectivity, SDS and FD functional model correction
17.5.0
2020-12
SA#90-E
SP-200996
0249
B
Application specific metadata container
17.5.0
2020-12
SA#90-E
SP-200996
0250
1
F
Removal of duplicate MCData disposition notification information flow
17.5.0
2020-12
SA#90-E
SP-200996
0251
F
Corrections to FD using procedures and editorials
17.5.0
2020-12
SA#90-E
SP-200996
0252
1
B
Depositing file contents distributed via FD communication using HTTP into MCData message store
17.5.0
2020-12
SA#90-E
SP-200996
0253
1
B
Distribution of file residing in MCData message store account of the MCData user
17.5.0
2021-04
SA#91-E
SP-210178
0255
1
B
Message Store control
17.6.0
2021-04
SA#91-E
SP-210178
0256
1
F
Corrections to FD using media plane
17.6.0
2021-04
SA#91-E
SP-210178
0257
F
Correction to Deposit an Object procedure
17.6.0
2021-04
SA#91-E
SP-210178
0258
D
Correct typos on information tables
17.6.0
2021-04
SA#91-E
SP-210178
0259
1
F
Correction and clarification on file upload using HTTP procedure
17.6.0
2021-04
SA#91-E
SP-210178
0260
F
Correction to message names in some procedures
17.6.0
2021-04
SA#91-E
SP-210178
0261
1
F
Add the IE of Emergency indicator in the message of MCData FD request
17.6.0
2021-04
SA#91-E
SP-210178
0263
1
B
Addition of MBMS delivery via MB2 interface for MCData
17.6.0
2021-04
SA#91-E
SP-210178
0264
1
F
Corrections to the file distribution using HTTP procedures
17.6.0
2021-04
SA#91-E
SP-210178
0265
1
B
MCData file upload using HTTP including request of network resources with required QoS
17.6.0
2021-06
SA#92-E
SP-210487
0263
3
B
Corrections and enhancements to the Notification procedures
17.7.0
2021-06
SA#92-E
SP-210487
0269
2
F
Aggregated notifications and reports
17.7.0
2021-06
SA#92-E
SP-210487
0270
1
F
Correct misuse of the term "transmission control"
17.7.0
2021-06
SA#92-E
SP-210487
0271
1
B
MCData file download including request of network resources with required QoS
17.7.0
2021-06
SA#92-E
SP-210487
0272
1
C
Enhancement and corrections to group file distribution using HTTP
17.7.0
2021-06
SA#92-E
SP-210487
0273
1
C
Enhancement and corrections to one-to-one file distribution using HTTP
17.7.0
2021-06
SA#92-E
SP-210567
0274
1
F
Correction to MCData-5 reference point description
17.7.0
2021-06
SA#92-E
SP-210487
0275
1
F
EN resolutions in clause 5
17.7.0
2021-06
SA#92-E
SP-210487
0276
1
F
EN resolutions in clause 6
17.7.0
2021-06
SA#92-E
SP-210487
0277
1
F
EN resolutions in clause 7
17.7.0
2021-06
SA#92-E
SP-210487
0278
1
F
EN resolution in B.1
17.7.0
2021-06
SA#92-E
SP-210487
0279
2
F
Proposal on Data Streaming service
17.7.0
2021-09
SA#93-E
SP-210962
0281
F
Various fixes for 23.282
17.8.0
2021-09
SA#93-E
SP-210962
0282
F
Notification URL correction
17.8.0
2021-09
SA#93-E
SP-210962
0283
F
Clarify the supports of stored and forward functionality
17.8.0
2021-09
SA#93-E
SP-210962
0284
1
F
Correction of preconditions and statements related to storing of MCData communication into Message store
17.8.0
2021-09
SA#93-E
SP-210962
0285
1
F
Clarifying the use of deposit file indication IE in MCData FD request using HTTP
17.8.0
2021-09
SA#93-E
SP-210962
0286
1
F
Clarifying the lossless communication
17.8.0
2021-12
SA#94-E
SP-211523
0287
F
Clarify MCData service delivery for offline users and delivery notification
17.9.0
2021-12
SA#94-E
SP-211523
0288
1
F
Missing information table for the notification message
17.9.0
2021-12
SA#94-E
SP-211523
0289
2
F
Disposition Type of specified MCData users
17.9.0
2021-12
SA#94-E
SP-211523
0291
1
F
Clarification on the use of MCData notification server(s)
17.9.0
2021-12
SA#94-E
SP-211529
0290
1
B
Connection authorisation configuration data
18.0.0
2022-06
SA#96
SP-220476
0294
F
Corrections to the use of MC service system
18.1.0
2022-06
SA#96
SP-220477
0295
1
B
Decoupling signalling and media for MCData service capabilities
18.1.0
2022-06
SA#96
SP-220476
0296
B
Allow the user to restrict the dissemination of the location information – MCData Configuration
18.1.0
2022-09
SA#97-E
SP-220924
0297
1
F
MCData communication to a FA user
18.2.0
2022-09
SA#97-E
SP-220924
0298
1
B
Call connect and disconnect over MBMS for MCData
18.2.0
2023-03
SA#99
SP-230289
0300
2
B
User profile configuration data to support MCData ad hoc group emergency alerts
18.3.0
2023-03
SA#99
SP-230287
0303
2
C
MCData user profile configuration parameters for location information
18.3.0
2023-03
SA#99
SP-230289
0304
2
B
Information flows and procedures for the ad hoc group data communication for SDS and FD services of MCData
18.3.0
2023-03
SA#99
SP-230289
0305
1
B
Description for the terms used in the Ad hoc Group Communication procedures
18.3.0
2023-03
SA#99
SP-230289
0306
1
B
Configuration parameters of Ad hoc group data communication for MCData
18.3.0
2023-06
SA#100
SP-230709
0307
1
B
Adds user profile data for allowing subsequent MCData communications after an adhoc group emergency alert
18.4.0
2023-06
SA#100
SP-230709
0308
1
B
Configuration for receiving the adhoc group emergency alert participants list notification (MCData)
18.4.0
2023-06
SA#100
SP-230709
0309
3
F
Example of MCData services which are not handled by SIP core
18.4.0
2023-06
SA#100
SP-230709
0310
B
Notifying authorized user about adhoc group participants list involving single MC systems - MCData
18.4.0
2023-06
SA#100
SP-230709
0311
2
B
Information flows and procedures involving multiple systems for the ad hoc group data session in MCData
18.4.0
2023-06
SA#100
SP-230709
0312
2
F
Corrections for ad hoc group data communication setup
18.4.0
2023-06
SA#100
SP-230709
0313
2
F
Correct MCData ID usage in information flow table
18.4.0
2023-06
SA#100
SP-230709
0314
1
F
MCData ad hoc group ID correction
18.4.0
2023-06
SA#100
SP-230709
0315
2
F
Remove unnecessary information flow tables
18.4.0
2023-06
SA#100
SP-230709
0316
1
B
Updates adhoc group call procedures for allowing a subsequent MCData communication after an adhoc group emergency alert
18.4.0
2023-09
SA#101
SP-230998
0319
1
F
Adding references on group definitions (MCData)
18.5.0
2023-09
SA#101
SP-231004
0323
1
F
Missing configuration for ad hoc group MCData communication
18.5.0
2023-09
SA#101
SP-231004
0324
1
F
Missing pre-conditions and steps for ad hoc group MCData communication
18.5.0
2023-09
SA#101
SP-231002
0317
3
B
Information flows and procedures to support ad hoc group standalone short data service using signalling control plane
19.0.0
2023-09
SA#101
SP-230999
0318
1
B
Addition of location Information Element to FD message
19.0.0
2023-09
SA#101
SP-231002
0320
1
B
Modify list of participants by changing the criteria during an ongoing MCData ad hoc group communication (single MC system)
19.0.0
2023-09
SA#101
SP-230999
0321
1
B
Clarifications on temporary and pre-arranged MCData Broadcast Groups
19.0.0
2023-12
SA#102
SP-231556
0325
1
F
Correction in procedure on changing the criteria during an ongoing MCData ad hoc group communication (single MC system)
19.1.0
2023-12
SA#102
SP-231556
0326
2
B
Changing the criteria during an ongoing MCData ad hoc group data session (multiple MC systems)
19.1.0
2023-12
SA#102
SP-231558
0331
1
A
Configuration for authorising modification of ad hoc group data communication participants - mcdata
19.1.0
2023-12
SA#102
SP-231556
0332
1
B
Configuration for authorising modification of ad hoc group emergency alert participants - mcdata
19.1.0
2023-12
SA#102
SP-231556
0333
F
Corrections to file availability request flow between Content and MCData server
19.1.0
2023-12
SA#102
SP-231556
0334
F
Corrections to clause reference and updating the descriptive text box of ad hoc group procedure figures
19.1.0
2023-12
SA#102
SP-231558
0336
1
A
Modification of ad hoc group data communication participants involving multiple MCData systems
19.1.0
2023-12
SA#102
SP-231558
0339
1
A
Correction to modification of ad hoc group data communication participants procedure
19.1.0
2023-12
SA#102
SP-231556
0341
1
F
Corrections on modifying the criteria during an ad hoc group data communication (MCData)
19.1.0
2023-12
SA#102
SP-231558
0343
1
B
Adhoc group data communication release by an authorized user (MCData)
19.1.0
2024-03
SA#103
SP-240314
0342
2
B
Change list of participants when criteria was used to setup the ad hoc group call (MCData)
19.2.0
2024-06
SA#104
SP-240768
0349
1
B
Information flows and procedures to support ad hoc group standalone file distribution using HTTP procedures
19.3.0
2024-06
SA#104
SP-240758
0355
1
A
Removal of GW MC service ID
19.3.0
2024-06
SA#104
SP-240757
0357
1
A
Ambiguity on routing request message
19.3.0
2024-06
SA#104
SP-240757
0360
1
A
IP address(es) of target data host(s) or server(s)
19.3.0
2024-09
SA#105
SP-241224
0361
1
B
Include application data in MCData IPcon request and response
19.4.0
2024-09
SA#105
SP-241218
0363
1
A
Clarification on Message store
19.4.0
2024-09
SA#105
SP-241224
0365
1
F
Update the pre-conditions of clause 7.17.3.1.4
19.4.0
2024-09
SA#105
SP-241224
0366
1
B
Migration during Ad hoc group call procedure
19.4.0
2024-12
SA#106
SP-241722
0367
1
B
Target MCData user configuration for recording
19.5.0
2024-12
SA#106
SP-241723
0368
1
C
Adding information elements to ad hoc group data session
19.5.0
2024-12
SA#106
SP-241722
0369
1
C
Clarification for Location user profile for MCData
19.5.0
2024-12
SA#106
SP-241707
0371
A
Corrections to the FD file removal procedures
19.5.0
2024-12
SA#106
SP-241723
0373
1
F
Update the ad-hoc group call modify procedures
19.5.0
2024-12
SA#106
SP-241722
0374
1
F
Corrections of MCPTT term used in MCData
19.5.0
2025-03
SA#107
SP-250211
0376
1
F
Remove MCData recording from Rel-19
19.6.0
2025-03
SA#107
SP-250199
0378
1
A
Adding the Off-network functional model
19.6.0
2025-06
SA#108
SP-250603
0380
1
A
Correction of clause 7.4.2.6.2
19.7.0
2025-06
SA#108
SP-250608
0383
1
A
Add statement to MCData ad hoc group communication about continuous updates to a group participant list based on criteria
19.7.0
2025-09
SA#109
SP-251057
0385
1
F
Removal of unneeded Transaction type IE
19.8.0
2025-09
SA#109
SP-251059
0388
1
F
Corrections to the information flow tables in clause 7.14.2.1.1
19.8.0
2025-09
SA#109
SP-251065
0391
1
F
Corrections to IE tables with Result return
19.8.0
2025-09
SA#109
SP-251058
0387
1
F
Clarification on the one-to-one communication
19.8.0
2026-01
SA#110
SP-251476
0393
1
F
Resolving Editor’s Note on server-to-server messages (MCData)
19.9.0
2026-01
SA#110
SP-251477
0396
1
F
Correction of procedure descriptions on various clauses
19.9.0
2026-01
SA#110
SP-251478
0395
B
Location information for server client direction in ad hoc group data session request
20.0.0
2026-01
SA#110
SP-251478
0397
1
F
Resolving Notes on server-to-server messages (MCData) information flows
20.0.0
2026-01
SA#110
SP-251478
0398
F
Clarification on Server-Server message (MCData) procedures
20.0.0
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 1 Scope
| The objective of this technical specification is to specify interworking between MC systems and LMR systems that satisfy the MCPTT requirements in 3GPP TS 22.179 [3], MCCoRe requirements in 3GPP TS 22.280 [2] and the MCData requirements (SDS only) in 3GPP TS 22.282 [4].
The present document refers to an InterWorking Function (IWF). The structure and functionality of the IWF is out of scope of the present document. The definition of reference points between the IWF and MC systems and the interactions between the IWF and MC systems are in scope of the present document.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.280: "Mission Critical Services Common Requirements (MCCoRe); Stage 1".
[3] 3GPP TS 22.179: "Mission Critical Push to Talk (MCPTT); Stage 1".
[4] 3GPP TS 22.282: "Mission Critical Data services".
[5] 3GPP TS 23.280: "Common functional architecture to support mission critical services; Stage 2".
[6] 3GPP TS 23.282: "Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2".
[7] 3GPP TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2".
[8] 3GPP TS 33.180: "Security of the mission critical service"
[9] TIA-603-D: "Land Mobile FM or PM Communications Equipment Measurement and Performance Standards".
[10] ETSI TS 103 389: "Rail Telecommunications (RT); Global System for Mobile communications (GSM); Usage of Session Initiation Protocol (SIP) on the Network Switching Subsystem (NSS) to Fixed Terminal Subsystem (FTS) interface for GSM Operation on Railways".
[11] ETSI TS 102 610: "Railways Telecommunications (RT); Global System for Mobile communications (GSM); Usage of the User-to-User Information Element for GSM Operation on Railways".
[12] ETSI TS 100 392-19-1: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 19: Interworking between TETRA and Broadband systems; Sub-part 1: Protocol specification for Interworking with 3GPP mission critical services"
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 3 Definitions, symbols and abbreviations
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 3.1 Definitions
| For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
End‑to‑End Encryption: encryption that is applied by an originating terminal or client and is decrypted only by chosen terminating terminals or clients.
User homed in the IWF: is an MC service ID that represents an LMR user in the MC system.
Interworking: a means of communication between mission critical systems and LMR systems whereby MC users obtaining service from a mission critical system can communicate with LMR users who are obtaining service from one or more LMR systems.
Interworking function: adapts LMR Systems to mission critical systems via the IWF interface and supports interworking between LMR systems and mission critical systems.
Interworking group: a group, which is composed of group members from the MC system and the LMR system and defined in the MC system or the LMR system.
LMR system: the collection of applications, services, and enabling capabilities providing a land mobile radio service offering group and private communications.
LMR user: a user of a device which allows participation in an LMR system.
NOTE: The term LMR user is defined for discussion purposes only and is out of scope of the present document.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 3.2 Abbreviations
| For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
E2EE End-to-End Encryption
IWF InterWorking Function
KEK Key Encryption Key (TETRA)
KMS Key Management Service
MC Mission Critical
MCPTT Mission Critical Push To Talk
LMR Land Mobile Radio
LMC Location Management Client
LMS Location Management Server
OTAK Over-The-Air-Key Management (TETRA)
OTAR Over-The-Air Rekeying (P25)
P25 Project 25
SDS Short Data Service
TETRA TErrestrial Trunked Radio
UE User Equipment
UKEK Unique Key Encryption Key (P25)
URI Uniform Resource Identifier
UUI User-to-User Information
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 4 Introduction
| Mission critical users currently employ a wide range of LMR mission critical Push To Talk services, and associated data capabilities where available.
The present document describes the architecture to support the interworking between the MC system and the LMR system to satisfy interworking requirements specified in 3GPP TS 22.179 [3] and 3GPP TS 22.282 [4]. Other LMR technologies may interwork as long as they conform to the present document.
The IWF, along with its LMR system, will appear as a peer interconnected MC system. This is meant as an approach for defining interactions on the IWF interface but is not intended to specify the functionality of the IWF nor meant to mandate a deployment model.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 5 Assumptions and architectural requirements
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 5.1 Key management
| Interworking requirements for key management for encrypted interworking include:
a) a mechanism to securely (i.e. authenticity, integrity, confidentiality) share an LMR E2EE traffic key for a private call sessions between a party in an MCPTT system and a party in the LMR system;
b) a mechanism to securely convey to group members, the LMR E2EE key or set of LMR E2EE keys associated with an MC service group or set of MC service groups, to be used for encryption of interworking group calls spanning the multiple systems;
c) a mechanism to securely share with temporary group members in MC systems, the LMR E2EE key(s) associated with a temporary MC service group to be used in interworking group calls spanning the multiple systems;
d) key management solutions shall not preclude the ability of an IWF to allow one or more individual Mission Critical Organizations from having sole control over and sole access to LMR E2EE traffic keys used for the entity's media traffic and users' key encryption keys (UKEKs or KEKs);
e) key management solutions shall support the ability of the IWF to decrypt/reencrypt the media traffic for zero or more groups; and,
f) for deployments where Mission Critical Organizations wish to use LMR E2EE mechanisms when interworking with LMR users:
i) a mechanism to securely provision an MC service client with the user's UKEK or KEK; and,
ii) a mechanism to convey LMR OTAR or OTAK message contents.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 5.2 Packet format
| Each LMR technology defines its own packet format for voice media transmission. For interworking sessions, there might be cases where LMR formatted media is required to be transferred between the IWF and LMR aware MCPTT clients. An example of such a case is where E2EE is used and thus the IWF is not able to decrypt the media. In such cases, media that is sent over the IWF-1 interface needs to be routed within MCPTT systems to/from LMR aware MCPTT clients using methods described in 3GPP TS 23.379 [7].
Requirements for media transmission across the IWF-1 interface include:
a) media transmission to carry the LMR formatted media between the IWF and LMR aware MCPTT clients; and
b) the MCPTT system, along with the IWF, may choose to encrypt the LMR formatted media using 3GPP mechanisms.
NOTE: The contents of the LMR formatted media is out of scope of the present document.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 6 Involved business relationships
| No business relationships have been identified.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 7 Functional model
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 7.1 General
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 7.2 Functional model description
| Figure 7.2‑1 shows the functional model for the application plane for interworking between MC systems and LMR systems. Functional entities and interfaces depicted on the right-hand side of the IWF‑x interfaces are defined in 3GPP TS 23.280 [5], 3GPP TS 23.379 [7], and 3GPP TS 23.282 [6].
Figure 7.2-1: Functional model for application plane for interworking
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 7.3 Functional entities description
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 7.3.1 IWF
| The IWF supports most of the functionality of peer MCPTT and MCData systems, with some differences, as specified in the present document. The IWF supports any necessary protocol translation and identity mapping between the MC systems and the IWF. The internal function of the IWF is out of scope of the present document.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 7.4 Reference points
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 7.4.1 Reference point IWF‑1 (between the IWF and the MCPTT server)
| The IWF‑1 reference point, which exists between the IWF and the MCPTT server, provides peer to peer interconnection between an LMR system and the MCPTT system. IWF‑1 supports a subset of MCPTT‑3 as defined in 3GPP TS 23.379 [7], with some differences, as specified in the present document. The IWF‑1 interface is supported by the same signalling plane protocol(s) as defined for MCPTT‑3 except as specified in the present document.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 7.4.2 Reference point IWF‑2 (between the IWF and the MCData server)
| The IWF‑2 reference point, which exists between the IWF and the MCData server, provides SDS interconnection between an LMR system and the MCData system. IWF‑2 supports a subset of the functionality of MCData‑SDS‑1 and MCData‑SDS‑2, as defined in 3GPP TS 23.282 [6] with some differences, as specified in the present document. The IWF‑2 interface is supported by the same signalling plane protocol(s) as defined for MCData‑3 except as specified in the present document.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 7.4.3 Reference point IWF‑3 (between the IWF and the group management server)
| The IWF‑3 reference point, which exists between the IWF and the group management server, provides group management interconnection between an LMR system and the MC system. IWF‑3 is based upon CSC‑16, as defined in 3GPP TS 23.280 [5] with some differences, as specified in the present document.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 7.4.4 Reference point IWF‑4 (between the IWF and the LMS)
| The IWF‑4 reference point, which exists between the IWF and the LMS, provides location information exchange between an LMR system and the MC system. Support of the IWF-4 reference point is optional, since there is no guarantee that the interworked LMR system can support location information.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 8 Identities
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 8.1 Identity mapping
| The IWF provides centralised support for interworking between an MCPTT or MCData system and an LMR system. In MCPTT systems, the identity of an LMR user is provided as an MCPTT ID, and the identity of an LMR group is provided as an MCPTT group ID, which can be used by the IWF to derive the corresponding identities used in an LMR system. Similarly, in MCData systems, the identity of an LMR user is provided as an MCData ID, and the identity of an LMR group is provided as an MCData group ID, which can be used by the IWF to derive the corresponding identities used in an LMR system.
Identities provided on IWF-x reference points are described in clause 8 of 3GPP TS 23.280 [5].
The IWF can perform the identity mapping between an MCPTT system or MCData system and an LMR system during exchange of signalling and media messages.
The assignment of a functional alias that belongs to the MC system to a user homed in the IWF enables the mapping to corresponding role-based addressing schemes applicable in the LMR system.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 9 Application of functional model to deployments
| No applications of functional model to deployments have been identified.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10 Procedures and information flows
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.1 Affiliation
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.