Web Analytics
Welcome New MEF Members
 
Inquiries: +1 310-642 2800

MEF has published 60 technical specifications and implementation agreements that effect communication service and technology interoperability, increase operational efficiency, and accelerate industry innovation. Current MEF 3.0 standards work is designed to enable agile, assured, and orchestrated communications services across a global ecosystem of automated networks.

Recent MEF Specifications

Specifications published by MEF are intended for general distribution to the public and may be downloaded from this site and reproduced without charge. Any reproduction of MEF documents shall contain the following statement: "Reproduced with permission of MEF Forum." All rights granted to MEF under applicable copyright laws are expressly reserved. No permission is granted to any recipient or user of MEF publications to modify any of the information contained therein and MEF disclaims all responsibility and liability for such modifications. Most specifications are introduced by a Powerpoint overview presentation that gives background and explanations that are in addition to the normative definitions in the specifications. The superseded specifications are included at the foot of the table.

All MEF Specifications

Filter:

Service Definitions
Specification # Description Overview Specification

6.2

Uses the service attributes and parameters that are defined in the MEF “Ethernet Services Attributes Phase 2” and applies them to create different Ethernet services. This document defines three generic service constructs called Ethernet Service types and specifies their associated service attributes and parameters used to create Point-to-Point, Multipoint-to-Multipoint, and Rooted-Multipoint Ethernet services. It defines the Ethernet Services (EPL, EVPL, E-Line, E-LAN, E-Tree, etc.) with Service Attributes and parameters as specified in MEF 10.3, “Ethernet Services Attributes” and in MEF 45, “Multi-CEN Layer 2 Control Protocol”

Document

8

Gives precise instructions for implementing interoperable CES equipment that reliably transport TDM circuits across Carrier Ethernet Networks while meeting the required performance of circuit emulated TDM services as defined in ITU-T and ANSI TDM standards

Document Document

22.3

This document identifies the requirements for MEF Ethernet Services and MEF External Interfaces (EIs such as User-Network Interface (UNI)s) for use in Mobile Backhaul networks based on MEF specifications. In addition, new interface and service attributes have been specified where needed. The services and requirements in this Implementation Agreement (IA) are based on the services defined in MEF 6.2, MEF 33 and MEF 51, as well as the attributes in MEF 10.3, MEF 26.2 and this IA. The aim is to be flexible to support a wide range of Ethernet service based mobile network deployments.

Document

33

Defines Ethernet Access Services, ENNI to UNI Carrier Ethernet services in contrast to the EVC-based (UNI to UNI) services which are defined in MEF 6.1

Document Document

43

Specifies the functionality offered by an Access Provider (AP) that, when combined with an Ethernet-Access (E-Access) Service, allows a Service Provider (SP) to monitor and configure selected objects associated with a given UNI and one or more OVC End Points at that UNI in the AP’s network.

Document

47

This document identifies the requirements for MEF Ethernet Services and MEF External Interfaces (EIs such as UNIs) as well as a management interface for use in support of Cloud Services.

Document

51

This document specifies Operator Virtual Connection (OVC) Services based mainly on the service attributes defined in MEF 26.1; there are also some service attributes defined in this document that go beyond MEF 26.1.

Document

62

This Implementation Agreement (IA) defines an Access E-Line Service that includes a specific set of management and Class of Service capabilities. The service defined in this IA is based on applicable functionality and associated requirements from existing MEF specifications.

Document
Service Attributes
Specification # Description Overview Specification

10.3

The attributes of Ethernet Services observable at a User Network Interface (UNI) and from UNI-to-UNI are defined. In addition, a frame-work for defining specific instances of Ethernet Services is described. These are used in MEF 6.1

Document
 

10.3.1

This amendment makes the following changes to MEF 10.3: section 8.8.7 is added to define the Composite Performance Metric, new terms are added to Table 1 of MEF 10.3., a new entry is added to Reference of MEF 10.3., and a new appendix is added to MEF 10.3 as Appendix D.

Document
 

10.3.2

This document amends MEF 10.3 to enhance the UNI Resiliency Service Attribute to include multiple physical links that can carry different Service Frames simultaneously at a UNI.

Document Document

23.2

This Implementation Agreement formalizes the CoS Name and defines three specific CoS Names called Class of Service Labels (CoS Labels). This IA also provides guidelines for CoS Names, in general, in terms of how the performance objectives for OVCs are composed into performance objectives for EVCs.

