WO2000072157A9

WO2000072157A9 - Architecture, system and method for scheduling networked resources using repeat-time sequence data

Info

Publication number: WO2000072157A9
Application number: PCT/US2000/014183
Authority: WO
Inventors: Jon Brelin
Original assignee: Sony Electronics Inc
Priority date: 1999-05-24
Filing date: 2000-05-23
Publication date: 2002-05-02
Also published as: JP2003500961A; WO2000072157A8; WO2000072157A1

Abstract

The invention is an architecture, a system (90) and a method for scheduling a shared resource (105) over a network from a plurality of client devices (91, 93, 95). The invention is particularly useful for scheduling data transactions between audio/video equipment networked within an input/output bus network (100). Preferably, schedule entries are submitted as resource requests from client devices (91, 93, 95) to an AV/C bulletin board (104) over an IEEE 1394 serial bus network using the AV/C protocol. The resource requests are organized into a resource calendar with command sets that are used to notify devices and users of possible schedule conflicts. Repeat-time sequence data is entered in each resource request and defines the start time and date, duration of each event, interval, number of events value corresponding to the number of times the request is to be repeated and the overall duration for each resource request submitted. The repeat-time sequence data provides for the ability to map a resource schedule or calendar. The invention also provides for a graphical user interface (109) that generates a graphical resource schedule that is viewable from networked client devices (91, 93, 95), wherein a user can view the resource calendar prior to making a schedule choices.

Description

ARCHITECTURE, SYSTEM AND METHOD FOR SCHEDULING NETWORKED RESOURCES USING REPEAT-TIME SEQUENCE DATA

Related Applications:

This application claims priority under 35 U.S.C. § 119(e) of the co-pending U.S. provisional application Serial Number 60/135,833 filed on May 24, 1999 and entitled "Scheduling Repeated Tasks Using Reset Count Information On Networked Devices Incorporating A Resource Schedule Board." The provisional application Serial Number 60/135,833 filed on May 24, 1999 and entitled "Scheduling Repeated Tasks Using Reset

Count Information On Networked Devices Incorporating A Resource Schedule Board" is also hereby incorporated by reference.

Field of the Invention: The invention relates to an architecture, a system and a method for allocating shared resources over a network. More specifically, this invention relates to an architecture, a system and a method for scheduling shared resources over a network using repeat-time sequence data.

Background of the Invention: Information and computation devices are often connected through local area networks

(LANs). LANs allow devices to send messages to each other, share resources, (such as RAM, hard drive space), download software and the like. A network can be constructed using a variety of routing hardware including internet connections and wireless transmitter/receiver devices. Intra-office networks, such as ETHERNETS, are common place and even in the home environment multiple computer devices are often networked. As with other networks, a typical intra-office network allows users at different computer terminals to share RAM, disk space, transfer files, share programs and in some cases share computing power. Network systems that have several client devices sharing a single resource, require an architecture, a system and a method of distributing the shared resource to the client devices. When a computing resource is shared between several client devices, computing time is often scheduled or partitioned using a systems resource manager. Some systems resource managers operate over a bus structure that is internal to the shared computing device. The systems resource manager allocates resource time for submitted resource requests according to partitioning criteria or an algorithm. The partitioning criteria or algorithm is generally systems specific and depends on the types of resource devices that are networked. Other systems resource managers operate through a second layer bus that is external to the shared resource device or through the network itself. Whether a systems resource manager operates internally to the resource device, externally over the network or any combination thereof, there are several general ways that resource requests are prioritized for processing. For example, resource requests are processed in the order that they are received by holding the request in an "order received QUE". Alternatively, resource requests are partitioned into parts or request data packets so that several resource requests are processed incrementally over an extended period of time. Lastly, resource requests are prioritized according to weighting factors, wherein the resource manager knows that certain requests have a higher priority and submits requests for processing according to their known priority.

Resource requests can be submitted over a network from client devices, from control devices or other scheduling devices. Herein, a client device refers to a networked device that receives scheduled resource time, while a scheduling device refers to a device that schedules resource time for itself or other networked devices. Resource devices are not limited to devices with a single resource function. Resource devices may have several resource functions, herein referred to as resource subunits, each of which are capable of being scheduled over a network. The above mentioned nomenclature is developed to explain and describe the direction that data is transmitted and received from one device to another device over a network. It is clear, however, that client devices can also be resource devices and that resource devices can also be client devices in different or simultaneous data transactions over the network.

The "IEEE 1394 Standard For A High Performance Serial Bus," draft ratified in 1995 is an international standard for implementing an inexpensive high-speed serial bus network which supports both asynchronous and isochronous format data transfers. Isochronous data transfers are real-time transfers which take place such that the time intervals between significant instances have the same duration at both the transmitting and receiving applications. Each packet of data transferred isochronously is transferred in its own time period. The IEEE 1394-1995 standard bus architecture provides multiple channels for isochronous data transfer between applications. A six bit channel number is broadcast with the data to ensure reception by the appropriate application. This allows multiple applications to simultaneously transmit isochronous data across the bus structure. Asynchronous transfers are traditional data transfer operations which take place as soon as possible and transfer an amount of data from a source to a destination.

