hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.1.3.8.1 Emergency group communication
| The off-network emergency group communication is a special case of off-network (non-emergency) group communication as defined in subclause 7.1.3.2, subclause 7.1.3.3, subclause 7.1.3.4, subclause 7.1.3.5, subclause 7.1.3.6 and subclause 7.1.3.7. The following are modifications to the aforementioned subclauses to support MCVideo emergency group communications:
- As a pre-condition, the client initiating the emergency communication has previously been provisioned with an MCVideo group designated as the MCVideo emergency group. The MCVideo client initiates MCVideo emergency group communications on this group. Alternatively, the MCVideo client could have been provisioned for emergency behaviour on the selected MCVideo group.
- The group communication announcement contains an indication that the MCVideo group communication is to be an MCVideo emergency communication regardless of whether or not the MCVideo client is in communication. Group communication participants learn of the MCVideo group's in-progress emergency state from the indication.
- Every communication initiated by the MCVideo client will be an emergency communication while the MCVideo client is in MCVideo emergency state.
- The MCVideo client enters the MCVideo emergency state when initiating an MCVideo emergency communication or emergency alert. Only the MCVideo user of the MCVideo client can clear the client's local MCVideo emergency state.
- The MCVideo group in-progress emergency state is cancelled when the communication ends.
- The MCVideo user who initiated the emergency communication, or upgraded the group communication to emergency group communication, or an authorized user, may cancel the in-progress emergency state with an MCVideo emergency group communication cancel message. The message is sent to the MCVideo group.
- When the MCVideo group is no longer in the in-progress emergency state, every client returns the value of ProSe Per Packet Priority to its default value.
- An in-progress MCVideo group communication is upgraded to an emergency group communication when the periodic group communication announcement contains the emergency indicator.
- The value of ProSe Per Packet Priority is upgraded according to emergency state of MCVideo group communication.
- An MCVideo group communication upgraded to emergency group communication does not affect the state of other MCVideo communication(s) in the client.
- The MCVideo group remains in the in-progress emergency state until the emergency group communication ends or the in-progress emergency state is cancelled.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.1.3.8.2 MCVideo imminent peril
| The off-network imminent peril group communication is a special case of off-network (non-imminent peril) group communication as defined in subclause 7.1.3.2, subclause 7.1.3.3, subclause 7.1.3.4, subclause 7.1.3.5, subclause 7.1.3.6 and subclause 7.1.3.7. The following are modifications to the aforementioned subclauses to support MCVideo imminent peril communications:
- As a pre-condition, the user initiating the imminent peril communication has previously been provisioned with an MCVideo group to be used as the MCVideo imminent peril group. The MCVideo client initiates MCVideo imminent peril group communications on this group. Alternatively, the MCVideo client could have been provisioned for imminent peril behaviour on the selected MCVideo group.
- The group communication announcement contains an indication that the MCVideo group communication is to be an MCVideo imminent peril communication. Group communication participants learn of the MCVideo group's in-progress imminent peril condition from the indication.
- The MCVideo group in-progress imminent peril state is considered cancelled when the communication ends.
- The MCVideo user who initiated the in-progress imminent peril communication or upgraded the group communication to imminent peril group communication, or an authorized user may cancel the in-progress imminent peril state with an MCVideo imminent peril group communication cancel message. The message is sent to the communication participants.
- When the MCVideo group is no longer in the in-progress imminent peril state, every MCVideo client returns the value of ProSe Per Packet Priority to its default value.
- An in-progress MCVideo group communication is upgraded to an imminent peril group communication when the periodic group communication announcement contains the imminent peril indicator.
- The value of ProSe Per Packet Priority is upgraded according to imminent peril state of MCVideo group communication.
- The MCVideo group remains in the in-progress imminent peril state until the imminent peril group communication ends or the in-progress imminent peril state is cancelled.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.1.3.9 MCVideo emergency alert
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.1.3.9.1 General
| The MCVideo client use emergency alert initiation and emergency alert cancel procedures defined in 3GPP TS 23.280 [6], with the following clarifications:
- The MC service ID is the MCVideo ID; and
- The MC service group ID is the MCVideo group ID.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2 Private call
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.1 General
| Private calls are enabled in both on-network and off-network.
Private calls can be setup in two different commencement modes, automatic commencement mode and manual commencement mode.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.2 Private call on-network
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.2.1 General
| The private call setup in automatic commencement mode is described in subclause 7.2.2.3.1, manual commencement mode in subclause 7.2.2.3.2 and private call release (client or server initiated) in subclause 7.2.2.3.3.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.2.2 Information flows for private call in on-network
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.2.2.1 MCVideo private call request (MCVideo client – MCVideo server)
| Table 7.2.2.2.1-1 describes the information flow MCVideo private call request from the MCVideo client to the MCVideo server.
Table 7.2.2.2.1-1: MCVideo private call request (MCVideo client – MCVideo server)
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
Functional alias
O
The functional alias of the calling party
MCVideo ID (see NOTE)
O
The MCVideo ID of the called party
Functional alias (see NOTE)
O
The functional alias of the called party
Transmit media request indication
M
This element indicates whether transmission control will be used for the private call.
SDP offer
M
Media parameters of MCVideo client.
Requested commencement mode
O
An indication that is included if the user is requesting a particular commencement mode
Implicit transmit media request
O
An indication that the user is also requesting the permission to transmit video
Push indication
O
Indicates that the private call request is for a one-to-one push call
Pull indication
O
Indicates that the private call request is for a one-to-one pull call
Requested priority
O
Application priority level requested for this call
NOTE: Either an MCVideo ID or a functional alias shall be present, but not both.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.2.2.2 MCVideo private call request
| Table 7.2.2.2.2-1 describes the information flow MCVideo private call request from the MCVideo server to the MCVideo server and from the MCVideo server to the MCVideo client.
Table 7.2.2.2.2-1: MCVideo private call request
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
Functional alias
O
The functional alias of the calling party
MCVideo ID
M
The MCVideo ID of the called party
Transmit media request indication
M
This element indicates whether transmission control will be used for the private call.
SDP offer
M
Media parameters of MCVideo client.
Requested commencement mode
O
An indication that is included if the user is requesting a particular commencement mode
Implicit transmit media request (see NOTE)
O
An indication that the user is also requesting the permission to transmit video
Push indication
O
Indicates that the private call request is for a one-to-one push call
Pull indication
O
Indicates that the private call request is for a one-to-one pull call
NOTE: This element shall not be included when the request is sent from the MCVideo server to the MCVideo client.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.2.2.3 MCVideo private call response (MCVideo client – MCVideo server)
| Table 7.2.2.2.3-1 describes the information flow MCVideo private call response from the MCVideo client to the MCVideo server.
Table 7.2.2.2.3-1: MCVideo private call response (MCVideo client – MCVideo server)
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
MCVideo ID
O
The MCVideo ID of the called party
SDP answer
M
Media parameters selected
Requested commencement mode
O
An indication of the commencement mode to be used.
Implicit transmit media request (see NOTE)
O
An indication that the user is also requesting the permission to transmit video
NOTE: This element shall be included when the response is associated to a request including a pull indication.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.2.2.4 MCVideo private call response
| Table 7.2.2.2.4-1 describes the information flow MCVideo private call response from the MCVideo server to the MCVideo server and from the MCVideo server to the MCVideo client.
Table 7.2.2.2.4-1: MCVideo private call response
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
MCVideo ID
O
The MCVideo ID of the called party
Acceptance confirmation
O
An indication whether the user has positively accepted the call.
SDP answer
M
Media parameters selected
Implicit transmit media request (see NOTE)
O
An indication that the user is also requesting the permission to transmit video
NOTE: This element shall not be included when the request is sent from the MCVideo server to the MCVideo client.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.2.2.5 MCVideo call end request
| Table 7.2.2.2.5-1 describes the information flow MCVideo call end request from the MCVideo client to the MCVideo server, from the MCVideo server to the MCVideo server and from the MCVideo server to the MCVideo client.
Table 7.2.2.2.5-1: MCVideo call end request
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
MCVideo ID
M
The MCVideo ID of the called party
MCVideo call end reason
O
Indicate that the reason to end the call, e.g., due to migration, or due to user request.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.2.2.6 MCVideo emergency private call request (MCVideo client to MCVideo server)
| Table 7.2.2.2.6-1 describes the information flow MCVideo emergency private call request from the MCVideo client to the MCVideo server.
Table 7.2.2.2.6-1: MCVideo emergency private call request (MCVideo client to MCVideo server)
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
Functional alias
O
The functional alias of the calling party
MCVideo ID
M
The MCVideo ID of the called party
Emergency indicator
M
Indicates that the private call request is an MCVideo emergency call
Alert indicator
M
Indicates whether an emergency alert is to be sent
Requested commencement mode
O
An indication of the commencement mode to be used.
Implicit transmit media request
O
An indication that the user is also requesting to transmit media
SDP offer
M
Media parameters of MCVideo client.
Requested priority
O
Priority level requested for the call
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.2.2.7 MCVideo emergency private call request
| Table 7.2.2.2.7-1 describes the information flow MCVideo emergency private call request from the MCVideo server to the MCVideo server and from the MCVideo server to the MCVideo client.
Table 7.2.2.2.7-1: MCVideo emergency private call request
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
Functional alias
O
The functional alias of the calling party
MCVideo ID
M
The MCVideo ID of the called party
Emergency indicator
M
Indicates that the private call request is an MCVideo emergency call
Alert indicator
M
Indicates whether an emergency alert is to be sent
Requested commencement mode
O
An indication of the commencement mode to be used.
Implicit transmit media request
O
An indication that the user is also requesting to transmit media.
SDP offer
M
Media parameters of MCVideo client.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.2.2.8 Emergency MCVideo private call response (MCVideo client – MCVideo server)
| Table 7.2.2.2.8-1 describes the information flow emergency MCVideo private call response from the MCVideo client to the MCVideo server.
Table 7.2.2.2.8-1: Emergency MCVideo private call response (MCVideo client – MCVideo server)
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
MCVideo ID
O
The MCVideo ID of the called party
SDP answer
M
Media parameters selected
Requested commencement mode
O
An indication of the commencement mode to be used.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.2.2.9 Emergency MCVideo private call response
| Table 7.2.2.2.9-1 describes the information flow Emergency MCVideo private call response from the MCVideo server to the MCVideo server and from the MCVideo server to the MCVideo client.
Table 7.2.2.2.9-1: Emergency MCVideo private call response
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
MCVideo ID
O
The MCVideo ID of the called party
Acceptance confirmation
O
An indication whether the user has positively accepted the call.
SDP answer
M
Media parameters selected
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.2.2.10 MCVideo progress indication
| Table 7.2.2.2.10-1 describes the information flow MCVideo progress indication from the MCVideo server to the MCVideo client.
Table 7.2.2.2.10-1: MCVideo progress indication information elements
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
MCVideo ID
M
The MCVideo ID of the called party
Progress indication
O
Indication to the caller.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.2.2.11 MCVideo functional alias resolution response
| Table 7.2.2.2.11-1 describes the information flow MCVideo functional alias resolution response from the MCVideo server to the MCVideo client.
Table 7.2.2.2.11-1: MCVideo functional alias resolution response information elements
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
MCVideo ID
M
The corresponding MCVideo ID of the called functional alias
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.2.3 Private call within one MC system
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.2.3.1 Private call setup in automatic commencement mode
| The procedure describes the scenario where an MCVideo user is initiating an MCVideo private call for communicating with another MCVideo user, with or without transmission control enabled, in an automatic commencement mode.
Procedures in figure 7.2.2.3.1-1 are the basic signalling control plane procedures for the MCVideo client initiating establishment of MCVideo private call with the chosen MCVideo user.
Pre-conditions:
1. MCVideo users on MCVideo client 1 and MCVideo client 2 are already registered for receiving MCVideo service.
2. The calling MCVideo user has selected automatic commencement mode for the call; or
3. The called MCVideo client is set to automatic commencement mode.
4. Optionally, the MCVideo client 1 may have a functional alias activated to be used.
5. The MCVideo server may have subscribed to the MCVideo functional alias controlling server within the MC system for functional alias activation/de-activation updates.
Figure 7.2.2.3.1-1: Private call setup in automatic commencement mode– MCVideo users in the same MC system
1. User at MCVideo client 1 would like to initiate an MCVideo private call for the chosen MCVideo user. The MCVideo user at MCVideo client 1 may include a functional alias used within the MCVideo private call.
2. MCVideo client 1 sends an MCVideo private call request towards the MCVideo server (via SIP core) using a service identifier as defined in 3GPP TS 23.228 [5] for MCVideo, for establishing a private call with the chosen MCVideo user. The MCVideo private call request contains the MCVideo ID or the functional alias of invited user, an SDP offer containing one or more media types. The MCVideo client 1 may include a Requested commencement mode that indicates that the call is to be established in automatic commencement mode if automatic commencement mode is requested by the initiating user.
NOTE 1: As part of this step, MCVideo client 1 and MCVideo client 2 set up a security association (when no functional alias is present), if end-to-end encryption is used for this call.
3. MCVideo server checks whether the MCVideo user at MCVideo client 1 is authorized to initiate the private call, and that MCVideo user at MCVideo client 2 is authorized to receive the private call. MCVideo server verifies whether the provided functional alias, if present, can be used and has been activated for the user. If the MCVideo private call request contains a functional alias instead of an MCVideo ID as called party, the MCVideo server shall resolve the functional alias to the corresponding MCVideo ID(s) for which the functional alias is active. The MCVideo server shall also check whether MCVideo client 1 is allowed to use the functional alias of MCVideo client 2 to setup a private call and whether MCVideo client 2 is allowed to receive a private call from MCVideo client 1 using the functional alias. If the MCVideo private call request requested automatic commencement mode then the MCVideo server also checks whether the MCVideo user at MCVideo client 1 is authorized to initiate a private call in automatic commencement mode.
NOTE 2: When a functional alias is shared among multiple MCVideo users, only one target MCVideo user can be target of the private call request. The MCVideo server resolves the associated MCVideo IDs of the functional alias and determines a MCVideo ID by help of criteria not defined here (e.g. location, time etc). This determination can include rejection of the call, if no suitable MCVideo ID is selected.
4a. If the MCVideo private call request contains only the functional alias instead of an MCVideo ID for the called party, the MCVideo server responds with a functional alias resolution response message that contains the resolved MCVideo ID back to MCVideo client 1.
4b. If the MCVideo server replies with a MCVideo functional alias resolution response message, the MCVideo client 1 abandons the first MCVideo private call request in step 2 and sends a new MCVideo private call request towards the resolved MCVideo ID.
NOTE 3: MCVideo client 1 and MCVideo client 2 set up a security association for the media, if end-to-end encryption is used for this call.
5. MCVideo server may provide a progress indication to MCVideo client 1 to indicate progress in the call setup process.
NOTE 4: Step 5 can occur at any time following step 4b, and prior to step 9.
6. If authorized, MCVideo server includes information that it communicates using MCVideo service, offers the same media types or a subset of the media types contained in the initial received request, includes the requested automatic commencement mode indication based on a requested automatic commencement mode by the calling user or based upon the setting of the called MCVideo client and sends the corresponding MCVideo private call request towards the MCVideo client 2, including the MC service ID and, if available the functional alias of the calling MCVideo user 1. If the called MCVideo user has registered to the MCVideo service with multiple MCVideo UEs and has designated the MCVideo UE for receiving the private calls, then the incoming MCVideo private call request is delivered only to the designated MCVideo UE.
7. The receiving MCVideo client 2 notifies the user about the incoming private call. If the functional alias of the calling user is included, it is displayed.
8. The receiving MCVideo client 2 accepts the private call automatically, and an MCVideo private call response is sent to the MCVideo server (via SIP core).
9. Upon receiving the MCVideo private call response from MCVideo client 2 accepting the private call request, the MCVideo server informs the MCVideo client 1 about successful call establishment.
10. MCVideo client 1 and MCVideo client 2 have successfully established media plane and transmission control for communication and both users can transmit media.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.2.3.2 Private call setup in manual commencement mode
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.2.3.2.1 Description
| Figure 7.2.2.3.2.2-1 describes the basic procedure for the MCVideo client initiating an MCVideo private call that uses manual commencement mode. The flow may use a transmit media request in the MCVideo private call request indicating that the originator will be granted permission to transmit when the call starts and eliminates the need for a separate initial transmit media request message during media plane establishment. Alternatively, the call initiation may be sent without the transmit media request, which allows the called party to transmit media request first.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.2.3.2.2 Procedure
| Both clients are served by the primary MC service provider in figure 7.2.2.3.2.2-1.
Pre-conditions:
1. MCVideo client 1 and MCVideo client 2 are both registered and their respective users, MCVideo user 1 and MCVideo user 2, are authenticated and authorized to use the MCVideo service.
2. The calling MCVideo user has selected manual commencement mode or has not specified a commencement mode for the call; and
3. The called MCVideo client is set to manual commencement mode.
4. Optionally, the MCVideo client 1 may have a functional alias activated to be used.
5. The MCVideo server may have subscribed to the MCVideo functional alias controlling server within the MC system for functional alias activation/de-activation updates.
Figure 7.2.2.3.2.2-1: MCVideo private call in manual commencement mode– MCVideo users in the same MC system
1. MCVideo user at MCVideo client 1 would like to initiate an MCVideo private call for the selected MCVideo user. The MCVideo user at MCVideo client 1 may include a functional alias used within the MCVideo private call.
2. MCVideo client 1 sends an MCVideo private call request addressed to the MC service ID of MCVideo user 2 using an MCVideo service identifier as defined in 3GPP TS 23.228 [5] (possible for the SIP core to route the request to the MCVideo server). The MCVideo private call request contains the MC service ID or the functional alias of invited user and an SDP offer containing one or more media types. The MCVideo client 1 may include a requested commencement mode that indicates that the call is to be established in manual commencement mode if manual commencement mode is requested by the initiating user.
NOTE 1: As part of this step, MCVideo client 1 and MCVideo client 2 set up a security association (when no functional alias is present), if end-to-end encryption is used for this call.
3. The MCVideo server confirms that both MCVideo users are authorized for the private call. MCVideo server verifies whether the provided functional alias, if present, can be used and has been activated for the user. If the MCVideo private call request contains a functional alias instead of an MCVideo ID as called party, the MCVideo server shall resolve the functional alias to the corresponding MCVideo ID(s) for which the functional alias is active. The MCVideo server shall also check whether MCVideo client 1 is allowed to use the functional alias of MCVideo client 2 to setup a private call and whether MCVideo client 2 is allowed to receive a private call from MCVideo client 1 using the functional alias. The MCVideo server checks the commencement mode setting of the called MCVideo client and also checks whether the MCVideo user at MCVideo client 1 is authorized to initiate a call in manual commencement mode.
NOTE 2: When a functional alias is shared among multiple MCVideo users, only one target MCVideo user can be target of the private call request. The MCVideo server resolves the associated MCVideo IDs of the functional alias and determines a MCVideo ID by help of criteria not defined here (e.g. location, time etc). This determination can include rejection of the call, if no suitable MCVideo ID is selected.
4a. If the MCVideo private call request contains only the functional alias instead of an MCVideo ID for the called party, the MCVideo server responds with a functional alias resolution response message that contains the resolved MCVideo ID back to MCVideo client 1.
4b. If the MCVideo server provided the corresponding MCVideo ID, the MCVideo client 1 abandons the first MCVideo private call request in step 2 and sends a new MCVideo private call request containing the resolved MCVideo ID.
NOTE 3: MCVideo client 1 and MCVideo client 2 set up a security association for the media, if end-to-end encryption is used for this call.
5. The MCVideo server includes information that it communicates using MCVideo service, offers the same media types or a subset of the media types contained in the initial received request and sends an MCVideo private call request for the call to MCVideo client 2, including the MC service ID, and, if available the functional alias of the calling MCVideo user 1. If the called MCVideo user has registered to the MCVideo service with multiple MCVideo UEs and has designated the MCVideo UE for receiving the private calls, then the incoming MCVideo private call request is delivered only to the designated MCVideo UE.
6. MCVideo server may provide a progress indication to MCVideo client 1 to indicate progress in the call setup process.
NOTE 4: Step 6 can occur at any time following step 4b, and prior to step 7b.
7a. The MCVideo user is alerted. MCVideo client 2 sends an MCVideo ringing to the MCVideo server.
7b. The MCVideo server sends an MCVideo ringing to MCVideo client 1, indicating that MCVideo client 2 is being alerted. If the functional alias of the calling user is included, it is displayed.
8. MCVideo user 2 is notified and has accepted the call using manual commencement mode (i.e., has taken some action to accept via the user interface).
9. The MCVideo client 2 sends an MCVideo private call response to the MCVideo server. If MCVideo user 2 has not accepted the incoming call, the MCVideo client 2 sends a call failure response to the MCVideo server without adding reason for call failure.
10. The MCVideo server sends an MCVideo private call response to MCVideo client 1 indicating that MCVideo user 2 has accepted the call, including the accepted media parameters.
11. The media plane and transmission control for communication is established.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.2.3.3 Private call release
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.2.3.3.1 Client initiated
| The procedure describes the scenario where an MCVideo client is requesting to release an ongoing MCVideo private call (with or without transmission control) and the call established in either of the two commencement modes (manual or automatic).
Procedures in figure 7.2.2.3.3.1-1 are the basic signalling control plane procedures for the MCVideo client initiating the release of an ongoing MCVideo private call.
Pre-condition:
1. It is assumed that MCVideo users on MCVideo client 1 and MCVideo client 2 are already registered for receiving MCVideo service and are involved in private call as described in subclause 7.2.2.3.1 and subclause 7.2.2.3.2.
Figure 7.2.2.3.3.1-1: Private call release – client initiated
1. User at MCVideo client 1 would like to release an ongoing MCVideo private call with MCVideo client 2.
2. MCVideo client 1 sends an MCVideo call end request towards the MCVideo server (via SIP core), for tearing down the private call with the other client.
3. MCVideo server sends the corresponding MCVideo call end request towards the MCVideo client specified in the original MCVideo call end request.
4. MCVideo user is notified about the release of the private call.
5. The receiving MCVideo client 2 acknowledges the MCVideo call end request with a MCVideo call end response.
6. After receiving the MCVideo call end response from MCVideo client 2, the MCVideo server generates an MCVideo call end response for the MCVideo client 1's MCVideo call end request.
7. MCVideo clients release all the media plane resources used for the private call. Further, if the private call was established with transmission control, transmission control resources are released.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.2.3.3.2 Server initiated
| The procedure describes the scenario where an MCVideo server is terminating an ongoing MCVideo private call and the call established in either of the two commencement modes (manual or automatic), upon conditions to terminate call e.g., MCVideo administrator configured maximum duration for MCVideo private calls has expired or timed out due to MCVideo private call without transmission/reception.
Procedures in figure 7.2.2.3.3.2-1 are the basic signalling control plane procedures for the MCVideo server initiating termination of an ongoing MCVideo private call.
Pre-condition:
1. It is assumed that MCVideo users on MCVideo client 1 and MCVideo client 2 are already registered for receiving MCVideo service and are involved in private call established either in manual or automatic commencement mode.
Figure 7.2.2.3.3.2-1: End private call – server initiated
1. Upon conditions to terminate call e.g., MCVideo administrator configured maximum duration for MCVideo private calls has expired or timed out due to MCVideo private call without transmission/reception, the MCVideo server decides to initiate termination of an ongoing MCVideo private call between MCVideo client 1 and MCVideo client 2.
2. MCVideo server sends an MCVideo call end request towards the MCVideo clients 1 and 2 (via SIP core), for tearing down the private call between them.
3. MCVideo users at client 1 and client 2 are notified about the termination of the private call.
4. The MCVideo call end request receiving MCVideo clients 1 and 2 acknowledge the request with MCVideo call end response.
5. MCVideo clients release all the media plane resources used for the private call. Further, if the private call was established with transmission control, transmission control resources are released.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.2.4 MCVideo emergency private call
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.2.4.1 MCVideo emergency private call commencement
| This procedure describes the case where an authorized MCVideo user is initiating an MCVideo emergency private call with unicast signalling for communicating with another MCVideo user. An MCVideo client in the MCVideo emergency state gains elevated access privilege for all of the MCVideo user's mission critical applications.
Procedures in figure 7.2.2.4.1-1 are the procedures for the MCVideo client initiating establishment of an MCVideo emergency private call.
Pre-conditions:
1. Both members of the MCVideo private call belong to the same MCVideo system.
2. The initiating MCVideo client 1 has been configured to send an MCVideo emergency alert prior to initiating an MCVideo emergency private call.
3. Optionally, the MCVideo client 1 may have a functional alias activated to be used.
4. The MCVideo server may have subscribed to the MCVideo functional alias controlling server within the MC system for functional alias activation/de-activation updates.
Figure 7.2.2.4.1-1 MCVideo emergency private call
1. The user at the MCVideo client 1 initiates an MCVideo emergency private call. MCVideo client 1 sets its MCVideo emergency state. MCVideo client 1 retains the MCVideo emergency state until explicitly cancelled by the user of MCVideo client 1.
NOTE 1: While MCVideo client 1 is in the emergency state, all MCVideo group and private calls initiated by MCVideo client 1 are initiated as MCVideo emergency calls.
2. MCVideo client 1 sends an MCVideo emergency private call request towards the MCVideo server. The request contains an indication of the MCVideo emergency. The MCVideo user at MCVideo client 1 may include a functional alias used within the MCVideo emergency private call. The MCVideo server verifies whether the provided functional alias can be used. The MCVideo server records the identity of the MCVideo user that initiated the MCVideo emergency private call until the MCVideo emergency is cancelled. If the MCVideo client is configured to send an MCVideo emergency alert when initiating an MCVideo emergency private call, the request also contains an indication that an MCVideo emergency alert is to be initiated.
3. MCVideo server sends the MCVideo emergency private call request towards the target MCVideo client. The request contains an indication of the in-progress emergency. The request contains an indication of an MCVideo emergency alert if the request from the originator indicated MCVideo emergency alert. If available the request contains the functional alias of the calling MCVideo user 1.
4. The MCVideo user on MCVideo client 2 is notified of the incoming MCVideo emergency private call. If the functional alias of the calling user is included it is displayed.
NOTE 2: MCVideo client 2 does not set its emergency state as a result of receiving the MCVideo emergency private call.
5. The receiving MCVideo client acknowledges the MCVideo emergency private call request to the MCVideo server via a MCVideo emergency private call response.
6. The MCVideo server adjusts the priority of the underlying bearer.
7. The MCVideo server informs MCVideo client 1 about the successful MCVideo emergency private call establishment via a MCVideo emergency private call response.
8. MCVideo client 1 and MCVideo client 2 establish the media plane and transmission control for video communication.
NOTE 3: The priority for the MCVideo emergency private call is retained until cancelled according to system policy (e.g. call end) or cancelled by an authorized MCVideo user.
NOTE 4: The initiating MCVideo user's MCVideo emergency state is retained by the system until cancelled as in subclause 7.1.2.6, or by the emergency alert cancellation procedure specified in 3GPP TS 23.280 [5] subclause 10.10.1.2.2.2. The initiating MCVideo user's MCVideo emergency state is also retained locally by the MCVideo client until explicitly cancelled by the MCVideo user.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.2.4.2 MCVideo private call emergency upgrade
| This procedure describes the case where an authorized MCVideo user is upgrading a private call to an MCVideo emergency private call while the private call is already in progress.
Procedures in figure 7.2.2.4.2-1 are the signalling procedures for the MCVideo client upgrading a private call to an MCVideo emergency private call.
Pre-conditions:
1. Both members of the private call belong to the same MCVideo system.
2. A private call is already in progress.
Figure 7.2.2.4.2-1: MCVideo private call upgrade
1. The MCVideo user at MCVideo client 1 initiates an emergency. MCVideo client 1 sets its MCVideo emergency state. MCVideo client 1 retains the MCVideo emergency state until explicitly cancelled by the user of MCVideo client 1.
NOTE 1: While MCVideo client 1 is in the emergency state, all MCVideo group and private calls initiated by MCVideo client 1 are initiated as MCVideo emergency calls.
2. MCVideo client 1 requests the MCVideo server to upgrade the private call to in-progress emergency by sending an MCVideo emergency private call request. If configured to send an MCVideo alert when initiating an MCVideo emergency upgrade, the request also contains an indication that an MCVideo alert is to be initiated. The request may contain an indication of an implicit transmit media request.
3. MCVideo server sends the MCVideo emergency request towards MCVideo client 2, the MCVideo client of the other participant.
4. The MCVideo user of MCVideo client 2 is notified of the in-progress emergency of the MCVideo emergency private call.
NOTE 2: MCVideo client 2 does not set its emergency state as a result of receiving the MCVideo emergency private call upgrade.
5. The receiving MCVideo client acknowledges the MCVideo emergency request to the MCVideo server.
6. The MCVideo server adjusts the priority of the underlying bearer for both participants in the private call. The priority is retained until the call ends.
7. The MCVideo server confirms the upgrade request to MCVideo client 1. If the MCVideo emergency request contained an implicit transmit media request, the MCVideo emergency private call response message contains the result of the implicit transmit media request.
8. MCVideo client 1 and MCVideo client 2 continue with the private call, which has been transformed into an MCVideo emergency private call. MCVideo client 1 can override MCVideo client 2 unless MCVideo client 2 is also in the MCVideo emergency state.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.3 Off-network private communications
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.3.1 General
| The private call setup in automatic commencement mode is described in subclause 7.2.3.4, manual commencement mode in subclause 7.2.3.5 and private call release in subclause 7.2.3.6.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.3.2 Information flows for off-network private communications
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.3.2.1 Private communication request
| Table 7.2.3.2.1-1 describes the information flow for the private communication request sent from one MCVideo client to another MCVideo client.
Table 7.2.3.2.1-1: Private communication request
Information element
Status
Description
MCVideo ID
M
The identity of the MCVideo user requesting the communication
MCVideo ID
M
The identity of the MCVideo user with whom communication was requested
SDP offer
M
SDP with media information offered by the caller
Video push indication
O
Indicates that the MCVideo private communication is for video push
Video pull indication
O
Indicates that the MCVideo private communication is for video pull
NOTE 1: For video push, 'the identity of the MCVideo user requesting the communication' refers to the user who will be the source of the video, and 'the identity of the MCVideo user with whom the communication was requested' refers to the user who will receive the video.
NOTE 2: For video pull, 'the identity of the MCVideo user requesting the communication' refers to the user who wants to receive the video, and 'the identity of the MCVideo user with whom the communication was requested' refers to the user who will be the source of the video.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.3.2.2 Private communication answer response
| Table 7.2.3.2.2-1 describes the information flow for the response of private communication request sent from one MCVideo client to another MCVideo client.
Table 7.2.3.2.2-1: Private communication answer response
Information element
Status
Description
MCVideo ID
M
The identity of the MCVideo user requesting the communication
MCVideo ID
M
The identity of the MCVideo user with whom communication was requested
SDP answer
M
SDP with media information accepted by the callee
NOTE 1: For video push, 'the identity of the MCVideo user requesting the communication' refers to the user who will be the source of the video, and 'the identity of the MCVideo user with whom the communication was requested' refers to the user who will receive the video.
NOTE 2: For video pull, 'the identity of the MCVideo user requesting the communication' refers to the user who wants to receive the video, and 'the identity of the MCVideo user with whom the communication was requested' refers to the user who will be the source of the video.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.3.2.3 Private communication release request
| Table 7.2.3.2.3-1 describes the information flow for the private communication release request sent from one MCVideo client to another MCVideo client.
Table 7.2.3.2.3-1: Private communication release request
Information element
Status
Description
MCVideo ID
M
The identity of the MCVideo user requesting the communication
MCVideo ID
M
The identity of the MCVideo user with whom communication was requested
MCVideo private communication release reason
O
Reason for the private communication release.
NOTE 1: For video push, 'the identity of the MCVideo user requesting the communication' refers to the user who will be the source of the video, and 'the identity of the MCVideo user with whom the communication was requested' refers to the user who will receive the video.
NOTE 2: For video pull, 'the identity of the MCVideo user requesting the communication' refers to the user who wants to receive the video, and 'the identity of the MCVideo user with whom the communication was requested' refers to the user who will be the source of the video.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.3.2.4 Private communication release response
| Table 7.2.3.2.4-1 describes the information flow for the private communication release response sent from one MCVideo client to another MCVideo client.
Table 7.2.3.2.4-1: Private communication release response
Information element
Status
Description
MCVideo ID
M
The identity of the MCVideo user requesting the communication
MCVideo ID
M
The identity of the MCVideo user with whom communication was requested
NOTE 1: For video push, 'the identity of the MCVideo user requesting the communication' refers to the user who will be the source of the video, and 'the identity of the MCVideo user with whom the communication was requested' refers to the user who will receive the video.
NOTE 2: For video pull, 'the identity of the MCVideo user requesting the communication' refers to the user who wants to receive the video, and 'the identity of the MCVideo user with whom the communication was requested' refers to the user who will be the source of the video.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.3.3 Use of ProSe for off-network private communications
| The use of ProSe capabilities for off-network private communications is described in clause 7.18.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.3.4 Automatic commencement private communication
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.3.4.1 General
| A private call request is sent by a MCVideo client directly to another MCVideo client, which checks the request, establishes the MCVideo session without further user interaction and notifies its user that the MCVideo session has been established.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.3.4.2 Procedure
| Figure 7.2.3.4.2-1 describes procedures to establish an off-network automatic commencement private communication between MCVideo user A MCVideo user B.
Pre-conditions:
1. MCVideo user A has initiated automatic commencement private communication with MCVideo user B.
2. MCVideo user B has indicated MCVideo client B as the designated MCVideo client for MCVideo private communications.
3. MCVideo client A and MCVideo client B are members of the same ProSe Discovery group and are ProSe 1:1 direct communication capable.
4. MCVideo client A has discovered MCVideo client B in proximity, associated with MCVideo user B, using ProSe Discovery procedures.
NOTE: How MCVideo client A determines that MCVideo client B is the designated MCVideo client of MCVideo user B for private communications is implementation specific.
Figure 7.2.3.4.2-1: Off-network automatic commencement private communication
1. The MCVideo client A sends the Private communication request towards MCVideo client associated with MCVideo user B. The Private communication request contains an indication for automatic commencement and the SDP offer.
2. On receiving a Private communication request with an indication for automatic commencement, the MCVideo client checks if it is the designated MCVideo client for off-network MCVideo private communications.
3a. The designated MCVideo client B automatically accepts the Private communication request, and sends a Private communication answer response, indicating the successful receipt of communication request to the MCVideo client A. The Private communication answer response contains the SDP answer.
3b. The designated MCVideo client B notifies the MCVideo user B about the incoming Private communication request.
NOTE 1: Step 3a and step 3b can occur in any order.
4. The MCVideo client A and the MCVideo client B establish the media plane for Private Communication.
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.
5. MCVideo media is transmitted from the MCVideo client A to the MCVideo client B and is presented to the MCVideo user B.
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.2.3.5 Manual commencement private communication
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.3.5.1 General
| A private call request is sent by a MCVideo client directly to another MCVideo client, which checks the request, establishes the MCVideo session without further user interaction and notifies its user about the incoming MCVideo session request. The MCVideo user may accept, reject or ignore the MCVideo session request.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.3.5.2 Procedure – Communication accepted
| Figure 7.2.3.5.2-1 describes procedures to establish an off-network manual commencement private communication between MCVideo user A MCVideo user B, which is accepted by the MCVideo user B.
Pre-conditions:
1. MCVideo user A has initiated manual commencement private communication with MCVideo user B.
2. MCVideo user B has indicated MCVideo client B as the designated MCVideo client for MCVideo private communications, if the MCVideo user B has signed on to the MCVideo service with multiple MCVideo clients.
3. MCVideo client A and MCVideo client B are members of the same ProSe Discovery group and are ProSe 1:1 direct communication capable.
4. MCVideo client A has discovered MCVideo clients B in proximity, associated with MCVideo user B, using ProSe Discovery procedures.
NOTE: How MCVideo client A determines that MCVideo client B is the designated MCVideo client of MCVideo user B for private communications is implementation specific.
Figure 7.2.3.5.2-1: Off-network manual commencement private communication – Accepted
1. The MCVideo client A sends the Private communication request towards MCVideo client associated with MCVideo user B. The Private communication request contains an indication for manual commencement and the SDP offer.
2. On receiving a Private communication request, the MCVideo client checks if it is the designated MCVideo client for off-network MCVideo private communications.
3a. The designated MCVideo client B presents the incoming Private communication request to the MCVideo user B.
3b. The MCVideo client B sends back a Private communication ringing response to the MCVideo client A.
NOTE 1: Step 3a and step 3b can occur in any order.
4. The MCVideo client A notifies the ringing status to the MCVideo user A.
5. The MCVideo user B accepts the Private communication request.
6. The MCVideo client B sends the Private communication answer response to the MCVideo client A. The Private communication response contains the SDP answer.
7. The MCVideo client A and the MCVideo client B establish the media plane for Private communication.
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.
8. MCVideo media is transmitted from the MCVideo client A to the MCVideo client B and is presented to the MCVideo user B.
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.2.3.5.3 Procedure – Communication rejected/ignored
| Figure 7.2.3.5.3-1 describes procedures to initiate an off-network manual commencement private communication between MCVideo user A MCVideo user B, which is rejected or ignored by the MCVideo user B.
Pre-conditions:
1. MCVideo user A has initiated manual commencement private communication with MCVideo user B.
2. MCVideo user B has indicated MCVideo client B as the designated MCVideo client for MCVideo Private Communications, if the MCVideo user B has signed on to the MCVideo service with multiple MCVideo clients.
3. MCVideo client A and MCVideo client B are members of the same ProSe Discovery group and are ProSe 1:1 direct communication capable.
4. MCVideo client A has discovered MCVideo clients B in proximity, associated with MCVideo user B, using ProSe Discovery procedures.
Figure 7.2.3.5.3-1: Off-network manual commencement private communication – Rejected or Ignored
1. The MCVideo client A sends the private communication request towards MCVideo client associated with MCVideo user B. The private communication request contains an indication for manual commencement and the SDP offer.
2. On receiving a Private communication request, the MCVideo client checks if it is the designated MCVideo client for off-network MCVideo private communications.
3a. The designated MCVideo client B presents the incoming Private communication request to the MCVideo user B.
3b. The MCVideo client B sends back a Private communication ringing response to the MCVideo client A.
NOTE 1: Step 3a and step 3b can occur in any order.
4. The MCVideo client A notifies the ringing status to the MCVideo user A.
5. The MCVideo user B rejects (or ignores) the Private communication request.
NOTE 2: The MCVideo client B determines that the MCVideo user B has ignored the Private communication request, if the MCVideo user B does not respond within a configured time limit.
6. The MCVideo client B sends a Private communication reject response to the MCVideo client A. The Private communication reject response may indicate that the MCVideo user B has ignored the Private communication request.
7. The MCVideo client A notifies the MCVideo user A that the Private communication request was rejected (or ignored).
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.3.6 Private communication release
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.3.6.1 General
| Either of the MCVideo users involved in a private communication may release the unidirectional media plane or the whole private communication at any time.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.2.3.6.2 Procedure
| Figure 7.2.3.6.2-1 describes procedures to release an ongoing MCVideo Private communication (either automatic commencement private communication or manual commencement private communication).
Either of the MCVideo users, the initiator or the receiver of the Private communication can request to release the Private communication.
The Private communication release request can be to release an individual (unidirectional) media plane or to terminate the Private communication. Based on the request the requested media plane or both the media planes are terminated in step 3.
Pre-conditions:
1. MCVideo client A and MCVideo client B are engaged in a Private communication.
2. MCVideo user A at MCVideo client A initiates release of the Private communication.
Figure 7.2.3.6.2-1: Off-network Private communication release
1, The MCVideo client A sends the Private communication release request to the MCVideo client B.
2a. The MCVideo client B sends a Private communication release response indicating successful receipt of the request to the MCVideo client A.
2b. The MCVideo client B notifies the MCVideo user B about the Private communication release request.
NOTE: Step 2a and step 2b can occur in any order.
3. MCVideo client A and MCVideo client B release the requested media plane. If both the media planes are released, the Private communication is terminated.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.3 Video pull
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.3.1 General
| MCVideo pull is enabled in both on-network and off-network mode.
For on-network MCVideo pull is supported between MCVideo clients, or between a MCVideo client and a MCVideo server.
For off-network MCVideo pull is supported between MCVideo clients only.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.3.2 On-network video pull
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.3.2.1 General
| A MCVideo user triggers its MCVideo client to pull a video either from another MCVideo client or from a MCVideo server.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.3.2.2 Information flows for on-network video pull
| The following information flows for private call specified in subclause 7.2.2.2 is used for on-network video pull:
- MCVideo private call request (MCVideo client – MCVideo server)
- MCVideo private call request (MCVideo server – MCVideo client)
- MCVideo private call response (MCVideo client – MCVideo server)
- MCVideo private call response (MCVideo server – MCVideo client)
- MCVideo call end request
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.3.2.2.1 MCVideo pull from server request
| Table 7.3.2.2.1-1 describes the information flow MCVideo pull from server request from the MCVideo client to the MCVideo server.
Table 7.3.2.2.1-1: MCVideo pull from server request
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
File URL
M
URL of the video file to be streamed
SDP offer
M
Media parameters of MCVideo client
Requested priority
O
Application priority level requested for this call
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.3.2.2.2 MCVideo pull from server response
| Table 7.3.2.2.2-1 describes the information flow MCVideo pull from server response from the MCVideo server to the MCVideo client.
Table 7.3.2.2.2-1: MCVideo pull from server response
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
SDP answer
M
Media parameters selected
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.3.2.2.3 MCVideo pull from server complete request
| Table 7.3.2.2.3-1 describes the information flow MCVideo pull from server complete request from the MCVideo client to the MCVideo server or from the MCVideo server to the MCVideo client.
Table 7.3.2.2.3-1: MCVideo pull from server complete request
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
Cause
M
End of communication cause
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.3.2.2.4 MCVideo pull from server complete response
| Table 7.3.2.2.4-1 describes the information flow MCVideo pull from server complete response from the MCVideo client to the MCVideo server or from the MCVideo server to the MCVideo client.
Table 7.3.2.2.4-1: MCVideo pull from server complete response
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.3.2.3 One-to-one video pull
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.3.2.3.1 General
| One-to-one video pull is a private call that only allows the called party to transmit video to the calling party, and the private call ends when the video transmission is completed.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.3.2.3.2 One-to-one video pull – call setup
| The procedure describes the case where an MCVideo user is initiating an MCVideo private call to pull video from called MCVideo user in an automatic or manual commencement mode. Only the called party is allowed to transmit video.
Procedures in figure 7.3.2.3.2-1 are the basic signalling control plane procedures for the MCVideo client initiating establishment of MCVideo private call with the chosen MCVideo user for video pull.
Pre-conditions:
1. Optionally, MCVideo client 1 may have a functional alias activated to be used.
2. The MCVideo server may have subscribed to the MCVideo functional alias controlling server within the MC system for functional alias activation/de-activation updates.
Figure 7.3.2.3.2-1: One-to-one video pull
1. MCVideo user on MCVideo client 1 initiates video pull from MCVideo client 2, by sending a private call request to the MCVideo server using a service identifier as defined in 3GPP TS 23.228 [5] for MCVideo, for establishing a private call with the chosen MCVideo user for video pull. The MCVideo private call request contains MCVideo ID of invited user, an SDP offer containing one or more media types and the video pull indication to indicate that invited user is requested to transmit video to the requester. The MCVideo user at MCVideo client 1 may include a functional alias used within the MCVideo private call request.
2. MCVideo server checks whether the MCVideo user at MCVideo client 1 is authorized to initiate the private call for video pull, and that MCVideo user at MCVideo client 2 is authorized to receive the private call for video pull. MCVideo server verifies whether the provided functional alias, if present, can be used and has been activated for the user.
3. MCVideo server may provide a progress indication to MCVideo client 1 to indicate progress in the call setup process.
NOTE 1: Step 3 can occur at any time following step 4, and prior to step 6.
4. If authorized, MCVideo server includes information that it communicates using MCVideo service, offers the same media types or a subset of the media types contained in the initial received request, includes the requested automatic commencement mode indication based on a requested commencement mode by the calling user or based upon the setting of the called MCVideo client and sends the corresponding MCVideo private call request towards the MCVideo client 2, including the MCVideo ID, and, if available the functional alias of the calling MCVideo user 1. If the called MCVideo user has registered to the MCVideo service with multiple MCVideo UEs and has designated the MCVideo UE for receiving the private calls, then the incoming MCVideo private call request is delivered only to the designated MCVideo UE.
5. The MCVideo client 2 notifies the user about the incoming private call for video pull. If a functional alias of the calling user is included it is displayed.
6. The receiving MCVideo client 2 accepts the private call for video pull, and sends an MCVideo private call response to the MCVideo server with an implicit transmit media request.
7. Upon receiving the MCVideo private call response from MCVideo client 2 accepting the private call request for video pull, the MCVideo server informs the MCVideo client 1 about successful call establishment via a private call response message.
8. MCVideo client 1 and MCVideo client 2 have successfully established media plane and transmission control for media communication.
NOTE 2: When the video transmission is completed, the private call is released.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.3.2.3.3 One-to-one video pull – call release
| The private call release procedure specified in subclause 7.2.2.3.3 is used for one-to-one video pull call release.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.3.2.4 One-from-server video pull
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.3.2.4.1 General
| One-from-server video pull is a private call between the calling party and the MCVideo server that allows the calling party to request streaming of a video from the server where it is stored in a file. The one-from-server video pull ends typically when the end of the video file has been reached or when the transmission is stopped by the calling user or by the MCVideo server.
NOTE: This procedure fulfills the requirements for the stage 1 replay of stored video feature.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.3.2.4.2 Procedure
| Procedure in figure 7.3.2.4.2-1 is the basic signalling control plane procedures for the MCVideo client initiating establishment of MCVideo video pull from the MCVideo server.
Pre-conditions:
1. MCVideo user 1 on MCVideo client 1 has been authenticated and authorized to use MCVideo service.
2. MCVideo client 1 is registered.
3. MCVideo client 1 has been received the URL of a video file available on the MCVideo server, e.g. within an MCData SDS.
Figure 7.3.2.4.2-1: One-from-server video pull
1. MCVideo user on MCVideo client 1 initiates the pull of a video from the server and sends an MCVideo pull from server request to the MCVideo server. The request contains the URL of the video file and an SDP offer with media description.
2. MCVideo server checks whether MCVideo client 1 is authorized to pull the requested video from the server.
3. MCVideo server accepts the pull from server request and sends an MCVideo pull from server response. The response contains the SDP answer.
NOTE 1: The SDP may contain a media description that allows the receiving party to remote control the stream (e.g. rewind, fast forward).
4. MCVideo client 1 and MCVideo server have successfully established the media plane and transmission control for the video stream.
5. Video stream is transmitted from MCVideo server to MCVideo client 1. The MCVideo client 1 may be able to remote control the video stream, subject to SDP negotiation.
6. MCVideo user on MCVideo client 1 stops the video pull from the server and sends an MCVideo pull from server complete request.
7. MCVideo server acknowledges the end of the communication.
NOTE 2: Alternatively, based on internal criteria (e.g. maximum duration of the video playback, end of the video file), the MCVideo server can end the transmission.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.3.3 Off-network video pull
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.3.3.1 General
| A MCVideo client pulls a video from another MCVideo client directly, i.e. without involving the network.
Off-network video pull communications are based on ProSe capabilities as described in clause 7.18.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.3.3.2 Information flows for off-network video pull
| The following information flows for private call specified in subclause 7.2.3.2 are used for off-network video pull:
- Private communication request; and
- Private communication answer response.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.3.3.3 Video pull to self
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.3.3.3.1 General
| A MCVideo user requests another MCVideo user to deliver a video from its MCVideo client.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.3.3.3.2 Procedure
| Figure 7.3.3.3.2-1 describes procedures for an off-network MCVideo video pull, inititated by MCVideo user A at MCVideo client A with another MCVideo client B, to pull a video to MCVideo client A.
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 user A has initiated MCVideo video pull 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.3.3.3.2-1: Off-network video pull to self
1. The MCVideo client A sends a Private communication request towards the MCVideo client B. The Private communication request includes a video pull request and indicates MCVideo client A as the intended recipient of the video pull. Private communication request contains the SDP offer.
2a. The MCVideo client B notifies the MCVideo user B about the incoming video pull request.
2b. The MCVideo client B automatically accepts the video pull request, and sends a Private communication answer response indicating the acceptance of the video pull request. The Private communication answer response contains SDP answer.
NOTE 1: Step 2a and step 2b can occur in any order.
3. The MCVideo client A notifies MCVideo user A about the incoming Private communication answer response as an indication of acceptance of MCVideo video pull request.
4. The MCVideo client A and the MCVideo client B establish the media plane for communication.
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.
5. Media is transmitted from MCVideo client B to MCVideo client A and presented to the MCVideo user A.
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 Video push
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.1 General
| MCVideo push is enabled in both on-network and off-network mode.
For on-network MCVideo push is supported between MCVideo clients, or between a MCVideo client and a MCVideo server.
For off-network MCVideo push is supported between MCVideo clients only.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.2 On-network video push
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.2.1 General
| A MCVideo user triggers its MCVideo client to push a video to another MCVideo client or a MCVideo server.
A MCVideo user triggers its MCVideo client to trigger a remote video push, i.e. a second MCVideo client pushes a video to a third MCVideo client or to a MCVideo group.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.2.2 Information flows for on-network video push
| The following information flows for private call specified in subclause 7.2.2.2 is used for on-network video push:
- MCVideo private call request (MCVideo client – MCVideo server)
- MCVideo private call request (MCVideo server – MCVideo client)
- MCVideo private call response (MCVideo client – MCVideo server)
- MCVideo private call response (MCVideo server – MCVideo client)
- MCVideo call end request
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.2.2.1 Remote video push request
| Table 7.4.2.2.1-1 describes the information flow remote video push request from the MCVideo client to the MCVideo server and from the MCVideo server to the MCVideo client.
Table 7.4.2.2.1-1: Remote video push request
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the call originating party
Functional alias
O
The functional alias of the originating party
MCVideo ID
M
The MCVideo ID of the source party who should transmit media
MCVideo ID
O
(see NOTE)
The MCVideo ID of the destination party who should receive media
MCVideo group ID
O
(see NOTE)
The MCVideo group ID of the destination group whose affiliated group members should receive media
SDP offer
O
Media parameters of MCVideo client.
Requested commencement mode
O
An indication that is included if the user is requesting a particular commencement mode
Requested priority
O
Application priority level requested for this call
NOTE: MCVideo ID information element is present if remote video push to destination user is requested. MCVideo group ID information element is present if remote video push to group is requested.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.2.2.2 Remote video push response
| Table 7.4.2.2.2-1 describes the information flow remote video push request from the MCVideo server to the MCVideo client and from the MCVideo client to the MCVideo server.
Table 7.4.2.2.2-1: Remote video push response
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the call originating party
MCVideo ID
M
The MCVideo ID of the source party who should transmit media
MCVideo ID
O
(see NOTE)
The MCVideo ID of the destination party who should receive media
MCVideo group ID
O
(see NOTE)
The MCVideo group ID of the destination group whose affiliated group members should receive media
Acceptance confirmation
O
An indication whether the user or group members have positively accepted the call.
SDP answer
M
Media parameters selected
NOTE: MCVideo ID information element is present if remote video push to destination user is requested. MCVideo group ID information element is present if remote video push to group is requested.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.2.2.3 Remote video push release request
| Table 7.4.2.2.3-1 describes the information flow Remote video push release request from the MCVideo client to the MCVideo server and from the MCVideo server to the MCVideo client.
Table 7.4.2.2.3-1: Remote video push release request
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the call originating party
MCVideo ID
M
The MCVideo ID of the source party who should transmit media
MCVideo ID
O
(see NOTE)
The MCVideo ID of the destination party who should receive media
MCVideo group ID
O
(see NOTE)
The MCVideo group ID of the destination group whose affiliated group members should receive media
NOTE: MCVideo ID information element is present if remote video push to destination user is requested. MCVideo group ID information element is present if remote video push to group is requested.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.2.2.4 MCVideo push to server request
| Table 7.4.2.2.4-1 describes the information flow MCVideo push to server request from the MCVideo client to the MCVideo server.
Table 7.4.2.2.4-1: MCVideo push to server request
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
Time limit
O
Requested duration of the stream to be recorded
SDP offer
M
Media parameters of MCVideo client
Requested priority
O
Application priority level requested for this call
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.2.2.5 MCVideo push to server response
| Table 7.4.2.2.5-1 describes the information flow MCVideo push to server response from the MCVideo server to the MCVideo client.
Table 7.4.2.2.5-1: MCVideo push to server response
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
Time limit
O
Accepted or imposed duration limit of the stream to be recorded
File URL
M
URL of the file the stream will be recorded to
SDP answer
M
Media parameters selected
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.2.2.6 MCVideo push to server complete request
| Table 7.4.2.2.6-1 describes the information flow MCVideo push to server complete request from the MCVideo client to the MCVideo server or from the MCVideo server to the MCVideo client.
Table 7.4.2.2.6-1: MCVideo push to server complete request
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
Cause
M
End of communication cause
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.2.2.7 MCVideo push to server complete response
| Table 7.4.2.2.7-1 describes the information flow MCVideo push to server complete response from the MCVideo client to the MCVideo server or from the MCVideo server to the MCVideo client.
Table 7.4.2.2.7-1: MCVideo push to server complete response
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the calling party
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.2.3 One-to-one video push
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.2.3.1 General
| One-to-one video push is a private call that only allows the calling party to transmit video to the called party, and the private call ends when the video transmission is completed.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.2.3.2 One-to-one video push – call setup
| Procedures in figure 7.4.2.3.2-1 are the basic signalling control plane procedures for the MCVideo client initiating establishment of MCVideo private call with the chosen MCVideo user for video push.
Pre-conditions:
1. This procedure is initiated either manually by the authorized MCVideo users at MCVideo client 1, or automatically due to triggers set by authorized MCVideo users at MCVideo client 1.
2. Optionally, MCVideo client 1 may have a functional alias activated to be used.
3. The MCVideo server may have subscribed to the MCVideo functional alias controlling server within the MC system for functional alias activation/de-activation updates.
Figure 7.4.2.3.2-1: One-to-one video push
1. MCVideo client 1 initiates push video to MCVideo client 2, and sends a private call request to the MCVideo server using a service identifier as defined in 3GPP TS 23.228 [5] for MCVideo, for establishing a private call with the chosen MCVideo user for video push. The MCVideo private call request contains MCVideo ID of invited user, an SDP offer containing one or more media types and the video push indication to indicate that requestor is requesting to transmit video to the called party. The MCVideo user at MCVideo client 1 may include a functional alias used within the MCVideo private call request.
2. MCVideo server checks whether the MCVideo user at MCVideo client 1 is authorized to initiate the private call for video push, and that MCVideo user at MCVideo client 2 is authorized to receive the private call for video push. MCVideo server verifies whether the provided functional alias, if present, can be used and has been activated for the user.
3. MCVideo server may provide a progress indication to MCVideo client 1 to indicate progress in the call setup process.
NOTE 1: Step 3 can occur at any time following step 4, and prior to step 6.
4. If authorized, MCVideo server includes information that it communicates using MCVideo service, offers the same media types or a subset of the media types contained in the initial received request, includes the requested automatic commencement mode indication based on a requested commencement mode by the calling user or based upon the setting of the called MCVideo client and sends the corresponding MCVideo private call request towards the MCVideo client 2, including the MCVideo ID and, if available the functional alias of the calling MCVideo user 1. If the called MCVideo user has registered to the MCVideo service with multiple MCVideo UEs and has designated the MCVideo UE for receiving the private calls, then the incoming MCVideo private call request is delivered only to the designated MCVideo UE.
5. The MCVideo client 2 notifies the user about the incoming private call for video push. If the functional alias of the calling user is included it is displayed.
6. The MCVideo client 2 accepts the private call for video push, and sends an MCVideo private call response to the MCVideo server.
7. Upon receiving the MCVideo private call response from MCVideo client 2 accepting the private call request for video push, the MCVideo server informs the MCVideo client 1 about successful call establishment via a private call response message.
8. MCVideo client 1 and MCVideo client 2 have successfully established media plane and transmission control for media communication.
NOTE 2: When the video transmission is completed, the private call is released.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.2.3.3 One-to-one video push – call release
| The private call release procedure specified in subclause 7.2.2.3.3 is used for one-to-one video push call release.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.2.4 One-to-server video push
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.2.4.1 General
| One-to-server video push is a private call between the calling party and the MCVideo server that allows the calling party to transmit video to the server for it to be recorded to a file. The one-to-server video push ends when the video transmission is stopped by the calling party or by the MCVideo server.
NOTE: This procedure fulfils part of the requirements for the stage 1 video processing capabilities feature.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.2.4.2 Procedure
| Procedure in figure 7.4.2.4.2-1 is the basic signalling control plane procedures for the MCVideo client initiating establishment of MCVideo video push to the MCVideo server.
Pre-conditions:
1. MCVideo user 1 on MCVideo client 1 has been authenticated and authorized to use MCVideo service.
2. MCVideo client 1 is registered.
Figure 7.4.2.4.2-1: One-to-server video push
1. MCVideo user on MCVideo client 1 initiates the push of a video to the server and sends an MCVideo push to server request to the MCVideo server. The request contains an SDP offer with media.
2. MCVideo server checks whether MCVideo client 1 is authorized to push a video to the server.
3. MCVideo server accepts the push to server request and sends an MCVideo push to server response. The response contains the SDP answer and the URL of the file where the video stream will be recorded.
NOTE 1: Push request and response can include a negotiated maximum duration for the transmission.
4. MCVideo client 1 and MCVideo server have successfully established the media plane and transmission control for the video stream.
5. Video stream is transmitted from MCVideo client 1 to MCVideo server. The MCVideo server records the stream to the file whose URL has been given in the MCVideo push to server response.
NOTE 2: Notifications of new media availability can be sent by the initiating MCVideo user or by the MCVideo server using the URL received in the MCVideo push to server response.
NOTE 3: MCVideo clients which receive the notification can initiate a pull of the video stream from the server using the URL provided in the notification, at their convenience, using the procedure defined in subclause 7.3.2.4.2.
6. MCVideo user on MCVideo client 1, or MCVideo client 1 based on pre-defined criteria (e.g. duration), stops the video push to the server and sends an MCVideo push to server complete request.
7. MCVideo server acknowledges the end of the communication.
NOTE 4: Alternatively, based on internal criteria (e.g. maximum duration of the recorded video), the MCVideo server can end the transmission.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.2.5 Remotely initiated video push
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.2.5.1 General
| Remotely initiated video push is a private call remotely initiated by a user that only allows a source user to transmit video to a destination, and the private call ends when the video transmission is completed or released by the authorized user who remotely initiated video push call.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.2.5.2 Remotely initiated video push – call setup
| The procedure describes the case where an authorized MCVideo user is initiating a remotely initiated video push call from source MCVideo user to a destination MCVideo user. Only the source user is allowed to transmit video to the destination user.
Procedures in figure 7.4.2.5.2-1 are the basic signalling control plane procedures for the MCVideo client remotely initiating establishment of MCVideo private call between the source and destination MCVideo users.
Figure 7.4.2.5.2-1: Remotely initiated video push – call setup
1. MCVideo user on MCVideo client 3 initiates remote video push from MCVideo client 1 to MCVideo client 2, by sending a remote video push request to the MCVideo server for establishing a one-to-one video push call between MCVideo client 1 and MCVideo client 2. The remote video push call request contains MCVideo ID of source (MCVideo client 1) and destination (MCVideo client 2) users
2. MCVideo server checks whether the MCVideo user at MCVideo client 3 is authorized to remotely initiate video push call between the source user and the destination user. MCVideo server also checks if there is any on-going call between the source user and the destination user.
3. If MCVideo client 3 is authorized and there is no on-ongoing private call between source user and destination user, the MCVideo server sends the remote video push request message to MCVideo client 1 including the information of MCVideo ID of source and destination users.
4. The MCVideo client 1 accepts the remote video push request and establishes a one-to-one video push call between MCVideo client 1 and MCVideo client 2 as described in the subclause 7.4.2.3.2. The video is transmitted from MCVideo client 1 to MCVideo Client 2.
5. The MCVideo client 1 sends a remote video push response message to MCVideo server indicating success or failure of call establishment between MCVideo client 1 and MCVideo client 2.
6. Upon receiving the remote video push response from MCVideo client 1, the MCVideo server informs the MCVideo client 3 about success or failure of the call establishment by sending a remote video push response message.
NOTE: Steps 5 and 6 can occur before step 4.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.2.5.3 Remotely initiated video push – call release by authorized user
| The procedure describes the case where an authorized MCVideo user is releasing a remotely initiated video push call.
Procedures in figure 7.4.2.5.3-1 are the basic signalling control plane procedures for the MCVideo client releasing the remotely initiated video push call between the source and destination users.
Figure 7.4.2.5.3-1: Remotely initiated video push – call release by authorized user
1. MCVideo user on MCVideo client 3 initiates release of remotely initiated video push call between MCVideo client 1 and MCVideo client 2, by sending a remote video push release request to the MCVideo server for releasing a one-to-one video push call between MCVideo client 1 and MCVideo client 2. The remote video push release request contains MCVideo ID of source user (MCVideo client 1) and destination user (MCVideo client 2).
2. MCVideo server checks whether the MCVideo user at MCVideo client 3 is authorized to release the remotely initiated video push call between MCVideo client 1 and MCVideo client 2, and whether there is any on-going one-to-one video push call between MCVideo client 1 and MCVideo client 2.
3. MCVideo server sends the remote video push release request to MCVideo client 1 for releasing the on-going one-to-one video push call between MCVideo client 1 and MCVideo client 2.
4. The MCVideo client 1 accepts the remote video push release request and performs the release procedure for the one-to-one video push call between MCVideo client 1 and MCVideo client 2 as described in the subclause 7.4.2.3.3.
5. The MCVideo client 1 sends a remote video push release response to the MCVideo server indicating the release of the one-to-one video push call between MCVideo client 1 and MCVideo client 2.
6. Upon receiving the remote video push release response from MCVideo client 1, the MCVideo server informs the MCVideo client 3 about the one-to-one video push call release by sending a remote video push release response message.
NOTE: Steps 5 and 6 can occur before step 4.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.2.6 Remotely initiated video push to group
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.2.6.1 General
| Remotely initiated video push to group is a type of broadcast group call that only allows the originating user to remotely request a source user to transmit video to the group, and the group call ends when the video transmission is completed or the authorized user releases the remotely initiated video push to group call.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.2.6.2 Remotely initiated video push to group – call setup
| The procedure describes the case where an authorized MCVideo user is initiating video push to group call for transmitting video from a source MCVideo user to the group. Only the source MCVideo user is allowed to transmit video.
Procedures in figure 7.4.2.6.2-1 are the basic signalling control plane procedures for the MCVideo client remotely initiating a video push to group call.
Pre-conditions:
1. MCVideo client 1 and MCVideo client 2 are affiliated members of the group X.
2. The user on MCVideo client 1 is authorized to remotely initiate a video push to group call to enable transmitting the video from the user on MCVideo client 2.
Figure 7.4.2.6.2-1: Remotely initiated video push to group – call setup procedure
1. MCVideo user on MCVideo client 1 remotely initiates a video push to group from MCVideo client 2, by sending a remote video push request to the MCVideo server. The remote video push request contains MCVideo ID of the source user (user of MCVideo client 2) and the MCVideo group ID of the group X to which the video transmission is requested.
2. MCVideo server checks whether the MCVideo user at MCVideo client 1 is authorized to remotely initiate a video push to group, and also checks whether MCVideo client 2 is transmitting video in any on-going MCVideo group call on group X. If MCVideo client 2 is already transmitting video to group X then a suitable response is provided in step 6 to MCVideo client 1.
3. The MCVideo server sends a remote video push request initiated by MCVideo client 1 to MCVideo client 2. The remote video push request contains MCVideo ID of the source user, the MCVideo group ID of the group X to which the video transmission is to be initiated by the source user and an SDP offer containing one or more media types.
4. MCVideo client 2 initiates a MCVideo broadcast group call on group X. The MCVideo client 2 begins to transmit video to the group X.
5. The MCVideo client 2 sends a remote video push response message to MCVideo server indicating success or failure in remotely initiating the video push to group X.
6. The MCVideo server sends a remote video push response message to MCVideo client 1 indicating success or failure in remotely initiating the video push to group X by the MCVideo client 2.
NOTE: Steps 5 and 6 can occur before step 4.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.2.6.3 Remotely initiated video push to group – call release by authorized user
| The procedure describes the case where an MCVideo user is remotely releasing a video push to group call for ending the video transmission from the source MCVideo user.
Procedures in figure 7.4.2.6.3-1 are the basic signalling control plane procedures for the MCVideo client remotely releasing a video push to group call.
Pre-condition:
- MCVideo client 1 and MCVideo client 2 are affiliated members of the group X and there is an on-going broadcast group call on group X from MCVideo client 2 remotely initiated by MCVideo client 1 as described in subclause 7.4.2.6.2.
Figure 7.4.2.6.3-1: Remotely initiated video push to group – call release by authorized user
1. MCVideo user on MCVideo client 1 remotely initiates a release of the video push to group call from MCVideo client 2, by sending a remote video push release request to the MCVideo server. The remote video push release request contains MCVideo ID of the source user (user of MCVideo client 2) and the MCVideo group ID of the group X to which the video transmission is to be released.
2. MCVideo server checks whether the MCVideo user at MCVideo client 1 is authorized to remotely release a video push to group call, and also checks whether MCVideo client 2 is transmitting video in an on-going MCVideo group call on group X remotely initiated by MCVideo client 1. If MCVideo client 2 is not transmitting video on group X then a suitable response is provided in step 5 to MCVideo client 1.
3. The MCVideo server sends a remote video push release request initiated by MCVideo client 1 to MCVideo client 2. The remote video push release request contains MCVideo ID of the source user, the MCVideo group ID of the group X to which the video transmission is to be released.
4. The MCVideo client 2 sends a remote video push release response message to MCVideo server indicating the release of video push to group call.
5. The MCVideo server sends a remote video push release response message to MCVideo client 1 indicating the release of video push to group call.
6. MCVideo client 2 stops the video transmission to the group X and releases the MCVideo broadcast group call on group X remotely initiated by MCVideo client 1.
NOTE: Step 6 can occur before steps 4 and 5.
|
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.3 Off-network video push
| |
f0eca71f00e75c097184182e982221fd | 23.281 | 7.4.3.1 General
| A MCVideo user triggers its MCVideo client to push a video to another MCVideo client.
A MCVideo user triggers its MCVideo client to trigger a remote video push, which requests a second MCVideo client to push a video to a third MCVideo client or to a MCVideo group.
Off-network remote video push works without involving the network.
Off-network video push communications are based on ProSe capabilities as described in clause 7.18.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.