JP5628129B2 - Gateway management method, gateway management device, and gateway device - Google Patents

Description

  The present invention relates to a gateway management method, a gateway management device, and a gateway device, and in particular, can provide information necessary for setting a resource upper limit of an application created by a service provider to a service provider in response to a request from the service provider. The present invention relates to a gateway management method, a gateway management device, and a gateway device.

  Conventionally, a gateway device connecting a WAN (Wide Area Network) such as ADSL (Asymmetric Digital Subscriber Line), CATV (Community Antenna TeleVision), and FTTH (Fiber To The Home) and a LAN (Local Area Network) such as a home network, So-called triple play services such as IP (Internet Protocol) telephone, video (broadcasting, VoD (Video on Demand), etc.), data communication (Internet connection, etc.) have been provided.

  In recent years, in addition to the triple play service, means for dynamically expanding functions by installing and managing applications that control various devices connected to a home network has been proposed (for example, Patent Document 1). reference).

  The home network system in Patent Document 1 introduces an application server such as a gateway device equipped with an OSGi (Open Services Gateway Initiative) framework that supports integration of various home network middleware, and provides a middleware service for accessing various devices. By providing as a bundle function, a home network system that is not restricted by middleware is realized.

  However, in the OSGi framework described in Patent Document 1, various software components (referred to as OSGi bundles) are operated on a framework that operates on a single software process. There is a problem that it is impossible to know in detail whether to consume resources such as CPU and memory.

  To solve this problem, a means for obtaining the resource consumption of individual bundles as an average consumption at a plurality of gateways (see, for example, Patent Document 2) or a software process of a separate OSGi framework for each service provider is generated. A means for realizing smooth service operation by setting a predetermined upper limit value in a memory used for each service provider (a Java (registered trademark) heap memory) is disclosed (for example, see Patent Document 3). ing.

  Patent Document 2 is an operation method of a management system that obtains an analysis result on resource consumption of a plurality of gateways, and includes consumption information indicating consumption detected by the gateway from each of the gateways; An operation method of a management system is disclosed in which an execution program list indicating a program executed at the gateway at the time of detection is acquired and a record including an average consumption is created.

  In Patent Document 3, the upper limit of the memory that can be used for each service provider is managed, and when the application is started, the upper limit value of the heap is set by the start option of Java (registered trademark). A method for making an application unavailable is disclosed.

Japanese Patent Laid-Open No. 2004-213612 (FIG. 3) JP 2007-316947 A (FIG. 1) JP 2008-15594 A (FIG. 1)

  The methods disclosed in Patent Document 2 and Patent Document 3 have the following problems. First, the method disclosed in Patent Document 2 discloses a method of obtaining an average consumption amount of resources consumed by each program by collecting resources consumed by a plurality of programs and an execution program list from a plurality of gateway devices. However, it is an average consumption amount to the last, and there is no mention of a method for obtaining an actual measurement value of the consumed resource amount indicating how each program actually consumed the resource in each gateway device. That is, there is no disclosure of a method for performing strict resource management based on the actual measurement value of the consumed resource amount.

  Further, in the method disclosed in Patent Document 3, there is no mention of how to determine the upper limit of the memory that can be used by the application. In other words, considering the demarcation points between service providers and platform providers that provide application platforms such as gateway devices and OSGi frameworks, the upper limit of available memory for applications provided by service providers It is considered natural for a user to declare and set the maximum amount of memory required by the user to the platform operator. However, for example, when a service provider does not have an actual gateway device and develops an application using an emulator of the gateway device, it may be difficult to accurately declare and set the required memory upper limit. There is sex.

  The present invention is an invention for solving the above-described problem, and collects actual resource measurement values necessary for executing application software created by a service provider from a gateway device in response to a request from the service provider, It is an object of the present invention to provide a gateway management method, a gateway management device, and a gateway device that can provide actual measured values of resources to a service provider.

  In order to achieve the above object, the gateway management method of the present invention manages an application, which is application software provided to a gateway device by a service provider, and measures resources required when the application is executed in the gateway device. A gateway management method for a gateway management apparatus for notifying a service provider of a value, wherein the gateway management apparatus manages each application provided by a service provider from a service provider server in association with the service provider. It has information (for example, service management table 2000), and associates the number of devices of the gateway device in which each application is executed with the actual measured resource value required when each application is executed. Storage unit (for example, service management DB 110) having the measured resource total management information (for example, actual resource information total management table 2200), and the gateway management apparatus executes each installed application from each gateway apparatus. The actual measured resource value required at the time is received, the actual measured resource aggregation management information is updated based on the received actual resource value (for example, step S2504), and the number of application devices registered in the application management information is updated. It is determined whether or not a predetermined value has been reached, and an actual resource value is notified to the service provider registered in the application management information for the application that has reached the predetermined value (for example, step S2508).

  According to the present invention, in response to a request from a service provider, it is possible to collect actual measured values necessary for executing application software created by the service provider from the gateway device and to provide the actual measured values to the service provider. can do.

It is a figure showing an example of functional composition and network composition in this embodiment. It is a figure which shows an example of the hardware constitutions of the gateway management apparatus and gateway apparatus in this embodiment. It is a figure which shows the whole available resource table of a gateway apparatus. It is a figure which shows the available resource table of a gateway apparatus. It is a figure which shows the required resource table of a gateway management apparatus. It is a figure which shows the processing flow of the new service introduction process to the gateway apparatus by an application distribution management part. It is a figure which shows the processing flow of the starting process of the service application by an application management part. It is a figure which shows the dependency relationship table of a gateway management apparatus. It is a figure which shows the introduction service application dependence management table of a gateway apparatus. It is a figure which shows the process ID management table of a gateway apparatus. It is a figure which shows an example of the screen display which can introduce a new introduction desired service. It is a figure which shows an example of the screen display which cannot introduce a new introduction desired service. It is a figure which shows an example of the function structure in this embodiment. It is a figure which shows the processing flow of the starting process of a service application in the environment where CABI and CABI-DMEL cannot be used. It is a figure which shows the processing flow of the memory usage-amount monitoring process of a service application in the environment where CABI and CABI-DMEL cannot be used. It is a figure which shows the processing flow of the CPU usage rate monitoring process of a service application in the environment where CABI and CABI-DMEL cannot be used. It is a figure which shows the sequence corresponding to the processing flow which shows the new service introduction process shown in FIG. It is a figure which shows the processing flow of the abnormality notification process of an application management part. It is a figure which shows the other processing flow of the abnormality notification process of an application management part. It is a figure which shows the service management table of a gateway management apparatus. It is a figure which shows the actual measurement resource information table of a gateway apparatus. It is a figure which shows the measurement resource information total management table of a gateway management apparatus. It is a figure which shows the processing flow of the new service registration process to the gateway management apparatus by an application registration management part. It is a figure which shows the processing flow of the measurement resource amount measurement process in a gateway apparatus. It is a figure which shows the processing flow of the measurement resource amount totaling process in a gateway management apparatus.