The IEEE 1394-1995 standard provides a high-speed serial bus for interconnecting digital devices thereby providing a universal I/O connection. The EEEE 1394-1995 standard defines a digital interface for the applications thereby eliminating the need for an application to convert digital data to analog data before it is transmitted across the bus. Correspondingly, a receiving application will receive digital data from the bus, not analog data, and will therefore not be required to convert analog data to digital data. The cable required by the IEEE 1394-1995 standard is very thin in size compared to other bulkier cables used to connect such devices. Devices can be added and removed from an IEEE 1394-1995 bus while the bus is active. If a device is so added or removed the bus will then automatically reconfigure itself for transmitting data between the then existing nodes. A node is considered a logical entity with a unique address on the bus structure. Each node provides an identification ROM, a standardized set of control registers and its own address space. Because of the these advantages the IEEE 1394-1995 standard provides for a unique networking structure that is capable of incorporating audio/video devices, media play/record devices and computing display devices.

A diverse range of products can be implemented with the ability to connect to an IEEE 1394-1995 serial bus network. These devices can have capabilities and functionality ranging from very simple to very complex. Specifically a variety of audio/video devices, media play/record devices and computing/display devices are capable of being linked together over an IEEE 1394 serial bus networking structure to support asynchronous and isochronous data transfers between the devices.

The IEEE 1394-1995 serial bus allows a collection of devices to work together in a high bandwidth, distributed environment to maximize the overall efficiency and functionality of the network. This allows manufacturers to remove expensive pieces of functionality from one device and locate that functionality in another device on the network, instead of duplicating this functionality in all devices on the network. While some of the devices have limited functionality and are relatively inexpensive, such devices require the support and interaction of other devices in order to bring the full functionality of the devices within the network to the user.

An AV/C Digital Interface Command Set is a command set used for transactions between consumer audio/video equipment over an IEEE 1394-1995 serial bus. Neither the EEEE 1394-1995 serial bus nor the AV/C Command Set provide a master-slave relationship between the devices coupled within the EEEE 1394-1995 serial bus network. Instead, both the IEEE 1394-1995 serial bus and the AV/C Command Set operate based on the cooperative peer-to-peer coexistence of devices within the network transmitting data formatted in accordance with the AV/C protocol.

An AV/C bulletin board subunit is an information architecture that is shared between devices networked over an IEEE 1394-1995 serial bus network. The AV/C bulletin board subunit typically is dedicated to a single device and supplies information about that devcie. A resource schedule bulletin board is also an information architecture that supports information shared between coupled devices within a network. The resource schedule bulletin board provides the organizational structure through which shared data is organized and communicated. The resource schedule bulletin board contains sub-boards of list descriptors with entry descriptors that represent encoded data that can be shared between devices within the network via descriptor commands. An AV/C bulletin board subunit is typically dedicated to a single resource device and supports the information architecture between that device and other compatible posting devices within an EEEE serial bus network. A posting device writes a request entry to a write enabled list within the resource schedule bulletin board specifying when it will use the resource.

To provide optimal functionality and utilization for a diverse collection of audio/video and computing devices networked over serial bus, scheduling is required to modulate and orchestrate data transfers between the networked devices. Currently there is no architecture, system or method available for scheduling such a diverse collection of devices conveniently and efficiently.

SUMMARY OF THE INVENTION:

The present invention provides an architecture, a system and a method for scheduling shared resources over a network using repeat-time sequence data. Repeat-time sequence data defines a start time and date, a duration, a number of events and an interval for each resource request submitted and provides for the ability to map a resource schedule. The number of events can be equal to one, if appropriate, for a singularly occurring request. The number of events can also be equal to any number greater than one for a request which is to be repeated. The interval is the time between events and can be daily, weekly, monthly or any other appropriate interval. The invention is particularly useful for scheduling resource devices,

- A - wherein the resource devices need to operate continuously for the duration of a resource task. This is typically the situation for media playing and recording devices or video/audio playing and recording devices.

The invention also provides a method of scheduling a shared resource over a network that utilizes a resource schedule board architecture (RSB) containing repeat-time sequence data. The RSB contains entries that are accessible by all the networked posting devices to determine resource availabilities. Each networked resource device has a dedicated resource board and memory for storing scheduling data submitted as resource requests.

In other embodiments the invention provides a programable scheduling system that allows users to submit resource requests from several remote client devices over a single network. The user creates a resource request from a networked client device. The resource request supplies resource schedule board (RSB) entries to the RSB over the network. RSB entries are added or updated each time a new resource request is created and submitted from the client device or different scheduling device. The RSB entries include a notice that the requesting client device intends to utilize the scheduled subunit during the specified time.

