WO2001056272A1 - Messaging protocol for demand-cast system and bandwidth management - Google Patents
Messaging protocol for demand-cast system and bandwidth management Download PDFInfo
- Publication number
- WO2001056272A1 WO2001056272A1 PCT/US2001/002452 US0102452W WO0156272A1 WO 2001056272 A1 WO2001056272 A1 WO 2001056272A1 US 0102452 W US0102452 W US 0102452W WO 0156272 A1 WO0156272 A1 WO 0156272A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- stream
- demand
- cast
- ipg
- stt
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/65—Transmission of management data between client and server
- H04N21/658—Transmission by the client directed to the server
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/235—Processing of additional data, e.g. scrambling of additional data or processing content descriptors
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
- H04N21/262—Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists
- H04N21/26208—Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists the scheduling operation being performed under constraints
- H04N21/26216—Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists the scheduling operation being performed under constraints involving the channel capacity, e.g. network bandwidth
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
- H04N21/262—Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists
- H04N21/26283—Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists for associating distribution time parameters to content, e.g. to generate electronic program guide data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/41—Structure of client; Structure of client peripherals
- H04N21/426—Internal components of the client ; Characteristics thereof
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/435—Processing of additional data, e.g. decrypting of additional data, reconstructing software from modules extracted from the transport stream
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/64—Addressing
- H04N21/6405—Multicasting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/64—Addressing
- H04N21/6408—Unicasting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
- H04N21/83—Generation or processing of protective or descriptive data associated with content; Content structuring
- H04N21/84—Generation or processing of descriptive data, e.g. content descriptors
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N7/00—Television systems
- H04N7/16—Analogue secrecy systems; Analogue subscription systems
- H04N7/173—Analogue secrecy systems; Analogue subscription systems with two-way working, e.g. subscriber sending a programme selection signal
- H04N7/17309—Transmission or handling of upstream communications
- H04N7/17336—Handling of requests in head-ends
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/47—End-user applications
Definitions
- the invention relates to communications systems in general. More specifically, the invention relates to video communications systems and interactive program guides for video programming.
- the use of compression techniques to reduce the amount of data to be transmitted may increase the speed of transmitting program guide information.
- the data to be transmitted is compressed so that the available transmission bandwidth is used more efficiently.
- MPEG Moving Pictures Experts Group
- the first, known as MPEG-1 refers to ISO/TEC standards 11172 and is incorporated herein by reference.
- MPEG-2 refers to ISO/IEC standards 13818 and is also incorporated herein by reference.
- a compressed digital video system is described in the Advanced Television Systems Committee (ATSC) digital television standard document A/53, and is incorporated herein by reference.
- ATSC Advanced Television Systems Committee
- the above-referenced standards describe data processing and manipulation techniques that are well suited to the compression and delivery of video, audio and other information using fixed or variable rate digital communications systems.
- the above-referenced standards, and other "MPEG-like" standards and techniques compress, illustratively, video information using infra-frame coding techniques (such as run-length coding, Huffman coding and the like) and inter-frame coding techniques (such as forward and backward predictive coding, motion compensation and the like).
- infra-frame coding techniques such as run-length coding, Huffman coding and the like
- inter-frame coding techniques such as forward and backward predictive coding, motion compensation and the like.
- MPEG and MPEG-like video processing systems are characterized by prediction-based compression encoding of video frames with or without infra- and/or inter-frame motion compensation encoding.
- the MPEG-1 and MPEG-2 standards have, in some instances, very strict elementary stream and fransport stream formats, causing usage of extra bandwidth for certain applications. For example, if a number of interactive program guide (IPG) pages were created as video sequences, only limited number of pages could be encoded into a transport stream(s) at a specified bandwidth.
- IPG interactive program guide
- the present invention provides messaging protocols for use between components of an interactive program guide (IPG) delivery system.
- the protocol provides a way to more efficiently utilize the finite bandwidth available for distribution of IPG video sequences.
- One embodiment ofthe present invention comprises messaging protocols for communications between a session manager(SM), a fransport stream generator (TSG), and a set top terminal (STT).
- the protocol for communication from the TSG to the STT specifies content for a demand-cast index table that may be transmitted within a private section of a MPEG fransport stream. This content includes a list of available demand-cast streams.
- the protocol for communication from the STT to the SM includes acquisition, release, and request messages.
- the protocol for communication from the SM to the TSG includes stream release, stream request, and reset messages, and the protocol for communication from the TSG to the SM includes acknowledgements of those messages.
- FIG. 1 depicts an illustrative communications network 100 for distributing video sequences to a plurality of terminals in accordance with an embodiment ofthe present invention.
- FIGS 2-6 depicts various methods and topologies for demand-casting interactive program guide (IPG) pages in accordance with embodiments ofthe present invention.
- IPG interactive program guide
- FIG. 2A is a flow chart showing a first push method 200 for demand- casting interactive program guide (IPG) pages in accordance with an embodiment ofthe present invention.
- IPG interactive program guide
- Figure 2B depicts a first push topology 250 for demand-casting IPG pages in accordance with an embodiment of the present invention.
- Figure 3 A is a flow chart showing a second push method 300 for demand- casting IPG pages in accordance with an embodiment ofthe present invention.
- Figure 3B depicts a second push topology 350 for demand-casting IPG pages in accordance with an embodiment ofthe present invention.
- Figure 4A is a flow chart showing a first pull method 400 for demand- casting IPG pages in accordance with an embodiment ofthe present invention.
- Figure 4B depicts a first pull topology 450 for demand-casting IP G pages in accordance with an embodiment ofthe present invention.
- Figure 5A is a flow chart showing a second pull method 500 for demand- casting IPG pages in accordance with an embodiment ofthe present invention.
- Figure 5B depicts a second pull topology 550 for demand-casting IPG pages in accordance with an embodiment ofthe present invention.
- Figure 6A is a flow chart showing a third pull method 600 for demand- casting of IPG pages in accordance with an embodiment ofthe present invention.
- Figure 6B depicts a third pull topology 650 for demand-casting of IPG pages in accordance with an embodiment ofthe present invention.
- Figure 6C is a flow chart showing a method 660 of terminating (or continuing) demand-casts in accordance with the third pull method 600.
- Figure 7 depicts a two-way system 700 for efficient delivery of demand- cast video sequences in accordance with an embodiment ofthe present invention.
- Figure 8 depicts an example of a set of JJPG pages for constant broadcast and other IPG pages for demand-cast in accordance with a preferred embodiment of the present invention.
- Figure 9 depicts an example of one frame taken from a video sequence that can be encoded using the present invention.
- Figure 10 depicts a first implementational architecture 1000 for managing delivery of video sequences of an interactive program guide in accordance with an embodiment ofthe present invention.
- Figure 11 depicts a second implementational architecture 1100 for managing delivery of video sequences of an interactive program guide in accordance with an embodiment ofthe present invention.
- Figure 12 depicts a third implementational architecture 1200 for managing delivery of video sequences of an interactive program guide in accordance with an embodiment ofthe present invention.
- Figure 13 depicts a fourth implementational architecture 1300 for managing delivery of video sequences of an interactive program guide in accordance with an embodiment of the present invention.
- Figure 14 depicts an embodiment for the content ofthe demand-cast index table.
- Figure 15 depicts one embodiment for the contents ofthe messages sent from the terminal 706 to the SM 702.
- Figure 16 depicts one embodiment for the contents ofthe messages sent from the SM 702 to the TSG 704.
- Figure 17 depicts one embodiment for the contents ofthe acknowledgement messages sent by the TSG 704 back to the SM 702.
- Figure 18 depicts an example showing status of active demand-cast streams in an IPG multiplex.
- Figure 19 illustrates the various scenarios for activation of a demand-cast stream.
- Figure 20 illustrates an overall process by which a released stream may be converted to a passive stream.
- FIG. 1 depicts an illustrative communications network 100 for distributing video sequences to a plurality of terminals in accordance with an embodiment ofthe present invention.
- the illustrative network 100 comprises a cable distribution network, but other types of distribution networks may also be used within the spirit and scope ofthe present invention.
- the illustrative network 100 includes one or more head-ends 102, one or more centers for local neighborhood equipment 104, a plurality of disfribution nodes 106, and a plurality of subscriber stations 108.
- the local neighborhood equipment (LNE) 104 may be located, for example, at remote hubs of a cable distribution network.
- the end- user terminals 108 may comprise, for example, interactive set-top terminals (STT) or other devices with similar interactive functionalities.
- the demand-cast term is used to refer to the process of managing and delivering content to one or more users depending on user demand for the content.
- Figures 2-6 depicts various methods and topologies for demand- casting interactive program guide (IPG) pages. The various methods/topologies are given for purposes of edification and are not meant to limit the scope ofthe present invention.
- Figure 2A is a flow chart showing a first push method 200 for demand- casting interactive program guide (IPG) pages in accordance with an embodiment ofthe present invention. As described below, the method 200 includes four steps.
- IPG interactive program guide
- a first set of IPG pages to be broadcast are predetermined.
- the first set of IPG pages may comprise video sequences, for example, for a current time period. For instance, if the current time is 1:07 pm, then the current time period may include programming from 1 :00 pm to 2:30 pm, assuming a 90 minute time period.
- a second set of IPG pages to be broadcast are predetermined.
- the second set of IPG pages may comprise video sequences, for example, for a prime time period.
- a prime time period is a time period during which a large number of viewers typically watch TV programming.
- the prime time period may include programming from 6:00 pm to 9:00 pm.
- bandwidth to broadcast the first and second sets of IPG pages is allocated in the distribution system for that purpose.
- a bandwidth manager (BWM) within a head-end 102 and/or local neighborhood equipment 104 allocates within the in-band network the necessary bandwidth to broadcast the first and second sets of IPG pages to the set-top terminals (STT) 108. If the first and second sets overlap, then only the non-redundant video sequences need to be broadcast and so only enough bandwidth to broadcast the non- redundant video sequences needs to be allocated. Such a situation may happen, for example, when the current time period is within prime time.
- the IPG pages ofthe first and second sets are broadcast to set-top terminals (STT) 108 within the broadcast range.
- the broadcast range may comprise all terminals 108 downstream from the head-end 102 or local neighborhood equipment 104. Only the non-redundant content needs to be broadcast. The broadcast is performed within the allocated in-band bandwidth.
- FIG. 2B depicts a first push topology 250 for demand-casting IPG pages in accordance with an embodiment ofthe present invention.
- the topology 250 relates to the push method 200 of Fig. 2A.
- the IPG pages are transmitted from the head-end (HE) 102 or local neighborhood equipment (LNE) 104 downstream within the illustrative communications network 100.
- the broadcast is pushed from the HE 102 or LNE 104 to the distribution nodes 106 and finally to the multitude of set-top terminals 108.
- HE head-end
- LNE local neighborhood equipment
- Figure 3 A is a flow chart showing a second push method 300 for demand- casting IPG pages in accordance with an embodiment ofthe present invention. As described below, the method 300 includes three steps.
- an IPG page is selected to be narrowcast to a group 352 of terminals 108.
- the group of terminals may be a group comprising a high concenfration of users with a particular ethnicity or special interest, and the IPG page selected may comprise programming targeted to that ethnic group or special interest group.
- the group of terminals may comprise terminals 108 in a school campus or business, and the IPG page selected may comprise class instruction or other targeted material.
- the group 352 may include terminals 108 in one geographic area or terminals 108 dispersed among different geographic areas but linked, for example, via a network group address.
- bandwidth to narrowcast the selected IPG pages is allocated in the distribution system for that purpose. For example, as described below in more detail, a bandwidth manager (BWM) within a head-end 102 and/or local neighborhood equipment 104 allocates within the in-band network the necessary bandwidth to narrowcast the selected IPG page to the group 352 of terminals 108. If the requested IPG page is already being broadcast per Figs. 2A and 2B, then no additional bandwidth for a narrowcast need be allocated.
- BWM bandwidth manager
- the selected IPG page is narrowcast to the group of terminals 108.
- the narrowcast need only be received by terminals 108 within the group 352 and does not need to be received by other STTs 108.
- the narrowcast is sent downstream from the head-end 102 or local neighborhood equipment 104 to the group 352 of terminals 108.
- the narrowcast is performed within the allocated in-band bandwidth. If the requested IPG page is already being broadcast per Figs. 2A and 2B, then the narrowcast need not be performed.
- FIG. 3B depicts a second push topology 350 for demand-casting IPG pages in accordance with an embodiment ofthe present invention.
- the topology 350 relates to the push method 300 of Fig. 3A.
- the TPG page is transmitted from the head-end (HE) 102 or local neighborhood equipment (LNE) 104 downstream within the illustrative communications network 100.
- the narrowcast is pushed from the HE 102 or LNE 104 to one or more distribution nodes 106 and finally to the terminals 108 within the group 352.
- Figure 4A is a flow chart showing a first pull method 400 for demand- casting IPG pages in accordance with an embodiment ofthe present invention. As described below, the method 400 includes three steps.
- a request for an IPG page is received from a STT 108.
- the request is transmitted upstream from the STT 108 to the HE 102 or LNE 104 by way ofthe communications network 100.
- the upstream transmission may be done via an out- of-band network.
- the upstream transmission may be done via an in-band network.
- Such a request may comprise, for example, a look ahead request where a user wishes to view programming for a time period ahead ofthe current time period.
- the STT 108 may first check to see whether or not the requested IPG page is already being broadcast before transmitting the request upstream.
- bandwidth to pointcast the requested IPG page is allocated in the distribution system for that purpose. For example, as described in more detail below, a bandwidth manager (BWM) within a head-end 102 and/or local neighborhood equipment 104 may allocate within the in-band network the necessary bandwidth to pointcast the requested IPG page to the requesting STT 108. Such allocation is performed if sufficient system resources are available to establish such a session. Moreover, if the requested IPG page is already being broadcast per Figs. 2A and 2B, then no additional bandwidth for a pointcast need be allocated. -n a third step 406, the requested IPG page is pointcast to the requesting set-top terminal (STT) 108.
- STT set-top terminal
- the pointcast need only be received by the requesting STT 108 and does not need to be received by other STTs 108.
- the pointcast is sent downstream from the head-end 102 or local neighborhood equipment 104 to the requesting STT 108.
- the pointcast is performed within the allocated in-band bandwidth. If the requested IPG page is already being broadcast per Figs. 2A and 2B, then the pointcast need not be performed.
- Figure 4B depicts a first pull topology 450 for demand-casting IPG pages in accordance with an embodiment ofthe present invention.
- the topology 450 relates to the pull method 400 of Fig. 4A.
- the request is fransmitted upstream from the requesting STT 108 to the HE 102 or LNE 104 via illustrative communications network 100.
- the requested IPG page is pointcast downstream from the HE 102 or LNE 104 to the requesting STT 108 via the network 100.
- Figure 5 A is a flow chart showing a second pull method 500 for demand- casting IPG pages in accordance with an embodiment ofthe present invention. As described below, the method 500 includes three steps.
- a request for an IPG page is received from a requesting STT 552.
- the request is fransmitted upstream from the requesting STT 552 to the HE 102 or LNE 104 by way ofthe communications network 100.
- the upstream transmission may be done via an out-of-band network.
- the upstream transmission may be done via an in-band network.
- Such a request may comprise, for example, a look ahead request where a user wishes to view available special interest programming for a time period ahead ofthe current time period.
- the requesting STT 552 may first check to see whether or not the requested IPG page is already being broadcast before transmitting the request upstream.
- bandwidth to narrowcast the requested IPG page is allocated in the distribution system for that purpose.
- a bandwidth manager (BWM) within a head-end 102 and/or local neighborhood equipment 104 may allocate within the in-band network the necessary bandwidth to narrowcast the requested IPG page to a group 554 of terminals which includes the requesting STT 552. Such allocation is performed if sufficient system resources are available to establish such a session. If the requested IPG page is already being broadcast per Figs. 2A and 2B, then no additional bandwidth for a pointcast need be allocated.
- the group 554 may include terminals 108 in one geographic area or terminals 108 dispersed among different geographic areas but linked, for example, via a network group address.
- the requested IPG page is narrowcast to the group 554 of terminals 108.
- the narrowcast need only be received by terminals 108 within the group 554 and does not need to be received by other STTs 108.
- the narrowcast is sent downstream from the head-end 102 or local neighborhood equipment 104 to the group 554 of terminals 108.
- the narrowcast is performed within the allocated in-band bandwidth. If the requested IPG page is already being broadcast per Figs. 2A and 2B, then the narrowcast need not be performed.
- Figure 5B depicts a second pull topology 550 for demand-casting IPG pages in accordance with an embodiment ofthe present invention.
- the topology 550 relates to the pull method 500 of Fig. 5 A.
- the request is transmitted upsfream from the requesting STT 552 to the HE 102 or LNE 104 via illustrative communications network 100.
- the requested IPG page is narrowcast downstream from the HE 102 or LNE 104 to the group 554 which includes the requesting STT 108 via the network 100.
- Figure 6A is a flow chart showing a third pull method 600 for demand- casting of IPG pages in accordance with an embodiment ofthe present invention. As described below, the method 600 includes five steps.
- a request for an IPG page is received from a first STT 652.
- the request is transmitted upsfream from the first STT 652 to the HE 102 or LNE 104 by way ofthe communications network 100.
- the upsfream transmission may be done via an out-of-band network.
- the upstream transmission may be done via an in-band network.
- Such a request may comprise, for example, a look ahead request where a user wishes to view programming for a time period ahead ofthe current time period.
- the first STT 652 may first check to see whether or not the requested IPG page is already being broadcast before transmitting the request upsfream.
- a stream 656 assigned to pointcast the requested IPG page may be allocated in the distribution system for that purpose. Such allocation is performed if sufficient system resources are available to establish such a session. For example, as described below in more detail, a bandwidth manager (BW ) within a headend 102 and/or local neighborhood equipment 104 may determine that sufficient resources are available to assign the stream 656 to pointcast the requested IPG page to the first STT 652. The stream assignment may be made, for example, by assigning a particular value to the program identifier (PID) for the stream 656. If the requested IPG page is already being broadcast per Figs. 2A and 2B, then the stream assignment need not be made.
- PID program identifier
- the requested IPG page is pointcast to the first STT 652 via the assigned stream 656. This may be done by transmitting packets that are identified by the particular PID value and contain the video sequence ofthe requested IPG page.
- the pointcast need only be received by the first STT 652 and does not need to be received by other STTs 108.
- the pointcast is sent downstream from the head-end 102 or local neighborhood equipment 104 to the first STT 652. If the requested IPG page is already being broadcast per Figs. 2A and 2B, then the pointcast need not be performed.
- a request for an IPG page is received from a second
- this second request is transmitted upsfream from the second STT 654 to the HE 102 or LNE 104 by way ofthe communications network 100 via either an out-of-band network or via an in-band network.
- the second STT 654 may be either in the same geographic area as the first STT 652, or the second STT 654 may be in a different geographic area as the first STT 652.
- the identifier (e.g., PID value) for the stream 656 is transmitted from the HE 102 or LNE 104 to the second STT 654. This enables the next step 612 to occur without use of additional PIDs or additional network bandwidth.
- the second STT 654 receives the requested IPG page via the same stream 656 as that which delivers the IPG page to the first STT 652. This may be done, for example, by setting the second STT 654 to decode and present packets that are identified by the particular PID value for the stream 656. Such packets are the ones which contain the video sequence ofthe requested IPG page. In this manner, "sharing" ofthe stream 656 occurs, changing the previously "single” pointcast to a "double" pointcast.
- additional terminals 108 may "share" the pointcast by requesting the same IPG page and receiving it via the same stream 656. In this way, any number of terminals 108 may share the pointcast. This results in more efficient use of limited bandwidth.
- FIG. 6B depicts a third pull topology 650 for demand-casting of IPG pages in accordance with an embodiment ofthe present invention.
- the topology 650 relates to the pointcast "sharing" method 600 of Fig. 6A.
- a request is fransmitted upsfream from the first STT 652 to the HE 102 or LNE 104 via illustrative communications network 100.
- the requested IPG page is pointcast by way of a stream 656 from the HE 102 or LNE 104 to the first STT 652.
- a second request for the same IPG page is transmitted upstream from the second STT 654 to the HE 102 or LNE 104 via the network 100.
- the identifier for the stream 656 is transmitted from the HE 102 or LNE 104 to the second STT 654.
- the second STT 654 uses the identifier to receive the IPG page from that same stream 656.
- Figure 6C is a flow chart showing a method 660 of terminating (or continuing) demand-casts in accordance with the third pull method 600. As described below, the method 660 includes five steps.
- a first step 662 an STT finishes viewing a stream which transmits an
- the STT may be either the first STT 652 or the second STT 654.
- the STT may be any of multiple terminals which are sharing the stream, or the STT may be the last terminal to be viewing a stream which was previously shared.
- a second step 664 the HE 102 or LNE 104 is notified that the STT has finished viewing the stream. Such a notification occurs by the STT sending a communication upsfream to the HE 102 or LNE 104 by way of an out-of-band or in-band network.
- a fourth step 668 if one or more STTs are still viewing that stream, then transmission ofthe stream by the HE 102 or LNE 104 continues. Such transmission is typically performed by an in-band delivery system.
- a fifth step 670 if no more STTs are still viewing that stream, then the stream is "torn down" so that it is no longer transmitted and no longer takes up network bandwidth.
- the torn down stream is made available for reassignment to reuse the bandwidth to transmit a different pointcast, narrowcast, or broadcast.
- a demand-cast J-PG system is a two-way system requiring communication between STT users on the cable network and the head-end via a back-channel.
- Demand- cast pages are inserted in the fransport stream for temporary broadcast based on access demand generated by STT users on the cable network.
- the STT simply acquires the corresponding stream.
- the STT requests from the head-end that the corresponding stream be inserted in the IPG multiplex. The head-end replaces the least frequently accessed and not currently accessed stream in the IPG multiplex with the newly requested page.
- a STT When a STT no longer accesses a guide page, it informs the head-end that it has released it.
- the IPG STT application When accessing a demand-cast page, the IPG STT application also times-out following a certain delay of inactivity (i.e. 2 minutes) on the part ofthe user. In this case it also informs the head-end that it has released the page. Informing the head-end when demand-cast pages become released ensures that non-accessed demand-cast pages become available for substitution.
- the head-end refuses to insert a newly requested guide page resulting in a blockage.
- Constantly broadcast pages offer the lowest latency access, whereas demand-cast pages may be delayed if not yet in the transport stream.
- Frequently accessed pages such as those in the current time slot and near look-ahead time slots, and perhaps prime-time slots need to be broadcast constantly so as to remain accessible with the minimum of latency. Less frequently accessed far look-ahead pages can be demand-cast.
- FIG. 7 depicts a two-way system 700 for efficient delivery of demand- cast video sequences in accordance with an embodiment ofthe present invention.
- the system 700 includes a session manager (SM) 702 and a transport stream generator (TSG) 704.
- SM session manager
- TSG transport stream generator
- Both the SM 702 and the TSG 704 may be, for example, co-located at a distribution center.
- the distribution center may comprise, for example, a headend 102 in the illustrative distribution system 100.
- the SM 702 and the TSG 704 may be at different locations.
- the SM 702 may be at a headend 102
- the TSG 704 may be at local neighborhood equipment 104 in the illustrative distribution system 100.
- One terminal 706 and its links to the SM 702 and the TSG 704 are illustrated in Fig. 10.
- the terminal 706 receives in-band communications from the TSG 704 and sends out-of-band (OOB) communications to the SM 702.
- the communications to the SM 702 may comprise upstream in-band communications.
- the session manager (SM) 702 may comprise, in one embodiment, a computer system residing at a cable headend 102.
- the computer system may comprise, for example, a computer server running a version ofthe UNIX (or alternatively Windows) operating system.
- the computer system may receive out-of-band commmunications from the terminals 706 by way of a connection to the network controller.
- the connection may comprise an Ethernet connection and the network controller may comprise one from General Instruments (now part of Motorola) or another supplier.
- the computer system also communicates with and controls the transport stream generator 704 by way of a network connection such as an Ethernet connection.
- the SM 702 manages delivery ofthe IPG to terminals 706 on multiple cable nodes each served by a separate J-PG multiplexed transport stream generated at a TSG 704.
- the SM 702 also monitors demand-cast sfream usage by the terminals 706. It tracks IPG demand-cast streams that are acquired by at least one terminal 706 by maintaining a dynamic list of terminals 706 using each sfream. This is done for each IPG multiplexed transport sfream managed by the SM 702.
- the SM 702 also accepts messages from terminals 706 indicating that they have acquired, released, or requested demand-cast streams.
- a terminal 706 that has acquired a demand-cast stream is registered to the stream, and a terminal 706 that has released a demand-cast stream is removed from the registry for the stream.
- the SM 702 informs the corresponding TSG 704 once there is no logner any terminals 706 registered to a particular demand-cast stream. It also informs the TSG 704 when a terminal 706 requests a demand-cast stream.
- the SM 702 may time-out acquisition of a sfream by any terminal
- the time-out may be implemented by removing the particular terminal 706 from the registry for the stream.
- the transport stream generator (TSG) 704 may comprise, in one embodiment, a computer system residing at a cable headend 102.
- the computer system may comprise, for example, a computer server running a version ofthe Windows (or alternatively UNIX) operating system.
- the TSG 704 may be located separately from the SM 702, for example, at local neighborhood equipment 104.
- Each TSG 704 is coupled to a SM 702, for example, via an Ethernet network.
- the TSG 704 may generate one or more IPG multiplexed transport stream, each broadcast to a respective node in the distribution system.
- the IPG multiplexed transport sfream comprises a MPEG transport sfream.
- the TSG 704 may communicate with the terminals 706 by way of tables in the private section ofthe MPEG fransport stream. Such a table may include a list of available demand-cast streams, along with the address ofthe source TSG 704 and information to identify the particular IPG multiplexed fransport stream to which the table belongs.
- the TSG 704 manages each IPG multiplexed fransport sfream which it generates.
- the TSG 704 receives information from the SM 702 indicating whether each demand-cast stream being served is currently being acquired by any terminal 706 or not. In other words, the TSG 704 is informed by the SM 702 when there is no longer any terminals 706 acquiring a demand-cast sfream.
- the TSG 704 maintains a status for each variable demand-cast stream being served. The status is adjusted upon receipt by the TSG 704 of certain messages from the SM 702.
- the basic states for the status comprise an "acquired" state wliich denotes that the demand-cast sfream is in use by one or more terminals 706, and a "released” state which denotes that that the demand-cast stream is not in use by any terminal 706.
- the TSG 704 keeps serving "acquired" demand-cast streams by multiplexing them into appropriate transport sfreams and replaces "released" demand-cast streams with new demand-cast streams upon receipt of a request message from the SM 702.
- the TSG 704 also keeps track ofthe order in which the streams are released, so that the oldest released stream may be used as the preferred candidate for replacement.
- the terminal 706 comprises a set-top terminal (STT) for use by a service subscriber.
- the STT may comprise an embedded system which includes a tuner, a demultiplexer, and a decoder.
- the STT drives the subscriber's display unit or TV set, and it may be connected to the TSG 704 by way of a RF feed from a cable distribution network.
- the IPG content may be received from a particular IPG multiplexed fransport stream on a specific QAM carrier signal.
- the IPG multiplexed fransport sfream may comprise an ensemble of elementary MPEG video streams, each representing a portion ofthe guide.
- the terminal 706 includes IPG client software application which is resident at the terminal 706.
- the IPG client application is responsible for presenting the IPG to the subscriber.
- the IPG client application demultiplexes and decodes IPG pages requested by the user. If a requested page is already being received via the IPG multiplexed transport stream, then the IPG client application acquires the stream immediately and sends a message to the SM 702 that it has acquired the stream. If the requested page is not in the IPG multiplexed transport stream, then the IPG client application sends a request message to the SM 702. Subsequently, the IPG client application acquires the sfream once it is received.
- the IPG client application when a stream is no longer being acquired, the IPG client application sends a release message to the SM 702. In one embodiment, if there is no remote control or other activity by the user for a period of time (for example, a few minutes), then the IPG client application times-out the acquisition. The time-out may be accomplished, for example, by sending a release message to the SM 702 and acquiring a broadcast stream instead.
- the demand-cast system consists of three major subsystems: the set top terminal (STT); the session manager (SM); and the transport stream generator (TSG.) A description of each subsystem follows.
- the set top terminal is the end-user or cable service subscriber tuner/demultiplexer/decoder and embedded system.
- the STT used in initial pilot deployments is the General Instruments DCT-2000. It is connected to the cable operator RF feed. It drives the subscribers display unit or TV set.
- the IPG content is in the IPG transport sfream (or multiplex) located on a specific QAM carrier.
- the IPG multiplex contains an ensemble of elementary MPEG video streams each representing portions ofthe guide. Some of these streams are guide grid pages.
- the STT receives messages from the head-end via tables in the private section ofthe IPG fransport sfream (in-band messaging.) The STT sends messages to the head-end via the out-of-band return path.
- the IPG Application is the set top terminal resident program responsible for presenting the DJNA Interactive Program Guide to the subscriber.
- the IPG application demultiplexes and decodes IPG pages requested by the user. If a particular page is in the IPG transport sfream, the STT acquires the stream immediately and informs the SM that it has requested it. If the page is not in the multiplex, the STT also sends a message to the SM that it has requested it. Then it acquires the stream once it's in the multiplex. When the STT no longer is acquiring a guide stream, it informs the SM that it has released it.
- the STT is on a demand-cast stream for more than 2minutes without any remote control activity, it times-out. It acquires a broadcast stream instead and informs the SM that it has released the demand-cast stream.
- the session manager is a computer residing at the cable head-end.
- the SM is a SPARC Station running Solaris. It is connected via Ethernet to the server side ofthe General Instruments network controller (NC) and is the receiver for OB return path messages originating from STTs.
- NC General Instruments network controller
- the SM can handle STTs on multiple cable nodes each served by a separate IPG multiplex.
- the SM communicates and controls the TSGs via Ethernet.
- the TSGs generate the IPG transport sfreams.
- the SM manages one or multiple cable networks and monitors demand- cast stream usage. It tracks IPG demand-cast streams that are acquired by at least one STT maintaining a dynamic list of STTs that are using them. This is done for each multiplex managed by the SM.
- the SM accepts messages from STTs indicating that they have requested or released demand-cast streams. A STT that has acquired a demand-cast stream is registered to the stream and a STT that has released a demand-cast stream is removed from the streams registry.
- the SM informs the TSG once there are no longer any STTs on a particular demand-cast stream. It also informs the TSG when a STT requests a demand-cast stream.
- the SM times-out any STT from a demand-cast stream if the box has not released the sfream within a few minutes. It does this by removing it from the demand- cast stream's registry.
- the fransport sfream generator is a computer residing at the cable headend.
- the TSG is a PCI WinNT system. It is connected via Ethernet to the SM controlling it.
- the TSG produces one or more IPG fransport sfreams each broadcast to their respective nodes.
- the TSG communicates with the STTs by way of tables in the private section ofthe IPG fransport streams.
- the table contains the list of available demand-cast streams along with the IP address ofthe source TSG (its IP address) and the channel number ofthe IPG multiplex, (which multiplex it is in the TSG)
- the TSG manages the transport sfream for each IPG multiplex it generates. It receives information from the SM on each demand-cast stream indicating whether the stream is currently acquired by any STT or released by all STTs. The TSG is informed by the SM when there is no longer any STT on a demand-cast sfream. The TSG is informed by the SM when a STT requests a demand-cast stream. The TSG maintains status for all the demand-cast streams in each multiplex. It adjusts the status for each stream for which it receives a message from the SM. The basic status is 'acquired' for sfreams in use by one or more STTs or 'released' for streams that are not in use by any STT.
- the TSG keeps 'acquired' sfreams in its multiplexes and replaces 'released' streams with new demand-cast sfreams upon request. It also keeps frack of which are the few oldest 'released' stream. The best candidate for replacement is always the oldest 'released' sfream. If all the demand-cast streams in a multiplex are 'acquired' then a new stream can not be inserted and the TSG refuses the request.
- Figure 8 depicts an example of a set of IPG pages for constant broadcast and other IPG pages for variable demand-cast in accordance with a preferred embodiment ofthe present invention.
- 40 IPG pages are constantly broadcast and up to 30 IPG pages may be variably demand-cast.
- the constant broadcast includes 10 guide pages for the current timeslot and 30 guide pages for the next three hourly timeslots.
- the variably demand- cast pages may be any pages within the guide page matrix that are not currently being broadcast.
- the terminal will end its access ofthe guide page. This may occur because the user has instructed the terminal to view a different page. Alternatively, this may occur because of a time-out due to inactivity over a period of time (for example, 2 minutes). In any case, when the terminal is no longer accessing the guide page, then the terminal transmits a message to the head-end which indicates that the terminal has released the corresponding stream. Informing the head-end when varibly demand-cast pages become released ensures that non-accessed demand-cast pages become available for substitution as described above.
- One advantage ofthe preferred embodiment ofthe present invention is that, if a particular page is intensively accessed (such as a page listing a major sports event), then the system needs to insert the particular page only once into the transport stream. Once inserted, the page is readily accessible by multiple terminals without consuming additional bandwidth. Other systems would be more susceptible to blockage. Blockage would occur, for example, when a newly requested page cannot be inserted into the fransport stream because there is no available bandwidth within the fransport sfream.
- An J-PG delivery system in accordance with a preferred embodiment ofthe present invention is a two-way system which is capable of two-way communications between set top terminals on the cable network and the equipment in the cable head-end. For example, communications may be transmitted from the terminals to the head-end via a back-channel, and content may be fransmitted from the head-end to the terminals by insertion into a fransport stream.
- Figure 9 depicts an example of one frame taken from a video sequence of an J-PG page in accordance with the present invention.
- the J-PG page 900 of Figure 9 comprises a first 905 A, second 905B and third 905C time slot objects, a plurality of channel content objects 910-1 through 910-8, a pair of channel indicator icons 941 A, 941B, a video barker 920 (and associated audio barker), a cable system or provider logo 915, a program description region 950, a day ofthe week identification object 931, a time of day object 939, a next time slot icon 934, a temporal increment/decrement object 932, a "favorites” filter object 935, a "movies” filter object 936, a "kids” (i.e., juvenile) programming filter icon 937, a "sports” programming filter object 938 and a VOD programming icon 933.
- the day ofthe week object 931 and next time slot icon 934 may comprise independent objects (as depicted in Figure 9) or may be considered together as parts of a combined object.
- the channels are displayed in 8-channel groups having associated with them three hour time slots.
- 10 video PIDs to carry the present- time channel/time/title information
- one or more audio PUD to carry the audio barker
- one or more data PID (or other data transport method) to carry the program description data, overlay data and the like.
- 160 (10*24/1.5) video PIDS, along with one or more audio and, optionally, one or more data PIDs.
- the amount of time provided for in broadcast video PIDs for the given channel groups comprises the time depth ofthe program guide, while the number of channels available through the guide (compared to the number of channels in the system) provides the channel depth of the program guide.
- the channel depth is said to be 50%.
- the time depth is said to be 12 hours.
- the time depth is said to be +16/-4 hours.
- the video streams representing the IPG are carried in a single transport stream or multiple transport sfreams, within the form of a single or multi-programs as discussed previously in this invention.
- a user desiring to view the next 1.5 hour time interval e.g., 9:30 - 11:00
- may activate a "scroll right" object or move the joystick to the right when a program within program grid 902 occupies the final displayed time interval.
- Such activation results in the controller ofthe STT noting that a new time interval is desired.
- the video sfream corresponding to the new time interval is then decoded and displayed. If the corresponding video stream is within the same fransport stream (i.e., a new PID), then the stream is immediately decoded and presented.
- the related transport stream is extracted from the broadcast stream and the related video sfream is decoded and presented. If the corresponding transport sfream is within a different broadcast stream, then the related broadcast stream is tuned, the corresponding fransport stream is extracted, and the desired video stream is decoded and presented.
- a user interaction resulting in a prior time interval or a different set of channels results in the retrieval and presentation of a related video stream.
- a pointcast session for example, may be initiated as described above in relation to Figs. 4A and 4B.
- the STT sends a request to the head end via the back channel requesting a particular stream.
- the head end then processes the request, retrieves the related stream from the information server, incorporates the sfream within a transport stream as a video ' PID (preferably, the transport stream currently being tuned/selected by the STT) and informs the STT which PID should be received, and from which transport stream it should be demultiplexed.
- the STT retrieves the related video PID.
- the STT first demultiplexes the corresponding transport stream (possibly tuning a different QAM sfream within the forward channel).
- the STT indicates to the head end that it no longer needs the stream, whereupon the head end tears down the pointcast session. The viewer is then returned to the broadcast stream from which the pointcast session was launched.
- the method for "sharing" pointcasts may avoid the need to tear down the pointcast session if another STT is still utilizing the pointcast.
- the above described pointcast sharing technique more efficiently utilizes the network bandwidth allocated to pointcasts. Now consider the difference in latencies between push demand-casts and pull demand-casts. Access to IPG pages with low latency is a desirable feature in providing a program guide. A system which only pushes IPG pages would offer potentially the lowest latency access, whereas a system which only pulls pages would incur significant delays in accessing each page.
- frequently accessed IPG pages such as those in the current time slot and near look-ahead time slots, and perhaps prime-time slots would be push demand-cast constantly so as to remain accessible with low latency. Less frequently accessed far look-ahead pages would be pull demand-cast.
- the first through fourth (1000 through 1300) implementational architectures described below are illustrative implementational architectures which may be used to implement the present invention. They are not meant to limit the present invention to those specific embodiments.
- Figure 1000 depicts a first implementational architecture 1000 for managing delivery of video sequences of an interactive program guide in accordance with an embodiment ofthe present invention.
- the first implementational architecture 1000 includes a key manager 1002, a subscription/billing manager 1004, an IPG generator 1006, and a head-end 102.
- This first architecture 1000 provides for encryption ofthe IPG content.
- the head-end 102 is coupled to a multitude of STTs 108 by way of both an in-band network and an out-of-band (OOB) network.
- the head-end 102 includes various components which are coupled together and interact with each other.
- the head-end 102 illustrated includes an advertising/html content source 1008, an IPG content source 1009, a compositor 1010, an encoder 1012, a processor 1014, a multiplexor 1016, an encryptor 1018, an in-band delivery system 1020, a controller 1022, a session manager 1024, an access manager 1026, a bandwidth manager 1028, and out-of-band (OOB) equipment 1030.
- Fig. 7 encompasses the functionality of multiple components of Fig. 10, including the session manager 1024 and the bandwidth manager 1028. Also, note that the fransport stream generator 704 of Fig. 7 encompasses the functionality of multiple components of Fig. 10, including the processor 1014 and the mux 1016.
- FIG. 11 depicts a second implementational architecture 1100 for managing delivery of video sequences of an interactive program guide in accordance with an embodiment ofthe present invention.
- the second implementational architecture 1100 includes the components ofthe first implementational architecture 1000.
- the second implementational architecture 1100 includes local neighborhood equipment 104 and a video-on-demand (VOD) server 1102. This second architecture 1100 provides for encryption ofthe IPG content.
- VOD video-on-demand
- the LNE 104 is coupled to the HE 102 by way of an in-band network and an OOB messaging system.
- the LNE 104 is also coupled to a multitude of STTs 108 by way of a local in-band network.
- the LNE 104 includes various components which are coupled together and interact with each other.
- the type of components in the LNE 104 are typically a subset ofthe type of components in the HE 102.
- the LNE 104 illustrated includes a processor 1114, a multiplexor 1116, an encryptor 1118, a local delivery system 1120, a controller 1122, a session manager (SM) 1124, an access manager (AM) 1126, and a bandwidth manager (BWM) 1128.
- SM session manager
- AM access manager
- BWM bandwidth manager
- FIG. 12 depicts a third implementational architecture 1200 for managing delivery of video sequences of an interactive program guide in accordance with an embodiment ofthe present invention.
- the implementational architecture 1200 includes a local IPG center 1202, a headend 1204, a service center 1206, and a plurality of set-top terminals (STT) 1208.
- the system may be integrated with a video on-demand (VOD) system 1210 and a corresponding VOD application 1238 at the STT 1208.
- VOD video on-demand
- This third architecture 1200 does not provide for encryption ofthe IPG content.
- the local IPG center 1202 generates guide page user interface (Ul) screens and periodically sends the Ul screens to an IPG server 1212 at the headend 1204.
- MSO/third party IPG add-on content 1214 may be provided to the IPG server 1212 from MSO equipment within the headend 1204.
- the add-on content may include real-time advertisement video or HTML pages for electronic commerce.
- the IPG server 1212 composes (C), encodes (E), processes (P), multiplexes (M), and modulates (QAM) the IPG content (guide plus add-on content) and transmits it to a combiner 1216.
- the combiner 1216 combines the IPG content with broadcast TV, premium content (e.g., HBO), pay-per-view (PPV), and other content from a multiple service operator (MSO) content delivery system 1218.
- the combined content is then broadcast to the STTs 1208 via an in-band distribution network 1220.
- an IPG application 1222 at the STT 1208 processes the IPG sfream and provides the IPG via an application programming interface (API) 1224 to a "native" application 1226 running on the STT 1208.
- API application programming interface
- the native application 1226 decodes and presents the IPG to the viewer.
- the TV program guide for a current time period (1.5 hours) is broadcast to viewers.
- two weeks of lookahead TV programming may be delivered to viewers on demand via demand-cast.
- the STT 1208 Upon a view action of moving a cursor to a lookahead time interval, the STT 1208 sends a request via a backchannel to a session manager (SM) 1228 [for example, via an OOB channel to a reverse path demodulator (RPD), then to a network controller (NC), then to the SM 1228].
- RPD reverse path demodulator
- NC network controller
- the SM 1228 also interacts with a subscription/billing interface 1230 in the VOD system 1210 to coordinate access to VOD services from a link in the IPG user interface (Ul).
- the Ul also provides for access to premium content and pay-per-view purchasing by interacting through a two-way interface to a MSO customer management system (CMS) 1232 and digital access controller (DAC) 1234 in the service center 1206.
- CMS customer management system
- DAC digital access controller
- the implementational architecture 1200 also includes a bandwidth manager (BWM) 1236.
- BWM bandwidth manager
- the BWM 1236 provides techniques for more efficient utilization ofthe finite bandwidth available for distribution ofthe IPG.
- the session manager 702 of Fig. 7 encompasses the functionality of multiple components of Fig. 12, including the session manager 1228 and the bandwidth manager 1236.
- the fransport stream generator 704 of Fig. 7 encompasses the functionality of multiple components of Fig. 12, including the processor (P) and the multiplexer (M).
- Figure 13 depicts a fourth implementational architecture 1300 for managing delivery of video sequences of an interactive program guide in accordance with an embodiment ofthe present invention.
- the implementational architecture 1300 of Fig. 13 has many similarities to the implementational architecture 1200 of Fig. 12. This fourth architecture 1300 does not provide for encryption ofthe IPG content.
- the fourth implementational architecture 1300 differs from the third implementational architecture 1200 primarily in that some ofthe equipment is distributed from the headend 1204 to a plurality of hubs 1302 in the distribution system.
- the combiner 1216 is moved from the headend 1204 to each ofthe hubs 1302.
- the processor (P), multiplexer (M), and modulator (QAM) are moved from the headend 1204 to each ofthe hubs 1302.
- the functionality ofthe TSG 704 is transferred to the hubs 1302.
- a messaging protocol for communicating between the major components ofthe system 700.
- the messaging protocol is described in relation to Figs. 14-17. Although a specific messaging protocol is described below, the present invention is not meant to be limited to that specific protocol.
- the "source” fransport stream generator (TSG) 704 communicates to a terminal 706 via, for example, a one-way in-band channel.
- the communication may be, for example, in the form of a "demand-cast index table" within a private section ofthe IPG MPEG transport stream.
- Fig. 14 depicts an embodiment for the content ofthe demand-cast index table.
- the content may include: (a) a table version number (which increments when the table content changes); (b) a list of available demand-cast streams; (c) an internet protocol (IP) address for the source TSG; (d) a MUX channel number within the source TSG, and (e) a time of day and day of week.
- IP internet protocol
- the terminal 706 communicates with the session manager (SM) 702 via, for example, a one-way out-of-band return path.
- the return path may be implemented, for example, using a user datagram protocol/internet protocol (UDP/IP) service to connect the terminal 706 to a network controller (NC) at the SM 702.
- Fig. 15 depicts one embodiment for the contents ofthe messages sent from the terminal 706 to the SM 702.
- the message content as shown includes: (a) a demand-cast stream identification; (b) the terminal's identification; (c) the IP address ofthe source TSG; (d) the MUX channel number within the source TSG; and (e) the message information itself.
- the message information may indicate: (1) an acquisition ofthe demand-cast stream by the terminal 706; (2) a release ofthe demand-cast stream by the terminal 706; or (3) a request for the demand-cast stream by the terminal 706.
- the SM 702 communicates with the source TSG 704 via, for example, a two-way communications chamiel.
- the two-way communications channel may comprise, for example, a TCP/IP connection over an Ethernet network.
- Fig. 16 depicts one embodiment for the contents ofthe messages sent from the SM 702 to the TSG 704.
- the message content as shown includes: (a) the demand-cast stream identification; (b) the MUX channel number within the source TSG; and (c) a message/command from a set of messages/commands.
- the set of messages/commands include: (1) demand-cast stream released (no longer acquired by any terminal); (2) demand-cast sfream requested; and (3) a reset command.
- Messages from the SM 702 to the TSG 704 may be acknowledged by the TSG 704.
- Fig. 17 depicts one embodiment for the contents ofthe acknowledgement messages sent by the TSG 704 back to the SM 702.
- An acknowledgement message as shown includes: (a) the demand-cast stream ID; (b) the MUX channel number; (c) the TSG's address; and (d) the acknowledgement itself.
- the acknowledgement may convey acknowledgement of : (1) release ofthe demand-cast stream; (2) request for the demand- cast stream; or (3) reset ofthe TSG 704.
- the TSG 704 models bandwidth usage for each IGP multiplexed fransport stream that it is managing.
- Each demand-cast stream within each transport sfream may be either active or inactive. Active streams are currently being multiplexed into the transport stream. Inactive sfreams are not currently being multiplexed into the transport sfream.
- FIG. 18 depicts an example showing statuses of active demand-cast streams in an IPG multiplex within a TSG 704. For each demand-cast stream, TSG assigns status with respect to the sfreams intended multiplex.
- Demand-cast stream status in context ofthe TSG, are:
- 'acquired' demand-cast streams are in the multiplex and are used by at least one STT. They are referenced in the demand-cast index table in the private section ofthe IPG fransport stream. They are not candidates for removal.
- 'inactive' demand-cast streams are not in the IPG multiplex. They are not referenced in the demand-cast index table. They may be inserted in the multiplex. Note that the TSG may remove all the 'passive' demand-cast sfreams from their respective IPG multiplexes and replace them with null packets. It is however advantageous to leave 'passive' demand-cast sfreams in the multiplex because if a STT attempts to acquire it, latency will be minimized.
- the TSG receives messages from the SM. Messages received from the SM are:
- the "release demand-cast stream” message includes the maximum number of STTs that were registered to the demand-cast stream.
- the TSG removes an 'passive' demand-cast stream from its corresponding multiplex, thereby making it 'passive' and replaces it with the new requested demand-cast sfream.
- the TSG adds reference to the new 'active' demand-cast stream in the demand-cast index table.
- the TSG assigns the status 'active' to the newly inserted demand- cast stream.
- the TSG acknowledges SM for the "request demand-cast sfream" message by sending a "success" message back to the SM.
- the TSG forces the oldest 'released' demand-cast stream to 'inactive' status and then follows the steps described directly above.
- the TSG finds no 'passive' or 'released' demand- cast stream in the corresponding multiplex, it can not fulfill the request. It acknowledges the SM for the "request demand-cast stream" message by sending a "fail" message back to the SM.
- the TSG changes the status ofthe 'released' or 'passive' demand-cast sfream to 'acquired.' It acknowledges the SM for the "request demand- cast stream" message by sending a "success” message back to the SM.
- the TSG receives a "release demand-cast stream” message from the SM, then the TSG acknowledges the SM by sending a "success” message. If the demand-cast stream is currently 'acquired', then the TSG changes the status ofthe stream to 'released.'
- Removal of a 'released' demand-cast streams could be done, however, such removal would be disadvantageous. Initially, the reference to the 'released' demand-cast stream would have to be removed from the "demand-cast index table", then a few seconds later, the stream could be physically removed from the multiplex. This delay between removal from the table and from the multiplex is necessary to prevent a race condition where a STT is acquiring a demand-cast sfream while the TSG is in the process of removing it. Therefore, only 'passive' sfreams are removed in accordance with a preferred embodiment ofthe present invention.
- the ratio of 'passive' to 'released' demand-cast may be specified in the TSG configuration file. It may be maintained as a percentage (i.e. 10% of 'released' sfreams are converted to 'passive') or it can be maintained as an absolute number (i.e. so as to ensure that there are usually two or three 'inactive' demand-cast sfreams).
- Figure 20 illustrates an overall process by which a released sfream may be converted to a passive sfream.
- Methods for determining which released sfreams are converted to passive streams include: an aging method and a statistical method.
- the oldest few 'released' demand-cast sfreams are constantly converted to 'passive' status by a maintenance thread.
- the "release demand- cast stream" messages include statistical data regarding the demand-cast sfream. This data is the maximum number of STTs that were on a released sfream before it was released.
- the TSG converts those demand-cast sfreams that have had the least amount of users to 'passive' status.
- the STT When the STT launches the IP G application, it tunes to the QAM carrying the IPG fransport sfream. When the STT requests its first demand-cast stream it opens the J-PG channel with the SM. When the QAM is tuned, the STT acquires the demand-cast index table and sends an Init command to SM.
- the SM knows nothing about the IPG multiplex fed to its client STTs. Upon receiving a first "request demand-cast stream" message from a STT, it verifies that it is aware ofthe mux ID. Mux ID includes TSG IP address and mux channel within the TSG. It it is aware, then nothing happens. If it is not aware, the TSG opens a communication socket with the source TSG. The SM maintains a log where it registers all muxes that it controls. For each mux in the log, the TSG IP address and mux channel number is recorded.
- the TSG is configured through its own configuration file.
- Configuration includes the number of demand-cast streams that can be supported by each JPG mux.
- the absolute number of 'passive' streams or the ratio of 'passive' streams to 'released' streams is specified in the configuration file.
- the SM If the SM is down, upon reset, it looks-up TSG log file and sends a reset command to the TSG.
- TSG When TSG receives a "reset" command from the SM, it removes reference to all demand-cast streams in the demand-cast index table in the multiplex referenced by the mux J-D in the reset command. Then a few second later, the TSG removes all the demand-cast streams within the multiplex.
- the STT When the STT does not "see” the PID ofthe demand-cast stream it is acquiring in the demand-cast index table, it acquires a default IPG broadcast PID. If the STT does not see the demand-cast index table, the STT exits the IPG application.
- Each TSG can manage more than one IPG multiplex.
- IPG multiplex is referred to by the IPG address ofthe host TSG and the mux channel number on the TSG.
- Each IPG multiplex is referred to by the IPG address ofthe host TSG and the mux channel number on the TSG.
- STT messages regarding demand-cast streams include demand-cast stream ID, TSG IP address and the mux channel number on the TSG.
Abstract
Description
Claims
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU2001234559A AU2001234559A1 (en) | 2000-01-26 | 2001-01-24 | Messaging protocol for demand-cast system and bandwidth management |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17810000P | 2000-01-26 | 2000-01-26 | |
US60/178,100 | 2000-01-26 | ||
US09/524,854 US7127737B1 (en) | 2000-01-26 | 2000-03-14 | Bandwidth management techniques for delivery of interactive program guide |
US09/524,854 | 2000-03-14 | ||
US53922800A | 2000-03-30 | 2000-03-30 | |
US09/539,228 | 2000-03-30 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2001056272A1 true WO2001056272A1 (en) | 2001-08-02 |
WO2001056272A9 WO2001056272A9 (en) | 2002-10-24 |
Family
ID=27390918
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2001/002452 WO2001056272A1 (en) | 2000-01-26 | 2001-01-24 | Messaging protocol for demand-cast system and bandwidth management |
Country Status (2)
Country | Link |
---|---|
AU (1) | AU2001234559A1 (en) |
WO (1) | WO2001056272A1 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FR2838597A1 (en) * | 2002-04-11 | 2003-10-17 | Thomson Licensing Sa | Digital television receiver electronic programme guide remote loading having digital word header and video information blocks with further header information interspersed. |
GB2403046A (en) * | 2001-03-16 | 2004-12-22 | Nds Ltd | A method for literal data access |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5557724A (en) * | 1993-10-12 | 1996-09-17 | Intel Corporation | User interface, method, and apparatus selecting and playing channels having video, audio, and/or text streams |
US5801753A (en) * | 1995-08-11 | 1998-09-01 | General Instrument Corporation Of Delaware | Method and apparatus for providing an interactive guide to events available on an information network |
US5867207A (en) * | 1994-01-05 | 1999-02-02 | Thomson Consumer Electronics, Inc. | Program guide in a digital video system |
-
2001
- 2001-01-24 WO PCT/US2001/002452 patent/WO2001056272A1/en active Application Filing
- 2001-01-24 AU AU2001234559A patent/AU2001234559A1/en not_active Abandoned
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5557724A (en) * | 1993-10-12 | 1996-09-17 | Intel Corporation | User interface, method, and apparatus selecting and playing channels having video, audio, and/or text streams |
US5867207A (en) * | 1994-01-05 | 1999-02-02 | Thomson Consumer Electronics, Inc. | Program guide in a digital video system |
US5801753A (en) * | 1995-08-11 | 1998-09-01 | General Instrument Corporation Of Delaware | Method and apparatus for providing an interactive guide to events available on an information network |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2403046A (en) * | 2001-03-16 | 2004-12-22 | Nds Ltd | A method for literal data access |
FR2838597A1 (en) * | 2002-04-11 | 2003-10-17 | Thomson Licensing Sa | Digital television receiver electronic programme guide remote loading having digital word header and video information blocks with further header information interspersed. |
EP1365588A1 (en) * | 2002-04-11 | 2003-11-26 | Thomson Licensing S.A. | Method for transmitting an electronic programme guide containing previews and corresponding data stream |
Also Published As
Publication number | Publication date |
---|---|
AU2001234559A1 (en) | 2001-08-07 |
WO2001056272A9 (en) | 2002-10-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7707608B2 (en) | Messaging protocol for interactive delivery system | |
EP1258143B1 (en) | Bandwidth management techniques for delivery of interactive program guide | |
CA2313846C (en) | Television advertisement delivery system and method | |
US5905522A (en) | Resource allocation method for interactive televideo system | |
US7124424B2 (en) | Method and apparatus for providing interactive program guide (IPG) and video-on-demand (VOD) user interfaces | |
EP2122841B1 (en) | Method and apparatus providing scalability for channel change requests in a switched digital video system | |
US8151294B2 (en) | Technique for delivering entertainment programming content including commercial content therein over a communications network | |
US6704930B1 (en) | Advertisement insertion techniques for digital video streams | |
US6557030B1 (en) | Systems and methods for providing video-on-demand services for broadcasting systems | |
CA2177152C (en) | An operations center with video storage for a television program packaging and delivery system | |
EP0594350B1 (en) | Interactive television multicasting | |
US8255956B2 (en) | System and method for delivery of short-time duration video segments | |
US20020170059A1 (en) | Universal STB architectures and control methods | |
US20080216135A1 (en) | Methods and apparatus for improved content delivery including content delivery streams dynamically populated in response to user requests | |
US20020023267A1 (en) | Universal digital broadcast system and methods | |
US7519982B1 (en) | Efficient delivery of interactive program guide using demand-cast | |
US7607152B1 (en) | Demand-cast system and bandwidth management for delivery of interactive programming | |
US20090165056A1 (en) | Method and apparatus for scheduling a recording of an upcoming sdv program deliverable over a content delivery system | |
US7490343B1 (en) | Method and apparatus for keeping track of program indexes in an interactive delivery system | |
WO2001056272A1 (en) | Messaging protocol for demand-cast system and bandwidth management | |
US7992172B1 (en) | Method and systems for multicast using multiple transport streams | |
CA2406714A1 (en) | Universal digital broadcast system and methods | |
JPH11205766A (en) | Digital network system using catv system | |
MXPA01012095A (en) | Providing simulated broadcast services over a limited bandwidth channel. | |
KR20040063795A (en) | Transmission of delayed access client data and demand |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
AK | Designated states |
Kind code of ref document: C2 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: C2 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
COP | Corrected version of pamphlet |
Free format text: PAGES 1/19-19/19, DRAWINGS, REPLACED BY NEW PAGES 1/19-19/19; DUE TO LATE TRANSMITTAL BY THE RECEIVING OFFICE |
|
122 | Ep: pct application non-entry in european phase | ||
NENP | Non-entry into the national phase |
Ref country code: JP |