Document Document
 

23.2.1

This amendment makes the following changes to MEF 23.21:

  • Changes are made to Section 8.6.1 of MEF 23.2 to generalize certain requirements to apply to CoS Names instead of just CoS Labels.

  • A new normative section is added that defines a set of token sharing Bandwidth Profile models. These models allow for multiple Bandwidth Profile Flows in an Envelope thus enabling token sharing among the Bandwidth Profile Flows.

  • New terms are added to the Terminology table of MEF 23.2

  • A new appendix is added that describes use cases for the defined token sharing Bandwidth Profile models.

Document

26.2

This document contains specifications for interconnecting Operator CENs in order to support MEF Forum Ethernet Services. This Technical Specification specifies:

  • The requirements at the ENNI reference point as well as the interface functionality in sufficient detail to ensure interoperability between two Operator CENs.
  • The connectivity attributes UNI to UNI, UNI to ENNI, and ENNI to ENNI such that multiple Operator CENs can be interconnected and the Ethernet services and Service Attributes in MEF 6.2, MEF 10.3, and MEF 51 can be realized.
  • The concept of the Super Operator which allows an Operator, acting as a Super Operator, to combine multiple Operator CENs together and make them appear as a single Operator CEN to a Service Provider or another Super Operator
Document

41

This document specifies a Generic Token Bucket Algorithm based on the Bandwidth Profile Algorithm specified in MEF 10.3 It is expected that other documents can reference this specification for describing new Bandwidth Profiles and methods for regulating the use of
other resources.

Document

45

This document specifies the service attributes and requirements for handling Layer 2 Control Protocol (L2CP) Frames in a Carrier Ethernet Network.

Document
 

45.0.1

Amendment to MEF 45: OVC Services Requirements for L2CP
Document

61

This document specifies the Service Attributes that need to be agreed between a Service Provider and a Subscriber for IP Services, including IP VPNs, cloud access1 and Internet access. Some key concepts are introduced, including IP UNIs, IP Virtual Connections, IP Virtual Connection End Points and IP UNI Access Links. Specific Service Attributes and corresponding behavioral requirements are defined for each of these entities. These include support for assured services, e.g. multiple Classes of Service, performance objectives specified in a Service Level Specification, and Bandwidth Profiles.

Document

63

The attributes of a Subscriber Layer 1 Service observable at a Layer 1 User Network Interface (L1 UNI) and from a L1 UNI to a L1 UNI are defined. In addition, a framework for defining specific instances of a Subscriber Layer 1 Service is described.

Document
Architecture
Specification # Description Overview Specification

2

Defines a broad frame work for hop-by-hop and end-to-end service level protection.

Document Document

3

Circuit Emulation Service “tunnels” TDM traffic through a Carrier Ethernet network allowing inclusion of legacy networks within a Carrier Ethernet environment

Document Document

4

Introduces the framework and terminology for the services (Eth) layer

Document Document

11

Defines a split demarcation function between the customer (Subscriber), and the Service Provider

Document Document

12.2

Defines the architecture framework to model the Ethernet Services Layer of MEF compliant Carrier Ethernet Networks.

Document Document

13

This allows existing Ethernet devices (switch, router, workstation, etc) acting as Customer Edge devices to be compliant to this IA with no additional software or hardware upgrades

Document Document

20

Specifies MEF UNI characteristics and operation in which customer side of the UNI is automatically configured by the network side of the UNI allowing verification of SLA and UNI connectivity. Additional objectives include support for Ethernet OAM (802.3ah, 802.1ag) over the UNI. Required for support of ELMI

Document Document

29

Defines an abstract set of Ethernet Service Constructs that are widely applicable regardless of how the UNI-to-UNI Network may be sugmented by providers

Document

32

Contains requirements for protecting Ethernet Services at an External Interface against link or a Network Element (NE) failure. This specification identifies resiliency requirements at external interfaces applicable to MEF Service and associated Service End Points.

Document Document
Information and Data Models
Specification # Description Overview Specification

7.3

This model identifies and defines the information necessary to manage the Carrier Ethernet services as defined by the MEF, including EVC and OVC services. This model is intended to mediate between a product information model and a resource information models, roughly following the TMF SID. This model can be used as the basis for LEGATO Interface Profiles defining APIs for managing Carrier Ethernet services.

