hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.1.3.6.2 End a media transmission – transmission control server initiated
| Figure 7.7.1.3.6.2-1 describes the procedure for ending a media transmission during an MCVideo session by the transmission control server. Only two UEs involved in the session are shown for the simplicity.
Pre-condition:
1. MCVideo session is established between MCVideo clients (client A and client B) and MCVideo server
2. Transmission control is established between transmission control participants and transmission control server.
3. Transmission control participant A and participant B have been granted the permission to transmit media and there are ongoing media transmission from transmission control participant A and participant B.
Figure 7.7.1.3.6.2-1: End a media transmission by the transmission control server
1. Transmission control server terminates the on-going media transmission from transmission control participant A due to a termination event (e.g. revoke for another priority media transmission or there are no receiving participants).
2. Transmission control server sends a transmit media end request message to transmission control participant A indicating the reason for ending the media transmission.
3. Transmission control participant A responds with a transmit media end response message to transmission control server as acknowledgement.
4. Transmission control server sends a transmit media end notify message to transmission control participant B indicating that the media transmission from transmission control participant A is terminated by the transmission control server.
5. The transmit media end notification shall cause the user of the transmission control participant B to be notified of the media transmission termination by the transmission control server.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.1.3.6.3 End a media transmission – remote MCVideo user initiated
| Figure 7.7.1.3.6.3-1 describes the procedure for ending a media transmission during an MCVideo session by a remote MCVideo user. Only two UEs involved in the session are shown for the simplicity.
Pre-condition:
1. MCVideo session is established between MCVideo clients (client A and client B) and MCVideo server
2. Transmission control is established between transmission control participants and transmission control server.
3. Transmission control participant B has been granted the permission to transmit media and there is ongoing media transmission from transmission control participant B.
4. Transmission control participant A is authorized to end the on-going media termination from transmission control participant B.
Figure 7.7.1.3.6.3-1: End a media transmission by a remote MCVideo user
1. Transmission control participant A sends a remote transmit media end request message to transmission control server including the MCVideo ID of the user at the UE of the transmission control participant B and the MCVideo ID of the user at the UE of the transmission control participant A.
2. Transmission control server checks whether the user at the UE of transmission control participant A is authorized to end the on-going media transmission from transmission control participant B. If authorized, the transmission control server ends the media transmission from transmission control participant B.
3. Transmission control server ends the on-going media transmission from transmission control participant B. The transmission control server shall send transmit media end notify messages to the transmission control participants receiving the media transmission from transmission control participant B, indicating that the transmission has ended.
4. Transmission control server responds with a remote transmit media end response message to transmission control participant A indicating that the transmission control server has ended the requested media transmission.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.1.3.7 Remotely initiated media transmission during an MCVideo session
| Figure 7.7.1.3.7-1 describes the procedure for remotely initiated media transmission during an MCVideo session by an authorized user. Only two UEs involved in the session are shown for the simplicity.
Pre-condition:
1. MCVideo session is established between MCVideo clients (client A and client B) and MCVideo server
2. Transmission control is established between transmission control participants and transmission control server and there is no ongoing media transmission.
3. The user of the UE at the transmission control participant A is authorized to remotely initiate a media transmission from transmission control participant B
Figure 7.7.1.3.7-1: Remotely initiated media transmission during an MCVideo session
1. Transmission control participant A sends a remote transmit media request message to transmission control server including the MCVideo ID of the user at the UE of the transmission control participant B and the MCVideo ID of the user at the UE of the transmission control participant A.
2. Transmission control server checks whether the user at the UE of transmission control participant A is authorized to remotely initiate a media transmission from transmission control participant B. If authorized, the transmission control server makes the determination on what action (grant, deny, or queue) to take on the request based on transmission control criteria (e.g., group policy) and determines to accept the remotely initiated transmit media request from transmission control participant A.
3. Transmission control server sends a transmit media granted message to transmission control participant B.
4. Transmission control server provides a remote transmit media response message to transmission control participant A indicating success (media transmission occurs from transmission control participant B) or a failure reason.
5. Transmission control participant B starts sending video media over the session established to the transmission control server.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.1.3.8 Transmission idle during an MCVideo session
| During silence, i.e., when no video transmission is ongoing, the transmission control server may send the transmission idle message to all transmission participants from time to time. The transmission control server sends the transmission idle message in the beginning of silence.
Figure 7.7.1.3.8-1 describes the procedure once the transmission idle message is sent from the transmission control server to the transmission control participant(s) during an already established MCVideo session. For simplicity, only three MCVideo UEs are participating in the MCVideo session.
Pre-condition:
1. MCVideo session is established between MCVideo clients (client A and client B) and MCVideo server.
2. The transmission control is established between the transmission control participants and transmission control server.
3. The transmission control participant A has been granted the permission to transmit media.
Figure 7.7.1.3.8-1: Transmission idle
1. The media transmission has ended according to clause 7.7.1.3.6.
2a – 2c. If no other MCVideo user has permission to transmit the media, then the transmission control server sends the transmission idle message to the transmission control participants.
3. The transmission control participants may notify the MCVideo users about the transmission idle i.e., silent period. Optionally, the transmission participant A, transmission participant B, and transmission participant C may send an acknowledgement to the transmission control server.
NOTE: The transmission idle may be sent multiple times during the MCVideo session.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.2 Off-network transmission control
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.2.1 General
| The procedure is for providing transmission control to MCVideo UE in an off-network case. Transmission control is performed by using transmission control information flows between the transmission control participant and the transmission control arbitrator. The transmission control arbitrator is a member MCVideo UE of the MCVideo group where the transmission rules are applied.
Off-network transmission control is based on ProSe capabilities as described in clause 7.18.
Transmission control in off-network can be performed in two ways:
- Single arbitrator: transmission participants rely on a single participant designated as transmission arbitrator for the arbitraton of transmission requests.
- Self arbitration: each transmsission participant arbitrates its own transmission based on its view of the topology.
Both of the approaches, as appropriate for the deployment model, can be adopted for MCVideo group using a configurable parameter (as defined in Annex A.4).
In the single arbitrator approach, one MCVideo client assumes the responsibility for arbitration of transmission requests for all group members within range. All requests for transmission are directed to the arbitrator, and the arbitrator checks the configured limits on the simultaneous transmissions, and grants or denies the request. If an MCVideo client is out of range of the current arbitrator, the MCVideo client is allowed to transmit and also become a transmission arbitrator. If there is insufficient capacity to carry an extra transmission i.e. the configured limit for simultaneous transmissions is reached, the MCVideo client may request that an existing transmitting MCVideo client is pre-empted; the pre-emption request is sent to the transmission arbitrator.
In the self arbitration approach, each MCVideo client decides for itself whether there is sufficient capacity to carry the transmission. If it determines that there is insufficient capacity i.e. the configured limit for simultaneous transmissions is reached, and from its perspective another transmitting MCVideo client has a lower priority, the requesting MCVideo client may send an override request directly to this other transmitting MCVideo client, which will either accept the override request and give way, or deny the override request.
In both the single arbitrator approach and the self arbitration approach, if there is insufficient capacity to carry the communication i.e. the configured limit on the simultaneous transmissions is reached, the MCVideo client may report this to the MCVideo user. The MCVideo user may decide to transmit anyway, and instruct the MCVideo client to proceed with the transmission.
NOTE: The ProSe function within the MCVideo client could determine that there is insufficient capacity to carry an MCVideo call requested by the MCVideo client, however interactions between the MCVideo client and the ProSe function are outside the scope of the present document.
Further subclauses apply to one or both of the single arbitrator approach and the self arbitration approach. Applicability is explicitly indicated in each of the relevant subclauses.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.2.2 Information flows for off-network transmission control
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.2.2.1 Transmission request
| Table 7.7.2.2.1-1 describes the information flow for the transmission request sent by a transmission participant to request for the transmission permission. This information flow is sent in unicast or broadcast.
Table 7.7.2.2.1-1: Transmission request
Information element
Status
Description
MCVideo ID
M
The identity of the MCVideo user requesting the transmission permission
Transmission priority
M
Priority of the request
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.2.2.2 Transmission granted
| Table 7.7.2.2.2-1 describes the information flow for the transmission granted sent by the transmission arbitrator, to indicate that a request for transmission is granted and media may be transmitted. This information flow is sent in unicast or broadcast.
Table 7.7.2.2.2-1: Transmission granted
Information element
Status
Description
MCVideo ID
M
Identity of the user whose client is acting as transmission arbitrator
MCVideo ID
M
Identity of the user that has been granted transmission permission
Duration
M
The time for which the granted party is allowed to transmit
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
MCVideo ID of subsequent arbitrator
O
Subsequent transmission arbitrator's identity
Acknowledgement required
O
Indicates if acknowledgement from the transmission participant is required
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.2.2.3 Transmission release
| Table 7.7.2.2.3-1 describes the information flow for transmission release sent by the transmission participant, to indicate that the media transmission is complete and transmission permission is released. This information flow is sent in unicast or broadcast.
Table 7.7.2.2.3-1: Transmission release
Information element
Status
Description
MCVideo ID
M
Identity of user releasing transmission
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.2.2.4 Transmission rejected
| Table 7.7.2.2.4-1 describes the information flow for transmission rejected sent by the transmission arbitrator, to indicate that a request for the transmission is rejected. This information flow is sent in unicast or broadcast.
Table 7.7.2.2.4-1: Transmission rejected
Information element
Status
Description
MCVideo ID
M
Identity of the user whose client is acting as transmission arbitrator
MCVideo ID of rejected party
M
Identity of user whose transmission request has been rejected
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Rejection cause
O
Indicates the cause for transmission rejection
Acknowledgement required
O
Indicates if acknowledgement from the transmission participant is required
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.2.2.5 Transmission revoked
| Table 7.7.2.2.5-1 describes the information flow for transmission revoked sent by the transmission arbitrator, to indicate that the transmission permission, that was earlier granted, is revoked. This information flow is sent in unicast or broadcast.
Table 7.7.2.2.5-1: Transmission revoked
Information element
Status
Description
MCVideo ID
M
Identity of the user whose client is acting as transmission arbitrator
MCVideo ID
M
Identity of user whose transmission permission has been revoked
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Acknowledgement required
O
Indicates if acknowledgement from the transmission participant is required
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.2.2.6 Transmission arbitration taken
| Table 7.7.2.2.6-1 describes the information flow for transmission taken sent by the transmission participant, to indicate that the transmission participant has taken the responsibility of transmission arbitration. This information flow is sent in unicast or broadcast.
Table 7.7.2.2.6-1: Transmission arbitration taken
Information element
Status
Description
MCVideo ID
M
Identity of the MCVideo user taking responsibility of transmission arbitration
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Permission to request the transmission
O
Indicates whether receiving parties are allowed to request the transmission or not (e.g. broadcast call).
Acknowledgement required
O
Indicates if acknowledgement from the transmission participant is required
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.2.2.7 Transmission arbitration release
| Table 7.7.2.2.7-1 describes the information flow for transmission arbitration release sent by the transmission arbitrator, to indicate that the responsibility of transmission arbitration is released. This information flow is sent in unicast or broadcast.
Table 7.7.2.2.7-1: Transmission arbitration release
Information element
Status
Description
MCVideo ID
M
Identity of the user whose client is acting as transmission arbitrator
MCVideo ID
O
Identity of the user whose client is being delegated transmission arbitrator function
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.2.3 Initializing transmission control – single arbitrator approach
| This subclause is applicable only in single arbitrator approach.
Figure 7.7.2.3-1 describes procedures for transmission participants when an MCVideo client initializes transmission control. The MCVideo client sends a transmission request to detect presence of a transmission arbitrator. If the MCVideo client does not receive a response to the transmission request, it sends a transmission arbitration taken message and becomes the transmission arbitrator. The MCVideo client may now transmit a video. This procedure applies when either there have been no recent MCVideo transmissions within the MCVideo group and therefore no arbitrator has been selected, or where there have been recent MCVideo transmissions which may still be ongoing, but the arbitrator cannot be reached, e.g. where MCVideo client that wants to transmit video has gone out of range of the arbitrator.
Pre-conditions:
1. An off-network group communication has been established.
2. MCVideo client 1 wishes to transmit video, and has determined that the pre-configured limit on the number of transmissions within the MCVideo group has not been reached.
Figure 7.7.2.3-1: Initializing transmission control, single arbitrator case
1. MCVideo client 1 sends a transmission request message to the MCVideo group.
2. MCVideo client 1 does not detect any response to the transmission request.
3a. MCVideo client 1 sends a transmission arbitration taken message to the MCVideo group.
3b. MCVideo user may be notified that the video can now be transmitted.
4. MCVideo client 1 transmits video to the MCVideo group.
7.7.2.3A Initializing transmission control – self arbitration approach
This subclause is applicable only in self arbitration approach.
Figure 7.7.2.3a-1 describes procedures for transmission participants when an MCVideo client initializes transmission control.
Pre-conditions:
1. An off-network group communication has been established.
2. MCVideo client 1 wishes to transmit video.
Figure 7.7.2.3a-1: Initializing transmission control, self arbitration case
1. The MCVideo client checks whether the pre-configured limit on the number of transmissions within the MCVideo group has been reached and informs the user. If the pre-configured limit on the number of transmissions within the MCVideo group has been reached, the MCVideo user may defer the transmission, or request an override as specified in subclause 7.7.2.8, or decide to continue with the transmission anyway.
NOTE: If the MCVideo user decides to transmit even if the pre-configured limit on the number of transmissions within the MCVideo group has been reached, the MCVideo user decides to accept any consequences of interference.
2. MCVideo client 1 sends a transmission arbitration taken message to the MCVideo group.
3. MCVideo client 1 transmits video to the MCVideo group.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.2.4 Transmission permission granted
| This subclause is applicable only in single arbitrator approach.
Figure 7.7.2.4-1 describes procedures for transmission participants when an MCVideo client requests for transmission permission.
The MCVideo client has detected presence of a transmission arbitrator e.g., by receiving responses to transmission arbitration control message. The MCVideo client sends a transmission request and waits for a response. The MCVideo client upon receiving a transmission granted message may transmit a video.
Pre-conditions:
1. An off-network group communication has been established.
2. At least one participant is currently transmitting video.
Figure 7.7.2.4-1: Requesting transmission permission
1. MCVideo client 2 sends a transmission request message to the MCVideo group.
2. MCVideo client 1, being the transmission arbitrator, checks if the configured limit of maximum simultaneous transmissions is already reached.
3. If the maximum simultaneous transmissions limit is not reached, MCVideo client 1 sends a transmission granted message to the MCVideo group. Transmission granted message indicates MCVideo client 2 as the intended recipient.
4. MCVideo user at MCVideo client 2 may be notified that the video can now be transmitted.
5. MCVideo client 2 transmits video to the MCVideo group.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.2.5 Transmission permission rejected
| This subclause is applicable only in single arbitrator approach.
Figure 7.7.2.5-1 describes procedures for transmission participants when an MCVideo client requests for transmission permission.
The MCVideo client has detected presence of a transmission arbitrator e.g., by receiving responses to transmission arbitration control message. The MCVideo client sends a transmission request and waits for a response.
Pre-conditions:
1. An off-network group communication has been established.
2. At least one participant is currently transmitting video.
Figure 7.7.2.5-1: Requesting transmission permission
1. MCVideo client 2 sends a transmission request message to the MCVideo group.
2. MCVideo client 1, being the transmission arbitrator, checks if the configured limit of maximum simultaneous transmissions is already reached.
3. If the maximum simultaneous transmissions limit has reached, MCVideo client 1 sends a transmission rejected message to the MCVideo group. Transmission denied message indicates MCVideo client 2 as the intended recipient. The transmission rejected message may include a rejection cause which indicates that the configured maximum transmissions limit has been reached.
4. MCVideo user at MCVideo client 2 may be notified that the video cannot be transmitted right now.
Following step 4, the MCVideo user at MCVideo client 2 may decide to transmit anyway, for example if the user knows the topology of the off-network MCVideo group and locations of the MCVideo group members and needs to transmit video to other local MCVideo group members despite causing a potential conflict with one or more other existing MCVideo transmissions within the MCVideo group. In this case, the MCVideo client follows the procedure in subclause 7.7.2.3.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.2.6 Releasing transmission permission
| This subclause is applicable in both the single arbitrator and self arbitration approaches.
Figure 7.7.2.6-1 describes procedures for transmission participants when an MCVideo client releases transmission permission.
The MCVideo client has detected presence of a transmission arbitrator e.g., by receiving responses to transmission arbitration control message. The MCVideo client stops the video transmission and sends a transmission release request.
Pre-conditions:
1. An off-network group communication has been established.
2. MCVideo client has requested transmission permission and may have received transmission permission.
Figure 7.7.2.6-1: Requesting transmission permission
1. If transmitting, the MCVideo client 2 stops the transmission of the video.
2. MCVideo client 2 sends a transmission release message to the MCVideo group.
NOTE: The transmission arbitrator does not respond to a pending (not granted or denied) transmission request if a transmission release notification is received from the MCVideo client.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.2.7 Transmission override
| This subclause is applicable in the single arbitrator in the approach.
Figure 7.7.2.7-1 describes procedures for transmission participants when an MCVideo client authorized to override, requests for transmission permission.
The MCVideo client has detected presence of a transmission arbitrator e.g., by receiving responses to transmission arbitration control message. The MCVideo client sends a transmission request and waits for a response.
Pre-conditions:
1. An off-network group communication has been established.
2. Maximum simultaneous transmissions limit has been reached.
Figure 7.7.2.7-1: Transmission override
1. MCVideo client 2 sends a transmission request message to the MCVideo group.
2. As the configured limit of maximum simultaneous transmissions is already reached, MCVideo client 1, being the transmission arbitrator, checks the override policy.
3. If MCVideo client 2 is authorized to override (based on e.g., transmission priority), MCVideo client 1 sends a transmission revoked message to the MCVideo group. Transmission revoked message indicates the MCVideo client from which the permission is revoked, as the intended recipient.
4. MCVideo client 3 stops transmission of video and MCVideo user at MCVideo client 3 may be notified that the transmission permission has been revoked.
5. MCVideo client 1 sends a transmission granted message to the MCVideo group. Transmission granted message indicates MCVideo client 2 as the intended recipient.
6. MCVideo user at MCVideo client 2 may be notified that the video can now be transmitted.
7. MCVideo client 2 transmits video to the MCVideo group.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.2.8 Transmission override (revoke self)
| This subclause is applicable in the single arbitrator approach.
NOTE: Transmission override in the self arbitration approach is implementation specific.
Figure 7.7.2.8-1 describes procedures for transmission participants when an MCVideo client authorized to override, requests for transmission permission.
The MCVideo client has detected presence of a transmission arbitrator e.g., by receiving responses to transmission arbitration control message. The MCVideo client sends a transmission request and waits for a response.
Pre-conditions:
1. An off-network group communication has been established.
2. Maximum simultaneous transmissions limit has been reached.
Figure 7.7.2.8-1: Transmission override
1. MCVideo client 2 sends a transmission request message to the MCVideo group.
2. As the configured limit of maximum simultaneous transmissions is already reached, MCVideo client 1, being a transmission arbitrator, checks the override policy.
3. If MCVideo client 2 is authorized to override (based on e.g., transmission priority), MCVideo client 1 may send a transmission revoked message to the MCVideo group. Transmission revoked message indicates the MCVideo client 1, the current arbitrator, whose permission is revoked.
4. MCVideo client 1 stops transmission of video and MCVideo user at MCVideo client 1 may be notified that the transmission permission has been revoked.
5. MCVideo client 1 sends a transmission granted message to the MCVideo group. The transmission granted message indicates MCVideo client 2 as the intended recipient and MCVideo client 2 as the subsequent transmission arbitrator.
6a. MCVideo client 2 sends a transmission arbitration taken message to the MCVideo group.
6b. MCVideo user at MCVideo client 2 may be notified that the video can now be transmitted.
NOTE: Step 6a and step 6b can occur in any order.
7. MCVideo client 1, upon receiving the transmission arbitration taken message releases transmission arbitration.
8. MCVideo client 2 transmits video to the MCVideo group.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.2.9 Transmission arbitration release
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.2.9.1 Transmission arbitration release
| This subclause is applicable only in single arbitrator approach.
Figure 7.7.2.9.1-1 describes procedures for an MCVideo client to release transmission arbitration. There is no other MCVideo client to which transmission arbitration can be delegated.
Pre-conditions:
1. An off-network group communication has been established.
2. Only MCVideo client 1 is transmitting a video.
Figure 7.7.2.9.1-1: Transmission arbitration release without delegation
1. MCVideo client 1 sends a transmission release message to the MCVideo group.
2. MCVideo client 1 stops transmission of the video.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.2.9.2 Transmission arbitration release with delegation
| This subclause is applicable only in single arbitrator approach.
Figure 7.7.2.9.2-1 describes procedures for an MCVideo client to release transmission arbitration. There are other MCVideo clients currently transmitting to which transmission arbitration can be delegated.
Pre-conditions:
1. An off-network group communication has been established.
2. At least one more MCVideo client is transmitting video other than the current transmission arbitrator.
Figure 7.7.2.9.2-1: Transmission arbitration release with delegation
1. MCVideo client 1 stops video transmission but does not release transmission arbitration.
2. MCVideo client 1 sends a transmission arbitration release message. The transmission arbitration release message indicates a MCVideo client which is currently transmitting video, MCVideo client 2, as the subsequent transmission arbitrator. The MCVideo client 1 waits for a confirmation before releasing transmission arbitration.
3. MCVideo client 1 detects no response from MCVideo client 2.
4. MCVideo client 1 sends another transmission arbitration release message. The transmission arbitration release message indicates another MCVideo client which is currently transmitting video, MCVideo client 3, as the subsequent transmission arbitrator. The MCVideo client 1 waits for a confirmation before releasing transmission arbitration.
5. MCVideo client 3 sends a transmission arbitration taken message to the MCVideo group.
6. MCVideo client 1, upon receiving the transmission arbitration taken message releases transmission arbitration.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.2.10 Simultaneous transmission requests
| This subclause is applicable in both the single arbitrator and self arbitration approaches.
Figure 7.7.2.10-1 describes procedures for transmission participants when simultaneous transmission requests are generated when more than one MCVideo client initializes transmission control.
Figure 7.7.2.10-1 shows the expected behaviour if simultaneous transmission requests are generated in the following scenarios:
- a single arbitrator approach is used but there is currently no arbitrator; or
- self arbitration is used.
Pre-conditions:
1. An off-network group communication has been established.
2. MCVideo client 1 has higher transmission priority than MCVideo client 2.
Figure 7.7.2.10-1: Simultaneous transmission requests
1a. The MCVideo client 1 sends the transmission request message to the MCVideo group.
1b. The MCVideo client 2 sends the transmission request message to the MCVideo group.
NOTE: Step 1a and 1b happen in parallel
2. On receiving a transmission request message, while waiting for a response to the sent transmission request message, the MCVideo client compares its transmission priority with the transmission priority indicated in the received transmission request message.
3. On determining that it has higher transmission priority than the received transmission request message(s), and no response to the sent transmission request message is received, the MCVideo client 1 sends the transmission arbitration taken message to the MCVideo group.
4. MCVideo user may be notified that the video can now be transmitted.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.8 MCVideo service configuration
| The MCVideo service shall support the procedures and related information flows as specified in subclause 10.1 of 3GPP TS 23.280 [6] with the following clarifications:
- The MC service client is the MCVideo client;
- The MC service server is the MCVideo server;
- The MC service ID is the MCVideo ID; and
- The MC service user profile index is the MCVideo user profile index.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.9 Affiliation and de-affiliation to/from MCVideo group(s)
| The MCVideo service shall support the procedures and related information flows as specified in subclause 10.8 of 3GPP TS 23.280 [6] with the following clarifications:
- The MC service client is the MCVideo client;
- The MC service server is the MCVideo server;
- The MC service group is the MCVideo group;
- The MC service ID is the MCVideo ID; and
- The MC service group ID is the MCVideo group ID.
When an MCVideo user has affiliated to an MCVideo group then the MCVideo user can send and receive MCVideo related media for that MCVideo group. When an MCVideo user has de‑affiliated from an MCVideo group then the MCVideo user cannot send and receive MCVideo related media to and from that MCVideo group.
7.9a Functional alias management
The MCVideo service shall support the functional alias activation, de-activation, taken over, subscription and notification and functional alias to group binding procedures and related information flows as specified in subclause 10.13 of 3GPP TS 23.280 [6].
- The MC service client is the MCVideo client;
- The MC service server is the MCVideo server;
- The MC service ID is the MCVideo ID.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.10 Use of MBMS transmission (on-network)
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.10.1 Information flows for MBMS Transmission
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.10.1.1 General
| Information flows for generic MBMS procedures are defined in 3GPP TS 23.280 [6].
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.10.1.2 MapGroupToBearer
| Table 7.10.1.2-1 describes the information flow to associate a MCVideo group call to a MBMS bearer. It is sent from the MCVideo server to the MCVideo client.
Table 7.10.1.2-1: MapGroupToBearer
Information element
Status
Description
MCVideo group ID
M
This element identifies the MCVideo group, in which the call is started.
Media stream identifier (video)
M
This element identifies the media stream of the SDP used for the Video group call (e.g. MBMS subchannel).
Media stream identifier (audio)
O
This element identifies the audio media stream of the SDP used for the Video group call (e.g. MBMS subchannel). This is used if separate codecs are used for video and audio.
TMGI (see NOTE)
O
The MBMS bearer identifier if the media of the MCVideo group call is not sent on the same MBMS bearer as this MapGroupToBearer message.
Call acknowledgement indicator
O
Indication that the MCVideo group call requires acknowledgement from receiving MCVideo clients.
NOTE: TMGI shall be present if this message is sent over a different MBMS bearer than the media of the group call; TMGI may be present if this message is sent over the same MBMS bearer as the media of the group call.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.10.1.3 UnmapGroupFromBearer
| Table 7.10.1.3-1 describes the information flow to disconnect a MCVideo group call from a MBMS bearer. It is sent from the MCVideo server to the MCVideo client.
Table 7.10.1.3-1: UnmapGroupFromBearer
Information element
Status
Description
MCVideo group ID
M
This element identifies the MCVideo group which will no longer use the MBMS bearer.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.10.2 Use of pre-established MBMS bearers
| The MCVideo service shall support the procedure for using pre-established MBMS bearers as specified 3GPP TS 23.280 [6] with the following clarifications:
- The MC service client is the MCVideo client;
- The MC service server is the MCVideo server; and
- The MC service ID is the MCVideo ID.
The MCVideo service shall use the MCVideo-1, MCVideo‑8 and MCVideo-9 reference points for this procedure.
MCVideo may use pre-established MBMS bearer for the different types of MCVideo group calls. Both pre-arranged group calls and chat group calls can use the pre-established MBMS bearer for distributing the media. The MBMS bearer can be used by any group. Depending on the capacity of the MBMS bearer, the bearer can be used to broadcast one or more group calls in parallel.
Both the media packets as well as the transmission control messages to the receiving MCVideo clients are sent on the MBMS bearer. Optionally a separate MBMS bearer could be used for the transmission control messages, due to different bearer characteristic requirements.
When using the pre-established MBMS bearer for MCVideo, the MCVideo server perform the procedure of call connect and disconnect over MBMS as defined in subclause 7.10.4 at the group communication session establishment step.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.10.3 Use of dynamic MBMS bearer establishment
| The MCVideo service shall support the procedure for using dynamic MBMS bearers as specified 3GPP TS 23.280 [6] with the following clarifications:
- The MC service client is the MCVideo client;
- The MC service server is the MCVideo server; and
- The MC service ID is the MCVideo ID.
The MCVideo service shall use the MCVideo-1, MCVideo-4, MCVideo-7, MCVideo-8 and MCVideo-9 reference points for this procedure.
MCVideo may use dynamic MBMS bearer establishment for the different types of MCVideo group calls. Both pre-arranged group calls and chat group calls can use the dynamic MBMS bearer for distributing the media.
Both the media packets as well as the transmission control messages to the receiving MCVideo clients are sent on the MBMS bearer.
When using the procedures for dynamic MBMS bearer establishment for MCVideo, the MCVideo server perform the procedure of mapping group communication to MBMS bearer as defined in subclause 7.10.4 at the group communication session establishment step.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.10.4 Video call connect and disconnect over MBMS
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.10.4.1 General
| MBMS bearer can be used for MCVideo group calls. One MBMS bearer is not permanently associated to one specific group or group call. Before sending media packets of a group call over MBMS bearer, the MCVideo server shall send the association information between group call and the MBMS bearer. The group call setup procedure indicates the media stream or media streams within one MBMS bearer that is used for the specific MCVideo group call. When the group call over the MBMS bearer is finished, this temporary association information of an MCVideo group call to specific resources on a MBMS bearer is undone. The procedure in figure 7.10.4.2.1-1 requires that the group session is setup before the call start. This eliminates the need for the receiving clients to continuously use a unicast bearer. Prior to this the MBMS bearer is activated and announced to the MCVideo clients.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.10.4.2 Procedure
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.10.4.2.1 Call connect over MBMS
| In figure 7.10.4.2.1-1 the MCVideo client 1 is the client that initiate an MCVideo chat group call and also the transmitting client. MCVideo client 1 may, but does not have to be in an MBMS service area. The MCVideo client 2 and MCVideo client 3 represents MCVideo clients receiving the MCVideo call over an MBMS bearer. There may be other receiving clients both over unicast bearers and over this or other MBMS bearer(s), however they are not illustrated in this figure.
The same procedure as for chat group call can also be applied for pre-arranged calls.
Pre-conditions:
- All users participating in the MCVideo group call are already affiliated to the group.
- All participating users have joined the group session.
Figure 7.10.4.2.1-1: Chat group call connect on MBMS bearer
1. Activation and announcement of MBMS bearer availability.
NOTE 1: The procedure does not include the steps for MCVideo client location reporting, or for MBMS capability information exchange.
2. MCVideo client 1 initiate the MCVideo group call by sending an initial transmit media request over a unicast bearer to the MCVideo server (reference point MCVideo-4).
3. The MCVideo server will send a MapGroupToBearer message over a previously activated MBMS bearer to all users that will receive the call over an MBMS bearer. The MapGroupToBearer message includes association information between the group call and MBMS bearer. The MapGroupToBearer message includes MCVideo group ID and information about the media stream identifier or media stream identifiers of the activated MBMS bearer and may include the identifier (i.e. the TMGI) of the MBMS bearer broadcasting the call. The message is sent over reference point MCVideo-9.
NOTE 2: Step 3 can be deferred until step 5 and the MapGroupToBearer message can then be included in the transmission arbitration taken message.
4. The MCVideo server grants the right to transmit for MCVideo client 1 and by that sends a transmit media granted message to the MCVideo client 1. This message is sent over a unicast bearer (reference point MCVideo-4).
5. A media transmission notification message is sent from the MCVideo server to all receiving users. This message includes the MCVideo ID of the transmitting MCVideo client as well as the MCVideo group ID. The message is sent over a MBMS bearer to all users that have previously been setup to receive calls over the MBMS bearer. The message is sent over reference point MCVideo-9.
6. The users of MCVideo clients are informed about the details of video tranmission and the video transmitter.
7. The MCVideo clients may send a receive media request to the MCVideo server, to indicate the reception of media over the MBMS bearer.
8. MCVideo server accepts the media receive request and sends a receive media response message to MCVideo clients over a MBMS bearer by using reference point MCVideo-9.
NOTE 3: The receive media response can also be sent by unicast to the MCVideo clients that request to receive media over the MBMS bearer.
NOTE 4: Step 7 and 8 may be omitted when auto-receive (i.e. forced reception mode) transmission mode is used based on configurations (e.g. for emergency group calls, imminent peril calls etc) as described in Annex A.
9. The media is sent from MCVideo client 1 to the MCVideo server over unicast bearer and from the MCVideo server to the MCVideo client 2 and MCVideo client 3 over MBMS bearer.
NOTE 5: Additional transmission request messages in the same call will not trigger the MapGroupToBearer message to be sent.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.10.4.2.2 Call disconnect over MBMS
| Figure 7.10.4.2.2-1 shows the high level procedure where an UnmapGroupFromBearer message is sent by the MCVideo server to the MCVideo clients to indicate that the MCVideo group call is being dissociated from the MBMS bearer.
Figure 7.10.4.2.2-1: Chat group call disconnect on MBMS bearer
1. An MCVideo group call is ongoing; the media is broadcasted over MBMS bearer to MCVideo client 2 and MCVideo client 3.
2. MCVideo server has determined to disconnect the call over the MBMS bearer for the MCVideo clients
3. An UnmapGroupFromBearer message is sent by the MCVideo server to MCVideo client 2, MCVideo client 3 and possibly to MCVideo client 1 (if in MBMS coverage area) on MBMS bearer(s).
NOTE 1: The UnmapGroupFromBearer message can be sent as part of other messages.
NOTE 2: The UnmapGroupFromBearer message and the MapGroupToBearer message can be combined, to facilitate switching bearers in one signalling step, as necessary.
7.10.5 Switching from MBMS bearer to unicast bearer
The MCVideo service shall support the procedure for switching from MBMS bearer to unicast bearer as specified 3GPP TS 23.280 [6] with the following clarifications:
- The MC service client is the MCVideo client;
- The MC service server is the MCVideo server; and
- The MC service ID is the MCVideo ID.
The MCVideo service shall use the MCVideo-1, MCVideo-4, MCVideo‑7, MCVideo-8 and MCVideo‑9 reference points for this procedure.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.11 Simultaneous session for MCVideo calls (on-network)
| An MCVideo client and MCVideo server may use a simultaneous session as defined in 3GPP TS 23.280 [6] for MCVideo calls. The MCVideo client becomes involved in a simultaneous session for MCVideo calls by inviting, joining or accepting more than one MCVideo call, or affiliating to a group.
NOTE: An MCVideo client affiliating to multiple MCVideo groups with active calls will result in the MCVideo client being invited simultaneously to multiple MCVideo calls.
The MCVideo client can also still handle multiple MCVideo calls in parallel at the same time i.e. using multiple dialogs.
The simultaneous session is established during either an originating on-demand call establishment or during pre-established session establishment or a modification of an already established pre-established session or on-demand call.
It is possible to change the prioritisation while the MCVideo client is engaged in multiple MCVideo calls. The setting of the priority can be made at MCVideo call setup or by performing a modification after the MCVideo call is established. This may result in more than one media bearer.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.12 User authentication and authorization for MCVideo service
| NOTE: Flow 7.12-1 is a high level user authentication and authorization flow. 3GPP TS 33.180 [14] defines the specific user authentication and authorization architecture required by the MCVideo service in order to realize the MCVideo user authentication and authorization requirements as defined in 3GPP TS 22.280 [2].
A procedure for user authentication is illustrated in figure 7.12-1. The user authentication is performed based on the procedure specified in 3GPP TS 23.280 [6].
Figure 7.12-1: MCVideo user authentication and registration, single domain
1. The user authentication is performed as per the general user authentication procedure specified in 3GPP TS 23.280 [6].
2. MCVideo client performs the MCVideo service authorization for the user. Step 2 utilizes the results of step 1.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.13 Support for multiple devices
| An MCVideo user may be authorized to use the MCVideo service from multiple MCVideo UEs as per the procedure in subclause 7.12.
If an MCVideo server receives a service authorization request for an MCVideo user who is previously MCVideo service authorized on another MCVideo UE, then the MCVideo server shall process this service authorization request as described in subclause 7.12. In the MCVideo service authorization response to the MCVideo user, the MCVideo server shall also indicate that the MCVideo user is already MCVideo service authorized from another MCVideo UE.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.14 Location information (on-network)
| The MCVideo system makes use of all of the procedures for location management as specified in 3GPP TS 23.280 [6], utilising the CSC-14 reference point between the location management client and location management server and the CSC‑15 reference point between the MCVideo server and location management server.
- The MC service client is the MCVideo client;
- The MC service server is the MCVideo server;
- The MC service group is the MCVideo group;
- The MC service ID is the MCVideo ID; and
- The MC service group ID is the MCVideo group ID.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.15 MCVideo resource management (on-network)
| Procedures for resource management are defined in subclause 10.11 of 3GPP TS 23.280 [6].
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.16 MCVideo client query
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.16.1 General
| The MCVideo client query is used by an authorized MCVideo client to retrieve the characteristics of the MCVideo clients in an area with certain criteria. The query criteria may be a set of capabilities, or category tags, or a mix of such criterions, etc.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.16.2 Information flows for MCVideo client query
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.16.2.1 MCVideo client query request
| Table 7.16.2.1-1 describes the information flow for the MCVideo client query request from MCVideo client to MCVideo sever.
Table 7.16.2.1-1: MCVideo client query request
Information Element
Status
Description
MCVideo ID
M
The identity of the MCVideo user requesting MCVideo client query
Location information
M
The location information where the query to be applied
Query criteria
O
A criteria filter for the query (e.g. category tags, video capabilities, etc.)
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.16.2.2 MCVideo client query response
| Table 7.16.2.2-1 describes the information flow for the MCVideo client query response from the MCVideo server to the MCVideo client.
Table 7.16.2.2-1: MCVideo client query response
Information Element
Status
Description
MCVideo ID list
O
The MCVideo clients that fulfil the query criteria
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.16.3 MCVideo client query procedure
| Figure 7.16.3-1 describes the procedure for MCVideo client query in on-network. This procedure is applicable to query the MCVideo clients belonging to the same MCVideo system as the requesting MCVideo user.
Pre-conditions:
1. The video capabilities have been collected at MCVideo server during the update MCVideo capabilities information at the MCVideo server procedure in subclause 7.5.2.3.
Figure 7.16.3-1: MCVideo client query procedure
1. MCVideo client A sends a MCVideo client query request to the MCVideo server with certain search criteria.
2. MCVideo server checks whether the MCVideo user of MCVideo client A has the authorization to perform MCVideo client query. If success, MCVideo server retrieves the MCVideo clients that fulfils the search criteria. If MCVideo group ID list is included in the MCVideo client query request, MCVideo server retrieves the affiliated group members that fulfil the query criteria in each affiliated MCVideo group in the received MCVideo group ID list.
3. MCVideo server returns the MCVideo client query response to the MCVideo client A with the retrieved MCVideo clients.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.17 MCVideo adaptation during MCVideo communication
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.17.1 General
| The MCVideo adaption is used by an authorized MCVideo client to automatically change the video communication parameters including codec, resolution etc. according to the network conditions changes detected through such as packet loss or packet delay.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.17.2 Information flows for MCVideo adaptation
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.17.2.1 MCVideo communication parameter update request
| Table 7.17.2.1-1 describes the information flow for the MCVideo communication parameter update request from MCVideo client to MCVideo sever and from MCVideo server to MCVideo client.
Table 7.17.2.1-1: MCVideo communication parameter update request
Information Element
Status
Description
MCVideo ID
M
The identity of the MCVideo user requesting to update MCVideo communication parameter
MCVideo group ID
O (see NOTE)
The identity of the MCVideo group which the MCVideo communication parameter to be updated (Only used in group communication)
MCVideo ID
O (see NOTE)
The identity of the MCVideo user ID which the MCVideo communication parameter to be updated (Only used in private communication)
SDP
M
The new SDP including codec, resolution, frame rate and etc. for MCVideo communication
NOTE: At least one of these information elements shall be present
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.17.2.2 MCVideo communication parameter update response
| Table 7.17.2.2-1 describes the information flow for the MCVideo communication parameter update response from the MCVideo server to the MCVideo client and from MCVideo client to MCVideo server.
Table 7.17.2.2-1: MCVideo communication parameter update response
Information Element
Status
Description
Result
M
Indicates success or failure
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.17.3 MCVideo adaptation procedure
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.17.3.1 MCVideo adaptation during group communication procedure – transmitting client triggered
| Figure 7.17.3.1-1 describes the procedure for transmitting MCVideo client triggered MCVideo communication parameters update in on-network. For simplicity, only one receiving user is shown in the figure. This procedure is applicable to only one MCVideo transmitting user during the MCVideo group call, e.g., broadcast group call.
NOTE: The MCVideo adaptation for MCVideo group communication allows multiple transmitting users are not specified in this release.
Pre-conditions:
1. MCVideo client 1 and MCVideo client 2 are the group communication participants, and the MCVideo client 1 is transmitting video in the MCVideo group communication.
Figure 7.17.3.1-1: Transmitting user triggered MCVideo adaptation in group communication
1. MCVideo client 1 sends MCVideo communication parameter update request to the MCVideo server to adjust the video communication parameters due to network conditions changes detected, e.g., through packet loss or packet delay. The new parameters including codec, resolution, frame rate and etc. are included.
2. MCVideo server checks whether the MCVideo user of MCVideo client 1 has the authorization to update the MCVideo communication parameters.
3. When authorized, MCVideo server sends the MCVideo communication parameter update request to the MCVideo client 2.
4. The MCVideo user of MCVideo client 2 is notified about the changes of MCVideo communication parameters.
5. The MCVideo client 2 accepts the request, and sends the MCVideo communication parameter update response to the MCVideo server.
6. The MCVideo server sends the MCVideo communication parameter update response to the MCVideo client 1 with the result.
7. Then, the MCVideo group communication applies the new MCVideo communication parameters.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.17.3.2 MCVideo adaptation during group communication procedure – receiving user triggered
| Figure 7.17.3.2-1 describes the procedure for MCVideo server initiated MCVideo communication parameters update in on-network. For simplicity, only one receiving user is shown in the figure. This procedure is applicable to only one MCVideo transmitting user during the MCVideo group call e.g., broadcast group call.
Pre-conditions:
1. MCVideo cient 1 and MCVideo client 2 are the group communication participants. MCVideo client 2 is transmitting video, and MCVideo client 1 is receiving video.
Figure 7.17.3.2-1: Receiving user triggered MCVideo adaptation in group communication
1. MCVideo client 1 sends MCVideo communication parameter update request to the MCVideo server to request the video communication parameters due to network conditions changes detected, e.g., through packet loss. The expected parameters including codec, resolution, frame rate and etc. are included.
2. MCVideo server may receive a multitude of notifications from the receiving users. The MCVideo server performs authorization check and determines to update the MCVideo communication parameters according to the received notifications.
NOTE 1: The determination of update the MCVIdeo communication parameters is implementation.
3. When authorized, MCVideo server sends the MCVideo communication parameter update request to the MCVideo client 2.
4. The MCVideo users of MCVideo client 1 and MCVideo client are notified about the changes of MCVideo communication parameters.
5. The MCVideo client 1 and MCVideo client 2 accepts the request, and sends the MCVideo communication parameter update response to the MCVideo server.
6. Then, the MCVideo group communication applies the new MCVideo communication parameters.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.17.3.3 MCVideo adaptation during private communication procedure – transmitting client triggered
| Figure 7.17.3.3-1 describes the procedure for transmitting MCVideo client initiated MCVideo communication parameters update in on-network. This procedure is applicable to the video push and video pull.
Pre-conditions:
1. The private communication is ongoing between MCVideo cient 1 and MCVideo client 2, and MCVideo client 1 is transmitting video to MCVideo client 2.
Figure 7.17.3.3-1: Transmitting user initiated MCVideo adaptation in private communication
1. MCVideo client 1 sends MCVideo communication parameter update request to the MCVideo server to adjust the video communication parameters due to network conditions changes detected, e.g., through packet loss. The new parameters including codec, resolution, frame rate and etc. are included.
2. MCVideo server checks whether the MCVideo user of MCVideo client 1 has the authorization to update the MCVideo communication parameters.
3. When authorized, MCVideo server sends the MCVideo communication parameter update request to the MCVideo client 2.
4. The MCVideo user of MCVideo client 2 is notified about the changes of MCVideo communication parameters.
5. The MCVideo client 2 accepts the request, and sends the MCVideo communication parameter update response to the MCVideo server.
6. The MCVideo server sends the MCVideo communication parameter update response to the MCVideo client 1 with the result.
7. Then, the MCVideo communication applies the new MCVideo communication parameters.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.17.3.4 MCVideo adaptation during group communication procedure – receiving user triggered
| Figure 7.17.3.4-1 describes the procedure for receiving user initiated MCVideo communication parameters update in on-network. This procedure is applicable in video push and video pull.
Pre-conditions:
1. The private communication is ongoing between MCVideo cient 1 and MCVideo client 2, and the MCVideo client 1 is receiving video from MCVideo client 2.
Figure 7.17.3.4-1: Receiving user triggered MCVideo adaptation in private communication
1. MCVideo client 1 sends MCVideo communication parameter update request to the MCVideo server to request the video communication parameters due to network conditions changes detected, e.g., through packet loss. The expected parameters including codec, resolution, frame rate and etc. are included.
2. MCVideo server checks whether the MCVideo user of MCVideo client 1 has the authorization to update the MCVideo communication parameters.
3. When authorized, MCVideo server sends the MCVideo communication parameter update request to the MCVideo client 2.
4. The MCVideo user of MCVideo client 2 is notified about the request of MCVideo communication parameters update.
5. The MCVideo client 2 accepts the request, and sends the MCVideo communication parameter update response to the MCVideo server.
6. The MCVideo server sends the MCVideo communication parameter update response to the MCVideo client 1 with the result.
7. Then, the MCVideo communication applies the new MCVideo communication parameters.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.18 Use of ProSe capabilities in off-network MCVideo communications
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.18.1 General
| When an MCVideo user using a ProSe-enabled UE wants to communicate with a specific MCVideo group or MCVideo user using ProSe capabilities, the MCVideo client enables the use of the ProSe layer procedures for public safety, as specified in 3GPP TS 23.303 [7].
For an off-network MCVideo group communication, the MCVideo client obtains configuration data such as the user info ID of the calling MCVideo user and the ProSe Group IP multicast address and ProSe Layer-2 Group ID associated to the target MCVideo group (as described in clause 8.1.3.2 in 3GPP TS 23.280 [6]), and provides it to the ProSe layer. The ProSe Layer-2 Group ID of the target MCVideo 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 MCVideo group communication, a group member discovery procedure may be initiated to identify whether other members of the target MCVideo group are in the proximity of the calling MCVideo user, as described in the ProSe direct discovery for public safety use procedure in 3GPP TS 23.303 [7]. The off-network MCVideo 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 MCVideo communication, the MCVideo client obtains configuration data such as the ProSe discovery group ID and user info ID of the target MCVideo user from the "List of user(s) who can be called in MCVideo private call" in the MCVideo user profile and requests the IP address of the MCVideo UE associated with the target MCVideo user from the ProSe layer.
The MCVideo client enables the ProSe layer to determine the IP address for the communication with the target MCVideo UE by providing the ProSe discovery group ID and user info ID (as defined in 3GPP TS 23.303 [7]) associated to the target MCVideo user. This may trigger the ProSe direct discovery for public safety use procedure to identify whether the target MCVideo user is in the proximity of the calling MCVideo user. The user info ID of the target MCVideo 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 MCVideo user to the MCVideo client to initiate the off-network one-to-one MCVideo communication based on the one-to-one ProSe direct communication procedure described in 3GPP TS 23.303 [7].
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.18.2 Procedures
| The off-network MCVideo communication procedures using the ProSe capabilities are described within the corresponding clauses of each MCVideo capability, e.g. group communication procedures for off-network are described in clause 7.1.3 and private communication procedures for off-network are described in clause 7.2.3.
7.19 Ad hoc group call
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.19.1 General
| This subclause contains procedures for ad hoc group call across one or more MCVideo systems, and associated functions such as emergency call, Imminent peril call, broadcast call and others.
The ad hoc group calls can use the participants list provided by either an initiator of the call or MCVideo server. The MCVideo server can use the criteria provided by the initiator of the call 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 MCVideo 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 [6].
The preconfigured MCVideo group that provides the configuration is not used for the MCVideo group communication, it only provides configuration for one or more adhoc group calls. The MCVideo group ID of the ad hoc group call is provided by the MCVideo server when the ad hoc group call is originated. In order to establish security context for the end-to-end secured ad hoc group call, the security related information is used from this preconfigured group.
NOTE 2: The configurations defined for the adhoc group call in user profile and service configuration document as described in the Annex A.3 and A.5 is applicable only for single MCVideo system.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.19.2 Information flows
| 7.19.2.1 Ad hoc group call request (MCVideo client – MCVideo server)
Table 7.19.2.1-1 describes the information flow ad hoc group call request from the MCVideo client to the MCVideo server.
Table 7.19.2.1-1 Ad hoc group call request information elements
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
Functional alias
O
The functional alias of the calling party
MCVideo ad hoc group ID (see NOTE 1)
O
The MCVideo group ID to be associated with the ad hoc group communication
Encryption supported (see NOTE 2)
O
Indicates whether this ad hoc group call supports end-to-end encryption
MCVideo ID list (see NOTE 3, NOTE 6, NOTE 7)
O
MCVideo IDs of the participants being invited for the ad hoc group call
SDP offer
M
Media parameters of MCVideo clients
Implicit transmit media request (see NOTE 4)
O
When originating client requests the transmission of media, this element shall be included
Broadcast indicator
(see NOTE 5)
O
Indicates that the group call request is for a broadcast group call
Imminent peril indicator (see NOTE 5)
O
Indicates that the ad hoc group call request is an MCVideo imminent peril call
Emergency Indicator (see NOTE 5)
O
Indicates that the ad hoc group call request is an MCVideo emergency call
MCVideo ID list (see NOTE 3)
O
List of participants required to acknowledge the ad hoc group call before start of the audio transmission
Location information
O
Location of the calling party.
Criteria for determining the participants (see NOTE 6, NOTE 7)
O
Carries the details of criteria or meaningful label identifying the criteria or the combination of both which will be used by the MCVideo server for determining the participants e.g., it can be a location based criteria to invite particpants in a particular area
Requested priority
O
Application priority level requested for this group call
NOTE 1: If this information element is not included, the MCVideo server assigns an MCVideo ad hoc group ID to be used for the ad hoc group communication. This information element is returned to the calling party to use in the ad hoc group 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 call is encrypted. When the ad hoc group call 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 call is unencrypted.
NOTE 3: This element is included only when the originating client sends the list of participants.
NOTE 4: This element is included only when the originating client requests the transmission of media.
NOTE 5: If used, only one of these information elements is present.
NOTE 6: Only one of these information elements is present.
NOTE 7: If the request follows an ad hoc group for emergency alert, then this element is not present.
7.19.2.2 Ad hoc group call request return (MCVideo server – MCVideo client)
Table 7.19.2.2-1 describes the information flow ad hoc group call request return from the MCVideo server to the MCVideo client. This response could be intermediate response to provide the server assigned MCVideo ad hoc group ID.
Table 7.19.2.2-1: Ad hoc group call request return information elements
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
MCVideo ad hoc group ID (NOTE)
O
The MCVideo group ID to be associated with the ad hoc group call which is either provided by the group call initiator or assigned by the MCVideo server. This information element shall be present if the authorization result is success.
Pre-configured group ID (NOTE)
O
The preconfigured MCVideo group ID whose group configuration is to be used for the ad hoc group call (e.g. information for end-to-end security).
Authorization result
M
Indicate if authorization is success or failure
NOTE: These IEs are included only when the Authorization Result IE indicates authorization is successful.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.19.2.3 Void
| 7.19.2.4 Ad hoc group call request (MCVideo server – MCVideo client)
Table 7.19.2.4-1 describes the information flow ad hoc group call request from the MCVideo server to the MCVideo client.
Table 7.19.2.4-1: Ad hoc group call request information elements
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
MCVideo ID
M
The identity of the MCVideo user towards which the request is sent
Functional alias
O
The functional alias of the calling party
MCVideo ad hoc group ID
M
The MCVideo group ID to be associated with the ad hoc group call
SDP offer
M
Media parameters of MCVideo server
Broadcast indicator
(NOTE)
O
Indicates that the ad hoc group call request is for a broadcast ad hoc group call
Imminent peril indicator (NOTE)
O
Indicates that the ad hoc group call request is an MCVideo imminent peril call
Emergency Indicator (NOTE)
O
Indicates that the ad hoc group call request is an MCVideo emergency call
Preconfigured ad hoc group identity
O
Group identity whose configuration is to be applied for this ad hoc group call.
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 MCVideo server used for determining the participants e.g., it can be a location based criteria to invite participants in a particular area.
NOTE: If used, only one of these information elements is present.
7.19.2.5 Ad hoc group call response (MCVideo server – MCVideo client)
Table 7.19.2.5-1 describes the information flow ad hoc group call response from the MCVideo server to the MCVideo client.
Table 7.19.2.5-1: Ad hoc group call response information elements
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
Functional alias
O
The functional alias of the calling party
MCVideo group ID
M
The MCVideo group ID to be associated with the ad hoc group call
SDP answer
O
Media parameters selected and present if the Result is success.
Result
M
Result of the group call request (success or failure)
Call resulting criteria for determining the participants (NOTE)
O
Call resulting criteria used by the MCPTT server to determine the list of participants to be invited.
NOTE: This information element shall be included only when the Result is success.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.19.2.6 Void
| 7.19.2.7 Ad hoc group call response (MCVideo client – MCVideo server)
Table 7.19.2.7-1 describes the information flow ad hoc group call response from the MCVideo client to the MCVideo server.
Table 7.19.2.7-1: Ad hoc group call response information elements
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the target MCVideo user
Functional alias
O
The functional alias of the target MCVideo user
MCVideo ad hoc group ID
M
The MCVideo group ID to be associated with the ad hoc group call
SDP answer
O
Media parameters selected and present if the Result is success.
Result
M
Result of the ad hoc group call request (success or failure)
7.19.2.8 Ad hoc group call release request (MCVideo server – MCVideo client)
Table 7.19.2.8-1 describes the information flow ad hoc group call release request from the MCVideo server to the MCVideo client.
Table 7.19.2.8-1: Ad hoc group call release request information elements
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the ad hoc group call participant
Functional alias
O
The functional alias of the ad hoc group call participant
MCVideo ad hoc group ID
M
The MCVideo group ID of the ad hoc group call on which call is released
7.19.2.8a Ad hoc group call release request (MCVideo client – MCVideo server)
Table 7.19.2.8a-1 describes the information flow ad hoc group call release request from the MCVideo client to the MCVideo server.
Table 7.19.2.8a-1: Ad hoc group call release request information elements
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the user authorized to release the ad hoc group call
Functional alias
O
The functional alias of the authorized user requesting to release the ad hoc group call
MCVideo ad hoc group ID
M
The MCVideo group ID of the ad hoc group call on which call is released
7.19.2.9 Ad hoc group call release response (MCVideo client – MCVideo server)
Table 7.19.2.9-1 describes the information flow ad hoc group call release response from the MCVideo client to the MCVideo server.
Table 7.19.2.9-1: Ad hoc group call release response information elements
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the ad hoc group call participant
Functional alias
O
The functional alias of the ad hoc group call participant
MCVideo group ID
M
The MCVideo group ID of the ad hoc group call on which call is released
7.19.2.9a Ad hoc group call release response (MCVideo server – MCVideo client)
Table 7.19.2.9a-1 describes the information flow ad hoc group call release response from the MCVideo server to the MCVideo client.
Table 7.19.2.9a-1: Ad hoc group call release response information elements
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the user authorized to release the ad hoc group call
Functional alias
O
The functional alias of the authorized user requesting to release the ad hoc group call
MCVideo group ID
M
The MCVideo group ID of the ad hoc group call on which call is released
7.19.2.10 Ad hoc group call notify (MCVideo server – MCVideo client)
Table 7.19.2.10-1 describes the information flow ad hoc group call notify from MCVideo server to MCVideo client.
Table 7.19.2.10-1: Ad hoc group call notify
Information element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party or the MCVideo ID of the authorized users who are configured to receive this notification.
Functional alias
O
The functional alias of the calling party
MCVideo ad hoc group ID
M
The MCVideo group ID associated with the ad hoc group call
MCVideo ID list
O
The list of the invited MCVideo users who did not acknowledge the ad hoc group call request within a configured time or the list of the invited MCVideo users who acknowledged the ad hoc group call request and joined or the list of the MCVideo users who joined or left the ongoing MCVideo ad hoc group call.
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 MCVideo server used for determining the participants e.g., it can be a location based criteria to invite participants in a particular area.
7.19.2.11 Modify ad hoc group call participants request (MCVideo client – MCVideo server)
Table 7.19.2.11-1 describes the information flow Modify ad hoc group call participants request from the MCVideo client to the MCVideo server.
Table 7.19.2.11-1: Modify ad hoc group call participants request
Information element
Status
Description
MCVideo ID
M
The MCVideo ID of the requesting MCVideo user who is authorized to modify the ad hoc group call participants
Functional alias
O
The functional alias of the requesting MCVideo user who is authorized to modify the ad hoc group call participants
MCVideo ad hoc group ID
M
The MCVideo group ID of ad hoc group call whose participants needs to be modified
MCVideo ID list (see NOTE)
O
List of additional MCVideo users to be added to the on-going ad hoc group call
MCVideo ID list (see NOTE)
O
List of MCVideo users to be removed from the on-going ad hoc group call
NOTE: Either one or both of these information elements is present
7.19.2.12 Modify ad hoc group call participants response (MCVideo server – MCVideo client)
Table 7.19.2.12-1 describes the information flow Modify ad hoc group call participants response from the MCVideo server to the MCVideo client.
Table 7.19.2.12-1: Modify Ad hoc group call participants response information elements
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the requesting MCVideo user who is authorized to modify the ad hoc group call participants
Functional alias
O
The functional alias of the requesting MCVideo user who is authorized to modify the ad hoc group call participants
MCVideo ad hoc group ID
M
The MCVideo group ID of ad hoc group call whose participants needs to be modified
Result
M
Result of the modify ad hoc group call participants request (success or failure)
MCVideo ID list
O
List of MCVideo users who are not allowed to be added to the on-going ad hoc group call. This list is provided if the operation is partially success.
7.19.2.13 Ad hoc group call leave request (MCVideo server – MCVideo client)
Table 7.19.2.13-1 describes the information flow ad hoc group call leave request from the MCVideo server to the MCVideo client.
Table 7.19.2.13-1: Ad hoc group call leave request information elements
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the ad hoc group call participant leaving the call
MCVideo ad hoc group ID
M
The MCVideo group ID of ad hoc group call on which call is on-going
Reason to leave
O
Carries the reason of why the MCVideo client is being asked to leave the ongoing ad hoc group call
7.19.2.13a Ad hoc group call leave request (MCVideo client – MCVideo server)
Table 7.19.2.13a-1 describes the information flow ad hoc group call leave request from the MCVideo client to the MCVideo server.
Table 7.19.2.13a-1: Ad hoc group call leave request information elements
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the ad hoc group call participant leaving the call
MCVideo ad hoc group ID
M
The MCVideo group ID of ad hoc group call on which call is on-going
Reason to leave
M
Carries the reason of why the MCVideo client is leaving ongoing ad hoc group call (e.g. Due to migration).
7.19.2.14 Ad hoc group call leave response (MCVideo client – MCVideo server)
Table 7.19.2.14-1 describes the information flow Ad hoc group call leave response from the MCVideo client to the MCVideo server.
Table 7.19.2.14-1: Ad hoc group call leave response information elements
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the ad hoc group call participant leaving the call
MCVideo ad hoc group ID
M
The MCVideo group ID of ad hoc group call on which call is on-going
7.19.2.14a Ad hoc group call leave response (MCVideo server – MCVideo client)
Table 7.19.2.14a-1 describes the information flow Ad hoc group call leave response from the MCVideo server to the MCVideo client.
Table 7.19.2.14a-1: Ad hoc group call leave response information elements
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the ad hoc group call participant leaving the call
MCVideo ad hoc group ID
M
The MCVideo group ID of ad hoc group call on which call is on-going
Result
M
Result of the ad hoc group call leave request – success or failure.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.19.2.15 Ad hoc group call add user notification (MCVideo server – MCVideo server)
| Table 7.19.2.15 -1 describes the information flow Ad hoc group call add user notification from one MCVideo server to another MCVideo server. This notification is to provide the list of MCVideo IDs meeting the criteria specified in the ad hoc group communication get userlist request from one MCVideo server to another MCVideo server.
Table 7.19.2.15-1: Ad hoc group call add user notification information elements
Information Element
Status
Description
MCVideo ad hoc group ID
M
The MCVideo group ID associated with the ad hoc group communication
MCVideo ID list
M
List of MCVideo IDs meeting the criteria specified in the ad hoc group communication get userlist
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.19.2.16 Ad hoc group call remove user notification (MCVideo server – MCVideo server)
| Table 7.19.2.16 -1 describes the information flow Ad hoc group call remove user notification from one MCVideo server to another MCVideo server. This notification is to provide the list of MCVideo IDs no longer meeting the criteria specified in the ad hoc group communication get userlist request from one MCVideo server to another MCVideo server.
Table 7.19.2.16-1: Ad hoc group call remove user notification information elements
Information Element
Status
Description
MCVideo ad hoc group ID
M
The MCVideo group ID associated with the ad hoc group communication
MCVideo ID list
M
List of MCVideo IDs no longer meeting the criteria specified in the ad hoc group communication get userlist
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.19.2.17 Ad hoc group call release notification (MCVideo server – MCVideo server)
| Table 7.19.2.17 -1 describes the information flow Ad hoc group call release notification from one MCVideo server to another MCVideo server. This notification is to indicate to stop evaluating the criteria to determine the participants list if another MCVideo server is having the criteria specified in the ad hoc group communication get userlist request.
Table 7.19.2.17-1: Ad hoc group call release notification information elements
Information Element
Status
Description
MCVideo ad hoc group ID
M
The MCVideo group ID associated with the ad hoc group communication
7.19.2.18 Ad hoc group call get userlist (MCVideo server – MCVideo server)
Table 7.19.2.18-1 describes the information flow ad hoc group call get userlist between MCVideo servers.
Table 7.19.2.18-1: Ad hoc group call get userlist
Information element
Status
Description
MCVideo ad hoc group ID
M
The associated MCVideo group ID of the ad hoc group call
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 MCVideo server for determining the participants e.g., it can be a location based criteria to invite participants in a particular area
7.19.2.19 Ad hoc group call get userlist response (MCVideo server – MCVideo server)
Table 7.19.2.19-1 describes the information flow ad hoc group call get userlist response between MCVideo servers.
Table 7.19.2.19-1: Ad hoc group call get userlist response
Information element
Status
Description
MCVideo ad hoc group ID
M
The associated MCVideo group ID of the ad hoc group call
MCVideo ID list
M
List of MCVideo IDs meeting the criteria specified in the ad hoc group call get userlist
7.19.2.20 Modify ad hoc group call criteria request (MCVideo client – MCVideo server)
Table 7.19.2.20-1 describes the information flow Modify ad hoc group call criteria request from the MCVideo client to the MCVideo server.
Table 7.19.2.20-1: Modify ad hoc group call criteria request
Information element
Status
Description
MCVideo ID
M
The MCVideo ID of the requesting MCVideo user who is authorized to modify the ad hoc group criteria
Functional alias
O
The functional alias of the requesting MCVideo user who is authorized to modify the ad hoc group criteria
MCVideo ad hoc group ID
M
The MCVideo group ID of ad hoc group call 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 MCVideo server for determining the participants e.g., it can be location-based criteria to invite participants in a particular area
7.19.2.20a Modify ad hoc group call criteria request (MCVideo server – MCVideo server)
Table 7.19.2.20a-1 describes the information flow Modify ad hoc group call criteria request from the MCVideo server to the MCVideo server.
Table 7.19.2.20a-1: Modify ad hoc group call criteria request
Information element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
Functional alias
O
The functional alias of the calling party
MCVideo ad hoc group ID
M
The MCVideo group ID of ad hoc group call 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 MCVideo server for determining the participants e.g., it can be location-based criteria to invite participants in a particular area
7.19.2.21 Modify ad hoc group call criteria response (MCVideo server – MCVideo client)
Table 7.19.2.21-1 describes the information flow Modify ad hoc group call criteria response from the MCVideo server to the MCVideo client.
Table 7.19.2.21-1: Modify Ad hoc group call criteria response information elements
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the requesting MCVideo user who is authorized to modify the ad hoc group criteria
Functional alias
O
The functional alias of the requesting MCVideo user who is authorized to modify the ad hoc group criteria
MCVideo ad hoc group ID
M
The MCVideo group ID of ad hoc group call whose participants list needs to be modified
Result
M
Result of the modify ad hoc group call participants request (success or failure)
Call resulting criteria for determining the participants (NOTE)
O
Call resulting criteria used by the MCPTT server to determine the list of participants to be invited.
NOTE: This information element shall be included only when the Result is success.
7.19.2.21a Modify ad hoc group call criteria response (MCVideo server – MCVideo server)
Table 7.19.2.21a-1 describes the information flow Modify ad hoc group call criteria response from the MCVideo server to the MCVideo server.
Table 7.19.2.21a-1: Modify Ad hoc group call criteria response information elements
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
Functional alias
O
The functional alias of the calling party
MCVideo ad hoc group ID
M
The MCVideo group ID of ad hoc group call whose participants list needs to be modified
Result
M
Result of the modify ad hoc group call participants request (success or failure)
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.19.3 Procedures
| 7.19.3.1 Ad hoc group call procedures in single MCVideo system
7.19.3.1.1 Ad hoc group call setup
Figure 7.19.3.1.1-1 below illustrates the ad hoc group call setup procedure initiated by an authorized user.
Pre-conditions:
1. The authorized user at MCVideo client 1 wants to invite MCVideo users at MCVideo client 2, MCVideo client 3 and MCVideo client 4 for the ad hoc group call and is aware of the MCVideo IDs of the participants or to invite the ad hoc group member if the ad hoc group call follows an ad hoc group emergency alert, the MCVideo client 1 is aware of the ad hoc group ID.
2. Number of participants being invited for the ad hoc group call is within the limit.
3. End-to-End encryption is supported for this ad hoc group call.
4. The pre-configured group identity and pre-configured group configuration to be used for an ad hoc group have been preconfigured in MCVideo 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.
NOTE 1: Selection of MCVideo 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.
Figure 7.19.3.1.1-1: Ad hoc group call setup
1. User at MCVideo client 1 would like to initiate an ad hoc group call. The MCVideo client 1 initiates the ad hoc group call by sending the ad hoc group call request containing the list of participants or an ad hoc group ID from an ad hoc group emergency alert to the MCVideo server. Encryption supported information element shall be set to true since end-to-end encryption is supported. An SDP offer containing the MCVideo client media parameters is included. If there is a transmit media request to transmit media, then the ad hoc group call request contains an indication of an implicit transmit media request. If the MCVideo user of MCVideo client 1 has selected a functional alias, then the ad hoc group call request contains that functional alias. If the ad hoc group call request contains an implicit transmit media request it may also include location information.
If the MCVideo user at MCVideo client 1 initiates an MCVideo emergency ad hoc group call or the MCVideo emergency state is already set for the MCVideo client 1 (due to a previously triggered MCVideo emergency alert):
i. the MCVideo ad hoc group call request shall contain an emergency indicator;
ii. if the MCVideo emergency state is not set already, MCVideo client 1 sets its MCVideo emergency state. The MCVideo emergency state of MCVideo client 1 is retained until explicitly cancelled by the user of MCVideo client 1.
2. The MCVideo server accepts the ad hoc group call request if the ad hoc group call is supported and authorized. Otherwise reject the ad hoc group call request and do not continue with the rest of the steps. If authorised, it validates whether the number of invited participants is within the configured limit before proceeding with the call setup.
If functional alias is present, the MCVideo 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 call request, the MCVideo server checks the privacy policy of the MCVideo user to decide if the location information of MCVideo client 1 can be provided to other users on the call (refer to Annex A.3 "Authorisation to provide location information to other MCVideo users on a call when talking").
If an emergency indicator is present in the received MCVideo ad hoc group call request, the MCVideo ad hoc group is considered to be in the in-progress emergency state until this ad hoc group call is terminated; and
If an imminent peril indicator is present in the received MCVideo ad hoc group call request, the MCVideo ad hoc group is considered to be in the in-progress imminent peril state until this ad hoc group call is terminated.
If the the MC service users' information received in step 1 does not contain an ad hoc group ID from an ad hoc group emergency alert, the MCVideo server forms the ad hoc group by using MCVideo users' information received in step 1, determines the preconfigured group to be used for the configuration of the ad hoc group and assigns a MCVideo group ID for the newly formed ad hoc group.
The MCVideo server considers the ad hoc group call participants as implicitly affiliated to the ad hoc group.
3. The MCVideo server shall send the ad hoc group call request return message to MCVideo client 1 containing the below:
i. The MCVideo ad hoc group ID either generated by the MCVideo server or provided by the MCVideo client 1 if the ad hoc group ID is from an ad hoc group emergency alert (only included when the ad hoc group call is authorized);
ii. The group ID of the pre-configured group to be used for the ad hoc group call (only included when the ad hoc group call is authorized); and
iii. Result of whether the ad hoc group call is authorized or not.
If the ad hoc group call request is not authorized, MCVideo client 1 shall not proceed with the rest of the steps.
4a-4c. The MCVideo server sends the ad hoc group call requests towards the MCVideo clients of the invited users based on step 1. While sending the ad hoc group call requests, the MCVideo server shall remove the information elements that are not required to be conveyed to the target MCVideo clients (e.g. MCVideo ID list of the users who are required to acknowledge)
5a-5c. The receiving MCVideo clients are notified about the incoming ad hoc group call.
6a-6c. The receiving MCVideo clients accept the ad hoc group call requests and send ad hoc group call responses to the MCVideo server. The response may also contain a functional alias of the responding MCVideo user, which is verified (valid and activated for the user) by the MCVideo server.
7. The MCVideo server sends the ad hoc group call response to MCVideo client 1 through the signalling path to inform about successful call establishment.
NOTE 2: Steps 5 to step 7 can start to occur before all of step 4 is completed since the MCVideo server do not require to wait for the previous ad hoc group call request to complete before sending the ad hoc group request to another participant.
8. If the initiating MCVideo user requires the acknowledgement from the invited MCVideo users, and the required MCVideo users do not acknowledge the call setup within a configured time (the "acknowledged call setup timeout"), then the MCVideo server may proceed with or abandon the call and then notify the initiating MCVideo user that the acknowledgements did not include all required members according to ad hoc group call policy from the user profile configuration. The MCVideo server may notify the initiating MCVideo user of all MCVideo users who did not acknowledge the ad hoc group call request within the configured time. This notification may be sent to the initiating MCVideo user by the MCVideo server more than once during the call when MCVideo users join or leave the MCVideo ad hoc group call.
9. MCVideo client 1, MCVideo client 2, MCVideo client 3 and MCVideo client 4 establish media plane and transmission control resources.
NOTE 2: Step 9 can occur any time following step 7 if the conditions to proceed with the call are met.
7.19.3.1.2 Release ad hoc group call by the MCVideo server
The procedure focuses on the case where the MCVideo server releases an ongoing MCVideo ad hoc group call for all the participants of that ad hoc group call, 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.19.3.1.2-1 below illustrates the signalling control plane procedure for the MCVideo server initiating termination an ongoing ad hoc group call.
Figure 7.19.3.1.2-1: Release ad hoc group call by the MCVideo server
1. It is assumed that MCVideo users on MCVideo client 1, client 2 and client 3 are already part of the ongoing ad hoc group call.
2. MCVideo server would like to release the MCVideo ad hoc group call which is ongoing e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving.
3. MCVideo server identifies the participants of the ongoing ad hoc group call and generates ad hoc group call release request to release ongoing session. The MCVideo server cancels the in-progress emergency state or in-progress imminent peril state of the ad hoc group if the ad hoc group call is an emergency or imminent peril call respectively.
4. MCVideo server sends ad hoc group call release request via SIP core towards each participant of the ongoing ad hoc group call.
5. MCVideo users are notified about the release of the ad hoc group call.
6. MCVideo client(s) receiving ad hoc group call release request, acknowledge towards the MCVideo server by sending an ad hoc group call release response.
NOTE: If the initiator of the ad hoc group call does not supply the participants list, the MCVideo client(s) may choose to store the list of participants for easy re-initiation of another ad hoc group call with the same participants.
7. MCVideo client 1, client 2 and client 3 have successfully released the transmission control and media plane resources associated with the ad hoc group call that is terminated and the ad hoc group ceases to exist (i.e., further call is not possible over the same ad hoc group, otherwise if the ad hoc group call follows an ad hoc group emergency alert the ad hoc group continues to exist (i.e., further calls over the same ad hoc group are possible).
7.19.3.1.2a Release ad hoc group call by an authorized user
The procedure focuses on the case where an authorized user releases an ongoing MCVideo ad hoc group call for all the participants of that ad hoc group call.
Figure 7.19.3.1.2a-1 below illustrates the signalling control plane procedure for the MCVideo client initiating termination of an ongoing ad hoc group call.
Figure 7.19.3.1.2a-1: Release ad hoc group call by an authorized user
1. It is assumed that MCVideo users on MCVideo client 1, client 2 and client 3 are already part of the ongoing ad hoc group call.
2. The authorized MCVideo user on MCVideo client 1 would like to release the MCVideo ad hoc group call which is ongoing and sends an ad hoc group call release request to the MCVideo server.
3. MCVideo server checks whether the MCVideo user on MCVideo client 1 is authorized to release the ad hoc group call and generates ad hoc group call release request to release ongoing session. The MCVideo server cancels the in-progress emergency state or in-progress imminent peril state of the ad hoc group if the ad hoc group call is an emergency or imminent peril call respectively.
4. The MCVideo server sends ad hoc group call release request via SIP core towards MCVideo client 2 and MCVideo client 3.
5. MCVideo users on MCVideo client 2 and MCVideo client 3 are notified about the release of the ad hoc group call.
6. MCVideo client 2 and MCVideo client 3 acknowledge the ad hoc group call release request towards the MCVideo server by sending an ad hoc group call release response.
7. The MCVideo server sends ad hoc group call release response to MCVideo client 1.
8. MCVideo user on MCVideo client 1 is notified about the release of the ad hoc group call.
9. MCVideo client 1, client 2 and client 3 have successfully released the floor control and media plane resources associated with the ad hoc group call that is terminated and the ad hoc group ceases to exist (i.e., further call is not possible over the same ad hoc group, otherwise if the ad hoc group call follows an ad hoc group emergency alert the ad hoc group continues to exist (i.e., further calls over the same ad hoc group are possible).
7.19.3.1.3 Ad hoc group call setup with MCVideo server determining the participants lists
Figure 7.19.3.1.3-1 below illustrates the ad hoc group call setup procedure initiated by the MCVideo user and MCVideo client 1 wherein the list of participants is determined by the MCVideo server based on the criteria received from the MCVideo client.
Pre-conditions:
1. The MCVideo user at MCVideo client 1 is authorized to initiate ad hoc group call.
2. The MCVideo user at MCVideo client 1 wants to invite MCVideo users who are satisfying certain criteria for the ad hoc group call.
Figure 7.19.3.1.3-1: Ad hoc group call participants determined by MCVideo server
1. User at MCVideo client 1 would like to initiate an ad hoc group call in-order to invite the participants satisfying specific criteria. The MCVideo client 1 initiates the ad hoc group call by sending the ad hoc group call request containing the details of the criteria to be applied by the MCVideo 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 MCVideo group whose configuration is to be applied is included. An SDP offer containing the MCVideo client media parameters is included. If there is a transmission request to transmit, then the ad hoc group call request contains an indication of an implicit transmit media request. If the MCVideo user of MCVideo client 1 has selected a functional alias, then the ad hoc group call request contains that functional alias. If the ad hoc group call request contains an implicit transmit media request it may also include location information.
If the MCVideo user at MCVideo client 1 initiates an MCVideo emergency ad hoc group call or the MCVideo emergency state is already set for the MCVideo client 1 (due to a previously triggered MCVideo emergency alert):
i. the MCVideo ad hoc group call request shall contain an emergency indicator;
ii. if the MCVideo emergency state is not set already, MCVideo client 1 sets its MCVideo emergency state. The MCVideo emergency state of MCVideo client 1 is retained until explicitly cancelled by the user of MCVideo client 1.
2. The MCVideo server accepts the ad hoc group call request if the ad hoc group call is supported and authorized. Otherwise reject the ad hoc group call request and do not continue with the rest of the steps.
If functional alias is present, the MCVideo 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 call request, the MCVideo server checks the privacy policy of the MCVideo user to decide if the location information of MCVideo client 1 can be provided to other users on the call (refer to Annex A.3 "Authorisation to provide location information to other MCVideo users on a call when talking").
If an emergency indicator is present in the received MCVideo ad hoc group call request, the MCVideo ad hoc group is considered to be in the in-progress emergency state until this ad hoc group call is terminated; and
If an imminent peril indicator is present in the received MCVideo ad hoc group call request, the MCVideo ad hoc group is considered to be in the in-progress imminent peril state until this ad hoc group call 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 MCVideo 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 MCVideo server assigns a MCVideo 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 MCVideo server shall send the ad hoc group call request return message to MCVideo client 1 containing the below:
i. The MCVideo ad hoc group ID, either generated by the MCVideo server, if not included in the ad hoc group call request of step 1, or if the provided MCVideo ad hoc group ID is not accepted by the MCVideo server, or provided by the MCVideo 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 call is authorized or not
If the ad hoc group call request is not authorized, MCVideo server and client 1 shall not proceed with the rest of the steps.
4. The MCVideo server determines the list of participants to be invited for the ad hoc group call 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 MCVideo server may modify the content of the criteria received in step 1 to determine the list of participants.
NOTE: The content of the Criteria information element, the details of the pre-defined criteria, and the way how the MCVideo server determines the list of participants are left to implementation.
5. The MCVideo server sends the ad hoc group call requests towards the MCVideo clients 2 and 3. While sending the ad hoc group call requests, the MCVideo server shall remove the information elements that are not required to be conveyed to the target MCVideo clients. This request carries the pre-configured group ID whose configuration is to be applied for this ad hoc group call if end-to-end encryption is requested. The MCVideo server considers the ad hoc group call participants as implicitly affiliated to the ad hoc group.
6. The receiving MCVideo clients are notified about the incoming ad hoc group call.
7. The receiving MCVideo clients accept the ad hoc group call requests and send ad hoc group call responses to the MCVideo server. The response may also contain a functional alias of the responding MCVideo user, which is verified (valid and activated for the user) by the MCVideo server.
8. The MCVideo server sends the ad hoc group call response to MCVideo client 1 through the signalling path to inform about successful call establishment. The ad hoc group call response contains the call resulting criteria used by the MCVideo server to determine the list of participants to be invited.
9. The MCVideo server may notify the initiating MCVideo user of all MCVideo users who acknowledged the ad hoc group call request and joined the ad hoc group call. This notification may be sent to the initiating MCVideo user by the MCVideo server more than once during the call when MCVideo users join or leave the MCVideo ad hoc group call. If the authorized users (not shown in figure) are configured to receive the participants information of ad hoc group call, the MCVideo server provides ad hoc group call notify about all MCVideo users who acknowledged the ad hoc group call request and joined the ad hoc group call, and when MCVideo users join or leave the MCVideo ad hoc group call. All ad hoc group call notify messages contain the call resulting criteria used by the MCVideo server to determine the list of participants to be invited.
10. MCVideo client 1, MCVideo client 2 and MCVideo client 3 establish media plane and transmission control resources.
The MCVideo server continuously checks whether other MCVideo users meet the criteria in order to add them to the ongoing ad hoc group communication, or whether any of the participating MCVideo users no longer meet the criteria in order to remove them from the ongoing ad hoc group communication, according to clause 7.19.3.1.5.
7.19.3.1.4 Modification of ad hoc group call participants by an authorized user
Figure 7.19.3.1.4-1 below illustrates the modification of ad hoc group call participants procedure by an authorized user.
Pre-conditions:
1. An ad hoc group call which is setup with participants list provided by the initiating MCVideo user as described in clause 7.19.3.1.1 or based on the criteria provided by the initiating MCVideo user as described in clause 7.19.3.1.3 is already in progress.
2. The participants of the MCVideo ad hoc group call belong to the single MCVideo system.
3. The MCVideo users on MCVideo client 1, MCVideo client 3 to MCVideo client n are on an ongoing ad hoc group call.
4. The MCVideo user at MCVideo client 1 determines to remove the user of MCVideo client 3 from the ad hoc group call and add user of MCVideo client 2 into the on-going ad hoc group call.
Figure 7.19.3.1.4-1: Modification of ad hoc group call participants by an authorized user
1. The MCVideo user at the MCVideo client 1 is authorized and requests to modify ad hoc group call participants. The MCVideo client 1 sends the modify ad hoc group call participants request to the MCVideo server in order to remove MCVideo client 3 from the ongoing ad hoc group call and add MCVideo client 2 into it.
2. The MCVideo server verifies whether the MCVideo client 1 is authorized to add or remove (modify) the participants of the on-going ad hoc group call regardless of the original group call setup parameters. When the group participants were initially determined by the MCVideo server with criteria and MCVideo users are to be removed, the MCVideo server removes MCVideo clients and marks them so that the MCVideo 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 MCVideo 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 MCVideo server sends modify ad hoc group call participants response to the MCVideo client 1.
4. The MCVideo server sends the ad hoc group call leave request to the MCVideo client 3 in order to remove it from the on-going ad hoc group call.
5. The MCVideo client 3 notifies the user of the ad hoc group call leave request.
6. The MCVideo client 3 sends the ad hoc group call leave response to the MCVideo server.
7. The MCVideo server sends the ad hoc group call request towards MCVideo client 2.
NOTE 2: Steps 7 to 9 can occur at any time following step 3.
8. The receiving MCVideo client 2 notifies the user about the incoming ad hoc group call.
9. The MCVideo client 2 accepts the ad hoc group call request and send ad hoc group call responses to the MCVideo server. The response may also contain a functional alias of the responding MCVideo user, which is verified (valid and activated for the user) by the MCVideo server. The MCVideo server considers the MCVideo user as implicitly affiliated to the ad hoc group.
10. The MCVideo server may notify the initiating MCVideo user of all the users who are added to the on-going ad hoc group call. This notification may be sent to the initiating MCVideo user by the MCVideo server more than once during the call when MCVideo users join or leave the ad hoc group call.
11. The MCVideo server may notify the participants about the change in the participants of on-going ad hoc group call.
7.19.3.1.5 Modification of ad hoc group call participants by the MCVideo server
Figure 7.19.3.1.5-1 below illustrates the modification of ad hoc group call participants procedure by the MCVideo server.
Pre-conditions:
1. The MCVideo client 1 is the initiator of the ad hoc group call.
2. MCVideo server determined the participants for the ad hoc group call based on the criteria specified by the MCVideo client 1 while initiating the ad hoc group call.
3. MCVideo 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 call.
4. The MCVideo server detects that the MCVideo client 5 satisfies the criteria and MCVideo client 4 stops to meet the criteria specified by the MCVideo client 1.
Figure 7.19.3.1.5-1: Modification of ad hoc group call participants by the MCVideo server
1. The ad hoc group call is established and on-going with the participants MCVideo client 1, MCVideo client 2, MCVideo client 3 and MCVideo client 4. The participants list is determined by the MCVideo server based on the criteria specified by the MCVideo client 1 while initiating the call
2. The MCVideo server detects that the MCVideo client 5 satisfies the criteria specified by the MCVideo client 1 and checks whether it has been previously removed by an authorized user as described in clause 7.19.3.1.4. If MCVideo client 5 has already been removed by an authorized user, the MCVideo server does not add the MCVideo client 5 back to the ad hoc group call and it skips step 3 to step 6. If MCVideo client 5 has not been already removed by an authorized user, the procedure continues with step 3.
3. The MCVideo server sends the ad hoc group call request to the MCVideo client 5.
4. The MCVideo client 5 notifies the user about the incoming ad hoc group call.
5. The MCVideo client 5 accepts the ad hoc group call request and sends the ad hoc group call response to the MCVideo server.
6. The on-going ad hoc group call is updated by adding MCVideo client 5 which satisfies the criteria specified by the MCVideo client 1.
7. The MCVideo server detects that the MCVideo client 4 is no more satisfying the criteria to be the participant of the ad hoc group call and checks whether it has been previously added by an authorized user as described clause 7.19.3.1.4. If MCVideo client 4 has been previously added by an authorized user, the MCVideo server does not remove it from the ad hoc group call and skips step 8 to step 11. If MCVideo client 4 has not been already added by an authorized user, the procedure continues with step 8.
8. The MCVideo server sends the ad hoc group call leave request to the MCVideo client 4 and removes it from the on-going ad hoc group call.
9. The MCVideo client 4 notifies the user of the ad hoc group call leave request.
10. The MCVideo client 4 sends the ad hoc group call leave response to the MCVideo server.
11. The on-going ad hoc group call is updated by removing MCVideo client 4, which no more satisfies the criteria specified by the MCVideo client 1.
7.19.3.1.6 Modification of ad hoc group call criteria by an authorized user
Figure 7.19.3.1.6-1 below illustrates the modification of ad hoc group call criteria procedure by an authorized user.
Pre-conditions:
1. The MCVideo user at the MCVideo client 1 is authorized to modify the criteria.
2. Both the MCVideo server and the MCVideo client 1 are aware of the criteria related to the ongoing ad hoc group call.
Figure 7.19.3.1.6-1: Modification of ad hoc group call criteria by the authorized user
1. The MCVideo user at the MCVideo client 1 is authorized and requests to modify the criteria for determining the list of participants. The MCVideo client 1 sends the modify ad hoc group call criteria request to the MCVideo server which contains the updated criteria to determine the list of participants.
2. The MCVideo server verifies whether the MCVideo client 1 is authorized to modify the criteria which determines the list of participants during on-going ad hoc group video call. The MCVideo 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.19.3.1.4.
If MCVideo client 3 satisfies the new criteria to be removed and
- has already been added by an authorized user, the MCVideo 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 MCVideo client 2 satisfies the new criteria to be added and
- has already been removed by an authorized user, the MCVideo server does not add it back to the call and skips the step 7 to step 9.
- has not been already removed by an authorized user, the procedure continues with step 4.
Depending on the criteria provided and based on local policy, the MCVideo server may modify the content of the criteria received in step 1 to determine the list of participants.
3. The MCVideo server sends modify ad hoc group call criteria response containing the call resulting criteria used by the MCVideo server to determine the list of participants to be invited to the MCVideo client 1.
4. The MCVideo server sends the ad hoc group call leave request to the MCVideo client 3 in order to remove it from the on-going ad hoc group call.
5. The MCVideo client 3 notifies the user of the ad hoc group call leave request.
6. The MCVideo client 3 sends the ad hoc group call leave response to the MCVideo server.
7. The MCVideo server sends the ad hoc group call request towards MCVideo client 2.
NOTE 1: Steps 7 to 9 can occur at any time following step 3.
8. The receiving MCVideo client 2 notifies the user about the incoming ad hoc group call.
9. The MCVideo client 2 accepts the ad hoc group call request and send ad hoc group call responses to the MCVideo server. The response may also contain a functional alias of the responding MCVideo user, which is verified (valid and activated for the user) by the MCVideo server. The MCVideo server considers the MCVideo user as implicitly affiliated to the ad hoc group.
10. The MCVideo server may notify the initiating MCVideo user of all the users who are added to the on-going ad hoc group call. This notification may be sent to the initiating MCVideo user by the MCVideo server more than once during the call when MCVideo users join or leave the ad hoc group call. All ad hoc group call notify messages contain the call resulting criteria used by the MCVideo server to determine the list of participants to be invited.
11. The MCVideo server may notify the participants about the change in the participants list of on-going ad hoc group call. All ad hoc group call notify messages contain the call resulting criteria used by the MCVideo server to determine the list of participants to be invited.
The MCVideo server continuously checks whether other MCVideo clients meet or if participating MCVideo 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.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.19.3.2 Ad hoc group call involving multiple MC systems
| 7.19.3.2.1 Ad hoc group call setup – Participants list determined by the MCVideo server
Figure 7.19.3.2.1-1 below illustrates the ad hoc group call setup procedure initiated by an authorized user wherein the list of participants is determined by the MCVideo server based on the criteria received from the MCVideo client and determined MCVideo users are from multiple MCVideo 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 MCVideo user/dispatcher belongs to the primary MC system.
3. The MCVideo server 1 of the primary MC system is where the authorized MCVideo user/dispatcher creates the ad hoc group.
4. Some users of the ad hoc group belong to MCVideo 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 MCVideo 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.19.3.2.1-1: Ad hoc group call setup involving multiple MCVideo systems
1-3. Same as described in subclause 7.19.3.1.3.
4. The MCVideo 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 call 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.
NOTE 1: The content of the Criteria information element, the details of the pre-defined criteria, and the way how the MCVideo server determines the list of participants are left to implementation.
5. If the MCVideo server 1 needs to involve the partner system based on the agreement and based on the criteria for determining the participants list, it sends the ad hoc group call get userlist request to the MCVideo server 2. Depending on the criteria provided and based on local policy, the MCVideo server may modify the content of the criteria received in step 1 to determine the list of participants. This request carries the call resulting criteria to be used by the partner MC system and is equal or derived from the criteria received in the step 1.
6. MCVideo server 2 evaluates the criteria and determines the participants satisfying the criteria (i.e. MCVideo client 3 and MCVideo client 4) and sends the response containing the list of MCVideo users satisfying the criteria. The partner MCVideo server may apply local policies if any while determining the participants satisfying the criteria.
7. The MCVideo server 1 compiles the list of participants to be invited for the ad hoc group call including the participants from both primary and partner MC system.
8a-8b. The MCVideo server 1 sends the ad hoc group call request towards the MCVideo client 3 and MCVideo client 4. While sending the ad hoc group call request, the MCVideo server shall remove the information elements that are not required to be conveyed to the target MCVideo clients. This request carries the pre-configured group ID whose configuration is to be applied for this ad hoc group call if end-to-end encryption is requested. The MCVideo server 1 considers the ad hoc group call participants as implicitly affiliated to the ad hoc group.
9. The MCVideo server 1 sends the ad hoc group call requests towards the MCVideo client 2. While sending the ad hoc group call request, the MCVideo server shall remove the information elements that are not required to be conveyed to the target MCVideo clients. This request carries the pre-configured group ID whose configuration is to be applied for this ad hoc group call if end-to-end encryption is requested. The MCVideo server 1 considers the ad hoc group call participants as implicitly affiliated to the ad hoc group.
10a-10c. The receiving MCVideo clients are notified about the incoming ad hoc group call.
11. The MCVideo client 2 accept the ad hoc group call request and send ad hoc group call response to the MCVideo server 1.
12. The MCVideo client 3 accepts the ad hoc group call request, and sends ad hoc group call response to the MCVideo server 1.
13. The MCVideo client 4 accepts the ad hoc group call request, and sends ad hoc group call response to the MCVideo server 1.
14. The MCVideo server 1 sends the ad hoc group call response to MCVideo client 1 through the signalling path to inform about successful call establishment. The ad hoc group call response contains the criteria used by the MCVideo server to determine the list of participants to be invited.
15. The MCVideo server 1 may notify the initiating MCVideo user of all MCVideo users who acknowledged the ad hoc group call request and joined the ad hoc group call. The MCVideo server 1 more than once during the call may send this notification to the initiating MCVideo user whenever an MCVideo user joins or leaves the MCVideo ad hoc group call. If the authorized users (not shown in figure) are configured to receive the participants information of ad hoc group call, the MCVideo server provides ad hoc group call notify about all MCVideo users who acknowledged the ad hoc group call request and joined the ad hoc group call, and when MCVideo users join or leave the MCVideo ad hoc group call. All ad hoc group call notify messages contain the call resulting criteria used by the MCVideo server to determine the list of participants to be invited.
16. The MCVideo client 1, MCVideo client 2, MCVideo client 3 and MCVideo client 4 establish media plane and transmission control resources.
NOTE 2: The ad hoc group call request and response exchanged between MCVideo server 1 of primary MC system and MCVideo client 3/MCVideo client 4 will always traversal through the MCVideo server 2.
The MCVideo server at the primary MC system and the MCVideo at the partner MC system continuously checks whether other MCVideo users in the primary MC system and MCVideo users in the partner MC system, respectively, meet the criteria in order to add them to the ongoing ad hoc group communication, or whether any of the participating MCVideo users in the primary MC system and MCVideo users in the partner MC system, respectively, no longer meet the criteria in order to remove them from the ongoing ad hoc group communication, according to clause 7.17.3.2.4.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.19.3.2.2 Modification of ad hoc group call participants by the MCVideo server
| Figure 7.19.3.2.2-1 below illustrates the MCVideo server modifying the ad hoc group call participants procedure involving multiple MCVideo systems.
Pre-conditions:
1. The MCVideo user at MCVideo client 1 is authorized to initiate ad hoc group call.
2. The MCVideo server 1 of the primary and MCVideo server 2 of the partner MCVideo systems determined the participants for the ad hoc group call based on the criteria specified by the MCVideo client 1 while initiating the ad hoc group call.
3. The MCVideo server 1 of the primary and MCVideo server 2 of the partner MCVideo 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 call.
4. The MCVideo server 1 of the primary MCVideo system detects that the MCVideo client 3 meets the criteria and MCVideo client 2 stops to meet the criteria specified by the MCVideo client 1.
5. The MCVideo server 2 of the partner MCVideo system detects that the MCVideo client 5 meets the criteria and MCVideo client 4 stops to meet the criteria specified by the MCVideo client 1.
Figure 7.19.3.2.2-1: Modification of ad hoc group call participants by the MCVideo server
1. The ad hoc group call is established and on-going with the participants MCVideo client 1, MCVideo client 2, and MCVideo client 4. The participants list is determined by both primary and partner systems MCVideo server based on the criteria specified by the MCVideo client 1 while initiating the call.
2. The MCVideo server 1 detects that MCVideo client 3 now meets criteria and successfully added to call.
3. The MCVideo server 1 detects that MCVideo client 2 does not meet criteria any more and successfully removed from a call.
4. The MCVideo server 2 detects that the MCVideo client 5 meets the criteria specified by the MCVideo client 1.
5. The MCVideo server 2 sends the notification to MCVideo server 1 of the primary MCVideo system to add the MCVideo user at MCVideo client 5 to on-going ad hoc group call.
6. The MCVideo server 1 sends the ad hoc group call request to the MCVideo client 5.
7. The MCVideo client 5 notifies the user about the incoming ad hoc group call.
8. The MCVideo client 5 accepts the ad hoc group call request and sends the ad hoc group call response to the MCVideo server 1.
9. The on-going ad hoc group call is updated by adding MCVideo client 5 which meets the criteria specified by the MCVideo client 1.
10. The MCVideo server 2 detects that the MCVideo client 4 is no more satisfying the criteria to be the participant of the ad hoc group call.
11. The MCVideo server 2 sends the notification to MCVideo server 1 of the primary MCVideo system to remove the MCVideo user at MCVideo client 4 from on-going ad hoc group call.
12. The MCVideo server 1 sends the ad hoc group call leave request to the MCVideo client 4 and removes it from the on-going ad hoc group call.
13. The MCVideo client 4 notifies the user of the ad hoc group call leave request.
14. The MCVideo client 4 sends the ad hoc group call leave response to the MCVideo server 1.
15. The on-going ad hoc group call is updated by removing MCVideo client 4, which no more meets the criteria specified by the MCVideo client 1.
NOTE: The ad hoc group call request and response exchanged between MCVideo server 1 of primary MC system and MCVideo client 4/MCVideo client 5 will always traversal through the MCVideo server 2.
7.19.3.2.3 Release ad hoc group call and stop determining the ad hoc group call participants by partner MCVideo system – Participants list determined by the MCVideo server
Figure 7.19.3.2.3-1 below illustrates the release of ad hoc group call and stopping of MCVideo server at the partner MC system from determining the ad hoc group call participants’ procedure once involving multiple MCVideo systems. This procedure, in particular describes about how the partner MC system is notified about ad hoc group call release to cease the determining of the participants by the partner MC system.
Pre-conditions:
1. The MCVideo user at MCVideo client 1 is authorized to initiate ad hoc group call.
2. The MCVideo server 1 of the primary and MCVideo server 2 of the partner MCVideo systems determined the participants for the ad hoc group call based on the criteria specified by the MCVideo client 1 while initiating the ad hoc group call.
3. The MCVideo server 1 of the primary and MCVideo server 2 of the partner MCVideo 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 call.
Figure 7.19.3.2.3-1: MCVideo server releases an ad hoc group call and stops the determination of ad hoc group call participants involving multiple MCVideo systems
1. The ad hoc group call is established and on-going with the participants MCVideo client 1, MCVideo client 2, MCVideo client 3, and MCVideo client 4. The participants list is determined by both primary and partner systems MCVideo server based on the criteria specified by the MCVideo client 1 while initiating the call.
2. The MCVideo server 1 detects that the ad hoc group call 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 MCVideo group members are not present.
3. The MCVideo server 1 sends the notification to MCVideo server 2 of the partner MCVideo system about the ad hoc group call release to stop determining the participants list by MCVideo server 2 of the partner MCVideo system.
4a-4d. The MCVideo server 1 sends ad hoc group call release request to all the participants of the ad hoc group call.
5a-5d. The MCVideo clients notifies the user about the release of the ad hoc group call.
6a-6d. All the participants of the ad hoc group call receives the ad hoc group call release request and sends the ad hoc group call release response to the MCVideo server 1 of the primary MCVideo server.
NOTE: The ad hoc group call request and response exchanged between MCVideo server 1 of primary MC system and MCVideo client 3/MCVideo client 4 will always traversal through the MCVideo server 2.
7.19.3.2.4 Procedure for ad hoc group call setup – Participants list provided by the Initiator
Figure 7.19.3.2.4-1 illustrates the procedure for ad hoc group call 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 MCVideo users are from multiple MCVideo 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 MCVideo user/dispatcher belongs to the primary MC system.
3. The MCVideo server of the primary MC system is where the authorized MCVideo user/dispatcher controls 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 to be used for an ad hoc group have been preconfigured in the MCVideo 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, MCVideo client is aware of the ad hoc group ID.
Figure 7.19.3.2.4-1: Ad hoc group call setup
1. The MCVideo client of the authorized user initiates an ad hoc group call with multiple users from primary and partner MC systems. An ad hoc group call request message with the information of the MCVideo IDs or an ad hoc group ID if the ad hoc group call follows an ad hoc group emergency alert is routed to the MCVideo server of the primary MC system.
2. If the ad hoc group call is supported, the MCVideo server of the primary MC system verifies whether the user at MCVideo client is authorized to initiate an ad hoc group call. If not authorized, the MCVideo server of the primary MC system rejects the ad hoc group call 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 MCVideo server of the primary MC system forms the ad hoc group by using received information. The MCData server further determines the preconfigured group to be used for the configuration and assigns an MCVideo group ID for the newly formed ad hoc group.
If no MCVideo ad hoc group ID was included in the ad hoc group call request of step 1, or if the provided MCVideo ad hoc group ID is not accepted by the MCVideo server, the MCVideo server assigns a MCVideo group ID for the newly formed ad hoc group
If the the MC service users' information received in step 1 does not contain an MCVideo ad hoc group ID from an ad hoc group emergency alert, the MCVideo server of the primary MC system forms the ad hoc group by using MCVideo users' information received in step 1, determines the preconfigured group to be used for the configuration of the ad hoc and assigns a MCVideo group ID for the newly formed ad hoc group.
The MCVideo server identifies the appropriate MCVideo server responsible for the MCVideo users of the ad hoc group. The MCVideo server considers the ad hoc group call participants as implicitly affiliated to the ad hoc group.
NOTE 1: The ad hoc group information including the MCVideo group ID and the list of users is held in dynamic data in the MCVideo server.
3. The MCVideo server shall send the ad hoc group call request return message to the MCVideo client containing the below:
i. The MCVideo ad hoc group ID either generated by the MCVideo server or provided by the MCVideo client if the ad hoc group ID is from an ad hoc group emergency alert (only included when the ad hoc group call is authorized);
ii. The group ID of the pre-configured group to be used for the ad hoc group call (only included when the ad hoc group call is authorized); and
iii. Result of whether the ad hoc group call is authorized or not.
If the ad hoc group call request is not authorized, the MCVideo client shall not proceed with the rest of the steps.
4. The MCVideo server of the primary MC system sends the ad hoc group call request to the affiliated group members of the ad hoc group belonging to the primary MC system.
5. The MCVideo clients receive in the ad hoc group call request the information of the MCVideo group ID for the ad hoc group and further notify their corresponding MCVideo user. The affiliated group members of the ad hoc group of the primary MC system may accept or reject the call and respond with the group call response.
6. The primary MCVideo server further initiates an ad hoc group call request message to the MCVideo users of the partner MC system. The ad hoc group call request message is routed to the MCVideo users via the MCVideo server of the partner MC system.
7. The MCVideo clients receive in the ad hoc group call request the information of the MCVideo group ID for the ad hoc group and further notify their corresponding MCVideo user. The MCVideo users upon receipt of the invitation may accept or reject the call, and respond with the ad hoc group call response. The ad hoc group call response message is routed to the MCVideo server of the primary MC system via the MCVideo server of the partner MC system.
8. The MCVideo server of the primary MC system provides an ad hoc group call response message to the MCVideo client of the authorized MCVideo user upon receiving response to the corresponding ad hoc group call request in step 1. The ad hoc group call response will consist of the success or failure result and/or detailed reason information in case of failure.
NOTE 2: The ad hoc group call response message is triggered depending on the conditions to proceed with the call.
9. Upon successful ad hoc group call setup, a group call is established amongst the multiple group members from primary and partner MC systems. The media plane and transmission control resources are established.
7.19.3.2.5 Procedure for ad hoc group call release by MCVideo server – Participants list provided by the Initiator
This procedure focuses on the case where an MCVideo server initiates the termination of an ongoing MCVideo ad hoc group call for all the participants of that group call, 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 MCVideo group members are not present.
Procedures in figure 7.19.3.2.5-1 are the signalling control plane procedures for the MCVideo server initiating termination of an ongoing MCVideo ad hoc group call.
Pre-condition:
- The MCVideo client 1 and MCVideo client 2 belong to primary MC system. The MCVideo client 3 belongs to partner MC system.
Figure 7.19.3.2.5-1: Ad hoc group call release
1. The MCVideo users on MCVideo client 1, client 2 and client 3 are already part of the ongoing ad hoc group call (e.g. as a result of ad hoc group call setup as specified in clause 7.19.3.2.4).
2. The MCVideo server would like to release the ad hoc group call which is ongoing e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or minimum number of affiliated MCVideo group members are not present.
3. The MCVideo server identifies the participants of the ongoing ad hoc group call and generates ad hoc group call release request to release ongoing session.
4. The MCVideo server sends an ad hoc group call release request via SIP core towards each participant of the ongoing group call. If the participants belong to partner MC system, then ad hoc group call release request is routed to the MCVideo clients of the partner MC system via the partner MCVideo server.
5. The MCVideo users are notified about the release of the ad hoc group call.
6. The MCVideo client(s) receiving ad hoc group call release request, send acknowledgement towards the MCVideo server by sending a ad hoc group call release response.
7. The MCVideo client 1, client 2 and client 3 have successfully released the transmission control and media plane resources associated with the ad hoc group call that is terminated. The MCVideo servers remove the ad hoc group information from the dynamic data held in the MCVideo servers and the ad hoc group ceases to exist, otherwise if the ad hoc group call follows an ad hoc group emergency alert the MCVideo servers keep the dynamic data and the ad hoc group continues to exist.
7.19.3.2.6 Modification of ad hoc group call participants by an authorized user
Figure 7.19.3.2.6-1 below illustrates the MCVideo user modifying the ad hoc group call participants procedure involving multiple MCVideo systems.
Pre-conditions:
1. An MCVideo ad hoc group call is already in progress and the participants list provided by the originating MCVideo user while initiating the MCVideo ad hoc group call.
2. The participants of the MCVideo ad hoc group call belongs to the multiple MCVideo system.
3. The MCVideo user at MCVideo client 1 determines that the MCVideo client 3 needs to be invited to on-going ad hoc group call and MCVideo client 2 needs to be removed from the on-going ad hoc group call from the primary MCVideo system.
4. The MCVideo user at MCVideo client 1 determines that the MCVideo client 5 needs to be invited to on-going ad hoc group call and MCVideo client 4 needs to be removed from the on-going ad hoc group call from the partner MCVideo system.
Figure 7.19.3.2.6-1: Modification of ad hoc group call participants by an authorized user
1. The MCVideo client 1 sends the modify ad hoc group call participants request to the MCVideo server 1 to remove both MCVideo client 2 and MCVideo client 4 from the on-going ad hoc group call and to add both MCVideo client 3 and MCVideo client 5 into on-going ad hoc group call.
2. The MCVideo server 1 verifies whether the MCVideo client 1 is authorized to add or remove (modify) the participants of the on-going ad hoc group call.
3. The MCVideo server 1 sends modify ad hoc group call participants response to the MCVideo client 1.
4. The MCVideo server 1 determines that MCVideo client 1 has requested that MCVideo client 3 from the primary MC system be invited to an on-going ad hoc group call and successfully added to the call according to the procedure defined in clause 7.19.3.1.4.
5. The MCVideo server 1 determines that MCVideo client 1 has requested that MCVideo client 2 from the primary MC system be removed from the on-going ad hoc group call and successfully removed from call according to the procedure defined in clause 7.19.3.1.4.
6. The MCVideo server 1 determines that MCVideo client 1 has requested that MCVideo client 5 from the partner MC system be invited to an on-going ad hoc group call. The MCVideo server 1 sends the ad hoc group call request to the MCVideo client 5.
7. The MCVideo client 5 notifies the user about the incoming ad hoc group call.
8. The MCVideo client 5 accepts the ad hoc group call request and sends the ad hoc group call response to the MCVideo server 1.
9. The on-going ad hoc group call is updated by adding MCVideo client 5 which is based on the modify participant list provided by the MCVideo client 1.
10. The MCVideo server 1 determines that MCVideo client 1 has requested that MCVideo client 4 from the partner MC system be removed from the on-going ad hoc group call. The MCVideo server 1 sends the ad hoc group call leave request to the MCVideo client 4.
11. The MCVideo client 4 notifies the user of the ad hoc group call leave request.
12. The MCVideo client 4 sends the ad hoc group call leave response to the MCVideo server 1.
13. The on-going ad hoc group call is updated by removing MCVideo client 4, which is based on the modify participant list provided by the MCVideo client 1.
NOTE: The ad hoc group call request and response exchanged between MCVideo server 1 of primary MC system and MCVideo client 4/MCVideo client 5 will always traversal through the MCVideo server 2.
14. The MCVideo server 1 may notify the initiating MCVideo user of all the users who are added to the on-going ad hoc group call. This notification may be sent to the initiating MCVideo user by the MCVideo server more than once during the call when MCVideo users join or leave the ad hoc group call.
15. The MCVideo server 1 may notify the authorized participants about the change in the participants list of on-going ad hoc group call.
7.19.3.2.7 Modification of ad hoc group call criteria by an authorized user
Figure 7.19.3.2.7-1 illustrates the modification of ad hoc group call criteria procedure by the initiator of the ad hoc group call between multiple MC systems.
Preconditions:
- The MCVideo user at the MCVideo client 1 is authorized to modify the criteria.
- The MCVideo server A and MCVideo server B are aware of the criteria related to the ongoing ad hoc group call.
- MC system A and MC system B are interconnected.
Figure 7.19.3.2.7-1: Modifying the criteria for determining the participants during an ongoing ad hoc group call between multiple MC systems
1. An ad hoc group call has been established based on criteria sent by an authorized MCVideo client upon initiating the ad hoc group call.
2. The MCVideo user at the MCVideo client 1 is authorized and wishes to modify the criteria for determining the list of ad hoc group call participants.
3a. MCVideo client 1 sends a modify ad hoc group call criteria request to MCVideo server A.
3b. MCVideo server A determines that the modify ad hoc group call criteria request received in step 3a has impact on users in MCVideo server B. Depending on the criteria provided and based on local policy, the MCVideo server may modify the content of the criteria received in step 3a to determine the list of participants.
3c. MCVideo server A sends a modify ad hoc group call criteria request to MCVideo server B containing the call resulting criteria to be used by MCVideo server B.
NOTE 1: If MCVideo server A identifies that the criteria require to add participants from another MC system then MCVideo server A sends an ad hoc group call request to the MCVideo server in that MC system.
4a/b. The MCVideo server A receives the ad hoc group call criteria modify response and forwards the response to MCVideo client 1 in MC system A.
5. MCVideo server B detects that MCVideo client 3 meets the criteria for the ongoing ad hoc group call initiated at MC system A.
5a. MCVideo server B sends an ad hoc group call add user notification message towards MCVideo server A.
5b. MCVideo server A sends an ad hoc group call request towards MCVideo client 3.
5c. The MCVideo user 3 is notified of entering an ongoing ad hoc group call.
5d. MCVideo client 3 sends an ad hoc group call response towards MCVideo server A.
5e. MCVideo server B sends an ad hoc group call remove user notification message towards MCVideo server A.
5f. MCVideo server A sends an ad hoc group call leave request towards MCVideo client 4.
5g. The MCVideo user 4 is notified of leaving an ongoing ad hoc group call.
5h. MCVideo client 4 sends an ad hoc group call leave response towards MCVideo server A.
6. The MCVideo server A may notify the authorised MCVideo user of all the users who are added to the on-going ad hoc group call. This notification may be sent to the authorised MCVideo user by the MCVideo server A more than once during the call when MCVideo users join or leave the ad hoc group call. All ad hoc group call notify messages contain the call resulting criteria used by the MCVideo server to determine the list of participants to be invited.
7. The MCVideo server A adds MCVideo client 3 to the ad hoc group call and removes MCVideo client 4 from the ad hoc group call.
The MCVideo servers continuously check whether other MCVideo clients meet or if participating MCVideo clients no longer meet the criteria for the ad hoc group 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 the ad hoc group call participant list then the ongoing ad hoc group emergency alert is modified accordingly.
Annex A (normative):
MCVideo related configuration data
A.1 General
This Annex provides information about the static data needed for configuration for the MCVideo service, which belongs to one of the following categories:
- MCVideo UE configuration data (see subclause A.2);
- MCVideo user profile configuration data (see subclause A.3);
- MCVideo related group configuration data (see subclause A.4); and
- MCVideo service configuration data (see subclause A.5).
For each configuration category, data is split between configuration data that is applicable to both on network and off network, configuration data that is applicable to on-network only, and configuration data that is applicable to off-network only. The configuration data in each configuration category corresponds to a single instance of the category type i.e. the MCVideo UE, MCVideo group, MCVideo user and MCVideo service configuration data refers to the information that will be stored against each MCVideo UE, MCVideo group, MCVideo user and MCVideo service. This means that the three separate tables (on-network and off-network, on-network only, off-network only) for each configuration category represent the complete set of data for each configuration data category element.
The columns in the tables have the following meanings:
- Reference: the reference of the corresponding requirement in 3GPP TS 22.281 [3] or 3GPP TS 22.280 [2] or the corresponding subclause from either the present document or the referenced document.
- Parameter description: A short definition of the semantics of the corresponding item of data, including denotation of the level of the parameter in the configuration hierarchy.
- When it is not clear to which functional entities the parameter is configured, then one or more columns indicating this are provided where the following nomenclature is used:
- "Y" to denote "Yes" i.e. the parameter denoted for the row needs to be configured to the functional entity denoted for the column.
- "N" to denote "No" i.e. the parameter denoted for the row does not need to be configured to the functional entity denoted for the column.
Parameters within a set of configuration data have a level within a hierarchy that pertains only to that configuration data. The hierarchy of the configuration data is common across all three tables of on-network and off-network, on network only and off network only. The level of a parameter within the hierarchy of the configuration data is denoted by use of the character ">" in the parameter description field within each table, one per level. Parameters that are at the top most level within the hierarchy have no ">" character. Parameters that have one or more ">" characters are child parameters of the first parameter above them that has one less ">" character. Parent parameters are parameters that have one or more child parameters. Parent parameters act solely as a "grouping" of their child parameters and therefore do not contain an actual value themselves i.e. they are just containers for their child parameters.
Each parameter that can be configured online shall only be configured through one online reference point. Each parameter that can be configured offline shall only be configured through one offline reference point. The most recent configuration data made available to the MCVideo UE shall always overwrite previous configuration data, irrespective of whether the configuration data was provided via the online or offline mechanism.
A.2 MCVideo UE configuration data
The general aspects of UE configuration are specified in 3GPP TS 23.280 [6]. Data in tables A.2-1 and A.2-2 have to be known by the MCVideo UE after MCVideo authorization.
Data in table A.2-1 can be configured offline using the CSC-11 reference point. Table A.2-1 contains the UE configuration required to support the use of off-network MCVideo service.
Table A.2-1: UE configuration data (on and off network)
Reference
Parameter description
[R-5.4.2-002] of 3GPP TS 22.280 [2]
Maximum number of simultaneous MCVideo group calls (Nc4)
[R-5.4.2-003] of 3GPP TS 22.280 [2]
Maximum number of video transmissions (Nc5) in a group
Table A.2-2: UE configuration data (on network)
Reference
Parameter description
Subclause 5.2.3 of 3GPP TS 23.280 [6]
Relay service (Y/N)
Subclause 5.2.3 of 3GPP TS 23.280 [6]
List of allowed relayed MCVideo groups and their relay service code (as specified in 3GPP TS 23.303 [7]) (optional) (see NOTE)
> MCVideo group ID
> Relay service code (as specified in 3GPP TS 23.303 [7])
NOTE: When the value of the parameter Relay service is N, this parameter and its child parameters are not needed.
A.3 MCVideo user profile configuration data
The general aspects of MC service user profile configuration data are specified in 3GPP TS 23.280 [6]. The MCVideo user profile configuration data is stored in the MCVideo user database. The MCVideo server obtains the MCVideo user profile configuration data from the MCVideo user database (MCVideo-2). The recording server obtains the MCVideo user profile configuration data from the configuration management server (REC-3 in 3GPP TS 23.280 [16]).
Tables A.3-1 and A.3-2 contain the MCVideo user profile configuration required to support the use of on-network MCVideo service. Tables A.3-1 and A.3-3 contain the MCVideo user profile configuration required to support the use of off-network MCVideo service. Data in table A.3-1 and table A.3-3 can be configured offline using the CSC-11 reference point.
Table A.3-1: MCVideo user profile configuration data (on and off network)
Reference
Parameter description
MCVideo UE
Rec. admin UE
&
Replay UE
(NOTE 8)
MCVideo Server
Configuration management server
Rec. server
MCVideo user database
Subclause 5.2.11 of 3GPP TS 23.280 [6]
MCVideo identity (MCVideo ID)
Y
Y
Y
Y
Y
Y
3GPP TS 33.180 [14]
KMSUri for security domain of MCVideo ID (see NOTE 1)
Y
Y
Y
Y
Subclause 5.2.11 of 3GPP TS 23.280 [6]
Pre‑selected MCVideo user profile indication (see NOTE 2)
Y
Y
Y
Y
Subclause 5.2.11 of 3GPP TS 23.280 [6]
MCVideo user profile index
Y
Y
Y
Y
Subclause 5.2.11 of 3GPP TS 23.280 [6]
MCVideo user profile name
Y
Y
Y
Y
[R-5.17-007],
[R-6.13.4-002] of 3GPP TS 22.280 [2]
User profile status (enabled/disabled)
Y
Y
Y
Y
Y
[R-5.7-001]
[R-6.9-003] of 3GPP TS 22.280 [2]
Authorised to create and delete aliases of an MCVideo user and its associated user profiles.
Y
Y
[R-5.7-002],
[R-6.9-003] of 3GPP TS 22.280 [2]
Alphanumeric aliases of user
Y
Y
Y
Y
[R-5.1.1-005],
[R-5.9-001] of 3GPP TS 22.280 [2]
Participant type of the user
Y
Y
Y
Y
[R-5.1.8-006],
[R-5.3-002],
[R-5.9-001],
[R-5.16.2-001],
[R-5.16.2-002] of 3GPP TS 22.280 [2]
User's Mission Critical Organization (i.e. which organization a user belongs to)
Y
Y
Y
Y
Y
Y
[R-5.2.2-003] and [R-6.6.3-002] of 3GPP TS 22.280 [2]
Authorisation to create a group-broadcast group (see NOTE 7)
Y
Y
[R-5.2.2-003] and [R-6.6.3-002 of 3GPP TS 22.280 [2]
Authorisation to create a user-broadcast group (see NOTE 7)
Y
Y
[R-5.6.2.4.1-002] of 3GPP TS 22.280 [2]
Authorised to activate MCVideo emergency alert
Y
Y
Y
Y
[R-5.6.2.4.1-013] of 3GPP TS 22.280 [17]
Automatically trigger a MCVideo emergency communication after initiating the MCVideo emergency alert
Y
Y
Y
Y
[R-5.6.2.4.1-004]
[R-5.6.2.4.1-008]
[R-5.6.2.4.1-012] of 3GPP TS 22.280 [2]
Group used on initiation of an MCVideo emergency group call (see NOTE 5)
Y
Y
Y
Y
[R-5.6.2.4.1-004],
[R-5.6.2.4.1-008],
[R-5.6.2.4.1-012] of 3GPP TS 22.280 [17]
Recipient for an emergency private MCVideo call (see NOTE 5)
> MCVideo ID
Y
Y
Y
Y
3GPP TS 33.180 [19]
> KMSUri for security domain of MCVideo ID (see NOTE 1)
Y
Y
Y
Y
[R-5.6.2.4.2-002] of 3GPP TS 22.280 [2]
Authorisation to cancel an MCVideo emergency alert
Y
Y
Y
Y
[R-6.15.6.2-002] of 3GPP TS 22.280 [2]
Authorised to activate an MCVideo ad hoc group emergency alert
Y
Y
Y
Y
[R-6.15.6.2-006] of 3GPP TS 22.280 [2]
Authorisation to cancel an MCVideo ad hoc group emergency alert
Y
Y
Y
Y
[R-6.15.6.2-007] of 3GPP TS 22.280 [2]
Authorised to set up an MCVideo group call using the ad hoc group used for the alert
Y
Y
Y
Y
Authorised to receive the participants information of an MCVideo ad hoc group emergency alert
N
Y
Y
Y
Authorised to modify the list of participants and criteria for an MCVideo ad hoc group emergency alert
Y
Y
Y
Y
[R-5.1.2.1.2-004] of 3GPP TS 22.281 [3]
Authorisation to modify the video settings of the transmitted video stream of another MCVideo User
Y
Y
Y
Y
[R-5.1.2.1.2-006] of 3GPP TS 22.281 [3]
Authorisation to renegotiate a codec during a video transmission.
Y
Y
Y
Y
[R-5.1.2.1.2-007] of 3GPP TS 22.281 [3]
Authorisation to remotely control the video capabilities or parameters for a camera on an MCVideo UE
Y
Y
Y
Y
[R-5.1.2.2.2-001] of 3GPP TS 22.281 [3]
Authorisation to remotely control the video capabilities or parameters of a remote MCVideo UE
Y
Y
Y
Y
[R-5.1.2.2.2-004] of 3GPP TS 22.281 [3]
Authorisation to receive and display the capabilities of a remote MCVideo UE
Y
Y
Y
Y
[R-5.1.3.1.2-004] of 3GPP TS 22.281 [3]
Authorisation to remotely activate another MCVideo User's camera
Y
Y
Y
Y
[R-5.1.9.2.2-002] of 3GPP TS 22.281 [3]
Authorisation to push a video to another MCVideo user .
Y
Y
Y
Y
[R-5.1.9.2.2-003] of 3GPP TS 22.281 [3]
Authorisation to enable and to disable the automatic sending of notification to a second MCVideo User that a video is being pushed to a third MCVideo User
Y
Y
Y
Y
[R-5.1.9.2.2-004] of 3GPP TS 22.281 [3]
List of MCVideo users for whom to receive notifications about video being pushed to them
Y
Y
Y
Y
> MCVideo IDs
[R-5.1.9.2.2-005] of 3GPP TS 22.281 [3]
List of specific video categories to receive (see NOTE 3)
Y
Y
Y
Y
> Video categories
[R-6.7.3-007] of 3GPP TS 22.280 [2]
List of user(s) who can be called in MCVideo private call
> MCVideo ID
Y
Y
Y
Y
> User info ID
Y
N
Y
Y
> ProSe discovery group ID
Y
N
Y
Y
> Presentation priority relative to other users and groups (see NOTE 4)
Y
Y
Y
Y
3GPP TS 33.180
> KMSUri for security domain of MCVideo ID (see NOTE 1)
Y
Y
Y
Y
[R-6.7.3-007] of 3GPP TS 22.280 [2]
Authorised to make a private video call towards users not included in "list of user(s) who can be called in MCVideo private call"
Y
Y
Y
Y
[R-5.1.10.2-002] of 3GPP TS 22.281 [3]
List of category tags
> Video category tag
Y
Y
Y
Y
[R-5.1.10.2-002] of 3GPP TS 22.281 [3]
Authorization to query MCVideo client
Y
Y
Y
Y
[R-5.1.3.2.2-004]
[R-5.1.10.2-002] of 3GPP TS 22.281 [3]
List of category tags that authorized to query MCVideo client
> Video category tag for query
Y
Y
Y
Y
[R-5.1.3.2.2-004]
[R-5.1.10.2-002] of 3GPP TS 22.281 [3]
List of geography areas that authorized to query MCVideo client
> Geography area to query
Y
Y
Y
Y
[R-5.1.1.1-015] of 3GPP TS 22.281 [3]
Authorization to perform video adaptation
Y
Y
Y
Y
[R-5.1.7-002] and
[R-6.8.7.2-007] and [R-6.8.7.2-008] of 3GPP TS 22.280 [2]
Priority of the user (see NOTE 6)
Y
Y
Y
[R-6.15.4-001…010] and
[R-5.1.10.2-008]
of 3GPP TS 22.280 [17]
User is a target for recording
Y
(NOTE 10)
Y
Y
Y
Y
Y
[R-6.15.4-001…010] and
[R-5.1.10.2-008]
of 3GPP TS 22.280 [17]
Recording server address (URI) (NOTE 9)
Y
(NOTE 10)
Y
Y
Y
Y
NOTE 1: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [6].
NOTE 2: As specified in 3GPP TS 23.280 [6], for each MCVideo user's set of MCVideo user profiles, only one MCVideo user profile shall be indicated as being the pre‑selected MCVideo user profile.
NOTE 3: If this list is blank then this implies that all video categories are acceptable for the MCVideo user.
NOTE 4: The use of this parameter by the MCVideo UE is outside the scope of the present document.
NOTE 5: This parameter is used for the emergency communication and also used as a target of the emergency alert request. At most one of them is configured; i.e. emergency communication will go to either a group or a user. If both are not configured the MCVideo user's currently selected group will be used.
NOTE 6: The use of the parameter is left to implementation.
NOTE 7: This parameter applies to temporary broadcast groups built from regrouping mechanism. This authorisation automatically sets the originator of the temporary group as the only transmitting party.
NOTE 8: This is the recording admin UE and/or replay UE of a user who is authorized to set this MCVideo user as target for recording and/or authorized to replay this MCVideo user’s recordings.
NOTE 9: If this parameter is absent, the recording server URI shall be that identified in the initial MC service UE configuration data (on-network, 3GPP TS 23.280 table A.6-1) or in the initial recording and replay UE configuration data (on-network, 3GPP TS 23.280 table A.10-1)
NOTE 10: These parameters, when provided to an MCVideo UE, are relevant only for recording administrators and replay users.
Table A.3-2: MCVideo user profile configuration data (on network)
Reference
Parameter description
MCVideo UE
Rec admin UE
&
Replay UE (NOTE 9)
MCVideo Server
Configuration management server
MCVideo user database
[R-5.1.5-001],
[R-5.1.5-002],
[R-5.10-001],
[R-6.4.7-002],
[R-6.8.1-008],
[R-6.7.4-002] of 3GPP TS 22.280 [2]
List of on-network MCVideo groups for use by an MCVideo user
> MCVideo Group ID
Y
Y
Y
Y
Y
> Application plane server identity information of group management server where group is defined
>> Server URI
Y
Y
Y
Y
Y
> Application plane server identity information of identity management server which provides authorization for group (see NOTE 1)
>> Server URI
Y
Y
Y
Y
Y
3GPP TS 33.180 [14]
> KMSUri for security domain of group (see NOTE 4)
Y
Y
Y
Y
> Presentation priority of the group relative to other groups and users (see NOTE 2)
Y
Y
Y
Y
Subclause 5.2.5 of 3GPP TS 23.280 [6]
List of groups user implicitly affiliates to after MCVideo service authorization for the user
> MCVideo Group ID
Y
Y
Y
Y
[R-6.4.2-006] of 3GPP TS 22.280 [2]
Authorisation of an MCVideo user to request a list of which MCVideo groups a user has affiliated to
Y
Y
Y
[R-6.4.6.1-002],
[R-6.4.6.1-003] of 3GPP TS 22.280 [2]
Authorisation to change affiliated groups of other specified user(s)
Y
Y
Y
[R-6.4.6.2-001],
[R-6.4.6.2-002] of 3GPP TS 22.280 [2]
Authorisation to recommend to specified user(s) to affiliate to specific group(s)
Y
Y
Y
[R-6.6.1-004] of 3GPP TS 22.280 [2]
Authorisation to perform regrouping
Y
Y
Y
Y
[R-6.7.2-001] of 3GPP TS 22.280 [2]
Presence status is available/not available to other users
Y
Y
Y
Y
[R-6.7.1-002],
[R-6.7.2-002] of 3GPP TS 22.280 [2]
List of MCVideo users that MCVideo user is authorised to obtain presence of
> MCVideo IDs
Y
Y
Y
Y
[R-6.8.7.4.2-001],
[R-6.8.7.4.2-002] of 3GPP TS 22.280 [2]
Authorisation of a user to cancel an emergency alert on any MCVideo UE of any user
Y
Y
Y
[R-6.13.4-001] of 3GPP TS 22.280 [2]
Authorisation for an MCVideo user to enable/disable an MCVideo user
Y
Y
Y
[R-6.13.4-003],
[R-6.13.4-005],
[R-6.13.4-006],
[R-6.13.4-007] of 3GPP TS 22.280 [2]
Authorisation for an MCVideo user to (permanently /temporarily) enable/disable a UE
Y
Y
Y
[R-7.14-002],
[R-7.14-003] of 3GPP TS 22.280 [2]
Authorization for manual switch to off-network while in on-network
Y
Y
Y
Y
[R-5.1.5-004] of 3GPP TS 22.280 [2]
Limitation of number of affiliations per user (Nc2)
N
Y
Y
Y
[R-6.4.6.1-001],
[R-6.4.6.1-004] of 3GPP TS 22.280 [2]
List of MCVideo users whose selected groups are authorized to be remotely changed
> MCVideo ID
Y
Y
Y
Y
[R-5.2.3.2-002],
[R-5.2.3.2-003] of 3GPP TS 22.281 [3]
Period after which MCVideo data on a MCVideo UE is to be deleted if no action is taken by an authorized MCVideo user
Y
Y
Y
Y
[R-5.2.6.2.2-004] of 3GPP TS 22.281 [3]
Maximum number of simultaneous video streams that can be received (see NOTE 3)
Y
Y
Y
Y
[R-5.2.6.2.2-005] of 3GPP TS 22.281 [3]
Authorisation to automatically receive video communications
Y
Y
Y
Y
[R-5.2.6.2.2-006] of 3GPP TS 22.281 [3]
Authorisation to automatically receive emergency video streams
Y
Y
Y
Y
[R-5.2.6.2.2-007] of 3GPP TS 22.281 [3]
Authorisation to automatically receive imminent peril video streams
Y
Y
Y
Y
[R-5.2.6.2.2-008] of 3GPP TS 22.281 [3]
List of MCVideo groups for which video can be automatically/mandatorily received
> MCVideo group IDs
Y
Y
Y
Y
[R-5.2.7.2-001] of 3GPP TS 22.281 [3]
Authorisation to request to override an active MCVideo transmission
Y
Y
Y
Y
[R-5.2.7.2-002] of 3GPP TS 22.281 [3]
Authorisation to select MCVideo transmissions that can be overridden
Y
Y
Y
Y
[R-5.2.7.2-004] of 3GPP TS 22.281 [3]
Authorisation to allow MCVideo private communications to override or not to override active MCVideo group communications
Y
Y
Y
Y
[R-5.2.8-005],
[R-5.2.8-006] of 3GPP TS 22.281 [3]
Maximum length of time of a single video transmission
Y
Y
Y
Y
[R-6.7.3-007a] of 3GPP TS 22.280 [2]
List of user(s) from which MCVideo private calls can be received
> MCVideo ID
Y
Y
Y
Y
> Presentation priority relative to other users and groups
Y
Y
Y
Y
3GPP TS 33.180 [18]
> KMSUri for security domain of MCVideo ID
Y
Y
Y
Y
[R-5.9a-012] of 3GPP TS 22.280 [2]
[R-5.9a-013] of 3GPP TS 22.280 [2]
Authorised to request association between active functional alias(es) and MCVideo ID(s)
Y
Y
Y
Subclause 5.2.9 of 3GPP TS 23.280 [16]
List of partner MCVideo systems in which this profile is valid for use during migration
Subclause 5.2.9 of 3GPP TS 23.280 [16]
> Identity of partner MCVideo system
Y
N
Y
Y
Subclause 10.1.1 of 3GPP TS 23.280 [16]
> Access information for partner MCVideo system (see NOTE 5)
Y
N
Y
Y
[R-6.6.4.2-002a] and [R-6.6.4.2-002b] of 3GPP TS 22.280 [2]
List of groups the client affiliates/de-affiliates when criteria is met
> MCVideo Group ID
Y
Y
Y
Y
>> Criteria for affiliation (see NOTE 7)
Y
Y
Y
Y
>> Criteria for de-affiliation (see NOTE 7)
Y
Y
Y
Y
>> Manual de-affiliation is not allowed if the criteria for affiliation are met
Y
Y
Y
Y
[R-6.6.4.2-002] of 3GPP TS 22.280 [2]
List of groups the client affiliates after receiving an emergency alert
> MCVideo Group ID
Y
Y
Y
Y
>> Manual de-affiliation is not allowed if the criteria for affiliation are met
Y
Y
Y
Y
[R-5.9a-012] of 3GPP TS 22.280 [2]
Authorised to take over a functional alias from another MCVideo user
N
Y
Y
Y
List of functional alias(es) of the MCVideo user
[R-5.9a-005] of 3GPP TS 22.280 [2]
> Functional alias
Y
Y
Y
Y
[R-5.9a-018] of 3GPP TS 22.280 [2]
>> MCVideo server trigger criteria for activation (see NOTE 6)
N
Y
Y
Y
[R-5.9a-017], [R-5.9a-018] of 3GPP TS 22.280 [2]
>> MCVideo server trigger criteria for de-activation (see NOTE 6)
N
Y
Y
Y
[R-5.9a-019] of 3GPP TS 22.280 [16]
>> MCVideo client trigger criteria for activation (see NOTE 6)
Y
Y
Y
Y
[R-5.9a-019] of 3GPP TS 22.280 [16]
>> MCVideo client trigger criteria for de-activation (see NOTE 6)
Y
Y
Y
Y
>> Manual de-activation is not allowed if the criteria are met (see NOTE 6)
Y
Y
Y
Y
[R-5.10-001b] of 3GPP TS 22.280 [16]
Maximum number of successful simultaneous MCVideo service authorizations for this user (see NOTE 8)
N
Y
Y
Y
[R-5.9a-020] of 3GPP TS 22.280 [17]
List of functional aliases to which private calls are allowed when using a certain functional alias
> Used functional alias
Y
Y
Y
Y
>> List of functional aliases which can be called
>>> Functional alias
Y
Y
Y
Y
[R-5.9a-021] of 3GPP TS 22.280 [17]
List of functional aliases from which private calls can be received when using a certain functional alias
> Used functional alias
N
Y
Y
Y
>> List of functional aliases from which calls can be received
>>> Functional alias
N
Y
Y
Y
Ad hoc group call authorizations
[R-6.15.5.3-001] of 3GPP TS 22.280 [17]
> Authorised to initiate ad hoc group call
Y
Y
Y
Y
R-6.15.5.3-003] of 3GPP TS 22.280 [17]
> Authorised to participate in ad hoc group call
Y
Y
Y
Y
> Authorised to initiate emergency ad hoc group call
Y
Y
Y
Y
> Authorised to initiate imminent peril ad hoc group call
Y
Y
Y
Y
> Authorised to receive the participants information of ad hoc group call
N
Y
Y
Y
> Authorised to modify the list of participants and criteria for an ad hoc group call
Y
Y
Y
Y
> Authorised to release ongoing ad hoc group calls
Y
Y
Y
Y
NOTE 1: If this parameter is not configured, authorization to use the group shall be obtained from the identity management server identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [6].
NOTE 2: The use of this parameter by the MCVideo UE is outside the scope of the present document.
NOTE 3: The parameter can be set to an unlimited number of simultaneous streams received that can be received.
NOTE 4: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [6].
NOTE 5: Access information for each partner MCVideo system comprises the list of information required for initial UE configuration to access an MCVideo system, as defined in table A.6-1 of 3GPP TS 23.280 [16]
NOTE 6: The criteria may consist of conditions like the location of the MCVideo user, local time etc.
NOTE 7: The criteria may consist of conditions such as the location of the MCVideo user or the active functional alias of the MCVideo user.
NOTE 8: If configured, this value has precedence over the system level parameter "maximum number of successful simultaneous service authorisations" in table A.5-2. If not configured, the corresponding parameter from table A.5-2 shall be used.
NOTE 9: This is the recording admin UE and/or replay UE of a user who is authorized to set this MCVideo user as target for recording and/or authorized to replay this MCVideo user’s recordings.
Table A.3-3: MCVideo user profile configuration data (off network)
Reference
Parameter description
MCVideo UE
MCVideo Server
Configuration management server
MCVideo user database
[R-7.2-003],
[R-7.6-004] of 3GPP TS 22.280 [2]
List of off-network MCVideo groups for use by an MCVideo user
> MCVideo Group IDs
Y
N
Y
Y
> Application plane server identity information of group management server where group is defined
>> Server URI
Y
N
Y
Y
> Application plane server identity information of identity management server which provides authorization for group (see NOTE 1)
>> Server URI
Y
N
Y
Y
3GPP TS 33.180 [14]
> KMSUri for security domain of group (see NOTE 3)
Y
N
Y
Y
> Presentation priority of the group relative to other groups and users (see NOTE 2)
Y
N
Y
Y
[R-7.12-002],
[R-7.12-003] of 3GPP TS 22.280 [2]
Authorization for off-network services
Y
N
Y
Y
Subclause 7.18.1
User info id (as specified in 3GPP TS 23.303 [7])
Y
N
Y
Y
NOTE 1: If this parameter is not configured, authorization to use the group shall be obtained from the identity management server identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [6].
NOTE 2: The use of this parameter by the MCVideo UE is outside the scope of the present document.
NOTE 3: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [6].
A.4 MCVideo related Group configuration data
The general aspects of group configuration are specified in 3GPP TS 23.280 [6].
Parameters specified in table A.4-1 are child parameters of the MCVideo configuration parameter specified in table A.4-1 in 3GPP TS 23.280 [6]. Parameters specified in table A.4-2 are child parameters of the MCVideo configuration parameter specified in table A.4-2 in 3GPP TS 23.280 [6]. Parameters specified in table A.4-3 are child parameters of the MCVideo configuration parameter specified in table A.4-3 in 3GPP TS 23.280 [6].
Table A.4-1: Group configuration data (on and off network)
Reference
Parameter description
MCVideo UE
MCVideo Server
Group management server
[R-5.12-001] of 3GPP TS 22.280 [2]
>> Media confidentiality and integrity protection (see NOTE)
Y
Y
Y
[R-5.12-001] of 3GPP TS 22.280 [2]
>> Transmission control confidentiality and integrity protection (see NOTE)
Y
Y
Y
[R-5.12-001] of 3GPP TS 22.280 [2]
>> Group media protection security material (see NOTE)
Y
N
Y
[R-5.1.1.1-010] of 3GPP TS 22.281 [3]
>> List of allowed sets of video codecs and related information in order of preference
[R-5.1.1.1-010] of 3GPP TS 22.281 [3]
>>> Video codecs
Y
Y
Y
[R-5.1.1.1-010] of 3GPP TS 22.281 [3]
>>> List of allowed video resolution
>>>> Video resolutions
Y
Y
Y
[R-5.1.1.1-010] of 3GPP TS 22.281 [3]
>>> List of allowed video frame rates
>>>> Video frame rates
Y
Y
Y
[R-5.1.1.3.2-002] of 3GPP TS 22.281 [3]
>> Allowed video modes
>>> Urgent real time mode allowed
N
Y
Y
>>> Non-urgent real time mode allowed
N
Y
Y
>>> Non real time mode allowed
N
Y
Y
[R-5.1.1.3.2-002] of 3GPP TS 22.281 [3]
>> Active video mode (urgent real time mode, non urgent real time mode, non real time mode)
Y
Y
Y
[R-5.3.2.2-002] of 3GPP TS 22.281 [3]
>> Allowed maximum simultaneous MCVideo transmitting group members
N
Y
Y
NOTE: Security mechanisms are specified in 3GPP TS 33.180 [14].
Table A.4-2: Group configuration data (on network)
Reference
Parameter description
MCVideo UE
MCVideo Server
Group management server
[R-6.4.5-001],
[R-6.4.5-003] of 3GPP TS 22.280 [2]
>> Authorisation of a user to request a list of affiliated members of a group
Y
Y
Y
[R-5.1.7-002],
[R-6.2.2-001],
[R-6.6.2.2-006],
[R-6.8.7.2-003] of 3GPP TS 22.280 [2]
>> Priority of the group
N
Y
Y
[R-5.2.6.2.1-001] of 3GPP TS 22.281 [3], [R-5.2.1-001] of 3GPP TS22.280 [17]
>> List of group members which are allowed to transmit video (see NOTE)
>>> MCVideo ID
Y
Y
Y
NOTE: This parameter sets the authorization to transmit video in pre-arranged groups used in broadcast calls.
Table A.4-3: Group configuration data (off network)
Reference
Parameter description
MCVideo UE
MCVideo Server
Group management server
Subclause 7.7.2.1
>> Indication of whether the UE shall use single arbitrator approach or self arbitration approach.
Y
N
Y
[R-5.3.2.2-003] of 3GPP TS 22.281 [3]
>> Allowed maximum number of simultaneous transmissions (N9)
Y
Y
Y
Subclause 7.1.3
>> Default ProSe Per-Packet priority (as specified in 3GPP TS 23.303 [7]) values
>>> MCVideo group call signalling
Y
N
Y
>>> MCVideo group call media
Y
N
Y
>>> MCVideo emergency group call signalling
Y
N
Y
>>> MCVideo emergency group call media
Y
N
Y
>>> MCVideo imminent peril group call signalling
Y
N
Y
>>> MCVideo imminent peril group call media
Y
N
Y
A.5 MCVideo service configuration data
The general aspects of MC service configuration are specified in 3GPP TS 23.280 [6]. The MCVideo service configuration data is stored in the MCVideo server.
Tables A.5-1 and A.5-2 describe the configuration data required to support the use of on-network MCVideo service. Tables A.5-1 and A.5-3 describe the configuration data required to support the use of off-network MCVideo service. Data in table A.5-1 and table A.5-3 can be configured offline using the CSC-11 reference point.
Table A.5-1: MCVideo service configuration data (on and off network)
Reference
Parameter description
MCVideo UE
MCVideo Server
Configuration management server
[R-5.2.2-001] of 3GPP TS 22.280 [2]
Levels of group hierarchy for group-broadcast groups (Bc1)
Y
Y
Y
[R-5.2.3-001] of 3GPP TS 22.280 [2]
Levels of user hierarchy for user-broadcast groups (Bc2)
Y
Y
Y
[R-5.7-002] of 3GPP TS 22.280 [2]
Minimum length (Nc3) of an alphanumeric identifier (i.e. alias) assigned by an MCVideo administrator.
Y
N
Y
Table A.5-2: MCVideo service configuration data (on network)
Reference
Parameter description
MCVideo UE
MCVideo Server
Configuration management server
[R-5.12-001] of 3GPP TS 22.280 [2]
Protect confidentiality of signalling (see NOTE 1)
Y
Y
Y
[R-5.12-001] of 3GPP TS 22.280 [2]
Protect integrity of signalling (see NOTE 1)
Y
Y
Y
[R-5.12-001] of 3GPP TS 22.280 [2]
Use signalling protection between MCVideo servers (see NOTE 1)
N
Y
Y
[R-5.12-001] of 3GPP TS 22.280 [2]
Use transmission control protection between MCVideo servers (see NOTE 1)
N
Y
Y
[R-5.10-001a] of 3GPP TS 22.280 [2]
Maximum number of successful simultaneous service authorizations of clients from a user
N
Y
Y
List of functional alias identities
[R-5.9a-005] of 3GPP TS 22.280 [2]
> Functional alias
N
Y
Y
[R-5.9a-005] of 3GPP TS 22.280 [2]
>> Limit number of simultaneous activations
N
Y
Y
[R-5.9a-005] of 3GPP TS 22.280 [2]
>> This functional alias can be taken over
N
Y
Y
>> List of users who can activate this functional alias
[R-5.9a-005] of 3GPP TS 22.280 [2]
>>> MCVideo ID
N
Y
Y
[R-5.9a-016] of 3GPP TS 22.280 [2]
>> Communication priority (see NOTE 2)
N
Y
Y
Ad hoc group call configurations
[R-6.15.5.3-005] of 3GPP TS 22.280 [17]
> Support of ad hoc group call (enabled/disabled) (see NOTE 3)
Y
Y
Y
[R-6.15.5.3-002] of 3GPP TS 22.280 [17]
> Maximum number of participants allowed to participate in an ad hoc group call
Y
Y
Y
[R-6.15.5.3-004] of 3GPP TS 22.280 [17]
> Hang timer for ad hoc group call
N
Y
Y
> Maximum duration for ad hoc group call
Y
Y
Y
> List of preferred video codecs for ad hoc group call
Y
Y
Y
NOTE 1: Security mechanisms are specified in 3GPP TS 33.180 [14].
NOTE 2: The usage of this parameter by the MCVideo server is up to implementation.
NOTE 3: If the support for ad hoc group call is disabled by the MC system then all other configurations related to ad hoc group call are not applicable.
Table A.5-3: MCVideo service configuration data (off network)
Reference
Parameter description
MCVideo UE
MCVideo Server
Configuration management server
[R-7.6-001], [R-7.6-002], [R-7.6-003] of 3GPP TS 22.280 [2]
Default ProSe Per-Packet priority (as specified in 3GPP TS 23.303 [7]) values
> MCVideo private call signalling
Y
N
Y
> MCVideo private call media
Y
N
Y
> MCVideo Emergency private call signalling
Y
N
Y
> MCVideo Emergency private call media
Y
N
Y
Subclause 7.5.3.3
Periodicity interval (in seconds) of Capability announcement (see NOTE)
Y
N
Y
NOTE: If the value of the periodicity interval is set to zero, the capability announcement is not sent.
Annex B (informative):
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New
version
2016-04
Initial version.
0.0.0
2016-06
Implemented the following pCRs approved in SA6#11:
S6-160535, S6-160536, S6-160589
Title aligned with the title in MCVideo WID.
0.1.0
2016-08
Implemented the following pCRs approved in SA6#12:
S6-160800, S6-160805,S6-160881, S6-160882, S6-160931
0.2.0
2016-10
Implemented the following pCRs approved in SA6#13: S6-161155, S6-161166, S6-161226, S6-161227, S6-161233, S6-161234, S6-161235, S6-161236, S6-161237, S6-161239, S6-161240, S6-161241, S6-161264
0.3.0
2016-11
Implemented the following pCRs approved in SA6#14: S6-161461, S6-161464, S6-161465, S6-161468, S6-161469, S6-161473, S6-161474, S6-161476, S6-161479, S6-161481, S6-161482, S6-161483, S6-161485, S6-161497, S6-161566, S6-161567, S6-161568, S6-161569, S6-161570, S6-161574, S6-161575, S6-161585, S6-161588, S6-161599, S6-161600, S6-161601, S6-161602, S6-161603, S6-161608
0.4.0
2016-11
SA#74
SP-160877
Submitted for Approval at SA#74
1.0.0
2016-12
SA#74
SP-160877
MCC Editorial update for publication after TSG SA approval (SA#74)
14.0.0
2017-03
SA#75
SP-170070
0001
1
F
Alignment of definitions
14.1.0
2017-03
SA#75
SP-170070
0002
2
F
Alignment of group affiliation and de-affiliation requirements
14.1.0
2017-03
SA#75
SP-170070
0003
1
F
Alignment of bearer management
14.1.0
2017-03
SA#75
SP-170070
0004
2
F
Adding descriptive text for several general sections
14.1.0
2017-03
SA#75
SP-170070
0005
1
F
MCVideo call connect and disconnect on MBMS
14.1.0
2017-03
SA#75
SP-170070
0007
F
Alignment of business relationships, identities, and application of functional model to deployments
14.1.0
2017-03
SA#75
SP-170070
0008
1
F
Functional model update
14.1.0
2017-03
SA#75
SP-170070
0009
1
F
Location related description alignment
14.1.0
2017-03
SA#75
SP-170070
0010
1
F
Reception control at receiving participant
14.1.0
2017-03
SA#75
SP-170070
0011
1
F
Feedback between reception control and transmission control
14.1.0
2017-03
SA#75
SP-170070
0013
1
F
Activity status sharing
14.1.0
2017-03
SA#75
SP-170070
0014
1
F
Corrections to video push
14.1.0
2017-03
SA#75
SP-170070
0017
F
Obsolete editor's notes
14.1.0
2017-03
SA#75
SP-170070
0018
F
Response message
14.1.0
2017-03
SA#75
SP-170070
0020
1
F
Clarification on Editor's notes in subclause 7.3.3.2 in MCVideo
14.1.0
2017-03
SA#75
SP-170070
0021
1
F
Clarification on Editor's notes in MCVideo
14.1.0
2017-03
SA#75
SP-170070
0022
1
F
Clarification on transmission control
14.1.0
2017-03
SA#75
SP-170070
0023
D
Editorial corrections in MCVideo
14.1.0
2017-03
SA#75
SP-170070
0024
2
F
MCVideo configurations
14.1.0
2017-03
SA#75
SP-170070
0027
1
F
Addition of definition for MCVideo ID
14.1.0
2017-03
SA#75
SP-170070
0028
1
F
Correction of requirement reference for list of implicitly affiliated groups in MCVideo user profile config
14.1.0
2017-03
SA#75
SP-170070
0029
3
F
Off-network transmission arbitration
14.1.0
2017-06
SA#76
SP-170391
0042
1
F
Miscellaneous corrections to configuration
14.2.0
2017-06
SA#76
SP-170391
0043
5
F
Addition of identity management server address per group
14.2.0
2017-06
SA#76
SP-170391
0044
F
Clarifications on off-network group call answer response
14.2.0
2017-06
SA#76
SP-170391
0045
1
F
Clarifications on off-network group call procedure descriptions
14.2.0
2017-06
SA#76
SP-170391
0046
1
F
Clarifications on pre-conditions of group communication in off-network
14.2.0
2017-06
SA#76
SP-170391
0048
F
Remove Editor's Note on broadcast group communication in 23281
14.2.0
2017-06
SA#76
SP-170391
0049
F
Remove Editor's Note on Video details in Video pull and push in 23281
14.2.0
2017-06
SA#76
SP-170391
0050
2
F
Remove Editor's Note on Device ID used for Capabilities info request in 23281
14.2.0
2017-06
SA#76
SP-170391
0051
1
F
Remove Editor's Note on Clarifications for periodic capability announcements in 23281
14.2.0
2017-06
SA#76
SP-170391
0052
1
F
Some clarifications on off-network group call
14.2.0
2017-06
SA#76
SP-170391
0060
1
F
Editorial correction in chapter Release chat group call of MCVideo
14.2.0
2017-06
SA#76
SP-170391
0061
2
F
Inclusion of KMSUri to allow multiple security domains
14.2.0
2017-06
SA#76
SP-170391
0062
F
Addition of ProSe Per Packet Priority to group configuration
14.2.0
2017-06
SA#76
SP-170391
0063
1
F
Configuration for emergency alerts
14.2.0
2017-06
SA#76
SP-170391
0066
1
F
Video modes usage
14.2.0
2017-06
SA#76
SP-170391
0067
2
F
Communications remote control
14.2.0
2017-06
SA#76
SP-170391
0069
3
F
Alignment of MCVideo user profile configurations
14.2.0
2017-06
SA#76
SP-170391
0071
F
Corrections to Group configuration data for all MC services
14.2.0
2017-06
SA#76
SP-170395
0070
1
C
Resource Management in MCVideo
15.0.0
2017-09
SA#77
SP-170680
0072
1
A
CR on MCVideo capabilities information retrival and remote transmit media end
15.1.0
2017-09
SA#77
SP-170680
0075
2
A
MCVideo call connect
15.1.0
2017-09
SA#77
SP-170683
0077
3
B
Camera query
15.1.0
2017-09
SA#77
SP-170683
0078
4
B
Video capabilities sharing enhancement
15.1.0
2017-09
SA#77
SP-170683
0079
1
B
MCVideo emergency private call
15.1.0
2018-01
SA#78
SP-170895
0080
3
B
Functional model for MCVideo interconnection
15.2.0
2018-01
SA#78
SP-170888
0083
1
A
CR on clarification for MC service group ID
15.2.0
2018-01
SA#78
SP-170892
0084
4
B
Mutual adaption during MCVideo communication
15.2.0
2018-01
SA#78
SP-170892
0085
3
B
Renaming of MCVideo emergency group call cancel and correction to clause 7.1.2.5.1.3
15.2.0
2018-01
SA#78
SP-170892
0086
1
F
Adding implicit transmit media request IE to MCVideo emergency group call request
15.2.0
2018-01
SA#78
SP-170892
0087
1
F
Renaming of MCVideo "emergency condition"
15.2.0
2018-01
SA#78
SP-170888
0091
2
A
Rejection of group call request
15.2.0
2018-01
SA#78
SP-170888
0093
2
A
MCVideo server PSI configuration
15.2.0
2018-01
SA#78
SP-170892
0095
1
D
Correction of wrong "MCPTT" words
15.2.0
2018-01
SA#78
SP-170892
0097
1
F
Renaming of "MCVideo emergency state cancel" and other corrections
15.2.0
2018-04
SA#79
SP-180147
0099
1
A
Correction of security specification references
15.3.0
2018-04
SA#79
SP-180154
0100
2
B
User profile for MCVideo migration
15.3.0
2018-04
SA#79
SP-180152
0101
1
F
Update of references to stage 1 specifications
15.3.0
2018-04
SA#79
SP-180154
0103
B
Definition of MCVideo-3
15.3.0
2018-06
SA#80
SP-180366
0105
A
Clarification for presentation priority in MCVideo UE configuration
15.4.0
2018-12
SA#82
SP-181170
0111
2
A
MCVideo QCI update
15.5.0
2018-12
SA#82
SP-181180
0109
D
Spelling of ProSe
16.0.0
2019-03
SA#83
SP-190070
0114
1
A
Corrections to MCVideo Group join information flows and procedure
16.1.0
2019-03
SA#83
SP-190073
0116
1
F
Corrections to 'general' subclause for pre-arranged and chat group calls
16.1.0
2019-03
SA#83
SP-190073
0117
1
B
Late entry for MCVideo chat group call
16.1.0
2019-03
SA#83
SP-190073
0118
1
B
Procedure for MCVideo user leaving a group call
16.1.0
2019-06
SA#84
SP-190488
0119
1
B
Restricting incoming private communications
16.2.0
2019-06
SA#84
SP-190488
0120
2
B
User configuration for functional alias information query for MCVideo
16.2.0
2019-06
SA#84
SP-190488
0121
1
B
User requested priority in 23.281
16.2.0
2019-06
SA#84
SP-190488
0122
2
B
MCVideo configuration for functional alias
16.2.0
2019-06
SA#84
SP-190488
0123
3
B
Criteria based automatic group affiliation and deaffiliation
16.2.0
2019-06
SA#84
SP-190488
0124
1
B
Add configuration data to support functional alias in MCVideo
16.2.0
2019-06
SA#84
SP-190488
0125
3
B
Add functional alias to MCVideo for video pull and push operations
16.2.0
2019-06
SA#84
SP-190488
0126
3
B
Add functional alias to MCVideo private calls
16.2.0
2019-06
SA#84
SP-190488
0127
4
B
Add functional alias to MCVideo group calls
16.2.0
2019-06
SA#84
SP-190484
0129
2
F
Remove the duplicated MCVideo server URI in UE configuration table
16.2.0
2019-06
SA#84
SP-190489
0130
2
F
Fix the missing parameters in the user profile configuration table
16.2.0
2019-06
SA#84
SP-190488
0131
B
MCVideo server limits the number of simultaneous successful service authorisations
16.2.0
2019-06
SA#84
SP-190488
0132
B
MCVideo client performs automatic activation and deactivation of functional aliases based on location
16.2.0
2019-09
SA#85
SP-190731
0133
3
F
Correct the configuration parameters for the MCVideo emergency alert procedures
16.3.0
2019-09
SA#85
SP-190732
0136
1
F
Fixing the user profile configuration data for criteria triggered functional alias activation and de-activation
16.3.0
2019-09
SA#85
SP-190735
0134
1
B
Communication priority for functional aliases
17.0.0
2019-12
SA#86
SP-191113
0137
2
B
Priority of the user
17.1.0
2019-12
SA#86
SP-191114
0138
1
F
Alignment on MCX emergency alert procedures
17.1.0
2020-03
SA#87-E
SP-200118
0139
3
B
Enhancing MCVideo communication requests with application priority capabilities in on-network mode
17.2.0
2020-03
SA#87-E
SP-200118
0140
2
F
Alignment of functional alias to group binding handling in MCVideo
17.2.0
2020-03
SA#87-E
SP-200118
0143
1
F
Adding missing server to server information flows for group calls
17.2.0
2020-03
SA#87-E
SP-200118
0144
1
F
Adding missing server to server information flows for private calls
17.2.0
2020-07
SA#88-E
SP-200340
0142
6
B
Introducing a functional alias as target address for private video calls
17.3.0
2020-09
SA#89-E
SP-200843
0145
1
F
Correction of private call setup procedures when using a functional alias as target address
17.4.0
2020-09
SA#89-E
SP-200846
0146
1
F
Add the IE of priority in Information flows for transmission control
17.4.0
2020-09
SA#89-E
SP-200843
0147
1
B
Limit the number of simultaneous logins on per user basis
17.4.0
2020-09
SA#89-E
SP-200846
0148
1
F
MCVideo emergency group call clarifications
17.4.0
2020-09
SA#89-E
SP-200846
0149
1
F
MCVideo emergency private call clarifications
17.4.0
2020-09
SA#89-E
SP-200846
0150
1
F
Clarifications on the use of ProSe in off-network MCVideo communications
17.4.0
2020-12
SA#90-E
SP-201000
0152
F
MCVideo pull and push corrections
17.5.0
2020-12
SA#90-E
SP-200994
0153
C
Call restrictions for normal private calls
17.5.0
2020-12
SA#90-E
SP-200990
0155
A
FA controlling role description in MCVideo
17.5.0
2020-12
SA#90-E
SP-200990
0157
A
FA management procedure in MCVideo
17.5.0
2021-06
SA#92-E
SP-210567
0158
F
Correction to MCVideo-5 reference point description
17.6.0
2021-12
SA#94-E
SP-211529
0159
1
B
Connection authorisation configuration data
18.0.0
2022-06
SA#96
SP-220476
0162
1
B
Allow the user to restrict the dissemination of the location information – MCVideo Configuration
18.1.0
2022-09
SA#97-E
SP-220924
0163
F
Private MCVideo call to a FA user
18.2.0
2022-09
SA#97-E
SP-220926
0164
C
Updating MCVideo private call end request information elements
18.2.0
2022-09
SA#97-E
SP-220924
0165
1
F
Auto-receive transmission mode for emergency call, imminent peril calls etc over unicast session
18.2.0
2023-03
SA#99
SP-230289
0168
2
B
User profile configuration data to support MCVideo ad hoc group emergency alerts
18.3.0
2023-03
SA#99
SP-230287
0171
2
C
Add location information in MCVideo group call message
18.3.0
2023-03
SA#99
SP-230287
0172
2
C
MCVideo user profile configuration parameters for location information
18.3.0
2023-03
SA#99
SP-230289
0173
1
B
Ad hoc group call feature for MCVideo
18.3.0
2023-06
SA#100
SP-230708
0174
1
B
Adds user profile data for allowing subsequent MCVideo communications after an adhoc group emergency alert
18.4.0
2023-06
SA#100
SP-230708
0175
1
B
Configuration for receiving the adhoc group emergency alert participants list notification (MCVideo)
18.4.0
2023-06
SA#100
SP-230708
0176
2
C
Correcting the ad hoc group communication criteria between multiple MCVideo systems
18.4.0
2023-06
SA#100
SP-230708
0177
B
Notifying authorized user about adhoc group participants list involving multiple MC systems - MCVideo
18.4.0
2023-06
SA#100
SP-230708
0178
1
B
Get user list Information flows for the ad hoc group call - MCVideo
18.4.0
2023-06
SA#100
SP-230708
0179
2
F
Correct MCVideo ad hoc group call information tables
18.4.0
2023-06
SA#100
SP-230708
0180
C
Addressing EN related to user configuration for ad hoc MCVideo communication
18.4.0
2023-06
SA#100
SP-230708
0181
1
B
Updates adhoc group call procedures for allowing a subsequent MCVideo call after an adhoc group emergency alert
18.4.0
2023-06
SA#100
SP-230708
0182
F
Corrections to ad hoc group call setup procedure involving multiple MC system
18.4.0
2023-09
SA#101
SP-230998
0184
1
F
Adding references on group definitions (MCVideo)
18.5.0
2023-09
SA#101
SP-231004
0187
F
Missing configuration for ad hoc group MCVideo call
18.5.0
2023-09
SA#101
SP-231004
0188
1
F
Missing pre-conditions and steps for ad hoc group MCVideo call
18.5.0
2023-09
SA#101
SP-231004
0189
1
F
Correcting configuration for ad hoc group MCVideo communication
18.5.0
2023-09
SA#101
SP-230999
0183
3
B
Clarifications on temporary and pre-arranged MCVideo Broadcast Groups
19.0.0
2023-09
SA#101
SP-230999
0185
1
B
Modify list of participants by changing the criteria during an ongoing MCVideo ad hoc group call (single MC system)
19.0.0
2023-12
SA#102
SP-231556
0190
2
B
Changing the criteria during an ongoing MCVideo ad hoc group call (multiple MC systems)
19.1.0
2023-12
SA#102
SP-231552
0195
2
A
Introducing transmission idle message for MCVideo
19.1.0
2023-12
SA#102
SP-231554
0197
2
B
Add Group communication handling with preconfigured regroup update procedures
19.1.0
2023-12
SA#102
SP-231556
0199
1
F
Configuration for authorising modification of ad hoc group call participants - mcvideo
19.1.0
2023-12
SA#102
SP-231556
0200
1
B
Configuration for authorising modification of ad hoc group emergency alert participants - mcvideo
19.1.0
2023-12
SA#102
SP-231558
0202
1
A
Configuration for authorising modification of ad hoc group emergency alert participants - mcvideo
19.1.0
2023-12
SA#102
SP-231558
0204
1
A
Correction to modification of ad hoc group call participants procedure - mcvideo
19.1.0
2023-12
SA#102
SP-231556
0206
1
F
Corrections on modifying the criteria during an ad hoc group call (MCVideo)
19.1.0
2023-12
SA#102
SP-231556
0208
1
B
Adhoc group call release by an authorized user (MCVideo)
19.1.0
2024-03
SA#103
SP-240314
0207
2
B
Change list of participants when criteria was used to setup the ad hoc group call (MCVideo)
19.2.0
2024-03
SA#103
SP-240304
0211
A
Correcting flow name for ad hoc gourp call in MCVideo
19.2.0
2024-06
SA#104
SP-240758
0222
1
A
Removal of GW MC service ID
19.3.0
2024-09
SA#105
SP-241224
0224
2
D
Correcting description of IEs in MCVideo ad hoc group call
19.4.0
2024-09
SA#105
SP-241224
0226
1
F
Update the pre-conditions of clause 7.19.3.1.4
19.4.0
2024-09
SA#105
SP-241224
0227
1
F
Resolve the EN in clause 7.19.3.1.3
19.4.0
2024-09
SA#105
SP-241224
0228
1
B
Migration during Ad hoc group call procedure
19.4.0
2024-12
SA#106
SP-241722
0228
1
B
Target MCVideo user configuration for recording
19.5.0
2024-12
SA#106
SP-241722
0230
1
C
Clarification for Location user profile for MCVideo
19.5.0
2024-12
SA#106
SP-241723
0232
1
C
Adding information elements to adhoc group call
19.5.0
2024-12
SA#106
SP-241723
0235
1
F
Update the ad-hoc group call modify procedures
19.5.0
2024-12
SA#106
SP-241707
0237
1
A
Resolving the ENs in 23.281
19.5.0
2024-12
SA#106
SP-241723
0235
1
B
MCVideo control plane user plane separation
19.5.0
2025-03
SA#107
SP-250212
0240
1
D
Editorial changes to TS23.281
19.6.0
2025-06
SA#108
SP-250605
0241
1
F
Correction of the description of procedure object
19.7.0
2025-06
SA#108
SP-250603
0242
F
Correction to A.3 MCVideo user profile configuration data
19.7.0
2025-06
SA#108
SP-250608
0245
1
A
Add statement to MCVideo ad hoc group communication about continuous updates to a group participant list based on criteria
19.7.0
2025-06
SA#108
SP-250604
0246
1
B
Ambient viewing alignments
20.0.0
2025-09
SA#109
SP-251056
0250
1
A
Resolving Editor’s Notes in the Rel-20 version of TS 23.281
20.1.0
2025-09
SA#109
SP-251065
0253
A
Corrections to IE tables with Result return
20.1.0
2025-09
SA#109
SP-251057
0256
A
Ambient viewing response IE corrections
20.1.0
|
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 1 Scope
| This document specifies the functional architecture, procedures and information flows needed to support the Mission Critical Data (MCData) services. MCData is a suite of services which utilizes the common functional architecture defined in 3GPP TS 23.280 [5] to support MC services over LTE including the common services core.
MCData services suite consists of the following sub-services:
- short data service (SDS);
- file distribution (FD);
- data streaming (DS); and
NOTE: Procedures for DS are not covered in the current specification.
- IP connectivity.
MCData features include:
- conversation management;
- transmission and reception control;
- communication release; and
- enhanced status.
The corresponding service requirements are defined in 3GPP TS 22.282 [3] and 3GPP TS 22.280 [2].
The present document is applicable primarily to MCData service using E-UTRAN access based on the EPC architecture defined in 3GPP TS 23.401 [4]. Certain application functions of the MCData service could also be supported via non-3GPP access networks but no additional functionality is specified to support non-3GPP access.
The MCData service can be used for public safety applications and also for general commercial applications e.g. utility companies and railways.
|
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.280: "Mission Critical Common Requirements (MCCoRe); Stage 1".
[3] 3GPP TS 22.282: "Mission Critical Data services".
[4] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[5] 3GPP TS 23.280: "Common functional architecture and information flows to support mission critical communication services; Stage 2".
[6] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[7] 3GPP TS 23.303: "Proximity-based services (ProSe); Stage 2".
[8] 3GPP TS 23.468: "Group Communication System Enablers for LTE (GCSE_LTE); Stage 2".
[9] 3GPP TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 2".
[10] 3GPP TS 23.002: "Network Architecture".
[11] 3GPP TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); stage 2".
[12] 3GPP TS 29.283: "Diameter data management applications".
[13] 3GPP TS 33.180: "Security of the Mission Critical Service".
[14] 3GPP TS 23.203: "Policy and charging control architecture".
[15] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
[16] 3GPP TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE); MB2 reference point; Stage 3".
[17] 3GPP TS 29.214: "Policy and charging control over Rx reference point".
[18] 3GPP TS 23.283: "Mission Critical Communication Interworking with Land Mobile Radio Systems; Stage 2".
[19] 3GPP TS 26.348: "Northbound Application Programming Interface (API) for Multimedia Broadcast/Multicast Service (MBMS) at the xMB reference point".
[20] 3GPP TS 29.116: "Representational state transfer over xMB reference point between content provider and BM-SC".
[21] 3GPP TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs".
[22] 3GPP TS 22.179: "Mission Critical Push to Talk (MCPTT); Stage 1".
|
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 3 Definitions, symbols and abbreviations
| |
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 3.1 Definitions
| For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
Auto-receive: A mechanism where data smaller than a configured size threshold are delivered to the receiving MCData client(s) from the MCData server i.e. without waiting for the receiving user to indicate a present need for the data.
Conversation identifier: A universally unique identifier that identifies a series of related MCData transactions.
Data stream: A sequence of data that is agnostic to any underlying media (e.g. audio, video, telemetry data), on which processing of data (e.g. semantic, syntactic, save or filter operation) can begin before all the content is received.
FD disposition: is one of "not downloaded" and "download completed".
Folder Identifier: A unique identifier that identifies a folder in the MCData message store
IP Data: Structured or unstructured payload that is transparent to the MCData transport service.
MCData client: An instance of an MC service client that provides the client application function for the MCData service.
MCData emergency communication: An MC service emergency group communication or MC service emergency private communication within the MCData service.
MCData group: An MC service group configured for MCData service.
MCData group affiliation: An MC service group affiliation for MCData.
MCData group communication: A one-to-many communication using an MCData service.
MCData group de-affiliation: An MC service group de-affiliation for MCData.
MCData ID: An instance of an MC service ID within the MCData service.
MCData imminent peril communication: An MC service imminent peril group communication within the MCData service.
MCData server: An instance of an MC service server that provides the server application function for the MCData service.
MCData service: A data communication service comprising at least one underlying generic capability (e.g. SDS, file distribution, data streaming) with strong security, high availability, reliability and priority handling to support applications for mission critical organizations and mission critical applications for other businesses and organizations (e.g. utilities, railways).
MCData UE: An MC service UE that can be used to participate in MCData services.
MCData user: An MC service user who is authorized for MCData services suite via an MCData UE.
Metadata: data associated with a transmitted or stored SDS, file or data stream, consisting of information from messages (e.g. MCData IDs, conversation ID) and other related information (e.g. size, type).
Object: An MCData communication information (such as a message or a file) that is stored in the MCData message store with its associated metadata.
Object identifier: A unique identifier that identifies an object stored in the MCData message store.
Reception control: A mechanism that allows the MCData service to regulate data reception to the receiving MCData clients.
Reply identifier: A reference to the original MCData transaction to which the current transaction is a reply.
SDS data: A payload with limited size and variable content type used in SDS transactions.
SDS disposition: is one of "undelivered", "delivered" and "read".
Standalone communication: A unidirectional one-to-one or group data communication completed after one transaction.
Transaction identifier: A unique identifier that identifies a MCData transaction within a conversation.
Transmission control: A mechanism that allows the MCData service to regulate data transmission requests from the sending MCData users, either prior to or after active sending from the MCData UE.
For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.280 [2] apply:
Mission Critical
Mission Critical Applications
Mission Critical Service
Mission Critical Organization
For the purposes of the present document, the following terms given in 3GPP TS 22.179 [22] apply:
Group-broadcast group
User-broadcast group
For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.282 [3] apply:
MCData system
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.280 [5] apply:
Ad hoc Group Communication
MC service client
MC service group
MC service group affiliation
MC service group de-affiliation
MC service ID
MC service server
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.203 [14] apply:
Dynamic PCC rule
|
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 3.2 Abbreviations
| For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
DS Data Streaming
E2EE End to End Encryption
FD File Distribution
ITSI Individual TETRA Subscriber Identity
LMR Land Mobile Radio
MC Mission Critical
MCData ID MCData user identity
PCC Policy and Charging Control
PCRF Policy and Charging Rules Function
QCI QoS Class Identifier
RSI Radio Set Identity
SDS Short Data Service
UM Unacknowledged Mode
|
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 4 Introduction
| The MCData service suite provides a set of generic capabilities and specific services to enable one-to-one and group data communications between MCData users.
The MCData architecture utilises the common functional architecture to support mission critical services over LTE defined in 3GPP TS 23.280 [5] and aspects of the IMS architecture defined in 3GPP TS 23.228 [6], the Proximity-based Services (ProSe) architecture defined in 3GPP TS 23.303 [7], the Group Communication System Enablers for LTE (GCSE_LTE) architecture defined in 3GPP TS 23.468 [8] defining MBMS support via the MB2 interface, the MBMS User Service architecture defined in 3GPP TS 26.348 [19], the Security of the Mission Critical Service in 3GPP TS 33.180 [13] and the PS-PS access transfer procedures defined in 3GPP TS 23.237 [9] to enable support of the MCData service.
The MCData UE primarily obtains access to the MCData service via E-UTRAN, using the EPS architecture defined in 3GPP TS 23.401 [4]. Certain application functions of MCData service can be accessed using MCData UEs via non-3GPP access networks.
The MCData system provides the function to support interworking with LMR systems defined in 3GPP TS 23.283 [18].
|
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 5 Architectural requirements
| |
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 5.1 Transmission control
| The MCData service supports the ability to transmit SDS messages automatically towards the selected recipient user (private communication) or members of the selected MCData group. The MCData server may still reject the sent message (e.g. if there is no authority to send).
For MCData types other than SDS using signalling control plane, the MCData service invokes a transmission request grant approach before data is permitted to be transmitted. The MCData service provides configurable limits for the maximum amount of data for and/or maximum amount of time that an MCData user can transmit in a single request, which may be configured by the MCData administrator.
For congestion control, related to transmission requests, the MCData service may perform the following:
- reject the data transmission requests and then shall notify the MCData user of the rejection;
- queue the data transmission requests; or
- at any time, withhold the permission to transmit data automatically.
The MCData service shall notify the transmitting MCData group member if there are no other MCData group members affiliated to the MCData group.
The MCData service supports the lossless communication, and it can be configured by the MCData administrator for the private communication and group communication. The lossless communication can be supported only if the user has a valid and active MCData message store account. If the lossless communication is configured for private communication and if the MCData communication cannot be delivered to the MCData user (e.g. if the recipient is not available at the time of data delivery or network congestion), it shall be made available to the MCData user by storing it in the MCData user's personal account in the MCData message store. If a MCData group is configured for lossless communication, all members of the selected MCData group shall receive the MCData communication, at a time dependent on affiliation status. An affiliated group member of this MCData group shall receive the MCData communication when they are sent. A group member that is not affiliated during MCData communication, the MCData communication shall be made available by storing it in the group member's personal account in the MCData message store. If a MCData group is not configured for lossless communication, only the affiliated members of the selected MCData group shall receive the MCData communication.
In order to support lossless communication, below are the conditions that needs to be satisfied:
- Lossless communication is provisioned
- MCData user has the valid MCData message store account
- Store communication into message store configuration parameter is enabled
- MCData user has requested to store the MCData communication into MCData message store
|
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 5.2 Reception control
| The MCData service shall support the ability to receive small amounts of data automatically. The MCData service may store data waiting for delivery in a temporary store, and notify availability to the receiving MCData users, i.e. deferred delivery. The data which is temporarily stored may be configured with "time to live" value, and subsequently, the data may be purged from the temporary store upon expiry of "time to live".
When a MCData user has an active MCData message store account and has activated lossless communication, the MCData service deferred delivery shall not be used when the user is offline.
The recipient individual user (private communication) or affiliated members of the MCData group(s) shall be notified of the list of available data either on request or periodically.
The MCData service shall provide a mechanism for the MCData user to select data to be downloaded from the list corresponding to the temporary store, subject to limitations such as expiry time and size.
The MCData service shall support the ability to automatically deliver files with a size less than a configured threshold value (i.e. auto-receive). The data size for auto-receive shall be configured by the MCData administrator.
|
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 5.3 Short Data Service capability
| The MCData service shall support SDS capability for one-to-one and group communications.
The SDS capability shall support messages with a maximum payload of at least 1000 bytes. The supported message types shall include text, binary, or hyperlinks. Multiple message types may be interleaved within in a single message payload. The payload shall support inclusion of location information of the sending MCData user, with or without user or application provided data.
The MCData service shall support messages to be sent over the signalling plane or the media plane.
The SDS capability shall allow for multiple related messages to be correlated and sequenced within the MCData service.
The MCData user shall be able to selectively request read and delivery receipt indication for the sent messages. The message delivery history information should be made available to an authorized MCData user.
The MCData service may support aggregation of disposition notifications when SDS messages are sent to multiple recipients.
|
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 5.4 File distribution capability
| The MCData service shall support distribution of files for one-to-one and group communications.
The MCData service shall allow the MCData user to send a file or a URL of a file to another MCData user. The source of the file can originate either from an MCData client or from a network functional entity. The generated URL shall be a reference to a stored file to allow for subsequent retrieval. The file storage policy may determine the availability of the file to be retrieved, and is subject to expiry time and size limitations.
When the file delivery request is set by the sending user to mandatory download, the MCData service shall proceed to deliver the file to the recipient when possible. The file distribution mechanisms shall support both unicast and broadcast delivery methods.
The MCData service shall support aggregation of download completed reports when files are distributed to multiple recipients.
The MCData service shall support mechanisms for detection and recovery of lost data. A receiving MCData client should be able to:
- detect and report when a transfer did not complete properly and request retransmission;
- identify and re-request the missing parts of an incompletely received file; and
- accept partial retransmissions and use them to reconstitute the original file.
When employing MBMS delivery:
- MCData may use the MB2 interface specified in 3GPP TS 23.468 [8]. See also Group Communication Delivery Method in 3GPP TS 26.346 [21]; or
- if MBMS user services and Download Delivery Method (see 3GPP TS 26.346 [21]) are utilized, MCData shall use the xMB interface specified in 3GPP TS 26.348 [19].
For the MBMS path, figure 5.4-1 shows both the MB2 and the xMB interfaces.
Figure 5.4-1 MCData on-network architecture showing the unicast and MBMS delivery paths
|
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 5.5 Data streaming capability
| The MCData service may support data streaming capability for one-to-one and group communications.
The MCData service may allow the MCData user to send a data stream or a URL of a data stream to another MCData user. The source of the data stream can originate either from an MCData client or from a network functional entity. For a data stream originating at a network functional entity, the data stream may be provided by an MCData user. The data streaming mechanisms shall support both unicast and broadcast delivery methods.
When the data streaming request is set to automatic reception, the MCData service may not require consent from the receiving MCData user.
The MCData user may be able to apply controls (i.e. start, stop, cancel) to the streams, and on a per recipient basis.
The stream may be terminated through an explicit user control (i.e. stop, cancel operation) or by reaching the end of the streamed content.
|
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 5.6 MCData group affiliation and MCData group de-affiliation
| MCData groups may be configured with one or more MCData sub-services (e.g. SDS, FD, DS) as specified within the MCData service. When an MCData user affiliates to an MCData group, the MCData user is affiliated to each of those MCData sub-services configured in the MCData group. The list of MCData sub-services configured for an MCData group shall be included in the MCData group configuration data.
MCData group affiliation shall be as specified in clause 5.2.5 of 3GPP TS 23.280 [5]. In addition, the following requirements shall be fulfilled by the MCData service for MCData users affiliated to MCData groups:
- MCData users receive notifications for participating in MCData sub-services and invitations for their affiliated MCData group(s).
- MCData users select an affiliated MCData group to initiate a new message, file distribution, data stream, etc.
- MCData users receive messages, files, data streams, enhanced status updates, etc, from their affiliated MCData group(s).
|
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 5.7 Conversation management
| The conversation management:
1. shall include a service indication for conversation management in each SDS and FD transaction.
2. may be comprised of SDS transactions or FD transactions or a combination of both.
3. shall include a conversation identifier in each SDS and FD transaction.
4. shall treat conversation between different set of users (either in one-to-one or group) as a separate conversation.
5. shall treat conversation between the same set of users (either in one-to-one or group), but with a different conversation identifier as a separate conversation.
|
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 5.8 Bearer management
| |
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 5.8.1 General
| The MCData UE shall use the APNs as defined in subclause 5.2.7.0 and table A.6-1 of 3GPP TS 23.280 [5]. The MCData UE shall use the MC services APN as defined in subclause 5.2.7.0 and table A.6-1 of 3GPP TS 23.280 [5] for the SIP-1 reference point.
|
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 5.8.2 EPS bearer considerations
| The EPS bearer considerations specified in subclause 5.2.7.2 of 3GPP TS 23.280 [5] shall apply.
|
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 5.8.3 EPS unicast bearer considerations for MCData
| For an MCData session request, resources shall be requested utilising interaction with dynamic PCC. The MCData system shall request resources over Rx to a PCRF. The dedicated bearer for MCData media shall utilise the QCI value of 70 (as specified in 3GPP TS 23.203 [14]). The request of resources over Rx shall include an application identifier for MCData in order for the PCRF to evaluate the correct QCI.
The UE is required to support at minimum one bearer, which is used for MCData (see annex A in 3GPP TS 36.331 [15]).
Depending on operator policy, for media plane:
- the MCData system may be able to request modification of the priority (ARP) of an existing bearer without the need to initiate a new dedicated GBR bearer; or
- the allocation of EPS bearers of desired priority for MCData communications may cause the pre-emption of lower priority pre-emptible EPS bearers (for MCData or for other applications), if the maximum number of bearers or maximum traffic capacity has been reached, in favour of the newly initiated MCData EPS bearer. In this case, if the new EPS bearer to be used for MCData communication has higher priority level (ARP) than other bearer(s), is allocated with a capability to pre-empt other bearers and the other bearer(s) are pre-emptible, then the EPS bearer for MCData communication pre-empts one (or more) of the existing EPS bearer(s).
NOTE: Operator policy takes into account regional/national requirements.
The EPS bearer(s) for MCData emergency communications shall have highest priority level among MCData communication types. The EPS bearer(s) for MCData imminent peril communications shall have higher priority level than for normal MCData communications but lower than the priority level for MCData emergency communications.
|
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 5.8.4 MBMS bearer management
| The MBMS bearer management for MC services is specified in subclause 5.2.7.1 of 3GPP TS 23.280 [5].
|
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 5.9 Disposition
| Disposition requests and notifications can be sent "in-band" using the same mechanism used for transport of the data, or can be sent "out-of-band" when the mechanism used for transport of the data is no longer available.
For standalone SDS and FD, the MCData UE shall use the signalling plane for disposition request and disposition notifications. For session SDS, the MCData UE shall use:
- the media plane for disposition request and disposition notifications; and
- the signalling plane for disposition notifications when the media plane is no longer available.
|
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 5.10 MCData message store
| MCData message store is used by MCData users to store their MCData communications permanently; it shall provide secured storage area for each authorized MCData user having a user account. The storage area is identified by the MCData user's MCData ID. The MCData message store shall allow an MCData user to access only the storage area that he is authorized to access. A user (i.e. a dispatcher) other than the user account holder shall be able to access the account holder's storage area if authorized.
During an active MCData communication, the participating function on the MCData server of a MCData user participant shall, if the configuration to store the MCData communication is enabled for and if requested by the MCData user, deposit messages and files exchanged in the conversation to the MCData user's storage area in the MCData message store. When depositing the MCData communication into the MCData message store, if no such MCData user account is available on the MCData message store the MCData server shall create the user's account first and then deposit the MCData communications. The MCData message store shall support user account creation and deposit MCData communications operations from the MCData server after successful authentication and authorization. The MCData message store shall support the message store client to retrieve, update, delete, search and synchronize MCData communications stored in the MCData message store, after successful authentication and authorization.
The MCData user shall have an option if he wants to store the MCData communications in the MCData message store or not. Based on the request from MCData user, messages and files exchanged in an active MCData communication shall be stored as objects in the MCData message store. A stored object shall contain the following information:
1. The message or file itself; and
2. Associated metadata, consisting of:
a. information retrieved from the information elements of the message or file, such as MCData IDs, Conversation identifier etc.; and
b. other information, such as object identifier, content type (message or file), status ("seen", "received by", "read by ", "downloaded by " etc).
If a file is distributed indirectly with a URL in a message, when this message is stored in the MCData user's account in the MCData message store, it could be stored as:
1. an object as the original message with the URL; or
2. an object as the message with a revised URL that the URL indicates where the file, retrieved from the MCData content server, is stored separately in the MCData user's storage account. With proper security and authorization, this URL can be accessible by other network entities such as the MCData content server.
NOTE: It is the decision of SA3 on the mechanism to store an encrypted message or file in the MCData message store.
When a MCData user logs onto a UE with successful authentication and authorization and obtains the user service profile, the message store client on the UE shall synchronize with the user's account on the MCData message store, either automatically or manually (i.e. interacts with the user on which option to synchronize or no synchronization at all), before any MCData service starts.
|
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 5.11 IP connectivity (IPcon) capability
| IP connectivity service enables the exchange of IP Data using MCData transport service and provides the transport of IP Data for e.g. data hosts, servers, etc. that do not have mission critical communication capabilities. The exchange of IP Data is not limited in a transaction.
Figure 5.11-1: IP connectivity model
The corresponding MCData client enables bidirectional IP Data communication with the support of the IP connectivity service and thus forms the gateway to data hosts or servers. Therefore, the IP connectivity MCData client requests the MCData transport service with the associated QoS requirement and communication priority.
An authorised MCData client supporting IP connectivity capabilities is able to bar incoming IP connectivity requests either on demand or by providing a list of excluded origins identified by the MCData ID and, if available, by the functional alias.
For IP connectivity, the MCData server may support following limitation to exchange IP Data:
- limit the total data volume between the authorized MCData clients, divided by transmission and reception;
- max time limit, e.g. total minutes or allow exchange between predefined start and end time.
IP connectivity MCData service supports MCData transport services for one-to-one and group communication.
The IP address allocation necessary for user-IP connectivity MCData transport service is independent to the IP address allocation of the individual data hosts attached with the MCData client supporting IP connectivity capabilities. The required IP address pools for the user-IP connectivity MCData service are managed by the IP connectivity MCData transport service.
NOTE: IP connectivity service on interworking is not covered in the current specification.
|
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 5.12 MBMS user service architecture requirements
| The MBMS user service architecture offers a set of delivery methods to applications, specified in 3GPP TS 26.346 [21]. The MBMS download delivery method is used for the delivery of files over MBMS and provides reliability control by means of forward-error-correction.
The MCData File Distribution capability can use the MBMS download delivery method by including, in the MC service-on network architecture (subclause 5.2.6 from 3GPP TS 23.280 [5]), the MBMS user service architecture (3GPP TS 26.346 [21]), with the MCData server assuming the role of the content provider.
The MCData server may determine the MBMS broadcast area based on the cell identities of the affiliated group members received over GC1.
When the xMB interface is used, the MCData server uses the xMB mission critical extension, specified in 3GPP TS 26.348 [19] to control the QoS and the MBMS broadcast area of the MBMS user services. The MCData server also provides a file delivery manifest over xMB-C (see subclause 5.6.2 from 3GPP TS 26.348 [19]) describing the list of files to be broadcasted, and, for each file, the target completion date and the number of repetitions.
The MBMS user service metadata, which provides the delivery and schedule parameters, are returned to the MCData server after the MBMS session creation or update, under the form of a SA file (annex L.3A from 3GPP TS 26.346 [21]). The MCData server signals this SA file, together with the service id and the uri of the file to be received to the targeted MCData clients.
NOTE: Use of service announcement channel to deliver MBMS user service metadata is not covered in the current specification.
|
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 5.13 MBMS delivery via MB2 interface
| MBMS delivery via MB2 applies to MCData services that use media plane for user traffic delivery.
|
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 5.14 Delivery Notification
| A MCData user may request a delivery report (such as delivered, message read, or file downloaded etc.) when sending a MCData data (i.e. a message or a file). The recipient((s) shall respond with the proper delivery status response(s) (such as delivered, message read, or file downloaded etc.) according to what is requested in the delivery report. The sender of the MCData data may include multiple delivery status (such as delivered, message read, or file downloaded etc.) in the delivery report and the recipient(s) shall respond accordingly.
When the recipient is offline and receives a MCData data with request for delivery report, the delivery status response(s) shall follow one of the two principles below:
1. If the deferred delivery is used to deliver the MCData data, the delivery status response(s) shall be determined and responded by the recipient when the data is delivered. The MCData server may send a provisional delivery status report (such as the recipient is offline and the data will be delivered when the recipient is online or discarded due to timeout etc.) to inform the sender about the data delivery progress.
2. If the data is delivered with lossless communication, the MCData server shall respond with a delivered status report to the sender once the data is deposited into the recipient's MCData message store account. If the message read or file downloaded status is requested, the recipient shall respond it when the data is synced on the user device and processed by the recipient.
5A Involved business relationships
The description of the involved business relationships for the MCData service is contained in clause 6 of 3GPP TS 23.280 [5].
|
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 6 Functional model
| |
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 6.1 General
| This clause defines the functional model for MCData service.
The security solution for the MCData service, including end-to-end encryption, is specified in 3GPP TS 33.180 [13].
|
2dd96bf681de222af7ac92f0500fa2dd | 23.282 | 6.2 Description of the planes
| The functional model for the support of MCData is defined as a series of planes to allow for the breakdown of the architectural description.
The description of the planes and the relationship between the planes are contained in the common functional architecture to support MC services in 3GPP TS 23.280 [5].
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.