# US 2003/0084205 A1 · Server for synchronization control, channel driver and method of linking channels

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2003/0084205 A1
- Document ID: US20030084205A1
- Status: Published application
- Kind: A1
- Application number: 10/284,228
- Filed: 2002-10-30
- Published: 2003-05-01
- Earliest claimed: 2001-10-30
- Assignees: NEC Corporation
- Inventors: Kazuaki Nakajima
- Web page: https://patentgrep.com/patent/US20030084205A1

## CPC

- H04N 7/173: with two-way working, e.g. subscriber sending a programme selection signal
- H04H 60/04: Studio equipment; Interconnection of studios
- H04N 7/16: Analogue secrecy systems; Analogue subscription systems
- H04N 21/242: Synchronisation processes, e.g. processing of PCR [Programme Clock References] {(arrangements for synchronising broadcast or distribution via plural systems in broadcast distribution systems H04H20/18)}
- H04N 21/26208: {the scheduling operation being performed under constraints}
- H04N 21/26233: {involving content or additional data duration or size, e.g. length of a movie, size of an executable file}
- H04N 21/26258: {for generating a list of items to be played back in a given order, e.g. playlist, or scheduling item distribution according to such list (retrieval of multimedia data based on playlists G06F16/40)}
- H04N: PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04H: BROADCAST COMMUNICATION (multiplex communication H04J; pictorial communication aspects of broadcast systems H04N)

## Abstract

A server for carrying out synchronization control, includes (a) at least one event receiver for receiving an event, (b) a memory storing therein distribution schedule information including a plurality of schedule data therein, each of the schedule data including (b1) a timing at which a channel driver controls a media server, (b2) a content of how the channel driver controls the media driver, and (b3) a timing type indicating which one of a time and the event the timing is defined by, and (c) a controller which detects whether a timing is established for each of the schedule data included in the distribution schedule information, and transmits a signal to the channel driver, the signal being indicative of a control associated with the established timing.

## Claims

### Claim 1

A server for carrying out synchronization control, comprising:
(a) at least one event receiver for receiving an event;
(b) a memory storing therein distribution schedule information including a plurality of schedule data therein, each of said schedule data including (b1) a timing at which a channel driver controls a media server, (b2) a content of how said channel driver controls said media driver, and (b3) a timing type indicating which one of a time and said event said timing is defined by; and
(c) a controller which detects whether a timing is established for each of said schedule data included in said distribution schedule information, and transmits a signal to said channel driver, said signal being indicative of a control associated with the established timing.

### Claim 2 (depends on 1)

The server as set forth in claim 1, wherein each of said schedule data includes:
at least one timing-describing section including data indicative of a timing a which said channel driver controls said media server; and
at least one command-describing section including data indicating said content of how said channel driver controls said media driver,
said timing-describing section including:
a timing type section indicative of which one of a time and an event a timing is defined by; and
a timing data section including, if a timing is defined by a time, the time, or if a timing is defined by an event, conditions in accordance with which said timing is established.

### Claim 3 (depends on 2)

The server as set forth in claim 2, wherein said controller includes:
(c1) a first timing-controller which detects whether a timing is established in said timing-describing section indicating that a timing is defined by a time;
(c2) a second timing-controller which detects whether a timing is established in said timing-describing section indicating that a timing is defined by an event; and
(c3) a distribution controller which produces a signal in accordance with a command-describing section associated with a timing-describing section indicating that a timing has been established and which is stored in a queue, and transmits said signal to said channel driver through a network.

### Claim 4 (depends on 3)

The server as set forth in claim 3, wherein said timing-describing section includes an operation-point item indicative of a start of a schedule, an end of a schedule or a timing at which an action is to be carried out,
said command-describing section includes an action-point item indicative of a start of a schedule, an end of a schedule or a timing at which an action is to be carried out, and
said controller processes all of command-describing sections including said action-point item having the same content as that of said operation-point item of said timing-describing section indicating that a timing has been established, among command-describing sections included in schedule data, when a timing is established in a timing-describing section in the schedule data.

### Claim 5 (depends on 4)