Embodiments of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a diagram illustrating an example of a functional configuration and a network configuration in the present embodiment. The gateway management system includes a gateway management device 100, a gateway device 200 in a plurality of user homes 50, and a plurality of service provider servers 40. In the user home 50, the gateway device 200 is connected to a plurality of home devices 240 via the user home network 230.

  The gateway management device 100, the service provider server 40, and the gateway device 200 are connected to a closed network such as FLET'S (registered trademark) or an external network 30 including the Internet, and exchange information according to a predetermined procedure. be able to.

  The gateway device 200 and the home device 240 are installed in the user home 50 and are connected to a user home network 230 configured by wire or wireless, and can exchange information according to a predetermined procedure.

  The gateway device 200 is connected to both the external network 30 and the user home network 230, and is a gateway for exchanging information with a device connected to the external network 30 for a device installed in the user home 50. As a function.

  As a processing unit, the gateway management device 100 receives a request from the service provider server 40 and performs an application registration management unit 101 that performs a new service registration process S2300 (see FIG. 23) in the gateway management device 100, and the gateway device 200. An application distribution management unit 102 that performs a new service introduction process S600 (see FIG. 6), an actually measured resource amount totaling process S2500 (see FIG. 25) received from the gateway device 200, and the DB management unit 103 are included. DB is an abbreviation for Data Base.

  The gateway management apparatus 100 has a service management DB 110. The service management DB 110 includes a service management table 2000 (application management information) (see FIG. 20), an actual resource information aggregation management table 2200 (an actual resource aggregation management information). (See FIG. 22), a necessary resource table 500 (resource management information) (see FIG. 5), and a dependency relationship table 800 (see FIG. 8) are stored.

  The gateway device 200 includes, as processing units, an application execution unit 210 that executes the service application 211 and an application management unit 220 that manages the status of the service application 211.

  The application management unit 220 includes a service application activation process S700 (see FIG. 7), a service application activation process S1400 (see FIG. 14), a memory usage monitoring process S1500 (see FIG. 15), and a memory usage monitoring process S1600 (see FIG. 16). ), Abnormality notification processing S1800 (see FIG. 18), abnormality notification processing S1900 (see FIG. 19), measured resource amount measurement processing S2400 (see FIG. 24), and the like.

  The gateway device 200 has a gateway management DB 250. The gateway management DB 250 includes an actual resource information table 2100 (actual resource device information) (see FIG. 21), an overall available resource table 300 (see FIG. 3), and usage. A possible resource table 400 (see FIG. 4), an introduction service application dependency management table 900 (see FIG. 9), and a process ID management table 1000 (see FIG. 10) are stored.

  FIG. 2 is a diagram illustrating an example of a hardware configuration of the gateway management apparatus 100 and the gateway apparatus 200. The gateway management device 100 includes an EPROM 11, a CPU 12, a main memory 13, a bus 14, a nonvolatile storage device 15, a peripheral control device 16, and a network I / F 17. The EPROM 11, the CPU 12, the main memory 13, and the peripheral control device 16 are connected to the bus 14, and the nonvolatile storage device 15 and the network I / F 17 are connected to the bus 14 via the peripheral control device 16, and information is transmitted according to a predetermined procedure. Can be exchanged. EPROM is an abbreviation for Erasable Programmable Read Only Memory, CPU is an abbreviation for Central Processing Unit, and I / F is an abbreviation for Interface.

  The gateway device 200 includes an EPROM 21, a CPU 22, a main memory 23, a bus 24, a nonvolatile storage device 25, a peripheral control device 26, a network I / F 27, and a network I / F 28. EPROM 21, CPU 22, main memory 23, and peripheral control device 26 are connected to bus 24, and network I / F 27, network I / F 28, and nonvolatile storage device 25 are connected to bus 24 via peripheral control device 26, Information can be exchanged according to a predetermined procedure.

  In the gateway management apparatus 100, the EPROM 11 stores a boot program. The nonvolatile storage device 15 stores various programs. When the gateway management device 100 is activated, various programs are read from the nonvolatile storage device 15 to the main memory 13 by a boot program stored in the EPROM 11. The CPU 12 transmits and receives signals to the network I / F 17 by executing various programs read to the main memory 13.

  The network I / F 17 is connected to the external network 30, and can exchange information with devices connected to the external network 30. The network I / F 17 can be realized by a network card or the like.

  As described above, the nonvolatile storage device 15 stores various programs that the CPU 12 reads into the main memory 13 and executes them, and can be realized by a flash memory or an HDD (hard disk drive).

  In the gateway device 200, the EPROM 21 stores a boot program. Various programs are stored in the nonvolatile storage device 25. When the gateway device 200 is activated, various programs are read from the nonvolatile storage device 25 to the main memory 23 by a boot program stored in the EPROM 21. The CPU 22 transmits and receives signals to the network I / F 27 and the network I / F 28 by executing various programs read to the main memory 23.

  The network I / F 27 is connected to the external network 30 and can exchange information with a device connected to the external network 30. The network I / F 27 can be realized by a network card or the like.

  The network I / F 28 is connected to the network 230 in the user's home 50 and can exchange information with devices connected to the user's home network 230. The network I / F 28 can be realized by a network card or the like.

  As described above, the nonvolatile storage device 25 stores various programs that the CPU 22 reads into the main memory 23 and executes them, and can be realized by a flash memory or an HDD (hard disk drive). Although not shown, the hardware configuration of the service provider server 40 is the same as that of a normal PC (Personal Computer).

  Next, in the present embodiment, each table handled by the gateway management device 100 and the gateway device 200 will be described.

  FIG. 3 is a diagram showing the entire available resource table 300 of the gateway device 200. The overall available resource table 300 is a table indicating the amount of resources that can be used by the entire application service. The overall available resource table 300 includes items such as an overall available CPU usage rate 301 and an overall available memory amount 302. Specifically, the row 303 shows that the total available CPU usage rate is 50% and the total available memory amount is 30 MB.

  FIG. 4 is a diagram showing an available resource table 400 of the gateway device 200. The available resource table 400 is a table for managing resources that can be used by individual application services. The available resource table 400 includes items such as an ID 401, an available heap memory amount 402, an available memory amount 403, and an available CPU usage rate 404. Specifically, when the ID of the row 405 is “000”, the available heap memory amount is 6 MB, the available memory amount is 15 MB, and the available CPU usage rate is 20%. When the ID of the row 406 is “003”, the available heap memory amount is 3 MB, the available memory amount is 6 MB, and the available CPU usage rate is 10%.

  FIG. 5 is a diagram showing the necessary resource table 500 of the gateway management apparatus 100. The necessary resource table 500 is a table for managing resources that can be used by individual application services managed by the gateway management apparatus 100. The required resource table 500 includes items such as ID 401, required heap memory amount 502, required memory amount 503, and required CPU usage rate 504. Specifically, as the required resource of the service application 211 provided by a plurality of service provider servers 40, when the ID of the row 506 is “001”, the required heap memory amount is 1 MB, the required memory amount is 2 MB, and the required amount The CPU usage rate is 10%. When the ID of the row 507 is “002”, the required heap memory amount is 4 MB, the required memory amount is 10 MB, and the required CPU usage rate is 30%.

  Furthermore, the ID “000” in the row 505 corresponds to “000” in the row 405 shown in FIG. 4, the ID “003” in the row 508 corresponds to “003” in the row 406 shown in FIG. The ID “010” in the row 509 corresponds to “010” in the row 407 shown in FIG.

  FIG. 8 is a diagram illustrating the dependency relationship table 800 of the gateway management apparatus 100. The dependency relationship table 800 is a table for managing dependency relationships between service applications. The dependency relationship table 800 includes items such as ID 401, Import-Package 802, and Export-Package 803.

  Import-Package 802 indicates a package necessary for using the bundle specified by ID 401, in other words, a package on which this bundle depends. In the example of line 804, Import-Package is org.osgi.framework, which means that it depends on a package called org.osgi.framework. Export-Package 803 indicates a package released to another bundle. In line 804, Export-Package is org.osgi.service.http, and a package org.osgi.service.http is released outside the bundle. Conversely, a package not declared in Export-Package 803 means that it cannot be accessed from another bundle.

  FIG. 9 is a diagram showing an introduction service application dependency management table 900 of the gateway device 200. The installed service application dependency management table 900 is a table for managing the dependency between service applications installed in the gateway device 200. The installed service application dependency management table 900 includes items such as ID 401, Import-Package 902, and Export-Package 903.

  FIG. 10 is a diagram showing a process ID management table 1000 of the gateway device 200. The process ID management table 1000 is a table for managing process IDs corresponding to the service application 211. The process ID management table 1000 includes items such as ID 401 and process ID 1002.

  FIG. 20 is a diagram showing the service management table 2000 of the gateway management apparatus 100. The service management table 2000 (application management information) is a table that manages the correspondence between service names, service provider names, and service IDs. The service management table 2000 includes items such as a service name 2001, a service provider name 2002, and an ID 401. Specifically, the service name “home control” is a service provided by a service provider of “Home Operation Co., Ltd.”, and the service name “healthcare” is “Health No. 1 Co., Ltd.” This service is provided by the service provider.

  FIG. 21 is a diagram showing an actually measured resource information table 2100 of the gateway device 200. The measured resource information table 2100 (measured resource device information) is a table for managing measured resource information corresponding to the ID 401. The actual resource information table 2100 includes items such as ID 401, actual heap memory amount 2101, actual memory amount 2102, actual CPU usage rate 2103, and operation time 2104.

  FIG. 22 is a diagram showing an actually measured resource information aggregation management table 2200 of the gateway management apparatus 100. The actually measured resource information total management table 2200 (actual resource total management information) is an actual resource information total management table of the number of investigation devices corresponding to the ID 401. The measured resource information aggregation management table 2200 includes an ID 401, the number of investigation devices 2201, a measured heap memory amount maximum value 2202, a measured heap memory amount average value 2203, a measured memory amount maximum value 2204, a measured memory amount average value 2205, and a measured CPU usage. There are items such as a maximum rate value 2206 and a measured CPU usage rate average value 2207. Specifically, referring to the row 2208, when the ID is “010”, the number of investigation devices is 15, and the maximum value and the average value of each resource are aggregated. For example, the maximum value of the actually measured heap memory amount is 0.5 MB, and the average value of the actually measured heap memory amount is 0.35 MB. From this, referring to FIG. 20 and FIG. 22, it is possible to obtain the maximum value and the average value of each resource with high accuracy when the service name with ID “010” operates “home control”.

