Discovery information for IP multicast

Field of the invention

0001The invention relates to the delivery of multimedia services from a DVB compliant bundle to subscribers connected to an IP network. The services are delivered over IP multicast.

Background of the invention

Broadcast of multimedia services

0002Digital multimedia services such as for example television broadcast are currently delivered through service providers such as cable companies, satellite operators and, of course, direct terrestrial broadcast reception via traditional antennas. Conventional cable service requires the installation of a dedicated cable to the subscriber's residence. Satellite broadcast service requires that the users have a satellite dish located on or somewhere close to their residence. Antennas are generally limited to the reception of local programming.

0003<figref idref="f0001">Fig. 1</figref> schematically shows a service provider 100 and satellite broadcast / reception equipment 101 used to deliver digital multimedia services to a subscriber.

0004The multimedia services are delivered to subscribers equipped with a Set Top Box (STB) 102 or any other device that allows to receive, decode and process the broadcast services. Other examples for such devices are a personal computer or a decoder integrated in a television set. The STB is connected to an audiovisual display 103 which allows to render graphics and sounds produced at an output of the STB as a result of processing. The STB receives instructions from a user through a control interface such as for example a remote control 104 or a keyboard. This allows to instruct the STB to switch from one service to another, e.g. to switch from one television channel to another.

0005The service providers may broadcast the multimedia services in the frame of an offer and according to a widespread regional standard, e.g., the DVB-SI (used in Europe) and ATSC-PSIP (used in the US) standards which are used for satellite and terrestrial broadcast, or the SCTE (used in the US) which is similar to the ATSC-PSIP standard but applied to cable networks. The standards each include similar functionalities including the use of service information in transport stream. The standards are well known and described in the art. The offer typically comprises a plurality of services, such as for example audio and/or visual programmes, data services or applications. Each service may be transmitted in data packets according to a well known MPEG-2 standard. The data packets are multiplexed in transport streams. A transport stream may therefore carry a plurality of services of the offer. Due to bandwidth reasons, the service provider may decide to use more than one transport stream to transport the services, each one of the transport streams being broadcast at a predetermined frequency. The transport streams are part of a regional standard compliant bundle. Furthermore each transport stream includes tables of Service information (SI) which indicates for example which services are available in a determined transport stream, or at which frequency the transport streams are broadcast.

0006In order to receive, decode and process the services, the STB is MPEG and regional standard compliant. The STB extracts and processes service information which allows for example to retrieve a description of a service and subsequently to select a service by tuning to a corresponding transport stream and filtering data packets.

IP-based multicast

0007IP based multicast relies on an infrastructure, in which an Internet Service Provider (ISP) operates the multicasting of audio/visual content with or without interactivity from various multimedia service operators and all the associated signalisation. Referring to <figref idref="f0001">Fig. 2</figref>, audio/visual content received for example from a satellite dish 200 is encapsulated in IP compliant format by an ISP 201 and multicast on the internet 202.

0008IP based multicast bears the possibility to easily combine the offers of a plurality of service providers that may deliver their programs over various types of distribution systems (cable network, satellite, terrestrial). All offers may be combined and brought to the subscriber using the internet. Hence the subscriber requires only one access, i.e. an access to the internet. This provides flexibility both to the ISP and to the subscriber.

0009The subscribers of the IP based multicast service providers have an IP compliant STB 203 and require a connection to the internet. Possible types of connections to the internet include a PSTN telephone network, an ADSL connection or a permanent broadband connection such as a fibreglass or cable network line.

0010A bandwidth of the connection to the internet may considerably vary depending on the type of connection used. The limitations of the available bandwidth has encouraged to develop IP based multicast systems which allow to selectively multicast a limited number of services from one localisation (IP address and port pair) to a range of subscribed STBs, e.g., a determined set top box obtains the services he has subscribed to only. It appears that the typical bandwidth available for internet connections is often at least one order of magnitude smaller than a bandwidth available in conventional cable networks or Satellite broadcast systems.

0011In known IP multicast networks, the STB may send requests to the ISP for receiving data, thereby submitting a localisation, i.e. an IP multicast address and port pair at which the data is being multicast. In response to the request, corresponding IP data packets are routed to the STB.

0012An example of an IP based multicast is described in <patcit id="pcit0001" dnum="US6351467B"><text>US 6,351,467</text></patcit>. A multicast network system utilizes a high speed link to multicast multimedia information from the Internet to a plurality of receivers (e.g. personal computers). Information from selected web sites is organized into "channels" and the receivers store the received channels such that a user can access the web page content at a hard disk speed. A conditional access system may ensure that only authorized receivers receive the channels.

