BACKGROUND OF THE INVENTION

&null;0001&null; 1. Field of the Invention

&null;0002&null; The present invention relates to a method and apparatus for creating data carousels, in particular providing a user who has a particular file structure in mind with an easy mechanism by which to create and optimise appropriate data carousels.

&null;0003&null; 2. Description of the Related Art

&null;0004&null; A data carousel may be created by developing new data or editing existing data.

&null;0005&null; For instance as part of a DVB compliant system, it is known to provide an information server for broadcasting any form of data, such as MHEG5 applications, HTML pages, Java applications, IRD software upgrades and other data services in the form of DSMCC objects on data carousels. An IRD is an Integrated Receiver Decoder and this term is used in standards documents to describe devices capable of receiving and decoding digital streams, eg. set top boxes and integrated digital TV sets.

&null;0006&null; Raw data may be divided into appropriate DSI (Download Server Initiate), DII (Download Information Indication) or DDB (Download Data Block) sections for insertion into MPEG transport stream packets as a data carousel. These are three types of messages defined in DSM-CC that carry the structure of a data carousel in the broadcast stream. In fact, DSI, DII and DDB are &null;messages&null; but &null;DSI section&null; is used to describe a MPEG section carrying a DSI message. Sections are split into packets, the lowest level structure in the stream. A data carousel is the collection of DSI, DII and DDB messages.

&null;0007&null; Alternatively, however, a user may determine a desired file structure for an object carousel consisting of files, directories and other object types. In DSM-CC there are five object types in an object carousel, namely Files, Directories, a Service Gateway, Streams and StreamEvents. These can all exist in the hierarchical structure that is like a filesystem. It is then a non trivial matter to rearrange the data of the object carousel into DSI, DII and DDB sections in an optimised manner for broadcast as a data carousel. There are many possible data carousel structures that can represent a given object carousel. It is desirable to choose an optimal data carousel that will be most effective by using knowledge of the intended use for the files in the object carousel and knowledge of the receiving equipment, but some experimentation is required to achieve this optimisation. Each time the user wishes to make alterations to the file structure on which the object carousel is based, it is necessary to reconsider entirely the structure of the corresponding data carousel.

OBJECTS OF THE INVENTION

&null;0008&null; It is an object of the present invention to provide a method and apparatus by which a user can easily create data carousels corresponding to desired file structures or object carousels. Furthermore, it is an object to provide a system whereby a user may more easily optimise data for use with a data carousel.

SUMMARY OF THE INVENTION

&null;0009&null; According to the present invention, there is provided a method of creating data carousels including representing an object carousel in a structured data format, analysing the structured data format representation of the object carousel for compatibility with at least one predetermined technical standard, creating a representation of a data carousel in the structured data format based on the step of analysing and providing output data to a carousel according to the structured data format representation of the data carousel.

&null;0010&null; According to the present invention, there is also provided an apparatus for creating data carousels, including a memory containing a data format definition for representing object carousels in a structured data format, a memory containing a data format definition for representing data carousels in the structured data format, a GUI by which a user may create a representation of an object carousel in the structured data format, a processor for analysing the structured data format representation of the object carousel for compatibility with at least one predetermined technical standard and for creating, on the basis of the analysis, a representation in the structured data format of a data carousel according to the data format definition for the structured data format representing data carousels.

&null;0011&null; In this way, by defining the required object carousel as a structured data format representation, it is possible to provide a predetermined algorithm in any appropriate processing language to automatically form a structured data format representation of an equivalent data carousel. Furthermore, compared to previous binary representations of the data carousel, the structured data format representation allows a user relatively easily to understand the structure of the data carousel. This allows the user to edit the resulting data carousel and to optimise it with regard to its use in providing an output byte stream suitable for broadcast.

&null;0012&null; In order to allow conversion from the object carousel structured data format representation to the data carousel structured data format representation, the two structured data format representations should follow predetermined formats. Hence, respective data format definitions may be defined for the structured data format representing object carousels and the structured data format representing data carousels.

&null;0013&null; Once provided with the data format definition for the structured data format representing object carousels, a user may construct a desired data structure in the structured data format for the object carousel. This may then be converted automatically to structured data conforming to the data format definition for the structured data format representing data carousels. With the data format definition for structured data representing data carousels, the user may then edit the structured data representation of the data carousel so as to optimise it.

&null;0014&null; In this respect, the apparatus may be provided with a GUI allowing a user to edit the structured data format representation of the data carousel so as to optimise the arrangement of the data for use as part of a carousel.

&null;0015&null; Having prepared an appropriate data carousel with the structured data format representation, an output stream may be provided to a carousel. Hence, the apparatus preferably includes an output processor for providing data to a carousel according to the structured data format representation of the data carousel.

&null;0016&null; It will be understood that the data carousel represented by the structured data format representation must conform to the appropriate technical standards for the system in which the data carousel is to be broadcast.

&null;0017&null; The specific examples described below are based on several standards documents published by various international organisations.

&null;0018&null; ISO publish the MPEG-2 family of standards of which part 1 (Systems) defines transport streams, packets, sections and multiplexing and part 6 (DSM-CC) defines underlying object and data carousel structures.

&null;0019&null; There are other standards which govern individual digital TV systems such as MHEG-5 (published by ISO) and MHP (published by DVB). They mainly define how the receiving equipment operates but they also refer to the MPEG standards and define further refinements and constraints on the stream structures that are generated.

&null;0020&null; Hence, the technical standards include appropriate standards for carousels and broadcast systems. Preferably, they include DSM-CC standards and relevant standards for broadcast systems.

&null;0021&null; Preferably, the structured data format is XML such that the data format definitions are XML schemas.

&null;0022&null; As mentioned above, conversion from the XML representation of the object carousel to the XML representation of the data carousel can be conducted in any appropriate manner as a data transformation. However, it is particularly advantageous to use an XSLT algorithm to carry out this conversion, since this is particularly well suited. The XSLT language allows convenient interpretation and manipulation of data in XML format.

