1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T J.98TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (05/2003) SERIES J: CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA SIGNALS Ancillary digital services for television transmission Metadata requirements for video-on-d
2、emand in cable networks ITU-T Recommendation J.98 ITU-T J-SERIES RECOMMENDATIONS CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA SIGNALS General Recommendations J.1J.9 General specifications for analogue sound-programme transmission J.10J.19 Performance characteri
3、stics of analogue sound-programme circuits J.20J.29 Equipment and lines used for analogue sound-programme circuits J.30J.39 Digital encoders for analogue sound-programme signals J.40J.49 Digital transmission of sound-programme signals J.50J.59 Circuits for analogue television transmission J.60J.69 A
4、nalogue television transmission over metallic lines and interconnection with radio-relay links J.70J.79 Digital transmission of television signals J.80J.89 Ancillary digital services for television transmission J.90J.99 Operational requirements and methods for television transmission J.100J.109 Inte
5、ractive systems for digital television distribution J.110J.129 Transport of MPEG-2 signals on packetized networks J.130J.139 Measurement of the quality of service J.140J.149 Digital television distribution through local subscriber networks J.150J.159 IPCablecom J.160J.179 Miscellaneous J.180J.199 Ap
6、plication for Interactive Digital Television J.200J.209 For further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. J.98 (05/2003) i ITU-T Recommendation J.98 Metadata requirements for video-on-demand in cable networks Summary The purpose of this Recommendation is to describe
7、requirements at the cable operators headend for Video-on-Demand (VoD) metadata. It is envisioned that an industry standard will promote new marketing opportunities, interoperability of assets, and reduce costs to cable operators and their customers. Source ITU-T Recommendation J.98 was prepared by I
8、TU-T Study Group 9 (2001-2004) and approved under the WTSA Resolution 1 procedure on 14 May 2003. ii ITU-T Rec. J.98 (05/2003) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardizati
9、on Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meet
10、s every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts p
11、urview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is v
12、oluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and
13、the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may invol
14、ve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recom
15、mendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. I
16、TU 2003 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. ITU-T Rec. J.98 (05/2003) iii CONTENTS Page 1 Scope 1 2 References. 2 2.1 Normative references 2 2.2 Informative references 2 2.3 Reference acquisition .
17、2 3 Terms and definitions . 2 4 Abbreviations and acronyms 3 5 Metadata requirements for video-on-demand. 3 ITU-T Rec. J.98 (05/2003) 1 ITU-T Recommendation J.98 Metadata requirements for video-on-demand in cable networks 1 Scope This Recommendation describes requirements in a cable operators headen
18、d for Video-on-Demand (VoD) metadata. It enables a consistent level of features and offerings for VoD services that require metadata. As illustrated in Figure 1, this Recommendation, along with other metadata Recommendations to be developed, will facilitate the distribution of content assets from mu
19、ltiple content providers over diverse networks to cable operators to support VoD and other applications at the headend. J.98_ F01Content Provider 1Content Provider 2Content Provider 3Studios/DistributorsSatellite, Fiber, Internet, othersADSAMSAMSAMSCustomersCustomersHeadendsScope of Metadata Effort
20、VOD Serversor ApplicationEqpCustomersCable Operator(Regional Distribution Center/Headends or Headend)Asset DistributionInterfaceNetwork DeliveryFigure 1/J.98 Distribution of content assets and scope of metadata effort The scope of this Recommendation is limited to specific metadata tags and the inte
21、rfaces that facilitate transfer of metadata and its content assets. This transfer occurs on a network from an independent provider to the cable operator via the Asset Distribution System (ADS) to whatever Asset Management System (AMS) there is residing at the cable operators headend. This Recommenda
22、tion provides a common set of metadata used to enable distribution of the content assets to an AMS, as illustrated in Figure 2. At the AMS, application-specific metadata is unwrapped to provide placement and business-rule information of the content assets. Some of the metadata may be reused in custo
23、mer services, but should provide a filtering mechanism that is at the discretion of the cable operator and application server as indicated in ITU-T Rec. J.97. 2 ITU-T Rec. J.98 (05/2003) J.98_F02ADI protocolADI metadataTCP/IPMOD appmetadataOther VOD metadataE-mail appmetadataETV appmetadataApplicati
24、on metadataAsset DistributionInterface Metadatausers of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published
25、. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. 2.1 Normative references 1 Extensible Markup Language (XML) 1.0 (Second Edition), W3C Recommendation, 6 October 2000. http:/www.w3.org/TR/2000/REC-xml-20001006. 2.2 I
26、nformative references 2 CableLabs Video-on-Demand Content Specification, MD-SP-VOD-CONTENT-I01-020327. 3 ITU-T Recommendation J.97 (2002), Metadata on cable networks. 2.3 Reference acquisition Cable Television Laboratories, Inc., 400 Centennial Parkway, Louisville, CO 80027; Phone +1-303-661-9100; F
27、ax +1-303-661-9199; Internet: http:/ ITU Telecommunication Standardization Sector, Geneva, Switzerland; Internet: http:/www.itu.int/ITU-T/. World Wide Web Consortium, Internet: http:/www.w3.org/TR/REC-xml. 3 Terms and definitions This Recommendation defines the following term: 3.1 metadata: Metadata
28、 is descriptive data associated with a content asset package or file. It may vary in depth from merely identifying the content package title or information to populate an EPG to providing a complete index of different scenes in a movie or providing business rules detailing how the content package ma
29、y be displayed, copied, or sold. Separate uses for metadata ITU-T Rec. J.98 (05/2003) 3 have originated from the studios, distribution networks (Cable, Satellite), down to the CPE (STBs, PVRs). 4 Abbreviations and acronyms This Recommendation uses the following abbreviations: ADI Asset Distribution
30、Interface CA Conditional Access CBR Constant Bit Rate CPE Customer Premises Equipment EPG Electronic Programme Guide MPEG Motion Picture Experts Group NTSC National Television Systems Committee SVoD Subscription Video-on-Demand VoD Video-on-Demand 5 Metadata requirements for video-on-demand The meta
31、data requirements for VoD are listed in Table 1. The metadata requirements are divided up into four categories for ease of classification. These categories are: 1) Metadata for filtering/categorizing/display operations (FILT); 2) Metadata for headend operations (OP); 3) Metadata for playback and pre
32、sentation of asset (PRES); 4) Metadata for business-rule support (BUS). The following format is used for capturing the metadata requirements from existing specification and member comments. Requirement One or two-line description of the requirement. Additional description (optional) Additional descr
33、iptive text which may include examples to clarify the requirement in the form of an example implementation. Phasing If the requirement is not necessary in the initial implementation, a later revision or phase of the Recommendation can be targeted to support this requirement. Phase 1 is defined as su
34、pporting existing VoD services in cable networks over MPEG-2 transport. Req/Opt Specifies if it is an optional or mandated requirement to support the phase according to requirements language. This allows for a basic implementation or more advanced features or service offering supported in the same p
35、hase based upon the additional optional metadata. The field is determined to be required if at least one of the metadata tags listed is required. 4 ITU-T Rec. J.98 (05/2003) Table 1/J.98 Metadata matrix of requirements for VoD Req # Requirement Additional description PhaseReq/Opt Current phase Metad
36、ata for filtering/categorizing/ display operations Allows for searches, lists, selective delivery, targeting, guides. FILT-1 Metadata must support filtering by metadata fields. E.g., Title, Director, Actors, Bio, Summary, run Time, box office, rental window, etc. 1 Req FILT-2 Metadata must support P
37、arental Control filters. This may be done by using MPAA/TV ratings and other advisories assigned to the content. 1 Req FILT-3 Metadata must support filtering based on availability of assets. Allows for VoD service to filter VoD content based on time-sensitive factors. Licensing windows are required,
38、 but the rest is optional. 1 Req FILT-4 Metadata should provide necessary information to support display of guides. To support EPG, VoD guides, title pages, and Cable guides 1 Opt FILT-5 Metadata should support filtering by genre or category according to an cable operator specific list. E.g., New re
39、leases, Last Chance, action/adventure, Comedy, Drama, Family, Kids, Horror, Thriller, etc. 1 Opt FILT-6 Metadata may support filtering based on different foreign language-based assets. E.g., support Spanish, French, Indian films 1 Opt FILT-7 Metadata may support filtering based on SVoD services. E.g
40、., search by episodes of TV show 1 Opt FILT-8 Metadata may support information indicating relationship between different related packages. SVoD TV episodes, or assets of other interests/indicates if relationship between packages. 1 Opt FILT-9 Metadata may support listing of material alphabetically,
41、numerically, or chronologically. Sort lists by numerical, alphabetical or time order 1 Opt FILT-10 Metadata may support expanded search capabilities based on fields. Allows for advanced searching based on other fields or combination of categories, e.g., director/actor combos 1 Opt FILT-11 Metadata s
42、hould support extensible list of filterable descriptors. List of example descriptors 1 Opt Headend operations with metadata This is information required to run headend operation, maintenance, and reporting tasks. OP-1 Cable operators must have capability to inspect, remove, change, or add to receive
43、d metadata fields. Allows for verification of metadata at headend, removal of unnecessary or unwanted information at the headend, or addition of cable-specific information 1 Req ITU-T Rec. J.98 (05/2003) 5 Table 1/J.98 Metadata matrix of requirements for VoD Req # Requirement Additional description
44、PhaseReq/Opt OP-2 Information required for ingestion of package/asset or playback of asset in cable system but not included since a metadata field must have a default value or profile that is used. E.g., encoding format might not be mentioned in a metadata field but an mpeg-2 encoding profile is the
45、 default profile used 1 Req OP-3 Metadata must indicate grouping of related assets into an asset or package. This allows for a movie along with its trailer, box cover, & posters to be distributed together as one package from a content provider to headend to VoD server. It also allows for a set of ti
46、tles to be distributed together as one package. 1 Req OP-4 Metadata must provide support for ingestion of package/asset into headend and its subsystems. Indicates where package is to be located and what format it is in 1 Req OP-5 Metadata must support unique package ID/asset ID, content ID and creat
47、ion date for each package/asset and may support unique ID down to each instance. Unique ID to track usage of content and where it is located. This provides interfaces to reporting, billing, and other backend functions. 1 Req OP-6 Each package/asset must have its own metadata associated with it. This
48、 allows for assets to be recombined into different combinations and packages without losing metadata necessary for each asset. This information could contain description of asset, when it was created, where is can be stored, what are its playback specs, and what are its rights for playing. 1 Req OP-
49、7 Metadata must support different types of delivery methods for packages/assets to headend. This supports different types of delivery like tape, satellite, website, IP or automatic/manual input modes. 1 Req OP-8 Metadata must be able to support separate delivery of metadata and content to the headend and its subsystems. This allows for metadata-only types of updates via package, staged delivery, or website lookup. This also allows for retransmission of corrupted metadata without retransmitting the MPEG content. 1 Req OP-9