The server as set forth in claim 4, wherein said timing-describing section includes an item for determining a first delay time by which establishment of a timing is delayed.

### Claim 6 (depends on 4)

The server as set forth in claim 4, wherein said command-describing section includes an item for determining a second delay time by which production of said signal is delayed.

### Claim 7 (depends on 6)

The server as set forth in claim 6, wherein said controller (a) adds said second delay time to a time at which a timing is established, (b) applies a first time resulted from the addition to a command-describing section associated with a timing-describing section indicating-that a timing has been established, and (c) stores said command-describing section in said queue, and
said distribution controller transmits a signal t said channel driver at a certain time before said first time having been applied to said command-describing section, said signal being indicative of said first time.

### Claim 8 (depends on 7)

The server as set forth in claim 7, wherein said distribution controller applies an identifier to said signal for identifying said signal only, and, when instructed of termination, interruption or restart of schedule, transmits a command indicative of termination, interruption or restart of said signal to said channel driver by designating said identifier of said signal.

### Claim 9 (depends on 2)

The server as set forth in claim 2, wherein said conditions are comprised of an equation for evaluating variables which are one of factors by which a timing is established, said equation including variables which are varied by a predetermined equation for operating variables, when said event occurs.

### Claim 10 (depends on 9)

The server as set forth in claim 9, wherein said memory stores (a) variable data including a title of said variables, an initial value, and a variation value, and (b) event-processing data including an identifier of an event and an equation for operating variables, and
said event receiver carries out said equation for operating variable in said event-processing data having an identifier identical with an identifier of a received event, to thereby update said variation value in said variable data.

### Claim 11 (depends on 9)

The server as set forth in claim 9, wherein said memory stores variable data including a title of said variables, an initial value, and a variation value,
said distribution schedule information includes schedule data having a command-describing section describing an equation for operating variables to update a variation value of said variable data, and
said server further comprising a command-processor which carries out a command-describing section describing said equation for operating variables, in response to establishment of a timing in a timing-describing section associated with said command-describing section.

### Claim 12 (depends on 2)

The server as set forth in claim 2, wherein said signal indicates a time at which said channel driver has to carry out a control, and abstract data identifying said control, and
said channel driver carries out an application identified by said abstract data at said time for controlling said media server.

### Claim 13 (depends on 12)

The server as set forth in claim 12, wherein said abstract data is comprised of a signal identifier and an argument.

### Claim 14 (depends on 2)

The server as set forth in claim 2, wherein said event receiver receives at least one of an identifier of an event which occurred at a user interface and an identifier of an event which occurred at an external system.

### Claim 15 (depends on 2)

The server as set forth in claim 2, wherein said event receiver receives an identifier of an event which occurred at said media server.

### Claim 16

A server for carrying out synchronization control, comprising:
(a) at least one event receiver for receiving an event;
(b) a memory storing therein distribution schedule information including a plurality of schedule data therein, each of said schedule data including (b1) a timing at which a channel driver controls a media server, (b2) a content of how said channel driver controls said media driver, and (b3) a timing type indicating which one of a time, said event, and establishment of a timing in other schedules said timing is defined by; and
(c) a controller which detects whether a timing is established for each of said schedule data included in said distribution schedule information, and transmits a signal to said channel driver, said signal being indicative of a control associated with the established timing.

### Claim 17 (depends on 16)

The server as set forth in claim 16, wherein each of said schedule data includes:
at least one timing-describing section including data indicative of a timing a which said channel driver controls said media server; and
at least one command-describing section including data indicating said content of how said channel driver controls said media driver,
said timing-describing section including:
a timing type section indicative of which one of a time, an event, and establishment of a timing in other timing-describing section a timing is defined by; and
a timing data section including, if a timing is defined by a time, the time, if a timing is defined by an event, conditions in accordance with which said timing is established, or if a timing is defined by establishment of a timing in other timing-describing section, data identifying said other timing-describing section.

### Claim 18 (depends on 17)