&null;0023&null; It should be noted that converting the XML representation of the object carousel with an XSLT algorithm is not straightforward, since the XSLT algorithm will require knowledge of the sizes of the files of the object carousel in order to create the appropriate XML representation of the data carousel. Hence, preferably, the sizes of the files of the object carousel are determined and provided in XML as a look-up table such that the XSLT algorithm uses the look up table when creating the XML representation of the data carousel.

&null;0024&null; It will be appreciated that the present invention and its preferred features as described above can be embodied as a computer program or code components stored on a computer readable storage medium.

BRIEF DESCRIPTION OF THE DRAWINGS

&null;0025&null; FIG. 1 illustrates a generalized broadcast system;

&null;0026&null; FIG. 2 illustrates information servers for producing data carousels;

&null;0027&null; FIG. 3 illustrates schematically object/data carousel;

&null;0028&null; FIG. 4 illustrates schematically a file structure in relation to a data carousel structure;

&null;0029&null; FIG. 5 illustrates schematically conversion from object to data carousels;

&null;0030&null; FIG. 6 illustrates schematically an apparatus for embodying the present invention; and

&null;0031&null; FIG. 7 illustrates schematically conversion from object to data carousels.

&null;0032&null; FIG. 1 illustrates a broadcasting system, such as a DVB system, in which an information server is incorporated for providing various types of data file on a carousel.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

&null;0033&null; The invention will be more clearly understood from the following description, given by way of example only, with reference to the accompanying drawings.

&null;0034&null; A play-out section 2 incorporates a number of video/audio sources 4 as well as live sources 6. Data from these sources, for instance in the form of MPEG-2 transport stream packets, is fed to a multiplexer 8 and output from the play-out section 2. The multiplexed stream of data is fed to a modulator 10 for transmission, in this example, from a satellite 12. The signal is then received by an IRD such as set top box 14 of television 16. Signals from a number of other modulators 10&null;, 10&null;, etc may be fed together and transmitted to the satellite 12.

&null;0035&null; In this system, it is also possible to provide an information server 18. Just like the video/audio sources 4,6, the information server 18 provides data, for instance in the form of MPEG transport stream packets to the multiplexer 8 for insertion into the data stream for transmission. The information server may be used to broadcast any form of data, but, in particular, MHEG5 applications, HTML pages, Java applications, IRD software upgrades and other data services in the form of DSM-CC objects on data carousels.

&null;0036&null; The information server may be controlled by a host computer 20.

&null;0037&null; The arrangement of data on object or data carousels is well known in the art and, indeed, has to conform to certain standards, according to the systems in question.

&null;0038&null; FIG. 2 illustrates how one host computer may be used to control any number of information servers, each producing a number of streams.

&null;0039&null; The host, together with an information server constructs a carousel of information, for instance as illustrated in FIG. 3. Transport stream data is constructed appropriately for transmitting in rotation a series of files, directories and other objects. For instance, each page as illustrated in FIG. 3 might comprise MHEG or HTML files or Java applications. As a result, the stream produced includes each of those pages in turn.

&null;0040&null; As illustrated, it is also possible to construct sub carousels, such that on each rotation of the main carousel of pages, a particular page itself rotates through a series of sub pages.

&null;0041&null; As is well known, the output stream is arranged in a predetermined manner. For instance, for DSM-CC, appropriate DSI, DII or DDB sections are arranged and assembled in MPEG transport stream packets.

&null;0042&null; As illustrated schematically in FIG. 4, the DSI/DII/DDB sections may be constructed using raw data 28. Often, however, a user prepares files 30 and determines a required file structure for an object carousel. This must then be converted to the appropriate DSI/DII/DDB sections.

&null;0043&null; Conversion of the various files 30 and their linked inter relations into the appropriate sections is a non trivial process. It is particularly difficult to provide sections in an optimised manner for broadcast and for efficient use by the receiving equipment. A large part of the optimisation process is delivering the data in a way that the receiving equipment can load it quickly from the stream in the order that it needs.

&null;0044&null; As illustrated in FIG. 5, it is proposed that the file structure of the object carousel should be created as an XML representation. XML stands for Extensible Mark-up Language and is a general purpose language that can be used to represent any type of structured information. As illustrated in FIG. 6, a GUI (Graphical User Interface) 40 interacts with a processor 42, for instance including a memory, to enable a user to create the desired object carousel and XML representation 50. Once the desired object carousel has been created as the XML representation 50, the processor 42 then conducts a predetermined conversion so as to produce an XML representation 52 of an equivalent data carousel. At this point, the processor 42 may be used to control an output processor 44 to create the required data stream on the basis of the data carousel defined by the XML representation. In particular, the output processor 44 derives the required raw data, for instance from some storage means and arranges this into appropriate sections as defined by the XML representation of the data carousel.

&null;0045&null; In this way, a user easily achieves an appropriate data carousel according to his/her requirements as defined for the object carousel. Furthermore, the XML representation of the data carousel may be relatively easily understood by the user, particularly as compared to bit/byte representations of data carousels. By means of the GUI 40, the user is then able to modify the generated data carousel as required by modifying the XML representation 52. In comparison, making equivalent modifications of a bit/byte data carousel would be extremely difficult if not impossible for most users.

&null;0046&null; The transformation or conversion process preferably includes the following steps.

&null;0047&null; The object carousel root directory, file, directory and other object declarations are mapped directly into the data carousel document, since the declaration format is identical for object and data carousels.

&null;0048&null; The object carousel contains a sequence that lists the files, directories and other objects that are to appear in the carousel. A list of modules is defined by working sequentially through the object carousel sequence. A module is &null;packed&null; with each object in order up to the point where adding another object would make the cumulative value of the object sizes exceed the module size limit defined in the DSM-CC specification or other standards for broadcast systems as appropriate. A new module is then created until the sequence is fully completed. This algorithm makes a simple fit that can be further optimised by hand later.

&null;0049&null; A message sequence is defined with the DSI and DII messages at the beginning referring to the modules in a simple linear sequence.

&null;0050&null; As the module declarations contain objects in the order described in the object carousel sequence, a message sequence is defined where each module is simply listed in order.

