Processing operations associated with resources on a local network

• US 20060245431A1
• Filed: 04/29/2005
• Published: 11/02/2006
• Est. Priority Date: 04/29/2005
• Status: Active Grant

• Current Assignee: Scenera Technologies LLC (Scenera Research LLC)
• Original Assignee: Scenera Technologies LLC (Scenera Research LLC)
• Inventors: Morris, Robert P.
• Granted Patent: US 7,292,579 B2
• Time in Patent Office: Days
• US Class Current: 370/395.400
• CPC Class Codes: H04L 12/2854 Wide area networks, e.g. public data networks

Abstract

Preferred embodiments of the invention provide a method and system for processing operations associated with resources on a local network. Aspect of the invention include receiving periodic messages containing resource information from network devices connected to the local network, wherein the resource information includes user-requestable services offered by the network device, and data stored by the network device having a mime type. The resource information from each of the messages and a timestamp are stored in a repository. From the stored timestamp and resource information it can be determined which user-requestable services and data having a mime type were available on the network over a predetermined time period. A view of the user-requestable services and data having a mime type that were available on the network over the predetermined period can then be generated, thereby enabling generation of current, past, and dynamic views of the user-requestable services offered by devices connected to the network and the data having a mime type stored by the devices. In a further embodiment, the system enables operations associated with the resources to be performed or scheduled at a time when the resources are unavailable via the network by performing or scheduling the operations on the corresponding resource identifiers stored in the repository.

Claims

1. A method for processing operations associated with resources on a local network, comprising;

receiving periodic messages containing resource information from network devices connected to the local network, wherein the resource information includes user-requestable services offered by the network device, and data stored by the network device having a mime type;

storing a timestamp and resource information from each of the messages in a repository;

determining from the stored timestamp and resource information which user-requestable services and data having a mime type were available on the network over a predetermined time period; and

generating a view of the user-requestable services and data having a mime type that were available on the network over the predetermined period, thereby enabling generation of current, past, and dynamic views of the user-requestable services offered by devices connected to the network and the data having a mime type stored by the devices.

2. The method of claim 1 further including:

performing the method in a mobile network device, wherein the local network is defined as any local network the mobile device connects with over a period of time.

3. The method of claim 1 further including:

performing the method using a server that is part of a topology service site accessible over the network.

4. The method of claim 1 wherein receiving periodic messages further includes:

detecting the network devices present on the network, and detecting a scope and depth of the resource information the network devices are willing to make public.

5. The method of claim 4 further including:

providing at least a portion of the network devices with a topology client application, and providing a network topology/view server, wherein the topology client application transmits the messages from the network devices to the network topology/view server, and the network topology/view server generates the view of the user-requestable services and data having a mime type.

6. The method of claim 5 further including:

providing the network topology/view server with services and a repository for storing, managing, and performing operations on the resource information associated with the network devices that connect to the network.

7. The method of claim 1 further including:

receiving a search request specifying a time period and query attributes; and

generating a view of the resources that were available on the network during the specified time period having attributes matching the query attributes.

8. The method of claim 7 further including:

providing the network topology/view server with a search service for enabling a user to enter the search request via a web interface, and to specify a current time period or a past time period in order to search for resources currently on the network or that were on the network at a past time.

9. The method of claim 6 further including:

providing the network topology/view server with a synchronization service that synchronizes the data having a mime type between at least two network devices regardless of whether the two network devices are connected to the network at the same time.

10. The method of claim 6 further including:

providing the network topology/view server with a pruning service for deleting the timestamp and resource information stored in the repository that have been stored longer than a predefined time.

11. The method of claim 6 further including:

providing the network topology/view server with a cache service for caching the data having a mime type from the network devices to allow the network devices to exchange data regardless of whether the network devices are connected to the network at the same time.

12. The method of claim 6 further including:

providing the network topology/view server with a backup service for backing up the data having a mime type from the network devices.

13. The method of claim 5 further including:

initiating detection of the network devices on the network by the network topology/view server.

14. The method of claim 13 further including:

initiating detection of the network devices on the network by the network devices.

15. The method of claim 1 further including:

allowing operations associated with the resources to be performed or scheduled at a time when the resources are unavailable via the network by performing or scheduling the operations on the corresponding resource identifiers stored in the repository.

16. The method of claim 15 further including:

receiving messages containing commands to perform operations on resources identified in the repository.

17. The method of claim 16 further including:

providing operations including at least one of invoking a particular service offered by a network device, viewing a connectivity of the resources in a topology view of the network, copying or moving resources from one network device to another network device, deleting a resource from a network devices, downloading a resource from a network device, and transmitting a copy of a resource from a network device to a device not associated with the network.

18. The method of claim 17 further including:

performing the scheduled operations on the resources at a time when the resources are available via the network.

19. A network system for a local network, comprising:

one or more network devices capable of communicating with the local network, at least a portion of the network devices including a client application for gathering resource information regarding the respective network device in which it resides, wherein the resource information includes user-requestable services offered by the network device, and data stored by the network device having a mime type; and

at least one server configured to provide a topology service for the network devices through the client applications, the server performing functions for,

receiving periodic messages containing resource information transmitted from the topology clients connected to the local network;

storing a timestamp and resource information from each of the messages in a repository;

determining from the stored timestamp and resource information which user-requestable services and data having a mime type were available on the network over a predetermined time period; and

generating a view of the user-requestable services and data having a mime type that were available on the network over the predetermined period, thereby enabling generation of current, past, and dynamic views of the user-requestable services offered by devices connected to the network and the data having a mime type stored by the devices.

20. The network system of claim 19 wherein the server is implemented in a mobile network device, wherein the local network is defined as any local network the mobile device connects with over a period of time.

21. The network system of claim 19 wherein the server is part of a topology service site accessible over the network.

22. The network system of claim 19 wherein the server further detects the network devices present on the network, and detects a scope and depth of the resource information the client applications are willing to make public.

23. The network system of claim 22 wherein the server includes a discovery service and a data manager for managing communication and messages sent from the client applications.

24. The network system of claim 23 wherein the server further includes a service manager that provides a common interface for adding additional services, wherein the additional services include functions for storing, managing, and performing operations on the resource information associated with the network devices that connect to the network.

25. The network system of claim 19 wherein the server is further capable of receiving a search request specifying a time period and query attributes, and generating a view of the resources that were available on the network during the specified time period having attributes matching the query attributes.

26. The network system of claim 25 wherein the server further includes a search service for enabling a user to enter the search request via a web interface, and to specify a current time period or a past time period in order to search for resources currently on the network or that were on the network at a past time.

27. The network system of claim 24 wherein the server further includes a synchronization service that synchronizes the data having a mime type between at least two network devices regardless of whether the two network devices are connected to the network at the same time.

28. The network system of claim 24 wherein the server further includes a pruning service for deleting the timestamp and resource information stored in the repository that have been stored longer than a predefined time.

29. The network system of claim 24 wherein the server further includes a cache service for caching the data having a mime type from the network devices to allow the network devices to exchange data regardless of whether the network devices are connected to the network at the same time.

30. The network system of claim 24 wherein the server further includes a backup service for backing up the data having a mime type from the network devices.

31. The network system of claim 24 wherein the client application includes service components matching those in the server, including any combination of a synchronization client, a cache client, a backup client, and service plug-ins.

32. The network system of claim 19 wherein the server allows operations associated with the resources to be performed or scheduled at a time when the resources are unavailable via the network by performing or scheduling the operations on the corresponding resource identifiers stored in the repository.

33. The network system of claim 32 wherein the server receives messages containing commands to perform operations on resources identified in the repository.

34. The network system of claim 33 wherein the operations including at least one of at least one of invoking a particular service offered by a network device, viewing a connectivity of the resources in a topology view of the network, copying or moving resources from one network device to another network device, deleting a resource from a network devices, downloading a resource from a network device, and transmitting a copy of a resource from a network device to a device not associated with the network.

35. The network system of claim 34 wherein the scheduled operations are performed on the resources at a time when the resources are available via the network.

36. A computer-readable medium containing program instructions for processing operations associated with resources on a local network, the program instructions for;

receiving periodic messages containing resource information from network devices connected to the local network, wherein the resource information includes user-requestable services offered by the network device, and data stored by the network device having a mime type;

storing a timestamp and resource information from each of the messages in a repository;

determining from the stored timestamp and resource information which user-requestable services and data having a mime type were available on the network over a predetermined time period; and