The server as set forth in claim 17, wherein said controller includes:
(c1) a first timing-controller which detects whether a timing is established in said timing-describing section indicating that a timing is defined by a time;
(c2) a second timing-controller which detects whether a timing is established in said timing-describing section indicating that a timing is defined by an event;
(c3) a third timing-controller which detects whether a timing is established in said timing-describing section indicating that a timing is defined by establishment of a timing in other timing-describing section; and
(c4) a distribution controller which produces a signal in accordance with a command-describing section associated with a timing-describing section indicating that a timing has been established and which is stored in a queue, and transmits said signal to said channel driver through a network.

### Claim 19 (depends on 18)

The server as set forth in claim 18, wherein said timing-describing section includes an operation-point item indicative of a start of a schedule, an end of a schedule or a timing at which an action is to be carried out,
said command-describing section includes an action-point item indicative of a start of a schedule, an end of a schedule or a timing at which an action is to be carried out,
said controller processes all of command-describing sections including said action-point item having the same content as that of said operation-point item of said timing-describing section indicating that a timing has been established, among command-describing sections included in schedule data, when a timing is established in a timing-describing section in the schedule data.

### Claim 20 (depends on 19)

The server as set forth in claim 19, wherein said timing-describing section includes an item for determining a first delay time by which establishment of a timing is delayed.

### Claim 21 (depends on 19)

The server as set forth in claim 19, wherein said command-describing section includes an item for determining a second delay time by which production of said signal is delayed.

### Claim 22 (depends on 21)

The server as set forth in claim 21, wherein said controller (a) adds said second delay time to a time at which a timing is established, (b) applies a first time resulted from the addition to a command-describing section associated with a timing-describing section indicating that a timing has been established, and (c) stores said command-describing section in said queue, and
said distribution controller transmits a signal t said channel driver at a certain time before said first time having been applied to said command-describing section, said signal being indicative of said first time.

### Claim 23 (depends on 22)

The server as set forth in claim 22, wherein said distribution controller applies an identifier to said signal for identifying said signal only, and, when instructed of termination, interruption or restart of schedule, transmits a command indicative of termination, interruption or restart of said signal to said channel driver by designating said identifier of said signal.

### Claim 24 (depends on 17)

The server as set forth in claim 17, wherein said conditions are comprised of an equation for evaluating variables which are one of factors by which a timing is established, said equation including variables which are varied by a predetermined equation for operating variables, when said event occurs.

### Claim 25 (depends on 24)

The server as set forth in claim 24, wherein said memory stores (a) variable data including a title of said variables, an initial value, and a value after varied, and (b) event-processing data including an identifier of an event and an equation for operating variables, and
said event receiver carries out said equation for operating variable in said event-processing data having an identifier identical with an identifier of a received event, to thereby update said value after varied in said variable data.

### Claim 26 (depends on 24)

The server as set forth in claim 24, wherein said memory stores variable data including a title of said variables, an initial value, and a variation value,
said distribution schedule information includes schedule data having a command-describing section describing an equation for operating variables to update a variation value of said variable data, and
said server further comprising a command-processor carries out a command-describing section describing said equation for operating variables, in response to establishment of a timing in a timing-describing section associated with said command-describing section.

### Claim 27 (depends on 17)

The server as set forth in claim 17, wherein said signal indicates a time at which said channel driver has to carry out a control, and abstract data identifying said control, and
said channel driver carries out an application identified by said abstract data at said time for controlling said media server.

### Claim 28 (depends on 27)

The server as set forth in claim 27, wherein said abstract data is comprised of a signal identifier and an argument.

### Claim 29 (depends on 17)

The server as set forth in claim 17, wherein said event receiver receives at least one of an identifier of an event which occurred at a user interface and an identifier of an event which occurred at an external system.

### Claim 30 (depends on 17)

The server as set forth in claim 17, wherein said event receiver receives an identifier of an event which occurred at said media server.

### Claim 31

A channel driver comprising:
(a) a memory storing a signal transmitted from a synchronization control server through a network, said synchronization control server controlling an operation of each of a plurality of media servers which distribute contents in accordance with distribution schedule information including schedule data defining a control timing with a time or an event, said signal including a control carried out by said media servers, a time at which said media servers carry out said control, and identifiers identifying said media servers; and
(b) a driver which detects a signal indicating that it is time to start said control, and causes a media server controller to carry out a control in accordance with the detected signal.