&null;0051&null; The transformation algorithm is representative of methods used by DSM-CC carousel servers to generate a transport stream. The object to data carousel mechanism allows a user to fine-tune the resulting data carousel before generation of a transport stream to ensure better performance based on the rough hints from the transformed object carousel. The object-data carousel transformation mechanism also allows algorithm designers to create alternative mappings to form the basis of later hand optimisation. As a tool, the translation mechanism provides an effort saving measure that can yield considerable benefits.

&null;0052&null; In order to allow a predetermined conversion algorithm to be used, the formats of the XML representations for the object and data carousels are predetermined. This may be achieved by appropriate respective XML schemas.

&null;0053&null; The following is an example of the XML schema for the object carousel representation.

&null;0054&null; -<xsd:schema xmlns:xsd&null;&null;http://www.w3.org/2001/XMLSchema&null;>

&null;0055&null; -<xsd:annotation>

&null;0056&null; -<xsd:documentation>Carousel Configuration schema for Sony

&null;0057&null; MediaCaster</xsd:documentation>

&null;0058&null; </xsd:annotation>

&null;0059&null; -<&null;--elements-->

&null;0060&null; <xsd:element name&null;&null;carousel&null;type&null;&null;carouselType&null;/>

&null;0061&null; <xsd:element name&null;&null;root&null;type&null;&null;directoryType&null;/>

&null;0062&null; <xsd: element name&null;&null;directory&null;type&null;&null;directoryType&null;/>

&null;0063&null; <xsd:element name&null;&null;file&null;type&null;&null;fileType&null;/>

&null;0064&null; <xsd:element name&null;&null;cycle&null;type&null;&null;cycleType&null;/>

&null;0065&null; <xsd:element name&null;&null;instance&null;type&null;&null;instanceType&null;/>

&null;0066&null; <xsd:element name&null;&null;stream&null;type&null;&null;streamType&null;/>

&null;0067&null; <xsd:element name&null;&null;streamEvent&null;type&null;&null;streamEventType&null;/>

&null;0068&null; <xsd:element name&null;&null;objectSequence&null;type&null;&null;objectSequenceType&null;/>

&null;0069&null; <xsd:element name&null;&null;objectRef&null;type&null;&null;objectReffype&null;/>

&null;0070&null; <xsd:element name&null;&null;comment&null;type&null;&null;xsd:string&null;/>

&null;0071&null; -<&null;--types-->

&null;0072&null; -<xsd:complexType name&null;&null;carouselType&null;>

&null;0073&null; -<xsd:sequence>

&null;0074&null; <xsd:element ref&null;&null;comment&null;minOccurs&null;&null;0&null;/>

&null;0075&null; <xsd:element ref&null;&null;root&null;/>

&null;0076&null; <xsd:element ref&null;&null;objectSequence&null;/>

&null;0077&null; </xsd:sequence>

&null;0078&null; </xsd:complexType>

&null;0079&null; -<&null;-- -->

&null;0080&null; -<xsd:complexType name&null;&null;objectSequenceType&null;>

&null;0081&null; -<xsd:sequence>

&null;0082&null; <xsd: element ref&null;&null;comment&null;minOccurs&null;&null;0&null;/>

&null;0083&null; <xsd: element ref&null;&null;objectRef&null;minOccurs&null;&null;0&null;maxOccurs&null;&null;unbounded&null;/>

&null;0084&null; </xsd:sequence>

&null;0085&null; </xsd:complexType>

&null;0086&null; -<&null;-- -->

&null;0087&null; -<xsd:complexType name&null;&null;directoryType&null;>

&null;0088&null; -<xsd:sequence>

&null;0089&null; <xsd:element ref&null;&null;comment&null;minOccurs&null;&null;0&null;/>

&null;0090&null; -<xsd:choice minOccurs&null;&null;0&null; maxOccurs&null;&null;unbounded&null;>

&null;0091&null; <xsd:element ref&null;&null;file&null;/>

&null;0092&null; <xsd:element ref&null;&null;cycle&null;/>

&null;0093&null; <xsd:element ref&null;&null;directory&null;/>

&null;0094&null; </xsd:choice>

&null;0095&null; </xsd: sequence>

&null;0096&null; <xsd:attribute name&null;&null;name&null;type&null;&null;xsd:string&null;use&null;&null;required&null;/>

&null;0097&null; </xsd:complexType>

&null;0098&null; -<&null;-- -->

&null;0099&null; -<xsd:complexType name&null;&null;fileType&null;>

&null;0100&null; -<xsd:sequence>

&null;0101&null; <xsd:element ref&null;&null;comment&null; minOccurs&null;&null;0&null;/>

&null;0102&null; </xsd:sequence>

&null;0103&null; <xsd:attribute name&null;&null;name&null;type&null;&null;xsd: string&null;use&null;&null;required&null;/>

&null;0104&null; <xsd:attribute name&null;&null;content&null;type&null;&null;xsd:string&null;use&null;&null;required&null;/>

&null;0105&null; <xsd:attribute name&null;&null;immediate&null;type&null;&null;xsd:boolean&null;use&null;&null;required&null;/>

&null;0106&null; <xsd:attribute name&null;&null;contentType&null;type&null;&null;xsd:string&null;/>

&null;0107&null; </xsd:complexType>

&null;0108&null; -<&null;-- -->

&null;0109&null; -<xsd:complexType name&null;&null;cycleType&null;>

&null;0110&null; -<xsd:sequence>

&null;0111&null; <xsd:element ref&null;&null;comment&null;minOccurs&null;&null;0&null;/>

&null;0112&null; <xsd:element ref&null;&null;instance&null;maxOccurs&null;&null;unbounded&null;/>

&null;0113&null; </xsd:sequence>

&null;0114&null; <xsd: attribute name&null;&null;name&null;type&null;&null;xsd:string&null;use&null;&null;required&null;/>

&null;0115&null; </xsd:complexType>

&null;0116&null; <&null;-- -->

&null;0117&null; -<xsd:complexType name&null;&null;instanceType&null;>

