hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.3.2 Information flows for off-network video push
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.3.2.1 Remote video push request
| Table 7.4.3.2.1-1 describes the information flow for the remote video push request sent from one MCVideo client to other MCVideo client(s).
Table 7.4.3.2.1-1: Remote video push request
Information element
Status
Description
MCVideo ID
M
The identity of the MCVideo user remotely requesting the video push
MCVideo ID
M
The identity of the MCVideo user from whom the video push is requested
Video information
O
Information identifying the video
MCVideo group ID
O
The MCVideo group ID to which the video is to be transmitted.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.3.2.2 Video push trying response
| Table 7.4.3.2.2-1 describes the information flow for the video push trying response sent from one MCVideo client to another MCVideo client.
Table 7.4.3.2.2-1: Video push trying response
Information element
Status
Description
MCVideo ID
M
The identity of the MCVideo user sending the trying response
MCVideo ID
M
The identity of the MCVideo user to whom the trying response is sent
MCVideo ID
M
The identity of the MCVideo user to whom the video is attempted
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.3.2.3 Notification of video push
| Table 7.4.3.2.3-1 describes the information flow for the notification of video push sent from one MCVideo client to another MCVideo client.
Table 7.4.3.2.3-1: Notification of video push
Information element
Status
Description
MCVideo ID
M
The identity of the MCVideo user sending the notification
MCVideo ID
M
The identity of the MCVideo user to whom the notification is sent
MCVideo ID
M
The identity of the MCVideo user to whom the video is pushed
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.3.3 Video push to another MCVideo user
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.3.3.1 General
| The MCVideo Push is the capability of a MCVideo user to push a video to another MCVideo user. A MCVideo user can push a video which is:
- being received by the MCVideo user from another a MCVideo client; or
- being recorded live on the MCVideo client.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.3.3.2 Procedure
| Figure 7.4.3.3.2-1 describes procedures for an off-network MCVideo video push, inititated by MCVideo client B with another MCVideo client C, to push a video received from MCVideo client A to MCVideo client C.
MCVideo client A or MCVideo client C or both can be autonomous MCVideo clients or can be human controlled MCVideo clients. In any such combination, following the procedure is followed.
MCVideo client A and MCVideo client B may belong to the same MCVideo user.
Pre-conditions:
1. MCVideo client A and MCVideo client B are engaged in MCVideo communication, where MCVideo client B is receiving media from MCVideo client A.
2. MCVideo user B has initiated MCVideo video push with MCVideo user C.
3. MCVideo client B and MCVideo client C are members of the same ProSe Discovery group and are ProSe 1:1 direct communication capable.
4. MCVideo client B has discovered MCVideo client C in proximity, associated with MCVideo user C, using ProSe Discovery procedures.
Figure 7.4.3.3.2-1: Off-network Video push to another MCVideo user
1. The MCVideo client B sends a Private communication request towards MCVideo client C. The Private communication request indicates that the request is for video push and contains the SDP offer.
2a. The MCVideo client C may notify the MCVideo user C about the MCVideo Push request (if the MCVideo client C is human controlled)
2b. The MCVideo client C automatically accepts the Private communication request for video push and sends a Private communication answer response to MCVideo client B. The Private communication answer response contains SDP answer.
NOTE 1: Step 2a and step 2b can occur in any order.
3a. If configured, the MCVideo client B notifies MCVideo client A about the video being pushed to MCVideo client C by sending a notification message to MCVideo client A.
3b. If configured, the MCVideo client A may notify the MCVideo user A about the video being pushed to MCVideo client C.
4. The MCVideo client B and MCVideo client C establish the media plane for communication.
5. Video being received by MCVideo client B from MCVideo client A is transmitted from MCVideo client B to MCVideo client C and presented to the MCVideo user C.
NOTE 2: If a MCVideo client fails to establish the communication, the MCVideo client should send a Private communication failed response indicating the failure reason to the appropriate MCVideo client(s).
NOTE 3: If a Private communication failed response is received by a MCVideo client, before or after establishing the media session, if already established, the session is terminated and the MCVideo user is notified about the failure and its reason, if any.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.3.4 Remotely initiated video push
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.3.4.1 General
| The MCVideo push is the capability of a MCVideo user to push a video from a second MCVideo user to a third MCVideo user.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.3.4.2 Procedure
| Figure 7.4.3.4.2-1 describes procedures for a remotely initiated off-network MCVideo video push, inititated by MCVideo user A at MCVideo client A with another MCVideo client B, to push a video to MCVideo client C.
MCVideo client B can be an autonomous MCVideo client or can be a human controlled MCVideo client. In either case, following procedure is followed.
Pre-conditions:
1. MCVideo user A has remotely initiated MCVideo video push with MCVideo user B.
2. MCVideo client A and MCVideo client B are members of the same ProSe Discovery group and are ProSe 1:1 direct communication capable.
3. MCVideo client A has discovered MCVideo client B in proximity, associated with MCVideo user B, using ProSe Discovery procedures.
Figure 7.4.3.4.2-1: Remotely initiated off-network video push
1. The MCVideo client A sends a Video push request towards the MCVideo client B. The Video push request indicates MCVideo client C as the intended recipient.
2a. The MCVideo client B checks whether there is on-going priviate communication with MCVideo client C. If there is on-going private communication with MCVideo client C, then step 3, step 4 and step 5 are skipped, else MCVideo client B enables ProSe layer to discover MCVideo client C as specified in subclause 7.2.3.
NOTE 1: MCVideo client A may provide the IP address of the MCVideo client C as part of the Video push request to the MCVideo B client. If such is the case, MCVideo client B does not require discovering MCVideo client C.
2b. The MCVideo client B notifies the MCVideo user B about the incoming Video push request (if MCVideo client B is human controlled).
2c. The MCVideo client B sends a video push trying response to MCVideo client A indicating that it is attempting to establish a connection with MCVideo client C,
NOTE 2: Step 2a, 2b and 2c can occur in any order.
3. Once the required details of MCVideo client C are obtained (either by discovery or from MCVideo client A) the MCVideo client B accepts the Video push request, and sends a Private communication request to MCVideo client C. The Private communication request indicates that the request was in response to the video push request from the MCVideo client A. The Private communication request contains the SDP offer.
4a. MCVideo client C sends a Private communication answer response to MCVideo client B in response to the Private communication request. The Private communication answer response contains the SDP answer.
4b: The MCVideo client C notifies MCVideo user C about the incoming Private communication request as an indication of incoming video.
NOTE 3: Step 4a and step 4b can occur in any order.
5. Upon receiving a Private communication answer response from the MCVideo client C, the MCVideo client B sends a notification message to the MCVideo client A indicating that MCVideo client C has accepted the request.
6. MCVideo client A notifies the MCVideo user A about the acceptance of the request by MCVideo client C (if the MCVideo client A is human controlled)
7. The MCVideo client B and the MCVideo client C establish the media plane for communication.
NOTE 4: If a MCVideo client fails to establish the communication, the MCVideo client should send a Private communication failed response indicating the failure reason to the appropriate MCVideo client.
8: Media is transmitted from MCVideo client B to MCVideo client C and presented to the MCVideo user C.
NOTE 5: If a Private communication failed response is received by a MCVideo client, before or after establishing the media session, if already established, the session is terminated and the MCVideo user is notified about the failure and its reason, if any.
NOTE 6: If the MCVideo client B fails to transmit the video to MCVideo client C, it should send a notification to MCVideo client A, indicating the reason.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.3.5 Remotely initiated video push to a group
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.3.5.1 General
| The MCVideo push is the capability of a MCVideo user to push a video from a second MCVideo user to a MCVideo group.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.3.5.2 Procedure
| Figure 7.4.3.5.2-1 describes procedures for an off-network remote video push request, initiated by MCVideo user A at MCVideo client A towards a MCVideo client B, to initiate a video push to MCVideo group G.
MCVideo client B can be an autonomous MCVideo client or can be a human controlled MCVideo client. In either case, following procedure should be followed.
Pre-conditions:
1. MCVideo client A and MCVideo client B are members of MCVideo group G.
2. MCVideo user A has initiated remote video push request with MCVideo user B to initiate a video push to MCVideo group G.
Figure 7.4.3.5.2-1: Remotely initiated video push to a group
1. MCVideo client A sends a remote video push request towards the MCVideo group. The remote video push request indicates MCVideo client B as the intended target of the request and MCVideo group G as the intended recipient.
2. Upon receiving the remote video push request as the intended target of the request, the MCVideo client B notifies the MCVideo user B of the remote video push request, if the MCVideo client B is human controlled. Other MCVideo group members notify their respective MCVideo users of the remote video push request.
3. The MCVideo client B automatically accepts the remote video push request and sends a group communication announcement message with video push indication towards the MCVideo group, as described in subclause 7.1.3.3. The group communication announcement message contains an SDP body and an indication that the group communication announcement is for video push.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5 Capability information sharing
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.1 General
| The MCVideo UE can store its capabilities information at the MCVideo server which can be retrieved by authorized users or MCVideo group members during on-network operations. The MCVideo UE can share their capabilities periodically or on-demand to another MCVideo UE or to MCVideo group members during off-network operations.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.2 On-network capability information sharing
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.2.1 General
| The MCVideo UE can store and update its capabilities information at the MCVideo server. Authorized MCVideo users or MCVideo group members can retrieve the capabilities information from the MCVideo server directly or via subscription and notification.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.2.2 Information flows for on-network capability information sharing
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.2.2.1 Update MCVideo capabilities info request
| Table 7.5.2.2.1-1 describes the information flow update MCVideo capabilities info request from the MCVideo client to the MCVideo server.
Table 7.5.2.2.1-1: Update MCVideo capabilities info request
Information element
Status
Description
MCVideo ID
M
Identity of the MCVideo user who is logged into the MCVideo UE
MCVideo capabilities
M
List of capabilities available at the MCVideo UE
NOTE: The device identification associated with MCVideo UE used for providing the MCVideo capabilities when the user logs on to multiple MCVideo UEs is specified by stage 3.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.2.2.2 Update MCVideo capabilities info response
| Table 7.5.2.2.2-1 describes the information flow update MCVideo capabilities info response from the MCVideo server to the MCVideo client.
Table 7.5.2.2.2-1: Update MCVideo capabilities info response
Information element
Status
Description
Result
M
Indicates success or failure
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.2.2.3 Get MCVideo capabilities info request
| Table 7.5.2.2.3-1 describes the information flow get MCVideo capabilities info request from the MCVideo client to the MCVideo server.
Table 7.5.2.2.3-1: Get MCVideo capabilities info request
Information element
Status
Description
MCVideo ID
M
Identity of the requesting MCVideo user
MCVideo ID list (see NOTE)
O
List of Identities of the target MCVideo users
MCVideo group ID list (see NOTE)
O
List of Identities of the target MCVideo groups
NOTE: At least one of the information elements shall be present.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.2.2.4 Get MCVideo capabilities info response
| Table 7.5.2.2.4-1 describes the information flow get MCVideo capabilities info response from the MCVideo server to the MCVideo client.
Table 7.5.2.2.4-1: Get MCVideo capabilities info response
Information element
Status
Description
Result
M
Indicates success or failure
MCVideo ID (see NOTE)
M
Identity of the MCVideo user whose MCVideo capabilities are requested
MCVideo capabilities (see NOTE)
M
List of capabilities available at the requested MCVideo user's UE
NOTE: The MCVideo capabilities correspond to the MCVideo ID. MCVideo ID and MCVideo capabilities information elements shall not be present if the Result is failure. Multiple pairs of MCVideoID and MCVideo capabilities information elements may be appended. Only the affiliated group members in the requested MCVideo group ID list are returned.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.2.2.5 Subscribe MCVideo capabilities info request
| Table 7.5.2.2.5-1 describes the information flow subscribe MCVideo capabilities info request from the MCVideo client to the MCVideo server.
Table 7.5.2.2.5-1: Subscribe MCVideo capabilities info request
Information element
Status
Description
MCVideo ID
M
Identity of the requesting MCVideo user
MCVideo ID
O
Identity of the target MCVideo user
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.2.2.6 Subscribe MCVideo capabilities info response
| Table 7.5.2.2.6-1 describes the information flow subscribe MCVideo capabilities info response from the MCVideo server to the MCVideo client.
Table 7.5.2.2.6-1: Subscribe MCVideo capabilities info response
Information element
Status
Description
Result
M
Indicates success or failure
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.2.2.7 Notify MCVideo capabilities info request
| Table 7.5.2.2.7-1 describes the information flow notify MCVideo capabilities info request from the MCVideo server to the MCVideo client.
Table 7.5.2.2.7-1: Notify MCVideo capabilities info request
Information element
Status
Description
MCVideo ID
M
Identity of the MCVideo user logged in at the target MCVideo UE
MCVideo capabilities
M
List of capabilities available at the target MCVideo user's UE
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.2.2.8 Notify MCVideo capabilities info response
| Table 7.5.2.2.8-1 describes the information flow notify MCVideo capabilities info response from the MCVideo client to the MCVideo server.
Table 7.5.2.2.8-1: Notify MCVideo capabilities info response
Information element
Status
Description
Result
M
Indicates success or failure
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.2.3 Update MCVideo capabilities information at the MCVideo server
| The procedure for updating the MCVideo capabilities information at the MCVideo server is described in figure 7.5.2.3-1.
Figure 7.5.2.3-1: Update MCVideo capabilities information at the MCVideo server
1. The MCVideo client sends an update MCVideo capabilities info request message to MCVideo server to update the capabilities information available at the MCVideo client
2. The MCVideo server stores the updated MCVideo capabilities information received from the MCVideo client.
3. The MCVideo server provides an update MCVideo capabilities info response indicating success or failure.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.2.4 Retrieve MCVideo capabilities information by the MCVideo client
| The procedure for retrieval of MCVideo capabilities information by the MCVideo client is described in figure 7.5.2.4-1.
Pre-conditions:
- The MCVideo server has received MCVideo capabilities information from MCVideo clients and has stored this information;
- The MCVideo user is authorized to access the MCVideo capabilities information from the MCVideo server.
- The requesting MCVideo user is within the same MCVideo system as the requested MCVideo users and the requested MCVideo groups.
Figure 7.5.2.4-1: Retrieve MCVideo capabilities information by the MCVideo client
1. The MCVideo client requests the MCVideo capabilities information by specifying some criteria (e.g. parameters, MCVideo ID).
2. The MCVideo server checks whether the user of the MCVideo client is authorized to retrieve the requested MCVideo capabilities information.
3. If authorized, the MCVideo server provides the requested MCVideo capabilities information to the MCVideo client.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.2.5 Subscription and notification for MCVideo capabilities information
| The procedure for subscription for MCVideo capabilities information as described in figure 7.5.2.5-1 is used by the MCVideo client to indicate to the MCVideo server that it wishes to receive updates of MCVideo capabilities information for which it is authorized.
Pre-conditions:
- The MCVideo server has some MCVideo capabilities information stored.
Figure 7.5.2.5-1: Subscription for MCVideo capabilities information
1. The MCVideo client subscribes to the MCVideo capabilities information stored at the MCVideo server using the subscribe MCVideo capabilities info request.
2. The MCVideo server provides a subscribe MCVideo capabilities info response to the MCVideo client indicating success or failure of the request.
The procedure for notification of MCVideo capabilities information as described in figure 7.5.2.5-2 is used by the MCVideo server to inform the MCVideo client that new or updated MCVideo capabilities information is available.
Pre-conditions:
- The MCVideo client has subscribed to the MCVideo capabilities information
- The MCVideo server has received and stored new or updated MCVideo capabilities information.
Figure 7.5.2.5-2: Notification of MCVideo capabilities information
1. The MCVideo server provides the notification to the MCVideo client, who previously subscribed for the MCVideo capabilities information.
2. The MCVideo client provides a notify MCVideo capabilities info response to the MCVideo server.
If the MCVideo server has notified the MCVideo client about new or updated MCVideo capabilities information through this procedure, the MCVideo client may then follow the procedure described in subclause 7.5.2.4 in order to retrieve that MCVideo capabilities information.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.3 Off-network capability information sharing
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.3.1 General
| Each MCVideo client within a MCVideo group needs to share its video capabilities with other members of the MCVideo group.
Video capability sharing can be done by sending information periodically as described in subclause 7.5.3.3 or on request as described in subclause 7.5.3.4.
The receiving MCVideo clients need to store and update the video capability information from the sharing MCVideo client.
Off-network video capability information sharing is based on ProSe capabilities as described in clause 7.18.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.3.2 Information flows for Off-network capability information sharing
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.3.2.1 Capability request
| Table 7.5.3.2.1-1 describes the information flow for the capability request sent from the MCVideo client to other MCVideo client(s).
Table 7.5.3.2.1-1: Capability request
Information Element
Status
Description
MCVideo ID
M
The identity of the MCVideo user requesting the capabilities
MCVideo ID
O
The identity of the MCVideo user towards whom the capability request was sent.
MCVideo group ID
O
The MCVideo group ID towards which the request was sent
Search criteria
O
A criteria filter for the capability request (e.g. category tags, video capabilities etc.)
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.3.2.2 Capability announcement
| Table 7.5.3.2.2-1 describes the information flow for the capability announcement sent from the MCVideo client to other MCVideo client(s).
Table 7.5.3.2.2-1: Capability announcement
Information Element
Status
Description
MCVideo ID
M
The identity of the MCVideo user announcing the capabilities
MCVideo ID
O
The identity of the MCVideo user towards whom the capability announcement was sent.
MCVideo group ID
O
The MCVideo group ID towards which the announcement was sent
Category tags
O
Category tags associated with a specific MCVideo UE or a video
Video capabilities
O
Set of video capabilities (e.g. codecs), camera capabilities (e.g. self-activated camera, wide field of view etc.)
Location
O
The location of the MCVideo user announcing the capabilities, if known
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.3.2.3 Activity status request
| Table 7.5.3.2.3-1 describes the information flow for the activity status request sent from the MCVideo client to other MCVideo client(s).
Table 7.5.3.2.3-1: Activity status request
Information Element
Status
Description
MCVideo ID
M
The identity of the MCVideo user requesting the activity status
MCVideo ID
O
The identity of the MCVideo user towards whom the activity status request was sent.
MCVideo group ID
O
The MCVideo group ID towards which the activity status request was sent
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.3.2.4 Activity status announcement
| Table 7.5.3.2.4-1 describes the information flow for the activity status announcement sent from the MCVideo client to other MCVideo client(s).
Table 7.5.3.2.4-1: Activity status announcement
Information Element
Status
Description
MCVideo ID
M
The identity of the MCVideo user announcing the activity status
Activity status
M
Current status of MCVideo UE's activities (e.g. receiving video, transmitting video, or recording video)
Video details
O
Details of the video like category tags or bit rate.
MCVideo ID
O
The identity of the MCVideo user towards whom the activity status announcement was sent.
MCVideo group ID
O
The MCVideo group ID towards which the activity status announcement was sent
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.3.3 Periodic capability announcements
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.3.3.1 General
| The MCVideo client periodically provides its video capability information to other members of the MCVideo group.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.3.3.2 Procedure
| Figure 7.5.3.3.2-1 describes procedures for periodic capability announcements.
Each MCVideo client periodically sends a Capability announcement messages to the MCVideo group. This Capability announcement message is received by all other members of MCVideo group members.
Upon receiving such a Capability announcement message, the MCVideo client stores/updates the information about the transmitting MCVideo client.
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.3.2-1: Periodic capability announcements
1. MCVideo client 1 periodically sends a Capability announcement message, which contains its capability information with other relevant information.
2. Other MCVideo clients, upon receiving a Capability announcement message from MCVideo client 1, cache its 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.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.3.4 Request capabilities from client(s)
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.3.4.1 General
| The MCVideo client requests video capability information from other members of the MCVideo group.
|
f0eca71f00e75c097184182e982221fd | 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.
|
f0eca71f00e75c097184182e982221fd | 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.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.3.5 Request activity status from client(s)
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.5.3.5.1 General
| The MCVideo client requests activity status information from other members of the MCVideo group.
|
f0eca71f00e75c097184182e982221fd | 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.
|
f0eca71f00e75c097184182e982221fd | 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.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.6 Ambient viewing call
| |
f0eca71f00e75c097184182e982221fd | 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.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.6.2 Information flows for ambient viewing call
| |
f0eca71f00e75c097184182e982221fd | 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.
|
f0eca71f00e75c097184182e982221fd | 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 (NOTE 1)
O
Media parameters
Ambient viewing type (NOTE 2)
O
The ambient viewing type indicates remotely initiated ambient viewing call or locally initiated ambient viewing call.
Result
M
It indicates the success or failure of the ambient viewing request
Reason (NOTE 2)
O
It indicates the reason of failure of ambient viewing request, e.g., due to the engagement of the "viewed to" user in MCVideo communication.
NOTE 1: This information element is included when the Result information element is success.
NOTE 2: This information element is included when the Result information element is failure.
|
f0eca71f00e75c097184182e982221fd | 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.
|
f0eca71f00e75c097184182e982221fd | 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.
|
f0eca71f00e75c097184182e982221fd | 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.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.6.3 Procedures
| |
f0eca71f00e75c097184182e982221fd | 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 in step 2a and the procedure ends.
Furthermore, the MCVideo server performs a check whether MCVideo client 2 is engaged in an MCVideo private or group communication. If MCVideo client 2 is engaged in a communication, an ambient viewing call response is sent to MCVideo client 1 in step 2a and the procedure ends.
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.
|
f0eca71f00e75c097184182e982221fd | 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.
- MCVideo client 2 is not engaged in an ongoing MCVideo private or group communication.
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.
|
f0eca71f00e75c097184182e982221fd | 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.
|
f0eca71f00e75c097184182e982221fd | 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.
|
f0eca71f00e75c097184182e982221fd | 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.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7 Transmission control
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.1 Transmission control for on-network MCVideo service
| |
f0eca71f00e75c097184182e982221fd | 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.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.1.2 Information flows for transmission control for on-network
| |
f0eca71f00e75c097184182e982221fd | 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).
|
f0eca71f00e75c097184182e982221fd | 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
|
f0eca71f00e75c097184182e982221fd | 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
|
f0eca71f00e75c097184182e982221fd | 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
|
f0eca71f00e75c097184182e982221fd | 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.
|
f0eca71f00e75c097184182e982221fd | 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
|
f0eca71f00e75c097184182e982221fd | 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
|
f0eca71f00e75c097184182e982221fd | 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
|
f0eca71f00e75c097184182e982221fd | 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
|
f0eca71f00e75c097184182e982221fd | 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.
|
f0eca71f00e75c097184182e982221fd | 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
|
f0eca71f00e75c097184182e982221fd | 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
|
f0eca71f00e75c097184182e982221fd | 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
|
f0eca71f00e75c097184182e982221fd | 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
|
f0eca71f00e75c097184182e982221fd | 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
|
f0eca71f00e75c097184182e982221fd | 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
|
f0eca71f00e75c097184182e982221fd | 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
|
f0eca71f00e75c097184182e982221fd | 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
|
f0eca71f00e75c097184182e982221fd | 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
|
f0eca71f00e75c097184182e982221fd | 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
|
f0eca71f00e75c097184182e982221fd | 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
|
f0eca71f00e75c097184182e982221fd | 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
|
f0eca71f00e75c097184182e982221fd | 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
|
f0eca71f00e75c097184182e982221fd | 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
|
f0eca71f00e75c097184182e982221fd | 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
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.1.3 Transmission control within one MC system for MCVideo service
| |
f0eca71f00e75c097184182e982221fd | 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.
|
f0eca71f00e75c097184182e982221fd | 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.
|
f0eca71f00e75c097184182e982221fd | 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.
|
f0eca71f00e75c097184182e982221fd | 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.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.1.3.5 Transmit media request cancellation from the video transmission queue
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 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).
|
f0eca71f00e75c097184182e982221fd | 23.281 | 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.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.7.1.3.6 End a media transmission during an MCVideo session
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 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.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.