Sélection de la langue

Search

Sommaire du brevet 2406715 

Énoncé de désistement de responsabilité concernant l'information provenant de tiers

Une partie des informations de ce site Web a été fournie par des sources externes. Le gouvernement du Canada n'assume aucune responsabilité concernant la précision, l'actualité ou la fiabilité des informations fournies par les sources externes. Les utilisateurs qui désirent employer cette information devraient consulter directement la source des informations. Le contenu fourni par les sources externes n'est pas assujetti aux exigences sur les langues officielles, la protection des renseignements personnels et l'accessibilité.

Disponibilité de l'Abrégé et des Revendications

L'apparition de différences dans le texte et l'image des Revendications et de l'Abrégé dépend du moment auquel le document est publié. Les textes des Revendications et de l'Abrégé sont affichés :

  • lorsque la demande peut être examinée par le public;
  • lorsque le brevet est émis (délivrance).
(12) Demande de brevet: (11) CA 2406715
(54) Titre français: PROCEDES POUR FOURNIR DES SERVICES DE VIDEO A LA DEMANDE POUR SYSTEMES DE TELEDIFFUSION
(54) Titre anglais: METHODS FOR PROVIDING VIDEO-ON-DEMAND SERVICES FOR BROADCASTING SYSTEMS
Statut: Réputée abandonnée et au-delà du délai pour le rétablissement - en attente de la réponse à l’avis de communication rejetée
Données bibliographiques
(51) Classification internationale des brevets (CIB):
  • G06F 13/38 (2006.01)
  • H04L 12/16 (2006.01)
  • H04N 21/234 (2011.01)
  • H04N 21/236 (2011.01)