Resource scheduling is preferably implemented through an AV/C resource schedule bulletin board which provides networked devices with information for avoiding schedule conflicts.

In yet another embodiment of the current invention, a scheduling architecture provides a resource schedule that is viewable over the network. The resource schedule is generated from all the resource request data submitted over the network. The resource schedule allows users to view the collection of schedule entries submitted for resources and thus allows the user to review resource availabilities before submitting a new resource request.

In further embodiments of the present invention the system allows a networked resource to be scheduled from a plurality of client devices by inputting schedule entries into an AV/C bulletin board using a remote control device.

The present invention also provides a method of allocating a shared resource over a network by generating a resource schedule that is executable over a network, wherein the resource schedule contains repeat-time sequence data for posting intended use of the resource time to client devices over an EEEE 1394-1995 serial bus network structure. The repeat-time sequence data indicates intended use of the shared resource on a weekly basis, on a daily basis or any other number of repeat time sequences described below.

The current invention provides for an architecture, a system and a method for scheduling resources that are shared over a network. The architecture, the system and the method of the present invention are particularly useful for scheduling resource devices over an EEEE 1394-1995 serial bus network, but can be used to schedule shared resources over any type of network. The current invention utilizes repeat-time sequence data to schedule resources, allowing resources to be scheduled efficiently for a plurality of requesting client devices.

Scheduling a shared resource is accomplished by inputting schedule entries at an appropriately configured device including a bulletin board subunit with a RSB. Such a device includes a resource device, a client device, a separate posting device or any combination thereof. Preferably, the scheduling is accomplished by accessing a schedule menu that is accessible at the posting device and inputting schedule entry selections therefrom. A complete schedule selection contains information about the resource requested, the start time that the resource is needed, the duration of time that the resource is needed for and a repeat- time sequence including a specified interval and a number of events value. A repeat-time sequence defines the start time, the number of entries, the duration and the interval of the resource request. The start time includes a time value and a date value. The RSB entries are then generated for the request and each include the corresponding time that the resource device is intended to be used. Once the schedule entries are completed, the request is submitted over the network to the resource device. Resource requests are stored as an entry in the RSB and can be accessed by devices within the network. At the start time indicated in the entry, the client device then reserves the resource device using an AV/C command and initiates the transfer of information to or from the resource device.

A RSB comprises submitted requests from each of the networked posting devices. Preferably, the RSB is accessible by each networked posting device and provides for communication between the posting devices and the resource device about resource availabilities for resource devices represented by the RSB. The RSB contains field entries for the resource requests which are submitted from posting devices. The field entries generate command sets that initiate the allocation of a resource for requesting devices.

In a particular embodiment of the invention, resource requests are entered from scheduling menus that are viewable from screens at posting devices and submitted to a RSB. The RSB is supported by a graphical user interface program operating from at least one computing unit with memory for storing programs and schedule data. In yet another embodiment, a graphical user interface provides a complete resource schedule viewable at the posting device, such that a user can review the resource schedule prior to inputting schedule request entries.

In a further embodiment of the current invention, resource requests are submitted from a scheduling computer or resource manager, wherein the scheduling computer schedules resource time for other networked devices. The posting computer generates schedule requests, modifies the resource schedule and submits complete resource requests to the networked resource to post notice of intended uses of resource devices. The scheduling computer can further provide the resource device with execution instructions including program data and which programs to provide during the scheduled resource time. An exemplary system for utilizing the aforementioned invention includes a resource device comprising at least one resource, posting devices through which resource requests are submitted and a network through which scheduling requests are transmitted to the resource device and through which resource time is allocated to the posting device. Client and resource devices are preferably audio/video devices that play and record media contents but may be any appropriate devices including computers. Resource devices are not limited to devices with a single resource function and may have several resource subunits.

Brief Description of the Drawings:

Fig. 1 illustrates a network of devices including a posting device 3 and a target device 5.

Fig. 2 shows a detailed resource schedule sub-entry according to the present invention. Fig. 3 illustrates unrepeating scheduling types graphically displayed on a time-line display.

Fig. 4 illustrates a schedule time-line display with conflicting resource requests. Fig. 5 illustrates a schedule time-line display with schedule conflicts resulting from multiple schedule entries.

Fig. 6 illustrates a system utilizing a scheduling architecture according to the present invention.

Fig. 7 illustrates a system within an EEEE 1394-1995 serial bus network according to the present invention.

Fig. 8 illustrates an alternative network system within an EEEE 1394-1995 serial bus network according to the present invention. Fig. 9 illustrates a block diagram of the internal components of the computer system within an EEEE 1394-1995 serial bus network according to the present invention.

Fig. 10 is a block-flow diagram according to the method of the preferred embodiment of the present invention. Fig. 11 illustrates a system with several client devices and a posting device networked to a shared resource device over an EEEE 1394-1995 serial bus according to the present invention.