generating a view of the user-requestable services and data having a mime type that were available on the network over the predetermined period, thereby enabling generation of current, past, and dynamic views of the user-requestable services offered by devices connected to the network and the data having a mime type stored by the devices.

37. A method for processing operations associated with resources on a local network, comprising;

receiving periodic messages including identifiers of resources from one or more network devices connected to the network, wherein the resources include at least one of services offered by the network devices and data stored by the network devices;

storing the resource identifiers from each of the messages in a repository; and

allowing operations associated with the resources to be performed or scheduled at a time when the resources are unavailable via the network by performing or scheduling the operations on the corresponding resource identifiers stored in the repository.

38. The method of claim 37 further including:

providing operations including at least one of invoking a particular service offered by a network device, viewing a connectivity of the resources in a topology view of the network, copying or moving resources from one network device to another network device, deleting a resource from a network devices, downloading a resource from a network device, and transmitting a copy of a resource from a network device to a device not associated with the network.

39. The method of claim 38 further including:

carrying out the scheduled operations on the resources at a time when the resources are available via the network.

40. The method of claim 39 further including:

receiving the operations in messages that include a command and an identification of a target resource, and storing the command in a request queue if the target resource is unavailable.

41. The method of claim 37 further including:

associating a timestamp with the resource identifiers in the periodic messages;

storing the timestamp and resource information from each of the messages in the repository;

determining from the stored timestamp and resource information which user-requestable services and data having a mime type were available on the network over a predetermined time period; and

generating a view of the user-requestable services and data having a mime type that were available on the network over the predetermined period, thereby enabling generation of current, past, and dynamic views of the user-requestable services offered by devices connected to the network and the data having a mime type stored by the devices.

42. The method of claim 37 further including:

performing the method in a mobile network device, wherein the local network is defined as any local network the mobile device connects with over a period of time.

43. The method of claim 37 further including:

performing the method using a server that is part of a topology service site accessible over the network.

44. A network system for a local network, comprising:

one or more network devices capable of communicating with the local network, at least a portion of the network devices including a client application for gathering resource information regarding the respective network device in which it resides, wherein the resource information includes least one of services offered by the network device, and data stored by the network device; and

at least one server configured to provide a topology service for the network devices through the client applications, the server performing functions for,

receiving periodic messages including identifiers of resources from the client applications in network devices connected to the network, wherein the resources include at least one of services offered by the network devices and data stored by the network devices;

storing the resource identifiers from each of the messages in a repository; and

allowing operations associated with the resources to be performed or scheduled at a time when the resources are unavailable via the network by performing or scheduling the operations on the corresponding resource identifiers stored in the repository.

45. The network system of claim 44 wherein the operations including at least one of invoking a particular service offered by a network device, viewing a connectivity of the resources in a topology view of the network, copying or moving resources from one network device to another network device, deleting a resource from a network devices, downloading a resource from a network device, and transmitting a copy of a resource from a network device to a device not associated with the network.

46. The network system of claim 45 wherein the scheduled operations are carried out on the resources at a time when the resources are available via the network.

47. The network system of claim 46 wherein the operations are included in messages that include a command and an identification of a target resource, and storing the command in a request queue if the target resource is unavailable.

48. The network system of claim 44 wherein the server further includes functions for;

associating a timestamp with the resource identifiers in the periodic messages;

storing the timestamp and resource information from each of the messages in the repository;

determining from the stored timestamp and resource information which user-requestable services and data having a mime type were available on the network over a predetermined time period; and

generating a view of the user-requestable services and data having a mime type that were available on the network over the predetermined period, thereby enabling generation of current, past, and dynamic views of the user-requestable services offered by devices connected to the network and the data having a mime type stored by the devices.

49. The network system of claim 44 wherein the server is implemented in a mobile network device, wherein the local network is defined as any local network the mobile device connects with over a period of time.

50. The network system of claim 44 wherein the server is part of a topology service site accessible over the network.

51. A computer-readable medium containing program instructions for processing operations associated with resources on a local network, the program instructions for;

receiving periodic messages including identifiers of resources from one or more network devices connected to the network, wherein the resources include at least one of services offered by the network devices and data stored by the network devices;

storing the resource identifiers from each of the messages in a repository; and

allowing operations associated with the resources to be performed or scheduled at a time when the resources are unavailable via the network by performing or scheduling the operations on the corresponding resource identifiers stored in the repository.