Synchronization of bulk data transfers to end node devices in a multimedia network

Abstract

Synchronization of bulk data transfers to end node devices in a multimedia network involves sending an initial schedule message prior to broadcast or multicast of a content file. The content file could be a promotion or other file that must be efficiently sent to a large number of end node devices, such as television set top boxes. The schedule message contains at least a data transmission time for the content file so that an end node device is aware of when to listen for the later bulk data transmission of the content file. The schedule message may contain other parameters such as promotion identification, message duration, frequency, multicast address and UDP port.

Description

BACKGROUND OF THE INVENTION

[0002] At the present time, most data network devices located in the residences include some type of personal computer. Typically, these personal computers are used to connect to Internet Service Providers over dial-up connections to execute application programs such as email clients and Web browsers that utilize the global Internet to access text and graphic content. Increasingly, the demand is for multimedia content, including audio and video, to be delivered over such networks. However, the backbone architectures of purely data networks, especially those designed for use with the telephone network, were not originally designed to handle such high data rates.

[0003] The trend is towards a more ubiquitous model where the network devices in the home will be embedded systems designed for a particular function or purpose. This has already occurred to some degree. Today, for example, cable television (CATV) network set-top boxes typically have limited data communication capabilities. The main function of the data devices is to handle channel access between residential users and a head end or server on the cable TV network.

[0004] However, it is estimated that the worldwide market for Internet appliances such as digital set-top boxes and Web-connected terminals will reach $17.8 billion in 2004, and millions of such digital set-top boxes have already been deployed. Increasingly, advertisers and content providers view the cable set-top as the first platform of choice for widespread delivery of a suite of intelligent content management and distribution services.

[0005] In the future, the functionality offered by these set-top boxes or other embedded platforms, such as a game system, will be expanded. For example, they may offer Internet browsing capabilities and e-commerce serving capabilities. Moreover, it is anticipated that common-household appliances will also have network functionality, in which they will be attached to the network to automate various tasks.

SUMMARY OF THE INVENTION

[0006] Because of the extremely large numbers of network devices in such networks, efficient distribution and delivery of promotions and other digital content remains a challenge. Where the personal computer can be updated with new network drivers as the network evolves, embedded client systems remain relatively static. In addition, such networks may have hundreds of thousands, if not millions, of network devices to manage. It is evident that standard data Open Systems Inerconnection (OSI) layered network protocols, which were optimized for peer to peer communication, are not an entirely acceptable arrangement.

[0007] Consider that the digital set top box provides certain interesting functionality, such as the ability to store certain amounts of data. The set top box can thus be designed to store a multimedia computer file which represents a digitized version of a promotion. However, such a network may have hundreds of thousands, if not millions of set top boxes, to which delivery of promotions must be individually coordinated. If such a data network were built using only the standard protocols such as direct TCP/IP messaging from a central promotion server to the set top boxes, the sheer volume of message traffic needed to route the promotions to the intended destinations would quickly overload the central data server.

[0008] The present invention involves a technique for synchronization of bulk data transfers to end node devices in a multimedia network in which an initial schedule message is sent prior to broadcast or multicast of a content file. The content file could be a promotion or other file that must be efficiently sent to a large number of end node devices, such as television set top boxes. The schedule message contains at least a data transmission time for the content file so that an end node device is aware of when to listen for the later bulk data transmission of the content file. The schedule message may contain other parameters such as promotion identification, message duration, frequency, multicast address and UDP port.

BRIEF DESCRIPTION OF THE DRAWINGS

[0009] FIG. 1 is a diagram illustrating a multimedia content delivery system for distributing content such as targeted promotions according to one embodiment of the present invention.

[0010] FIG. 2 is a diagram of a set top box/video display system displaying active promotions according to one embodiment.

[0011] FIG. 3A is a diagram illustrating a set of packages according to one embodiment.

[0012] FIG. 3B is a table containing typical data transmission parameters specified by a package according to one embodiment.

[0013] FIG. 3C is a table containing parameters specified by a transmission group according to one embodiment.

[0014] FIG. 3D is a flow diagram illustrating a process for packaging promotions for transmission groups according to one embodiment.

[0015] FIG. 3E is a diagram illustrating one way in which devices may be mapped from their a promotion group into transmission groups.

[0016] FIG. 4A is a time line diagram illustrating a promotion transmission lead-time with its constituent lead-times according to one embodiment.

[0017] FIG. 4B is a time line diagram illustrating a schedule transmission lead-time according to one embodiment.

[0018] FIG. 5 is a state line diagram illustrating a process for synchronizing the delivery of promotions to end node devices according to one embodiment.

[0019] FIG. 6A is a table identifying the parameters of a local moniker according to one embodiment.

[0020] FIG. 6B is a table identifying the parameters of a remote moniker according to one embodiment.

[0021] FIG. 7 is a flow diagram illustrating a process for generating transmission schedules for devices according to one embodiment.

[0022] FIG. 8 is a flow diagram illustrating a process of generating transmission requests according to one embodiment.

[0023] FIG. 9 is a table illustrating the parameters of a transmission request according to one embodiment.

[0024] FIG. 10 is a diagram illustrating the organization of tables of record within the database according to one embodiment.

[0025] The foregoing and other objects, features and advantages of the invention will be apparent from the following more particular description of preferred embodiments of the invention, as illustrated in the accompanying drawings in which like reference characters refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the invention.

DETAILED DESCRIPTION OF A PREFERRED EMBODIMENT

[0026] Turning attention now to the drawings, FIG. 1 illustrates a multimedia content delivery system for distributing content such as targeted promotions according to one embodiment of the present invention. Embodiments of the multimedia content delivery system allow advertisers and service providers the ability to effectively utilize a multimedia network for targeting promotions or other content at consumers through network devices. In particular, the system facilitates the targeting of promotions in varying degrees of granularity from individuals to entire market segments. The system includes a large number of set top boxes or network devices 10 connected to respective video displays 20, such as televisions.