Document
  MEF_7.3_UML.rar   Document

31

Service OAM Fault Management Definition of Managed Objects (SNMP)
Document Document
  MEF_31_MIBs.zip   Document
 

31.0.1

Amendment to Service OAM SNMP MIB for Fault Management
Document Document
    MEF_31.0.1-SOAM-TC-MIB.zip   Document

36.1

Specifies the Performance Monitoring(PM) SNMP Management Information Base(MIB) necessary to manage Service OAM implementations that satisfy the Service OAM requirements and framework specified by MEF 17.

Document Document
  MEF_36.1-SOAM-PM-MIB.zip   Document

38

Specifies the Fault Management (FM) YANG Modules necessary to implement the Service Operations, Administration, and Maintenance (OAM) that satisfies the Service OAM requirements and framework specified by MEF 17.

Document Document
  MEF_38_YANG_CFM_SOAM_FM_Modules.zip   Document

39

Specifies the Performance Monitoring(PM) YANG Module necessary to satisfy the Service OAM requirements and framework specified by MEF 17.

Document Document
  MEF_39_YANG_SOAM_PM_Module.zip   Document

40

Specifies the User Network Interface (UNI) and Ethernet Virtual Connection (EVC) Management Information Base (MIB) necessary to configure and monitor the UNI and EVC.

Document Document
  MEF_40_MEF-UNI-EVC-MIB.zip   Document

42

Specifies the External Network Network Interface (ENNI), Operator Virtual Connection (OVC), and Virtual User Network Interface (VUNI) Management Information Base (MIB) necessary to configure and monitor the MEF ENNI, OVC, and VUNI.

Document
  MEF_42_MEF-ENNI-OVC-MIB.zip   Document

44

Specifies the Virtual NID (vNID) Management Information Base (MIB) necessary to configure and monitor the MEF vNID functionality that satisfies the requirements and definitions found in MEF 43 (vNID) by the Service Provider (SP).
Document
  MEF_44_MEF-VNID-MIB.zip   Document

56

This Interface Profile Specification specifies Legato Management Interface in support of MEF 6.2 Services and is a realization of relevant classes from MEF 7.3 Information Model. The LEGATO_SCA Interface is for use at a Service Orchestrator Function for interfacing with Business Applications as described in MEF LSO RA and process for Service Configuration & Activation.

Document
  MEF 56.zip   Document

58

This document specifies the YANG modules for MEF 6.2 EVC based Services and MEF 10.3 Ethernet Services Attributes. These modules are for use in Service Orchestration Function (SOF) and to communicate the configuration state for Service attributes and values with other entities, such as Business Applications or Partners or Customers, specified in MEF 55 Lifecycle Ser-vice Orchestration Reference Architecture. One use of these modules is for the use cases at Le-gato reference point for Service Configuration and Activation (SCA) specified in MEF 56 SCA (Legato) Interface Profile specification. The elements of the YANG modules are aligned with the objects identified in MEF 7.3 Carrier Ethernet Service Information Model.

Document
  MEF 58-Legato-YANG-MachineFiles.zip   Document

59

Lifecycle Service Orchestration Reference Architecture (LSO RA, MEF 55) extends the traditional MEF scope concerning Service Modeling, from a pure view “from outside the network” to cover a range of Operational, Orchestration, and Network Management behaviors, including SDN and NFV paradigms.

In support to MEF 55, NRM IM is then defined to manage the Network Infrastructure, through SDN Controllers, WAN Controllers, OTN Subnetwork Managers, and other legacy Network Management Systems.

Document

60

This Interface Profile Specification defines the Presto Management Interface for the network control and management domain in support of [MEF 6.2] and [MEF 51] Services and is a specialization of relevant classes from the MEF NRM (Network Resource Model). The Presto NRP (Network Resource Provisioning) Interface is for use by a Service Orchestration Functionality (SOF) as described in [MEF 55] and in support of processes for Service Configuration and Activation [MEF 56] at the network resource layer.

The Presto NRP requests ICM to create connectivity or functionality associated with specific Service Components of an end-to-end Connectivity Service within the domain managed by each ICM. Presto may also allow the ICM to describe Resources and capabilities it can instantiate.

Document
Service Activation and Test
Specification # Description Overview Specification

46