### Claim 32 (depends on 31)

The channel driver as set forth in claim 31, wherein said driver, on receipt of a command of terminating or interrupting a signal identified with a designated identifier, from said synchronization control server through a network, terminates or interrupts a signal identified with said designated identifier.

### Claim 33 (depends on 32)

The channel driver as set forth in claim 32, wherein said driver, on receipt of a command of restarting a signal identified with an identifier and indicative of a delay time from said synchronization control server through a network after receiving a command of interrupting said signal from said synchronization control server, releases interruption of said signal with delaying a time at which said signal is to be carried out, by said delay time.

### Claim 34 (depends on 31)

The channel driver as set forth in claim 31, further comprising a communication unit which transmits an event identifier identifying an event which occurred in said media servers, to said synchronization control server through a network.

### Claim 35

A program for causing a computer to act as a server for carrying out synchronization control, said server comprising:
(a) at least one event receiver for receiving an event;
(b) a memory storing therein distribution schedule information including a plurality of schedule data therein, each of said schedule data including (b1) a timing at which a channel driver controls a media server, (b2) a content of how said channel driver controls said media driver, and (b3) a timing type indicating which one of a time and said event said timing is defined by; and
(c) a controller which detects whether a timing is established for each of said schedule data included in said distribution schedule information, and transmits a signal to said channel driver, said signal being indicative of a control associated with the established timing.

### Claim 36 (depends on 35)

The program as set forth in claim 35, wherein each of said schedule data includes:
at least one timing-describing section including data indicative of a timing a which said channel driver controls said media server; and
at least one command-describing section including data indicating said content of how said channel driver controls said media driver,
said timing-describing section including:
a timing type section indicative of which one of a time and an event a timing is defined by; and
a timing data section including, if a timing is defined by a time, the time, or if a timing is defined by an event, conditions in accordance with which said timing is established.

### Claim 37 (depends on 36)

The program as set forth in claim 36, wherein said controller includes:
(c1) a first timing-controller which detects whether a timing is established in said timing-describing section indicating that a timing is defined by a time;
(c2) a second timing-controller which detects whether a timing is established in said timing-describing section indicating that a timing is defined by an event; and
(c3) a distribution controller which produces a signal in accordance with a command-describing section associated with a timing-describing section indicating that a timing has been established and which is stored in a queue, and transmits said signal to said channel driver through a network.

### Claim 38 (depends on 37)

The program as set forth in claim 37, wherein said timing-describing section includes an operation-point item indicative of a start of a schedule, an end of a schedule or a timing at which an action is to be carried out,
said command-describing section includes an action-point item indicative of a start of a schedule, an end of a schedule or a timing at which an action is to be carried out,
said controller processes all of command-describing sections including said action-point item having the same content as that of said operation-point item of said timing-describing section indicating that a timing has been established, among command-describing sections included in schedule data, when a timing is established in a timing-describing section in the schedule data.

### Claim 39 (depends on 38)

The program as set forth in claim 38, wherein said timing-describing section includes an item for determining a first delay time by which establishment of a timing is delayed.

### Claim 40 (depends on 38)

The program as set forth in claim 38, wherein said command-describing section includes an item for determining a second delay time by which production of said signal is delayed.

### Claim 41 (depends on 40)

The program as set forth in claim 40, wherein said controller (a) adds said second delay time to a time at which a timing is established, (b) applies a first time resulted from the addition to a command-describing section associated with a timing-describing section indicating that a timing has been established, and (c) stores said command-describing section in said queue, and
said distribution controller transmits a signal t said channel driver at a certain time before said first time having been applied to said command-describing section, said signal being indicative of said first time.

### Claim 42 (depends on 41)

The program as set forth in claim 41, wherein said distribution controller applies an identifier to said signal for identifying said signal only, and, when instructed of termination, interruption or restart of schedule, transmits a command indicative of termination, interruption or restart of said signal to said channel driver by designating said identifier of said signal.

