Although MCVideo requires low latency video streams not all video streams need to comply with the same low latency. There are some situations where the latency is less important but it is very important to capture what is visible in front of the camera at the precise time. These different requirements do not necessarily relate to the level of situational Emergency and so there is a difference in a MCVideo service between Emergency and urgency. To avoid dimensioning a service to only cope with the most urgent requirements all the time and to avoid having the user community invoke Emergency just to mark a video as low latency, video modes are introduced.

[R-5.1.1.3.2-001] [R-5.1.1.3.2-002] [R-5.1.1.3.2-003]

Circumstances can affect the quality of the video connection and it should therefore be possible to adapt the video connection parameters to those circumstances in an effective manner. Mission critical control room operators and dispatchers will use video to analyse and control incidents in the field. The dispatcher might need to adapt the video quality to the purpose and for efficient use of 3GPP network resources. In the same way, an incident might be remotely managed by an officer in the field, using videos received from users involved in the incident and other sources. If only an overview of the scene is needed, a low video quality might be all that is needed. If there is a need to read a license plate or to recognize something in the scene, a very high definition video may be required. Those adaptations will have to be done in real time.

[R-5.1.2.1.2-001] [R-5.1.2.1.2-002] [R-5.1.2.1.2-003] [R-5.1.2.1.2-004] [R-5.1.2.1.2-005] [R-5.1.2.1.2-006] [R-5.1.2.1.2-007]

In order to enable remote control of video cameras in the field, there is a need to exchange those video capability parameters and to allow control of a subset of those parameters.

[R-5.1.2.2.2-001] [R-5.1.2.2.2-002] [R-5.1.2.2.2-003] [R-5.1.2.2.2-004] [R-5.1.2.2.2-005]

In addition to video parameters control, there is a need to remotely control the camera views (Pan, Tilt, Zoom). The technical solution need to leverage already existing standards. In addition, a user will need to be able to capture and store video from a remote camera.

[R-5.1.3.1.2-001] [R-5.1.3.1.2-002] [R-5.1.3.1.2-003] [R-5.1.3.1.2-004]

When arriving at an incident and/or affiliating to a group related to the incident, an authorized user wants to discover the cameras he/she can connect to and control. The presence, exact location, addressing information, video coverage area and capabilities of cameras might not always be known to MCVideo Users. However, an authorized MCVideo User might want to discover and establish communication in order to avail himself of the video information provided by such cameras. The MCVideo service might need to control access of various users (or types of users) to different sets of cameras. For example, a remotely located medical expert might be granted access to cameras within ambulances at an incident scene, but not to security surveillance cameras. Within its allowed set of cameras, a user mightwant to find a subset that meets certain criteria. This can be achieved by establishing categories and associating them to various cameras. An interested user could then specify the categories of interest and the MCVideo Service would identify to the user cameras of the specified categories. Examples of categories include certain technical capabilities of the camera (e.g. self-activated camera, wide field of view etc.)and areas of use (traffic, security surveillance).

[R-5.1.3.2.2-001] [R-5.1.3.2.2-002] [R-5.1.3.2.2-003] [R-5.1.3.2.2-004]

Authorized users will need to be able to remotely control video communications.

[R-5.1.3.3.2-001] [R-5.1.3.3.2-002] [R-5.1.3.3.2-003] [R-5.1.3.3.2-004]

Considering that video distribution will take significant amount of resources, and considering an operational user may in many cases not be available to watch a video, the system needs to provide an efficient means to manage entering and leaving video communications.

[5.1.7.1.2-001] [5.1.7.1.2-002] [5.1.7.1.2-003] [5.1.7.1.2-004] [5.1.7.1.2-005] [5.1.7.1.2-006]

Users need the capability to pull a video from a source which might be a UE in the field, or a video storage server . In this service, a user requests another user to transmit a video stored or directly taken from the camera.

[R-5.1.9.1.2-001]

Users need the capability to push a video to another user.

[R-5.1.9.2.2-001] [R-5.1.9.2.2-002] [R-5.1.9.2.2-003] [R-5.1.9.2.2-004] [R-5.1.9.2.2-005] [R-5.1.9.2.2-006] [R-5.1.9.2.2-007] [R-5.1.9.2.2-008] [R-5.1.9.2.2-009] [R-5.1.9.2.2-010]