Detailed Description of a Preferred Embodiment: Figure 1 illustrates a network of devices including a posting device 3 and a target device 5. In the preferred embodiment of the invention, resource schedule entries 2, as shown in Figure 1, include the capability of specifying repeat-time information for resource device requests. Resource request entries are generated from networked client or scheduling devices 3 using any suitable method known in the art, such as a scheduling protocol supplied with a typical VCR device. The resource request entries are used by a target device 5 which includes the bulletin board subunit including a resource schedule board (RSB) 4 to build a resource schedule according to which resource time is allocated to the requesting client devices over a network. In one embodiment of the current invention, the scheduling data and scheduling architecture is transparent to the user and provides information to coordinate data transfer between devices at a systems level. In another embodiment of the current invention scheduling data and resource schedules are accessible to the users over the network. In further embodiments of the invention, viewable scheduling menus and resource schedules are generated by a graphical user interface. A schedule entry is generated by entering schedule data into a scheduling menu and submitting the data as a resource request from the posting device 3 to the target device 5 over the network. Resource requests for all the requesting client devices are stored in a memory unit at a central location and the graphical user interface generates viewable resource schedules therefrom. The internal data structure and the graphical interface used for supporting the scheduling menus is application and device dependent. Again referring to Fig. 1, resource requests are made by entering schedule data including a start time and date, a duration time, repeat information including an interval value and a number of events value, if appropriate, and a resource indicator in the resource request entry box 6. A resource request containing the scheduling data shown in the box 6 is submitted over the network and transferred to or used to make a new resource schedule entry 2. The RSB 4 includes one or more entries 2, each representing a received resource request and specification indicating that the posting device intends to utilize the resource device according to the information specified in the resource schedule entry 2. In accordance with an alternative embodiment described above, field values in the resource schedule entries 2 are used to provide a graphical user interface with scheduling data needed to generate a resource schedule accessible over the network.

Figure 2 illustrates a view 20 of a high level schedule entry section 21 detailing the schedule entries that are input from a posting or scheduling device to provide a complete resource request. The start time is input in the entry block 25, the duration time is input in the entry block 27, and resource device information is input in the entry block 17. The repeat- time sequences are input in the entry blocks 11 and 29. Only one of the entry blocks 11 and 29 will be used in each entry, as appropriate. The entry block 29 is used for resource schedule entries to be repeated on a weekly basis. The entry block 11 is used for resource schedule entries to be repeated on a specific interval basis.

In order to specify the repeat-time sequence entries, a number of events value and a repeat interval are required. The number of events value can be equal to any appropriate number, including one, and specifies the number of times the entry is to be repeated. The repeat interval is the time between events and can be daily, weekly, monthly or any appropriate interval. For example, in the entry block 29, intervals such as daily, weekly or monthly are input along with a number in the number_of_events field which specifies the number of events value and represents the number of times that the request is to be executed, and thus defines the overall duration. Also, certain days of the week can be blocked out or not included within the schedule. By blocking out dates within an overall duration, the resource can be more efficiently used by other client devices. For example, a schedule request can contain field values that indicate a resource is needed every day for two weeks except for Tuesday of the second week. Thus, by viewing the resource schedule, other client or scheduling devices can see that the resource is available on that Tuesday and schedule resource time accordingly. It is convenient to provide day selections such as Monday, Thursday etc., as shown in block 29, wherein when a user schedules the resource for a particular day, the resource will automatically be scheduled for that selected day for the overall duration of the schedule entry. The entry block 11 shows an entry form used for resource schedule entries to be repeated on a specific interval basis. In the entry line 13 a time interval is input, which is either a regular time interval (such as an hour or a day) or an irregular time interval that does not follow a naturally repeating block of time. On the entry line 15, the number of events value is input specifying the number of times the resource request is to be executed. For example, if a user inputs a schedule entry with an interval value corresponding to one hour and 20 minutes and a number of events value equal to nine, then the shared resource will be scheduled for nine one hour and 20 minute intervals, starting at a time specified in the entry block 25, with a duration as specified in the duration entry block 27. Prior to submitting a resource request over the network, the client device reviews the resource schedule to determine resource availabilities. In the event that the requested time is already scheduled by another device, the system informs the user that there is a schedule conflict. In an alternative embodiment, the resource schedule board is supported by a graphical user interface, which the user can review before submitting a new request over the network to ensure that the resource is available at the desired time.

Viewing a resource schedule in a menu display or in a numeric list form is difficult for a user. Accordingly, the graphical user interface of this embodiment generates an easy to read graphical representation of the collective resource requests. This graphical representation is in the form of a time-line display that is viewable from each of the networked posting devices. In Figure 3, a series of exemplary schedule displays are shown for a resource device with two resource subunits as indicated by the resource labels 1 and 2, respectively. Each set of displays corresponds to one day of the week, in this case Tuesday, Thursday, Saturday and Sunday. According to the displays shown in Figure 3, the resource 1 has been scheduled from 5:30AM to 9AM Tuesday, Thursday and Saturday, while the resource 2 remains available for those times. On Sunday, the resource 2 is scheduled at 9AM to an unspecified time, while the resource 1 remains available all day on Sunday. With time-line displays, such as those shown in Figure 4, a user can quickly view the resource schedule from a networked client device. Figure 4 shows a twenty four (24) hour exemplary schedule time-line display for a resource 1 that has schedule entries submitted from client devices A and B. Client device A has scheduled the resource 1 at 3 AM to an unspecified period of time, while the client device

