ETSI TS 122 281 V15.1.0 (2018-07)

LTE; Mission Critical Video over LTE (3GPP TS 22.281 version 15.1.0 Release 15)

RTS/TSGS-0122281vf10

General Information

• Status: Published
• Publication Date: 25-Jul-2018
• Technical Committee: 3GPP SA 1 - Services
• Current Stage: 12 - Completion
• Completion Date: 26-Jul-2018

Standards Content (Sample)

TECHNICAL SPECIFICATION
LTE;
Mission Critical Video over LTE
(3GPP TS 22.281 version 15.1.0 Release 15)

3GPP TS 22.281 version 15.1.0 Release 15 1 ETSI TS 122 281 V15.1.0 (2018-07)

Reference
RTS/TSGS-0122281vf10
Keywords
LTE
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2018.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3GPP TS 22.281 version 15.1.0 Release 15 2 ETSI TS 122 281 V15.1.0 (2018-07)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
http://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TS 22.281 version 15.1.0 Release 15 3 ETSI TS 122 281 V15.1.0 (2018-07)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 6
1 Scope . 7
2 References . 7
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 8
4 Overview . 8
4.1 Description of the MCVideo service . 8
4.2 Comparison with the MCPTT service . 9
4.3 Video surveillance . 9
4.4 Group Management/ Communication and Affiliation . 9
4.5 Security . 10
4.6 Confidentiality: . 10
4.7 User identities and inter-working between MCServices . 10
4.8 Non video aspects of the MCVideo service . 10
4.8.1 Relationship with other MCServices . 10
4.8.2 Camera control . 10
4.8.3 Location . 11
4.8.4 Emergency Alert . 11
4.9 Video codecs . 11
5 MCVideo specific requirements . 11
5.1 MCVideo services common for on network and off network . 11
5.1.1 Video characteristics . 11
5.1.1.1 Operational recommendations and requirements for video codecs for the MCVideo service . 11
5.1.1.2 End-user criteria and requirements for the selection of a video codec for MCVideo service . 12
5.1.1.3 Video modes . 13
5.1.1.3.1 Description . 13
5.1.1.3.2 Requirements . 13
5.1.2 Video parameters remote control . 13
5.1.2.1 Remote modification of real time video quality . 13
5.1.2.1.1 Service description . 13
5.1.2.1.2 Requirements . 13
5.1.2.2 Video capabilities information management . 14
5.1.2.2.1 Service description . 14
5.1.2.2.2 Requirements . 14
5.1.3 Video remote control including camera discovery . 14
5.1.3.1 Remote camera control . 14
5.1.3.1.1 Service description . 14
5.1.3.1.2 Requirements . 14
5.1.3.2 Camera discovery . 15
5.1.3.2.1 Service description . 15
5.1.3.2.2 Requirements . 15
5.1.3.3 Communications remote control . 15
5.1.3.3.1 Service description . 15
5.1.3.3.2 Requirements . 15
5.1.4 Video processing capabilities . 15
5.1.4.1 Service description . 15
5.1.4.2 Requirements . 16
5.1.5 Robots video remote control . 16
5.1.5.1 Service description . 16
5.1.5.2 Requirements . 16
ETSI
3GPP TS 22.281 version 15.1.0 Release 15 4 ETSI TS 122 281 V15.1.0 (2018-07)
5.1.6 MCVideo Profile management and administration . 17
5.1.6.1 Service description . 17
5.1.6.2 Requirements . 17
5.1.7 Capabilities additional to MCCoRe . 17
5.1.7.1 Leaving and rejoining an in progress video communication . 17
5.1.7.1.1 Service description . 17
5.1.7.1.2 Requirements . 17
5.1.8 MCVideo capability information sharing . 17
5.1.8.1 Service description . 17
5.1.8.2 Requirements . 18
5.1.9 Video push and pull services . 18
5.1.9.1 Video pull service . 18
5.1.9.1.1 Service description . 18
5.1.9.1.2 Requirements . 18
5.1.9.2 Video push service . 18
5.1.9.2.1 Service description . 18
5.1.9.2.2 Requirements . 18
5.1.10 Video streams availability and characteristics . 19
5.1.10.1 Service description . 19
5.1.10.2 Requirements . 19
5.1.11 Video conferencing . 19
5.1.11.1 Service description . 19
5.1.11.2 Requirements . 19
5.1.12 Additional security requirements for MCVideo . 20
5.1.12.1 General . 20
5.1.12.2 Requirements . 20
5.2 MCVideo services requirements specific to on-network use . 20
5.2.1 Video availability notification . 20
5.2.1.1 Service description . 20
5.2.1.2 Requirements . 20
5.2.2 Replay of stored video . 21
5.2.2.1 Service description . 21
5.2.2.2 Requirements . 21
5.2.3 Video storage control . 21
5.2.3.1 Service description . 21
5.2.3.2 Requirements . 21
5.2.4 Capabilities additional to MCCoRe . 21
5.2.4.1 Service description . 21
5.2.4.2 Requirements . 21
5.2.5 Video control by a dispatcher. 22
5.2.5.1 Service description . 22
5.2.5.2 Requirements . 22
5.2.6 Transmission control. 22
5.2.6.1 Overview . 22
5.2.6.2 Transmission control requirements . 22
5.2.6.2.1 General . 22
5.2.6.2.2 Receiving video streams . 23
5.2.6.2.3 Entering an ongoing video stream . 24
5.2.6.2.4 Video streams reconfiguration and termination . 24
5.2.7 Override . 24
5.2.7.1 Overview . 24
5.2.7.2 General aspects . 24
5.2.8 Communication termination . 25
5.3 MCVideo services requirements specific to off-network use . 26
5.3.1 Private Communication Off-Network . 26
5.3.1.1 Overview . 26
5.3.1.2 Private Communication Off-Network general requirements . 26
5.3.1.3 Private Communication Off-Network commencement requirements . 26
5.3.1.4 Private Communication Off-Network termination . 26
5.3.1.5 Private Communication Off-Network administration . 27
5.3.2 MCVideo Transmission Control Off-Network . 27
5.3.2.1 Overview . 27
ETSI
3GPP TS 22.281 version 15.1.0 Release 15 5 ETSI TS 122 281 V15.1.0 (2018-07)
5.3.2.2 General Aspects . 27
5.3.2.3 Requesting Permission to Transmit . 27
5.3.2.4 Override . 28
5.3.2.5 Terminating Permission to Transmit . 28
5.3.2.6 Transmit Time Limit . 28
5.4 Performance and quality requirements for on-network and off-network . 28
5.4.1 MCVideo device and camera moving at high speed . 28
5.4.1.1 Service description . 28
5.4.1.2 Requirements . 29
5.4.2 Latencies . 29
6 Interworking . 29
6.1 Interworking with non 3GPP video systems . 29
Annex A (informative): Change history . 30
History . 31