[0027] Promotions 30 typically include promotional content that may be presented in various multimedia formats including standard audio visual clips, but also computer graphics, icons, or Hypertext Markup Language (HTML) content. Promotions are used to advertise goods and services, promote events, or present other commercial or non-commercial information. One or more promotions 30 may be simultaneously active within the video displays 20 and may be displayed in different ways. For example, in FIG. 2, promotions 30 are presented on electronic program guides, channel information bars 40, or overlaying video broadcast programming. Some active promotions that may be displayed on digital set top boxes allow user interaction such as linking to e-commerce web-sites via hyperlink connections or direct communication to a promotion server subsystem to obtain additional software, such as device drivers, video games, or other application software.

[0028] Referring back to FIG. 1, the multimedia content delivery system also includes a promotion server subsystem 200 located at a data center and a promotion agent subsystem 300 embedded within each of the network devices. The promotion server subsystem 200 and the promotion agent subsystems 300 communicate with each other through a combination of application-level messaging and serialized bulk data transmissions.

[0029] The promotion server subsystem 200 periodically collects viewer usage data from the promotion agent subsystem 300 of each of the multimedia content viewing devices to generate viewership profiles. In television networks, the data collected by the promotion server subsystem 200 may include tuner data (i.e., a history of channels watched) and responses to past promotions. This history is kept on a relatively fine time scale, such as five seconds. In this way, it can be determined how long a particular promotion was deployed, or even which portions of a promotion or video program were viewed.

[0030] Regarding promotion delivery, the promotion server subsystem 200 includes a database server 210, a promotion manager server 220, one or more bulk data servers 230, a promotion manager client 240, a life-cycle manager server 240, and a bank of routers 250-1, 250-2, . . . , 250-n. These components are typically located at a central location in the multimedia network at a data center, at a head end, or divided between the two depending on the density and population of devices. It should be understood that these components may share physical platforms or be distributed across multiple machines located at different places in the network. For scalability reasons, a promotion scheduling process in the promotion manager server 220 may be separated from a function which is responsible for delivering promotion packages to the network devices 10. The delivery function may be instantiated on multiple machines, for example, to provide better scalability, such as having one bulk data server per head end in the network. The life cycle manager 240 may also be instantiated separately for each router 250.

[0031] The routers 250 communicate with the network devices 10 through a data network 75 which may itself include a further hierarchy of routers and bulk servers (not shown in FIG. 1). Ultimately, each of the network devices is connected to the network 75 through a head end location 50. In a typical cable television network, there may be many thousands of network devices connected to a particular head end, and there may be many thousands of head ends 50.

[0032] To determine how to deliver targeted promotions to the network devices, the life-cycle manager server 240 of the promotion server subsystem 200 first generates viewership profiles for each of the multimedia content viewing devices from the collected data using a variety of statistical models. The viewership profiles are then used to associate groups of network devices with a given target promotion.