Next, the operation of the processing unit of each apparatus according to the present embodiment will be described with reference to FIG.
The gateway management apparatus 100 has a function as a service service application distribution base for distributing service applications provided by service providers holding various service provider servers 40 to the gateway apparatus 200 via the external network 30. Yes. The service provider holding the service provider server 40 includes setting up a service application distribution server or the like by entrusting the distribution of the created service application 211 to the gateway management apparatus 100, and an application execution unit 210. There is no need to distribute the gateway device 200 or the like to the user, and the service can be provided at a reduced cost.

  The gateway device 200 includes an application execution unit 210 that executes various service applications 211. The application execution unit 210 can be realized using, for example, an application execution platform such as the OSGi (registered trademark) framework. By executing the service application 211 distributed by the gateway management apparatus 100, various application devices The function of the gateway device 200 can be flexibly expanded, such that 240 can be controlled via the user home network 230.

  When the OSGi framework is used as the application execution unit 210, the normal OSGi framework can execute a plurality of service applications 211 on a single framework. However, it is assumed that the application execution unit 210 is activated separately for each service application 211 in order to control resources such as the CPU processing time (CPU usage rate) and the amount of used memory of the gateway device 200 to be used in detail.

  An application execution platform such as the OSGi framework allows various service applications 211 to appropriately call each other's functions. For example, an HTTP service defined by the OSGi service platform specification as a standard has functions of a WEB server and a servlet container, and another service application 211 implemented as a servlet registers itself in a servlet container function provided by the HTTP service. Thus, the service provider providing the service application 211 can easily use the functions of the WEB server and the servlet container.

  When the application execution unit 210 is activated for each service application 211, the cooperation function between the service applications 211 as described above cannot be used normally. However, the OSGi service platform specification R4.2 has a standard service similar to the HTTP service. As a remote service specification has been added. The remote service makes it possible to share the Import / Export function of the OSGi core service with an OSGi framework that operates on a different Java (registered trademark) VM.

  In the present embodiment, unless otherwise specified, the application execution unit 210 is realized using the OSGi framework, and the application execution unit 210 differs depending on the application management unit 220 for each of various service applications 211 (different software processes). ) It is assumed that a plurality of application execution units 210 executed and activated above can cooperate with each other using a remote service, which is a standard service of the OSGi service platform.

  In the present embodiment, the service application 211 includes one or a plurality of programs (referred to as software parts or OSGi bundles). In this embodiment, it is assumed that one application execution unit 210 operates one service application 211. However, a plurality of service applications 211 can be executed by one application execution unit 210. For example, the same application execution unit can be used for each provider of the service application 211.

  In the present embodiment, resources such as CPU usage rate and memory usage can be managed for each application execution unit 210. For example, as described above, when the same application execution unit 210 is used for each provider of the service application 211, when the available resource amount is exceeded, the service application 211 provided by the service application provider is provided. I understand that there will be a problem with either.

  When a plurality of service applications 211 are executed by a single application execution unit 210, the number of executions of a program (such as JavaVM or OSGi framework) that realizes the application execution unit 210 in the entire gateway device decreases, and the memory in the entire device correspondingly. Although there is an effect that the usage amount can be saved, in the present embodiment, it is assumed that one service application operates in one application execution unit in order to simplify the description.

  In addition, the gateway device 200 according to the present embodiment assumes a configuration capable of appropriately controlling the CPU usage rate, the memory usage amount, and the Java heap memory usage upper limit value of each software process executed by the application execution unit 210. .

  For example, when the OS (basic software) of the gateway device 200 is Linux (registered trademark), the CPU usage rate of the software process can be controlled using a CPU resource management system such as CABI (CPU Accounting and Blocking Interface). is there. CABI can set the upper limit of CPU usage time in a certain cycle. For example, for a certain software process, CABI AO (accounting object) having a cycle of 100 ms and upper limit of CPU usage time of 30 ms is set. In this case, if the CPU is used for 30 ms during 100 ms, the use of the CPU after 30 ms is blocked, and the CPU resources are released to other processes. In the present embodiment, it is assumed that the OS of the gateway apparatus 200 is Linux and CABI is used for CPU resource management unless otherwise specified. However, for example, other real-time OSs also use the same mechanism. May be possible.

  For example, when the OS (basic software) of the gateway device 200 is Linux, the memory usage of the software process is a memory such as CABI-DMEL (Common resource management Accounting and Blocking Interfaces-Dependable Memory management system for Embedded Linux). Control is possible using a resource management system. The CABI-DMEL can limit the upper limit of physical memory allocation to a certain software process, and can block memory allocation when attempting to secure memory above the upper limit. In the present embodiment, it is assumed that the OS of the gateway device 200 is Linux and CABI-DMEM is used for memory resource management unless otherwise specified. For example, a similar mechanism is used in other OSs as well. May be possible.

  In the present embodiment, it is assumed that the application execution unit 210 is realized using the OSGi framework, but the OSGi framework is started using Java VM (Java Virtual Machine). JavaVM can specify the upper limit of the heap memory that can be used by the program to be executed, and can block the use of heap memory that exceeds the set upper limit value.

  FIG. 13 is a diagram illustrating an example of a functional configuration according to the present embodiment. FIG. 13 is a functional configuration diagram of the gateway device 200 when a Java VM, an OSGi framework (OSGi Framework), and a remote service bundle that is a standard service of OSGi are used as programs for realizing the application execution unit 210.

  Each time the service application 211 is executed, the Java VM and the OSGi framework are activated, the remote service bundle operates on each OSGi framework, and each service application 211 on the OSGi framework of each application execution unit 210a, 210b, 210c. Is working.

  OSGi can normally call each other's functions (services) between programs (bundles) running on the OSGi framework running on the same JavaVM, but OSGi running on different JavaVMs using remote services. Functions (services) of the service application 211 that can exchange information on functions (services) between the frameworks and that are executed on the OSGi framework in which the remote service has been introduced. Can be used. In addition, the application management unit 220 performs management such as activation processing of the application execution units 210a, 210b, and 210c.

  FIG. 23 is a diagram showing a processing flow of new service registration processing S2300 to the gateway management apparatus 100 by the application registration management unit 101. FIG. 23 is a flowchart illustrating a procedure in which the application registration management unit 101 of the gateway management apparatus 100 registers a new service in the gateway management apparatus 100 based on information received from the service provider server 40 of the service provider.

  In step S2301, information on a service newly registered from the service provider server 40 of the service provider by the application registration management unit 101 of the gateway management apparatus 100, that is, a service provider name, a service application program, a service name, and a necessary heap This is a process of receiving information on the amount of memory, the amount of required memory, the required CPU usage rate, and the presence / absence of actual measurement resource measurement.

  Step S2302 is processing in which the application registration management unit 101 newly determines the ID of the service application. As the ID, a value that has not been registered as an ID corresponding to the service name described in the service management table 2000 (see FIG. 20) is selected.

  In step S2303, the application registration management unit 101 adds a service name, a service provider name, and the ID determined in step S2302 to the service management table 2000.

  In step S2304, the application registration management unit 101 adds the ID, the required heap memory amount, the required memory amount, and the required CPU usage rate to the required resource table 500 (see FIG. 5).

  If the measured resource measurement designation is included in the information received from the service provider (step S2305, Yes), the process proceeds to step S2306. If there is no measured resource measurement designation (step S2305, No), the process is terminated.

  In step S2306, the application registration management unit 101 creates a new record in the actually measured resource information total management table 2200 (see FIG. 22), adds an ID, and sets 0 as an initial value to the number of corresponding investigation devices. It is processing.

  FIG. 6 is a diagram illustrating a process flow of the new service introduction process S600 to the gateway apparatus 200 by the application distribution management unit 102. FIG. 6 is a flowchart showing a procedure until the service selected by the user is introduced into the gateway device 200 via the gateway management device 100. Hereinafter, the description of FIG. 6 is processing of the application distribution management unit 102 unless otherwise specified, and steps S609 to S611 are processing of the gateway device 200.

  When the service user accesses the gateway device 200 from a PC that is one of the home appliances 240, a service application management screen is displayed. The service application management screen displays a list of service applications that are currently installed and a list of service applications that are not yet installed. The service application list displays whether the service application is charged or free, whether there is a free trial period even if there is a charge, and what the service contents are. The service user selects the service name “healthcare” (see FIG. 20) as a service application desired to be introduced, for example, a free service for three months.

  Step S601 is processing in which the application distribution management unit 102 acquires the ID (A) of a service application that is desired to be newly installed by the service user.

  In step S602, the application distribution management unit 102 uses the information (the total available CPU usage rate and the total available memory amount) (B) described in the total available resource table 300 (see FIG. 3) from the gateway device 200, and the usage. This is a process of acquiring a list of IDs (C) described in the possible resource table 400 (see FIG. 4).

  Step S603 is a process in which the application distribution management unit 102 checks the application dependency when a service application is newly installed, and extracts the ID of an application that needs to be installed in addition to the application that the user desires to newly install. That is, using the ID (A) of the service application desired to be newly installed, the ID list (C) of the service application already installed in the gateway device 200, and the information (D) described in the dependency table 800, When installing a service application, check whether there is an additional required service application. If there is, add the ID (A) of the service application desired to be newly installed and the ID of the service service application required for the addition, A process of extracting ID list of service applications to be introduced into Towei device 200 (E).

  Step S604 is processing in which the application distribution management unit 102 calculates the total number of resources required when introducing the new installation desired service application into the gateway apparatus 200, that is, refers to the necessary resource table 500, and refers to the gateway apparatus. The required memory amount for the ID list (C) already installed in 200 and the total required CPU usage rate (F), and the required memory amount and the total required CPU usage rate (G) for the ID list (E) desired to be newly introduced. This is a calculation process.

  Step S605 is a process in which the application distribution management unit 102 compares the total amount of required resources when a new installation desired service application is installed with the total amount of resources (B) that can be used in the gateway device 200, that is, This is processing for comparing the total amount of available resources (B) with the total amount of memory and CPU usage (F + G) required after the introduction of a service application to be newly introduced.

  In step S606, as a result of the comparison in step S605, the application distribution management unit 102 determines whether or not the required resource amount when the newly installed desired service application is within the range of the total resource amount usable in the gateway device 200. This is a process of checking, that is, a process of checking whether F + G <B is satisfied for each of the memory amount and the CPU usage rate. If F + G <B is satisfied for each of the memory amount and the CPU usage rate (step S606, Yes), the process proceeds to step S607. If F + G <B is not satisfied for each of the memory amount and the CPU usage rate (step S606, No), the process proceeds to step S612.

  Step S607 is a process in which the application distribution management unit 102 presents to the service user via the gateway device 200 that a service application desired to be newly installed can be installed.

  Step S608 is processing in which the application distribution management unit 102 transmits a newly installed service application and related information to the gateway device 200, that is, the newly installed service application to the gateway device 200, the required memory amount of each of the service applications, and the necessary information. The required resource information (H) such as the CPU usage rate, the information (I) related to the dependency of each service application, and the actually measured resource information aggregation management table 2200 (see FIG. 22) are included, and the ID of the newly introduced service application is included. If it is, it is a process of transmitting (J) that the ID is necessary for collecting the actually measured resource information.

  Step S609 is processing in the application management unit 220 of the gateway device 200. The gateway device 200 adds H information to the available resource table 400 and I information to the introduction service application dependency management table 900.

  Step S610 is processing in the application management unit 220 of the gateway device 200. When the gateway device 200 has information indicating that it is necessary to collect actual resource information (J), a new record is created in the actual resource information table 2100, the corresponding ID is added, and the operation time is an initial value. This is a process of setting to 0.

  Step S611 is processing in the application management unit 220 of the gateway device 200. This is a process in which the gateway device 200 activates the service application. Then, after the process of step S611, the series of processes ends.

  Step S612 is a process of presenting to the service user via the gateway device 200 that the service application desired to be newly installed cannot be installed. Then, after the process of step S612, the series of processes ends.

  In step S604 in FIG. 6, the required memory amount is used as the memory usage amount, but there is no description of the required memory amount in the required resource table 500 (see FIG. 5), and only the required heap memory amount is described. The necessary heap memory amount may be used as the memory usage amount. Further, the necessary heap memory amount does not include the memory amount used by JavaVM itself, but may be used as the memory usage amount with some expectation of the memory amount that JavaVM will use. For example, assuming that JavaVM uses the same amount of memory as the required heap memory amount, the required memory amount may be twice the required heap memory amount.

  FIG. 11 is a diagram illustrating an example of a screen display on which a new introduction desired service can be introduced. FIG. 11 is an example of a screen image of information that the gateway management device 100 presents to the service user via the gateway device 200 in step S607 in FIG. Specifically, the screen displays “Check that there is enough resources to execute the selected service. Install the selected service on the gateway device”.

  FIG. 12 is a diagram illustrating an example of a screen display in which a new introduction desired service cannot be introduced. FIG. 6 is an example of a screen image of information presented to the service user by the gateway management apparatus 100 in step S612 in FIG. Specifically, the screen says “Could not confirm that there is enough resources to run the selected service. The selected service cannot be installed on the gateway device. Stop unnecessary services, etc. Please perform the service installation process again. "Is displayed.

  FIG. 17 is a diagram showing a sequence corresponding to the processing flow showing the new service introduction processing shown in FIG. Step S1701 is a process of selecting a service application desired to be newly installed by connecting to the gateway management apparatus 100 via the gateway apparatus 200 using the service user's PC. Step S1702 is processing in which the gateway management apparatus 100 obtains the service application ID (A), and corresponds to step S601.

  Step S1703 is processing in which the gateway management apparatus 100 requests the gateway apparatus 200 to transmit the information (B) described in the overall available resource information table and the list of IDs (C) described in the available resource table. .

  Step S1704 is processing in which the gateway device 200 transmits information (B) described in the overall available resource information table and a list of IDs (C) described in the available resource table to the gateway management device 100. This corresponds to S602.

  In step S1705, the gateway management apparatus 100 extracts a list (E) of IDs of service applications to be introduced into the gateway apparatus 200 using the list of IDs A and C and the information (D) described in the dependency relationship table. And corresponds to step S603.

  In step S1706, the gateway management apparatus 100 determines the total amount (F) of the required memory amount and the required CPU usage rate corresponding to the ID list of C for each of the required memory amount and the required CPU usage rate described in the required resource table. , A process for extracting the total (G) of the required memory amount and the required CPU usage rate corresponding to the ID list of E, and corresponds to step S604.

  Step S1707 confirms that the gateway management apparatus 100 does not exceed the total available resource amount for the memory amount and CPU usage rate of the gateway device 200 when a new service is introduced, that is, the required memory amount and the required CPU usage rate. This is a process for checking whether the sum of the value of F and the value of G does not exceed the value of the total available memory amount and the total available CPU usage rate in B, and corresponds to steps S605 and S606.

  Step S1708 is processing in which the gateway management apparatus 100 presents to the service user via the gateway apparatus 200 that a service application desired to be newly installed can be introduced, and corresponds to step S607.

  In step S1709, the gateway management apparatus 100 sends to the gateway apparatus 200 the information (H) corresponding to the ID of the service application among the information of the newly installed service application and the necessary resource table 500, and the information of the dependency table 800. With reference to the information (I) corresponding to the ID of the service application and the actually measured resource information aggregation management table 2200 (see FIG. 22), if the ID of the newly introduced service application is included, the ID is collected as the actually measured resource information. This is a process of transmitting (J) to the effect, and corresponds to step S608.

  Step S1710 is a process in which the gateway apparatus 200 adds the H information to the available resource table 400 and the I information to the introduction service application dependency management table 900, and corresponds to step S609.

  In step S 1711, when there is information indicating that the gateway device 200 needs to collect actually measured resource information (J), the corresponding ID is added to the actually measured resource information table 2100, and the operation time is set to 0 which is an initial value. This process starts the service application, and corresponds to step S610.

  FIG. 7 is a diagram showing a processing flow of service application activation processing S700 by the application management unit 220.

  In step S701, the application management unit 220 obtains the available heap memory amount, available memory amount, and available CPU usage rate corresponding to the ID of the service application 211 to be activated from the available resource table 400 (see FIG. 4). It is processing to do.

  In step S702, the application management unit 220 uses the CABI API (Application Program Interface) to generate an accounting object related to the available CPU usage value.

  In step S703, the application management unit 220 uses the CABI-DMEL API to generate an accounting object related to the available memory amount value.

  In step S704, the application management unit 220 sets the available heap memory amount to the maximum heap amount of the JavaVM activation option and starts the OSGi framework (application execution unit 210), and the service application is added to the OSGi framework. This is a process for installing and executing 211.

  In step S705, the application management unit 220 examines and acquires the process ID of the software process that executed the service application 211, and binds the process ID to CABI and CABI-DMEL accounting objects.

  Step S706 is processing in which the application management unit 220 stores the ID of the service application 211 and the process ID in the process ID management table 1000 (see FIG. 10).

  Here, operations of CABI and CABI-DMEL will be briefly described. CABI creates an accounting object using the period and CPU usage time as parameters, and binds the process to be controlled to the accounting object. For example, when the available CPU usage rate is 20%, a period of 100 ms and a CPU usage time of 20 ms are described.

  Normally, in a non-real-time OS such as Linux, if the CPU has a surplus capacity, a large amount of CPU resources (usage time) are allocated even for a process with a low priority. When CABI is used, even if the CPU has spare capacity, if the CPU resource for the time set in the accounting object is consumed, the process releases the task and does not use the CPU resource any more. In the case of using CABI, the set cycle and CPU usage time are the maximum available values. Even if the CPU for the set time is not used, if an interrupt is generated from a process with a higher priority, CPU resources are released even if the usage time is not reached.

  CABI-DMEL sets the amount of memory available for accounting objects. When a process to be controlled is bound to an accounting object, CABI-DMEL monitors the memory allocation / release of the process, and rejects any attempt to allocate a memory exceeding the set amount of memory. In this case, the process to be controlled has failed to secure the memory, and in some cases, the process itself may end abnormally. Logs and the like when CABI or CABI-DMEL is used can be recorded in a system log or the like and can be referred to from the application management unit.

  By performing new service introduction processing and service activation processing as shown in FIG. 6 and FIG. 7, resources used by the service application 211 operating on the gateway device 200 are appropriately controlled, and the required resource amount of the service application 211 is ensured. It can be secured.

  In the process of FIG. 6, whether or not the service application 211 can be distributed is determined by the gateway management apparatus 100 (for example, step S606), but this may be performed by the gateway apparatus 200.

  By transmitting the operation log of the service application 211 activated in the process of step S704 in FIG. 7 to the gateway management apparatus 100 or the service provider server 40 (service provider server), it can be used for maintenance management. is there. For example, when there is a service application 211 that attempts to use a resource exceeding the set upper limit value, it is possible to improve the quality of software by transmitting the log to the service provider server.

  24 and 25 are processes for investigating how much resource amount is actually used (actual resource amount) when the service application 211 installed in the gateway apparatus 200 is operated.

  FIG. 24 is a diagram illustrating a process flow of the actually measured resource amount measurement process S2400 in the gateway device 200. The actually measured resource amount measurement process S2400 is started when the gateway apparatus 200 is activated by the application management unit 220 of the gateway apparatus 200, and always performs a loop process while the gateway apparatus 200 is activated. The main components of the processing illustrated in FIG.

  Step S2401 is processing in which the application management unit 220 acquires all the IDs described from the actually measured resource information table 2100 (see FIG. 21).

  Step S2402 is processing in which the application management unit 220 refers to the process ID management table 1000 (see FIG. 10) and acquires a process ID corresponding to each ID acquired in step S2401.

  Step S2403 is processing in which the application management unit 220 acquires the heap memory amount, the memory amount, and the CPU usage rate of the process corresponding to each process ID. It can be realized by calling an OS function, a JavaVM function, or the like.

  In step S2404, the application management unit 220 checks whether the resource amount acquired in the current loop is larger than the resource amount acquired so far (takes the maximum value). This is a process of describing the resource amount in the actually measured resource information table 2100, that is, the heap measured in the current loop with respect to the actually measured heap memory amount, the actually measured memory amount, and the actually measured CPU usage rate corresponding to each ID in the actually measured resource information table 2100. If the amount of memory, the amount of memory, and the CPU usage rate are large, each value in the actually measured resource information table 2100 is updated. Processing stop time (sleep time, for example, 10 seconds, 1 minute, 1 While in such a set) is added process.

  Step S2405 is a process in which the application management unit 220 collects the actual resource information for a sufficient period, and then transmits the information to the gateway management apparatus. That is, the operation time for each ID in the actual resource information table 2100 If the measured resource measurement time determined by the system in advance (for example, 1 day, 1 week, etc.) is exceeded, the ID row information (ID, measured heap memory amount, measured memory amount, measured CPU usage rate) is gateway-managed This is a process for transmitting to the device and deleting the ID line.

  Step S2406 is processing in which the application management unit 220 sleeps in advance as a predetermined stop time (the stop time referred to in step S2404). Then, the process returns to step S2401.

  FIG. 25 is a diagram showing a process flow of the measured resource amount totaling process S2500 in the gateway management apparatus 100. This will be described with reference to FIG. The gateway management device 100 receives and aggregates the measured resource amounts from the plurality of gateway devices 200. All of the processes described in FIG. 25 are the application distribution management unit 102.

  The application distribution management unit 102 collects the measured resource information of the service application that is required to collect the measured resource information according to the designation of the service provider from the many gateway devices 200 that distributed the service application, and the maximum value and the average value thereof. Is calculated and recorded in the actually measured resource information aggregation management table 2200 (see FIG. 22). In addition, when the application distribution management unit 102 collects measured resource information from a sufficient number of gateway devices 200, the application distribution management unit 102 transmits the result to a service provider that provides the corresponding service application.

  Step S2501 is a process in which the application distribution management unit 102 receives the actually measured resource information sent by the process in step S2405 of FIG. 24, and step S2502 is a process of reading the ID described in the received actually measured resource information. is there.

  In step S2503, the application distribution management unit 102 updates the maximum value of each resource in the actual resource information aggregation management table 2200 (see FIG. 22), that is, the received actual resource information and the actual resource information aggregation management table 2200. And the measured heap memory amount, the measured memory amount, and the measured CPU usage rate of the received measured resource information are the maximum measured heap memory amount and the maximum measured memory amount described in the measured resource information aggregation management table 2200. If the value is larger than the actual measured CPU usage rate maximum value, each maximum value is updated.

  Step S2504 is processing in which the application distribution management unit 102 updates the average value of each resource in the actually measured resource information totaling management table 2200 (see FIG. 22). That is, the actual resource information is totaled based on the received actual resource information. This is a process of recalculating the average value of each resource in the ID row of the management table 2200. For example, the measured memory average value of the service application whose ID is “010” can be calculated by the following calculation formula.

