Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.281  Word version:  19.1.0

Top   Top   Up   Prev   Next
1…   5…   6…   7…   7.1.2.3…   7.1.2.3.1.2…   7.1.2.3.2…   7.1.2.4…   7.1.2.5.2…   7.1.3…   7.2…   7.2.2.3…   7.2.2.4…   7.2.3…   7.3…   7.4…   7.4.3…   7.5…   7.5.2.3…   7.6…   7.7…   7.7.1.3…   7.7.1.3.2A…   7.7.1.3.4…   7.7.1.3.6…   7.7.2…   7.7.2.7…   7.7.2.9…   7.8…   7.11…   7.17…   7.19…   7.19.2.8…   7.19.3…   7.19.3.1.4…   7.19.3.2…   7.19.3.2.3…   7.19.3.2.6…   A…

 

7.5.2.3  Update MCVideo capabilities information at the MCVideo serverp. 112

The procedure for updating the MCVideo capabilities information at the MCVideo server is described in Figure 7.5.2.3-1.
Reproduction of 3GPP TS 23.281, Fig. 7.5.2.3-1: Update MCVideo capabilities information at the MCVideo server
Up
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 clientp. 113

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.
Reproduction of 3GPP TS 23.281, Fig. 7.5.2.4-1: Retrieve MCVideo capabilities information by the MCVideo client
Up
Step 1.
The MCVideo client requests the MCVideo capabilities information by specifying some criteria (e.g. parameters, MCVideo ID).
Step 2.
The MCVideo server checks whether the user of the MCVideo client is authorized to retrieve the requested MCVideo capabilities information.
Step 3.
If authorized, the MCVideo server provides the requested MCVideo capabilities information to the MCVideo client.
Up

7.5.2.5  Subscription and notification for MCVideo capabilities informationp. 113

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.
Reproduction of 3GPP TS 23.281, Fig. 7.5.2.5-1: Subscription for MCVideo capabilities information
Up
Step 1.
The MCVideo client subscribes to the MCVideo capabilities information stored at the MCVideo server using the subscribe MCVideo capabilities info request.
Step 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.
Reproduction of 3GPP TS 23.281, Fig. 7.5.2.5-2: Notification of MCVideo capabilities information
Up
Step 1.
The MCVideo server provides the notification to the MCVideo client, who previously subscribed for the MCVideo capabilities information.
Step 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.
Up

7.5.3  Off-network capability information sharingp. 114

7.5.3.1  Generalp. 114

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.
Up

7.5.3.2  Information flows for Off-network capability information sharingp. 115

7.5.3.2.1  Capability requestp. 115
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).
Information Element Status Description
MCVideo IDMThe identity of the MCVideo user requesting the capabilities
MCVideo IDOThe identity of the MCVideo user towards whom the capability request was sent.
MCVideo group IDOThe MCVideo group ID towards which the request was sent
Search criteriaOA criteria filter for the capability request (e.g. category tags, video capabilities etc.)
Up
7.5.3.2.2  Capability announcementp. 115
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).
Information Element Status Description
MCVideo IDMThe identity of the MCVideo user announcing the capabilities
MCVideo IDOThe identity of the MCVideo user towards whom the capability announcement was sent.
MCVideo group IDOThe MCVideo group ID towards which the announcement was sent
Category tagsOCategory tags associated with a specific MCVideo UE or a video
Video capabilitiesOSet of video capabilities (e.g. codecs), camera capabilities (e.g. self-activated camera, wide field of view etc.)
LocationOThe location of the MCVideo user announcing the capabilities, if known
Up
7.5.3.2.3  Activity status requestp. 115
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).
Information Element Status Description
MCVideo IDMThe identity of the MCVideo user requesting the activity status
MCVideo IDOThe identity of the MCVideo user towards whom the activity status request was sent.
MCVideo group IDOThe MCVideo group ID towards which the activity status request was sent
Up
7.5.3.2.4  Activity status announcementp. 116
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).
Information Element Status Description
MCVideo IDMThe identity of the MCVideo user announcing the activity status
Activity statusMCurrent status of MCVideo UE's activities (e.g. receiving video, transmitting video, or recording video)
Video detailsODetails of the video like category tags or bit rate.
MCVideo IDOThe identity of the MCVideo user towards whom the activity status announcement was sent.
MCVideo group IDOThe MCVideo group ID towards which the activity status announcement was sent
Up

7.5.3.3  Periodic capability announcementsp. 116

7.5.3.3.1  Generalp. 116
The MCVideo client periodically provides its video capability information to other members of the MCVideo group.
7.5.3.3.2  Procedurep. 116
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.
Reproduction of 3GPP TS 23.281, Fig. 7.5.3.3.2-1: Periodic capability announcements
Up
Step 1.
MCVideo client 1 periodically sends a Capability announcement message, which contains its capability information with other relevant information.
Step 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.

7.5.3.4  Request capabilities from client(s)p. 117

7.5.3.4.1  Generalp. 117
The MCVideo client requests video capability information from other members of the MCVideo group.
7.5.3.4.2  Request clients with particular capabilitiesp. 117
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.
Reproduction of 3GPP TS 23.281, Fig. 7.5.3.4.2-1: Request clients with particular capabilities
Up
Step 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.
Step 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.
Step 3.
MCVideo clients, upon receiving a Capability announcement message from another MCVideo client, cache its presence and capability information along with other relevant information.
Up
7.5.3.4.3  Request capabilities from a particular clientp. 118
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.
Reproduction of 3GPP TS 23.281, Fig. 7.5.3.4.3-1: Request capabilities from a particular client
Up
Step 1.
MCVideo client 1 sends a Capability request message towards MCVideo client 2.
Step 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.
Step 3.
MCVideo client 1, upon receiving a Capability announcement message, caches MCVideo client 2's presence and capability information along with other relevant information.
Up

7.5.3.5  Request activity status from client(s)p. 119

7.5.3.5.1  Generalp. 119
The MCVideo client requests activity status information from other members of the MCVideo group.
7.5.3.5.2  Request activity status of group membersp. 119
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.
Reproduction of 3GPP TS 23.281, Fig. 7.5.3.5.2-1: Request activity status of group members
Up
Step 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.
Step 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.
Step 3.
MCVideo clients, upon receiving an activity status announcement message from another MCVideo client, cache its presence and activity status information.
Up
7.5.3.5.3  Request activity status from a particular clientp. 120
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.
Reproduction of 3GPP TS 23.281, Fig. 7.5.3.5.3-1: Request activity status from a particular client
Up
Step 1.
MCVideo client 1 sends an activity status request message towards MCVideo client 2.
Step 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.
Step 3.
MCVideo client 1, upon receiving an activity status announcement message, caches MCVideo client 2's presence and activity status information.

Up   Top   ToC