0013Another example of an IP based multicast is described in <patcit id="pcit0002" dnum="WO9963759A"><text>WO99/63759</text></patcit>. The described system is used to broadcast content based on IP multicast using for example ADSL connections to reach set top boxes. The system allows to retrieve broadcast television signals and to configure these signals into IP format for transmission over a network. Furthermore the system comprises a management system for managing a subscriber's access to the television signals. The subscriber may select television programs using an Interactive Program Guide (IPG). The subscriber accesses the IPG through the Set Top Box (STB). In the STB implementation some memory may be available locally for storing specific information, or alternatively, the entire IPG is maintained in the network. The system further has a Digital TV Manager (DTVM), distinct from the STB, that provides end to end management of services and resources of the integrated broadcast delivery system. The DTVM in conjunction with the IPG provides a subscriber with the ability to channel browse for TV programs. Data delivered to the IPG is tailored by the provider based on a number of parameters such as the customer profile.

0014Another example of an IP based multicast system may be found in <patcit id="pcit0003" dnum="WO9931871A"><text>WO99/31871</text></patcit>. This system was specifically designed to take into account the limited bandwidth of subscriber's internet connection. One or more central channel server(s) collect(s) information about available programming services distributed from a multiplicity of content providers. The channel server maintains a channel list database which tracks available content channel offerings and a subscriber database, which contains subscriber identifications and permitted channels for each subscriber. The subscriber sends requests for programs to the channel server which checks the request and enables a flow of channel programming from the content provider to the subscriber's STB.

0015In both <patcit id="pcit0004" dnum="WO9931871A"><text>WO99/31871</text></patcit> and <patcit id="pcit0005" dnum="WO9963759A"><text>WO99/63759</text></patcit>, the subscriber is in communication with a server that receives and processes requests for programs. The flow of the program to the subscriber's STB is enabled only if the subscriber's request is found by the server to be valid. In order to provide this functionality, the server needs to process channel information from the content providers and to maintain a subscriber database.

0016It appears that the bandwidth of subscriber's internet connections is increasing as fibreglass networks or other performing technologies are being deployed. The bandwidth is often reaching values which is comparable with that of bandwidth available in conventional cable networks or Satellite broadcast systems.

Summary of the invention

0017The invention is set out in the claims. It provides a method for receiving in a set top box receiver connected to an IP multicast network the multimedia services of at least one offer among many offers being delivered in form of a bundle of transport streams multicast on the IP multicast network and a set top box receiver as described in the appended claims.

Brief description of the figures

0018The invention will now be described in greater detail with reference to the accompanying drawings, in which <ul id="ul0001" list-style="none"><li><figref idref="f0001">Fig. 1</figref> shows a network system for broadcasting a DVB compliant bundle according to prior art ;</li><li><figref idref="f0001">Fig. 2</figref> shows a network system for IP multicasting services according to prior art ;</li><li><figref idref="f0002">Fig. 3</figref> shows an example of a network system as used in the invention ;</li><li><figref idref="f0003">Fig. 4A, 4B and 4C</figref> contains syntax diagrams for describing entity relation ;</li><li><figref idref="f0003">Fig. 5</figref> contains a data model according to the invention ;</li><li><figref idref="f0004">Fig. 6</figref> schematically illustrates an example for multicasting transport streams according to the invention ;</li><li><figref idref="f0005">Fig. 7</figref> schematically illustrates an example for offer and stream information according to the invention ;</li><li><figref idref="f0006">Fig. 8</figref> contains a flowchart explaining an example of processing discovery information at a STB according to the invention ;</li><li><figref idref="f0007">Fig. 9</figref> contains a flowchart explaining an example of obtaining a transport stream in a STB according to the invention.</li></ul>

Description of the preferred embodiments

<i>General overview</i>

0019Referring to <figref idref="f0002">Fig. 3</figref>, a Multimedia Service Operator (MSO) 300 selects multimedia services broadcast over satellite, terrestrial and cable. The selection shown in <figref idref="f0002">Fig. 3</figref> represents an example, and it may be varied in any combination of the suggested or any other known broadcast means. The multimedia services are delivered in digital television transport streams broadcast according to a regional standard such as for example the DVB broadcast standard. At this stage the transport streams are in MPEG-2 standard format. The MSO provides the MPEG-2 transport streams to an IP delivery network operator, such as for example an Internet Service Provider (ISP) 301. The transport streams are IP encapsulated by the ISP 301 and multicast on an IP broadband network 302. The network 302 may for example be the internet or a proprietary IP network. Subscribers each have a STB 303 which is connected to the IP broadband network to receive IP data packets from the ISP 302.