&null;0118&null; -<xsd:sequence>

&null;0119&null; <xsd:element ref&null;&null;comment&null;minOccurs&null;&null;0&null;/>

&null;0120&null; </xsd:sequence>

&null;0121&null; <xsd: attribute name&null;&null;content&null;type&null;&null;xsd:string&null;use&null;&null;required&null;/>

&null;0122&null; <xsd: attribute name&null;&null;contentType&null;type&null;&null;xsd:string&null;/>

&null;0123&null; </xsd:complexType>

&null;0124&null; -<&null;-- -->

&null;0125&null; <xsd:complexType name&null;&null;streamType&null;abstract&null;&null;true&null;>

&null;0126&null; -<xsd:sequence>

&null;0127&null; <xsd:element ref&null;&null;comment&null;minOccurs&null;&null;0&null;/>

&null;0128&null; </xsd:sequence>

&null;0129&null; <xsd:attribute name&null;&null;name&null;type&null;&null;xsd:string&null;use&null;&null;required&null;/>

&null;0130&null; </xsd:complexType>

&null;0131&null; -<&null;-- -->

&null;0132&null; <xsd:complexType name&null;&null;streamEventType&null;abstract&null;&null;true&null;>

&null;0133&null; -<xsd:sequence>

&null;0134&null; <xsd:element ref&null;&null;comment&null;minOccurs&null;&null;0&null;/>

&null;0135&null; </xsd:sequence>

&null;0136&null; <xsd:attribute name&null;&null;name&null;type&null;&null;xsd:string&null;use&null;&null;required&null;/>

&null;0137&null; </xsd:complexType>

&null;0138&null; -<&null;-- -->

&null;0139&null; -<xsd:complexType name&null;&null;objectReffype&null;>

&null;0140&null; <xsd:sequence />

&null;0141&null; <xsd:attribute name&null;&null;path&null;type&null;&null;xsd:string&null;use&null;&null;required&null;/>

&null;0142&null; </xsd:complexType>

&null;0143&null; </xsd:schema>

&null;0144&null; As exemplified above, a preferred schema allows concise declaration of the hierarchical structure of files, directories and other objects in an object carousel, together with hints about the order in which they should appear in a data carousel.

&null;0145&null; An example of an appropriate XML schema for the data carousel representation is given below.

&null;0146&null; -<xsd:schema xmlns:xsd&null;&null;http://www.w3.org/2001/XMLSchema&null;>

&null;0147&null; -<xsd:annotation>

&null;0148&null; <xsd:documentation>Carousel Configuration schema for Sony

&null;0149&null; MediaCaster</xsd:documentation>

&null;0150&null; </xsd:annotation>

&null;0151&null; -<&null;-- elements-->

&null;0152&null; <xsd:element name&null;&null;carousel&null;type&null;&null;carouselType&null;/>

&null;0153&null; <xsd:element name&null;&null;root&null;type&null;&null;directoryType&null;/>

&null;0154&null; <xsd:element name&null;&null;directory&null;type&null;&null;directoryType&null;/>

&null;0155&null; <xsd:element name&null;&null;file&null;type&null;&null;fileType&null;/>

&null;0156&null; <xsd:element name&null;&null;cycle&null;type&null;&null;cycleType&null;/>

&null;0157&null; <xsd:element name&null;&null;instance&null;type&null;&null;instanceType&null;/>

&null;0158&null; <xsd:element name&null;&null;stream&null;type&null;&null;streamType&null;/>

&null;0159&null; <xsd:element name&null;&null;streamEvent&null;type&null;&null;streamEventType&null;/>

&null;0160&null; <xsd:element name&null;&null;programStreamInfo&null;type&null;&null;programStreamInfoType&null;/>

&null;0161&null; <xsd:element name&null;&null;eventStreamInfo&null;type&null;&null;eventStreamInfoType&null;/>

&null;0162&null; <xsd:element name&null;&null;event&null;type&null;&null;eventType&null;/>

&null;0163&null; <xsd:element name&null;&null;module&null;type&null;&null;moduleType&null;/>

&null;0164&null; <xsd:element name&null;&null;objectRef&null;type&null;&null;objectRefType&null;/>

&null;0165&null; >xsd:element name&null;&null;binaryContent&null;type&null;&null;binaryContentType&null;/>

&null;0166&null; <xsd:element name&null;&null;DII&null;type&null;&null;DIIType&null;/>

&null;0167&null; <xsd:element name&null;&null;moduleInfo&null;type&null;&null;moduleInfoType&null;/>

&null;0168&null; <xsd:element name&null;&null;tapList&null;type&null;&null;tapListType&null;/>

&null;0169&null; <xsd:element name&null;&null;privateData&null;type&null;&null;privateDataType&null;/>

&null;0170&null; <xsd:element name&null;&null;objectUseTap&null;type&null;&null;objectUseTapType&null;/>

&null;0171&null; <xsd:element name&null;&null;tap&null;type&null;&null;tapType&null;/>

&null;0172&null; <xsd:element name&null;&null;userInfo&null;type&null;&null;userInfoType&null;/>

&null;0173&null; <xsd:element name&null;&null;labelDescriptor&null;type&null;&null;labelDescriptorType&null;/>

&null;0174&null; <xsd: element name&null;&null;cachingPriorityDescriptor&null;

&null;0175&null; type&null;&null;cachingPriorityDescriptorType&null;/>

&null;0176&null; <xsd:element name&null;&null;descriptor&null;type&null;&null;descriptorType&null;/>

&null;0177&null; <xsd:element name&null;&null;DSI&null;type&null;&null;DSIType&null;/>

&null;0178&null; <xsd:element name&null;&null;messageSequence&null;type&null;&null;messageSequenceType&null;/>

&null;0179&null; <xsd:element name&null;&null;messageRef&null;type&null;&null;messageReffype&null;/>

&null;0180&null; <xsd:element name&null;&null;elementaryStream&null;type&null;&null;elementaryStreamType&null;/>