B has scheduled the resource 1 from 7 PM to 10 PM. Because the duration of the request is not specified in the resource request submitted by the client device A, there is a potential schedule conflict with the client device B. Creating a schedule conflict, such as the one indicated in Figure 4, does not prevent a client device from submitting a resource request. When a client device submits a resource request that is in conflict with other requests, the system will preferably notify the user that the request generates a schedule conflict, but will still allow the request to be submitted. According to the preferred embodiment of the current invention, the system continuously monitors the actual usage of the shared resource and updates the resource schedule accordingly. Thus, in the event that the client device A is turned off, cancels the request or finishes using the resource 1, before the start time of the resource request submitted by the client device B, the resource will expect to be used according to the resource request submitted from the client device B. Figure 5 illustrates two twenty four (24) hour exemplary time-line displays corresponding to the resources 1 and 2, with each of the time-line displays indicating a schedule conflict. According to the schedule for resource 1, client device A and client device B have both scheduled the resource 1 for a segment of time between 9 and 10 AM. There are several ways that the system can resolve the schedule conflict. In one embodiment of the invention, the "first to schedule" client device will receive priority and any remaining time left on the schedule after the conflict time has passed will be allocated to the "next to schedule" client device. Thus, if the client device A was the first to schedule the resource 1, the complete segment of resource time is allocated to the client device A. However, if the client device B was the first to submit the resource request, the resource time before 9 AM and the time after 10 AM is allocated to the client device A and the resource time between 9 AM and

10 AM will be allocated to the client device B.

Again referring to Figure 5, the time-line display schedule for the resource 2 shows a scheduling conflict between 5 PM and 6PM for the client devices C and D. According to the adaptive conflict remedy described above, if the client device D was the first to schedule, the resource 2 is allocated to the client device C for the last hour of the third two (2) hour scheduled sequence, as well as the two (2) hour segments scheduled from 6 AM to 8 AM and 12 PM to 2PM. However, if the client device C was the first to schedule, the resource 2 is allocated to client device C for all three of the two (2) hour segments scheduled. In the event that the client device C finishes using the resource 2, cancels the request or is turned off prior to the start time of the resource request for the client device D, the resource time between 4

PM and 6 PM is allocated to the client device D.

In the preferred embodiment of the present invention, scheduling conflicts are not resolved by the RSB, but instead, if a scheduling conflict arises, the user is notified of the conflict through the network of devices and allowed to resolve the conflict as they deem appropriate. Further, in the preferred embodiment of the present invention, the first client device to use the resource device receives priority. Thus, in the display of Figure 5, if the client device A was the first to use the resource 1, it would continue to use the resource 1 through the time between 9 and 10 AM, when the client device B had also scheduled the resource 1. In the event that the client device A finishes using the resource 1 , cancels the request or is turned off prior to the start time of the resource request for the client device B, the resource time between 9 and 10 AM is used by the client device B.

There are many alternative remedies for resolving schedule request conflicts that are in accordance with the current invention. For example, in the event of a schedule conflict between two client devices, the resource time is allocated to the device with the least amount of reserved resource time, thus providing for a "fair share" resolution to schedule conflicts. In addition, particular schedule times can be given weighting factors according to demands on the system for those times. Accordingly, scheduling resource time at peak times or prime times will be given a higher overall schedule value, that is used for determining which client device should "fairly" receive resource time in the event of a schedule conflict. Such a conflict remedy can be successfully implemented, especially when the resource is scheduled to record broadcasts or live programs. It is typically not desired to have only a portion of a program recorded and the user may prefer to have either the complete program recorded or none of the program recorded. Further, schedule menus can be configured to allow a user to input voluntary or subjective weighting factors. In this way the user helps to discriminate which of their scheduled requests will be eliminated in the event of schedule conflict. It is clear that any number of scheduling conflict remedies are in accordance with the current invention and the remedy will depend on the devices included within the network. Figure 6 illustrates a system 40 with a scheduling architecture 41 according to the present invention. The scheduling architecture 41 has an interface 43 that allows the user to input schedule entries, such as a menu interface corresponding to VCR programing protocol. The architecture is configured to be invisible to the user or is supported by a interface that is a graphical user interface program. The graphical user interface program 43 is capable of generating graphical displays of resource schedules, such as those described in Figures 3-5 and entry data structures similar to those described in Figures 1 and 2. The client devices 44 and 47 submit schedule requests 51 and 53 through the menu interface 43 to a CPU 45. The CPU 45 stores the resource requests and generates a resource schedule. The CPU 45 is also capable of storing program data that provides execution instructions to the resource devices 46 and 48, while a resource request is being processed. Resource requests are processed by the devices 46 and 48 according to the resource calendar and resource time is allocated to the devices 44 and 47 according to the implemented protocol and conflict resolution procedure. Again referring to Figure 6, the system 41 monitors the actual usage of the resources 46 and

