7.5 Capability information sharing
23.2813GPPFunctional architecture and information flows to support Mission Critical Video (MCVideo)Release 18Stage 2TS
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.
7.5.2 On-network capability information sharing
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.
7.5.2.2 Information flows for on-network capability information sharing
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.
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 |
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. |
||
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. Mulitple 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. |
||
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 |
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 |
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 |
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 |
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 a 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 a Update MCVideo capabilities info response indicating success or failure.
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.
Editor’s note: It is FFS for the case when the requesting MCVideo user is not within the same MCVideo system and the requested MCVideo users and the requested groups.
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.
7.5.3 Off-network capability information sharing
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.
7.5.3.2 Information flows for Off-network capability information sharing
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.) |
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 |
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 |
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 |
7.5.3.3 Periodic capability announcements
7.5.3.3.1 General
The MCVideo client periodically provides its video capability information to other members of the MCVideo group.
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.
7.5.3.4 Request capabilities from client(s)
7.5.3.4.1 General
The MCVideo client requests video capability information from other members of the MCVideo group.
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 criterions, 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 criteria, 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.
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.
7.5.3.5 Request activity status from client(s)
7.5.3.5.1 General
The MCVideo client requests activity status information from other members of the MCVideo group.
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 criterions, 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 a 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 criteria, 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.
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.