0020There may be additional MSOs, e.g., an MSO 304, providing transport streams to the ISP 302.

0021Alternatively, it would be possible to IP encapsulate the transport stream at the level of the MSOs instead of the ISP, and to deliver the IP encapsulated transport stream to the ISP before multicast.

0022The MSOs generate discovery information needed at the receiver side, i.e., at the STB 303 side to be able to locate the different transport streams. More precisely the discovery information is required by the STB to localise an IP multicast transport stream, i.e., to know at which IP address and port the corresponding IP packets may be received. The discovery information is inserted into one or many textual files, e.g. into the well known XML textual file format, and IP multicast on the IP broadband network 302 for the STB 303. Typically the discovery information is cyclically multicast.

0023The STB 303 receives the XML textual files, extracts the discovery information and uses the discovery information to select a transport stream and to determine the localisation at which the transport stream is IP multicast. After receiving IP packets from the localisation, the MPEG-2 transport stream is decapsulated out of the IP packets. Further information necessary to discover actual services available over the received transport stream or indeed other transport streams, is afterwards acquired from the transport stream itself through classical use of service information as defined in the regional standard used for broadcasting the transport streams, e.g. the well known DVB-SI standard.

<i>Data model for discovery information</i>

0024<figref idref="f0003">Fig. 4A, 4B and 4C</figref> each represent an entity relation diagrammatic syntax that will be used to describe a data model for the discovery information.

0025<figref idref="f0003">Fig. 4A</figref> represents entities E1 and E2, where one entity E1 is in relation to one or many entities E2.

0026<figref idref="f0003">Fig. 4B</figref> represents a case in which one entity E1 is in relation to zero, one or many entities E2.

0027<figref idref="f0003">Fig. 4C</figref> represents a case in which one entity E1 inherits from one entity E2.

0028Referring to <figref idref="f0003">Fig. 5</figref>, a data model for the discovery information generated by the MSO, i.e. MSO discovery information 500 is presented. Information in box 500 may comprise information about zero, one or a plurality of MSO offers 501. As an example, in the case illustrated in <figref idref="f0002">Fig. 3</figref>, two MSOs 300 and 304 contribute to the information about their offers to the MSO discovery information.

0029Referring again to <figref idref="f0003">Fig. 5</figref>, the MSO offer 501 may correspond to one or many sources of discovery information 502. The nature of the discovery information 502 is described as a specialisation in Stream Discovery Information 503, that corresponds to information about transport streams available through IP multicast. The Stream Discovery Information 503 corresponds to one or many Stream localisations 504.

0030It is understood that the discovery information 502 may correspond also to other types of information than Stream Discovery Information 503. This may be the case if other data than transport streams are to be made available to the STB. One example of other data is a discovery information about a service that is being multicast, i.e., the discovery information comprises a name, a proprietary IP address and a port number for that service. Another example may be discovery information related to a Video On Demand service.

<i>IP multicast system for D VB transport streams</i>

0031Referring to <figref idref="f0004">Fig. 6</figref>, a schematic representation of a system for bringing DVB transport streams to the STB of a subscriber using an IP broadcast network is shown.

0032In this example, two offers (Offer 1 and Offer 2) are provided. The offers may be provided through one or more MSOs (not shown).

0033The offers 1 and 2 respectively cover transport streams TS_1,1 - TS_1,4 and TS_2,1 - TS_2,3 available in MPEG-2 format. IP encapsulation in box 600 is used to encapsulate the transport streams, that are subsequently IP multicast at stream localisations respectively referenced by LN_1,1 - LN_1,4 and LN_2,1 - LN_2,3, by an ISP 601.

<i>Example of discovery information</i>

0034Referring to <figref idref="f0005">Fig. 7</figref>, a schematic example in which discovery information is obtained and multicast for the system shown in <figref idref="f0004">Fig. 6</figref>, is given.

0035A first table 701 of offer information is created that indicates for each offer 1 and 2, a service provider offer localisation respectively LN_0,1 and LN_0,2 at which it is intended to multicast stream information.

0036A second table 702 and a third table 703 of stream information are created for respectively offer 1 and 2. Each table contains a list of transport streams and corresponding stream localisations.

0037The stream information table 702 contains the list of transport streams TS_1,1 -TS_1,4 from offer 1 and the corresponding stream localisations LN_1,1 - LN_1,4.

0038The stream information table 703 contains the list of transport streams TS_2,1 - TS_2,3 from offer 2 and the corresponding stream localisations LN_2,1 - LN_2,3.

