Content for TS 23.281 Word version: 19.6.0

1… 5… 6… 7… 7.1.2.3… 7.1.2.4… 7.1.3… 7.2… 7.2.3… 7.3… 7.4… 7.5… 7.6… 7.7… 7.7.1.3.5… 7.7.2… 7.8… 7.17… 7.19… 7.19.3… 7.19.3.1.4… 7.19.3.2… 7.19.3.2.5… A…

7.8 MCVideo service configuration 7.9 Affiliation and de-affiliation to/from MCVideo group(s) 7.9a Functional alias management 7.10 Use of MBMS transmission (on-network) 7.11 Simultaneous session for MCVideo calls (on-network) 7.12 User authentication and authorization for MCVideo service 7.13 Support for multiple devices 7.14 Location information (on-network) 7.15 MCVideo resource management (on-network) 7.16 MCVideo client query
...

7.8 MCVideo service configuration p. 161

The MCVideo service shall support the procedures and related information flows as specified in subclause 10.1 of TS 23.280 with the following clarifications:

The MC service client is the MCVideo client;
The MC service server is the MCVideo server;
The MC service ID is the MCVideo ID; and
The MC service user profile index is the MCVideo user profile index.

7.9 Affiliation and de-affiliation to/from MCVideo group(s) p. 161

The MCVideo service shall support the procedures and related information flows as specified in subclause 10.8 of TS 23.280 with the following clarifications:

The MC service client is the MCVideo client;
The MC service server is the MCVideo server;
The MC service group is the MCVideo group;
The MC service ID is the MCVideo ID; and
The MC service group ID is the MCVideo group ID.

When an MCVideo user has affiliated to an MCVideo group then the MCVideo user can send and receive MCVideo related media for that MCVideo group. When an MCVideo user has de-affiliated from an MCVideo group then the MCVideo user cannot send and receive MCVideo related media to and from that MCVideo group.

7.9a Functional alias management |R16| p. 162

The MCVideo service shall support the functional alias activation, de-activation, taken over, subscription and notification and functional alias to group binding procedures and related information flows as specified in subclause 10.13 of TS 23.280.

The MC service client is the MCVideo client;
The MC service server is the MCVideo server;
The MC service ID is the MCVideo ID.

7.10 Use of MBMS transmission (on-network) |R17| p. 162

7.10.1 Information flows for MBMS Transmission p. 162

7.10.1.1 General p. 162

Information flows for generic MBMS procedures are defined in TS 23.280.

7.10.1.2 MapGroupToBearer p. 162

Table 7.10.1.2-1 describes the information flow to associate a MCVideo group call to a MBMS bearer. It is sent from the MCVideo server to the MCVideo client.

Table 7.10.1.2-1: MapGroupToBearer

Information element	Status	Description
MCVideo group ID	M	This element identifies the MCVideo group, in which the call is started.
Media stream identifier (video)	M	This element identifies the media stream of the SDP used for the Video group call (e.g. MBMS subchannel).
Media stream identifier (audio)	O	This element identifies the audio media stream of the SDP used for the Video group call (e.g. MBMS subchannel). This is used if separate codecs are used for video and audio.
TMGI (see Note)	O	The MBMS bearer identifier if the media of the MCVideo group call is not sent on the same MBMS bearer as this MapGroupToBearer message.
Call acknowledgement indicator	O	Indication that the MCVideo group call requires acknowledgement from receiving MCVideo clients.
NOTE: TMGI shall be present if this message is sent over a different MBMS bearer than the media of the group call; TMGI may be present if this message is sent over the same MBMS bearer as the media of the group call.

7.10.1.3 UnmapGroupFromBearer p. 163

Table 7.10.1.3-1 describes the information flow to disconnect a MCVideo group call from a MBMS bearer. It is sent from the MCVideo server to the MCVideo client.

Table 7.10.1.3-1: UnmapGroupFromBearer

Information element	Status	Description
MCVideo group ID	M	This element identifies the MCVideo group which will no longer use the MBMS bearer.