ETSI
3GPP TS 22.281 version 15.1.0 Release 15 6 ETSI TS 122 281 V15.1.0 (2018-07)
Foreword
rd
This Technical Specification has been produced by the 3 Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
ETSI
3GPP TS 22.281 version 15.1.0 Release 15 7 ETSI TS 122 281 V15.1.0 (2018-07)
1 Scope
The present document provides the service requirements for operation of the MCVideo service. MCVideo makes use of
capabilities included in Group Communication System Enablers, Proximity Services, Isolated E-UTRAN operation for
Public Safety and Mission Critical Services Common Requirements with additional requirements specific to the
MCVideo Service. The MCVideo Service can be used for public safety applications and also for general commercial
applications (e.g. utility companies and railways). The requirements in this specifications do not apply to GSM or
UMTS.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] Void.
[3] 3GPP TS 22.280: "Mission Critical Services Common Requirements (MCCoRe)".
[4] 3GPP TS 22.179: “Mission Critical Push To Talk (MCPTT); Stage 1”.
[5] 3GPP TS 22.282: “Mission Critical Data services”.
[6] ITU-T Recommendation H.264: Advanced video coding for generic audiovisual services, v2,
2016”.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following
apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP
TR 21.905 [1].
MCVideo Quality: a measure of the distortion or artefacts in a video signal which impacts the ability of a Mission
Critical Organisation to utilise the video for its intended purpose. For example if the purpose of the video is to capture
license plates on vehicles in a range of outdoor conditions, video quality is measured in the ability of the video outputs
to provide the specific information across a range of environmental conditions.
Real Time: Of or relating to systems that update information at the same rate as they receive data, enabling them to
direct or control a process such as video recording and display. Sometimes referred to as live or real life timing of
events.
Real-Time Video: Video viewed at the same time it is being shot.
Robot: A machine that can perform a task automatically or via remote control such as an unmanned vehicle that can be
aerial (e.g., Unmanned aerial vehicle (UAV), aerial drone), aquatic (e.g., unmanned surface vehicle (USV)), submarine,
(e.g., unmanned underwater vehicles (UUV), underwater drone) or terrestrial (unmanned ground vehicle (UGV)).
ETSI
3GPP TS 22.281 version 15.1.0 Release 15 8 ETSI TS 122 281 V15.1.0 (2018-07)
NOTE: Unmanned vehicles typically have a set of sensors to observe the environment, and either autonomously
make decisions about their behavior or pass the information to a human operator at a different location
who controls the vehicle through teleoperation.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
3GPP TR 21.905 [1].
IOPS Isolated E-UTRAN Operation for Public Safety
MCCoRe Mission Critical Services Common Requirements
MCData Mission Critical Data
MCPTT Mission Critical Push to Talk
MCVideo Mission Critical Video
PTZ Pan-Tilt-Zoom
TVNP TV Network Protocol
4 Overview
4.1 Description of the MCVideo service
MCVideo defines a service for Mission Critical video communication using 3GPP transport networks. Mission Critical
refers to meeting the needs of agencies providing Public Safety services such as, but not limited to, Police, Fire and
Ambulance services. Those needs include high reachability, availability and reliability of the service, low latency, real-
time operating capabilities, highly secured operations, inter-operability with other services and systems, private and
group communications, handling of emergencies and ability to provide prioritization, pre-emption, queuing and QoS.
Although the service is designed for transport over commercial and dedicated 3GPP networks it is not expected to be
limited to use over 3GPP networks. However, performance over other transport networks has not been considered when
producing this document.
MCVideo service includes:
- Video capture and encoding of the video information;
- Secure streaming and storing of the video information;
- Video decoding and rendering of the video information;
- Processing of the video information, including the ability to annotate video frames and recognize video
features;
- Mission critical and public safety level functionality (e.g. group sessions, affiliations, end-to-end
confidentiality, emergency type communications) and performance (e.g. low latency);
- Transmission and control of the parameters relevant to those functions;
- Secure operation such that video information can be reasonably un-impeachable when used in evidentiary
procedures;
- Definition and configuration of MCVideo groups and applications;
- Configuration of the MCVideo users' profiles and of the MCVideo UEs; and
- Interoperability with other services and systems.
While the streaming of video is part of the MCVideo Service, the non-real-time or offline transfer of a video clip stored
as a file containing video data is covered by the MCData Service as defined in 3GPP TS 22.282 [5].
An MCVideo video stream can be associated with a stand alone MCVideo group of users, or can be one of the streams
of a multi-media MCX Service group.
ETSI
3GPP TS 22.281 version 15.1.0 Release 15 9 ETSI TS 122 281 V15.1.0 (2018-07)
An MCVideo UE is a device that provides video acquisition (e.g. has a camera), video rendering (has a display) or both
and normally also has some encoding / decoding, communication and storage capabilities.
4.2 Comparison with the MCPTT service
MCVideo makes use of many of the same capabilities that were originally defined for MCPTT in 3GPP TS 22.179 [4]
and now are mostly specified at stage 1 in the MCCoRe specification [3]. Such capabilities include, but are not limited
to, Group Communication, Group Management, Affiliation, Security and Confidentiality. The MCVideo service also
allows the same user to have multiple user profiles defined and to simultaneously use multiple UEs.
However, the MCVideo Service also differs from MCPTT in some respects. In MCPTT there is a specific way of floor
control to assert good order and appropriate use of priority to control and manage situations where multiple users in a
group might attempt to speak at the same time. Simultaneous speech can degrade intelligibility of communications. The
role of floor control is to manage who can transmit at a point in time and who will have to wait to speak to the group. In
MCVideo the control approach is more varied. There is admission control to manage the appropriate access to network
resources according to the user's priority and the UE's capabilities. In some cases, this may include control to restrict
simultaneous video being sent from different users in the group (likely to be useful for network capacity/UE
limitations). From a user perspective there is not the same need to restrict multiple simultaneous transmission and
presentation of video within the same group, as if different streams are available at the UE then the user could choose
which, to look at them simultaneously. It is assumed that users that are permitted to transmit video are generally
allowed to send video to a group, unless there is a network capacity/UE restriction rule that places limitations on the
number of videos to that group. In this case users would be trained in appropriate use of that choice.
The point at which video is transmitted to a group may vary, e.g. a user may press to send video and wait until allowed
by the network to stream to the affiliated group according to the admission control policy. However, the user may be
able to "force" the immediate transmission of the video information, for example, by pressing and holding the button to
send video. In this case the UE will take immediate action to capture the video for onward transmission as soon as
permitted. Also the UE will communicate the immediate nature of the video to the network, which may choose to
authorise the access and then locally store it for onward transmission or stream it immediately to the relevant group. In
this case the video may be slightly delayed due to the start up delay. It is also possible for the user to mark their video
communication as Emergency or Imminent Peril and this will immediately elevate the priority of video communications
for this group above non emergency video.
A further way that MCVideo differs from MCPTT is that group members may be configured not to automatically
receive video. Video may be streamed up to the network and users invited to join when/if convenient/appropriate for
them or only if they have access to a multicast enabled device. An example might be where a Police Officer driving to
an incident is not able to view a video of the events unfolding, but his partner in the car can usefully receive and view
the video. In this case MCVideo working together with MCPTT will provide a powerful solution to know which videos
to receive for those best placed to receive them. This user reception function might be used to late join a video stream or
with the store and forward capability for video.
4.3 Video surveillance
Surveillance cameras could also use the MCVideo service in which case, in addition to the existing video storage and
monitoring activity already used for the surveillance camera, authority may be given to users in the MCVideo system to
connect to, control receive and forward video either to an individual or to a group. Surveillance includes the ability to
locally and remotely activate video streaming automatically or on demand, to control the positioning, optical and video
parameters of the camera and to recognize video features. The camera may be exclusively in the MCVideo system, or it
may be accessed by connection from the MCVideo Service via an existing external interface for surveillance camera
networks. In this latter case, the external interface is expected to provide requests for control and onward streaming of
video, which will be managed together with the normal control network for those cameras. This external interface is
outside of the control of 3GPP and existing standards may be used for part or all of the functionality of this interface
e.g. TVNP.
4.4 Group Management/ Communication and Affiliation
MCVideo group communication aspects are very similar to MCPTT. Each user may be a member of several, even
many, groups. Membership is determined by administration control and provides a user identity based level of authority
to join a group. Each user chooses to affiliate to the groups that they want to receive video communication from. Once a
user has successfully affiliated to a group they will begin to receive video communications directed to that group
according to the video distribution approach used. A user who wishes to send video to a group shall select the relevant
group and then they may send video to it.
ETSI
3GPP TS 22.281 version 15.1.0 Release 15 10 ETSI TS 122 281 V15.1.0 (2018-07)
Groups may interwork with other MCX Service groups, so a single group could be configured for MCPTT and
MCVideo and any other combination of MCX Services. The present document does not describe how that is managed,
it could be a single group with a single affiliate message and separate attributes for each service or it may be different
groups managed together by administrator control and linked in the UE to allow single user action to trigger the same
action e.g. affiliate, for each relevant service. It shall be possible for services actions to be taken independently because
some UE may not be capable of all of the linked services and some users may not be given access to some services or
some groups for some services.
4.5 Security
All MCVideo communications, video and supporting signalling and messaging which start and end entirely within
MCVideo systems are protected by the security mechanisms used for other MCX Services and defined in MCCoRe.
MCVideo communications to and from external end points may be security protected and routed through the normal
MCVideo system and then forwarded into the required network for onward delivery to the external end point.
Alternatively, such communication could just use the protection and routing provided by the transport network. Given
the potential use of stored video information in evidentiary procedures, ensuring the integrity, confidentiality and
accuracy of the video information and its associated meta-data is of paramount importance for MCVideo Data.
4.6 Confidentiality:
MCVideo has the same confidentiality requirements as for other MCX Services and are defined in MCCoRe [3].
4.7 User identities and inter-working between MCServices
All users have a unique identity and at least one alias for other MCServices. A single user can have the same or
different aliases for any and every MCX Service and group that they are members of, but user identities and aliases for
each user resolve to a unique identity even among multiple independent MCX Services in the same domain (e.g. State
or Country. In this way, a user who identifies another user using one service will be able to make contact using a
different service.
For example, multiple groups and multiple Mission Critical organisations working in the same building might use a
map application, which shows them where all the other users are. It should be possible for one user to be able to identify
a nearby user from the map and request a video (via the MCVideo Service) of the situation from a certain vantage in
order to take appropriate action. The other user may be in a combined group for the mapping application (MCData) but
not currently known affiliated in any other group along with the requesting user. User identities requirements are
specified in MCCoRe [3].
It is assumed in the present document that, even when there is no configured inter-service interworking action, the User
ID for any user detected in any MCService can be used to establish video communication to that user, subject to the
user being authorised for the MCVideo Service and the UE being MCVideo capable.
4.8 Non video aspects of the MCVideo service
4.8.1 Relationship with other MCServices
As with MCPTT which has non-speech aspects to the service, in a similar way there are non-video aspects for the
MCVideo service. Many of these services are in common with MCPTT such as Emergency Alert signalling, Location
messaging etc. but some are also distinct such as video camera control (PTZ – Pan, Tilt, Zoom).
It may also be possible for some MCCoRe aspects to work in the same way between MCVideo and MCData, for
example store and forward video.
4.8.2 Camera control
Camera control is specified in MCVideo but it is not intended to define a new PTZ protocol. Where protocols exist,
these should be assumed for MCVideo e.g. TVNP for PTZ although TVNP is unlikely to be the only relevant standard
so there should be provision to use alternative standards according to need.
ETSI
3GPP TS 22.281 version 15.1.0 Release 15 11 ETSI TS 122 281 V15.1.0 (2018-07)
4.8.3 Location
As with other MCServices, from time to time MCVideo Service providing UE location is required. Ideally the same
location messaging for a MCService UE supporting multiple services could be used to update all relevant services at the
same time. Location messaging requirements are defined at stage 1 in MCCoRe specification [3].
4.8.4 Emergency Alert
As with other MCServices, the MCVideo Service will use an Emergency Alert to indicate an emergency state and to
gain transport network priority. When multiple services are operating together it should be configurable whether the
Emergency state of one service affects or not the Emergency state of another service. This situation may be complex to
handle between groups using different services. Operational requirements are defined in the Interworking clause of
MCCoRe specification [3].
4.9 Video codecs
In general, an MCVideo UE can support several video codecs (or video codec operating modes) of which some could
be optional, some could be locally/regionally mandated via regulation, and one is globally mandated via 3GPP implicit
(by reference) or explicit (by detailed specification) standardization as the mandatory universal interoperability video
codec. If MCVideo UEs participate in a video session, they may need to negotiate or rely on defaults or other rules to
establish a common video codec for the video session. Transcoding is not desirable on grounds of complexity and
efficiency and in order to enable end-to-end ciphering.
The MCVideo service supports both combined (for efficiency and synchronization) and separate (for cases when the
video component cannot or will not be received) handling of video and audio streams.
5 MCVideo specific requirements
5.1 MCVideo services common for on network and off network
5.1.1 Video characteristics
5.1.1.1 Operational recommendations and requirements for video codecs for the
MCVideo service
[R-5.1.1.1-001] The video codecs for the MCVideo service should be able to compress/record variable (from very low
to very high) resolution video information acquired in real-time:
- in conditions of varied mobility (from static to highly mobile); and
- in conditio
...