[0033] Promotion groups are collections of multimedia content viewing devices whose individual viewership profiles match membership criteria describing a particular demographic or viewership history. For example, a promotion group may be demographically based, (i.e., married women in their 30's with more than one school age child and a household income of at least $100,0000), or based on viewership history, (i.e., tends to watch the Golf Channel on Sunday afternoon). Therefore, the promotion server subsystem 200 is adaptable to changes in viewer usage or viewership patterns by making adjustments to promotion groups. Viewership profiles and promotion groups are described in more detail in U.S. patent application Attorney Docket Number 2657.2003-000, entitled “Using Viewership Profiles to Target Advertisements” filed on the same date herewith.

[0034] Promotions are then scheduled for delivery to specific promotion groups. A promotion is scheduled for delivery to a promotion group by an advertiser or service provider entering a scheduling request for a promotion such as via a promotion manager interface client 225. As promotions are scheduled, the promotion manager server 220 adds or removes promotion groups and/or scheduling information to promotions. This causes the creation or modification promotion delivery packages via stored data functions or procedures in the database 210. Later, the package information is read from the database 210 and used to create customized transmission schedules that specify when and how each of the network devices 10 is to receive it.

[0035] The promotion agent subsystem 300 embedded in each of the network devices 10 includes a promotion agent 310 and a bulk data agent 320. Upon receipt of the transmission schedule messages, the promotion agent 310 processes each schedule entry forwarding promotion download requests to the bulk data agent 320 to receive each promotion identified in the transmission schedule. The bulk data agent 320 handles the reception of the promotions from the scheduled data transmission as specified in the promotion download requests. For example, in one embodiment, the bulk data agent 320 tunes into a multicast data transmission stream at a specified time and channel or network address specified in the transmission schedule.

[0036] To initiate a transmission of promotion packages, the promotion manager server 220 extracts a set of promotion packages from the database 210 and converts each into a transmission request that is sent to one or more of the bulk data servers 230. The bulk data server 230 fetches the promotions from the database 210 that are identified in the transmission request message, and transmits them via multicast or broadcast transmission. The decision to broadcast or multicasts depends on which is supported between the head end and the capabilities of the end node devices.

[0037] Once the promotions have been successfully delivered, the promotions are activated at the network viewing devices as specified in promotion control data of the transmission schedules. Promotion activation may be event, time, or channel driven.

[0038] Packaging Promotions for Transmission Groups

[0039] Promotions may be scheduled for promotion groups that include diverse types of end node devices. For example, a promotion group may include devices that are functionally different, such as television set top boxes and Internet video phones. Even functionally similar types of devices (e.g., set top boxes) may differ with respect to certain physical and functional device attributes. Such attributes may include data storage capacity and the ability to receive multicast transmissions using standard data protocols, such as Transmission Control Protocol or Universal Data Protocol over Internet Protocol (TCP/IP or UDP/IP) networks. Device attributes have a direct effect on the manner in which promotions and other content are actually delivered to devices of targeted promotion groups. For example, devices with less data storage capacity are not able to cache as many promotions as devices with more storage capacity. The promotion server subsystem 200 adapts the delivery of promotions to the attributes of different device types within a promotion group through the use of packages.

[0040] FIG. 3A is a diagram illustrating a set of packages according to one embodiment. A package is a data object 600 containing a set of promotions 610 and data transmission parameters 620 that specify the time and/or manner of delivery for a set of promotions to a particular transmission group. Transmission groups are sets of end node devices sharing common device attributes, such as storage and resource limitations. For example, set top boxes of a particular model number may be considered to be part of the same transmission group. Devices may be initially assigned to a transmission group manually, or automatically, during an automated registration process in which device attributes are discovered.

[0041] FIG. 3B is a table containing typical data transmission parameters specified by a package according to one embodiment. Such parameters include data rates, data transmission times, and routing addresses, such multicast or broadcast port addresses. Furthermore, a package includes a TRANSMISSION_GROUP_ID parameter that identifies the transmission group which is to receive the package. FIG. 3C is a table containing parameters specified by a transmission group according to one embodiment. The parameters of a transmission group add to or affect the data transmission parameters of the package. For example, the size of a package is determined by the maximum package size parameter of a transmission group.

[0042] When a promotion is scheduled, the scheduling process determines TRANSMISSION_GROUP_ID by mapping promotion group identifiers into transmission group identifiers. In the preferred embodiment, all of the promotions within a single package share a common transmission group identifier. When a promotion is associated with more than one transmission group, a separate package is created in the system for each group.

[0043] FIG. 3D is a flow diagram illustrating a process for packaging promotions for transmission groups according to one embodiment.

[0044] In step 410, a promotion is scheduled for delivery to one or more promotion groups where each of the promotion groups includes a set of end node devices. In particular, an advertiser or service provider enters a promotion schedule request into the promotion server subsystem 200 through the promotion manager client 225. In one embodiment, the promotion schedule request identifies a promotion, a recipient of the promotion (i.e. promotion group), as well as promotion scheduling information (e.g., channel time slot information containing start times, trigger events, or other such criteria for promotion activation).

[0045] The promotion manager server 220, in turn, places database function calls that add the promotion, recipients, and scheduling information to the database 210. As an indirect result of the promotion manager server 220 adding/removing recipients to promotions and adding/removing scheduling information for promotions, packages are created or modified. According to one embodiment, the creation and modification of packages is handled by a set of stored database procedures internal to the database 210 starting at step 420.

[0046] In step 420, the set of end node devices included in the promotion group is subdivided into one or more transmission groups. According to one embodiment, the promotion group is resolved into transmission groups by an internal database query resulting in a list of unique transmission group identifiers corresponding to the various types of end node devices within the promotion group. FIG. 3E is a diagram illustrating one way in which devices may be mapped from their promotion group into transmission groups. Each of the resulting transmission groups 510 and 520 includes a mutually exclusive set of devices from the promotion group. Packages then must be created and/or appended to for each of the transmission groups which is to receive the promotion.

[0047] Referring back to FIG. 3D, a determination is made whether or not a package has been created for a transmission group in step 430. According to one embodiment, this involves an internal database query for a package indexed by the unique identifier for the transmission group.

[0048] If there is no package associated with a transmission group, a new package is created for the transmission group in step 440. The creation of a package involves creating a new package record within the database 210. The data transmission parameters of the package record illustrated in FIG. 3B are adapted to the device attributes of the transmission group. The record is maintained in the database 210 within a table of other package records.

[0049] In more detail regarding adapting packages to transmission groups, one attribute of network devices of the same transmission group may include data storage capacity. The data storage capacity may be an expected amount or percentage of available cache memory in the set top box. Alternatively, the data storage capacity may be an expected amount or percentage of data storage dedicated solely for caching promotions. Network providers in cable networks typically restrict data storage available for dedicated functionality, such as promotion caching.

[0050] Accordingly, the package may be adapted with a maximum package size less than or equal to the data storage capacity available for the specific end node devices which are members of the present transmission group. The maximum package size, therefore, limits the number and size of promotions that can be delivered to a transmission group. The maximum package size may be different among packages for transmission groups ranging from small to large package sizes. The maximum package size ensures that an optimal number and size of promotions are delivered to devices within a transmission group.

[0051] In another preferred embodiment, the common device attributes accommodated by the package may also include data processor speed. Faster data processors are able to handle higher data transmission rates as opposed to slower processors. A package may be adapted to accommodate the data processor speed for a transmission group by specifying an appropriate data transmission rate, which throttles the rate at which data is transmitted to devices so as not to cause packet overrun on the embedded client. Data overrun typically occurs when a device data processor cannot handle the amount of data being received from the network. The data transmission rate is the number of ticks per network packet during transmission. A network packet is about 640 bytes and a tick is approximately 1×10−7 seconds.

[0052] Referring to step 450, if a package is already created for a transmission group, the promotion manager server 220 determines whether there is sufficient space to add the scheduled promotion based on its maximum package size. Promotions are added to each package unless the maximum package size would be surpassed. Therefore, if there is insufficient space for the addition of the promotion, a new package is created for the transmission group as specified in step 440.

[0053] Once a package is either created or located within the database 210 having sufficient space, the promotion is added to the package in step 460. Promotions may be added to packages containing promotions for different promotion groups. In one embodiment, promotions are added to packages by creating a record in the database 210 that correlates a promotion identifier with a package identifier and storing the record in a corresponding table entry.

[0054] Precasting Promotions in a Multimedia Network

[0055] In addition to specifying the manner of transmitting promotion packages, packages may also specify the timing of promotion delivery to transmission groups. As illustrated in FIG. 3B, each package specifies a package start time (i.e., PACKAGE_START_TIME) corresponding to the earliest promotion start time for its set of promotions. As promotions are added to a package, the package start time is updated using the start time of the earliest promotion in the package.

[0056] According to a preferred embodiment of the present invention, a package of promotions is sent in advance of, or “precast” to a transmission group at a data transmission time which is prior to the package start time to ensure that the promotions will be activated as scheduled.

[0057] Optimally, the data transmission time should be far in advance of the package start times, particularly at a time of low network bandwidth utilization such as in the early pre-dawn hours of the day. However, due to certain device constraints, in particular data storage capacity, packages destined for transmission groups having low data storage capacity must be delivered closer to the package start time. Otherwise, there is a risk that promotions from subsequent packages may overwrite promotions that were previously cached but have not yet expired.

[0058] The promotion delivery system therefore optimally precasts packages of promotions by accounting for the data storage capacity and other common device attributes of a transmission group. The process results in packages of promotions being transmitted at appropriate data transmission times preventing data loss and utilizing the available network bandwidth more efficiently.

[0059] In brief overview, the process for determining the data transmission time for a package of promotions involves (1) determining a package transmission lead-time from the common device attributes of a transmission group; (2) determining a data transmission time by subtracting the package transmission lead-time from the package start time; and (3) initiating the transmission of the promotion package to the transmission group at the data transmission time.

[0060] FIG. 4A is a time line diagram illustrating considerations for determining a package transmission lead-time with its constituent lead-times according to one embodiment. Each of the constituent lead-times relates to a common device attribute of the transmission group to which the package corresponds. The package transmission lead-time 700 typically includes a storage dependent lead-time ΔT1, a data transit lead-time ΔT2, a network latency lead-time ΔT3, and a load factor lead-tine ΔT4.

[0061] According to one embodiment, the data storage capacity of a transmission group is a device attribute for determining the package transmission lead-time. Device storage capacity is accounted for in a storage-dependent lead-time ΔT1 which is a variable time period directly related to the data storage capacity of a transmission group.

[0062] Transmission groups having low storage capacity need promotion content cached in its devices closer to the time of promotion activation. Otherwise, there is a risk that the promotion content may be overwritten by promotions from subsequent packages, prior to the scheduled time for activation of the stored promotion. Therefore, if the device data storage capacity is low, the storage-dependent lead-time ΔT1 is relatively short, being closer to the package start time. Short storage-dependent lead-times typically range from seconds to minutes.

[0063] Conversely, transmission groups having high data storage capacity have the necessary cache resources to store more promotions. This allows promotion content to be received at an earlier time when expected network bandwidth utilization is low. Therefore, the storage-dependent lead-time ΔT1 is relatively long for the transmission groups which have high data storage capacity, optimally falling within a period of expected low bandwidth utilization of the multimedia network. Long storage-dependent lead-times typically range from hours to days. According to one embodiment, the storage-dependent lead-time ΔT1 is stored in the database 210 as a transmission group parameter (i.e., DATA_TX_LEADTIME) of FIG. 3C.

[0064] By way of example, assume that a set of promotions is targeted for a promotion group having two transmission groups. One group corresponds to devices having a low storage capacity attribute, while the other is associated with a high storage capacity attribute. Packages are created containing the promotions and having the same package start time for each group. However, the package of promotions for the transmission group having a high storage capacity would have an earlier data transmission time (e.g., one day in advance of package start time at 3:00 AM) as opposed to the transmission group having less storage capacity (e.g., 5 minutes prior to package start time). Thus, by precasting the packages at different data transmission times, allocation of network bandwidth is more efficiently distributed for promotion delivery among the transmission groups.

[0065] According to another embodiment, the device processor speed of a transmission group is another device attribute for determining the package transmission lead-time 700. Since device processor speeds vary between manufacturers and device models, the processor speed of a transmission group is accommodated by a data transmission rate for a promotion package. Accordingly, the data transit lead-time ΔT2 accounts for the time period necessary to transmit the entire package of promotions to a transmission group. The data transit lead-time ΔT2 is calculated by multiplying the (1) inverse of the data transmission rate, (2) sum total of the set of promotion sizes, and (3) cycle count. The cycle count is the number of times the data transmission is repeated. Repetition allows devices that started to receive promotions late to retrieve what it may have previously missed.

[0066] According to a further embodiment, network latency is a common device attribute for determining the package transmission lead-time 700. Although devices may be similar in terms of manufacturer and model, the network topology, to which such devices are connected, can affect the timing of promotion delivery. Where network latency is a factor, such devices are typically grouped together in a separate transmission group statically accounting for such network latency delays.

[0067] For example, a transmission group of devices that are connected to a satellite network are typically slower than a transmission group of devices connected to a cable television network. A network latency lead-time ΔT3 is a variable time period that may be directly related to the network delays attributed to the particular network topology for a transmission group. The network latency lead-time ΔT3 is relatively long if the network latency associated with a particular network topology is typically high. Conversely, the network latency lead-time ΔT3 is relatively short if the network latency is at most nominal.

[0068] Alternatively, the network latency lead-time ΔT3 may be determined dynamically by network statistics accumulated by the promotion manager server 220. For example, as the promotion manager server 220 delivers messages to devices, it can keep track of how long it took for acknowledgment messages to be returned from devices on various subnets or head ends of the multimedia network. The network latency lead-time ΔT3 may be dynamically adjusted to account for network delays attributed to network congestion.

[0069] Another factor that determines the package transmission lead-time is the server load factor which affects the performance of the promotion manager server 220. If the load on the promotion manager server 220 causes the scheduling process to slow down, then there is a risk that the promotions may not be delivered at the specified data transmission times, particularly with transmission groups having low data storage capacity. Therefore, in order to account for the server load factor, a load factor lead-time ΔT4 is added to the package transmission lead-time 700. The load factor lead-time ΔT4 is a variable time period that adjusts to the statistics associated with server performance.

[0070] The promotion manager server 220 monitors its own performance by keeping track of how long certain tasks take to perform. For example, the promotion manager server 220 may track performance statistics relating to the processing of packages or the return of acknowledgment messages from other processes in the promotion server subsystem 200. Such statistics provide an indication of server performance.

[0071] If the statistics indicate that server performance is slow, the load factor lead-time ΔT4 is increased by an amount to account for the server delays in excess of the average data processing times. Conversely, if the statistics indicate that server performance is average or better, the load factor lead-time ΔT4 may by decreased by a nominal amount if at all.

[0072] The data transmission time is subsequently calculated by adding up the constituent lead-times of the package transmission lead-time 700 and subtracting the resulting time period from the package start time. The resulting data transmission time is the time when the multicast or broadcast transmission of promotions must start. According to one embodiment, the data transmission time is stored as a parameter, DATA_TX_TIME, of a package as illustrated in FIG. 3B.

[0073] In addition to determining data transmission times for promotion packages, the promotion manager server 220 determines a schedule transmission time for sending transmission schedule messages to end node devices of targeted promotion groups. Transmission schedules are used to synchronize the delivery of promotions between the promotion server subsystem 200 and devices of targeted promotion groups. The schedules typically contain information relating to the time and manner of promotion delivery and are customized for each end node device. The generation of transmission schedules and their use are discussed in more detail with reference to FIG. 5 and FIG. 7.

[0074] The schedule transmission time is a calculated time when the transmission schedules are to be delivered to the targeted end node devices. It is typically determined by subtracting a schedule transmission lead-time ΔT5 from the data transmission time for a package of promotions.

[0075] FIG. 4B is a time line diagram illustrating a schedule transmission lead-time according to one embodiment. The schedule transmission lead-time ΔT5 is typically a fixed time period. The fixed time period should be long enough to allow for the delivery of a schedule message to a device and for the return of an acknowledgment message back (e.g., 120 seconds). Preferably, the fixed time period should allow for multiple deliveries and acknowledgments of schedule messages prior to the data transmission time for the instances where initial delivery attempts fail. The schedule transmission time is determined by subtracting the schedule transmission lead-time ΔT5 from the data transmission time DATA_TX_TIME. According to one embodiment, the schedule transmission time is stored as a parameter, INFO_TX_TIME, of a package as illustrated in FIG. 3B.

[0076] As additional promotions are added or removed, affected packages are automatically adjusted, provided the transmission schedules have not been previously transmitted. Packages can only be changed manually once the transmission schedule has been sent, since any changes may involve re-transmitting the schedule to the devices.

[0077] Synchronization of Bulk Data Transfers

[0078] Once packages of promotions have been created, the promotion delivery system provides an efficient way of delivering these packages to devices of targeted promotion groups. Due to the potential large number of devices, it is not efficient to deliver promotions individually to each device. Likewise, broadcast transmissions of promotions unnecessarily interrupt devices that are not targeted for promotions in addition to those that are. Therefore, the promotion delivery system delivers promotions by synchronizing end node devices of targeted promotion groups with multicast transmissions of promotion content.

[0079] In brief overview, the process involves (1) scheduling transmissions of promotion packages for delivery across multiple media; (2) notifying devices of targeted promotion groups of the scheduled bulk data transmissions; (3) transmitting the packages of promotions via multicast or broadcast transmission; and (4) selectively receiving a subset of the promotions during the scheduled transmissions. This process is not limited solely to promotions, but can be modified to handle other types of content as well, such as software applications, drivers, and other data files.

[0080] FIG. 5 is a state line diagram illustrating a process for synchronizing the delivery of promotions to end node devices according to one embodiment.

[0081] In step 800, the promotion manager server 220 obtains a set of promotion packages from the promotion database 210. Packages are selected in order according to their package start times from earliest to latest.

[0082] In step 810, the promotion manager server 220 schedules multicast transmissions of promotions by generating customized transmission schedules for each targeted end node device from the set of selected promotion packages. The transmission schedules identify the promotion content to be received, how and when the content will be delivered, and criteria for activating the promotion. The process for generating transmission schedules is discussed in more detail with respect to FIG. 7. According to one embodiment, the times specified in the transmission schedules are synchronized with a time server on the multimedia network or, in the case of television networks, may be synchronized with the broadcast television programming.

[0083] In step 820, the promotion manager server 220 notifies all devices of targeted promotion groups of the scheduled transmissions by sending the transmission schedules individually as messages to the promotion agent 310 of each of the end node devices 300. Since transmission schedules are reliably delivered as messages, the promotion manager server 220 is able to track which devices have received their schedules and those that have not.

[0084] In general, all messages, including schedule messages, are delivered over a message routing subsystem. The message routing subsystem is an application level system involving the message routers 250-n such that communication between the promotion server subsystem 200 and promotion agent subsystems 300 embedded within end node devices is facilitated regardless of server platform.

[0085] In step 830, the promotion agent 310 processes the transmission schedules converting them into promotion download request messages. The promotion download request messages direct the bulk data agent 320 to receive data and the manner of doing so. The payload of the promotion download request message typically contains a serialized local moniker and a serialized remote moniker.

[0086] FIG. 6A is a table identifying the parameters of a local moniker according to one embodiment. The local moniker specifies where to cache promotions in the device once the promotions are received (e.g., file path or registry subkey).

[0087] FIG. 6B is a table identifying the parameters of a remote moniker according to one embodiment. The remote moniker for a multicast transmission specifies the module identifiers which correlate with the promotion content to be received. Furthermore, multicast start times, duration of the multicast transmission, and an IP multicast address and UDP port number may be specified. Alternatively, the start time may be replaced with a trigger event initiating the reception of a multicast transmission.

[0088] In step 840, the promotion agent 310 delivers the promotion download request messages to the bulk data agent 320 which maintains the responsibility for selectively receiving subsets of promotions from multicast transmissions as specified.

[0089] In step 850, the promotion manager server 220 generates transmission requests for each of the selected promotion packages. In brief overview, a transmission request contains module identifiers that correspond to the actual promotion content being delivered as well as data transmission parameters controlling the time and/or manner in which the set of promotions are to be transmitted. Such parameters extracted from the package may include data transmission rate, multicast IP address and port number, and number of transmission repeat cycles. The generation of transmission requests is discussed in more detail with reference to FIG. 8.

[0090] In step 860, the promotion manager server 220 sends the transmission requests as messages to a bulk data server 230. In a preferred embodiment, the promotion manager server 220 may send the same transmission request to multiple bulk data servers located at the head ends of the multimedia network providing additional scalability.

[0091] In step 870, the bulk data server 230 obtains the promotions from the database 210 by the module identifiers specified in the transmission requests. Promotion content is transferred from the database 210 to a bulk data cache local to the bulk data server.

[0092] The size of the local bulk data cache varies in time based on the size and number of promotions identified in the transmission requests received from the promotion manager server 220. The amount of memory allocated for the cache increases with the number and size of promotion content identified in a transmission request. As promotion packages expire (e.g., time for promotion activation has ended), stored promotion content is flushed (e.g. deleted) from the cache and memory is deallocated from the cache; thus reducing the overall cache size.

[0093] In step 880, the bulk data agent 320 “tunes” into the multicast transmission at the specified data transmission time or in response to a specified trigger event. The bulk data agent 320 “tunes” into the multicast transmission by opening a connection to the IP multicast address and port.

[0094] In step 890, the bulk data server opens a multicast transmission sending the promotions to the IP multicast port address.

[0095] In step 895, the bulk data agent selectively receives the subset of promotions in the transmission and caches the promotions in its local device cache. In selectively receiving the promotions, the bulk data agent 320 scans the multicast data stream for the module identifiers corresponding to the subset of promotions specified in the remote monikers extracted from the promotion download request messages.

[0096] For subnetworks or devices that do not support IP multicast, the bulk data transmission is performed through an IP broadcast. Although broadcast transmissions of promotions would be sent to all devices, only those devices that have received transmission schedules will selectively receive the promotions from the data stream.

[0097] Once the promotions have been successfully installed, promotions may be activated at specified times or events indicated in the transmission schedules.

[0098] Scheduling Packages

[0099] In more detail regarding the generation of transmission schedules and transmission requests, the promotion scheduling process occurs in two interleaved phases with the promotion manager server 220 cyclically processing packages extracted from the database 210. The first phase involves the generation of transmission schedules and transmission requests from promotion packages. Transmission schedules and transmission requests are then utilized in the second phase of the delivery process for synchronizing bulk data transfers of promotion packages discussed previously. Transmission schedules are distributed to end node devices 300 of targeted promotion groups notifying them in advance of subsequent bulk data transfers, while transmission requests are delivered to bulk data servers 230 to initiate the transfers.

[0100] In brief overview, the generation of transmission schedules involves the promotion manager server 220 (1) extracting a set of packages from the database 210; (2) generating a map of device transmission schedules from the extracted packages; (3) iterating through the map of device transmission schedules generating individual schedule messages for each device; and (4) transmitting the individual schedule messages to each device in the map using standard messaging.

[0101] In more detail, FIG. 7 is a flow diagram illustrating a process for generating transmission schedules for devices according to one embodiment.

[0102] In step 2000, the promotion manager server 220 extracts a set of packages that have not been processed for schedule distribution. According to one embodiment, a package indicates that it has not been processed for schedule distribution by setting its boolean INFO_TX_SENT parameter to false. Furthermore, the current system time should be within a specified range of the package's schedule transmission time (i.e., INFO_TX_TIME) for the package to be extracted. In one embodiment, the specified range is determined by the following:

(INFO—TX—TIME−ΔTproc/2)≦Tsys≦(INFO—TX—TIME+ΔTproc/2)  (1)

[0103] where ΔTproc is the amount of time needed to process a maximum number of packages and Tsys is the current system time.

[0104] Packages may be extracted at a variable polling rate. Limits may be configured relating to the minimum and maximum poll frequencies. However, the exact value of the polling rate at a given time is controlled by the promotion manager server 220 itself based on the current package load. As the number of packages processed per cycle remains constant or increases, the current polling rate decreases toward the minimum poll frequency value at configurable increments. Conversely, as the number of packages decreases, the polling rate increases toward the maximum poll frequency value at configurable increments.

[0105] Furthermore, the promotion manager server 220 maintains internal information relating to its own performance, specifically the rate at which packages are being processed. The host system on which a promotion manager server 220 executes indirectly affects the efficiency of the scheduling process. As the number of processes on the system changes, the physical resources made available to the promotion manager server 220 by the operating system vary. When the promotion manager server 220 has fewer resources, the average package-processing rate will increase. When the promotion manager server 220 has more resources, this time decreases.

[0106] In step 2010, after extracting the packages, the promotion manager server 220 serially processes the set of packages selecting a package in order of earliest package start time and extracting a set of promotion identifiers from the selected package.

[0107] In step 2020, the promotion manager server 220 selects one of the promotion identifiers and obtains a list of device identifiers representing actual end node devices that are targeted for the promotion.

[0108] In step 2030, the promotion manager server 220 generates a transmission schedule for each device identifier adding a schedule entry for the selected promotion. Each schedule entry contains promotion control data which identifies the promotion, transmission parameters, and activation criteria. According to one embodiment, transmission schedules are generated in memory as a stack of data objects representing multiple schedule entries generated from records within various tables of the database 210.

[0109] In more detail, the promotion is identified in a schedule entry by its module identifier. The module identifier corresponds to the promotion content stored in the database 210 and is associated with the promotion identifier. It is possible that multiple promotion identifiers may be associated with the same module identifier. The module identifier is used by the bulk data agent 320 of an end node device during a bulk data transmission to selectively receive promotion content in the data stream.

[0110] The transmission parameters identified in the schedule entry are obtained from the data transmission parameters of the selected package. According to one embodiment, the transmission parameters in the schedule entry may include a package transmission start time, the duration of the transmission, and IP multicast address and port number. Alternatively, the package transmission start time may be replaced with a trigger event similar to those for promotion activation. This information is used by the bulk data agent to receive the multicast transmission.

[0111] The activation criteria specified in the schedule entry is obtained from time slot records stored in the database 210 that are associated with the promotion identifiers. In general, the schedule entry specifies an activation trigger event for the promotion and the duration of the promotion. In particular, an activation trigger event may include a start time, a start message from the promotion manager server 220, the capture of ATVEF tag in the video blanking interval during a program broadcast, a channel change event, or a power event (e.g., OFF/ON).

[0112] In step 2040, the promotion manager server 220 determines whether there are more promotions to process for this package. If so, the process returns to step 2020 to select another promotion identifier from the package.

[0113] Otherwise, in step 2050, the promotion manager server 220 determines whether there are more packages to process. If so, the process returns to step 2010 to select the next package from the extracted set.

[0114] As processing proceeds to subsequent packages, additional schedule entries are added to previously existing transmission schedules. If a transmission schedule has not been created for a device, then a new transmission schedule is created and the schedule entry added. After the last package has been processed, the promotion manager has an map of device specific transmission schedules, keyed by device identifier.

[0115] After all of the packages have been processed, the promotion manager server 220 iterates through the map of device transmission schedules serializing each one. Serializing transforms the stack of data objects into binary serial data that may be transmitted in the payloads of transmission schedule messages. Due to the fixed payload size of a message, more than one schedule message may be required to deliver the entire transmission schedule to a device. The schedule messages are sent with an expiration time such that the delivery time is limited. In the case of message delivery failure where the delivery time expires with no message acknowledgment from a device, transmission errors are reported in an error queue, and error information is captured in the database as well. The promotion manager server 220 may then retransmit the schedule message. As schedule message deliveries proceed, the INFO_TX_SENT flag in each package is set to true and the schedule distribution process concludes.

[0116] Upon reception at an end node device, the promotion agent regenerates the stack of data objects by de-serializes it into memory where it is used to drive the promotion reception and delivery process on the device.

[0117] Once the transmission schedules have been delivered, transmission requests are generated to initiate the scheduled transmissions from bulk data servers located at the data center or head ends of a multimedia network. In brief overview, the generation of transmission requests involves the promotion manager server 220 (1) extracting a set of packages from the database 210; (2) generating an individual transmission request for each of the extracted packages; and (3) transmitting the transmission request to a bulk data server using standard messaging.

[0118] In more detail, FIG. 8 is a flow diagram illustrating a process of generating transmission requests according to one embodiment.

[0119] In step 3000, the promotion manager server 220 extracts a set of packages whose transmission schedules have been distributed but have not been processed for data transmission. The extraction of the set of packages for data transmission may occur simultaneously with the extraction of packages for transmission schedule distribution. However, once extracted, packages are processed serially in order of earliest package start time, with data transmissions taking priority over schedule transmissions.

[0120] According to one embodiment, a package indicates that its promotions have not been delivered by setting its boolean DATA_TX_SENT parameter to false. Furthermore, the current system time should be within a specified range of the package's data transmission time (i.e., DATA_TX_TIME) for a package to be extracted. The specified range may be determined by the following:

(DATA—TX—TIME−ΔTproc/2)≦Tsystem≦(DATA—TX—TIME+ΔTproc/2)  (2)

[0121] where ΔTproc is the amount of time needed to process a maximum number of packages and Tsys is the current system time.

[0122] In step 3010, after extracting the packages, the promotion manager server 220 serially processes the set of packages selecting a package in order of earliest package start time and extracting the data transmission parameters from the package. Each package contains all of the parameters needed to initiate a multicast data transmission. Such parameters include the transmission start time, the duration of the transmission, the data transmission rate, and the IP multicast address and port.

[0123] In step 3020, the promotion manager server 220 creates a transmission request object for the package containing the extracted data transmission parameters. These parameters control the time and manner of transmitting the packages.

[0124] In step 3030, the promotion manager server 220 extracts the set of promotion identifiers from the package and resolves them into the associated module identifiers that correspond to the actual promotion content stored in the database 210.

[0125] In step 3040, the promotion manager server 220 adds each of the module identifiers to the transmission request object. FIG. 9 is a table illustrating the parameters of a transmission request according to one embodiment.

[0126] In step 3050, the promotion manager server 220 determines which bulk data servers 320 are to transmit promotion packages and thus receive the transmission request. According to one embodiment, the promotion manager server 220 resolves each package into a list of the network identifiers that need to multicast the data. The list of network identifiers is distilled from the list of promotion recipients (i.e., device identifiers). From the network identifiers, a message router 250-n servicing each network identifier is determined. Transmission request messages are then sent to each of the bulk data servers 230 that services head end networks 50 via the message routers.

[0127] In step 3060, the promotion manager server 220 serializes the transmission request object and sends it in the payload of messages to the appropriate bulk data servers that will handle the bulk data transfers of the identified promotion content as specified.

[0128] FIG. 10 is a diagram illustrating the organization of the tables of records within the database 210 according to one embodiment. The solid and dotted lines illustrate the interrelations among various records. For example according to one embodiment, T_PACKAGE 910 is database record within a table of other T_PACKAGES implementing a package. The package is adapted for the common attributes of a transmission group through a parameter which references the group identifier for a particular transmission group (i.e. TRANSMISSION_GROUP_ID). This identifier is used to index into a table of T_TRANSMISSION_GROUP records 920 that specify parameters for data transmission, such as maximum storage threshold and data transmission rates, to the member devices of the transmission group. such as a particular class of set top boxes.

[0129] While this invention has been particularly shown and described with references to preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the scope of the invention encompassed by the appended claims.

Claims

1. A method for synchronizing bulk data transfers of content to end node devices in a multimedia network, comprising: scheduling multiple transmissions of content to two or more sets of end node devices; notifying multiple sets of end node devices of the scheduled transmissions; transmitting the content; and selectively receiving a subset of the content during the scheduled transmissions.

2. The method for synchronizing bulk data transfers of claim 1, wherein scheduling transmissions comprises: generating transmission schedules for the two or more sets of end node devices, each transmission schedule being customized for an end node device; the transmission schedules comprising content control data for the subset of content, the content control data specifying parameters for selectively receiving the subset of content.

3. The method for synchronizing bulk data transfers of claim 2, wherein the parameters comprise a data transmission time.

4. The method for synchronizing bulk data transfers of claim 2, wherein the parameters comprise a set of module identifiers, each module identifier uniquely identifying content scheduled for transmission.

5. The method for synchronizing bulk data transfers of claim 2, wherein the parameters comprise a destination port address.

6. The method for synchronizing bulk data transfers of claim 5, wherein the destination port address is a multicast port address.

7. The method for synchronizing bulk data transfers of claim 5, wherein the destination port addresses is a broadcast port address.

8. The method for synchronizing bulk data transfers of claim 2, wherein notifying multiple sets of end node devices comprises: delivering the transmission schedules to each device of the two or more sets of end node devices prior to the scheduled transmissions.

9. The method for synchronizing bulk data transfers of claim 1, wherein selectively receiving the subset of content comprises: listening for the subset of content on a destination port address during the scheduled transmissions initiated at a data transmission time; selecting the subset of content during the scheduled transmissions; and receiving the subset of content.

10. A method for synchronizing bulk data transfers of claim 1, wherein scheduling transmissions further comprises: generating a transmission request for the content, the transmission request comprising transmission control data controlling the transmission of content.

11. The method for synchronizing bulk data transfers of claim 10, wherein the transmission control data of the transmission request comprises module identifiers corresponding to content scheduled for transmission, a data transmission rate, a data transmission time, and a destination port address.

12. The method for synchronizing bulk data transfers of claim 1, wherein the content is a plurality of promotions.

13. The method for synchronizing bulk data transfers of claim 1, wherein the scheduled transmissions are scheduled multicast transmissions.

14. The method for synchronizing bulk data transfers of claim 1, wherein the scheduled transmissions are scheduled broadcast transmissions.

15. The method for synchronizing bulk data transfers of claim 1 wherein the content is transmitted multiple times during the scheduled transmissions to ensure that the plurality of end node devices receive the subset of content.

16. The method for synchronizing bulk data transfers of claim 2, wherein the parameters specify a capture of an ATVEF HTML tag in the video blanking interval during a program broadcast as a trigger event to initiate reception of content.

17. The method for synchronizing bulk data transfers of claim 2, wherein the parameters specify a receipt of a start message as a trigger event t o initiate reception of content.

18. A content delivery system for synchronizing bulk data transfers of content to end node devices in a multimedia network, comprising: a content server subsystem; a plurality of end node devices; the content server subsystem scheduling multiple transmissions of content to two or more sets of end node devices; the content server subsystem notifying multiple sets of end node devices of the scheduled transmissions; the content server subsystem transmitting the content; and the plurality of end node devices selectively receiving a subset of the content during the scheduled transmissions.

19. The content delivery system of claim 18, wherein the content server subsystem schedules transmissions by generating transmission schedules for the two or more sets of end node devices, each transmission schedule being customized for an end node device; the transmission schedules comprising content control data for the subset of content, the content control data specifying parameters for selectively receiving the subset of content.

20. The content delivery system of claim 19, wherein the parameters comprise a data transmission time.

21. The content delivery system of claim 19, wherein the parameters comprise a set of module identifiers, each module identifier uniquely identifying content scheduled for transmission.

22. The content delivery system of claim 19, wherein the parameters comprise a destination port address.

23. The content delivery system of claim 22, where the destination port address is a multicast port address.

24. The content delivery system of claim 22, where the destination port address is a broadcast port address.

25. The content delivery system of claim 19, wherein the content server subsystem notifies the multiple sets of end node devices by delivering the transmission schedules to each device of the two or more sets of end node devices prior to the scheduled transmissions.

26. The content delivery system of claim 18, wherein the plurality of end node devices selectively receive the subset of content by listening for the subset of content on a destination port address during the scheduled transmission initiated at a data transmission time, selecting the subset of content during the scheduled transmissions, and receiving the subset of content.

27. The content delivery system of claim 19, wherein the content manager server comprises: a content database, the content database storing the content; a content scheduler, the content scheduler generating and delivering the transmission schedules to the plurality of end node devices; and a bulk data server, the bulk data server transmitting the content.

28. The content delivery system of claim 27, wherein the content scheduler generates and delivers a transmission request to the bulk data server, the transmission request comprising transmission control data controlling the transmission of content.

29. The content delivery system of claim 28, wherein the transmission control data of the transmission request comprises a destination port address, a data transmission time, a data transmission rates and module identifiers corresponding to the scheduled subset of content.

30. The content delivery system of claim 29, wherein the bulk data server obtains the content from the content database and transmits the content to the destination port address at the data transmission time at the data transmission rate.

31. The content delivery system of claim 19, wherein each of the plurality of end node devices comprises: a content agent; a bulk data agent; the content agent receiving a transmission schedule from the content manager server; the bulk data agent selectively receiving the subset of content during the scheduled transmissions.

32. The content delivery system of claim 31, wherein the content agent forwards download requests for the subset of content to the bulk data agent, the download requests comprising destination port addresses and data transmission times extracted from the transmission schedule.

33. The content delivery system of claim 32, wherein the bulk agent selectively receives the subset of content by listening on the destination port address during the scheduled transmission initiated at the data transmission time for the subset of content, selecting the subset of content during the scheduled transmissions, and receiving the subset of content.

34. The content delivery system of claim 18 wherein the plurality of end node devices are a plurality of set top boxes capable of activating content in a television environment.

35. The content delivery system of claim 18 wherein the content is a plurality of promotions.

36. The content delivery system of claim 18 wherein the scheduled transmissions are scheduled multicast transmissions.

37. The content delivery system of claim 18 wherein the scheduled transmissions are scheduled broadcast transmissions.