Service management system, and method, communications unit and integrated circuit for use in such system

• US 20040230687A1
• Filed: 04/27/2004
• Published: 11/18/2004
• Est. Priority Date: 04/28/2003
• Status: Abandoned Application

• Current Assignee: Panasonic Corporation (Panasonic Holdings Corporation)
• Original Assignee: Panasonic Corporation (Panasonic Holdings Corporation)
• Inventors: Nakamura, Tomonori, Oashi, Masahiro, Nishimura, Yasushi, Waki, Yasushi
• Application Number:
  US10/832,240
• Publication Number:
  US 20040230687A1
• Time in Patent Office: Days
• US Class Current: 709/228
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

When terminating an app 1, a communications unit 10 identifies any apps dependent on the app 1. In a case where an app 2 is dependent on the app 1, the communications unit 10 requests a communications unit 20 to terminate the app 2. In response to this, the communications unit 20 identifies any apps dependent on the app 2. In a case where an app 3 is dependent on the app 2, the communications unit 20 requests a communications unit 30 to terminate the app 3. In response to this, the communications unit 30 terminates the app 3, and notifies the communications unit 20 of the termination. In response to this, the communications unit 20 terminates the app 2, and notifies the communications unit 10 of the termination. In response to this, the communications unit 10 terminates the app 1. As a result, the apps 1 to 3 are all terminated.

Claims

1. A system for providing an intended service using a plurality of communications units that are connected to a network and execute applications in cooperation with one another, each of the communications units comprising:

dependence table definition means for defining a dependence table identifying dependencies between applications being executed by the communications units;

dependent app identification means for, when terminating a running application, referencing the dependence table to identify a dependent application to be terminated following termination of the application being terminated;

termination request means for requesting a communications unit executing the dependent application identified by the dependent app identification means to terminate the dependent application; and

dependent app termination means for, when requested by another communications unit to terminate a dependent application, terminating the dependent application.

2. The service management system according to claim 1, wherein the dependence table definition means defines the dependence table while regarding an application started by a running application as a dependent application.

3. The service management system according to claim 1, wherein:

the dependence table definition means defines a dependent application by associating a dependent app identifier with each running application; and

the dependent app identification means identifies a dependent application based on the dependent app identifier associated with an application being terminated.

4. The service management system according to claim 3, wherein when a dependent application is started, the dependence table definition means associates a dependent app identifier with the dependent application, the dependent app identifier indicating on which application the dependent application is dependent.

5. The service management system according to claim 1, wherein any application started derivatively from a dependent application is a dependent application.

6. The service management system according to claim 1, wherein:

the dependence table identifies an independent application whose termination is independent of termination of any other applications; and

each communications unit further comprises independent app confirmation means for, when starting an application, prompting a user to confirm whether or not to start the application as an independent application.

7. The service management system according to claim 6, wherein the independent app confirmation means registers a result of the confirmation by the user as a user confirmation identifier associated with the started application in the dependence table.

8. The service management system according to claim 1, wherein:

each communications unit further comprises identifier confirmation means for, when instructing another communications unit to start an application derivatively from a running application, confirming a user confirmation identifier of the running application; and

if it is confirmed by the identifier confirmation means that the running application is an application that has been started without user'"'"'s confirmation, the dependence table definition means regards the application started derivatively from the running application as a dependent application.

9. The service management system according to claim 1, wherein each communications unit further comprises derivative app start determination means for, when starting an application derivatively from another application running on another communications unit, determining whether or not to start the derivative application based on the number of generations notified by the other communications unit.

10. The service management system according to claim 1, wherein each communications unit further comprises derivative app start determination means for, when starting an application derivatively from another application running on another communications unit, determining whether or not to start the derivative application based on the number of applications registered in the dependence table.

11. The service management system according to claim 1, wherein:

the dependence table identifies an independent application whose termination is independent of termination of any other applications;

each communications unit further comprises;

service status notification request means for, when terminating an independent application, requesting another communications unit executing another independent application started derivatively from the independent application to notify the communications unit of a progress of the service; and

service status reception means for receiving the notification of the progress of the service from the other communications unit; and

the other communications unit receiving the service progress notification request notifies the communications unit of the progress of the service at a predetermined time.

12. The service management system according to claim 11, wherein the predetermined time is when the service is terminated.

13. The service management system according to claim 11, wherein the progress of the service is notified at regular time intervals after the notification request is received.

14. The service management system according to claim 11, wherein when an independent application that has been started without user'"'"'s confirmation and that is being executed by one of the communications units involved in the service is terminated, the communications unit notifies all the other communications units that have issued a service progress notification request of the termination of the independent application that has been started without user'"'"'s confirmation.

15. The service management system according to claim 11, wherein the service status notification request means prompts a user to determine whether or not to issue the service progress notification request.

16. The service management system according to claim 1, wherein an application started by a user for initiating the service is handled as a root application, each communications unit further comprising:

communications abnormality detection means for detecting whether or not a communications abnormality has occurred;

communications abnormality notification means for, if the communications abnormality detection means detects a communications abnormality, notifying the communications unit executing the root application of the communications abnormality;

independent app identification means for identifying an independent application whose termination is independent of termination of any other applications involved in the service; and

app termination means for, if the communications unit is executing the root application and if the communications unit is notified of a communications abnormality by another communications unit, instructing other communications units to terminate any independent application identified by the independent app identification means and any dependent application dependent on the root application.

17. The service management system according to claim 16, wherein:

each communications unit further comprises root app proxy request means for, when terminating the root application started by the user for initiating the service, requesting a communications unit executing an independent application identified by the independent app identification means to act as a proxy for performing a function obtained by executing the root application; and