48 as well as any incoming schedule requests and updates the resource schedule calendar.

Figure 7 illustrates an exemplary system 60 configured with an EEEE 1394-1995 input/output serial bus 70 according to the present invention. A television 61, an internet monitoring device 63, and a personal computer 65 are connected to a recording and playback device 64 through the IEEE 1394-1995 serial bus 70. The scheduling architecture described in Figure 6 is preferably an integral part of the device 64 operating from device software (not shown), but may also be part of the personal computer 65 or any other device within the EEEE 1394-1995 serial bus network 60. The televison 61 and the internet monitoring device 63 are operable with a remote control device 69. Scheduling menus are accessible from each of the devices 61, 63 and 65 and are viewable over their respective video screens. Schedule entries are input as previously described and submitted as resource requests to the device 64. It is preferred that schedule entries are input at the televison 61 and the internet monitoring device 63 with the remote control device 69. The device 63 is detachably connectable to the internet via the connection 67. The personal computer 65 is also capable of submitting requests to the resource device 64 received from a user utilizing a keyboard 66 to be added to the scheduling menu. In a particular embodiment of the current invention, the schedule entries are stored in a memory unit of the computer 65 and the scheduling architecture is supported on the computer 65, by appropriate software which generates the resource schedule.

Figure 8 illustrates an alternative configuration 70 for a network system configured within an EEEE 1394-1995 serial bus 80 according to the present invention. The video monitoring devices 71 and 73 are audio/video devices and are coupled to a video recording and media playing device 74 by the EEEE 1394-1995 serial bus 80, as shown. A computing unit 75 is also coupled to the video recording and media playing device 74 by the EEEE 1394- 1995 serial bus 80. When a user enters a scheduling request to the computer system 75, the computer system 75 transmits appropriate scheduling requests to the resource schedule board maintained by the video recording and media playing device 74. Figures 7 and 8 are illustrative only and there are number of system configurations and a diverse range of devices that can be supported within an EEEE 1394-1995 serial bus to provide point-to-point data stream transmissions. Further, there is no systems limitation that all the devices coupled within the IEEE 1394-1995 serial bus need to be used in order to practice the invention.

Figure 9 illustrates a block diagram 110 of the internal components of the computer system 150 within the EEEE 1394-1995 serial bus according to the invention. The computer system 150 represents either of the computer systems 65 and 75 illustrated in Figures 7 and 8.

The computer system 150 includes a central processor unit (CPU) 135, a main memory 133, a video memory 140, a mass storage device 153 and an IEEE 1394-1995 interface circuit 131, all coupled together by a conventional bidirectional system bus 151. The interface circuit 131 includes a physical interface circuit 130 for sending and receiving communications over the IEEE 1394-1995 serial bus cables 157 and 155. The physical interface circuit 130 is coupled to the video camera 123 via the EEEE 1394-1995 serial bus cable 155 and to the television 121 via the EEEE 1394-1995 serial bus cable 157. The system bus 151 contains an address bus for addressing any portion of the memories 133, 140 and 153. The system bus 151 also includes a data bus for transferring data between and among the CPU 135, the main memory 133, the video memory 140, the mass storage device 153 and the interface circuit 131.

The computer system 150 is also coupled to a number of peripheral input and output devices including a keyboard 125, a mouse 127 and the associated display 120. The keyboard 125 is coupled to the CPU 135 for allowing a user to input data and control commands into the computer system 150. A conventional mouse 127 is coupled to the keyboard 125 for manipulating graphic images on the display 120 as a cursor control device. As is well known in the art, the mouse 127 can alternatively be coupled directly to the computer system 150 through a serial port.

A port of the video memory 140 is coupled to a video multiplex and shifter circuit 137, which in turn is coupled to a video amplifier 139. The video amplifier 139 drives the display 120. The video multiplex and shifter 137 and the video amplifier 139 convert pixel data stored in the video memory 140 to raster signals suitable for use by the display 120. It will be apparent that one or more of the elements of the computer system 150 illustrated in Figure 9 can be omitted or replaced and that elements can be added to the computer system 150 while achieving the principle advantages of the present invention. Figure 10 illustrates a flow diagram outlining the steps according to the method of the current invention for scheduling a shared resource over a network from a plurality of client devices. The clients C, to C_n submit schedule entries S, to S_n by inputting schedule data into menus M, through M_n, respectively. The schedule entries S, to S_n are submitted as resource requests K, to R„ over the network bus (not shown) to a resource schedule board (RSB) 99 which includes a resource schedule bulletin board subunit and maintains the resource schedule board. The resource requests R, to R„ contain scheduling data including request times, request durations, resource indicators and client device indicators. The RSB 99 maintains the resource schedule for a shared resource device 108, having the resources R, to R„. The RSB

