OC-SP-AMD-I01-130502：开放有线电视测量规范

需积分: 5 47 浏览量更新于2024-07-09 收藏 1.58MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

资源详情

资源推荐

OC-SP-AMD-I01-130502 OpenCable™ Specifications

8 CableLabs



05/02/13

There are three fundamental entities involved:

• Affiliates – Service providers may send a variety of data products to any number of affiliates, including

content owners, audience measurement firms, research firms, agencies/advertisers, and programmers.

Ideally, the affiliates consume data in Audience Measurement Interface (AMI) format, accessing it through

the enterprise-level interfaces.

• Data Collection and Processing Platforms – The essential role is to store, aggregate, and process low-

level event streams from Media Delivery Platforms. This role is the responsibility of a service provider,

although agents of a service provider may implement some of these logical functions. Ideally, these

platforms collect Media Event Data Model (MEDM) data elements, process it, and deliver Media

Measurement Data Model (MMDM) data elements.

• Media Delivery Platforms – A device or system that supports navigation/discovery, processing, or

presentation of media to viewers, including traditional STBs, DVRs, VOD servers, and emerging platforms

such as IP streaming servers servicing video gateways, PCs, mobile, and tablet devices. Media Delivery

Platforms also include interactive environments, such as EBIF, tru2way, and other application platforms.

Ideally, these platforms generate MEDM data elements.

These entities process data in well-defined ways and share information through specified interfaces. The four areas

of specification are:

• Enterprise-level Measurement Interfaces – These are formats and interfaces that serve to provide access

to data at the enterprise level, between service providers and the affiliates of their choosing. Data access

may be via a data representation, encoded format, or other means.

• Processing Rules – This is a set of rules governing how media event data is processed to support

enterprise-level interfaces and data products. Requirements on data collection and processing platforms in

support of these rules, such as data retention, auditing, security, and privacy, may be included here.

• Media Event Data Model (MEDM) – Media Delivery Platforms generate low-level events that should

conform to a well-defined MEDM in order to support cross-platform comparability. Media Delivery

Platforms may evolve to support the MEDM directly, or “adapters” may transform existing proprietary

formats into these well-known models. Media Event Data Models will be developed for linear, non-linear,

and interactive service delivery models. Included in these specifications are “cap and edit” rules that define

some level of business logic applied to the low-level events.

• Media Measurement Data Model (MMDM) – Media events are collected, filtered, enriched,

transformed, and correlated, resulting in data ready for making measurement calculations. This processing

is unique to each service provider, and the details relating to the internal collection and processing of the

media events into measurement data are outside the scope of this document. However, consistent

definitions of measurements are necessary, as this data is foundational to deriving data products including

metrics.

• Audience Measurement Interface (AMI) – Further aggregation and processing of measurements results

in metrics that can be delivered to affiliate consumers and can be used to determine effectiveness and

revenue models.

• Platform Interfaces – Platform Interface specifications, including transport protocol and data format

definitions, will be developed for many Media Delivery Platforms. These interfaces can ensure data quality

and comparability, and all implementations should conform to the MEDM. Conformance can lead to cost-

effective product implementations and integrations. For those Media Delivery Platforms that do not

implement a well-defined interface, a proprietary adapter should be developed to define conformance with

the MEDM. An adapter defines how a data format maps to the MEDM. In practice, a Data Collection and

Processing Platform may physically store data in an implementation-specific way. The Data Collection and

Processing Platform should conform to the MEDM so Processing Rules can result in deterministic results

independent of the source or format of the data collected via the Platform Interfaces.

OC-SP-AMD-I01-130502 OpenCable™ Specifications

10 CableLabs



05/02/13

6 EVENTS - MEDIA EVENT DATA MODEL (MEDM)

The Media Event Data Model (MEDM) defines a model for events related to the delivery, processing, or

presentation of media to viewers, such as tuning to a broadcast channel, selecting and controlling an on-demand

asset, or recording to a DVR. The data model is generalized to express any linear and non-linear service, including

but not limited to DVR and home networking, mobile, and online content delivery.

The Media Event Data Model is defined by contextual, conceptual, and logical models describing increasing levels

of detail of the model. The conceptual and logical models are described by a UML entity-relationship diagram with

accompanying narrative description of the entities. The logical model is presented in a subsequent section.

Many encoding formats and transport protocols may be defined that conform to the model. Differing circumstances

will dictate optimal interfaces for gathering or sharing measurement data. For instance, an enterprise-level interface

that exports huge volumes of data from a service provider to an affiliate can look very different from the mechanism

used to log and transmit events from an embedded device on a constrained legacy cable network. Regardless of the

encoded formats of the data, they should conform to this data model to support cross-platform comparability.

6.1 Conceptual Data Model

Figure 5 is the conceptual level entity-relationship diagram for media events. No attributes are presented in this

diagram; the discussion below is of entities only. Full discussion of these entities and associated attributes is

included in the detailed logical data model defined below.

The base entity is the MediaEvent. The various event entities all extend the base MediaEvent entity. For clarity,

MediaEvent is not shown in the diagram. In practice, a stream of MediaEvents is generated by a device that delivers

processes or presents media. MediaEvents are then collected by a service provider or designated agent. Data coming

from a specific device, such as a set-top box or VOD server, may not fully populate the data model, and some

attributes may be sourced from service-provider Reference or Enrichment data. For instance, a set-top box interface

may not include any information about a viewer. The association of data from a set-top box and the viewer

information may be made by the service provider after the data is collected from the set-top box or when exposing

data via the Media Event Data Model.

Figure 5 - MEDM Conceptual Data Model

Audience Measurement Data Specification OC-SP-AMD-I01-130502

05/02/13 CableLabs