the communications unit receiving the request from the root app proxy request means continues to render the service while using a running independent application as a root application.

18. The service management system according to claim 17, wherein the independent app identification means selects an independent application to serve as a proxy for the root application based on a predetermined priority.

19. The service management system according to claim 18, wherein the priority is determined based on a network communications cost.

20. The service management system according to claim 17, wherein if no independent application is identified by the independent app identification means, the root app proxy request means designates a dependent application started derivatively from the root application as a proxy application to serve as a proxy for the root application.

21. The service management system according to claim 20, wherein each communications unit further comprises service continuability determination means for determining that the service can no longer be continued if the proxy application is a dependent application and if the proxy application receives a communications failure notification from another communications unit.

22. The service management system according to claim 20, wherein each communications unit further comprises root switching means for, if the proxy application is a dependent application and if an independent application is started derivatively from the proxy application, switching the root application to the independent application.

23. The service management system according to claim 1, comprising a management server in which all independent applications involved in the service are registered, wherein if the management server is instructed by a user to terminate the service, the management server terminates all of the registered independent applications.

24. A service management method for managing termination of a service provided by a plurality of communications units connected to a network and cooperating with one another, the method comprising:

a step in which each of the communications units involved in the service defines a dependence table identifying dependencies between applications being executed by the communications units;

a step in which a terminating communications unit, among the communications units, that is executing an application being terminated identifies a dependent application started derivatively from the application being terminated based on the dependence table;

a step in which the terminating communications unit instructs a communications unit executing the dependent application to terminate the dependent application via the network; and

a step in which the terminating communications unit terminates the application being terminated, after the dependent application is terminated.

25. The service management method according to claim 24, wherein in the step of defining the dependence table, the dependence table is defined while regarding an application started by a running application as a dependent application.

26. The service management method according to claim 24, wherein:

in the step of defining the dependence table, a dependent application is defined by associating a dependent app identifier with each running application; and

in the step of identifying a dependent application, a dependent application is identified based on the dependent app identifier associated with an application being terminated.

27. The service management method according to claim 24, wherein any application started derivatively from a dependent application is a dependent application.

28. The service management method according to claim 24, wherein:

the dependence table identifies an independent application whose termination is independent of termination of any other applications; and

the method further comprises a step in which a communications unit starting an application prompts a user to confirm whether or not to start the application as an independent application.

29. The service management method according to claim 24, wherein:

the method further comprises a step in which a communications unit instructing another communications unit to start an application derivatively from a running application confirms a user confirmation identifier of the running application; and

in the step of defining the dependence table, if it is confirmed that the running application is an application that has been started without user'"'"'s confirmation, the dependence table is defined while regarding the application started derivatively from the running application as a dependent application.

30. The service management method according to claim 24, further comprising a step in which a communications unit starting an application derivatively from another application running on another communications unit determines whether or not to start the derivative application based on the number of generations notified by the other communications unit.

31. The service management method according to claim 24, further comprising a step in which a communications unit starting an application derivatively from another application running on another communications unit determines whether or not to start the derivative application based on the number of applications registered in the dependence table.

32. The service management method according to claim 24, wherein the dependence table identifies an independent application whose termination is independent of termination of any other applications, the method further comprising:

a step in which a communications unit terminating an independent application requests another communications unit executing another independent application started derivatively from the independent application to notify the communications unit of a progress of the service;

a step in which the communications unit terminating the independent application receives the notification of the progress of the service from the other communications unit; and

a step in which the communications unit receiving the service progress notification request notifies the communications unit of the progress of the service at a predetermined time.

33. The service management method according to claim 24, wherein an application started by a user for initiating the service is handled as a root application, the method further comprising:

a step in which each communications unit detects whether or not a communications abnormality has occurred;

a step in which a communications unit that has detected a communications abnormality notifies the communications unit executing the root application of the communications abnormality;

a step in which each communications unit identifies an independent application whose termination is independent of termination of any other applications involved in the service; and

a step in which if a communications unit executing the root application is notified of a communications abnormality by another communications unit, the communications unit instructs other communications units to terminate any independent application identified in the step of identifying an independent application and any dependent application dependent on the root application.

34. The service management method according to claim 24, further comprising a step in which if a management server in which all independent applications involved in the service are registered is instructed by a user to terminate the service, the management server terminates all of the registered independent applications.

35. A communications unit connected to a network for providing an intended service by executing an application in cooperation with at least one other communications unit connected to the network, the communications unit comprising:

dependence table definition means for defining a dependence table identifying dependencies between applications being executed by the communications units on the network;

dependent app identification means for, when terminating a running application, referencing the dependence table to identify a dependent application dependent on the application being terminated;

termination request means for requesting a communications unit executing the dependent application identified by the dependent app identification means to terminate the dependent application; and

dependent app termination means for, when requested by another communications unit on the network to terminate a dependent application, terminating the dependent application.

36. An integrated circuit for use in a communications unit connected to a network for providing an intended service by executing an application in cooperation with at least one other communications unit connected to the network, the integrated circuit comprising:

dependence table definition means for defining, in a storage device of the communications unit, a dependence table identifying dependencies between applications being executed by the communications units on the network;

dependent app identification means for, when terminating a running application, referencing the dependence table to identify a dependent application dependent on the application being terminated;

termination request means for requesting a communications unit executing the dependent application identified by the dependent app identification means to terminate the dependent application; and

dependent app termination means for, when requested by another communications unit on the network to terminate a dependent application, terminating the dependent application.