&null;0181&null; <xsd:element name&null;&null;comment&null;type&null;&null;xsd:string&null;/>

&null;0182&null; <&null;-- types-->

&null;0183&null; -<xsd:complexType name&null;&null;carouselType&null;>

&null;0184&null; -<xsd:sequence>

&null;0185&null; <xsd:element ref&null;&null;comment&null;minOccurs&null;&null;0&null;/>

&null;0186&null; <xsd:element ref&null;&null;root&null;/>

&null;0187&null; <xsd:element ref&null;&null;module&null;maxOccurs&null;&null;unbounded&null;/>

&null;0188&null; <xsd:element ref&null;&null;DII&null;maxOccurs&null;&null;unbounded&null;/>

&null;0189&null; <xsd:element ref&null;&null;DSI&null;/>

&null;0190&null; <xsd:element ref-&null;messageSequence&null;/>

&null;0191&null; <xsd:element ref&null;&null;elementaryStream&null;/>

&null;0192&null; </xsd:sequence>

&null;0193&null; </xsd:complexType>

&null;0194&null; -<xsd:complexType name&null;&null;directoryType&null;>

&null;0195&null; -<xsd:sequence>

&null;0196&null; <xsd: element ref&null;&null;comment&null;minOccurs&null;&null;0&null;/>

&null;0197&null; -<xsd: choice minOccurs&null;&null;0&null;maxOccurs&null;&null;unbounded&null;>

&null;0198&null; <xsd:element ref&null;&null;file&null;/>

&null;0199&null; <xsd:element ref&null;&null;cycle&null;/>

&null;0200&null; <xsd:element ref&null;&null;directory&null;/>

&null;0201&null; <xsd:element ref&null;&null;stream&null;/>

&null;0202&null; <xsd:element ref&null;&null;streamEvent&null;/>

&null;0203&null; </xsd:choice>

&null;0204&null; </xsd:sequence>

&null;0205&null; <xsd:attribute name&null;&null;name&null;type&null;&null;xsd:string&null;use&null;&null;required&null;/>

&null;0206&null; </xsd:complexType>

&null;0207&null; -<xsd:complexType name&null;&null;fileType&null;>

&null;0208&null; -<xsd:sequence>

&null;0209&null; <xsd:element ref&null;&null;comment&null;minOccurs&null;&null;0&null;/>

&null;0210&null; </xsd:sequence>

&null;0211&null; <xsd:attribute name&null;&null;name&null;type&null;&null;xsd:string&null;use&null;&null;required&null;/>

&null;0212&null; <xsd:attribute name&null;&null;content&null;type&null;&null;xsd:string&null;use&null;&null;required&null;/>

&null;0213&null; <xsd:attribute name&null;&null;immediate&null;type&null;&null;xsd:boolean&null;use&null;&null;required&null;/>

&null;0214&null; <xsd:attribute name&null;&null;contentType&null;type&null;&null;xsd:string&null;/>

&null;0215&null; </xsd:complexType>

&null;0216&null; -<&null;-- -->

&null;0217&null; <xsd:complexType name&null;&null;cycleType&null;>

&null;0218&null; -<xsd:sequence>

&null;0219&null; <xsd: element ref&null;&null;comment&null;minOccurs&null;&null;0&null;/>

&null;0220&null; <xsd:element ref&null;&null;instance&null;maxOccurs&null;&null;unbounded&null;/>

&null;0221&null; </xsd:sequence>

&null;0222&null; <xsd:attribute name&null;&null;name&null;type&null;&null;xsd:string&null;use&null;&null;required&null;/>

&null;0223&null; </xsd:complexType>

&null;0224&null; -<&null;-- -->

&null;0225&null; -<xsd:complexType name&null;&null;instanceType&null;>

&null;0226&null; -<xsd:sequence>

&null;0227&null; <xsd:element ref&null;&null;comment&null;minOccurs&null;&null;0&null;/>

&null;0228&null; </xsd:sequence>

&null;0229&null; <xsd:attribute name&null;&null;content&null;type&null;&null;xsd:string&null;use&null;&null;required&null;/>

&null;0230&null; <xsd:attribute name&null;&null;contentType&null;type&null;&null;xsd:string&null;/>

&null;0231&null; </xsd:complexType>

&null;0232&null; -<&null;-- -->

&null;0233&null; -<xsd:complexType name&null;&null;streamType&null;>

&null;0234&null; -<xsd:sequence>

&null;0235&null; <xsd:element ref&null;&null;comment&null;minOccurs&null;&null;0&null;/>

&null;0236&null; <xsd:element ref-&null;programStreamInfo&null;/>

&null;0237&null; </xsd:sequence>

&null;0238&null; <xsd: attribute name&null;&null;name&null;type&null;&null;xsd:string&null;use&null;&null;required&null;/>

&null;0239&null; </xsd:complexType>

&null;0240&null; -<&null;-- -->

&null;0241&null; -<xsd:complexType name&null;&null;streamEventType&null;>

&null;0242&null; -<xsd:sequence>

&null;0243&null; <xsd:element ref&null;&null;comment&null;minOccurs&null;&null;0&null;/>

&null;0244&null; <xsd:element ref&null;&null;event&null;maxOccurs&null;&null;unbounded&null;/>

&null;0245&null; <xsd:element ref&null;&null;eventStreamInfo&null;/>

&null;0246&null; <xsd:element ref&null;&null;programStreamInfo&null;/>

&null;0247&null; </xsd:sequence>

&null;0248&null; <xsd:attribute name&null;&null;name&null;type&null;&null;xsd:string&null;use&null;&null;required&null;/>

&null;0249&null; </xsd:complexType>

&null;0250&null; -<&null;-- -->

&null;0251&null; -<xsd:complexType name&null;&null;programStreamInfoType&null;>

&null;0252&null; <xsd:sequence />

&null;0253&null; <xsd: attribute name&null;&null;audio&null;type&null;&null;xsd:boolean&null;use&null;&null;required&null;/>

&null;0254&null; <xsd: attribute name&null;&null;video&null;type&null;&null;xsd:boolean&null;use&null;&null;required&null;/>