99 is preferably integral to the shared resource device 108.

Still referring to Figure 10, according to one embodiment of the invention the client devices C, to C_n can view the resource schedule maintained at the RSB 99 from a monitoring means 98. The monitoring means 98 preferably provides a graphical display of the collective schedule entries submitted for each resource R, to R„. By viewing the resource schedule, a user can modify schedule entries taking into account the system load and or scheduling conflicts and submit new or modified schedule entries S,.to S_n, .

Figure 11 illustrates a system 90 with several client devices 91, 93 and 95. Each of the client devices 91, 93 and 95 have their own menu interface 92, 94 and 96, respectively. The menu interfaces 92, 94 and 96 support scheduling menus. The client devices 91, 93 and 95 are networked by a bus structure 100, that is preferably an EEEE 1394-1995 serial bus network. From the menu interfaces 92, 94 and 96, resource requests are submitted to a bulletin board subunit 104. The bulletin board subunit 104 stores resource requests and generates a resource schedule board (RSB) 101. The RSB 101 preferably includes repeat count information according to the present invention. The RSB 101 contains command sets that inform the shared resource device 105 when and how the resources 106, 107 and 108 are to be utilized within the EEEE 1394-1995 serial bus network. The scheduling menus and resource schedule are viewable on a systems monitor 109 that is in communication with the bulletin board subunit 104. The scheduling menus and resource schedule are also accessible from any of the client devices 91, 93 and 95. The resource device 105 and the client devices

91, 93 and 95 are preferably operable with input devices, such as a systems remote control 103, that can turn the devices on and off, and from which schedule entry data can be input.

The present invention allows a device with a resource, such as a video recording and media playing device coupled within an IEEE 1394-1995 serial bus, to be scheduled from a plurality of client or control devices. The invention provides for a resource schedule board that includes repeat-time data from schedule entries submitted. The described resource schedule board allows the resource to be efficiency scheduled by the plurality of devices for future use. The invention also provides a method of dealing with scheduling conflicts which helps to maintain harmony and efficiency between devices within the system. Prior to the current invention, there was no method for dealing with conflicting schedule requests within an EEEE 1394-1995 serial bus network and client devices could write over a previously submitted schedule request. Also, an embodiment of the current invention provides for a simple way to review schedule requests over the network with a graphical user interface which generates a graphical resource schedule calendar accessible over the network.

The present invention has been described in terms of specific embodiments incorporating details to facilitate the understanding of the principles of construction and operation of the invention. Such reference herein to specific embodiments and details thereof is not intended to limit the scope of the claims appended hereto. It will be apparent to those skilled in the art that modifications can be made in the embodiment chosen for illustration without departing from the spirit and scope of the invention. Specifically, it will be apparent to one of ordinary skill in the art that the device of the present invention could be implemented in several different ways and the architecture, system and method disclosed above are only illustrative of preferred embodiments of the invention. Specifically, it will be apparent to those skilled in the art that while the preferred embodiment of the present invention is used with an EEEE 1394-1995 serial bus structure, the present invention could also be implemented on any other appropriate digital interfaces or bus structures, including other or later versions of the EEEE 1394 serial bus.

Claims

ClaimsWhat is claimed is:

1. An architecture for scheduling a shared resource within a network for a plurality of devices, the architecture comprising: a) a means to generate schedule data comprising, starting times, duration times, and repeat-time sequences; and b) a means to submit the schedule entries over the network to generate a resource schedule.

2. The architecture of claim 1, wherein the means for generating schedule entries comprises a schedule entry menu generated by a graphical user interface.

3. The architecture of claim 2, wherein the graphical user interface further generates a display of the resource schedule from the schedule data.

4. The architecture of claim 3, wherein the schedule display is a time-line graph.

5. The architecture of claim 4, wherein the schedule display is viewable over the network from the plurality of devices.

6. The architecture of claim 1, wherein resource entries are in an AV/C bulletin board format.

7. The architecture of claim 1, wherein means for generating schedule entries comprises a remote control device.

8. The architecture of claim 1 , wherein the network complies with a version of the EEEE 1394 standard.

9. A system for scheduling a resource over a network, the system comprising: a) a resource device comprising one or more resources; b) a client device in communication with the resource device; and c) a resource schedule controller to enter schedule data into a resource schedule, the schedule data comprising an execution time, a duration of time and repeat time sequence, whereby the resource is allocated for use by the client device over the network according to the resource schedule.

10. The system of claim 9, wherein the network complies with a version of the EEEE 1394 standard.