7.10.2 Use of pre-established MBMS bearers p. 163

The MCVideo service shall support the procedure for using pre-established MBMS bearers as specified TS 23.280 with the following clarifications:

The MC service client is the MCVideo client;
The MC service server is the MCVideo server; and
The MC service ID is the MCVideo ID.

The MCVideo service shall use the MCVideo-1, MCVideo-8 and MCVideo-9 reference points for this procedure.

MCVideo may use pre-established MBMS bearer for the different types of MCVideo group calls. Both pre-arranged group calls and chat group calls can use the pre-established MBMS bearer for distributing the media. The MBMS bearer can be used by any group. Depending on the capacity of the MBMS bearer, the bearer can be used to broadcast one or more group calls in parallel.

Both the media packets as well as the transmission control messages to the receiving MCVideo clients are sent on the MBMS bearer. Optionally a separate MBMS bearer could be used for the transmission control messages, due to different bearer characteristic requirements.

When using the pre-established MBMS bearer for MCVideo, the MCVideo server perform the procedure of call connect and disconnect over MBMS as defined in subclause 7.10.4 at the group communication session establishment step.

7.10.3 Use of dynamic MBMS bearer establishment p. 163

The MCVideo service shall support the procedure for using dynamic MBMS bearers as specified TS 23.280 with the following clarifications:

The MC service client is the MCVideo client;
The MC service server is the MCVideo server; and
The MC service ID is the MCVideo ID.

The MCVideo service shall use the MCVideo-1, MCVideo-4, MCVideo-7, MCVideo-8 and MCVideo-9 reference points for this procedure.

MCVideo may use dynamic MBMS bearer establishment for the different types of MCVideo group calls. Both pre-arranged group calls and chat group calls can use the dynamic MBMS bearer for distributing the media.

Both the media packets as well as the transmission control messages to the receiving MCVideo clients are sent on the MBMS bearer.

When using the procedures for dynamic MBMS bearer establishment for MCVideo, the MCVideo server perform the procedure of mapping group communication to MBMS bearer as defined in subclause 7.10.4 at the group communication session establishment step.

7.10.4 Video call connect and disconnect over MBMS p. 164

7.10.4.1 General p. 164

MBMS bearer can be used for MCVideo group calls. One MBMS bearer is not permanently associated to one specific group or group call. Before sending media packets of a group call over MBMS bearer, the MCVideo server shall send the association information between group call and the MBMS bearer. The group call setup procedure indicates the media stream or media streams within one MBMS bearer that is used for the specific MCVideo group call. When the group call over the MBMS bearer is finished, this temporary association information of an MCVideo group call to specific resources on a MBMS bearer is undone. The procedure in Figure 7.10.4.2.1-1 requires that the group session is setup before the call start. This eliminates the need for the receiving clients to continuously use a unicast bearer. Prior to this the MBMS bearer is activated and announced to the MCVideo clients.

7.10.4.2 Procedure p. 164

7.10.4.2.1 Call connect over MBMS p. 164

In Figure 7.10.4.2.1-1 the MCVideo client 1 is the client that initiate an MCVideo chat group call and also the transmitting client. MCVideo client 1 may, but does not have to be in an MBMS service area. The MCVideo client 2 and MCVideo client 3 represents MCVideo clients receiving the MCVideo call over an MBMS bearer. There may be other receiving clients both over unicast bearers and over this or other MBMS bearer(s), however they are not illustrated in this Figure.

The same procedure as for chat group call can also be applied for pre-arranged calls.

Pre-conditions:

All users participating in the MCVideo group call are already affiliated to the group.
All participating users have joined the group session.

Reproduction of 3GPP TS 23.281, Fig. 7.10.4.2.1-1: Chat group call connect on MBMS bearer

Figure 7.10.4.2.1-1: Chat group call connect on MBMS bearer

Step 1.

Activation and announcement of MBMS bearer availability.

Step 2.