&null;0255&null; <xsd:attribute name&null;&null;data&null;type&null;&null;xsd:boolean&null;use&null;&null;required&null;/>

&null;0256&null; <xsd: attribute name&null;&null;description&null;type&null;&null;xsd:string&null;use&null;&null;required&null;/>

&null;0257&null; <xsd: attribute name&null;&null;durationSeconds&null;type&null;&null;xsd:integer&null;use&null;&null;required&null;/>

&null;0258&null; <xsd: attribute name&null;&null;durationMicroSeconds&null;type&null;&null;xsd:integer&null;use&null;&null;required&null;/>

&null;0259&null; <xsd: attribute name&null;&null;transportStreamID&null;type&null;&null;xsd:integer&null;use&null;&null;required&null;/>

&null;0260&null; <xsd:attribute name&null;&null;programNumber&null;type&null;&null;xsd:integer&null;use&null;&null;required&null;/>

&null;0261&null; <xsd:attribute name&null;&null;networkID&null;type&null;&null;xsd:integer&null;use&null;&null;required&null;/>

&null;0262&null; <xsd:attribute name&null;&null;PMTTag&null;type&null;&null;xsd:integer&null;use&null;&null;required&null;/>

&null;0263&null; </xsd:complexType>

&null;0264&null; -<&null;-- -->

&null;0265&null; <xsd:complexType name&null;&null;eventStreamInfoType&null;>

&null;0266&null; <xsd:sequence />

&null;0267&null; <xsd:attribute name&null;&null;pid&null;type&null;&null;xsd:integer&null;use&null;&null;required&null;/>

&null;0268&null; <xsd: attribute name&null;&null;bitrate&null;type&null;&null;xsd:integer&null;use&null;&null;required&null;/>

&null;0269&null; </xsd:complexType>

&null;0270&null; -<&null;-- -->

&null;0271&null; - <xsd:complexType name&null;&null;eventType&null;>

&null;0272&null; <xsd:sequence />

&null;0273&null; <xsd:attribute name&null;&null;name&null;type&null;&null;xsd:string&null;use&null;&null;required&null;/>

&null;0274&null; <xsd:attribute name&null;&null;id&null;type&null;&null;xsd:integer&null;use&null;&null;required&null;/>

&null;0275&null; </xsd:complexType>

&null;0276&null; -<xsd:complexType name&null;&null;moduleType&null;>

&null;0277&null; -<xsd:sequence>

&null;0278&null; <xsd: element ref&null;&null;comment&null;minOccurs&null;&null;0&null;/>

&null;0279&null; -<xsd:choice>

&null;0280&null; <xsd: element ref-&null;objectRef&null;minOccurs&null;&null;0&null;maxOccurs&null;&null;unbounded&null;/>

&null;0281&null; <xsd:element ref&null;&null;binaryContent&null;/>

&null;0282&null; </xsd:choice>

&null;0283&null; </xsd:sequence>

&null;0284&null; <xsd:attribute name&null;&null;name&null;type&null;&null;xsd:string&null;use&null;&null;required&null;/>

&null;0285&null; </xsd:complexType>

&null;0286&null; -<&null;-- -->

&null;0287&null; -<xsd:complexType name&null;&null;objectRefType&null;>

&null;0288&null; <xsd:sequence />

&null;0289&null; <xsd: attribute name&null;&null;path&null;type&null;&null;xsd:string&null;use&null;&null;required&null;/>

&null;0290&null; </xsd:complexType>

&null;0291&null; -<&null;-- -->

&null;0292&null; <xsd:complexType name&null;&null;binaryContentType&null;>

&null;0293&null; <xsd:sequence />

&null;0294&null; <xsd:attribute name&null;&null;path&null;type&null;&null;xsd:string&null;use&null;&null;required&null;/>

&null;0295&null; </xsd:complexType>

&null;0296&null; -<&null;-- -->

&null;0297&null; -<xsd:complexType name&null;&null;DIIType&null;>

&null;0298&null; -<xsd:sequence>

&null;0299&null; <xsd:element ref&null;&null;moduleInfo&null;minOccurs&null;&null;0&null;maxOccurs&null;&null;unbounded&null;/>

&null;0300&null; <xsd:element ref&null;&null;privateData&null;minOccurs&null;&null;0&null;maxOccurs&null;&null;unbounded&null;/>

&null;0301&null; </xsd:sequence>

&null;0302&null; <xsd:attribute name&null;&null;name&null;type&null;&null;xsd:string&null;use&null;&null;required&null;/>

&null;0303&null; <xsd:attribute name&null;&null;transactionID&null;type&null;&null;xsd:hexBinary&null;/>

&null;0304&null; <xsd: attribute name&null;&null;downloadID&null;type&null;&null;xsd:integer&null;/>

&null;0305&null; /xsd:complexType>

&null;0306&null; -<&null;-- -->

&null;0307&null; -<xsd:complexType name&null;&null;modulelnfoType&null;>

&null;0308&null; -<xsd:sequence>

&null;0309&null; <xsd:element ref&null;&null;tapList&null;/>

&null;0310&null; <xsd:element ref&null;&null;userInfo&null;/>

&null;0311&null; </xsd:sequence>

&null;0312&null; <xsd: attribute name&null;&null;moduleRef&null;type&null;&null;xsd:string&null;use&null;&null;required&null;/>

&null;0313&null; <xsd:attribute name&null;&null;moduleTimeOut&null;type&null;&null;xsd:hexBinary&null;/>

&null;0314&null; <xsd:attribute name&null;&null;blockTimeOut&null;type&null;&null;xsd:hexBinary&null;/>

&null;0315&null; <xsd: attribute name&null;&null;minBlockTime&null;type&null;&null;xsd:hexBinary&null;/>

&null;0316&null; </xsd:complexType>

&null;0317&null; -<xsd:complexType name&null;&null;tapListType&null;>

&null;0318&null; -<xsd:sequence>

&null;0319&null; <xsd:element ref&null;&null;objectUseTap&null;/>

