Request event manager and event lists for home and office systems and networks

A computer readable medium containing therein computer readable codes for causing a computer system to perform a method of synchronizing different network activity over time comprising:

• accessing a network service database containing a plurality of service offerings that aggregate capabilities of a plurality of devices;
• presenting the plurality of service offerings to a user;
• receiving a service-centric based request from said user based on one or more of said service offerings;
• determining one or more resources for carrying out said service-centric based request from said network service database;
• translating said service-centric based request into one or more device-specific events based request based on said network service database;
• constructing a service request list based on said device-specific events, wherein said service request list is arranged as a hierarchical data structure that includes a top level and one or more lower levels, wherein said top level includes a handle logically associated with said service-centric based request and timing information for carrying out said service-centric based request, and wherein a lower level includes one or more logical links between said resources, and one or more device-specific commands for carrying out said service-centric based request by said resources;
• determining whether said service request list conflicts with another service request list;
• and
• provided that said service request list does not conflict with said another service request list, storing said service request list.

A home server for coupling to a network of consumer electronic devices, said home server comprising:

• logic for accessing a network service database containing a plurality of service offerings that aggregate capabilities of a plurality of devices;
• logic for receiving a service-centric based request from a user application, that is non-device-specific, based on one or more of said service offerings;
• logic for determining one or more resources of said network for carrying out said service-centric based request from said network service database, wherein said resources include one or more source devices, one or more destination devices and one or more communication links;
• logic for translating said service-centric based request into one or more device-specific events for carrying out said service-centric based request by said resources based on the network service database;
• logic for constructing a service request list that is based on said device-specific events, wherein said service request list is arranged as a hierarchical data structure that includes a top level and one or more lower levels, wherein said top level includes a handle logically associated with said service-centric based request, and descriptive information and timing information for carrying out said service-centric based request, and wherein a lower level includes one or more logical links between said resources, and one or more device-specific commands for carrying out the service-centric based request by said resources;
• logic for determining whether said service request list conflicts with another service request list;
• and
• logic for storing said service request list if said service request list does not conflict with said another service request list.