### Claim 43 (depends on 36)

The program as set forth in claim 36, wherein said conditions are comprised of an equation for evaluating variables which are one of factors by which a timing is established, said equation including variables which are varied by a predetermined equation for operating variables, when said event occurs.

### Claim 44 (depends on 43)

The program as set forth in claim 43, wherein said memory stores (a) variable data including a title of said variables, an initial value, and a variation value, and (b) event-processing data including an identifier of an event and an equation for operating variables, and
said event receiver carries out said equation for operating variable in said event-processing data having an identifier identical with an identifier of a received event, to thereby update said variation value in said variable data.

### Claim 45 (depends on 43)

The program as set forth in claim 43, wherein said memory stores variable data including a title of said variables, an initial value, and a variation value,
said distribution schedule information includes schedule data having a command-describing section describing an equation for operating variables to update a variation value of said variable data, and
said server further comprising a command-processor carries out a command-describing section describing said equation for operating variables, in response to establishment of a timing in a timing-describing section associated with said command-describing section.

### Claim 46 (depends on 36)

The program as set forth in claim 36, wherein said signal indicates a time at which said channel driver has to carry out a control, and abstract data identifying said control, and
said channel driver carries out an application identified by said abstract data at said time for controlling said media server.

### Claim 47 (depends on 46)

The program as set forth in claim 46, wherein said abstract data is comprised of a signal identifier and an argument.

### Claim 48 (depends on 36)

The program as set forth in claim 36, wherein said event receiver receives at least one of an identifier of an event which occurred at a user interface and an identifier of an event which occurred at an external system.

### Claim 49 (depends on 36)

The program as set forth in claim 36, wherein said event receiver receives an identifier of an event which occurred at said media server.

### Claim 50

A program for causing a computer to act as a server for carrying out synchronization control, said server comprising:
(a) at least one event receiver for receiving an event;
(b) a memory storing therein distribution schedule information including a plurality of schedule data therein, each of said schedule data including (b1) a timing at which a channel driver controls a media server, (b2) a content of how said channel driver controls said media driver, and (b3) a timing type indicating which one of a time, said event, and establishment of a timing in other schedules said timing is defined by; and
(c) a controller which detects whether a timing is established for each of said schedule data included in said distribution schedule information, and transmits a signal to said channel driver, said signal being indicative of a control associated with the established timing.

### Claim 51 (depends on 50)

The program as set forth in claim 50, wherein each of said schedule data includes:
at least one timing-describing section including data indicative of a timing a which said channel driver controls said media server; and
at least one command-describing section including data indicating said content of how said channel driver controls said media driver,
said timing-describing section including:
a timing type section indicative of which one of a time, an event, and establishment of a timing in other timing-describing section a timing is defined by; and
a timing data section including, if a timing is defined by a time, the time, if a timing is defined by an event, conditions in accordance with which said timing is established, or if a timing is defined by establishment of a timing in other timing-describing section, data identifying said other timing-describing section.

### Claim 52 (depends on 51)

The program as set forth in claim 51, wherein said controller includes:
(c1) a first timing-controller which detects whether a timing is established in said timing-describing section indicating that a timing is defined by a time;
(c2) a second timing-controller which detects whether a timing is established in said timing-describing section indicating that a timing is defined by an event;
(c3) a third timing-controller which detects whether a timing is established in said timing-describing section indicating that a timing is defined by establishment of a timing in other timing-describing section; and
(c4) a distribution controller which produces a signal in accordance with a command-describing section associated with a timing-describing section indicating that a timing has been established and which is stored in a queue, and transmits said signal to said channel driver through a network.

### Claim 53 (depends on 52)

The program as set forth in claim 52, wherein said timing-describing section includes an operation-point item indicative of a start of a schedule, an end of a schedule or a timing at which an action is to be carried out,
said command-describing section includes an action-point item indicative of a start of a schedule, an end of a schedule or a timing at which an action is to be carried out,
said controller processes all of command-describing sections including said action-point item having the same content as that of said operation-point item of said timing-describing section indicating that a timing has been established, among command-describing sections included in schedule data, when a timing is established in a timing-describing section in the schedule data.