6.1.1 MEDM Entities

Table 1 - MEDM Entity Descriptions and Relationships

MEDM Entity Entity Description Entity Relationships

Media Viewer

The MediaViewer entity represents a viewer of media

content. Media viewers may be known to the service

provider, in which case an associated Media Viewer

Type is referenced.

A MediaViewer belongs to a single

household. The MediaViewer has

many media events associated with

it.

Media Viewer

Type

The MediaViewerType entity provides descriptive

information about known Media Viewers.

The MediaViewerType may

represent either an entire

household or a specific viewer in a

household and has MediaViewers

assigned to it.

Session Start

Event

The SessionStartEvent is a specialization of MediaEvent

and inherits all of its attributes.

Session is a general term indicating a linear TV channel

or a non-linear video segment.

Session start is a generalized representation of the

initiation of media processing, which may indicate

selection of a linear broadcast channel, or the start of a

non-linear session. Non-linear sessions may be

supported by many environments, such as traditional

cable VOD, Digital Video Recorder (DVR), Web-based

video playout, home networked streaming, or any other

non-broadcast media processing environment. Every

SessionStartEvent SHALL be paired with a

SessionEndEvent, grouping all intermediate events into

a logical session sequence.

An instance of a SessionStartEvent

is associated with a MediaViewer

whose actions generated the event.

It is also associated with the single

MediaDevice that actually

generated the event.

Session End Event

SessionEndEvent is a specialization of MediaEvent that

represents the termination of media processing. Session

termination may represent tuning away from a linear

channel, the end of a DVR recording, or the termination

of a non-linear session.

An instance of a SessionEndEvent

is associated with a MediaViewer

whose actions generated the event.

Is also associated with the single

MediaDevice that actually

generated the event.

Presentation State

Event

PresentationStateEvent is a specialization of

MediaEvent that represents a change in the presentation

attributes of a media presentation. Examples include a

switch from the main display to picture-in-picture (PiP)

on a TV, scaling the video window on a TV, muting

audio, bringing an active DVR recording to the

foreground, or another such change.

PresentationStateEvents SHALL be generated with

every SessionStartEvent.

An instance of a

PresentationStateEvent is

associated with a MediaViewer

whose actions generated the event.

Is also associated with the single

MediaDevice that actually

generated the event.

OC-SP-AMD-I01-130502 OpenCable™ Specifications

12 CableLabs



05/02/13

MEDM Entity Entity Description Entity Relationships

Segment Event

SegmentEvent is a specialization of MediaEvent that

represents the processing of a logical segment of

content. For example, as the boundaries between

entertainment and advertising segments are crossed,

SegmentEvents MAY be generated to indicate these

boundary crossings. The MediaOffset attribute found in

all MediaEvents between SegmentEvents are offsets

within the ContentID identified by the SegmentEvent.

Boundaries may be identified by in-band signals, such

as SCTE 35 markers, or by schedule metadata.

An instance of a SegmentEvent is

associated with a MediaViewer

whose actions generated the event.

Is also associated with the single

MediaDevice that actually

generated the event.

Play Control Event

PlayControlEvent is a specialization of MediaEvent that

represents a trick mode event during presentation of

non-linear content. A transition from presenting linear

content live to presenting from a time-shift buffer is

considered a transition to non-linear content. Trick

modes include pause and skip. Skip can be used to

model forward and backward play at any speed.

An instance of a PlayControlEvent

is associated with a MediaViewer

whose actions generated the event.

Is also associated with the single

MediaDevice that actually

generated the event.

App State Event

AppStateEvent is a specialization of MediaEvent that

represents the loading, launching, suspension, or

termination of an interactive application. Examples of

interactive applications are ETV or OCAP applications.

Not addressed here is application instrumentation, which

is the collection of application level clickstream events

used to interpret viewer behavior within the context of

an application (for example, companion applications).

An instan

ce of an AppStateEvent is

associated with a MediaViewer

whose actions generated the event.

Is also associated with the single

MediaDevice that actually

generated the event.

Media Device

The MediaDevice entity represents a media delivery,

processing, or presentation platform. Examples include

cable set-top boxes, televisions, tablets, PCs, mobile

devices, and any other devices that present media to a

viewer.

The MediaDevice is associated

with one or more MediaEvents. In

practice, this means that each

MediaEvent must be associated

with a device.

剩余136页未读，继续阅读

len_wang

粉丝: 1
资源: 1394

OC-SP-AMD-I01-130502：开放有线电视测量规范

httpd-2.4.46-1.x86_64.tar.bz2

OC.Gen-X.app.zip

芯片研究：2022年春季的张X-M. Yung和M.-H.s的芯片1，2（DOI：10.1016/j.chip.2021.100002）

OC-3与OC-12在SDH传输网络中的作用

OC-SVM较SVM的好处

OC-SVM与SVM区别

OC-softmax

error: src refspec master does not match any error: failed to push some refs to 'ssh://git.sankuai.com/~yangleping/oc-test.git'

oc-sort代码实现

Schol 等人针对这一问题，提出了单类支持向量机（OC-SVM），因此可以将样本分布不均匀的问题转换成一分类问题，但该方法不能充分捕获数据的时间相关性。

deep oc-sort

Last metadata expiration check: 1:50:42 ago on Sun 16 Jul 2023 11:41:22 PM CST. Package python3-pip-9.0.3-22.oc8.noarch is already installed. Dependencies resolved. Nothing to do.

oc pdfview旋转pdf页面

STM32F030C8T6 定时器中断处理函数的详细代码，用于实现正弦波信号的矩形脉冲调制：上述这个代码中，while（1）语句中在主循环中执行其他任务指的是什么任务

最新资源