MCVideo client 1 initiate the MCVideo group call by sending an initial transmit media request over a unicast bearer to the MCVideo server (reference point MCVideo-4).

Step 3.

The MCVideo server will send a MapGroupToBearer message over a previously activated MBMS bearer to all users that will receive the call over an MBMS bearer. The MapGroupToBearer message includes association information between the group call and MBMS bearer. The MapGroupToBearer message includes MCVideo group ID and information about the media stream identifier or media stream identifiers of the activated MBMS bearer and may include the identifier (i.e. the TMGI) of the MBMS bearer broadcasting the call. The message is sent over reference point MCVideo-9.

Step 4.

The MCVideo server grants the right to transmit for MCVideo client 1 and by that sends a transmit media granted message to the MCVideo client 1. This message is sent over a unicast bearer (reference point MCVideo-4).

Step 5.

A media transmission notification message is sent from the MCVideo server to all receiving users. This message includes the MCVideo ID of the transmitting MCVideo client as well as the MCVideo group ID. The message is sent over a MBMS bearer to all users that have previously been setup to receive calls over the MBMS bearer. The message is sent over reference point MCVideo-9.

Step 6.

The users of MCVideo clients are informed about the details of video tranmission and the video transmitter.

Step 7.

The MCVideo clients may send a receive media request to the MCVideo server, to indicate the reception of media over the MBMS bearer.

Step 8.

MCVideo server accepts the media receive request and sends a receive media response message to MCVideo clients over a MBMS bearer by using reference point MCVideo-9.

Step 9.

The media is sent from MCVideo client 1 to the MCVideo server over unicast bearer and from the MCVideo server to the MCVideo client 2 and MCVideo client 3 over MBMS bearer.

7.10.4.2.2 Call disconnect over MBMS p. 165

Figure 7.10.4.2.2-1 shows the high level procedure where an UnmapGroupFromBearer message is sent by the MCVideo server to the MCVideo clients to indicate that the MCVideo group call is being dissociated from the MBMS bearer.

Reproduction of 3GPP TS 23.281, Fig. 7.10.4.2.2-1: Chat group call disconnect on MBMS bearer

Figure 7.10.4.2.2-1: Chat group call disconnect on MBMS bearer

Step 1.

An MCVideo group call is ongoing; the media is broadcasted over MBMS bearer to MCVideo client 2 and MCVideo client 3.

Step 2.

MCVideo server has determined to disconnect the call over the MBMS bearer for the MCVideo clients

Step 3.

An UnmapGroupFromBearer message is sent by the MCVideo server to MCVideo client 2, MCVideo client 3 and possibly to MCVideo client 1 (if in MBMS coverage area) on MBMS bearer(s).

7.10.5 Switching from MBMS bearer to unicast bearer p. 166

The MCVideo service shall support the procedure for switching from MBMS bearer to unicast bearer as specified TS 23.280 with the following clarifications:

The MC service client is the MCVideo client;
The MC service server is the MCVideo server; and
The MC service ID is the MCVideo ID.

The MCVideo service shall use the MCVideo-1, MCVideo-4, MCVideo-7, MCVideo-8 and MCVideo-9 reference points for this procedure.

7.11 Simultaneous session for MCVideo calls (on-network) p. 166

An MCVideo client and MCVideo server may use a simultaneous session as defined in TS 23.280 for MCVideo calls. The MCVideo client becomes involved in a simultaneous session for MCVideo calls by inviting, joining or accepting more than one MCVideo call, or affiliating to a group.

The MCVideo client can also still handle multiple MCVideo calls in parallel at the same time i.e. using multiple dialogs.

The simultaneous session is established during either an originating on-demand call establishment or during pre-established session establishment or a modification of an already established pre-established session or on-demand call.

It is possible to change the prioritisation while the MCVideo client is engaged in multiple MCVideo calls. The setting of the priority can be made at MCVideo call setup or by performing a modification after the MCVideo call is established. This may result in more than one media bearer.

7.12 User authentication and authorization for MCVideo service p. 166