&null;0320&null; <xsd:element ref&null;&null;tap&null;minOccurs&null;&null;0&null;maxOccurs&null;&null;unbounded&null;/>

&null;0321&null; </xsd:sequence>

&null;0322&null; </xsd:complexType>

&null;0323&null; -<xsd:complexType name&null;&null;objectUseTapType&null;>

&null;0324&null; <xsd:sequence />

&null;0325&null; <xsd:attribute name&null;&null;tag&null;type&null;&null;xsd:integer&null;/>

&null;0326&null; </xsd:complexType>

&null;0327&null; -<&null;-- -->

&null;0328&null; -<xsd:complexType name&null;&null;tapType&null;>

&null;0329&null; <xsd:sequence />

&null;0330&null; <xsd:attribute name&null;&null;id&null;type&null;&null;xsd:integer&null;/>

&null;0331&null; <xsd:attribute name&null;&null;use&null;type&null;&null;xsd:integer&null;/>

&null;0332&null; <xsd:attribute name&null;&null;tag&null;type&null;&null;xsd:integer&null;/>

&null;0333&null; </xsd:complexType>

&null;0334&null; -<&null;-- -->

&null;0335&null; -<xsd:complexType name&null;&null;userInfoType&null;>

&null;0336&null; -<xsd:sequence>

&null;0337&null; <xsd:element name&null;&null;compressedModuleDescriptor&null;/>

&null;0338&null; <xsd:element ref&null;&null;labelDescriptor&null;/>

&null;0339&null; <xsd:element ref&null;&null;cachingPriorityDescriptor&null;/>

&null;0340&null; <xsd:element ref-&null;descriptor&null;maxOccurs&null;&null;unbounded&null;/>

&null;0341&null; </xsd:sequence>

&null;0342&null; </xsd:complexType>

&null;0343&null; -<&null;-- -->

&null;0344&null; -<xsd:complexType name&null;&null;labelDescriptorType&null;>

&null;0345&null; <xsd:sequence/>

&null;0346&null; <xsd:attribute name&null;&null;label&null;type&null;&null;xsd:string&null;/>

&null;0347&null; </xsd:complexType>

&null;0348&null; -<&null;-- -->

&null;0349&null; -<xsd:complexType name&null;&null;cachingPriorityDescriptorType&null;>

&null;0350&null; <xsd:sequence/>

&null;0351&null; <xsd:attribute name&null;&null;priorityValue&null;type-&null;xsd:byte&null;/>

&null;0352&null; <xsd:attribute name&null;&null;transparencyLevel&null;type&null;&null;xsd:byte&null;/>

&null;0353&null; </xsd:complexType>

&null;0354&null; -<&null;-- -->

&null;0355&null; -<xsd:complexType name&null;&null;descriptorType&null;>

&null;0356&null; <xsd:sequence />

&null;0357&null; <xsd:attribute name&null;&null;tag&null;type&null;&null;xsd:byte&null;/>

&null;0358&null; </xsd:complexType>

&null;0359&null; -<&null;-- -->

&null;0360&null; -<xsd:complexType name&null;&null;privateDataType&null;>

&null;0361&null; <xsd:sequence />

&null;0362&null; </xsd:complexType>

&null;0363&null; -<&null;-- -->

&null;0364&null; -<xsd:complexType name&null;&null;DSIType&null;>

&null;0365&null; -<xsd:sequence>

&null;0366&null; <xsd:element ref&null;&null;comment&null;minOccurs&null;&null;0&null;/>

&null;0367&null; </xsd:sequence>

&null;0368&null; <xsd:attribute name&null;&null;name&null;type&null;&null;xsd:string&null;use&null;&null;required&null;/>

&null;0369&null; </xsd:complexType>

&null;0370&null; -<&null;-- -->

&null;0371&null; -<xsd:complexType name&null;&null;messageSequenceType&null;>

&null;0372&null; -<xsd:sequence>

&null;0373&null; <xsd:element ref&null;&null;comment&null;minOccurs&null;&null;0&null;/>

&null;0374&null; <xsd:element ref&null;&null;messageRef&null;minOccurs&null;&null;0&null; maxOccurs&null;&null;unbounded&null;/>

&null;0375&null; </xsd:sequence>

&null;0376&null; </xsd:complexType>

&null;0377&null; -<&null;-- -->

&null;0378&null; -<xsd:complexType name&null;&null;messageRefType&null;>

&null;0379&null; <xsd:sequence />

&null;0380&null; <xsd: attribute name&null;&null;name&null;type&null;&null;xsd:string&null;use&null;&null;required&null;/>

&null;0381&null; </xsd:complexType>

&null;0382&null; -<&null;-- -->

&null;0383&null; -<xsd:complexType name&null;&null;elementaryStreamType&null;>

&null;0384&null; -<xsd:sequence>

&null;0385&null; <xsd:element ref&null;&null;comment&null;minOccurs&null;&null;0&null;/>

&null;0386&null; </xsd:sequence>

&null;0387&null; <xsd: attribute name&null;&null;name&null;type&null;&null;xsd:string&null;use&null;&null;required&null;/>

&null;0388&null; </xsd:complexType>

&null;0389&null; -<&null;-- -->

&null;0390&null; </xsd:schema>

&null;0391&null; As exemplified above, a preferred schema provides a readable description of the detailed structure of a data carousel. It specifies the grouping of objects into modules, the parameters associated with modules and the order and relative frequency of DSI, DII and DDB sections in the output stream. These are all factors that can affect the performance of the broadcast at the receiving equipment and it is desirable to allow easy experimentation with these parameters in order to maximise performance.

&null;0392&null; It will, of course, be evident that other schemas could also be constructed, though, then, of course, the conversion between the XML representations would be different.

&null;0393&null; Conversion may be achieved with any appropriate algorithm defined using any desired language, such as C&null;&null;.