This specification defines the protocol and functionality for Latching Loopbacks (LLs) for Service Activation Testing (SAT) and troubleshooting up to the Information Rate for point-to-point and multipoint services across multiple Carrier Ethernet Networks (CENs).

Document

48

This document specifies the requirements and use cases for Carrier Ethernet Service Activation Testing (SAT) for E-Access services (Access Ethernet Private Line (Access EPL) and Access Ethernet Virtual Private Line (Access EVPL)) as defined in MEF 33. Service Activation Testing encompasses those business processes for testing MEF services to ensure that the service is configured as specified and meets the defined Service Acceptance Criteria (SAC). Service Activation Testing occurs after the Operator Virtual Connection (OVC) for an E-Access service has been provisioned and before the service is deployed to the customer.

Document

49

This document standardizes the following: The test PDUs that are exchanged between devices during the test, the control protocol used to configure SAT test, and the control PDUs that are exchanged between the devices in two operators’ networks.

The control protocol provides the ability to configure and control the SAT steps and to fetch test results at the completion of the test. The requirements defined within this document are based on the SAT process as defined in section 10 of the Carrier Ethernet Service Activation Testing Technical Specification (MEF 48).

Document
 

49.0.1

Amendment to Service Activation Testing Control Protocol and PDU Formats
Document
SOAM Fault and Performance Management
Specification # Description Overview Specification

17

Provides requirements to be satisfied by the Service OAM mechanisms in MENs and framework for discussing and implementing those mechanisms. It also provides context for several MEF specifications (UNI type 2 and E-NNI) and the work of other standards bodies

Document Document

30.1

Implementation Agreement (IA) for Service Operations, Administration, and Maintenance (OAM) that builds upon the framework and requirements specified by MEF 17. In particular, specifying Service OAM requirements for Maintenance Entity Groups (MEGs) and for Fault Management(FM).

Document Document
 

30.1.1

Amendment to SOAM FM IA
Document

35.1

Specifies an Implementation Agreement for Service Operations, Administra-tion, and Maintenance (SOAM) that satisfies and extends the Performance Monitoring(PM) framework and requirements described in MEF 17.

Document Document
Element Management
Specification # Description Overview Specification

15

Specifies the network management requirements to be met by Network Elements supporting Ethernet Service Phase 1

Document Document

16

Enables customer equipment to receive information regarding the status and attributes of Ethernet Services thus allowing automatic configuration and improved Subscriber network performance

Document Document
MEF Service Lifecycle
Specification # Description Overview Specification

50.1

This document specifies process flows for the Third Network lifecycle, including Product Service Resource (PSR) Definition Lifecycle and Product Service Resource (PSR) Instance Lifecycle, examined from the perspective of external commercial product considerations and internal service and resource considerations. In addition, we examine these areas from the perspectives of TM Forum’s Strategy Infrastructure Product Lifecycle and Operations Lifecycle.

Document

52

This specification documents a Carrier Ethernet service performance reporting framework in which Carrier Ethernet Network (CEN) Operators provide their Subscribers with access to Key Performance Indicators (KPIs) and statistics reporting through a standardized interface.

Document

53

This document specifies the processes, use cases and guidelines for a standardized MEF Carrier Ethernet Services Qualification Questionnaire that can be used by potential buying carriers to more efficiently find a selling carrier that matches their needs. The questionnaire will encompass MEF defined services and process alignment (quote/order/delivery/assurance/billing/etc) information.

Document Document
  MEF-53-Ethernet-Services-Qualification-Questionnaire.xlsx   Document

54

This document is intended to act as an Implementation Agreement for any Operator interested in connecting their Carrier Ethernet network to another Operator using an Ethernet ENNI.
Document Document

55

LSO is an agile approach to streamlining and automating the service lifecycle in a sustainable fashion for coordinated management and control across all network domains responsible for delivering an end-to-end Connectivity Service (e.g., Carrier Ethernet, IP VPN, MPLS, etc.). This document describes a Reference Architecture and Framework for orchestrating the service lifecycle.
Document
 

55.0.1

This document is an amendment to Lifecycle Service Orchestration (LSO) Reference Architecture (RA), MEF 55. The changes to MEF 55 are:

  • Changes to Section 3 (Terminology) and Section 10 (Operational Threads for LSO)
Document
 

55.0.2