((Number of surveyed devices in table 2200 × average value of actually measured memory in table 2200) + actually measured memory in received resource information) / (number of surveyed devices in table 2200 + 1)
The table names in the calculation formula are abbreviated.

  The measured heap memory amount and the measured CPU usage rate can be calculated in the same procedure.

  Step S2505 is processing in which the application distribution management unit 102 increments the number of investigation devices in the corresponding ID row of the actually measured resource information total management table 2200 by 1 (adds the device received this time).

  Step S2506 is processing in which the application distribution management unit 102 confirms whether or not a sufficient amount of actually measured resource information can be aggregated for the service application with the relevant ID, that is, in the relevant ID row of the actually measured resource information summary management table 2200. If the number of survey devices has reached a certain number (for example, 10, 100, 1000, etc.) determined in advance by the system (step S2506, Yes), the process proceeds to step S2507, and the measured resource information aggregate value of the corresponding ID row is set as the service business. Send to the person. If the number of investigation devices has not reached the predetermined number determined in advance by the system (step S2506, No), the process is terminated.

  Step S2507 is processing in which the application distribution management unit 102 acquires information about the service provider that transmits the measured resource information aggregate value, that is, the service name and service provider name corresponding to the ID from the service management table 2000. Is the process of reading out.

  In step S2508, the application distribution management unit 102 transmits information described in the measured resource information total management table 2200 to the corresponding service provider as the measured resource total information of the service application with the service name.

  In FIG. 25, the application distribution management unit 102 of the gateway management apparatus 100 transmits the measured resource aggregate information to the service provider when the number of surveyed devices reaches a certain number, but the application distribution management unit 102 sends the measured resource to the service provider. The timing for transmitting the total information may be, for example, when a service provider makes an inquiry to the gateway management apparatus after a predetermined period (for example, one week, one month, etc.) determined in advance by the system. In that case, items and processing of the actually measured resource information aggregation management table 2200 are changed as appropriate.

  FIGS. 14, 15, and 16 are diagrams showing service application activation processing, memory usage monitoring processing, and CPU usage monitoring processing in an environment where CABI and CABI-DMEL cannot be used.

  FIG. 14 is a diagram showing a processing flow of service application activation processing S1400 in an environment where CABI and CABI-DMEL cannot be used.

  Step S1401 is a process in which the application management unit 220 acquires the available heap memory amount corresponding to the ID of the service application to be activated from the available resource table 400 (see FIG. 4).

  In step S1402, the application management unit 220 sets the available heap memory amount to the maximum heap amount of the JavaVM activation option, starts the OSGi framework (application execution unit), and loads the service application in the OSGi framework. Installation and execution process.

  In step S1403, the application management unit 220 investigates and acquires the process ID of the software process that executed the service application. This is a process of storing the service application ID and the process ID in the process ID management table 1000 (see FIG. 10).

  FIG. 15 is a diagram showing a processing flow of the memory usage monitoring process S1500 in an environment where CABI and CABI-DMEL cannot be used.

  Step S1501 is processing in which the application management unit 220 checks whether there is a service application ID for which regular monitoring has not been completed in the process ID management table 1000 (see FIG. 10). If there is a service application ID for which periodic monitoring has not been completed in the process ID management table 1000 (step S1501, Yes), the process proceeds to step S1502. Alternatively, if there is no service application ID for which periodic monitoring has not been completed in the process ID management table (step S1501, No), the process proceeds to step S1508.

  Step S1502 is a process in which the application management unit 220 acquires from the process ID management table 1000 the ID of a service application that has not been periodically monitored and the process ID corresponding to the service application ID.

  Step S1503 is processing in which the application management unit 220 acquires the memory usage of the process corresponding to the process ID.

  Step S1504 is a process in which the application management unit 220 checks whether the memory usage exceeds the available memory size corresponding to the service application ID. When the memory usage exceeds the available memory corresponding to the service application ID (step S1504, Yes), the process proceeds to step S1505. If the memory usage does not exceed the available memory corresponding to the service application ID (step S1504, No), the process proceeds to step S1508.

  Step S1505 is processing in which the application management unit 220 forcibly terminates the service application corresponding to the service application ID.

  In step S1506, the application management unit 220 determines that the service application ID from the available resource table 400 (see FIG. 4), the installed service application dependency management table 900 (see FIG. 9), and the process ID management table 1000 (see FIG. 10). This is a process for deleting an item corresponding to.

  In step S1507, the application management unit 220 records in the system log or the like that the service application has been forcibly terminated due to an excess of available memory usage. Step S1508 is processing in which the application management unit 220 stops for a predetermined time. Thereafter, the process returns to step S1501.

  FIG. 16 is a diagram showing CPU usage rate monitoring processing S1600 in an environment where CABI and CABI-DMEL cannot be used.

  Step S1601 is processing in which the application management unit 220 acquires the load average of the CPU of the gateway device 200. The load average is a value representing the average number of processes waiting to be executed, and means a load average. Usually used as an indicator of server load. If this value is large, the load is large, and if it is small, the load is small.

  Step S1602 is a process in which the application management unit 220 checks whether load average> 1. If load average> 1 (step S1602, Yes), the process proceeds to step S1603. If load average> 1 is not satisfied (step S1602, No), the process proceeds to step S1609.

  Step S1603 is processing in which the application management unit 220 checks whether there is a service application ID for which regular monitoring has not been completed in the process ID management table 1000 (see FIG. 10). If there is a service application ID that has not been periodically monitored in the process ID management table 1000 (step S1603, Yes), the process proceeds to step S1604. Alternatively, if there is no service application ID for which periodic monitoring has not been completed in the process ID management table 1000 (step S1603, No), the process proceeds to step S1609.

  In step S1604, the application management unit 220 acquires from the process ID management table 1000 the ID of a service application that has not been periodically monitored and the process ID corresponding to the service application ID.

  Step S1605 is processing in which the application management unit 220 acquires the CPU usage rate of the process corresponding to the process ID.

  In step S1606, the application management unit 220 checks whether the CPU usage rate exceeds the available CPU usage rate corresponding to the service application ID. When the CPU usage rate exceeds the available CPU usage rate corresponding to the service application ID (step S1606, Yes), the process proceeds to step S1607. If the CPU usage rate does not exceed the available CPU usage rate corresponding to the service application ID (step S1606, No), the process proceeds to step S1609.

  Step S1607 is processing in which the application management unit 220 lowers the thread priority of the process corresponding to the process ID. Step S1608 is processing in which the application management unit 220 records in the system log or the like that the service application has exceeded the available CPU usage rate. Step S1609 is processing for stopping for a certain period of time. Thereafter, the process returns to step S1601.

  FIG. 18 is a diagram illustrating a processing flow of the abnormality notification processing S1800 of the application management unit 220. FIG. 18 shows a procedure for notifying the gateway management apparatus 100 of an abnormality when the service application 211 exceeds the available resource amount.

  Step S1801 is processing in which the application management unit 220 acquires information regarding whether or not the service application 211 has exceeded the available resource amount from a system log or the like.

  Step S1802 is processing in which the application management unit 220 checks whether there is a service application that exceeds the available resource amount. If there is a service application that exceeds the available resource amount (step S1802, Yes), the process proceeds to step S1803. If there is no service application exceeding the available resource amount (step S1802, No), the process proceeds to step S1804.

  Step S1803 is processing in which the application management unit 220 transmits information regarding whether or not the service application ID and the amount of available resources have been exceeded to the gateway management apparatus 100.

  Step S1804 is processing in which the application management unit 220 stops the abnormality notification processing S1800 for a predetermined time. Thereafter, the process returns to step S1801.

  FIG. 19 is a diagram illustrating a processing flow of the abnormality notification processing S1900 of the application management unit 220. FIG. 19 is another processing flow of FIG. 18 and shows a procedure for notifying the gateway management apparatus 100 of an abnormality when the service application exceeds the available resource amount.

  Step S1901 is processing in which the application management unit 220 acquires information about whether or not the service application has exceeded the available resource amount from the system log or the like.

  Step S1902 is processing in which the application management unit 220 checks whether there is a service application exceeding the available resource amount. If there is a service application exceeding the available resource amount (step S1902, Yes), the process proceeds to step S1903. If there is no service application exceeding the available resource amount (step S1902, No), the process proceeds to step S1905.

  In step S1903, the application management unit 220 refers to the installed service application dependency management table 900 (see FIG. 9) and describes the information in the Export-Package for the information described in the Import-Package corresponding to the ID of the service application. This is a process of obtaining a list (J) of IDs of service applications that are present.

  Step S1904 is processing in which the application management unit 220 transmits the ID of the service application, information regarding whether or not the available resource amount has been exceeded, and information on J to the gateway management apparatus.

  Step S1905 is processing in which the application management unit 220 stops the abnormality notification processing S1900 for a predetermined time. Thereafter, the process returns to step S1901.

  In this embodiment, the gateway management apparatus 100 that distributes application service execution software (application software) developed by a service provider to the gateway apparatus 200 having an application service execution platform can be used by each application service execution software. A table for managing the resource amount of the gateway device 200 is provided, and when new software is distributed to the gateway device 200, the total amount of resources available to the application service execution software of the gateway device 200 and the gateway device 200 already. Obtain the total available resource amount of the installed software, and the total available resource amount of the installed software and the availability of new software The total of the amount of resources and the total amount of resources that can be used by the application service execution software are compared. The total amount of available resources of the installed software and the total amount of resources that can be used by the new software are When the service execution software does not exceed the total available resources, new software distribution is permitted. The gateway management device 100 can collect the measured resource amount of the application execution software from the gateway device 200 according to the request of the service provider, and can provide the service provider with information on the collected measured resource amount.

  In the embodiment, the gateway device 200 executes application service execution software distributed by the gateway management device 100, and includes a processing unit and a storage unit including a memory. The storage unit stores the application service execution software. When the total amount of resources that can be used and the total amount of resources that can be used with software that has already been installed are held, and the new software is requested from the gateway management apparatus 100, the processing unit holds the application service execution software that is held. The total amount of available resources and the total amount of available resources of already installed software are transmitted to the gateway management apparatus 100. The gateway device 200 can measure the measured resource amount of the application execution software according to the request of the gateway management device 100, and can transmit the measured measured resource amount to the gateway management device 100.

  Furthermore, the gateway management system including the gateway management apparatus 100 that distributes application service execution software to the gateway apparatus 200 having the application service execution platform manages the resource amount of the gateway apparatus 200 that can be used by each application service execution software. When the gateway management device 100 distributes new software to the gateway device 200, the total amount of resources that can be used by the application service execution software from the gateway device 200 and the use of software that has already been installed in the gateway device 200. The total available resource amount is obtained, and the total of the available resource amount of the installed software and the available resource amount of the new software Compare the total amount of resources that can be used by the application service execution software, and the total amount of available resources of the software that has already been installed and the total amount of available resources of the new software can be used by the application service execution software. Allow distribution of new software if the total amount of resources is not exceeded. The gateway management system can collect the measured resource amount of the application execution software from the gateway device 200 according to the request of the service provider, and can provide the service provider with information on the collected measured resource amount.

  According to the present embodiment, the gateway management apparatus 100 includes a service management table 2000 that manages each application provided by the service provider, the number of devices of the gateway apparatus 200 on which each application is executed, and when each application is executed. A storage unit having an actually measured resource information totaling management table 2200 associated with actual measured values necessary for the resource, and the actual measured values required when each installed application is executed from each gateway device 200. When received, the measured resource information aggregation management table 2200 is updated based on the received measured resource value. When the number of devices reaches a predetermined value, the service provider registered in the service management table 2000 is notified of the measured resource value. Can be notified.

  As described above, the gateway management apparatus 100 according to the present embodiment distributes the service application 211 to the gateway apparatus 100 in accordance with a request from the service provider, and then executes the service application on the gateway apparatus 200. It is possible to provide the service provider with information collected and aggregated from many gateway devices 200 as to whether the amount of resources (heap memory amount, memory amount, CPU usage rate) has been used.

  By installing the above-mentioned mechanism, service providers can obtain measured resource aggregation information even when developing service applications using emulators, etc., without using actual devices. It is possible to estimate with a high accuracy the amount of necessary resources that a person registers in the gateway management apparatus.

  For example, in a system in which the gateway management apparatus 100 charges the service provider according to the required resource amount set by the service provider, the service provider needs as much as possible within the range in which the service application operates stably. Although we want to reduce the resource amount, it is considered that the required resource amount can be set smaller by using the mechanism of this embodiment.

  For example, when a service provider starts a new service, first it is necessary to collect the measured resource amount as a beta test, and the required resource amount is set to a large value with some margin and registered in the gateway management device. It is possible to operate such as obtaining aggregate information and registering the official version with the minimum required resource amount setting based on the result.