0039The tables 701 - 703 are inserted into XML textual files which are in turn prepared to be transmitted over the IP broadband network (not shown).

0040The table 701 is cyclically multicast at a predetermined offer localisation LN_0,0 which is known by the STB. Hence the STB will know from where to obtain the offer information, which is required to obtain a transport stream.

0041The tables 702 and 703 are cyclically multicast respectively at the service provider offer localisations indicated in the table 701 of offer information, i.e., at the service provider offer localisations LN_0,1 and LN_0,2.

<i>Stream discovery information</i>

0042Stream discovery information may comprise information about one or a plurality of Transport Streams (TS).

0043For each TS the following fields may be indicated: <ul id="ul0002" list-style="dash"><li>an original network identification (Id),</li><li>a TS Id, and</li><li>a localisation.</li></ul>

0044The original network Id is a parameter that identifies a network used to initially provide the TS, before the TS is converted for delivery over the IP multicast delivery network.

0045The TS Id is a parameter that identifies a Transport Stream.

0046Both the original network Id and the TS Id are parameters used for example in the local DVB standard, as part of DVB Service Information.

0047A combination of the original network Id and the TS Id as presented in this example allows each TS to be uniquely identified in the IP multicast network. Hence, a service transported in a TS and having a service Id, may be uniquely referenced through a path "original network Id/TS Id/service Id".

0048The localisation comprises information that allows to localise a TS in the IP multicast network. The localisation comprises an IP multicast address and a port number for the TS.

0049In a preferred embodiment of the present example, the Stream Discovery Information may comprise an Identifier for the MSO that provides the Transport Stream(s) and a Version number that indicates a version number of the Stream Discovery Information. The version number may be incremented every time a change in the Stream Discovery Information is made.

<i>Use of discovery information in the STB</i>

0050It is understood that the STB is basically compliant to a regional standard, for example DVB compliant for the processing of MPEG-2 transport streams, i.e., it may process DVB transport streams and the corresponding DVB SI service information. This is well known in the art and will not be described here in any more detail.

0051One difference of the inventive STB as compared to a standard DVB compliant STB, is that it must be enabled to obtain the transport stream from a stream localisation in the IP broadband network, the transport stream being multicast at the stream localisation.

0052Hence, any request from the STB which aims at accessing a service located in a determined transport stream, as determined through relevant DVB service information, will make use of discovery information gathered from multicast offer and stream information.

0053When requesting a transport stream, the receiver uses a same transport stream identification as in DVB-SI. However, instead of tuning to a frequency read from a table and corresponding to the frequency at which the transport stream may be received, as is the case in DVB bundles, the tuner looks up a table of multicast localisations and reads the IP address and port pair (stream localisation) from which the transport stream may be obtained.

0054This table is compiled from multicast offer and stream information, and stored into the STB.

0055All further processing of the transport stream in itself and of DVB service information is done according to known methods well described in prior art. DVB service information contained in the transport streams may for example be used to build an Electronic Program Guide.

0056An example of processing offer and stream information will now be described together with <figref idref="f0006">Fig. 8</figref>. The example is based on the offers 1 and 2 described in relation to <figref idref="f0004">Figs. 6</figref> and <figref idref="f0005">7</figref>.

0057In box 800, the STB obtains at the predetermined offer localisation LN_0,0 the table 701 of offer information. The STB processes the offer information to extract for each offer, i.e., offer 1 and 2, the service provider offer localisations LN_0,1 and LN_0,2 at which stream information may be obtained.

0058The stream information is obtained in box 801 from the service provider offer localisations, and a table 802 listing for each offer, the stream localisation at which a transport stream is multicast by the ISP, is compiled and stored into the STB.

0059The table 802 is used by the STB to identify at which stream localisation a stream may be obtained. This is illustrated in <figref idref="f0007">Fig. 9</figref>. Following a request 900 for a transport stream TS_X,Y, e.g., a request generated by an application running in the STB, the table 802 (known from <figref idref="f0006">Fig. 8</figref>) is looked up in box 901, and the stream localisation LN_X,Y retrieved. In a next step 902 the multicast transport stream TS_X,Y is obtained from stream localisation LN_X,Y, in form of IP packets 903. The MPEG-2 packets of the transport stream are extracted through IP decapsulation in 904. The MPEG-2 transport stream is obtained for further processing by the MPEG-2 part of the STB in 906.

0060Having described preferred embodiments of the invention with reference to the accompanying drawings, it is to be understood that the invention is not limited to these precise embodiments and that various changes and modifications could be effected therein by a person skilled in the art without departing from the scope of the invention as defined in the appended claims.