hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.14.2.4 MCData user remote initiated tear down point-to-point IP connectivity
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.14.2.5 Remote initiated point-to-point IP connectivity application priority change
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.14.2.6 Group standalone IP connectivity using media plane
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.16 Use of ProSe capabilities in off-network MCData communications
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
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].
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.17 Ad hoc group data communication
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.17.2 Common Information flows
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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.
Authorization result
M
Indicate if authorization is success or failure
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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.
Editor's Note: It is FFS if the server to server message is needed in a call request or response message.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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.
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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)
Editor's Note: It is FFS if the server to server message is needed in a call request or response message.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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)
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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).
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.17.3 Common Ad hoc group data communication procedures
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.17.3.1 Ad hoc group data communication procedures in single MCData system
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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).
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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 citeria received from the MCData client.
Pre-conditions:
1. The MCData user at MCData client 1 is authorized to initate ad hoc group data communication.
2. The MCData user at MCData client 1 wants to invite MCData users who are satisying 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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.17.3.2 Ad hoc group data communication involving multiple MC systems
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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 call follows an ad hoc group emergency alert is routed to the MCData server of the primary MC system.
2. If the ad hoc group call 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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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.
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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 citeria 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 call 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. 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.
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.
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 call 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 call 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.
NOTE 2: The ad hoc group data session request and response exchanged between MCData server 1 of primary MC system and MCData client 3/MCData client 4 will always traversal through the MCData server 2.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
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.
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.
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.
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.
NOTE: The ad hoc group data session request and response exchanged between MCData server 1 of primary MC system and MCData client 4/MCData client 5 will always traversal through the MCData server 2.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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 initate 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.
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 receives the ad hoc group data session release request and sends the ad hoc group data session release response to the MCData server 1 of the primary MCData server.
NOTE: The ad hoc group data session request and response exchanged between MCData server 1 of primary MC system and MCData client 3/MCData client 4 will always traversal through the MCData server 2.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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.
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.
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.
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.
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.
NOTE: The ad hoc group data communication request and response exchanged between MCData server 1 of primary MC system and MCData client 4/MCData client 5 will always traversal through the MCData server 2.
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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 call 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.
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.
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.
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.
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.17.4 Ad hoc group short data service data communication procedures
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.17.4.3 Ad hoc group short data service data communication procedures in single MCData system
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.17.4.4 Ad hoc group short data service data communication procedures involving multiple MC systems
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.17.5 Ad hoc group file distribution communication procedures
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.17.5.3 Ad hoc group file distribution communication procedures in single MCData system
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.17.5.4 Ad hoc group file distribution communication procedures involving multiple MC systems
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.17.6 Ad hoc group standalone short data service using signalling control plane
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.17.6.1 Information flows
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.17.6.2 Ad hoc group standalone short data service using signalling control plane common procedure
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.17.6.3 Ad hoc group standalone short data service using signalling control plane involving single MCData system
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.17.6.4 Ad hoc group standalone short data service using signalling control plane involving multiple MCData system
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.17.7 Ad hoc group standalone file distribution using HTTP procedures
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.17.7.1 Information flows
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
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
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.17.7.2 Ad hoc group standalone file distribution using HTTP involving single MCData system
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
74a89e0c2be836f74f1a8daa1b5c5f20
|
23.282
|
7.17.7.3 Ad hoc group standalone file distribution using HTTP involving multiple MCData system
| |
74a89e0c2be836f74f1a8daa1b5c5f20
|
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.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.