This document is an amendment to Lifecycle Service Orchestration (LSO) Reference Architec- ture (RA), MEF 55. The changes to MEF 55 are:

  • Changes to Section 3 (Terminology), Section 7.2 (Information Model), 7.3 (Business Process Flows) and Section 12 (References)
  • New Appendix describing TOSCA Service Templates for deployment of MEF Services and the relevant MEF LSO entities that could use such templates. Additionally, example TOSCA Node Types and TOSCA Topology are provided for illustration purposes.
Document

57

This document represents the cumulative work between MEF and ATIS Ordering and Billing Forum (OBF) to identify the common ordering attributes and processes needed to support inter-carrier Product Ordering of Ethernet Services worldwide. This document supports the requirements defined in the MEF Lifecycle Service Orchestration (LSO) Reference Architecture and Framework (MEF 55, “LSO RA”) requirements for Ordering over the Sonata interface (Service Provider <-> Partner interactions). Information contained within this document will be utilized by both Buyer and Seller ordering systems for the development of automated API systems.

Document
Abstract Test Suites
Specification # Description Overview Specification

9

Defines the test suite for conformance of Ethernet services and equipment when deployed at the UNI. This is one of the two foundational documents of the CE 1.0 Certification Program.

Document Document

14

Defines the requirements and corresponding test procedures for Service Performance and Bandwidth Profile Service Attributes that may be specified as part of a Service Level Specification (SLS) for an Ethernet Service. This is one of the two foundational documents of the CE 1.0 Certification Program.

Document Document

18

Specifies testing procedures for pass/fail assessment of conformance with each of the operating modes in MEF 8.

Document Document

19

Supplements the MEF test specifications MEF 9, and MEF 14 with test procedures for UNI manual configuration mode defined in MEF 13

Document Document

21

The Link OAM part of the Abstract Test Suite for UNI Type 2 describes test procedures based on a combination of the requirements for Link OAM described in MEF 20, etc.

Document Document

24

Defines test procedures based on a combination of requirements for E-LMI described in MEF 20

Document Document

25

Defines test procedures based on a combination of requirements for Service OAM described in MEF 20

Document

27

Defines test procedures based on requirements for UNI Type 2 described in MEF 20

Document

34

Defines test procedures for testing and certification of Ethernet Access (E-Access) Services namely Access EPL and Access EVPL deployed service provider networks. The test cases are based on requirements defined in MEF 33 and MEF 23.1

Document

37

Defines Abstract Test Suite for External Network Network Interface (ENNI) in accordance with the requirements and service attributes specified in the ENNI (MEF 26.1)

Document
Superseded MEF Specifications
Specification # Description Superseded
by MEF
Overview Specification

1

Ethernet Services Model Phase I
10 Document

5

Traffic Management Phase 1
10 Document

6

Metro Ethernet Services Definitions Phase 1
6.1 Document

6.1

Metro Ethernet Services Definitions Phase 2
6.2 Document Document

6.1.1

Layer 2 Control Protocol Handling Amendment to MEF 6.1
45 Document

7

EMS-NMS Information Model
7.1 Document Document

7.1

Phase 2 EMS-NMS Information Model
7.2 Document Document

7.1.1

Technical Corrections to MEF 7.1
7.2 Document

7.2

Carrier Ethernet Information Model
7.3 Document Document

10

Ethernet Services Attributes Phase 1
10.1 Document Document

10.1

Ethernet Services Attributes Phase 2
10.2 Document Document

10.1.1

Amendment to MEF 10.1 Ethernet Services Attributes Phase 2
10.2 Document

10.2

MEF 10.2 Ethernet Services Attributes Phase 2
10.3 Document Document

10.2.1

Performance Attributes Amendment to MEF 10.2
10.3 Document

12

Metro Ethernet Network Architecture Framework Part 2: Ethernet Services Layer
12.1 Document

12.1

Carrier Ethernet Network Architecture Framework Part 2: Ethernet Services Layer - Basic Elements
12.2 Document Document

12.1.1

Network Architecture Framework Part 2: External Interface Extensions
12.2 Document

22

Mobile Backhaul Implementation Agreement (2/09)
22.2 Document

22.1

Mobile Backhaul Phase 2 Implementation Agreement
22.2 Document Document

22.1.1

Amendment to MEF 22.1 – Small Cell Backhaul
22.2 Document Document

22.2.1

Mobile Backhaul Phase 3 - Amendment 1: Time Synchronization
22.3 Document Document

22.2