### Claim 54 (depends on 53)

The program as set forth in claim 53, wherein said timing-describing section includes an item for determining a first delay time by which establishment of a timing is delayed.

### Claim 55 (depends on 53)

The program as set forth in claim 53, wherein said command-describing section includes an item for determining a second delay time by which production of said signal is delayed.

### Claim 56 (depends on 55)

The program as set forth in claim 55, wherein said controller (a) adds said second delay time to a time at which a timing is established, (b) applies a first time resulted from the addition to a command-describing section associated with a timing-describing section indicating that a timing has been established, and (c) stores said command-describing section in said queue, and
said distribution controller transmits a signal t said channel driver at a certain time before said first time having been applied to said command-describing section, said signal being indicative of said first time.

### Claim 57 (depends on 56)

The program as set forth in claim 56, wherein said distribution controller applies an identifier to said signal for identifying said signal only, and, when instructed of termination, interruption or restart of schedule, transmits a command indicative of termination, interruption or restart of said signal to said channel driver by designating said identifier of said signal.

### Claim 58 (depends on 51)

The program as set forth in claim 51, wherein said conditions are comprised of an equation for evaluating variables which are one of factors by which a timing is established, said equation including variables which are varied by a predetermined equation for operating variables, when said event occurs.

### Claim 59 (depends on 58)

The program as set forth in claim 58, wherein said memory stores (a) variable data including a title of said variables, an initial value, and a value after varied, and (b) event-processing data including an identifier of an event and an equation for operating variables, and
said event receiver carries out said equation for operating variable in said event-processing data having an identifier identical with an identifier of a received event, to thereby update said value after varied in said variable data.

### Claim 60 (depends on 58)

The program as set forth in claim 58, wherein said memory stores variable data including a title of said variables, an initial value, and a variation value,
said distribution schedule information includes schedule data having a command-describing section describing an equation for operating variables to update a variation value of said variable data, and
said server further comprising a command-processor carries out a command-describing section describing said equation for operating variables, in response to establishment of a timing in a timing-describing section associated with said command-describing section.

### Claim 61 (depends on 51)

The program as set forth in claim 51, wherein said signal indicates a time at which said channel driver has to carry out a control, and abstract data identifying said control, and
said channel driver carries out an application identified by said abstract data at said time for controlling said media server.

### Claim 62 (depends on 61)

The program as set forth in claim 61, wherein said abstract data is comprised of a signal identifier and an argument.

### Claim 63 (depends on 51)

The program as set forth in claim 51, wherein said event receiver receives at least one of an identifier of an event which occurred at a user interface and an identifier of an event which occurred at an external system.

### Claim 64 (depends on 51)

The program as set forth in claim 51, wherein said event receiver receives an identifier of an event which occurred at said media server.

### Claim 65

A method of linking channels in distribution of contents from a plurality of media servers to clients through separate channels, comprising the steps of:
(a) detecting whether a timing is established in each of timing types in each of a plurality of schedule data included in distribution schedule information, each of said schedule data including (a1) a timing at which each of said media servers is controlled, (a2) a content of how each of said media drivers is controlled, (a3) a channel to be controlled, and (a4) a timing type indicating which one of a time and an event said timing is defined by; and
(b) transmitting a signal indicative of a control associated with an established timing, to a channel driver which controls a media server associated with said channel to be controlled.

### Claim 66

A method of linking channels in distribution of contents from a plurality of media servers to clients through separate channels, comprising the steps of:
(a) detecting whether a timing is established in each of timing types in each of a plurality of schedule data included in distribution schedule information, each of said schedule data including (a1) a timing at which each of said media servers is controlled, (a2) a content of how each of said media drivers is controlled, (a3) a channel to be controlled, and (a4) a timing type indicating which one of a time, an event, and establishment of a timing in other schedules said timing is defined by; and
(b) transmitting a signal indicative of a control associated with an established timing, to a channel driver which controls a media server associated with said channel to be controlled.