(72) Inventeurs :
  • HOANG, KHOI (Etats-Unis d'Amérique)
(73) Titulaires :
  • PREDIWAVE, CORP.
(71) Demandeurs :
  • PREDIWAVE, CORP. (Etats-Unis d'Amérique)
(74) Agent: FASKEN MARTINEAU DUMOULIN LLP
(74) Co-agent:
(45) Délivré:
(86) Date de dépôt PCT: 2001-05-31
(87) Mise à la disponibilité du public: 2001-12-06
Licence disponible: S.O.
Cédé au domaine public: S.O.
(25) Langue des documents déposés: Anglais

Traité de coopération en matière de brevets (PCT): Oui
(86) Numéro de la demande PCT: PCT/US2001/017986
(87) Numéro de publication internationale PCT: WO 2001093062
(85) Entrée nationale: 2002-10-10

(30) Données de priorité de la demande:
Numéro de la demande Pays / territoire Date
09/584,832 (Etats-Unis d'Amérique) 2000-05-31
09/709,948 (Etats-Unis d'Amérique) 2000-11-10

Abrégés

Abrégé français

Cette invention se rapporte à un procédé qui permet d'envoyer des données à une station client via un serveur de commande central (102) pour fournir des services de données à la demande et qui consiste à cet effet: à recevoir un fichier de données, à spécifier un intervalle de temps, à effectuer le parçage de ce fichier de données en plusieurs blocs de données sur la base de l'intervalle de temps, pour que chaque bloc de données soit affichable pendant un intervalle de temps, à déterminer un nombre requis d'intervalles de temps pour envoyer le fichier de données, à attribuer à chaque intervalle de temps au moins un premier bloc de données et éventuellement un ou plusieurs blocs de données additionnelles, pour que, en partant de n'importe lequel des intervalles de temps, (i) le fichier de données puisse être affiché par accès au premier bloc de données; (ii) lors d'un intervalle de temps suivant, un bloc de données suivant, consécutif à un bloc de données préalablement affiché, soit disponible pour affichage; et (iii) à répéter les étapes (ii) jusqu'à ce que tous les blocs de données pour le fichier de données ont été affichés, et à envoyer les blocs de données sur la base de l'étape d'attribution.


Abrégé anglais


A method of sending data to a client via a central controlling server (102) to
provide data-on-demand services comprises the steps of: receiving a data file,
specifying a time interval, parsing the data file into a plurality of data
blocks based on the time interval such that each data block is displayable
during a time interval, determining a required number of time slots to send
the data file, allocating to each time slot at least a first of the plurality
of data blocks and optionally one or more additional data blocks, such that
starting from any of the time slots, (i) the data file can be displayed by
accessing the first of the plurality of data blocks; (ii) at a consecutive
time slot, a next data block sequential to a prior displayed data block is
available for displaying; and (iii) repeating steps (ii) until all of the
plurality of data blocks for the data file has been displayed, and sending the
plurality of data blocks based on the allocating step.

Revendications

Note : Les revendications sont présentées dans la langue officielle dans laquelle elles ont été soumises.


WHAT IS CLAIMED IS:
1. A method for sending data to a client to provide data-on-demand services,
comprising the
steps of:
(a) receiving a data file;
(b) specifying a time interval;
(c) parsing said data file into a plurality of data blocks based on said time
interval;
(d) selecting a set of prefetch data blocks from said plurality of data
blocks;
(e) sending said set of prefetch data blocks in a dedicated channel;
(f) transmitting the remaining data blocks of said plurality of data blocks in
a
transmission channel.
2. The method of claim 1, wherein said step of selecting a set of prefetch
data blocks
includes the steps of:
determining a bandwidth reduction and a prefetch delay time; and
selecting said prefetch data blocks based on said bandwidth reduction and said
prefetch
delay time.
3. A method for sending data to a client to provide data-on-demand services,
comprising the
steps of:
(a) receiving a data file;
(b) specifying a time interval;
(c) parsing said data file into a plurality of data blocks based on said time
interval
such that each data block is displayable during said time interval;
(d) sending said plurality of data blocks in a transmission channel;
(e) receiving a request for a preview;
(f) randomly selecting a set of data blocks from said plurality of data blocks
to
compose said preview; and
(g) causing a display of said preview.
4. The method of claim 3, further comprising the steps of:
sending a set of commercial data blocks in a dedicated channel; and
causing a display of said set of commercial data blocks at predetermined
times.
5. The method of claim 4, wherein said step of causing a display includes the
steps of:
22

receiving a user selection of a price based on a frequency of commercial
display; and
causing a display of said set of commercial data blocks based on said user
selection.
6. The method of claim 3, further comprising the steps of:
checking a packet header of said data file for an emergency bit; and
causing a display of emergency information when said emergency bit is
detected.
7. The method of claim 6, further comprising the steps of:
determining whether said emergency information is for a relevant region; and
displaying said emergency information if said emergency information is for
said relevant
region.
23

Description

Note : Les descriptions sont présentées dans la langue officielle dans laquelle elles ont été soumises.


CA 02406715 2002-10-10
WO 01/93062 PCT/USO1/17986
METHODS FOR PROVIDING VIDEO-ON-DEMAND SERVICES FOR
BROADCASTING SYSTEMS
BRIEF DESCRIPTION OF THE INVENTION
This invention relates generally to data-on-demand systems. In particular,
this invention
relates to video-on-demand systems.
BACKGROUND OF THE INVENTION
Video-on-demand (VOD) systems are one type of data-on-demand (DOD) systems. In
VOD systems, video data files are provided by a server or a network of servers
to one or more
clients on a demand basis.
In a conventional VOD architecture, a server or a network of servers
communicates with
clients in a standard hierarchical client-server model. For example, a client
sends a request to a
server for a data file (e.g., a video data file). In response to the client
request, the server sends
the requested data file to the client. In the standard client-server model, a
client's request for a
data file can be fulfilled by one or more servers. The client may have the
capability to store any
received data file locally in non-volatile memory for later use. The standard
client-server model
requires a two-way communications infrastructure. Currently, two-way
communications require
building new infrastructure because existing cables can only provide one-way
communications.
Example of two-way communications infrastructure are hybrid fiber optics
coaxial cables (HFC)
or all fiber infrastructure. Replacing existing cables is very costly and the
resulting services may
not be affordable by most users.
In addition, the standard client-server model has many limitations when a
service
provider (e.g., a cable company) attempts to provide VOD services to a large
number of clients.
One limitation of the standard client-server model is that the service
provider has to implement a
mechanism to continuously listen and fulfill every request from each client
within the network;
thus, the number of clients who can receive service is dependent on the
capacity of such a
mechanism. One mechanism uses massively-parallel computers having large and
fast disk arrays
as local servers. However, even the fastest existing local server can only
deliver video data
streams to about 1000 to 2000 clients at one time. Thus, in order to service
more clients, the
number of local servers must increase. Increasing local servers requires more
upper level servers
to maintain control of the local servers.

CA 02406715 2002-10-10
WO 01/93062 PCT/USO1/17986
Another limitation of the standard client-server model is that each client
requires its own
bandwidth. Thus, the total required bandwidth is directly proportional to the
number of
subscribing clients. Cache memory within local servers has been used to
improve bandwidth
limitation but using cache memory does not solve the problem because cache
memory is also
limited.
Presently, in order to make video-on-demand services more affordable for
clients,
existing service providers are increasing the ratio of clients per local
server above the local
server's capabilities. Typically, a local server, which is capable of
providing service to 1000
clients, is actually committed to service 10,000 clients. This technique may
work if most of the
subscribing clients do not order videos at the same time. However, this
technique is set up for
failure because most clients are likely to want to view videos at the same
time (i.e., evenings and
weekends), thus, causing the local server to become overloaded.
Thus, it is desirable to provide a system that is capable of providing on-
demand services
to a large number of clients over virtually any transmission medium without
replacing existing
infrastructure.
SUMMARY OF THE INVENTION
In an exemplary embodiment, at a server side, a method for sending data to a
client to
provide data-on-demand services comprises the steps of: receiving a data file,
specifying a time
interval, parsing the data file into a plurality of data blocks based on the
time interval such that
each data block is displayable during the time interval, determining a
required number of time
slots to send the data file, allocating to each time slot at least a first of
the plurality of data blocks
and optionally one or more additional data blocks, such that the plurality of
data blocks is
available in sequential order to a client accessing the data file during any
time slot, and sending
the plurality of data blocks based on the allocating step. In one embodiment,
the parsing step
includes the steps of: determining an estimated data block size, determining a
cluster size of a
memory in a channel server, and parsing the data file based on the estimated
data block size and
the cluster size. In another embodiment, the determining step includes the
step of assessing
resource allocation and bandwidth availability.
In one embodiment, the method further comprises the steps of selecting a set
of prefetch
data blocks from the plurality of data blocks and separately sending the set
of prefetch data
blocks in a dedicated channel for sending prefetch data, program guide,
commercials, firmware
update, etc. In an exemplary embodiment, the step of selecting a set of
prefetch data blocks
includes the steps of: (1) determining a bandwidth reduction, a bandwidth
allocation for prefetch
2

CA 02406715 2002-10-10
WO 01/93062 PCT/USO1/17986
data in the dedicated channel, and a delay time; and (2) selecting the
prefetch data blocks based
on the bandwidth reduction, the bandwidth allocation, and the delay time.
In another embodiment, the method further comprises the steps of receiving a
request for
a preview, randomly selecting a set of data blocks from the plurality of data
blocks to compose
the preview, and causing a display of the preview. In yet another embodiment,
the method
further comprises sending a set of commercial data blocks in the dedicated
channel and causing a
display of the set of commercial data blocks at predetermined times. In an
exemplary
embodiment, the commercial data blocks are continuously sent in the dedicated
channel. In this
embodiment, the step of displaying the set of commercial data blocks includes
the steps of
receiving a user selection of a price based on a frequency of commercial
display and causing a
display of the set of commercial data blocks based on the user selection.
In yet another embodiment, the method further comprises the steps of checking
a packet
header of the data file for an emergency bit, tuning to the dedicated channel
to receive
emergency information when the emergency bit is detected, and causing a
display of the
emergency information. In one embodiment, this method further comprises the
steps of
determining whether the emergency information is for a relevant region and
displaying the
emergency information if the emergency information is for the relevant region.
In an exemplary embodiment, at a client side, a method for processing data
received from
a server to provide data-on-demand services comprises the steps of: (a)
receiving a selection of a
data file during a first time slot; (b) receiving at least one data block of
the data file during a
second time slot; (c) during a next time slot: receiving any data block not
already received,
sequentially displaying a data block of the data file, and repeating step (c)
until all data blocks of
the data file has been received and displayed. In one embodiment, the method
for processing
data received from a server is performed by a set-top box at the client side.
In an exemplary embodiment, a data file is divided into a number of data
blocks and a
scheduling matrix is generated based on the number of data blocks. At the
server side, the
scheduling matrix provides a send order for sending the data blocks, such that
a client can access
the data blocks in sequential order at a random time. In an exemplary
embodiment, a method for
generating a scheduling matrix for a data file comprises the steps of: (a)
receiving a number of
data blocks [x] for a data file; (b) setting a first variable [j] to zero; (c)
setting a second variable
[i] to zero; (d) clearing all entries in a reference array; (e) writing at
least one data block stored in
matrix positions of a column [(i+j) modulo x] in a matrix to a reference
array, if the reference
array does not already contain the data block; (f) writing a data block [i]
into the reference array
and a matrix position [(i+j) modulo x, j] of the matrix, if the reference
array does not contain the
3

CA 02406715 2002-10-10
WO 01/93062 PCT/USO1/17986
data block [i]; (g) incrementing the second variable [i] by one and repeating
step (e) until the
second variable [i] is equal to the number of data blocks [x]; and (h)
incrementing the first
variable [j] by one and repeating the step (c) until the first variable [j] is
equal to the number of
data blocks [x]. In one embodiment, a scheduling matrix is generated for each
data file in a set
of data files and a convolution method is applied to generate a delivery
matrix based on the
scheduling matrices for sending the set of data files.
A data-on-demand system comprises a first set of channel servers, a central
controlling
server for controlling the first set of channel servers, a first set of up-
converters coupled to the
first set of channel servers, a combinerlamplifier coupled to the first set of
up-converters, and a
combiner/amplifier adapted to transmit data via a transmission medium. In an
exemplary
embodiment, the data-on-demand system further comprises a channel monitoring
module for
monitoring the system, a switch matrix, a second set of channel servers, and a
second set of up-
converters. The channel monitoring module is configured to report to the
central controlling
server when system failure occurs. The central controlling server, in response
to report from the
channel monitoring module, instructs the switch matrix to replace a defective
channel server in
the first set of channel servers with a channel server in the second set of
channel servers and a
defective up-converter in the first set of up-converters with an up-converter
in the second set of
up-converters.
A method for providing data-on-demand services comprises the steps of
calculating a
delivery matrix of a data file, sending the data file in accordance with the
delivery matrix, such
that a large number of clients is capable of viewing the data file on demand.
In one embodiment,
the data file includes a video file.
BRIEF DESCRIPTION OF THE DRAWINGS
FIGURE 1 A illustrates an exemplary DOD system in accordance with an
embodiment of
the invention.
FIGURE 1B illustrates an exemplary DOD system in accordance with another
embodiment of the invention.
FIGURE 2 illustrates an exemplary channel server in accordance with an
embodiment of
the invention.
FIGURE 3 illustrates an exemplary set-top box in accordance with an embodiment
of the
invention.
FIGURE 4 illustrates an exemplary process for generating a scheduling matrix
in
accordance with an embodiment of the invention.
4

CA 02406715 2002-10-10
WO 01/93062 PCT/USO1/17986
DETAILED DESCRIPTION OF THE INVENTION
Figure 1A illustrates an exemplary DOD system 100 in accordance with an
embodiment
of the invention. In this embodiment, the DOD system 100 provides data files,
such as video
files, on demand. However, the DOD system 100 is not limited to providing
video files on
demand but is also capable of providing other data files, for example, game
files on demand.
The DOD system 100 includes a central controlling server 102, a central
storage 103, a plurality
of channel servers 104a-104n, a plurality of up-converters 106a-106n , and a
combiner/amplifier
108. The central controlling server 102 controls the channel servers 104. The
central storage
103 stores data files in digital format. In an exemplary embodiment, data
files stored in the
central storage I03 is accessible via a standard network interface (e.g.,
ethernet connection) by
any authorized computer, such as the central controlling server 102, connected
to the network.
Each channel server 104 is assigned to a channel and is coupled to an up-
converter 106. The
channel servers 104 provide data files that are retrieved from the central
storage 103 in
accordance with instructions from the central controlling server 102. The
output of each channel
server 104 is a quadrature amplitude modulation (QAM) modulated intermediate
frequency (IF)
signal having a suitable frequency for the corresponding up-converter 106. The
QAM-
modulated IF signals are dependent upon adopted standards. The current adopted
standard in the
United States is the data-over-cable-systems-interface-specification (DOCSIS)
standard, which
requires an approximately 43.75MHz IF frequency. The up-converters 106 convert
IF signals
received from the channel servers 104 to radio frequency signals (RF signals).
The RF signals,
which include frequency and bandwidth, are dependent on a desired channel and
adopted
standards. For example, under the current standard in the United States for a
cable television
channel 80, the RF signal has a frequency of approximately 559.25MHz and a
bandwidth of
approximately 6MHz. The outputs of the up-converters 106 are applied to the
combiner/amplifier 108. The combiner/amplifier 108 amplifies, conditions, and
combines the
received RF signals then outputs the signals out to a transmission medium 110.
In an exemplary embodiment, the central controlling server 102 includes a
graphics user
interface (not shown) to enable a service provider to schedule data delivery
by a drag-and-drop
operation. Further, the central controlling server 102 authenticates and
controls the channel
servers 104 to start or stop according to delivery matrices. In an exemplary
embodiment, the
central controlling server 102 automatically selects a channel and calculates
delivery matrices for
transmitting data files in the selected channel. The central controlling
server 102 provides
offline addition, deletion, and update of data file information (e.g.,
duration, category, rating,
5

CA 02406715 2002-10-10
WO 01/93062 PCT/USO1/17986
and/or brief description). Further, the central controlling server 102
controls the central storage
103 by updating data files and databases stored therein.
In an exemplary embodiment, an existing cable television system 120 may
continue to
feed signals into the combinerlamplifier 108 to provide non-DOD services to
clients. Thus, the
DOD system 100 in accordance with the invention does not disrupt present cable
television
services.
Figure IB illustrates another exemplary embodiment of the DOD system 100 in
accordance with the invention. In addition to the elements illustrated in
Figure 1A, the DOD
system 100 includes a switch matrix 112, a channel monitoring module 114, a
set of back-up
channel servers 116a-116b, and a set of back-up up-converters 118a-118b. In
one embodiment,
the switch matrix 112 is physically located between the up-converters 106 and
the
combiner/amplifier 108. The switch matrix 112 is controlled by the central
controlling server
102. The channel monitoring module 114 comprises a plurality of configured set-
top boxes,
which simulate potential clients, for monitoring the health of the DOD system
100. Monitoring
results are communicated by the channel monitoring module 1 I4 to the central
controlling server
102. Tn case of a channel failure (i.e., a channel server failure, an up-
converter failure, or a
communication link failure), the central controlling server 102 through the
switch matrix 112
disengages the malfunctioning component and engages a healthy backup component
116 and/or
I 18 to resume service.
In an exemplary embodiment, data files being broadcasted from the DOD system
100 are
contained in motion pictures expert group (MPEG) files. Each MPEG file is
dynamically
divided into data blocks and sub-blocks mapping to a particular portion of a
data file along a
time axis. These data blocks and sub-blocks are sent during a pre-determined
time in accordance
with three-dimensional delivery matrices provided by the central controlling
server 102. A
feedback channel is not necessary for the DOD system 100 to provide DOD
services. However,
if a feedback channel is available, the feedback channel can be used for other
purpose, such as
billing or providing Internet services.
Figure 2 illustrates an exemplary channel server 104 in accordance with an
embodiment
of the invention. The channel server 104 comprises a server controller 202, a
CPU 204, a QAM
modulator 206, a local memory 208, and a network interface 210. The server
controller 202
controls the overall operation of the channel server I04 by instructing the
CPU 204 to divide data
files into blocks (further into sub-blocks and data packets), select data
blocks for transmission in
accordance with a delivery matrix provided by the central controlling server
102, encode selected
data, compress encoded data, then deliver compressed data to the QAM modulator
206. The
6

CA 02406715 2002-10-10
WO 01/93062 PCT/USO1/17986
QAM modulator 206 receives data to be transmitted via a bus (i.e., PCI, CPU
local bus) or
Ethernet connections. In an exemplary embodiment, the QAM modulator 206 may
include a
downstream QAM modulator, an upstream quadrature amplitude modulation
/quadrature phase
shift keying (QAM/QPSK) burst demodulator with forward error correction
decoder, and/or an
upstream tuner. The output of the QAM modulator 206 is an )F signal that can
be applied
directly to an up-converter 106.
The network interface 210 connects the channel server 104 to other channel
servers 104
and to the central controlling server 102 to execute the scheduling and
controlling instructions
from the central controlling server 102, reporting status back to the central
controlling server
102, and receiving data files from the cental storage 103. Any data file
retrieved from the central
storage 103 can be stored in the local memory 208 of the channel server 104
before the data file
is processed in accordance with instructions from the server controller 202.
In an exemplary
embodiment, the channel server 104 may send one or more DOD data streams
depending on the
bandwidth of a cable channel (e.g., 6, 6.5, or 8MHz), QAM modulation (e.g.,
QAM 64 or QAM
256), and a compression standard/bit rate of the DOD data stream (i.e., MPEG-1
or MPEG-2).
Figure 3 illustrates an exemplary set-top box (STB) 300 in accordance with an
embodiment of the invention. The STB 300 comprises a QAM demodulator 302, a
CPU 304, a
conditional access module 306 (e.g., a smart card system), a local memory 308,
a buffer memory
309, a STB controller 310, a decoder 312, and a graphics overlay module 314.
The STB
controller 310 controls the overall operation of the STB 300 by controlling
the CPU 302 and the
QAM demodulator 302 to select data in response to a client's request, decode
selected data,
decompress decoded data, re-assemble decoded data, store decoded data in the
local memory 308
or the buffer memory 309, and deliver stored data to the decoder 312. In an
exemplary
embodiment, the STB controller 310 controls the overall operation of the STB
300 based on data
packet headers in the data packets received from the transmission medium 110.
In an exemplary
embodiment, the local memory 308 comprises non-volatile memory (e.g., a hard
drive) and the
buffer memory 309 comprises volatile memory.
In one embodiment, the QAM demodulator 302 comprises transmitter and receiver
modules and one or more of the following: privacy encryption/decryption
module, forward error
correction decoder/encoder, tuner control, downstream and upstream processor,
CPU and
memory interface circuits. The QAM demodulator 302 receives modulated IF
signals, samples
and demodulates the signals to restore data. The conditional access module 306
permits a
decoding process when access is granted after authentication and/or when
appropriate fees have
been charged. Access condition is determined by the service provider.
7

CA 02406715 2002-10-10
WO 01/93062 PCT/USO1/17986
. In an exemplary embodiment, when access is granted, the decoder 312 decodes
at least
one data block to transform the data block into images displayable on an
output screen. The
decoder 312 supports commands from a subscribing client, such as play, stop,
pause, step,
rewind, forward, etc.
The graphics overlay module 314 enhances displayed graphics quality by, for
example,
providing alpha blending or picture-in-picture capabilities. In an exemplary
embodiment, the
graphics overlay module 314 can be used fox graphics acceleration during game
playing mode,
for example, when the service provider provides games-on-demand services using
the system in
accordance with the invention.
In an exemplary embodiment, although data files are broadcasted to all cable
television
subscribers, only the DOD subscriber who has a compatible STB 300 will be able
to decode and
enjoy data-on-demand services. In one exemplary embodiment, permission to
obtain data files
on demand can be obtained via a smart card system in the conditional access
control module 306.
A smart card may be rechargeable at a local store or vending machine set up by
a service
provider. In another exemplary embodiment, a flat fee system provides a
subscriber an unlimited
access to all available data files.
In an exemplary embodiment, data-on-demand interactive features permit a
client to
select at any time an available data file. The amount of time between when a
client presses a
select button and the time the selected data file begins playing is referred
to as a response time.
As more resources are allocated (e.g., bandwidth, server capability) to
provide DOD services, the
response time gets shorter. In an exemplary embodiment, a response time can be
determined
based on an evaluation of resource allocation and desired quality of service.
In an exemplary embodiment, a selected response time determines the duration
of a time
slot. The duration of a time slot (TS) is the time interval for playing a data
block at normal speed
by a client. In an exemplary embodiment, a data file, such as a video file, is
divided into a
number of data blocks such that each data block can support the playing of the
data file for the
duration of a time slot.
In one embodiment, the number of data blocks (NUM OF BLKS) for each data file
can
be calculated as follows:
Estimated_BLK_Size = (DataFile_Size * TS) / DataFile_Length (1)
BLK SIZE = (Estimated BLK Size + CLUSTER_SIZE - lByte) / CLUSTER SIZE (2)
BLK_SIZE BYTES = BLK_SIZE * CLUSTER_SIZE (3)
NUM-OF_BLKS =(DataFile_Size + BLK_SIZE_BYTES - lByte) / BLK_SIZE_BYTES (4)
8

CA 02406715 2002-10-10
WO 01/93062 PCT/USO1/17986
. In equations (1) to (4), the Estimated_BLK_Size is an estimated block size
(in Bytes); the
DataFile_Size is the data file size (in Bytes); TS represents the duration of
a time slot (in
seconds); DataFile_Length is the duration of the data file (in seconds); BLK
SIZE is the number
of clusters needed for each data block; CLUSTER SIZE is the size of a cluster
in the local
memory 208 for each channel server 104 (e.g., 64KBytes); BLK_SIZE_BYTES is a
block size in
Bytes. In this embodiment, the number of blocks (NUM_OF_BLKS) is equal to the
data file size
(in Bytes) plus a data block size in Bytes minus 1 Byte and divided by a data
block size in Bytes.
Equations (1) to (4) illustrate one specific embodiment. A person of skill in
the art would
recognize that other methods are available to calculate a number of data
blocks for a data file.
For example, dividing a data file into a number of data blocks is primarily a
function of an
estimated block size and the cluster size of the local memory 208 of a channel
server 104. Thus,
the invention should not be limited to the specific embodiment presented
above.
Figure 4 illustrates an exemplary process for generating a scheduling matrix
for sending
a data file in accordance with an embodiment of the invention. In an exemplary
embodiment,
this invention uses time division multiplexing (TDM) and frequency division
multiplexing
(FDM) technology to compress and schedule data delivery at the server side. In
an exemplary
embodiment, a scheduling matrix is generated fox each data file. In one
embodiment, each data
file is divided into a number of data blocks and the scheduling matrix is
generated based on the
number of data blocks. Typically, a scheduling matrix provides a send order
for sending data
blocks of a data file from a server to clients, such that the data blocks are
accessible in sequential
order by any client who wishes to access the data file at a random time.
At step 402, a number of data blocks (x) for a data file is received. A first
variable, j, is
set to zero (step 404). A reference array is cleared (step 406). The reference
array keeps track of
data blocks for internal management purposes. Next, j is compared to x (step
408). If j is less
than x, a second variable, i, is set to zero (step 412). Next, i is compared
to x (step 414). If i is
less than x, data blocks stored in the column [(i+j) modulo (x)] of a
scheduling matrix are written
into the reference array (step 418). If the reference array already has such
data block(s), do not
write a duplicate copy. Initially, since the scheduling matrix does not yet
have entries, this step
can be skipped. Next, the reference array is checked if it contains data block
i (step 420).
Initially, since all entries in the reference array has been cleared at step
406, there would be
nothing in the reference array. If the reference array does not contain data
block i, data block i is
added into the scheduling matrix at matrix position [(i+j) modulo (x), j] and
the reference array
(step 422). After the data block i is added to the scheduling matrix and the
reference array, i is
incremented by 1, such that i = i + 1 (step 424), then the process repeats at
step 414 until i = x. If
9

CA 02406715 2002-10-10
WO 01/93062 PCT/USO1/17986
the reference array contains data block i, i is incremented by l, such that i
= i + 1 (step 424), then
the process repeats at step 414 until i = x. When i = x, j is incremented by
1, such that j = j + 1
(step 4.16) and the process repeats at step 406 until j = x. The entire
process ends when j = x
(step 410).
In an exemplary embodiment, if a data file is divided into six data blocks (x
= 6), the
scheduling matrix and the reference arrays are as follows:
Scheduling Matrix (SM)
TSO TSl TS2 TS3 TS4 TS5
[0,0] blk0[1,0] blkl[2,0] blk2[3,0]blk3[4,0] blk [5,0]blk
4 5
[0,1] [1,1] blk [2,1] [3,1] [4,1] [5,0]
0
[0,2] [1,2] [2,2] blk0[3,2]blkl[4,2] [5,1]
[0,3] [1,3] [2,3] [3,3]blk0[4,3] [5,2]blk2
[0,4] [1,4] blk3[2,4] [3,4] [4,4] blk0[5,3]blkl
[0,5] [1,5] [2,5] [3,5]blk4[4,5] [5,4]blk0
Reference Array (RA)
space0 spacel space space3 space4 spaces
2
TSO blk0 blkl blk2 blk3 blk4 blk5
TS1 blkl blk0 blk2 blk3 blk4 blk5
TS2 blk2 blk0 blk3 blkl blk4 blk5
TS3 blk3 blkl blk0 blk4 blk5 blk2
TS4 blk4 blk0 blk5 blk2 blkl blk3
TS5 blk5 blk2 blkl blk0 blk3 blk4
In this exemplary embodiment, based on the scheduling matrix above, the six
data blocks
of the data file are sent in the following sequence:

CA 02406715 2002-10-10
WO 01/93062 PCT/USO1/17986
TS0 => blk0
TS 1 => blk0, blkl, blk3
TS2 => blk0, blk2
TS3 => blk0, blkl, blk3, blk4
TS4 => blk0, blk4
TS5 => blk0, blkl, blk2, blk5
In another exemplary embodiment, a look-ahead process can be used to calculate
a look-
ahead scheduling matrix to send a predetermined number of data blocks of a
data file prior to a
predicted access time. For example, if a predetermined look-ahead time is the
duration of one
time slot, for any time slot greater than or equal to time slot number four,
data block 4 (blk4) of a
data file should be received by a STB 300 at a subscribing client at or before
TS3, but blk4
would not be played until TS4. The process steps fox generating a look-ahead
scheduling matrix
is substantially similar to the process steps described above for Figure 4
except that the look-
ahead scheduling matrix in this embodiment schedules an earlier sending
sequence based on a
look-ahead time. Assuming a data file is divided into six data blocks, an
exemplary sending
sequence based on a look-ahead scheduling matrix, having a look-ahead time of
the duration of
two time slots, can be represented as follows:
TSO => blk0
TS 1 => blk0, blk 1, blk3, blk4
TS2 => blk0, blk2
TS3 => blk0, blkl, blk3, blk4, blk5
TS4 => blk0, blk5
TS5 => blk0, blkl, blk2
A three-dimensional delivery matrix for sending a set of data files is
generated based on
the scheduling matrices for each data file of the set of data files. In the
three-dimensional
delivery matrix, a third dimension containing ms for each data file in the set
of data files is
generated. The three-dimensional delivery matrix is calculated to efficiently
utilize available
bandwidth in each channel to deliver multiple data streams. In an exemplary
embodiment, a
convolution method, which is well known in the art, is used to generate a
three-dimensional
delivery matrix to schedule an efficient delivery of a set of data files. For
example, a
convolution method may include the following policies: (1) the total number of
data blocks sent
11

CA 02406715 2002-10-10
WO 01/93062 PCT/USO1/17986
in the duration of any time slot (TS) should be kept at a smallest possible
number; and (2) if
multiple partial solutions are available with respect to policy (1), the
preferred solution is the one
which has a smallest sum of data blocks by adding the data blocks to be sent
during the duration
of any reference time slot, data blocks to be sent during the duration of a
previous time slot (with
respect to the reference time slot), and data blocks to be sent during the
duration of a next time
slot (with respect to the reference time slot). For example, assuming an
exemplary system
sending two short data files, M and N, where each data file is divided into
six data blocks, the
sending sequence based on a scheduling matrix is as follows:
TSO => blk0
TS 1 => blk0, blkl, blk3
TS2 => blk0, blk2
TS3 => blk0, blkl, blk3, blk4
TS4 => blk0, blk4
TS5 => blk0, blkl, blk2, blk5
Applying the exemplary convolution method as described above, possible
combinations
of delivery matrices are as follows:
Option 1: Send video file N at shift 0 TS Total Data Blocks
_______________________________________________________________________________
_____________________________________________TSO => Mo,
NO 2 TS1 => M0, M1, M3, N0,
Nl, N3 6 TS2 => M0, M2, N0, N2
4TS3 => M0, Ml, M3, M4, N0, N1, N3, N4
8TS4 => M0, M4, N0, N4
2,5 4TS5 => M0, M1, M2, M5, N0, Nl, N2, N5
8
Option 2: Send video file N at shift 1 TS Total Data Blocks---------------
_______________________________________________________________________________
______________________________TSO => M0, N0, N1, N3
4 TS1 => M0, Ml, M3, N0,
N2 5 TS2 => M0, M2, N0, Nl, N3,
N4 6TS3 => M0, M1, M3, M4, N0,
N4 6 TS4 => M0, M4, N0, N1, N2, N5
6TS5 => M0, M1, M2, M5, NO
5
12

CA 02406715 2002-10-10
WO 01/93062 PCT/USO1/17986
- Option 3: Send video file N at shift 2 TS Total Data Blocks---------------
___________________,___________________________________________________________
______________________________TSO => M0, N0, N2
3 TSl => M0, M1, M3, N0, Nl, N3,
N4 7 TS2 => M0, M2, N0, N4
4TS3 => M0, Ml, M3, M4, N0, N1, N2, N5
8TS4 => M0, M4, NO
3TS5 => M0, M1, M2, M5, N0, N1, N3
7
Option 4: Send video file N at shift 3 TS Total Data Blocks----------------
_______________________-________________________________-______________-
____________________________________TSO => M0, N0, Nl, N3,
N4 5 TS1 => M0, Ml, M3, N0,
N4 5 TS2 => M0, M2, N0, Nl, N2,
N5 6 TS3 => M0, Ml, M3, M4,
No 5
TS4 => M0, M4, N0, N1, N3 5 TS5 =>
M0, M1, M2, M5, N0, N2 6
Option 5: Send video file N at shift 4 TS Total Data Blocks----------------
_______________________________________________________________________________
_____________________________TSO => M0, N0,
N4 3 TS1 => M0, M1, M3, N0, Nl, N2,
N5 7 TS2 => M0, M2, NO
3TS3 => M0, M1, M3, M4, N0, Nl, N3
7
TS4 => M0, M4., N0, N2 4TS5 => M0, Ml, M2, M5, N0,
N1, N3, N4 8
Option 6: Send video file N at shift 5 TS Total Data Blocks-----------------
_______________________________________________________________________________
____________________________TSO => M0, N0, Nl, N2,
N5 5
TS1 => M0, M1, M3, NO 4 TS2 => M0,
M2, N0, N1, N3 5TS3 => M0, M1, M3, M4, N0,
N2 6TS4 => M0, M4, N0, N1, N3, N4
6TS5 => M0, M1, M2, M5, N0, N4
6
Applying policy (1), options 2, 4, and 6 have the smallest maximum number of
data
blocks (i.e., 6 data blocks) sent during any time slot. Applying policy (2),
the optimal delivery
matrix in this exemplary embodiment is option 4 because option 4 has the
smallest sum of data
13

CA 02406715 2002-10-10
WO 01/93062 PCT/USO1/17986
blocks of any reference time slot plus data blocks of neighboring time slots
(i.e., 16 data blocks).
Thus, optimally for this embodiment, the sending sequence of the data file N
should be shifted
by three time slots. In an exemplary embodiment, a three-dimensional delivery
matrix is
generated for each channel server I04.
When data blocks for each data file axe sent in accordance with a delivery
matrix, a large
number of subscribing clients can access the data file at a random time and
the appropriate data
blocks of the data file will be timely available to each subscribing client.
In the example
provided above, assume the duration of a time slot is equal to 5 seconds, the
DOD system 100
sends data blocks for data files M and N in accordance with the optimal
delivery matrix (i.e.,
shift delivery sequence of data file N by three time slots) in the following
manner:
Time 00:00:00=> MO NO N1 N3 N4
Time 00:00:05=> MO Ml M3 NO N4
Time 00:00:10=> MO M2 NO Nl N2 N5
Time 00:00:15=> MO Ml M3 M4 NO
Time 00:00:20=> MO M4 NO N1 N3
Time 00:00:25=> MO Ml M2 M5 NO N2
Time 00:00:30=> MO NON1 N3 N4
Time 00:00:35=> MO Ml M3 NO N4
Time 00:00:40=> MO M2 NO N1 N2 N5
Time 00:00:45 => MO M 1 M3 M4 NO
Time 00:00:50=> MO M4 NO N1 N3
Time 00:00:55=> MO M1 M2 M5 NO N2
If at time 00:00:00 a client A selects movie M, the STB 300 at client A
receives, stores,
plays, and rejects data blocks as follows:
Time 00:00:00 => Receive MO => play M0, store M0.
Time 00:00:05 => Receive Ml, M3 => play Ml, store M0, M1, M3.
Time 00:00:10 => Receive M2 => play M2, store M0, M1, M2 M3.
Time 00:00:15 => Receive M4 => play M3, store M0, Ml, M2, M3, M4.
Time 00:00:20 => Receive none => play M4, store M0, Ml, M2, M3, M4.
Time 00:00:25 => Reeeive M5 => play M5, store M0, Ml, M2, M3, M4, M5.
14

CA 02406715 2002-10-10
WO 01/93062 PCT/USO1/17986
If at time 00:00:10, a client B selects movie M, the STB 300 at client B
receives, stores,
plays, and rejects data blocks as follows:
Time 00:00:10 => Rcv M0, M2 => play M0, store M0, M2.
Time 00:00:15 => Rcv Ml, M3, M4 => play M1, store M0, M1, M2, M3, M4.
Time 00:00:20 => Rcv none => play M2, store M0, Ml, M2, M3, M4.
Time 00:00:25 => Rcv M5 => play M3, store M0, M1, M2, M3, M4, M5.
Time 00:00:30 => Rcv none => play M4, store M0, Ml, M2, M3, M4, M5.
Time 00:00:35=> Rcv none => play M5, store M0, Ml, M2, M3, M4, M5.
If at time 00:00:15, a client C selects movie N, the STB 300 of the client C
receives,
stores, plays, and rejects data blocks as follows:
Time 00:00:15 => Rcv NO => play N0, store N0.
Time 00:00:20 => Rcv N1 N3 => play N1, store N0, N1, N3.
Time 00:00:25 => Rcv N2 => play N2, store N0, Nl, N2, N3.
Time 00:00:30 => Rcv N4 => play N3, store N0, N1, N2, N3, N4.
Time 00:00:35 => Rcv none => play N4, store N0, N1, N2, N3, N4.
Time 00:00:40 => Rcv N5 => play N5, store N0, Nl, N2, N3, N4, N5.
If at time 00:00:30, a client D also selects movie N, the STB 300 at the
client D receives,
stores, plays, and rejects data blocks as follows:
Time 00:00:30 => Rcv N0, N1, N3, N4 => play N0, store N0, N1, N3, N4.
Time 00:00:35 => Rcv none => play N1, store N0, N1, N3, N4.
Time 00:00:40 => Rcv N2, N5 => play N2, store N0, N1, N2, N3, N4, N5.
Time 00:00:45 => Rcv none => play N3, store N0, N1, N2, N3, N4, N5.
Time 00:00:50 => Rcv none => play N4, store N0, N1, N2, N3, N4, N5.
Time 00:00:55 => Rcv none => play N5, store N0, N1, N2, N3, N4, N5.
As shown in the above examples, any combination of clients can at a random
time
independently select and begin playing any data file provided by the service
provider.
GENERAL OPERATION
A service provider can schedule to send a number of data files (e.g., video
files) to
channel servers 104 prior to broadcasting. The central controlling server 102
calculates and

CA 02406715 2002-10-10
WO 01/93062 PCT/USO1/17986
sends to the channel servers 104 three-dimensional delivery matrices (ID, time
slot, and data
block send order). During broadcasting, channel servers 104 consult the three-
dimensional
delivery matrices to send appropriate data blocks in an appropriate order.
Each data file is
divided into data blocks so that a large number of subscribing clients can
separately begin
viewing a data file continuously and sequentially at a random time. The size
of a data block of a
data file is dependent on the duration of a selected time slot and the bit
rate of the data stream of
the data file. For example, in a constant bit rate MPEG data stream, each data
block has a fixed
size of: Block Size (MBytes) = BitRate (Mb/s) x TS (sec) / 8 (1).
In an exemplary embodiment, a data block size is adjusted to a next higher
multiple of a
memory cluster size in the local memory 208 of a channel server 104. For
example, if a
calculated data block length is 720Kbytes according to equation ( 1 ) above,
then the resulting
data block length should be 768Kbytes if the cluster size of the local memory
208 is 64Kbytes.
In this embodiment, data blocks should be further divided into multiples of
sub-blocks each
having the same size as the cluster size. In this example, the data block has
twelve sub-blocks of
64KBytes.
A sub-block can be further broken down into data packets. Each data packet
contains a
packet header and packet data. The packet data length depends on the maximum
transfer unit
(MTU) of a physical layer where each channel server's CPU sends data to. In
the preferred
embodiment, the total size of the packet header and packet data should be less
than the MTU.
However, for maximum efficiency, the packet data length should be as long as
possible.
In an exemplary embodiment, data in a packet header contains information that
permits
the subscriber client's STB 300 to decode any received data and determine if
the data packet
belongs to a selected data file (e.g., protocol signature, version, ID, or
packet type information).
The packet header may also contain other information, such as block/sub-
block/packet number,
packet length, cyclic redundancy check (CRC) and offset in a sub-block, and/or
encoding
information.
Once received by a channel server 104, data packets are sent to the QAM
modulator 206
where another header is added to the data packet to generate a QAM-modulated
IF output signal.
The maximum bit rate output for the QAM modulator 206 is dependent on
available bandwidth.
For example, for a QAM modulator 206 with 6MHz bandwidth, the maximum bit rate
is 5.05
(bit/symbol) x 6 (MHz) = 30.3 Mbitlsec.
The QAM-modulated IF signals are sent to the up-converters 106 to be converted
to RF
signals suitable for a specific channel (e.g., for CATV channel 80, 559.250MHz
and 6MHz
bandwidth). For example, if a cable network has high bandwidth (or bit rate),
each channel can
16

CA 02406715 2002-10-10
WO 01/93062 PCT/USO1/17986
be used to provide more than one data stream, with each data stream occupying
a virtual sub-
channel. For example, three MPEG1 data streams can fit into a 6MHz channel
using QAM
modulation. The output of the up-converters 106 is applied to the
combiner/amplifier 108, which
sends the combined signal to the transmission medium 110.
In an exemplary embodiment, the total system bandwidth (BW) for transmitting
"N" data
streams is BW = N x bw, where bw is the required bandwidth per data stream.
For example,
three MPEG-1 data streams can be transmitted at the same time by a DOCSIS
cable channel
having a system bandwidth of 30.3 Mbits/sec because each MPEG-1 data stream
occupies 9
Mbits/sec of the system bandwidth.
Typically, bandwidth is consumed regardless of the number of subscribing
clients
actually accessing the DOD service. Thus, even if no subscribing client is
using the DOD
service, bandwidth is still consumed to ensure the on-demand capability of the
system.
In an exemplary embodiment, the total system bandwidth (BW) may be reduced by
prefetching some data blocks of each data file. Prefetch data blocks are
continuously sent in a
separate, dedicated channel. In one embodiment, the prefetch data blocks for a
data file are sent
sequentially in a group. By sending prefetch data blocks, the total system
bandwidth (BW)
needed fox delivering the remaining data blocks is reduced. After determining
a desirable
number of prefetch data blocks to be sent in a separate channel, the schedule
for sending the
remaining data blocks should be adjusted so that the prefetch data blocks are
not sent again with
other data blocks.
For example, in the exemplary schedule matrix above, where a data file is
divided into
six data blocks, if the first data block "b0" and the second data block "b 1"
are both prefetch data
blocks, the schedule matrix should be modified to be as follows for the
remaining data blocks
(b2-b5):
TSO => [nothing)
TS 1 => blk3
TS2 => blk2
TS3 => blk3, blk4
TS4 => blk4
TS5 => blk2, blk5
In the above example, if b0 is the only prefetch data block, the total
bandwidth for
sending the remaining data blocks (bl-b5) of the data file is reduced by 37.5%
[i.e., six data
blocks removed from a total of sixteen data blocks]. Next, if data block "b 1"
is also a prefetch
data block, the bandwidth for sending the remaining data blocks (b2-b5) is
reduced by an
17

CA 02406715 2002-10-10
WO 01/93062 PCT/USO1/17986
additional 12.5%. Thus, the incremental bandwidth reduction for prefetching b1
is not as great
as prefetching b0. Because the incremental bandwidth reduction diminishes as
more data blocks
are prefetched, an optimal number of prefetch data blocks for each data file
can be determined
based on a desired bandwidth reduction. In an exemplary embodiment, the
bandwidth saved by
prefetching data blocks x to y of a data file can be estimated by the
following equation:
~(I);n=(x+1)to(y+1)
n
In addition, as the number of prefetch data blocks increases, the prefetch
delay time
increases. The prefetech delay time is determined based on the size of a data
block for each data
file, the number of prefetch data blocks per data file, the number of data
files being sent, and the
allocated prefetch bandwidth in the dedicated channel. In an exemplary
embodiment, all
prefetch data blocks for each data file are sent sequentially and continuously
in the dedicated
channel, one data block per time slot. A person skilled in the art would
recognize that as the
number of prefetch data blocks increases, the longer the prefetch delay time.
Thus, when
determining an optimal number of prefetch data blocks for each data file, an
acceptable prefetch
delay time should be considered.
For example, if data blocks b0 and b 1 of data files M and N are to be
prefetched in the
dedicated channel, these prefetch data blocks can be sent in the following
manner:
MO M 1 NO N 1 MO M 1 NO N 1. . . ..
Assuming a given allocated prefetch bandwidth of PRF BW (Mb/s), in an
exemplary
embodiment, a prefetch delay time can be calculated as follows: Prefetch delay
time = [ data
block size (Mbytes) * number of prefetch data blocks * (number of data files
to be sent + 1 ) * 8
] / P12F-BW (Mb/s)
In an exemplary embodiment, a prefetch cycle time (PRF TIME), which is the
time
required to send a complete round of prefetched data blocks for all data files
being sent, can be
calculated as follows: Prefetch cycle time = [data block size (Mbytes) *
number of prefetch data
blocks * number of data files to be sent * 8 ] / PRF BW (Mb/s).
In one embodiment, to reduce the prefetch delay time, prefetch data blocks of
a new data
file are sent more frequently than prefetch data blocks in an old data file
(e.g., a data file that has
been sent continuously for a predetermined amount of time). Fox example, if M
is an old data
file and N is a new data file, the prefetch data blocks are sent in the
following manner:
NO N 1 NO N 1 MO M 1 NO N 1 NO N 1 MO M 1...
The STB 300, once turned on, continuously receives and updates a program guide
stored
in the local memory 308 of a STB 300. In an exemplary embodiment, the STB 300
displays data
18

CA 02406715 2002-10-10
WO 01/93062 PCT/USO1/17986
- file information including the latest program guide on a TV screen. Data
file information, such
as video file information, may include movielD, movie title, description (in
multiple languages),
category (e.g., action, children), rating (e.g., R, PG13), cable company
policy (e.g., price, length
of free preview), subscription period, movie poster, and movie preview. In an
exemplary
embodiment, data file information is sent via the dedicated channel, such as a
channel reserved
for firmware update, commercials, and/or emergency information. In another
exemplary
embodiment, information is sent in a physical channel shared by other data
streams. In an
exemplary embodiment, while the STB 300 is not playing any data file, the STB
300 is tuned
into the dedicated channel and is ready to receive and update prefetch data
blocks that have not
yet been received.
In an exemplary embodiment, previews are comprised of randomly selected data
blocks
in a data stream of a data file. Thus, a user who selects a preview of a data
file multiple times is
unlikely to view an identical preview. An advantage of randomly composed
previews is that the
DOD system 100 does not need extra bandwidth to broadcast a predetermined
preview program.
Instead, the DOD system 100 randomly selects data blocks in the normal data
stream of a data
file after a user requests to view a preview of that data file. In a preferred
embodiment, some
data blocks cannot become a part of any preview. For example, if a data file
provides a movie,
the data blocks of the second half of the movie should not become a part of a
randomly selected
preview.
A subscribing client can view a list of available data files arranged by
categories
displayed on a television screen. When the client selects one of the available
data files, the STB
300 controls its hardware to tune into a corresponding physical channel and/or
a virtual sub-
channel to start receiving data packets for that data file. The STB 300
examines every data
packet header, decodes data in the data packets, and determines if a received
data packet should
be retained. If the STB 300 determines that a data packet should not be
retained, the data packet
is discarded. Otherwise, the packet data is saved in the local memory 308 for
later retrieval or is
temporarily stored in the buffer memory 309 until it is sent to the decoder
312.
To improve performance efficiency by avoiding frequent read/write into the
local
memory 308, in an exemplary embodiment, the STB 300 uses a "sliding window"
anticipation
technique to lock anticipated data blocks in the memory buffer 309 whenever
possible. Data
blocks are transferred to the decoder 312 directly out of the memory buffer
309 if a hit in an
anticipation window occurs. If an anticipation miss occurs, data blocks are
read from the local
memory 308 into the memory buffer 309 before the data blocks are transferred
to the decoder
312 from the memory buffer 309.
19

CA 02406715 2002-10-10
WO 01/93062 PCT/USO1/17986
In an exemplary embodiment, the STB 300 responds to subscribing client's
commands
via infrared (IR) remote control unit buttons, an IR keyboard, or front panel
pushbuttons,
including buttons to pause, play in slow motion, rewind, zoom and single step.
In an exemplary
embodiment, if a subscribing client does not input any action for a
predetermined period of time
(e.g., scrolling program menu, or selecting a category or movie), a scheduled
commercial is
played automatically. The scheduled commercial is automatically stopped when
the subscribing
client provides an action (e.g., press a button in a remote control unit). In
another exemplary
embodiment, the STB 300 can automatically insert commercials while a video is
being played.
The service provider (e.g., a cable company) can set up a pricing policy that
dictates how
frequently commercials should interrupt the video being played.
In an exemplary embodiment, a cable company using the DOD system 100 can
preset a
price list based on the number of commercial interruptions. In one embodiment,
data blocks for
commercials are continuously broadcasted via a dedicated channel which also
broadcasts a
program guide, an emergency bit, and any firmware update. A user can choose
from such a price
list an acceptable balance between price and commercials. In an exemplary
embodiment, the
DOD system 100 implements the user's selection by maintaining an internal
clock which allows
automatic insertion of commercial data blocks at the predetermined time
intervals based on the
user's selected pricing scheme.
If an emergency information bit is found in a data packet header, the STB 300
pauses any
data receiving operation and controls its hardware to tune into the channel
reserved for receiving
data file information to obtain and decode any emergency information to be
displayed on an
output screen. In an exemplary embodiment, when the STB 300 is idled, it is
tuned to the
channel reserved for receiving data file information and is always ready to
receive and display
any emergency information without delay.
In one embodiment, when the STB 300 appears to be idle (e.g., when a user is
not using
the system), an alarm may go off to alert a user to turn on the output device
to view the
emergency information. In another embodiment, the STB 300 is capable of
distinguishing
emergency information for different regions. For example, the emergency
information for an
unrelated region will not interrupt a data file being played or trigger an
alarm. In contrast, in
existing systems, cable companies have to manually interrupt a broadcast to
send emergency
information.
The foregoing examples illustrate certain exemplary embodiments of the
invention from
which other embodiments, variations, and modifications will be apparent to
those skilled in the
art. The invention should therefore not be limited to the particular
embodiments discussed

CA 02406715 2002-10-10
WO 01/93062 PCT/USO1/17986
above, but rather is defined by the following claims.
21

Dessin représentatif
Une figure unique qui représente un dessin illustrant l'invention.
États administratifs

2024-08-01 : Dans le cadre de la transition vers les Brevets de nouvelle génération (BNG), la base de données sur les brevets canadiens (BDBC) contient désormais un Historique d'événement plus détaillé, qui reproduit le Journal des événements de notre nouvelle solution interne.

Veuillez noter que les événements débutant par « Inactive : » se réfèrent à des événements qui ne sont plus utilisés dans notre nouvelle solution interne.

Pour une meilleure compréhension de l'état de la demande ou brevet qui figure sur cette page, la rubrique Mise en garde , et les descriptions de Brevet , Historique d'événement , Taxes périodiques et Historique des paiements devraient être consultées.

Historique d'événement

Description Date
Inactive : CIB expirée 2022-01-01
Inactive : CIB désactivée 2021-11-13
Inactive : CIB désactivée 2021-11-13
Inactive : CIB désactivée 2021-11-13
Inactive : CIB désactivée 2021-11-13
Inactive : CIB attribuée 2020-03-27
Inactive : CIB attribuée 2020-03-27
Inactive : CIB expirée 2011-01-01
Inactive : CIB expirée 2011-01-01
Inactive : CIB expirée 2011-01-01
Inactive : CIB expirée 2008-01-01
Demande non rétablie avant l'échéance 2006-05-31
Le délai pour l'annulation est expiré 2006-05-31
Inactive : CIB de MCD 2006-03-12
Inactive : CIB de MCD 2006-03-12
Réputée abandonnée - omission de répondre à un avis sur les taxes pour le maintien en état 2005-05-31
Inactive : Grandeur de l'entité changée 2004-06-08
Lettre envoyée 2003-11-20
Inactive : Transfert individuel 2003-10-10
Inactive : Demandeur supprimé 2003-09-10
Inactive : Correspondance - Formalités 2003-03-21
Inactive : CIB attribuée 2003-02-25
Inactive : CIB en 1re position 2003-02-25
Inactive : CIB attribuée 2003-02-25
Inactive : CIB enlevée 2003-02-25
Inactive : CIB attribuée 2003-02-25
Inactive : CIB attribuée 2003-02-25
Inactive : Page couverture publiée 2003-01-28
Inactive : Lettre de courtoisie - Preuve 2003-01-28
Inactive : Notice - Entrée phase nat. - Pas de RE 2003-01-24
Demande reçue - PCT 2002-11-20
Exigences pour l'entrée dans la phase nationale - jugée conforme 2002-10-10
Exigences pour l'entrée dans la phase nationale - jugée conforme 2002-10-10
Demande publiée (accessible au public) 2001-12-06

Historique d'abandonnement

Date d'abandonnement Raison Date de rétablissement
2005-05-31

Taxes périodiques

Le dernier paiement a été reçu le 2004-05-19

Avis : Si le paiement en totalité n'a pas été reçu au plus tard à la date indiquée, une taxe supplémentaire peut être imposée, soit une des taxes suivantes :

  • taxe de rétablissement ;
  • taxe pour paiement en souffrance ; ou
  • taxe additionnelle pour le renversement d'une péremption réputée.

Veuillez vous référer à la page web des taxes sur les brevets de l'OPIC pour voir tous les montants actuels des taxes.

Historique des taxes

Type de taxes Anniversaire Échéance Date payée
Taxe nationale de base - petite 2002-10-10
TM (demande, 2e anniv.) - petite 02 2003-06-02 2003-04-22
Enregistrement d'un document 2003-10-10
TM (demande, 3e anniv.) - générale 03 2004-05-31 2004-05-19
Titulaires au dossier

Les titulaires actuels et antérieures au dossier sont affichés en ordre alphabétique.

Titulaires actuels au dossier
PREDIWAVE, CORP.
Titulaires antérieures au dossier
KHOI HOANG
Les propriétaires antérieurs qui ne figurent pas dans la liste des « Propriétaires au dossier » apparaîtront dans d'autres documents au dossier.
Documents

Pour visionner les fichiers sélectionnés, entrer le code reCAPTCHA :



Pour visualiser une image, cliquer sur un lien dans la colonne description du document. Pour télécharger l'image (les images), cliquer l'une ou plusieurs cases à cocher dans la première colonne et ensuite cliquer sur le bouton "Télécharger sélection en format PDF (archive Zip)" ou le bouton "Télécharger sélection (en un fichier PDF fusionné)".

Liste des documents de brevet publiés et non publiés sur la BDBC .

Si vous avez des difficultés à accéder au contenu, veuillez communiquer avec le Centre de services à la clientèle au 1-866-997-1936, ou envoyer un courriel au Centre de service à la clientèle de l'OPIC.


Description du
Document 
Date
(aaaa-mm-jj) 
Nombre de pages   Taille de l'image (Ko) 
Dessin représentatif 2002-10-10 1 18
Page couverture 2003-01-28 2 49
Description 2002-10-10 21 1 222
Abrégé 2002-10-10 2 69
Revendications 2002-10-10 2 58
Dessins 2002-10-10 5 94
Rappel de taxe de maintien due 2003-02-03 1 106
Avis d'entree dans la phase nationale 2003-01-24 1 189
Demande de preuve ou de transfert manquant 2003-10-14 1 102
Courtoisie - Certificat d'enregistrement (document(s) connexe(s)) 2003-11-20 1 125
Courtoisie - Lettre d'abandon (taxe de maintien en état) 2005-07-26 1 175
Rappel - requête d'examen 2006-02-01 1 117
PCT 2002-10-10 3 109
Correspondance 2003-01-06 1 26
Correspondance 2003-03-21 1 29
Taxes 2003-04-22 1 32
PCT 2002-10-11 3 164
Taxes 2004-05-19 1 32