11, 21 EPROM
12,22 CPU
13, 23 Main memory 14, 24 Bus 15, 25 Non-volatile storage device 16, 26 Peripheral control device 17, 27, 28 Network I / F
DESCRIPTION OF SYMBOLS 30 External network 40 Service provider server 50 User's house 100 Gateway management apparatus 101 Application registration management part 102 Application distribution management part 103 DB management part 110 Service management DB
DESCRIPTION OF SYMBOLS 200 Gateway apparatus 210 Application execution part 211 Service application 220 Application management part 230 User home network 240 Home equipment 250 Gateway management DB
300 Total available resource table 400 Available resource table 500 Required resource table (resource management information)
800 Dependency table 900 Introduction service application dependency management table 1000 Process ID management table 2000 Service management table (application management information)
2100 Actual resource information table (actual resource device information)
2200 Actual resource information aggregation management table (actual resource aggregation management information)

Claims (14)

The gateway of the gateway management apparatus that manages the application, which is application software provided to the gateway device by the service provider, and notifies the service provider of the actual measured resource value required when the application is executed in the gateway device A management method,
The gateway management device
The service provider has application management information for managing each application provided from the service provider server in association with the service provider, and the number of gateway devices on which each application is executed and each application is executed. A storage unit having actual resource total management information associated with actual required resource values when
The gateway management device
From each of the gateway devices, receive the resource actual measurement value required when each installed application is executed, update the actual resource aggregation management information based on the received resource actual value,
It is determined whether the number of devices of the application registered in the application management information has reached a predetermined value, and the service provider registered in the application management information for the application that has reached the predetermined value The gateway management method characterized by notifying. The gateway management device further includes:
Resource management information for managing resource values of the gateway device that can be used by each application is stored in the storage unit,
When the gateway management apparatus receives an application distribution request from the service provider, the gateway management apparatus associates the application that has received the distribution request with a resource value set by the service provider, and registers it in the resource management information. With
The gateway management method according to claim 1, wherein a new record is created in the measured resource total management information, and the number of devices for the application that has received the distribution request is initialized. The gateway management device
When distributing a new application to the gateway device,
Obtaining a total of resource values available for applications of the gateway device and a total of available resource values of applications already installed in the gateway device;
Comparing the sum of the available resource values of the installed application and the available resource value of the new application with the sum of the resource values available to the application of the gateway device;
The total of the available resource values of the installed application and the available resource value of the new application does not exceed the total amount of resources available to the application of the gateway device. The gateway management method according to claim 1, wherein distribution of the application is permitted. The gateway management device
When the new application distributed to the gateway device is an application in which a record is created in the measured resource aggregation management information,
The gateway management method according to claim 2, wherein the gateway device is notified that resource actual measurement values are collected when the new application is executed in the gateway device. The gateway management method according to claim 2, wherein the resource value is at least one of a CPU usage rate of the gateway device and a memory usage amount of the gateway device. The gateway management method according to claim 1, wherein the gateway device is an execution environment configured by an operation system, a Java VM, and an OSGi. A gateway management device that manages an application that is application software provided to a gateway device by a service provider,
The service provider has application management information for managing each application provided from the service provider server in association with the service provider, and the number of gateway devices on which each application is executed and each application is executed. A storage unit for storing measured resource total management information associated with actual measured values required when
Received from each gateway device is a resource actual measurement value required when each installed application is executed, updates the actual resource aggregation management information based on the received resource actual value, and the application management information An application that determines whether the number of devices registered in the application reaches a predetermined value and notifies the service provider registered in the application management information of the resource measured value for the application that has reached the predetermined value A gateway management device comprising a distribution management unit. The gateway management device
Resource management information for managing resource values of the gateway device that can be used by each application is stored in the storage unit,
The gateway management device further includes:
When receiving an application distribution request from the service provider, the application received the distribution request is associated with the resource value set by the service provider and registered in the resource management information, and the measured resource aggregation The gateway management apparatus according to claim 7, further comprising an application registration management unit that creates a new record in management information and initially sets the number of devices for the application that has received the distribution request. The application distribution management unit
When distributing a new application to the gateway device,
Obtaining a total of resource values available for applications of the gateway device and a total of available resource values of applications already installed in the gateway device;
Comparing the sum of the available resource values of the installed application and the available resource value of the new application with the sum of the resource values available to the application of the gateway device;
When the total of the available resource values of the installed application and the available resource value of the new application does not exceed the total amount of resources available to the application of the gateway device, the new resource value The gateway management apparatus according to claim 7 or 8, wherein distribution of an application is permitted. The application distribution management unit
When the new application distributed to the gateway device is an application in which a record is created in the measured resource aggregation management information,
The gateway management apparatus according to claim 8, wherein the gateway apparatus notifies the gateway apparatus that resource actual measurement values are collected when the new application is executed in the gateway apparatus. The gateway management device according to claim 8, wherein the resource value is at least one of a CPU usage rate of the gateway device and a memory usage amount of the gateway device . The gateway management apparatus according to claim 7, wherein the gateway apparatus is an execution environment configured by an operation system, a Java VM, and an OSGi. A gateway device that executes an application that is application software distributed by the gateway management device,
The gateway device is
When each application is executed, it includes a storage unit that stores the actual measured resource value and the operation time necessary for each application in association with each other, and stores the actual measured resource device information.
The gateway device is
When deployed for each application is performed for every predetermined period, the resource was measured it becomes necessary for each application, if the resource measured value the measurement is greater than the registered resource measured value to the actual resource information, Update the resource actual measurement value of the actual resource information,
When the operating time exceeds a predetermined time, a resource measured value of the measured resource information is transmitted to the gateway management device. The gateway device is
When the application newly distributed from the gateway management device receives a notification that it collects resource actual measurement values when executed in the gateway device,
The gateway apparatus according to claim 13, wherein a new record is created in the actually measured resource apparatus information, and an operation time of the newly distributed application is initialized.

Images