&null;0394&null; FIG. 7 illustrates schematically a conversion process using an XSLT algorithm 54. XSLT stands for Extensible Stylesheet Language Transformation and is a language and processor that allows relatively easy development of transformations between different formats of XML. It is particularly well suited to converting XML, because the language has built-in features for interpreting and transforming XML. However, the XSLT algorithm needs to know the sizes of the files of the object carousel in order to create the appropriate data carousel XML representation. The XSLT algorithm itself is unable to determine the sizes. Therefore, an additional algorithm 56 is provided to analyse the object carousel so as to determine the size of files and provide this information as an XML look-up table 58. Thus, the XSLT conversion algorithm analyses the XML representation of the object carousel and uses information regarding file size from the XML look-up table to create the XML representation of the data carousel.

&null;0395&null; The stylesheet implements a simple module packing algorithm to transform an XML object carousel structure into a detailed XML data carousel structure. Implementation in XSLT allows convenient interpretation of the incoming XML structure and also allows flexibility about where in the system the algorithm is executed.

&null;0396&null; In addition, more sophisticated techniques for creating data carousel structures would be relatively easy to incorporate and the implementation would be easily adaptable to accommodate future changes to the object carousel and data carousel XML schemas.

&null;0397&null; The look-up table algorithm for object carousel file sizes may be implemented as a UNIX shell script. An example is given below.

&null;0398&null; &null;&null;/bin/sh

&null;0399&null; &null;

&null;0400&null; &null; Given an object carousel XML description on stdin, generate a list of

&null;0401&null; &null; Pathnames used by the carousel and the sizes of the corresponding

&null;0402&null; &null; files. The list is in XML and appears on stdout.

&null;0403&null; &null;

&null;0404&null; &null; usage: generateFileSizes carouselDir

&null;0405&null; &null;

&null;0406&null; &null; check args

&null;0407&null; if&null;$&null;&null;&null;1&null;; then

&null;0408&null; echo &null;usage:generateFileSizes carouselDir&null;1>&2

&null;0409&null; exit 1

&null;0410&null; fi

&null;0411&null; &null; temporary file

&null;0412&null; TMPFILE&null;generateFileSizes.$$

&null;0413&null; &null; where are the carousel files&null;

&null;0414&null; CAROUSELDIR&null;&null;$1&null;

&null;0415&null; &null; separate elements that are on the same line

&null;0416&null; &null; NOTE it seems to be necessary to go via a temorary file . . .

&null;0417&null; &null; a pipe doesn't seem to work

&null;0418&null; sed -e's/>/>Vg'>$TMPFILE

&null;0419&null; &null; isolate the content files that appear in the carousel

&null;0420&null; FILES&null;&null;cat $TMPFILE&null;sed -n -e&null;s/.*content&null;&null;&null;&null;(&null;&null;&null;*&null;)&null;&null;.*$&null;1/p&null;

&null;0421&null; &null; output an element listing the files and their sizes

&null;0422&null; echo &null;<files>&null;

&null;0423&null; for i in $FILES; do

&null;0424&null; &null; get the size of a file

&null;0425&null; SIZE&null;&null;1s -1$CAROUSELDIR/$i&null;awk&null;&null;print $5&null;&null;

&null;0426&null; &null; output an element

&null;0427&null; echo &null;<file path&null;&null;&null;$i&null;&null;size&null;&null;&null;$SIZE&null;&null;/>&null;

&null;0428&null; done

&null;0429&null; echo &null;</files>&null;

&null;0430&null; rm $TMPFILE

&null;0431&null; This script generates an XML look-up table that maps file names used by an object carousel to the sizes of the files. References to files are extracted from an XML object carousel description and each file is examined in turn to produce a list of XML elements, each containing the name of a file and its size in bytes.

&null;0432&null; The following is an example of a look-up table:

&null;0433&null; <files>

&null;0434&null; <file path&null;&null;diddle.txt&null;size&null;&null;168&null;/>

&null;0435&null; <file path&null;&null;dingdong.txt&null;size&null;&null;269&null;/>

&null;0436&null; <file path&null;&null;kxmrain.txt&null;size&null;&null;423&null;/>

&null;0437&null; <file path&null;&null;raining.txt&null;size&null;&null;212&null;/>

&null;0438&null; <file path&null;&null;Jack/jack.txt&null;size&null;&null;72&null;/>

&null;0439&null; <file path&null;&null;Jack/jacksprat.txt&null;size&null;&null;124&null;/>

&null;0440&null; <file path&null;&null;Jack/jackjill.txt&null;size&null;&null;259&null;/>

&null;0441&null; <file path&null;&null;More/sheep.txt&null;size&null;&null;167&null;/>

&null;0442&null; <file path&null;&null;More/owl.txt&null;size&null;&null;1205&null;/>

&null;0443&null; <file path&null;&null;More/Other/dance.txt&null;size&null;&null;194&null;/>

&null;0444&null; <file path&null;&null;More/Other/goosey.txt&null;size&null;&null;223&null;/>

&null;0445&null; <file path&null;&null;More/Other/hush.txt&null;size&null;&null;616&null;/>

&null;0446&null; <file path&null;&null;More/Other/kookaburra.txt&null;size&null;&null;299&null;/>

&null;0447&null; <file path&null;&null;More/Other/mulberry.txt&null;size&null;&null;1409&null;/>

&null;0448&null; <file path&null;&null;More/Other/unicom.txt&null;size&null;&null;222&null;/>

&null;0449&null; <file path&null;&null;More/Other/georgie.txt&null;size&null;&null;128&null;/>

&null;0450&null; <file path&null;&null;More/Other/hickory.txt&null;size&null;&null;125&null;/>

&null;0451&null; <file path&null;&null;More/Other/knickknack.txt&null;size&null;&null;2032&null;/>

&null;0452&null; <file path&null;&null;More/Other/ladybird.txt&null;size&null;&null;189&null;/>

&null;0453&null; <file path&null;&null;More/Other/spider.txt&null;size&null;&null;210&null;/>

&null;0454&null; </files>

&null;0455&null; Finally, it should be appreciated that the present invention is not constrained to television systems but could be applied to any data broadcast system, based, for instance, on MPEG streams, such as DAB (Digital Audio Broadcasting) digital radio or custom broadcast applications.