hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.3.4.2 Request clients with particular capabilities
|
Figure 7.5.3.4.2-1 describes procedures for a mechanism to request other MCVideo clients having particular characteristics to share their capabilities.
MCVideo client sends a capability request message to other MCVideo clients with search criteria. The search criteria may include MCVideo user ID or MCVideo client ID or a set of capabilities or a particular category of capabilities, or a mix of such criteria, etc.
Upon receiving the capability request message, the MCVideo client that fulfils the search criteria responds to the received capability request message with a capability announcement message.
Pre-conditions:
1. Information for ProSe direct communications corresponding to the MCVideo group and its mapping to ProSe Layer-2 Group ID are pre-configured in MCVideo client 1.
2. MCVideo client 1 to MCVideo client N are members of the same MCVideo group.
Figure 7.5.3.4.2-1: Request clients with particular capabilities
1. MCVideo client 1 sends a capability request message with search criteria to request MCVideo clients of the MCVideo group, with particular characteristics, to share their capabilities.
2. Upon receiving a capability request message with search criteria, all MCVideo clients which fulfil the search criteria respond with a Capability announcement message, which contains its capability information with other relevant information.
NOTE 1: If the capability request message does not contain a search criterion, all the MCVideo clients that receive the capability request message respond with a capability announcement message.
3. MCVideo clients, upon receiving a capability announcement message from another MCVideo client, cache its presence and capability information along with other relevant information.
NOTE 2: Capability announcement may include specific category tags (e.g. certain video camera), video capabilities of the client, location, camera angles, camera orientation, etc.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.3.4.3 Request capabilities from a particular client
|
Figure 7.5.3.4.3-1 describes procedures for a mechanism to request a particular MCVideo client in proximity, for its capabilities.
MCVideo client sends a capability request message to the other MCVideo client.
Upon receiving the capability request message, the MCVideo client responds to the received capability request message by sending a capability announcement message to the sender of the capability request message.
Pre-conditions:
1. Information for ProSe direct communications corresponding to the MCVideo client 2 is pre-configured in MCVideo client 1.
2. MCVideo client 1 has discovered MCVideo client 2 in proximity using ProSe Discovery procedures.
Figure 7.5.3.4.3-1: Request capabilities from a particular client
1. MCVideo client 1 sends a capability request message towards MCVideo client 2.
2. Upon receiving the capability request message, the MCVideo client 2 responds with a capability announcement message, which contains its capability information with other relevant information.
3. MCVideo client 1, upon receiving a capability announcement message, caches MCVideo client 2's presence and capability information along with other relevant information.
NOTE: Capability announcement may include specific category tags (e.g. certain video camera), video capabilities of the client, location, camera angles, camera orientation, etc.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.3.5 Request activity status from client(s)
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.3.5.1 General
|
The MCVideo client requests activity status information from other members of the MCVideo group.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.3.5.2 Request activity status of group members
|
Figure 7.5.3.5.2-1 describes procedures to request activity status of other MCVideo clients having particular characteristics.
MCVideo client sends an activity status request message to other MCVideo clients with search criteria. The search criteria may include MCVideo user ID or MCVideo client ID or a set of capabilities or a particular category of capabilities, or a mix of such critera, etc.
Upon receiving the activity status request message, the MCVideo client that fulfils the search criteria responds to the received activity status request message with an activity status announcement message.
Pre-conditions:
1. Information for ProSe direct communications corresponding to the MCVideo group and its mapping to ProSe Layer-2 Group ID are pre-configured in MCVideo client 1.
2. MCVideo client 1 to MCVideo client N are members of the same MCVideo group.
Figure 7.5.3.5.2-1: Request activity status of group members
1. MCVideo client 1 sends an activity status request message with search criteria to request MCVideo clients of the MCVideo group, with particular characteristics, to share their activity status.
2. Upon receiving an activity status request message with search criteria, all MCVideo clients which fulfil the search criteria respond with an activity status announcement message, which contains its activity status information.
NOTE: If the activity status request message does not contain a search criterion, all the MCVideo clients that receive the activity status request message respond with an activity status announcement message.
3. MCVideo clients, upon receiving an activity status announcement message from another MCVideo client, cache its presence and activity status information.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.5.3.5.3 Request activity status from a particular client
|
Figure 7.5.3.5.3-1 describes procedures to request a particular MCVideo client in proximity, for its activity status.
MCVideo client sends an activity status request message to the other MCVideo client.
Upon receiving the activity status request message, the MCVideo client responds to the received activity status request message by sending an activity status announcement message to the sender of the activity status request message.
Pre-conditions:
1. Information for ProSe direct communications corresponding to the MCVideo client 2 is pre-configured in MCVideo client 1.
2. MCVideo client 1 has discovered MCVideo client 2 in proximity using ProSe Discovery procedures.
Figure 7.5.3.5.3-1: Request activity status from a particular client
1. MCVideo client 1 sends an activity status request message towards MCVideo client 2.
2. Upon receiving the activity status request message, the MCVideo client 2 responds with an activity status announcement message, which contains its activity status information.
3. MCVideo client 1, upon receiving an activity status announcement message, caches MCVideo client 2's presence and activity status information.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.6 Ambient viewing call
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.6.1 General
|
The ambient viewing call is a type of a private MCVideo call that only allows a "viewed to" user to transmit media to a "viewing" user such that there is no indication on the MCVideo UE of the "viewed to" user about the call and the media transmission.
NOTE 1: "viewed to" user refers to the user who is transmitting media in an ambient viewing call.
NOTE 2: "viewing" user refers to the user who is receiving media in an ambient viewing call.
There are two types of ambient viewing call as below:
- Remotely initiated ambient viewing is initiated by the authorized user (e.g., dispatcher) who wants to view to another user. In this case, the "viewed to" user is the called party, and shall automatically accept the call without causing any indication about the call and transmit the media to the "viewing" user.
- Locally initiated ambient viewing is initiated by an authorized user who wants another user to view to the MCVideo UE communication. In this case, the "viewed to" user is the calling party and shall automatically transmit the media to the "viewing" user without causing any indication about the call processing and media transmission.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.6.2 Information flows for ambient viewing call
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.6.2.1 Ambient viewing call request
|
Table 7.6.2.1-1 describes the information flow for the ambient viewing call request from MCVideo client and MCVideo sever and MCVideo server to the MCVideo client.
Table 7.6.2.1-1: Ambient viewing call request
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the "viewing" user to view
MCVideo ID
M
The MCVideo ID of the "viewed to" user
SDP offer
M
Media parameters of MCVideo client.
Ambient viewing type
M
The ambient viewing type indicates remotely initiated ambient viewing call or locally initiated ambient viewing call.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.6.2.2 Ambient viewing call response
|
Table 7.6.2.2-1 describes the information flow ambient viewing call response from the MCVideo client to the MCVideo server and MCVideo server to the MCVideo client.
Table 7.6.2.2-1: Ambient viewing call response
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the "viewing" user
MCVideo ID
M
The MCVideo ID of the "viewed to" user
SDP answer
M
Media parameters
Ambient viewing type
M
The ambient viewing type indicates remotely initiated ambient viewing call or locally initiated ambient viewing call.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.6.2.3 Ambient viewing call release request
|
Table 7.6.2.3-1 describes the information flow ambient viewing call release request from the MCVideo client to the MCVideo server and MCVideo server to the MCVideo client.
Table 7.6.2.3-1: Ambient viewing call release request
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the "viewing" user
MCVideo ID
M
The MCVideo ID of the "viewed to" user
Ambient viewing type
M
The ambient viewing type indicates remotely initiated ambient viewing call or locally initiated ambient viewing call.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.6.2.4 Ambient viewing call release response
|
Table 7.6.2.4-1 describes the information flow ambient viewing call release response from the MCVideo client to the MCVideo server and MCVideo server to the MCVideo client.
Table 7.6.2.4-1: Ambient viewing call release response
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the "viewing" user
MCVideo ID
M
The MCVideo ID of the "viewed to" user
Ambient viewing type
M
The ambient viewing type indicates remotely initiated ambient viewing call or locally initiated ambient viewing call.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.6.2.5 Ambient viewing call release notification
|
Table 7.6.2.5-1 describes the information flow ambient viewing call release notification from the MCVideo server to the MCVideo client.
Table 7.6.2.5-1: Ambient viewing call release notification
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the user to view
MCVideo ID
M
The MCVideo ID of the user to be viewed to
Call release reason
M
The reason for call release by the MCVideo server
Ambient viewing type
M
The ambient viewing type indicates remotely initiated ambient viewing call or locally initiated ambient viewing call.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.6.3 Procedures
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.6.3.1 Remotely initiated ambient viewing call setup procedure
|
The MCVideo service provides the capability for an authorised user to initiate a remotely initiated ambient viewing call.
Figure 7.6.3.1-1 illustrates the high level procedure of remotely initiated ambient viewing call setup procedure.
Pre-conditions:
- MCVideo client 1 is the client of the authorized user who is authorized to invoke a remotely initiated ambience viewing call with MCVideo client 2.
- MCVideo user 1 is the "viewing" user at MCVideo client 1, and MCVideo user 2 is the "viewed to" user at MCVideo client 2.
Figure 7.6.3.1-1: Remotely initiated ambient viewing call setup
1. MCVideo client 1 initiates a remotely initiated ambient viewing call to MCVideo client 2 by sending an ambient viewing request to MCVideo server. The remotely initiated ambient viewing call type is included.
2. The MCVideo server performs an authorization check for the authorized user 1 for the remotely initiated ambient viewing call. If authorization fails, the MCVideo server provides a failure response to MCVideo client 1.
3. The MCVideo server sends the ambient viewing call request to MCVideo client 2.
4. MCVideo client 2 returns the ambient viewing call response to the MCVideo server.
5. MCVideo server provides an ambient viewing call response to MCVideo client 1, indicating that whether the remotely initiated ambient viewing call is set up successfully or not.
6. The transmission control server of the MCVideo server then sends a media transmit granted message to MCVideo client 2 according to the ambient viewing type received in step 1.
7. After receiving the media transmit granted message, the MCVideo client to be viewed to transmit video to the MCVideo client 1 for viewing.
NOTE: MCVideo client 2 does not provide any indication of the ambient viewing call release to its user.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.6.3.2 Locally initiated ambient viewing call setup procedure
|
The MCVideo service provides the capability for an authorised user to initiate a locally initiated ambient viewing call.
Figure 7.6.3.2-1 illustrates the high level procedure of locally initiated ambient viewing call setup procedure.
Pre-conditions:
- MCVideo client 2 is the client of the authorized user who is authorized to invoke a locally initiated ambient viewing call from MCVideo client 2.
- MCVideo user 1 is the "viewing" user at MCVideo client 1, and MCVideo user 2 is the "viewed to" user at MCVideo client 2.
Figure 7.6.3.2-1: Locally initiated ambient viewing call setup
1. MCVideo client 2 initiates a locally initiated ambient viewing call to MCVideo client 1 by sending an ambient viewing request to MCVideo server. The locally initiated ambient viewing call type is included.
2. The MCVideo server performs an authorization check for the authorized user 2 for the locally initiated ambient viewing call. If authorization fails, the MCVideo server provides a failure response to MCVideo client 2.
3. The MCVideo server sends the ambient viewing call request to MCVideo client 1.
4. MCVideo client 1 returns the ambient viewing call response to the MCVideo server.
5. MCVideo server provides an ambient viewing call response to MCVideo client 2, indicating that whether the locally initiated ambient viewing call is set up successfully or not.
6. The transmission control server of the MCVideo server then sends a media transmit granted message to MCVideo client 2 according to the ambient viewing type received in step 1.
7. After receiving the media transmit granted message, the MCVideo client to be viewed to, transmits video to the MCVideo client 1 for viewing.
NOTE: MCVideo client 2 does not provide any indication of the ambient viewing call release to its user.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.6.3.3 Ambient viewing call release – server initiated
|
Figure 7.6.3.3-1 illustrates the information flow for ambient viewing call release – server initiated when trigger by the MCVideo administrator. This procedure is applied for both remotely initiated ambient viewing call and the locally initiated ambient viewing call.
Pre-conditions:
- MCVideo client 1 is the MCVideo client of the authorized user, who initiated the ambient viewing call at MCVideo client 2.
- There is an ongoing ambient viewing call between MCVideo client 2 and MCVideo client 1.
- MCVideo user 1 is the "viewing" user at MCVideo client 1, and MCVideo user 2 is the "viewed to" user at MCVideo client 2.
Figure 7.6.3.3-1: Ambient viewing call release – server initiated
1. The ambient viewing call release criteria by the MCVideo administrator.
2. The MCVideo server sends an ambient viewing call release request to MCVideo client 2.
3. MCVideo client 2 stops transmitting media to MCVideo client 1.
NOTE: MCVideo client 2 does not provide any indication of the ambient viewing call release to its user.
4. MCVideo client 2 provides an ambient viewing call release response to the MCVideo server.
5. The MCVideo server sends an ambient viewing call release notification to MCVideo client 1 together with a reason code identifying that the call was released.
6. MCVideo client 1 notifies the authorized MCVideo user 1.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.6.3.4 Ambient viewing call release – "viewing" user initiated
|
Figure 7.6.3.4-1 illustrates the information flow for ambient viewing call release – "viewing" user initiated. This procedure is applied for both remotely initiated ambient viewing call and the locally initiated ambient viewing call.
Pre-conditions:
- MCVideo client 1 is the client of the authorized user, who is authorized to release the ambient viewing call at MCVideo client 2.
- There is an ongoing ambient viewing call between MCVideo client 2 and MCVideo client 1.
- MCVideo user 1 is the "viewing" user at MCVideo client 1, and MCVideo user 2 is the "viewed to" user at MCVideo client 2.
Figure 7.6.3.4-1: Ambient viewing call release – "viewing" user initiated
1. The authorized user 1 at MCVideo client 1 initiates the ambient viewing call release to MCVideo client 2 by sending an ambient viewing call release request to the MCVideo server.
2. The MCVideo server sends an ambient viewing call release request to MCVideo client 2.
3. MCVideo client 2 stops transmitting media to MCVideo client 1.
NOTE: MCVideo client 2 does not provide any indication of the ambient viewing call release to its user.
4. MCVideo client 2 provides an ambient viewing call release response to the MCVideo server.
5. The MCVideo server provides the ambient viewing call release response to MCVideo client 1.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.6.3.5 Ambient viewing call release – "viewed to" user initiated
|
Figure 7.6.3.5-1 illustrates the information flow for ambient viewing call release – "viewed to" user initiated. This procedure is only applied for the locally initiated ambient viewing call.
Pre-conditions:
- MCVideo client 2 is the client of the authorized user, who is authorized to release the locally initiated ambient viewing call at MCVideo client 2.
- There is an ongoing ambient viewing call between MCVideo client 1 and MCVideo client 2.
- MCVideo user 1 is the current user at MCVideo client 1 who is viewing, and MCVideo user 2 is the current user at MCVideo client 2 who is being viewed to.
Figure 7.6.3.5-1: Ambient viewing call release – "viewed to" user initiated
1. The authorized user 2 at MCVideo client 2 initiates the ambient viewing call release by sending an ambient viewing call release request to the MCVideo server.
2. The MCVideo server provides an ambient viewing call release request to MCVideo client 1.
3. MCVideo client 1 is notified about the ambient viewing call release.
4. MCVideo client 1 provides an ambient viewing call release response to the MCVideo server.
5. The MCVideo server provides the ambient viewing call release response to MCVideo client 2.
6. MCVideo client 1 stops transmitting media to MCVideo client 2.
NOTE: MCVideo client 1 does not provide any indication of the ambient viewing call release to its user.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7 Transmission control
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1 Transmission control for on-network MCVideo service
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.1 General
|
The procedure is for providing a transmission control to MCVideo UE in an on-network case and applies for both private call and group call. Transmission control is performed by using transmission control information flows between the transmission control participant and the transmission control server.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.2 Information flows for transmission control for on-network
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.2.1 General
|
When the transmission control server receives a transmit media request from the transmission control participant, it decides whether to give a grant or not. The result is informed to the requesting transmission control participant. When the transmission control participant receives a transmit media granted message, it can send video media over the uplink bearer established beforehand. The transmit media revoked message can be used as part of revoke. The transmit media queue status request can be used to know current position in the queue for media transmission.
Some transmission control information flows can also piggyback call control information flows to provide efficient call setup and clearing:
- Call setup request is optionally carried in transmit media request (uplink); and
- Call release request is optionally carried in media transmission release (uplink).
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.2.2 Transmit media request
|
Table 7.7.1.2.2-1 describes the information flow transmit media request, from the transmission control participant to the transmission control server, which is used to request the transmit media request. This information flow is sent in unicast to the transmission control server.
Table 7.7.1.2.2-1: Transmit media request
Information element
Status
Description
MCVideo ID
M
Identity of the user whose media transmission is requested
Media identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Media priority
O
Priority of the media
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.2.3 Transmit media granted
|
Table 7.7.1.2.3-1 describes the information flow transmit media granted, from the transmission control server to the transmission control participant, which is used to indicate that a transmit media request is granted and media transmission is possible. This information flow is sent in unicast (to the granted transmission control participant).
Table 7.7.1.2.3-1: Transmit media granted
Information element
Status
Description
Media 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 control participant is required
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.2.4 Transmit media rejected
|
Table 7.7.1.2.4-1 describes the information flow transmit media rejected, from the transmission control server to the transmission control participant, which is used to indicate that a transmit media request is rejected. This information flow is sent in unicast (to the refused transmission control participant).
Table 7.7.1.2.4-1: Transmit media rejected
Information element
Status
Description
Media 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 transmit media rejection
Acknowledgement required
O
Indicates if acknowledgement from the transmission control participant is required
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.2.5 Media transmission notification
|
Table 7.7.1.2.5-1 describes the information flow media transmission notification, from the transmission control server to the transmission control participant, which is used to indicate that a media transmission is available from another user. This information flow is sent in unicast (to the receiving transmission control participant).
Table 7.7.1.2.5-1: Media transmission notification
Information element
Status
Description
MCVideo ID
M
Identity of the user who is transmitting the media
Media identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Media reception mode (see NOTE)
M
Indicates the media reception mode (manual or forced).
NOTE: In the case of manual reception mode, to receive media, an explicit request from the user is required, whereas an explicit request is not required for the forced reception mode.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.2.6 Receive media request
|
Table 7.7.1.2.6-1 describes the information flow receive media request, from the transmission control participant to the transmission control server, which is used to request the reception of the media from another user. This information flow is sent in unicast (to the transmission control server).
Table 7.7.1.2.6-1: Receive media request
Information element
Status
Description
MCVideo ID
M
Identity of the user who is requesting the reception of the media
Source MCVideo ID
M
Identify of the user who is transmitting the media
Media identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.2.7 Receive media response
|
Table 7.7.1.2.7-1 describes the information flow receive media response, from the transmission control server to the transmission control participant, which is used to indicate whether the media reception is possible or not. This information flow is sent in unicast (to the receiving transmission control participant).
Table 7.7.1.2.7-1: Receive media response
Information element
Status
Description
Result
M
Indicates whether media reception is possible as per the request
Rejection cause
O
Indicates the cause for rejecting the media receive request
Media identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.2.8 Media reception notification
|
Table 7.7.1.2.8-1 describes the information flow media reception notification, from the transmission control server to the transmission control participant, which is used to indicate that a media reception has been initiated to a user. This information flow is sent in unicast (to the transmitting transmission control participant).
Table 7.7.1.2.8-1: Media reception notification
Information element
Status
Description
MCVideo ID
M
Identity of the user who is receiving the media
Media identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.2.9 Queue position info
|
Table 7.7.1.2.9-1 describes the information flow queue position info, from the transmission control server to the transmission control participant, which is used to indicate that the transmit media request is queued and the queue position to the transmit media requesting UE. The MCVideo server and the MCVideo client support queuing of the transmit media requests shall support this information flow. This information flow is sent in unicast (to the queued transmission control participant).
Table 7.7.1.2.9-1: Queue position info
Information element
Status
Description
Queue position info
M
Position of the queued transmit media request in the queue
Media 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 control participant is required
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.2.10 Transmission revoked
|
Table 7.7.1.2.10-1 describes the information flow transmission revoked, from the transmission control server to the transmission control participant, which is used to indicate that the on-going video transmission is queued and the queue position is provided or the on-going video transmission is terminated. This information flow is sent in unicast (to the queued transmission control participant).
Table 7.7.1.2.10-1: Transmission revoked
Information element
Status
Description
Revoke reason
M
The reason for revoke like queue or termination of on-going video transmission
Queue position info
O
(see NOTE 1)
Position of the queued transmit media request in the queue
Media identifier
O
(see NOTE 2)
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 control participant is required
NOTE 1: If revoke reason is queuing, then queue position info is included.
NOTE 2: If revoke reason is termination, then media identifier is included.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.2.11 Queue position request
|
Table 7.7.1.2.11-1 describes the information flow queue position request, from the transmission control participant to the transmission control server, which is used to request the position in the video transmission queue. The MCVideo server and the MCVideo client support queuing of the transmission control requests shall support this information flow. This information flow is sent in unicast to the transmission control server.
Table 7.7.1.2.11-1: Queue position request
Information element
Status
Description
Media identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.2.12 Transmit media cancel request
|
Table 7.7.1.2.12-1 describes the information flow transmit media cancel request, from the transmission control participant to the transmission control server. This information flow is sent in unicast to the transmission control server.
Table 7.7.1.2.12-1: Transmit media cancel request
Information element
Status
Description
MCVideo ID
M
Identity of the user whose media transmission is requested for cancellation
Media identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.2.13 Transmit media cancel response
|
Table 7.7.1.2.13-1 describes the information flow transmit media cancel response, from the transmission control server to the transmission control participant. This information flow is sent in unicast to the transmission control server.
Table 7.7.1.2.13-1: Transmit media cancel response
Information element
Status
Description
Media identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.2.14 Transmit media cancel request notify
|
Table 7.7.1.2.14-1 describes the information flow transmit media cancel request notify, from the transmission control server to the transmission control participant. This information flow is sent in unicast to the transmission control server.
Table 7.7.1.2.14-1: Transmit media cancel request notify
Information element
Status
Description
Media identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.2.15 Transmit media end request
|
Table 7.7.1.2.15-1 describes the information flow transmit media end request, from the transmission control participant to the transmission control server and from the transmission control server to the transmission control participant. This information flow is sent in unicast to the transmission control server/transmission control participant.
Table 7.7.1.2.15-1: Transmit media end request
Information element
Status
Description
MCVideo ID
M
Identity of the user whose media transmission is requested to be terminated.
Media identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.2.16 Transmit media end response
|
Table 7.7.1.2.16-1 describes the information flow transmit media end response, from the transmission control participant and the transmission control server and from the transmission control server to the transmission control participant. This information flow is sent in unicast to the transmission control server/transmission control participant.
Table 7.7.1.2.16-1: Transmit media end response
Information element
Status
Description
Media identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.2.17 Remote transmit media request
|
Table 7.7.1.2.17-1 describes the information flow remote transmit media request, from the transmission control participant to the transmission control server. This information flow is sent in unicast to the transmission control server.
Table 7.7.1.2.17-1: Remote transmit media request
Information element
Status
Description
MCVideo ID
M
Identity of the user who remotely initiated the media transmission of another user.
MCVideo ID
M
Identity of the user whose media transmission is requested
Media identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Media priority
O
Priority of the media
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.2.18 Remote transmit media response
|
Table 7.7.1.2.18-1 describes the information flow remote transmit media response, from the transmission control server to the transmission control participant. This information flow is sent in unicast to the transmission control participant.
Table 7.7.1.2.18-1: Remote transmit media response
Information element
Status
Description
Media identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.2.19 Remote transmit media end request
|
Table 7.7.1.2.19-1 describes the information flow remote transmit media end request, from the transmission control participant to the transmission control server. This information flow is sent in unicast to the transmission control server.
Table 7.7.1.2.19-1: Remote transmit media end request
Information element
Status
Description
MCVideo ID
M
Identity of the user whose media transmission is requested for cancellation
Media identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.2.20 Remote transmit media cancel response
|
Table 7.7.1.2.20-1 describes the information flow transmit media end response, from the transmission control server to the transmission control participant. This information flow is sent in unicast to the transmission control server.
Table 7.7.1.2.20-1: Remote transmit media end response
Information element
Status
Description
Media identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.2.21 Media reception end request
|
Table 7.7.1.2.21-1 describes the information flow media reception end request, from the transmission control server to the transmission control participant and from the transmission control participant to the transmission control server.
Table 7.7.1.2.21-1: Media reception end request
Information element
Status
Description
MCVideo ID
M
Identity of the user whose media receipt is requested for cancellation
Media identifier
M
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.2.22 Media reception end response
|
Table 7.7.1.2.22-1 describes the information flow media reception end response, from the transmission control server to the transmission control participant and from the transmission control participant to the transmission control server.
Table 7.7.1.2.22-1: Media reception end response
Information element
Status
Description
/Media identifier
M
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.2.23 Media reception override notification
|
Table 7.7.1.2.23-1 describes the information flow media reception override notification, from the transmission control server to the transmission control participant.
Table 7.7.1.2.23-1: Media reception override notification
Information element
Status
Description
MCVideo ID
M
Identity of the user who is requesting the reception of the media
MCVideo ID
O
Identify of the user of the overriding media
Media identifier
M
Identifies the communication of overriding media, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
MCVideo ID
O
Identify of the user of the overridden media
Media identifier
M
Identifies the communication of overridden media, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.2.24 Transmit media end notify
|
Table 7.7.1.2.24-1 describes the information flow transmit media end notify, from the transmission control server to the transmission control participant. This information flow is sent in unicast to the transmission control server.
Table 7.7.1.2.24-1: Transmit media end notify
Information element
Status
Description
MCVideo ID
M
Identity of the user whose media transmission has been released
Media identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.2.25 Transmission idle
|
Table 7.7.1.2.25-1 describes the information flow transmission idle from the transmission control server to the transmission control participant(s) during silent period (i.e., when no video transmission is ongoing). This information flow is sent over unicast or broadcast.
Table 7.7.1.2.25-1: Transmission idle
Information element
Status
Description
Media identifier
O
Identity of the communication, e.g., by identifying the media flow within a media multiplex, present only if media multiplexing
Acknowledgement required
O
Indicates if acknowledgment from the transmission control participant(s) is required
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.3 Transmission control within one MC system for MCVideo service
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.3.1 Transmission control during an MCVideo session
|
Figure 7.7.1.3.1-1 describes the procedure for transmission control between the transmission control participant and the transmission control server during an MCVideo session. 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.
Figure 7.7.1.3.1-1: Transmission control during an MCVideo session
1. Transmission control participant A wants to send video media over the session.
2. Transmission control participant A sends a transmit media request message to transmission control server which includes transmission priority and other information as necessary.
3. 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 transmit media request from transmission control participant A.
4. Transmission control server responds with a transmit media granted message (4a) to transmission control participant A. Transmission control server may send transmit media rejected message (4b) indicating the cause of rejection or queue position info message (4c) indicating that the transmit media request has been queued.
5. The transmit media granted shall cause the user of UE A where the transmission control participant A is located to be notified.
6. Transmission control participant A starts sending video media over the session established to the transmission control server.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.3.2 Reception control during an MCVideo session
|
Figure 7.7.1.3.2-1 describes the procedure for the reception control between the transmission control participant and the transmission control server during an MCVideo session. 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 has been granted the permission to transmit media.
Figure 7.7.1.3.2-1: Reception control during an MCVideo session
1. The transmission control server determines the reception mode for downlink transmission control participants for the media transmission permitted to transmission control participant A. The manual and forced reception modes are determined based on configurations (e.g. auto-receive video transmissions, auto-receive emergency video transmissions) as described in Annex A.
2. Transmission control server sends a media transmission notification message to the transmission control participant B including information about the video transmitter and the reception mode.
3. The receipt of the media transmission notification is used to inform the user of UE B the details of video transmission and the video transmitter.
4. Based on the notification received, the user of UE B may want take actions (receive, reject or cancel) regarding the media available for reception.
5. If user of UE B wants to receive the media or it required to receive the media via forced reception, it causes the transmission control participant B to send a media receive request message to the transmission control server.
6. Transmission control server makes the determination on what action (e.g., real-time stream downlink, make stream downloadable, reject) to take on the request based on reception control criteria (e.g., allowed simultaneous reception) and determines to accept the media receive request from transmission control participant B. Transmission control server will also determine the availability of the media at the server to initiate the downlink reception.
7. Transmission control server sends a receive media response message to transmission control participant B.
NOTE: Step 5 to 7 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.
8. Transmission control server sends video media to transmission control participant B.
9. Optionally, the transmission control server sends media reception notification message to transmission control participant A which includes the information about the video recipient (transmission control participant B).
7.7.1.3.2A End media reception – receiving user initiated
Figure 7.7.1.3.2A-1 describes the procedure for the receiving user-initiated media reception end. 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 has been granted the permission to transmit media.
Figure 7.7.1.3.2A-1: End media reception – receiving user initiated
1. The MCVideo user determines to end a receiving video stream.
2. The user sends a media reception end request including the video stream to be ended to the transmission control server.
3. The transmission control server returns a media reception end response.
4. Upon receiving the media reception end request, the transmission control server stops sending the video stream selected to the transmission control participant B.
5. If the end media reception at transmission control participant B causes the video transmission continuation condition to fail, then the transmission control server initiates the media transmission end procedure as described in subclause 7.7.1.3.6.2.
7.7.1.3.2B End media reception – transmission control server initiated
Figure 7.7.1.3.2B-1 describes the procedure for the transmission control server-initiated media reception end. 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 has been granted the permission to transmit media.
Figure 7.7.1.3.2B-1: End media reception – transmission control server initiated
1. The transmission control server determines to end a video stream transmitting to transmission control participant B according to events or configurations.
2. The transmission control server sends a media reception end request including the video stream to be ended to the transmission control participant B.
3. The MCVideo user is notified about the media reception end.
4. The transmission control participants B returns a media reception end response.
5. The transmission control server stops sending the video stream selected to the transmission control participant B.
6. If the end media reception at transmission control participants B causes the continuation conditions to fail, then the transmission control server initiates media transmission end procedure as described in subclause 7.7.1.3.6.2.
7.7.1.3.2C Reception control on overridden – mandatory mode
Figure 7.7.1.3.2C-1 describes the procedure for the reception control on overridden with mandatory mode that the transmission control server determines the video stream to be overridden. 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 has been granted the permission to transmit media.
Figure 7.7.1.3.2C-1: Reception control on overriding/overridden – mandatory mode
1. A new media stream is to be delivered to the transmission control participant B while the maximum number of simultaneous streams is reached. The transmission control server determines to override another media stream being received by the transmission control participant B accord to the media stream characteristics.
2. Transmission control server sends a media reception override notification message to the transmission control participant B including information about the video stream being overridden and stop the downlink delivery of the overridden video stream to the transmission control participant B. The overriding video stream information maybe also included.
3. The user of UE B is notified about the details of overriding/overridden.
4. The transmission control server initiates the media reception end procedure as described in subclause 7.7.1.3.2B. 5. The transmission control server performs the normal reception control procedure as described in subclause 7.7.1.3.2.
7.7.1.3.2D Reception control on overridden – negotiated mode
Figure 7.7.1.3.2D-1 describes the procedure for the reception control on overridden with negotiated mode that the transmission control participant determines the video stream to be overridden. 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 has been granted the permission to transmit media.
Figure 7.7.1.3.2D-1: Reception control on overriding/overridden – negotiated mode
1. A new media stream is to be delivered to the transmission control participant B while the maximum number of simultaneous streams is received. The transmission control server determines to override another media stream being received by the transmission control participant B according to the media stream characteristics.
2. Transmission control server sends a media transmission notification message to the transmission control participant B including information about the new video stream.
3. The user of transmission control participant B is notified about the maximum number of simultaneous streams received. The MCVideo user determines to reject the video stream or accept the video streaming by overriding a receiving video stream.
4. The transmission control participant initiates the media reception end procedure as described in subclause 7.7.1.3.2A.
5. Then the transmission control participant B requests to receive the new video stream as the normal reception control procedure described in subclause 7.7.1.3.2.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.3.3 Transmission revoke during an MCVideo session
|
Figure 7.7.1.3.3-1 describes the procedure for transmission revoke during an MCVideo session. 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 may be ongoing media transmission from transmission control participant B.
4. The maximum media transmission limit for the MCVideo session is reached.
Figure 7.7.1.3.3-1: Transmission revoke during an MCVideo session
1. Transmission control participant A wants to send video media over the session.
2. Transmission control participant A sends a transmit media request message to transmission control server which includes transmission priority and other information as necessary.
3. Transmission control server determines to accept the transmit media request from transmission control participant A and decides to pre-empt the on-going video transmission from transmission control participant B by queuing or ending the on-going video transmission.
4. Transmission control server responds with a transmission revoked message (4a) to transmission control participant B with the action of pre-emption whether queued or terminated. Transmission control server responds with a transmit media granted message (4b) to transmission control participant A.
5. The transmission revoked shall cause the transmission control participant B to be notified of the revoke (5a) of the on-going video transmission by queuing or termination. The transmit media granted shall cause the user of UE A where the transmission control participant A is located to be notified.
6. Transmission control participant A starts sending video media over the session established to the transmission control server.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.3.4 Queue position during an MCVideo session
|
Figure 7.7.1.3.4-1 describes the procedure where the transmission control is conducted for the MCVideo session already established between MCVideo clients (with transmit media granted to transmission control participant B) and server (with a revoke determination at transmission control server). Only two UEs involved in the session are shown for the simplicity.
Figure 7.7.1.3.4-1: Queue status during an MCVideo session
1. It is assumed that transmission control participant B has been granted permission to transmit media and is transmitting video media. There are several other transmission control participants (including transmission control participant A) requesting video transmission which get queued at the transmission control server.
2. Transmission control participant A would like to know its current position in the video transmission queue.
3. Transmission control participant A sends a queue position request message to the transmission control server.
4. Transmission control server determines the current queue position of transmission control participant A from the video transmission queue.
5. Transmission control server responds with the current position in queue position info message.
6. User at transmission control participant A is informed about the current queue position.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.3.5 Transmit media request cancellation from the video transmission queue
|
7.7.1.3.5.1 Transmit media request cancellation from the queue – MCVideo user initiated
Figure 7.7.1.3.5.1-1 illustrates the procedure for transmit media request cancellation from the video transmission queue initiated by the MCVideo user. The MCVideo user may be an authorized user who has rights to cancel the transmit media requests of other MCVideo users, whose transmit media requests are in video transmission queue.
Pre-conditions:
- It is assumed that transmission control participant B has been granted the permission for video transmission and is transmitting video. There are several other transmission control participants (including transmission control participant A and transmission control participant C) requesting the permission to transmit media which have been queued at the transmission control server.
Figure 7.7.1.3.5.1-1: Transmit media request cancellation from queue initiated by MCVideo user
1. The transmission control participant A wants to remove the transmit media request from the video transmission queue. If transmission control participant A is an authorized MCVideo user with the rights to cancel another MCVideo user's transmit media request, the authorized MCVideo user may request for transmit media request cancellation for one or more transmission control participants, whose transmit media request needs to be removed from the video transmission queue.
2. The transmission control participant A sends a transmit media cancel request (initiating MCVideo ID) message to the transmission control server. If the transmission control participant A wants to remove the transmit media request(s) of other participant(s), the target participant(s)' MCVideo ID should be included in this message.
3. The transmission control server shall check whether the requesting transmission control participant has authorization to cancel the transmit media request(s). If authorized, the transmit media request(s) will be removed from the video transmission queue. When the on-going transmissions are completed and are within the limit of the maximum simultaneous transmissions, the transmission control server will process the transmit media request from the updated video transmission queue.
4. If the transmit media cancel request in step 3 is sent by an authorized user (e.g., dispatcher) to cancel the transmit media request(s) of other participant(s) from the video transmission queue, the transmit media cancel request notify message is sent to the transmission control participant whose transmit media request was cancelled from the video transmission queue.
5. The transmission control server provides a transmit media cancel response to the transmission control participant A when the transmit media request cancellation is completed. Optionally, the new queue position information may be notified to the transmission control participants whose transmit media requests are in the video transmission queue (not shown in the figure).
7.7.1.3.5.2 Transmit media request cancellation from the queue - transmission control server initiated
Figure 7.7.1.3.5.2-1 illustrates the procedure for transmit media request cancellation from the queue initiated by the transmission control server. Only two UEs involved in the session are shown for the simplicity.
Pre-conditions:
- It is assumed that transmission control participant B has been granted the permission to transmit media and is transmitting video. There are several other transmission control participants (including transmission control participant A and participant C) requesting the permission to transmit media which have been queued at the transmission control server.
Figure 7.7.1.3.5.2-1: Transmit media request cancellation from queue initiated by transmission control server
1. The transmission control server removes the transmit media request from the video transmission queue based on policy. e.g., expiration of a timer. In the case when transmission control server receives repeated transmit media requests from a transmission control participant while the limit for maximum simultaneous media transmissions has reached, the new transmit media request is accepted and added into the video transmission queue and the existing/former transmit media request is removed from the video transmission queue or the new transmit media request is rejected and the existing/former transmit media request of this transmission control participant is retained in the video transmission queue.
2. The transmission control server sends a transmit media cancel request notify to the transmission control participant(s) whose transmit media request is removed from the video transmission queue.
3. Optionally, the new queue position information is notified to the other transmission control participants whose transmit media requests are queued.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.1.3.6 End a media transmission during an MCVideo session
|
7.7.1.3.6.1 End a media transmission – MCVideo user initiated
Figure 7.7.1.3.6.1-1 describes the procedure for ending a media transmission during an MCVideo session by a 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 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.1-1: End a media transmission by an MCVideo user
1. Transmission control participant A wants to end its media transmission in a session and sends a transmit media end request message to transmission control server.
2. Transmission control server terminates the on-going media transmission from transmission control participant A.
3. Transmission control server responds with a transmit media end response message to transmission control participant A indicating that the transmission control server has terminated the media transmission.
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 user.
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 sending user.
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.
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.
|
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.2 Off-network transmission control
| |
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.2.2 Information flows for off-network transmission control
| |
89176587a041225641da2ef55c9ebaf5
|
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
|
89176587a041225641da2ef55c9ebaf5
|
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
|
89176587a041225641da2ef55c9ebaf5
|
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
|
89176587a041225641da2ef55c9ebaf5
|
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
|
89176587a041225641da2ef55c9ebaf5
|
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
|
89176587a041225641da2ef55c9ebaf5
|
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
|
89176587a041225641da2ef55c9ebaf5
|
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
|
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.7.2.9 Transmission arbitration release
| |
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.10 Use of MBMS transmission (on-network)
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.10.1 Information flows for MBMS Transmission
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.10.1.1 General
|
Information flows for generic MBMS procedures are defined in 3GPP TS 23.280 [6].
|
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.10.4 Video call connect and disconnect over MBMS
| |
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.10.4.2 Procedure
| |
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
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].
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.16 MCVideo client query
| |
89176587a041225641da2ef55c9ebaf5
|
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.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.