A procedure for user authentication is illustrated in Figure 7.12-1. The user authentication is performed based on the procedure specified in TS 23.280.

Reproduction of 3GPP TS 23.281, Fig. 7.12-1: MCVideo user authentication and registration, single domain

Figure 7.12-1: MCVideo user authentication and registration, single domain

Step 1.

The user authentication is performed as per the general user authentication procedure specified in TS 23.280.

Step 2.

MCVideo client performs the MCVideo service authorization for the user. Step 2 utilizes the results of step 1.

7.13 Support for multiple devices p. 167

An MCVideo user may be authorized to use the MCVideo service from multiple MCVideo UEs as per the procedure in subclause 7.12.

If an MCVideo server receives a service authorization request for an MCVideo user who is previously MCVideo service authorized on another MCVideo UE, then the MCVideo server shall process this service authorization request as described in subclause 7.12. In the MCVideo service authorization response to the MCVideo user, the MCVideo server shall also indicate that the MCVideo user is already MCVideo service authorized from another MCVideo UE.

7.14 Location information (on-network) p. 167

The MCVideo system makes use of all of the procedures for location management as specified in TS 23.280, utilising the CSC-14 reference point between the location management client and location management server and the CSC-15 reference point between the MCVideo server and location management server.

The MC service client is the MCVideo client;
The MC service server is the MCVideo server;
The MC service group is the MCVideo group;
The MC service ID is the MCVideo ID; and
The MC service group ID is the MCVideo group ID.

7.15 MCVideo resource management (on-network) |R15| p. 167

Procedures for resource management are defined in subclause 10.11 of TS 23.280.

7.16 MCVideo client query |R15| p. 168

7.16.1 General p. 168

The MCVideo client query is used by an authorized MCVideo client to retrieve the characteristics of the MCVideo clients in an area with certain criteria. The query criteria may be a set of capabilities, or category tags, or a mix of such criterions, etc.

7.16.2 Information flows for MCVideo client query p. 168

7.16.2.1 MCVideo client query request p. 168

Table 7.16.2.1-1 describes the information flow for the MCVideo client query request from MCVideo client to MCVideo sever.

Table 7.16.2.1-1: MCVideo client query request

Information element	Status	Description
MCVideo ID	M	The identity of the MCVideo user requesting MCVideo client query.
Location information	M	The location information where the query to be applied.
Query criteria	O	A criteria filter for the query (e.g. category tags, video capabilities, etc.).

7.16.2.2 MCVideo client query response p. 168

Table 7.16.2.2-1 describes the information flow for the MCVideo client query response from the MCVideo server to the MCVideo client.

Table 7.16.2.2-1: MCVideo client query response

Information element	Status	Description
MCVideo ID list	O	The MCVideo clients that fulfil the query criteria.

7.16.3 MCVideo client query procedure p. 168

Figure 7.16.3-1 describes the procedure for MCVideo client query in on-network. This procedure is applicable to query the MCVideo clients belonging to the same MCVideo system as the requesting MCVideo user.

Pre-conditions:

The video capabilities have been collected at MCVideo server during the update MCVideo capabilities information at the MCVideo server procedure in subclause 7.5.2.3.

Reproduction of 3GPP TS 23.281, Fig. 7.16.3-1: MCVideo client query procedure

Figure 7.16.3-1: MCVideo client query procedure

Step 1.

MCVideo client A sends a MCVideo client query request to the MCVideo server with certain search criteria.

Step 2.

MCVideo server checks whether the MCVideo user of MCVideo client A has the authorization to perform MCVideo client query. If success, MCVideo server retrieves the MCVideo clients that fulfils the search criteria. If MCVideo group ID list is included in the MCVideo client query request, MCVideo server retrieves the affiliated group members that fulfil the query criteria in each affiliated MCVideo group in the received MCVideo group ID list.

Step 3.

MCVideo server returns the MCVideo client query response to the MCVideo client A with the retrieved MCVideo clients.