11. The system of claim 9, wherein the resource schedule controller further comprises: a) a viewing screen for displaying a posting menu, wherein the schedule data is entered in to the posting menu; b) a data storage device for receiving and storing the schedule data; c) a computing unit for generating the resource schedule from the schedule data; and d) a graphical user interface, operable from the computing unit, wherein the graphical user interface generates the posting menu.

12. The system of claim 11, wherein schedule data is entered into the posting menu from a device selected from the group consisting of a keyboard and a remote control.

13. The system of claim 9, wherein the resource device comprises a video recorder.

14. The system of claim 13, wherein the client device comprises a video receiver and transmitter.

15. The system of 11 , wherein the viewing screen is integral to the client device.

16. The system of 15, wherein the data storage device, the computing unit and the graphical user interface program are integral to the resource device.

17. The system of claim 16, wherein the graphical user interface further generates a resource schedule display viewable over the viewing screen.

18. The system of claim 17 wherein resource schedule display is a graphical time-line display.

19. A system for scheduling a resource over an EEEE 1394 serial bus, the system comprising a networked resource device comprising a resource with an AV/C bulletin board, wherein schedule entries are capable of being submitted to the AV/C bulletin board over the EEEE 1394 serial bus from a plurality of posting devices to generate a resource schedule, wherein the AV/C bulletin board comprises schedule requests comprising values for a start time, a duration time interval and a number of events sequence.

20. The system of claim 19 wherein the AV/C bulletin board further comprises a collection of schedule entries submitted from the plurality of posting devices.

21. The system of claim 20, wherein a set of executable commands are generated from the AV/C bulletin board according to the schedule calendar.

22. The system of claim 19, wherein the AV/C bulletin board is displayable at each of the plurality of posting devices and the schedule entries are made therefrom.

23. A system for allocating a shared resource between a plurality of client devices, the system comprising an input/output bus structure for networking the shared resource and the plurality of client devices, wherein the input/output bus structure transmits executed resource requests to the plurality of client devices according to a resource schedule, and wherein the resource schedule is programable by submitting resource schedule entries comprising repeat-time sequence data over the bus structure.

24. The system of claim 23, wherein resource requests are generated by providing schedule entries submitted from the client devices.

25. The system of claim 23, further comprising a scheduling unit for receiving the schedule entries and generating the resource schedule, the scheduling unit comprising: a) a memory device for storing the schedule entries; and b) a controller for generating the resource schedule.

26. The system of claim 25, wherein the scheduling unit further comprises a graphical user interface for generating a graphic resource schedule.

27. The system of claim 23, wherein the resource schedule is viewable from the devices over the input output bus.

28. The system of claim 23, wherein the bus structure substantially complies with a version of the EEEE 1394 standard.

29. A method for scheduling and allocating a shared resource between a plurality devices over the network, the method comprising the steps of: a) receiving schedule entries from posting client devices over a network, wherein the schedule entries have schedule data comprising a start time, a duration time interval and a number of events sequence; and b) generating a resource schedule comprising resource requests.

30. The method of claim 29, further comprising the step of continuously updating the resource schedule based on new schedule requests.

31. The method of claim 29, further comprising the step of continuously updating the resource calendar based upon processed resource requests.

32. The method of claim 29, further comprising the step of resolving schedule conflicts.

33. A system for scheduling a resource over a network, the system comprising: a) a resource device comprising one or more resources; b) a posting device in communication with the resource device; and c) a bulletin board subunit configured for communication with the posting device for entering schedule data, wherein the bulletin board subunit includes a resource schedule, into which the schedule data comprising an execution time, a duration interval and number of events sequence.

34. The system of claim 33, wherein the network complies with a version of the IEEE 1394 standard.

35. The system of claim 33, wherein a device which includes the bulletin board subunit comprises: a) a viewing screen for displaying a posting menu, wherein the schedule data is entered in to the posting menu; b) a data storage device for receiving and storing the schedule data; and c) a computing unit for generating the resource schedule from the schedule data; and d) a graphical user interface program, operable from the computing unit, wherein the graphical user interface generates the posting menu.

36. The system of claim 35, wherein schedule data is entered into the posting menu from a device selected from the group consisting of a keyboard and a remote control.

37. The system of claim 33, wherein the resource device comprises a video recorder.

38. The system of claim 37, wherein the posting device comprises a video receiver and transmitter.

39. The system of 35, wherein the viewing screen is integral to the posting device.

40. The system of 39, wherein the data storage device, the computing unit and the graphical user interface program are integral to the resource device.

41. The system of claim 40, wherein the graphical user interface further generates a resource schedule display viewable over the viewing screen.

42. The system of claim 41 wherein resource schedule display is a graphical time-line display.

43. The system of claim 33 wherein the duration interval has a selective value of one of daily, weekly and a specified time.

44. The system of claim 43 wherein when the duration interval is equal to weekly, one or more selected days of a week are further specified.

45. The system of claim 43 wherein when the duration interval is equal to the specified time, a time value including hours, minutes and seconds is specified.