Mobile Backhaul Phase 3 Implementation Agreement
22.3 Document Document

23

Class of Service Phase 1 Implementation Agreement
23.1 Document

23.1

Class of Service Phase 2 Implementation Agreement
23.2 Document Document

26

External Network to Network Interface (ENNI) Phase I
26.1 Document Document

26.0.1

Corrected Figure 10 for MEF 26
26.1 Document

26.0.2

OVC Layer 2 Control Protocol Tunneling Amendment to MEF 26
26.1 Document

26.0.3

Service Level Specification Amendment to MEF 26
26.1 Document

26.1

External Network Network Interface (ENNI) Phase 2
26.2 Document Document

28

External Network Network Interface (ENNI) Support for UNI Tunnel Access and Virtual UNI
26.2 Document Document

30

Service OAM Fault Management Implementation Agreement
30.1 Document Document

35

Service OAM Performance Monitoring Implementation Agreement
35.1 Document Document

35.0.1

SOAM PM Implementation Agreement Amendment (TCA)
35.1 Document Document

35.0.2

SOAM PM Implementation Agreement Amendment-2 (1SL)
35.1 Document Document

36

Service OAM SNMP MIB for Performance Monitoring
36.1 Document Document

50

Service Operations Guidelines
50.1 Document Document
OpenCloud Connect
Specification # Description Overview Specification

OpenCloud Connect Reference Architecture
Document
IMTC Specifications
Specification # Description Overview Specification

Document Number Title Date Description Download
IMTC 1015 SIP Video Profile Best Practices 11 March
2016
The document defines the SIP Video Profile, covering bandwidth, flow control, and intra-frame request use cases and proposed best practices. Download
IMTC 1013 SIP Video Profile Best Practices 03 October
2014
The document defines the SIP Video Profile, covering bandwidth, flow control, and intra-frame request use cases and proposed best practices. This revised version introduces clarifications to improve interworking with IMS/3GPP implementations Download
IMTC 1012

SIP Video Profile Best Practices

6 February
2013

The document defines the SIP Video Profile, covering bandwidth, flow control, and intra-frame request use cases and proposed best practices

Download

Working Group Documents

These protocol specifications describe how to multiplex multiple screens, multiple audio streams, and an auxiliary-data screen into respective Real-Time Transport Protocol (RTP) flows using a multiplexing technique.

 

The TIP protocol specification also defines how RTP Control Protocol (RTCP) based extensions are used to indicate attributes of media flows as they are initiated. It also defines how endpoints and other devices can provide feedback or identify adjustments during the life of the streams.

 

Click here for more details

This document contains a specification for the transport of H.264/MPEG-­4 Part 10 Advanced Video Coding Annex G (Scalable Video Coding) [1] bitstreams in unified communication applications.

The goal of this specification is to support the use of AVC and SVC video in the entire gamut of unified communications applications that use video. Targeted application scenarios thus include low-­end mobile phone video chat, all the way to high-­‐end multi-­‐monitor telepresence systems.

This specification assumes that the reader is familiar with the H.264/MPEG-­4 Part 10 AVC standard specification and its Scalable Video Coding (SVC) extension specified in Annex G. In the following, the term ‘AVC’ refers to the H.264/MPEG‐4 Part 10 specification excluding the scalability features of Annex G, whereas ‘SVC’ refers specifically to systems that use the scalability features.

Document

This document contains a specification for H.264/MPEG-4 Part 10 Advanced Video Coding(AVC) Modes for real-time point-to‐point and multipoint conferencing products.

The goal of this specification is to support the use of AVC and SVC video in the entire gamut of unified communications applications that use video. Targeted application scenarios thus include low-end mobile phone video chat, all the way to high-end multi‐monitor telepresence systems.

This specification assumes that the reader is familiar with the H.264/MPEG-4 Part 10 AVC standard specification and its Scalable Video Coding (SVC) extension specified in Annex G. In the following, the term ‘AVC’ refers to the H.264/MPEG-4 Part 10 specification excluding the scalability features of Annex G, whereas ‘SVC’ refers specifically to systems that use the scalability features.

Document

Specification of Interoperable Scalability Modes for the HEVC Video Coding Standard for Unified Communication Applications
Document

Specification of Interoperable Scalability Modes for the HEVC Video Coding Standard for Unified Communication Applications (Obsolete)
Document

 

SCROLL TO TOP