GMI 2008 STB-1/Xa Implementation Agreement between IMS Aware ...
Upcoming SlideShare
Loading in...5
×
 

GMI 2008 STB-1/Xa Implementation Agreement between IMS Aware ...

on

  • 581 views

 

Statistics

Views

Total Views
581
Views on SlideShare
581
Embed Views
0

Actions

Likes
0
Downloads
3
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

GMI 2008 STB-1/Xa Implementation Agreement between IMS Aware ... GMI 2008 STB-1/Xa Implementation Agreement between IMS Aware ... Document Transcript

  • GMI 2008 STB-1/Xa Implementation Agreement between IMS Aware IPTV UE and the Service Selection Function – IPTV (SSF-IPTV) MSF-IA-XML.002-FINAL
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface MultiService Forum Implementation Agreement Contribution Number: msf2008.117.04 Document Filename: MSF-IA-XML.002-FINAL Working Group: Protocol and Control Title: GMI 2008 STB-1/Xa Implementation Agreement between IMS Aware IPTV UE and the Service Selection Function – IPTV (SSF-IPTV) Editor: Jim McEachern jmce@nortel.com Kevin Boyle Working Group Chairperson: Chris Gallon Date: 10/7/2008 Abstract: The MultiService Forum (MSF) is responsible for developing Implementation Agreements or Architectural Frameworks which can be used by developers and network operators to ensure interoperability between components from different vendors. MSF Implementation Agreements are formally ratified via a Straw Ballot and then a Principal Member Ballot. Draft MSF Implementation Agreements or Architectural Framework may be published before formal ratification via Straw or Principal Member Ballot. In order for this to take place, the MSF Technical Committee must formally agree that a draft Implementation Agreement or Architectural Framework should be progressed through the balloting process. A Draft MSF Implementation Agreement or Architectural Framework is given a document number in the same manner as an Implementation Agreement. Draft Implementation Agreements may be revised before or during the full balloting process. The revised document is allocated a new major or minor number and is published. The original Draft Implementation Agreement or Architectural Framework remains published until the Technical Committee votes to withdraw it. After being ratified by a Principal Member Ballot, the Draft Implementation Agreement or Architectural Framework becomes final. Earlier Draft Implementation Agreements or Architectural Frameworks remain published until the Technical Committee votes to withdraw them. The use of capitalization of the key words “MUST”, “SHALL”, “REQUIRED”, “MUST NOT”, “SHOULD NOT”, “SHOULD”, “RECOMMENDED”, “NOT RECOMMENDED”, “MAY” or “OPTIONAL” is as described in section V-B of the MSF Technical Committee Operating Procedures. © 2008 MultiService Forum. All rights reserved 2 of 31
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface The goal of the MSF is to promote multi-vendor interoperability as part of a drive to accelerate the deployment of next generation networks. To this end the MSF looks to adopt pragmatic solutions in order to maximize the chances for early deployment in real world networks. To date the MSF has defined a number of detailed Implementation Agreements and detailed Test Plans for the signaling protocols between network components and is developing additional Implementation Agreements and Test Plans addressing some of the other technical issues such as QoS and Security to assist vendors and operators in deploying interoperable solutions. The MSF welcomes feedback and comment and would encourage interested parties to get involved in this work program. Information about the MSF and membership options can be found on the MSF website http://www.msforum.org/ Note: Attention is called to the possibility that use or implementation of this MSF Implementation Agreement may require use of subject matter covered by intellectual property rights owned by parties who have not authorized such use. By publication of this Implementation Agreement, no position is taken by MSF as its Members with respect to the existence or validity of any intellectual property rights in connection therewith, nor does any warranty, express or implied, arise by reason of the publication by MSF of this Implementation Agreement. Moreover, the MSF shall not have any responsibility whatsoever for determining the existence of IPR for which a license may be required for the use or implementation of an MSF Implementation Agreement, or for conducting inquiries into the legal validity or scope of such IPR that is brought to its attention. DISCLAIMER The information in this publication is believed to be accurate as of its publication date. Such information is subject to change without notice and the MultiService Forum is not responsible for any errors or omissions. The MultiService Forum does not assume any responsibility to update or correct any information in this publication. Notwithstanding anything to the contrary, neither the MultiService Forum nor the publisher make any representation or warranty, expressed or implied, concerning the completeness, accuracy, or applicability of any information contained in this publication. No liability of any kind whether based on theories of tort, contract, strict liability or otherwise, shall be assumed or incurred by the MultiService Forum, its member companies, or the publisher as a result of reliance or use by any party upon any information contained in this publication. All liability for any implied or express warranty of merchantability or fitness for a particular purpose is hereby disclaimed. The receipt or any use of this document or its contents does not in any way create by implication or otherwise: Any express or implied license or right to or under any MultiService Forum member company’s patent, copyright, trademark or trade secret rights which are or may be associated with the ideas, techniques, concepts or expressions contained herein; nor © 2008 MultiService Forum. All rights reserved 3 of 31 View slide
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface Any warranty or representation that any MultiService Forum member companies will announce any product(s) and/or service(s) related thereto, or if such announcements are made, that such announced product(s) and/or service(s) embody any or all of the ideas, technologies, or concepts contained herein; nor Any commitment by a MultiService Forum company to purchase or otherwise procure any product(s) and/or service(s) that embody any or all of the ideas, technologies, or concepts contained herein; nor Any form of relationship between any MultiService Forum member companies and the recipient or user of this document. Implementation or use of specific MultiService Forum Implementation Agreements, Architectural Frameworks or recommendations and MultiService Forum specifications will be voluntary, and no company shall agree or be obliged to implement them by virtue of participation in the MultiService Forum. For addition information contact: MultiService Forum 48377 Fremont Blvd., Suite 117 Fremont, CA 94538 USA Phone: +1 510 492-4050 Fax: +1 510 492-4001 info@msforum.org http://www.msforum.org © 2008 MultiService Forum. All rights reserved 4 of 31 View slide
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface I. The MultiService Forum The MultiService Forum (MSF) is a global association of service providers, system suppliers and other organizations committed to developing and promoting open-architecture, multiservice communication systems. Founded in 1998, the MSF is an open-membership organization comprised of the world's leading telecommunications companies. The MSF's activities include developing implementation agreements, promoting worldwide compatibility and interoperability, and encouraging input to appropriate national and international standards bodies. As part of MSF’s effort to drive and promote interoperability, the MSF has created a number of programs geared toward accelerating real world network deployments: 1. Global MSF Interoperability (GMI) events. GMI events provide a real-world setting for vendors to test their solutions and provide evidence that vendor products meet the interoperability standards set forth by MSF Implementation Agreements. Each MSF GMI event is built around a set of capabilities defined for a given release of the MSF Architecture. 2. Next Generation Network (NGN) Test Bed. The NGN test bed provides a facility to enable carriers and vendors to perform in-depth testing of a specific interface as defined in a given release of the MSF architecture. 3. Certification Programs. For more mature technologies the MSF can provide Certification of compliance to a given Implementation Agreement where MSF members believe that it is of value to the industry to do so. II. An introduction to MSF documentation and GMI 2008 This document is part of the MSF Release 4 set of architectural, protocol and test documentation. The MSF Release 4 Architecture is a physical implementation of the functional architectures that have been proposed by the key Standards Development Organizations. As such the MSF Release 4 Architecture represents the current state of the industry and it identifies current open interfaces between physically separate network elements. MSF Implementation Agreements define the protocols to be used over specific open interfaces. Where possible MSF Implementation Agreements are based on industry standard protocols augmented with additional information so as to ensure interoperability between communicating © 2008 MultiService Forum. All rights reserved 5 of 31
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface network elements. This level of interoperability is achieved by closing any gaps and tightening any optional capabilities in those industry standards to remove the danger of mutually incompatible selections by vendors. An MSF Implementation Agreement is targeted at a given release of the MSF architecture but can be used in any circumstance where an operator wishes to deploy the open interface and its functionality within their own network. The MSF Release 4 architecture and its associated implementation agreements are used as the basis for GMI 2008. GMI 2008 is a global test event executed to demonstrate multi-vendor, multi-service interoperability based around IMS and includes IPTV and web based services. As part of GMI 2008 a number of detailed test scenarios have been developed and a number of test plans defined. Test plans contain the set of test cases required to demonstrate a given MSF Release 4 capability and serve to exercise and validate the set of Implementation Agreements required to realize the capability. Following the completion of GMI 2008 the MSF Release 4 architecture and individual implementation agreements will be updated if the testing identifies any deficiencies in the documents. For more information about the scope of GMI2008 please go to http://www.msforum.org III. Impact on previously published MSF documents This is a new specification for MSF release 4 and GMI 2008. © 2008 MultiService Forum. All rights reserved 6 of 31
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface Contents 1.  Scope of this document........................................................................................................... 8  2.  Definitions and abbreviations ................................................................................................. 8  2.1.  Definitions........................................................................................................................ 8  2.2.  Abbreviations ................................................................................................................... 8  3.  Applicability ........................................................................................................................... 8  3.1.  Functionality................................................................................................................... 10  3.1.1.  Retrieving Content Catalog..................................................................................... 10  3.1.2.  Selection of Content................................................................................................ 10  3.1.3.  Selection via a Web Page........................................................................................ 11  4.  STB-1/Xa Interface Functional Overview ............................................................................ 11  4.1.  Browser Client................................................................................................................ 11  4.2.  Non-Browser Client ....................................................................................................... 11  4.3.  Session Establishment .................................................................................................... 12  4.3.1.  Client Behavior ....................................................................................................... 12  5.  STB-1/Xa Interface Protocol Detail...................................................................................... 13  5.1.  SIP Notification Framework .......................................................................................... 13  5.2.  Asset Identification ........................................................................................................ 14  5.2.1.  Content Catalogue................................................................................................... 14  5.2.2.  Video Asset URI Identifier ..................................................................................... 14  5.2.3.  XML File for UE .................................................................................................... 15  6.  References............................................................................................................................. 30  Figures Figure 1 STB-1/Xa Interface in the MSF R4 Architecture..................................................... 9  Figure 2 STB-1/Xa Interface – Simplified Architecture....................................................... 10  © 2008 MultiService Forum. All rights reserved 7 of 31
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface 1. Scope of this document The MSF have adopted the STB-1/Xa interface for the control interface for an IPTV UE to view a content catalogue on a web page, or to download a full content catalogue as an XML document. This Implementation Agreement provides details of STB-1/Xa interface, as used in the MSF R4 architecture. If the content catalogue is viewed as a web page, then it is accessed using standard HTTP, and is displayed using a standard web browser. If the content catalogue is downloaded as an XML document, then the mechanism for displaying the catalogue is an implementation detail for the Set Top Box (STB) and is out of scope for this IA. For the purposes of GMI 2008, some services may not be supported via a simple web interface as defined in this IA. It is also possible that in some cases it may not be possible to download a full content catalogue as specified in this IA. In those cases, it will still be possible to test other aspects of the IPTV architecture by pre-configuring the STB with the contents of the content catalogue already loaded. 2. Definitions and abbreviations 2.1. Definitions Not Applicable 2.2. Abbreviations STB Set Top Box 3. Applicability The scope of the interface described in this IA is shown in the figure below. © 2008 MultiService Forum. All rights reserved 8 of 31
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface Application Presence ISC Applications Server- IPTV Server- IPTV ??/Xa SSF-IPTV IMS aware IPTV UE CP-IPTV ?/DB-4 ??/SS-4 ??/Ut ISC SDF- IPTV Sh Parlay / X Common Resources Gateway Service ISC ??/Xc SS-MCF APP-1/ISC/Ma Broker / SCIM -IPTV ??DB-5 HSS SESS-2/Gm UPSF-IPTV Cx ??/y2 ??/Xp ??/ via SCIM ??/Sh ISC/Ma IMS Core Consumer Access Location Server (CLF) S-CSC IPTV-SCF ??/e2 P-CSC TC-0/Gq’ Access-Resource Transport Control ??/Xd Admission Control Server ??/Rq Session Policy Decision Server ??/Rr TC-1/Ia ??/Xd SS-MDF -IPTV D-SBG-NE C-Border Gw Access Access-Resource Admission Ctrl Srv Node ??/Xc/Xd Multicast Multicast Resource Srv Control Srv Transport Processing Fixed Access Figure 1 STB-1/Xa Interface in the MSF R4 Architecture The scope of this IA can also be illustrated on a simplified architecture diagram that highlights the interfaces that are specific to IPTV. This is shown below in Figure 2. © 2008 MultiService Forum. All rights reserved 9 of 31
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface ACS MI-2* IPTV Apps Server *based on DSLF TR-069 and 135 (data I Ut AS-IPTV UPS CP M S STB-1/Xa SSF SDF PS-IPTV Sr A DB-2/ Sh APP- 1/ ISC Other IMS w CR Domain UPSF HSS a r DB-0/ SS-MCF e SESS-2/ SESS-4/ Mw Gm Core IMS Xp P-CSC S-CSC I-CSC I SESS-8/ Y2 SS-MDF P LOC-1/e2 TC-0/ Gq’ T Video Media Server V NACF RACF (SPDF) - TC-11/e4 Xc Xd SESS-7/ U Xc (and Dj) TC-1/ Ia Xc E Transport Processing Video Functions Headend TR-5/Xd Xd Transport & Access Networks Figure 2 STB-1/Xa Interface – Simplified Architecture Note: Yellow interfaces are not opened for testing at GMI 2008. 3.1. Functionality 3.1.1. Retrieving Content Catalog This IA defines a mechanism for an IMS aware IPTV UE to view a content catalogue on a web page, or to download a content catalogue in the form of an XML document. The information in the content catalogue is then used to display available content to the user in a format chosen by the STB. The details of the presentation format are out of scope for GMI 2008 and will not be specified in this IA nor tested in GMI 2008. 3.1.2. Selection of Content © 2008 MultiService Forum. All rights reserved 10 of 31
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface The content catalogue provides a URI which is used to initiate a session to access specific content. The details of the mechanism for transferring the URI from the content catalogue to the SIP UA (IPTV UE) are out of scope for GMI 2008. GMI 2008 will merely verify that the URI in the content catalogue can be used by the IPTV UE to access content. 3.1.3. Selection via a Web Page This IA also includes an option for a simplified user interface consisting of a standard web browser viewing a web page via HTTP, and selecting the content through the web interface. For broadcast service, this could require a two-page interface, where the initial page provides the address for the SIP session to the AS, and the subsequent page provides the multicast addresses for the individual channels. In order to implement certain functions of a broadcast service (like channel up/down, for instance) the UE may require preconfiguration with the channel map correlating the multicast addresses with their respective channels. 4. STB-1/Xa Interface Functional Overview 4.1. Browser Client In some cases, the UE may contain a web browser, such that the consumer can point the interface to a URI given by the service provider. At that address, the service provider may place the content catalog, such that the catalog does not need to be retrieved by, or sent to, the UE. For broadcast service, the UE would need the multicast addresses for the channels in order to connect to the content streams. Supplying the address at content selection time could be done through a web interface where the initial selection provides the address to establish the SIP session, and then a subsequent page would provide channel links to enable selection of the proper multicast. This arrangement would preclude a “channel up/channel down” function that is solely in the STB, however. This content catalog webpage would utilize standard HTML, and is accessed using HTTP. Selection of a particular asset is achieved through clicking its link, which returns a URI for the asset. For subsequent client behavior, see clause 4.3. 4.2. Non-Browser Client Prior to usage of the STB-1/Xa interface to retrieve the content catalogue, the UE utilizes the SIP notification framework to request its service data. Along with the service data, the URI for the content catalogue is obtained. More detailed information on the usage of the SIP Notification framework to retrieve the catalogue URI is provided in section 5.1. © 2008 MultiService Forum. All rights reserved 11 of 31
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface The format of the content catalogue may vary from client to client. For the MSFR4 IPTV UE client the catalogue will be an XML document and will be identified by a URI delivered within the body of the SIP Notify. The format of the document is defined in section 5.2.3 It should be observed that the HSS filter criteria must be sufficiently defined such that the Subscribe messages are routed to the correct app servers based upon the event package name. 4.3. Session Establishment At this point, the subscriber has received a content catalogue either through a browser interface or by retrieving it as XML data. Either way, the user may now select a video asset. The content catalogue will return (in the case of a web catalogue) or embed (for non-browser catalogues) for each asset a URI which the client will utilize to initiate the viewing session. If the URI is a SIP URI, it shall correspond to the video asset being selected. If the URI is an HTTP URI, it shall reference a web page, potentially with embedded web services calls that could be utilized to solicit or confirm payment information or the like. This web services dialogue would then yield the SIP URI which is used to invoke the session establishment. 4.3.1. Client Behavior Once the user selects a video asset item from the catalogue, the client obtains the corresponding URI from the content catalogue. This is done using HTTP GET in the case of a browser-based web catalogue, or by looking up the embedded URI in the XML data in the case of a non- browser catalogue. If the URI is an HTTP URI, the client shall execute an HTTP GET and fetch the webpage. The page may utilize web services to perform functions prior to the user accessing the video asset. Once these functions are successfully completed, the SIP URI shall be provided so that the session establishment can commence. Specification of these services is out of scope and is left to the vendors, though care should be taken to avoid using protocols and methods that are uncommon or unlikely to appear in an embedded client. An example of an HTTP URI is: http://server.provider.com/epg.htm If the URI is a multicast address, the UE shall utilize IGMP to join the multicast over the Xc/Dj interface. For details of the protocol usage for these interfaces, see the corresponding Implementation Agreement. An example of a multicast URI is: multicast://239.3.7.0:37000. If the URI is a SIP URI, it shall construct a SIP INVITE message to be sent using the SESS- 2/Gm interface. Once the session is established, video control (trick play, etc.) is handled using RTSP over the Xc interface. For details of the protocol usage for these interfaces, see the corresponding Implementation Agreement. An example of a SIP URI is sip:+1-212-555- 1212:1234@gateway.com;user=phone. © 2008 MultiService Forum. All rights reserved 12 of 31
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface 5. STB-1/Xa Interface Protocol Detail The STB-1/Xa interface utilizes HTTP per RFC 2616. XML, per the XML 1.0 specification, may also be used for transmittal of content catalogue data through the HTTP session. Other protocols that may be used over the STB-1/Xa interface, such as those for web services, are not specified here. 5.1. SIP Notification Framework Note: This section describes requirements for the SESS-2/Gm interface that are needed in order to make the STB-1/Xa interface work if the service data is not pre-provisioned. Because these requirements are not generally applicable to the SESS-2/Gm interface, they are located here. In the event that the Content Catalogue URI is not pre-provisioned, the client will need a method of retrieving it. While there are many methods for providing service data to clients, there are several key benefits in using a SIP Notification framework over IMS: • Leverages the Authenticated and Secured SIP Interface through which the IMS client registers the subscriber with the network • IMS enables the Client to utilize the notification framework to obtain service data without requiring any service data provisioning or special configuration on the client • Standards Based SIP Notification framework • RFC 3265 • Precedent for Use in Initialization Model • A Framework for Session Initiation Protocol User Agent Profile Delivery draft-ietf-sipping-config-framework-15.txt • Define ITF-Profiles For key UE sub-classes • Flexible Request & Notification framework • Enables transport of service data via wide range of mechanisms: • IP Multicast (data carousel), HTTP GET, Web Services, etc. • Pull Model for Initial Data; Supports Push for Notification of changes • Once Subscribed to Event Notification, Notify can be dispatched by App server anytime there is a change in data. The model for service data configuration via the SIP notification framework is modeled after the IETF draft, “A Framework for Session Initiation Protocol User Agent Profile Delivery” (draft- ietf-sipping-config-framework-15.txt). An event package, UE-Service-Data, is defined which enables the UE to inform the IP Video AS of certain capabilities and to request certain types of service data. Event Package Name: UE-Service-Data • Event header field present in SUBSCRIBE and NOTIFY requests for this package Event Package Parameters: © 2008 MultiService Forum. All rights reserved 13 of 31
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface • For use in Subscribe: • Data-Type: Indicates the token name of the service data type the UE wishes to obtain. • For GMI2008, a single Data-Type will be supported: Content-Catalogue; however Data-Types can be added to reflect additional service config data as the need arises in GMI2008. A separate Subscribe is required for each Data-Type. • ITF_Sub-type: Describes the general type of UE. Exact values are tbd and will likely leverage work in SDOs such as DVB. Candidates include: STB, PC, SmartPhone. • ITF Vendor: The vendor of the UE. In keeping with the SIP config framework document, the implementer SHOULD use their DNS domain name (e.g. example.com) as the value of the "vendor" parameter so that it is known to be unique. • ITF Version: String text describing the version of the UE. • Other Device Characteristics: other characteristics such as screen size, aspect ratio, RTSP support, IGMP support, OMA Bcast support, etc. need to be known in order for the IP Video AS to provide the best service offer possible; however, they will not be defined in this specification at this time. 5.2. Asset Identification The content catalogue is retrieved using an HTTP GET. The catalog data is then displayed to the user in a way that allows for easy selection of a video asset. How the UE chooses to provide this data to the user is at the discretion of the UE vendor. 5.2.1. Content Catalogue A URI identifying the content catalogue shall be returned to the UE in the NOTIFY message resulting from the SUBSCRIBE request (refer to section 5.1) if the subscriber is known by the IMS to subscribe to the IPTV services. The content catalogue includes a list of video assets which the subscriber is authorized to view and which are able to be played on the subscriber’s currently active device. This catalog may be an XML data set, as described in section 5.2.3, or may be a web page with a list of the video assets. An identifier for each video asset is included in the catalogue. As described in 4.2, this identifier is either the SIP URI which is used for the address of the SIP Invite message, or is an HTTP URI used to access web services that will subsequently provide the SIP URI. 5.2.2. Video Asset URI Identifier The SIP URI identifying the commercial asset is provided either through the content catalogue or after successful web services processing. This URI is used by the client for the “TO” header of the INVITE message signaled to the IPTV AS over the SESS-2/Gm and APP-1/ISC interfaces. The format is as follows: <Cvod-asset-id>@<video-service-subdomain>.<operator-domain> © 2008 MultiService Forum. All rights reserved 14 of 31
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface The Cvod-asset-id is a unique identifier which identifies a video asset and video-service- subdomain maps to the IPTV AS. As an example: sip:batman@iptvAS.somewhere.com where: <Cvod-asset-id> = batman <video-service-subdomain> = iptvAS <operator-domain> = somewhere.com 5.2.3. XML File for UE For GMI2008, the content catalogue will be defined as an XML file modeled after the ATIS IIF metadata definitions, which are in turn a modification of the TVAnytime metadata. The XML Schema definition (xsd) is available in ATIS-0800020 and is duplicated here for reference. In case of differences between this version and that in ATIS-0800020, the published version in the ATIS specification shall take precedence. XSD Definition: <?xml version="1.0" encoding="UTF-8"?> <schema targetNamespace="http://www.atis.org/schemas/0800020/epg/1" xmlns:epg="http://www.atis.org/schemas/0800020/epg/1" version="0" xmlns:tva="urn:tva:metadata:2007" xmlns:mpeg7="urn:tva:mpeg7:2005" xmlns:mps="http://www.atis.org/schemas/0800013/mps/1" xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> <import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="xml.xsd"/> <import namespace="urn:tva:mpeg7:2005" schemaLocation="tva_mpeg7.xsd"/> <import namespace="urn:tva:metadata:2007" schemaLocation="tva_metadata_3-1_v141.xsd"/> <import namespace="http://www.atis.org/schemas/0800013/mps/1" schemaLocation="ATIS-0800013.xsd"/> <annotation> <documentation xml:lang="en"> This schema is copyrighted by the Alliance for Telecommunications Industry Solutions ("ATIS") and distributed in conjunction with ATIS-0800020. Disclaimer and Limitation of Liability The information provided in ATIS-0800020, is directed solely to professionals who have the appropriate degree of experience to understand and interpret its contents in accordance with generally accepted engineering or other professional standards and applicable regulations. No recommendation as to products or vendors is made or should be implied. NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURTHER NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTIBILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. ATIS SHALL NOT BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY ATIS FOR THIS STANDARD, WITH RESPECT TO ANY CLAIM, AND IN NO EVENT SHALL ATIS BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. ATIS EXPRESSLY ADVISES THAT ANY AND ALL USE OF OR RELIANCE UPON THE INFORMATION PROVIDED IN THIS STANDARD AND IS AT THE RISK OF THE USER. </documentation> © 2008 MultiService Forum. All rights reserved 15 of 31
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface </annotation> <annotation> <documentation xml:lang="en"> This XML document contains the normative definition of the XML Schema defined in ATIS-0800020. In the event the informative part of the corresponding standard contradicts this XML schema, the XML schema in this file should be used as the definitive specification. </documentation> </annotation> <element name="EPGMain" type="epg:EPGMainType"/> <annotation> <documentation xml:lang="en">IIFMainType</documentation> </annotation> <complexType name="EPGMainType"> <sequence> <element name="MetadataOriginationInformationTable" type="tva:MetadataOriginationInformationTableType" minOccurs="0"/> <element name="ClassificationSchemeTable" type="tva:ClassificationSchemeTableType" minOccurs="0"/> <element name="RatingRegionTables" type="epg:RatingRegionTablesType" minOccurs="0"/> <element name="ProgramDescription" type="epg:ProgramDescriptionType" minOccurs="0"/> <element name="Publisher" type="mpeg7:TextualType" minOccurs="0" maxOccurs="unbounded"/> <element name="RightsOwner" type="mpeg7:TextualType" minOccurs="0" maxOccurs="unbounded"/> <element name="CopyrightNotice" type="mpeg7:TextualType" minOccurs="0" maxOccurs="unbounded"/> </sequence> <attribute ref="xml:lang" use="required"/> </complexType> <annotation> <documentation xml:lang="en" > ProgramDescriptionType </documentation> </annotation> <complexType name="ProgramDescriptionType"> <sequence> <element name="ProgramInformationTable" type="epg:ProgramInformationTableType" minOccurs="0"/> <element name="GroupInformationTable" type="epg:GroupInformationTableType" minOccurs="0"/> <element name="SuperGroupInformationTable" type="epg:SuperGroupInformationTableType" minOccurs="0"/> <element name="ProgramLocationTable" type="epg:ProgramLocationTableType" minOccurs="0"/> <element name="ServiceInformationTable" type="epg:ServiceInformationTableType" minOccurs="0"/> <element name="CreditsInformationTable" type="epg:CreditsInformationTableType" minOccurs="0"/> <element name="ProgramReviewTable" type="epg:ProgramReviewTableType" minOccurs="0"/> <element name="PurchaseInformationTable" type="epg:PurchaseInformationTableType" minOccurs="0"/> </sequence> </complexType> <annotation> <documentation xml:lang="en" > ProgramInformationTableType </documentation> </annotation> <complexType name="ProgramInformationTableType"> <sequence> <element name="ProgramInformation" © 2008 MultiService Forum. All rights reserved 16 of 31
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface type="epg:ProgramInformationType" minOccurs="0" maxOccurs="unbounded"/> </sequence> <attribute name="metadataOriginIDRef" type="tva:TVAIDRefType" use="optional"/> <attribute ref="xml:lang" use="optional"/> </complexType> <annotation> <documentation xml:lang="en" > GroupInformationTableType </documentation> </annotation> <complexType name="GroupInformationTableType"> <sequence> <element name="GroupInformation" type="tva:GroupInformationType" minOccurs="0" maxOccurs="unbounded"/> </sequence> <attribute name="metadataOriginIDRef" type="tva:TVAIDRefType" use="optional"/> <attribute ref="xml:lang" use="optional"/> </complexType> <annotation> <documentation xml:lang="en" > SuperGroupInformationTableType </documentation> </annotation> <complexType name="SuperGroupInformationTableType"> <sequence> <element name="SuperGroupInformation" type="epg:SuperGroupInformationType" minOccurs="0" maxOccurs="unbounded"/> </sequence> <attribute name="metadataOriginIDRef" type="tva:TVAIDRefType" use="optional"/> <attribute ref="xml:lang" use="optional"/> </complexType> <annotation> <documentation xml:lang="en" > ProgramLocationTableType </documentation> </annotation> <complexType name="ProgramLocationTableType"> <sequence> <element name="Schedule" type="epg:ScheduleType" minOccurs="0" maxOccurs="unbounded"/> <element name="BroadcastEvent" type="epg:BroadcastEventType" minOccurs="0" maxOccurs="unbounded"/> <element name="OnDemandProgram" type="epg:OnDemandProgramType" minOccurs="0" maxOccurs="unbounded"/> <element name="OnDemandService" type="epg:OnDemandServiceType" minOccurs="0" maxOccurs="unbounded"/> </sequence> <attribute name="metadataOriginIDRef" type="tva:TVAIDRefType" use="optional"/> <attribute ref="xml:lang" use="optional"/> </complexType> <annotation> <documentation xml:lang="en" > ServiceInformationTableType </documentation> </annotation> <complexType name="ServiceInformationTableType"> <sequence> <element name="ServiceInformation" type="epg:ServiceInformationType" minOccurs="0" maxOccurs="unbounded"/> © 2008 MultiService Forum. All rights reserved 17 of 31
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface </sequence> <attribute name="metadataOriginIDRef" type="tva:TVAIDRefType" use="optional"/> <attribute ref="xml:lang" use="optional"/> </complexType> <annotation> <documentation xml:lang="en" > CreditsInformationTableType </documentation> </annotation> <complexType name="CreditsInformationTableType"> <sequence> <choice minOccurs="0" maxOccurs="unbounded"> <element name="PersonName" type="epg:PersonCreditType"/> <element name="OrganizationName" type="epg:OrganizationCreditType"/> </choice> </sequence> <attribute name="metadataOriginIDRef" type="tva:TVAIDRefType" use="optional"/> <attribute ref="xml:lang" use="optional"/> </complexType> <annotation> <documentation xml:lang="en" > ProgramReviewTableType </documentation> </annotation> <complexType name="ProgramReviewTableType"> <sequence> <element name="Review" type="epg:ReviewType" minOccurs="0" maxOccurs="unbounded"/> </sequence> <attribute name="metadataOriginIDRef" type="tva:TVAIDRefType" use="optional"/> <attribute ref="xml:lang" use="optional"/> </complexType> <annotation> <documentation xml:lang="en" > PurchaseInformationTableType </documentation> </annotation> <complexType name="PurchaseInformationTableType"> <sequence> <element name="PurchaseInformation" type="epg:PurchaseInformationType" minOccurs="0" maxOccurs="unbounded"/> </sequence> <attribute name="metadataOriginIDRef" type="tva:TVAIDRefType" use="optional"/> <attribute ref="xml:lang" use="optional"/> </complexType> <annotation> <documentation xml:lang="en" > PersonInformationType </documentation> </annotation> <complexType name="PersonInformationType"> <complexContent> <extension base="mpeg7:PersonNameType"> <sequence> <element name="PersonURL" type="anyURI" minOccurs="0" maxOccurs="unbounded"/> </sequence> </extension> </complexContent> </complexType> <annotation> <documentation xml:lang="en" > OrganizationInformationType </documentation> </annotation> © 2008 MultiService Forum. All rights reserved 18 of 31
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface <complexType name="OrganizationInformationType"> <complexContent> <extension base="mpeg7:OrganizationType"> <sequence> <element name="OrganizationURL" type="anyURI" minOccurs="0" maxOccurs="unbounded"/> </sequence> </extension> </complexContent> </complexType> <annotation> <documentation xml:lang="en" > PersonCreditType </documentation> </annotation> <complexType name="PersonCreditType"> <complexContent> <extension base="epg:PersonInformationType"> <attribute name="personNameId" type="tva:TVAIDType" use="required"/> </extension> </complexContent> </complexType> <annotation> <documentation xml:lang="en" > OrganizationCreditType </documentation> </annotation> <complexType name="OrganizationCreditType"> <complexContent> <extension base="epg:OrganizationInformationType"> <attribute name="organizationNameId" type="tva:TVAIDType" use="required"/> </extension> </complexContent> </complexType> <annotation> <documentation xml:lang="en">IIFAgentType</documentation> </annotation> <complexType name="IIFAgentType"> <sequence> <choice minOccurs="0" maxOccurs="unbounded"> <element name="PersonName" type="epg:PersonInformationType"/> <element name="PersonNameIDRef" type="tva:TVAIDRefElementType"/> <element name="OrganizationName" type="epg:OrganizationInformationType"/> <element name="OrganizationNameIDRef" type="tva:TVAIDRefElementType"/> </choice> </sequence> </complexType> <annotation> <documentation xml:lang="en">ReviewerType</documentation> </annotation> <complexType name="ReviewerType"> <complexContent> <extension base="epg:IIFAgentType"> <sequence> <element name="Publication" type="mpeg7:TextualType" minOccurs="0"/> </sequence> </extension> </complexContent> </complexType> <annotation> <documentation xml:lang="en">RatingType</documentation> © 2008 MultiService Forum. All rights reserved 19 of 31
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface </annotation> <complexType name="RatingType"> <complexContent> <extension base="mpeg7:RatingType"> <attribute name="iconRef" type="anyURI" use="optional"/> </extension> </complexContent> </complexType> <annotation> <documentation xml:lang="en" > MediaReviewType </documentation> </annotation> <complexType name="MediaReviewType"> <sequence> <element name="Rating" type="epg:RatingType" minOccurs="0" maxOccurs="unbounded"/> <element name="FreeTextReview" type="mpeg7:TextualType" minOccurs="0" maxOccurs="unbounded"/> <element name="Reviewer" type="epg:ReviewerType" minOccurs="0" maxOccurs="unbounded"/> <element name="ReviewReference" type="anyURI" minOccurs="0" /> </sequence> </complexType> <annotation> <documentation xml:lang="en">ReviewType</documentation> </annotation> <complexType name="ReviewType"> <complexContent> <extension base="epg:MediaReviewType"> <attribute name="programId" type="tva:CRIDType" use="required"/> <attributeGroup ref="tva:fragmentIdentification"/> <attribute name="metadataOriginIDRef" type="tva:TVAIDRefType" use="optional"/> <attribute ref="xml:lang" use="optional"/> </extension> </complexContent> </complexType> <annotation> <documentation xml:lang="en" > CopyControlInformationType </documentation> </annotation> <simpleType name="CopyControlInformationType"> <restriction base="string"> <enumeration value="CopyNever"/> <enumeration value="CopyOnce"/> <enumeration value="CopyFreely"/> </restriction> </simpleType> <annotation> <documentation xml:lang="en" > CopyPrivilegesType </documentation> </annotation> <complexType name="CopyPrivilegesType"> <sequence> <element name="CopyPrivilege" type="epg:CopyControlInformationType" minOccurs="1"/> <element name="CopyOnceSurcharge" type="tva:PriceType" minOccurs="0"/> <element name="CopyFreelySurcharge" type="tva:PriceType" minOccurs="0"/> </sequence> </complexType> <annotation> <documentation xml:lang="en">PurchaseType</documentation> © 2008 MultiService Forum. All rights reserved 20 of 31
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface </annotation> <complexType name="PurchaseType"> <complexContent> <extension base="tva:PurchaseType"> <sequence> <element name="CopyPrivileges" type="epg:CopyPrivilegesType" minOccurs="0"/> </sequence> <attribute name="previewPeriod" type="duration" use="optional"/> <attribute name="resumeViewAllowed" type="boolean" use="optional"/> </extension> </complexContent> </complexType> <annotation> <documentation xml:lang="en" > PurchaseItemType </documentation> </annotation> <complexType name="PurchaseItemType"> <sequence> <element name="Price" type="tva:PriceType" maxOccurs="unbounded"/> <element name="Purchase" type="epg:PurchaseType" minOccurs="0" maxOccurs="unbounded"/> <element name="Description" type="mpeg7:TextualType" minOccurs="0" maxOccurs="unbounded"/> <element name="PricingServerURL" type="anyURI" minOccurs="0" maxOccurs="unbounded"/> </sequence> <attribute name="start" type="dateTime" use="optional"/> <attribute name="end" type="dateTime" use="optional"/> </complexType> <annotation> <documentation xml:lang="en" > PurchaseInformationType </documentation> </annotation> <complexType name="PurchaseInformationType"> <complexContent> <extension base="tva:PurchaseItemType"> <attribute name="purchaseId" type="tva:TVAIDType" use="required"/> <attributeGroup ref="tva:fragmentIdentification"/> <attribute name="metadataOriginIDRef" type="tva:TVAIDRefType" use="optional"/> </extension> </complexContent> </complexType> <annotation> <documentation xml:lang="en" > ProgramInformationType </documentation> </annotation> <complexType name="ProgramInformationType"> <sequence> <element name="BasicDescription" type="epg:BasicContentDescriptionType"/> <element name="OtherIdentifier" type="mpeg7:UniqueIDType" minOccurs="0" maxOccurs="unbounded"/> <element name="AVAttributes" type="epg:AVAttributesType" minOccurs="0"/> <element name="MemberOf" type="tva:BaseMemberOfType" minOccurs="0" maxOccurs="unbounded"/> <element name="DerivedFrom" type="tva:DerivedFromType" minOccurs="0"/> <element name="EpisodeOf" type="tva:EpisodeOfType" minOccurs="0"/> © 2008 MultiService Forum. All rights reserved 21 of 31
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface <element name="PartOfAggregatedProgram" type="tva:CRIDType" minOccurs="0"/> <element name="AggregationOf" type="tva:AggregationOfType" minOccurs="0"/> </sequence> <attribute name="programId" type="tva:CRIDType" use="required"/> <attribute name="metadataOriginIDRef" type="tva:TVAIDRefType" use="optional"/> <attribute ref="xml:lang" use="optional"/> </complexType> <annotation> <documentation xml:lang="en" > BasicContentDescriptionType </documentation> </annotation> <complexType name="BasicContentDescriptionType"> <sequence> <element name="Title" type="mpeg7:TitleType" minOccurs="0" maxOccurs="unbounded"/> <element name="MediaTitle" type="mpeg7:TitleMediaType" minOccurs="0" maxOccurs="unbounded"/> <element name="ShortTitle" type="tva:ShortTitleType" minOccurs="0" maxOccurs="unbounded"/> <element name="Synopsis" type="tva:SynopsisType" minOccurs="0" maxOccurs="unbounded"/> <element name="PromotionalInformation" type="mpeg7:TextualType" minOccurs="0" maxOccurs="unbounded"/> <element name="ProgramURL" type="anyURI" minOccurs="0" maxOccurs="unbounded"/> <element name="ProgramInfoURL" type="anyURI" minOccurs="0" maxOccurs="unbounded"/> <element name="Keyword" type="tva:KeywordType" minOccurs="0" maxOccurs="unbounded"/> <element name="Genre" type="tva:GenreType" minOccurs="0" maxOccurs="unbounded"/> <element name="RRTParentalGuidance" type="epg:RRTParentalGuidanceType" minOccurs="0" maxOccurs="unbounded"/> <element name="ParentalGuidance" type="mpeg7:ParentalGuidanceType" minOccurs="0" maxOccurs="unbounded"/> <element name="Language" type="mpeg7:ExtendedLanguageType" minOccurs="0" maxOccurs="unbounded"/> <element name="CaptionLanguage" type="tva:CaptionLanguageType" minOccurs="0" maxOccurs="unbounded"/> <element name="SignLanguage" type="tva:SignLanguageType" minOccurs="0" maxOccurs="unbounded"/> <element name="CreditsList" type="epg:CreditsListType" minOccurs="0"/> <element name="AwardsList" type="epg:AwardsListType" minOccurs="0"/> <element name="BoxOffice" type="tva:PriceType" minOccurs="0" maxOccurs="unbounded"/> <element name="RelatedMaterial" type="tva:RelatedMaterialType" minOccurs="0" maxOccurs="unbounded"/> <element name="ProductionDate" type="tva:TVATimeType" minOccurs="0"/> <element name="ProductionLocation" type="mpeg7:regionCode" minOccurs="0" maxOccurs="unbounded"/> <element name="CreationCoordinates" type="tva:CreationCoordinatesType" minOccurs="0" maxOccurs="unbounded"/> <element name="DepictedCoordinates" © 2008 MultiService Forum. All rights reserved 22 of 31
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface type="tva:DepictedCoordinatesType" minOccurs="0" maxOccurs="unbounded"/> <element name="ReleaseInformation" type="tva:ReleaseInformationType" minOccurs="0" maxOccurs="unbounded"/> <element name="Duration" type="duration" minOccurs="0"/> <element name="PurchaseList" type="epg:PurchaseListType" minOccurs="0"/> </sequence> <attribute name="programFormat" use="optional"> <simpleType> <restriction base="string"> <enumeration value="Series"/> <enumeration value="Movie"/> <enumeration value="Paid program"/> <enumeration value="Special"/> </restriction> </simpleType> </attribute> <attribute name="copyRestrictions" type="epg:CopyControlInformationType" use="optional"/> </complexType> <annotation> <documentation xml:lang="en" > VideoAttributesType </documentation> </annotation> <complexType name="VideoAttributesType"> <complexContent> <extension base="tva:VideoAttributesType"> <sequence> <element name="ActiveFormatDescription" minOccurs="0"> <simpleType> <restriction base="unsignedInt"> <maxInclusive value="15"/> </restriction> </simpleType> </element> </sequence> </extension> </complexContent> </complexType> <annotation> <documentation xml:lang="en" > ImageAttributesType </documentation> </annotation> <complexType name="ImageAttributesType"> <sequence> <element name="FileFormat" type="tva:ControlledTermType"/> <element name="FileSize" type="unsignedLong" minOccurs="0"/> <element name="HorizontalSize" type="unsignedShort" minOccurs="0"/> <element name="VerticalSize" type="unsignedShort" minOccurs="0"/> <element name="Color" type="tva:ColorType" minOccurs="0"/> </sequence> </complexType> <annotation> <documentation xml:lang="en" > AVAttributesType </documentation> </annotation> <complexType name="AVAttributesType"> <sequence> <element name="FileFormat" type="tva:ControlledTermType" minOccurs="0"/> <element name="FileSize" type="unsignedLong" minOccurs="0"/> <element name="System" type="tva:ControlledTermType" © 2008 MultiService Forum. All rights reserved 23 of 31
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface minOccurs="0"/> <element name="BitRate" type="tva:BitRateType" minOccurs="0"/> <element name="AudioAttributes" type="tva:AudioAttributesType" minOccurs="0" maxOccurs="unbounded"/> <element name="VideoAttributes" type="epg:VideoAttributesType" minOccurs="0"/> </sequence> </complexType> <annotation> <documentation xml:lang="en" > RelatedMaterialType </documentation> </annotation> <complexType name="RelatedMaterialType"> <sequence> <element name="HowRelated" type="tva:ControlledTermType" minOccurs="0"/> <element name="Format" type="tva:ControlledTermType" minOccurs="0"/> <element name="RRTParentalGuidance" type="epg:RRTParentalGuidanceType" minOccurs="0" maxOccurs="unbounded"/> <element name="ParentalGuidance" type="mpeg7:ParentalGuidanceType" minOccurs="0" maxOccurs="unbounded"/> <element name="CaptionText" type="mpeg7:TextualType " minOccurs="0" maxOccurs="unbounded"/> <choice minOccurs="0"> <element name="AVAttributes" type="epg:AVAttributesType"/> <element name="ImageAttributes" type="epg:ImageAttributesType"/> </choice> <element name="AvailableTime" type="tva:TVATimeType" minOccurs="0" maxOccurs="unbounded"/> <choice> <element name="MediaLocator" type="mps:ResourceLocatorType"/> <element name="SegmentReference" type="tva:SegmentReferenceType"/> </choice> <element name="PromotionalText" type="mpeg7:TextualType" minOccurs="0" maxOccurs="unbounded"/> <element name="PromotionalMedia" type="mpeg7:TitleMediaType" minOccurs="0" maxOccurs="unbounded"/> <element name="SourceMediaLocator" type="mpeg7:MediaLocatorType" minOccurs="0"/> </sequence> </complexType> <annotation> <documentation xml:lang="en" > RRTParentalGuidanceType </documentation> </annotation> <complexType name="RRTParentalGuidanceType"> <sequence> <element name="Dimension" maxOccurs="unbounded"> <complexType> <sequence> <element name="RatingDimension" type="unsignedByte"/> <element name="RatingValue"> <simpleType> <restriction base="unsignedByte"> © 2008 MultiService Forum. All rights reserved 24 of 31
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface <maxInclusive value="15"/> </restriction> </simpleType> </element> </sequence> </complexType> </element> <element name="RatingDescriptionText"> <simpleType> <restriction base="string"> <length value="16"/> </restriction> </simpleType> </element> </sequence> <attribute name="ratingRegion" type="unsignedByte"/> </complexType> <annotation> <documentation xml:lang="en" > CreditsItemType </documentation> </annotation> <complexType name="CreditsItemType"> <complexContent> <extension base="epg:IIFAgentType"> <sequence> <element name="Character" type="mpeg7:PersonNameType" minOccurs="0" maxOccurs="unbounded"/> </sequence> <attribute name="role" type="mpeg7:termReferenceType" use="required"/> </extension> </complexContent> </complexType> <annotation> <documentation xml:lang="en" > CreditsListType </documentation> </annotation> <complexType name="CreditsListType"> <sequence> <element name="CreditsItem" type="epg:CreditsItemType" minOccurs="0" maxOccurs="unbounded"/> </sequence> </complexType> <annotation> <documentation xml:lang="en" > PurchaseListType </documentation> </annotation> <complexType name="PurchaseListType"> <sequence> <choice minOccurs="0" maxOccurs="unbounded"> <element name="PurchaseItem" type="epg:PurchaseItemType"/> <element name="PurchaseIdRef" type="tva:TVAIDRefType"/> </choice> <element name="HowToPurchase" type="mpeg7:TextualType" minOccurs="0" maxOccurs="unbounded"/> </sequence> </complexType> <annotation> <documentation xml:lang="en" > SuperGroupInformationTypeType </documentation> </annotation> <complexType name="SuperGroupTypeType"> <complexContent> <extension base="tva:BaseProgramGroupTypeType"> © 2008 MultiService Forum. All rights reserved 25 of 31
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface <attribute name="value" use="required"> <simpleType> <restriction base="string"> <enumeration value="seriesFamily"/> <enumeration value="otherChoice"/> </restriction> </simpleType> </attribute> </extension> </complexContent> </complexType> <annotation> <documentation xml:lang="en" > SuperGroupInformationType </documentation> </annotation> <complexType name="SuperGroupInformationType"> <sequence> <element name="GroupType" type="epg:SuperGroupTypeType"/> <element name="BasicDescription" type="epg:BasicContentDescriptionType"/> </sequence> <attribute name="groupId" type="tva:CRIDType" use="required"/> <attribute name="ordered" type="boolean" use="optional" default="false"/> <attribute name="numOfItems" type="unsignedInt" use="optional"/> <attributeGroup ref="tva:fragmentIdentification"/> <attribute name="metadataOriginIDRef" type="tva:TVAIDRefType" use="optional"/> <attribute ref="xml:lang" use="optional"/> </complexType> <annotation> <documentation xml:lang="en"/> </annotation> <complexType name="ChannelNumberType"> <attribute name="major" type="unsignedInt"/> <attribute name="minor" type="unsignedInt" use="optional"/> </complexType> <annotation> <documentation xml:lang="en" > ServiceInformationType </documentation> </annotation> <complexType name="ServiceInformationType"> <complexContent> <extension base="tva:ServiceInformationType"> <sequence> <element name="OriginalChannelNumber" type="epg:ChannelNumberType" minOccurs="0"/> <element name="RRTParentalGuidance" type="epg:RRTParentalGuidanceType" minOccurs="0" maxOccurs="unbounded"/> <element name="ParentalGuidance" type="mpeg7:ParentalGuidanceType" minOccurs="0" maxOccurs="unbounded"/> <element name="PurchaseList" type="epg:PurchaseListType" minOccurs="0"/> </sequence> <attribute name="originalServiceProvider" type="string" use="optional"/> <attribute name="originalServiceLocation" type="string" use="optional"/> <attribute name="affiliateNetwork" type="string" use="optional"/> </extension> </complexContent> © 2008 MultiService Forum. All rights reserved 26 of 31
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface </complexType> <annotation> <documentation xml:lang="en" > ProgramLocationType </documentation> </annotation> <complexType name="ProgramLocationType" abstract="true"> <complexContent> <extension base="tva:ProgramLocationType"> <sequence> <element name="EventInfoURL" type="anyURI" minOccurs="0" maxOccurs="unbounded"/> <element name="RRTParentalGuidance" type="epg:RRTParentalGuidanceType" minOccurs="0" maxOccurs="unbounded"/> <element name="ParentalGuidance" type="mpeg7:ParentalGuidanceType" minOccurs="0" maxOccurs="unbounded"/> <element name="TrickModeRestrictions" type="epg:TrickModeRestrictionType" minOccurs="0"/> <element name="Part" minOccurs="0"> <complexType> <attribute name="total" type="unsignedInt" use="optional"/> </complexType> </element> </sequence> <attribute name="copyRestrictions" type="epg:CopyControlInformationType" use="optional"/> </extension> </complexContent> </complexType> <annotation> <documentation xml:lang="en" > TrickModeRestrictionType </documentation> </annotation> <simpleType name="TrickModeRestrictionType"> <restriction base="string"> <enumeration value="pause"/> <enumeration value="FF"/> <enumeration value="RW"/> </restriction> </simpleType> <annotation> <documentation xml:lang="en" > TrickModeRestrictionsType </documentation> </annotation> <simpleType name="TrickModeRestrictionsType"> <list itemType="epg:TrickModeRestrictionType"/> </simpleType> <annotation> <documentation xml:lang="en" > RatingRegionTableType </documentation> </annotation> <complexType name="RatingRegionTableType"> <sequence> <element name="RatingRegionName" type="mpeg7:TextualType"/> <element name="RatingRegion" type="unsignedByte"/> <element name="TableVersion" type="unsignedByte"/> <sequence> <element name="Dimension" maxOccurs="255"> <complexType> <sequence> <element name="RatingDimensionName" type="mpeg7:TextualType"/> <element name="RatingDimension" type="unsignedByte"/> <element name="GraduatedScale" type="boolean"/> © 2008 MultiService Forum. All rights reserved 27 of 31
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface <element name="DimensionValue" maxOccurs="16"> <complexType> <sequence> <element name="RatingValueText" type="mpeg7:TextualType"/> <element name="AbbrevValueText" type="mpeg7:TextualType"/> <element name="RatingValue"> <simpleType> <restriction base="unsignedByte"> <maxInclusive value="15"/> </restriction> </simpleType> </element> </sequence> </complexType> </element> </sequence> </complexType> </element> </sequence> </sequence> </complexType> <annotation> <documentation xml:lang="en" > RatingRegionTablesType </documentation> </annotation> <complexType name="RatingRegionTablesType"> <sequence> <element name="RatingRegionTable" type="epg:RatingRegionTableType" maxOccurs="unbounded"/> </sequence> </complexType> <annotation> <documentation xml:lang="en" > ScheduleEventType </documentation> </annotation> <complexType name="ScheduleEventType"> <complexContent> <extension base="epg:ProgramLocationType"> <sequence> <element name="PublishedStartTime" type="dateTime" minOccurs="0"/> <element name="PublishedEndTime" type="dateTime" minOccurs="0"/> <element name="PublishedDuration" type="duration" minOccurs="0"/> <element name="Live" type="tva:FlagType" minOccurs="0"/> <element name="Repeat" type="tva:FlagType" minOccurs="0"/> <element name="FirstShowing" type="tva:FlagType" minOccurs="0"/> <element name="LastShowing" type="tva:FlagType" minOccurs="0"/> <element name="Free" type="tva:FlagType" minOccurs="0" /> </sequence> <attribute name="metadataOriginIDRef" type="tva:TVAIDRefType" use="optional"/> <attribute ref="xml:lang" use="optional"/> </extension> </complexContent> </complexType> <annotation> © 2008 MultiService Forum. All rights reserved 28 of 31
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface <documentation xml:lang="en">ScheduleType</documentation> </annotation> <complexType name="ScheduleType"> <sequence> <element name="ScheduleEvent" type="epg:ScheduleEventType" maxOccurs="unbounded"/> </sequence> <attribute name="serviceIDRef" type="tva:TVAIDRefType" use="required"/> <attribute name="start" type="dateTime" use="optional"/> <attribute name="end" type="dateTime" use="optional"/> <attributeGroup ref="tva:fragmentIdentification"/> <attribute name="metadataOriginIDRef" type="tva:TVAIDRefType" use="optional"/> <attribute ref="xml:lang" use="optional"/> </complexType> <annotation> <documentation xml:lang="en" > BroadcastEventType </documentation> </annotation> <complexType name="BroadcastEventType"> <complexContent> <extension base="epg:ScheduleEventType"> <attribute name="serviceIDRef" type="tva:TVAIDRefType" use="optional"/> <attributeGroup ref="tva:fragmentIdentification"/> </extension> </complexContent> </complexType> <annotation> <documentation xml:lang="en" > OnDemandProgramType </documentation> </annotation> <complexType name="OnDemandProgramType"> <complexContent> <extension base="epg:ProgramLocationType"> <sequence> <element name="PublishedDuration" type="duration" minOccurs="0"/> <element name="StartOfAvailability" type="dateTime" minOccurs="0"/> <element name="EndOfAvailability" type="dateTime" minOccurs="0"/> <element name="FirstAvailability" type="tva:FlagType" minOccurs="0"/> <element name="LastAvailability" type="tva:FlagType" minOccurs="0"/> <element name="ImmediateViewing" type="tva:FlagType" minOccurs="0"/> </sequence> <attributeGroup ref="tva:fragmentIdentification"/> <attribute ref="xml:lang" use="optional"/> </extension> </complexContent> </complexType> <annotation> <documentation xml:lang="en" > OnDemandServiceType </documentation> </annotation> <complexType name="OnDemandServiceType"> <sequence> <element name="OnDemandProgram" type="epg:OnDemandProgramType" maxOccurs="unbounded"/> </sequence> <attribute name="serviceIDRef" type="tva:TVAIDRefType" use="required"/> © 2008 MultiService Forum. All rights reserved 29 of 31
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface <attributeGroup ref="tva:fragmentIdentification"/> <attribute name="metadataOriginIDRef" type="tva:TVAIDRefType" use="optional"/> <attribute ref="xml:lang" use="optional"/> </complexType> <annotation> <documentation xml:lang="en">AwardType</documentation> </annotation> <complexType name="AwardType"> <sequence> <element name="Category" type="mpeg7:TextualType"/> <choice minOccurs="0"> <element name="Nominee" type="epg:CreditsItemType"/> <element name="Recipient" type="epg:CreditsItemType"/> </choice> </sequence> </complexType> <annotation> <documentation xml:lang="en" > AwardsListItemType </documentation> </annotation> <complexType name="AwardsListItemType"> <sequence> <element name="Title" type="mpeg7:TextualType"/> <element name="Year" type="gYear"/> <element name="Award" type="epg:AwardType" minOccurs="0" maxOccurs="unbounded"/> </sequence> </complexType> <annotation> <documentation xml:lang="en">AwardsListType</documentation> </annotation> <complexType name="AwardsListType"> <sequence> <element name="AwardsListItem" type="epg:AwardsListItemType" maxOccurs="unbounded"/> </sequence> </complexType> </schema> 6. References [1] IETF RFC 2616, Hypertext Transfer Protocol -- HTTP/1.1 [2] ATIS-0800020, IPTV Electronic Program Guide Metadata Specification [3] W3C REC: eXtensible Markup Language (XML) 1.0 [4] IETF RFC 2396, Uniform Resource Identifiers (URI): Generic Syntax [5] IETF RFC 1738, Uniform Resource Locators (URL) [6] IETF draft-ietf-sipping-config-framework-15.txt [7] MSF 2008.095.05, GMI 2008 Xc Implementation Agreement between UE and Video Media Server (SS-MCF) [8] MSF-SIP-IA.016.FINAL, SIP IA for MSFR4 / GMI2008 [9] ETSI TS 183 063, IMS-based IPTV stage 3 specification © 2008 MultiService Forum. All rights reserved 30 of 31
  • MSF-IA-XML.002-FINAL Implementation Agreement for STB-1/Xa Interface © 2008 MultiService Forum. All rights reserved 31 of 31