JP2013003816A - Virtualized home gateway system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a virtualized home gateway system enabling a provider who provides a new service to a user by using apparatuses and sensors installed in a home network to provide the service by effectively using the existing apparatuses and sensors.SOLUTION: A software execution environment in which information collection, protocol conversion and control of various sensors and apparatuses connected to a home network 3 under a home gateway which is connected to a wide area network 5 are performed, is collectively installed in a server which is connected to the wide area network as a virtual execution environment. Management of application software in a home gateway function is made easier and hardware restrictions by the home gateway are reduced. By providing a service management part 10 performing control of services, service management is made easier and thus entering a new business by another provider using the apparatuses and sensors 4 is made possible.

Description

  The present invention relates to a virtualized home gateway system, and more particularly to a home gateway system that improves system operability and maintainability by centrally arranging functions.

  In conventional home gateways, for example, as disclosed in Patent Document 1, Non-Patent Document 1, and Non-Patent Document 2, application software is distributed to home gateways arranged in each home in order to execute home services. In addition, a method of executing using the CPU and memory of the home gateway has been proposed. Similarly, it has been proposed to arrange a home server having a large storage capacity in a home network.

Japanese Patent No. 4575177

Shigeki Kitajima and Kento Iwasaki, “Approach to Service Platform System for Home Appliances”, Hitachi Review, Vol. 90, no. 06, pp. 46-49, June 2008 Takushi Hamada, Chiyo Ohno et al., “Home Network Technology Development”, Hitachi Review, Vol. 89, no. 06, pp. 44-47, June 2007

However, in this method, it is necessary to manage home gateways arranged in each home and application software in the home gateway, and the hardware configuration of the home gateway, that is, the CPU capability in the design and operation of the application. There were restrictions due to the amount of memory.
In addition, when a home server having a large storage capacity is arranged in the home network, there is a capacity limitation of these storage devices, and the management of the device is also left to the user, thus ensuring the reliability of data storage. It was difficult.
In addition, sensors installed in each home are assumed to correspond to a single service provider. When receiving similar services from multiple providers, similar sensors, etc. There was a need to duplicate the arrangement in the home.
Moreover, since the application is intended for the home network connected to the home gateway installed in the home, it is difficult to handle a plurality of home networks as a single home network.
In the present invention, in view of the above points, it is possible that an operator who provides a new service to a user using devices and sensors arranged in a home network effectively provides services using existing devices and sensors. It is an object of the present invention to provide a possible virtualized home gateway system.

In order to solve the above problems, in the present invention, for example, a software execution environment for performing various sensors, device control, information collection, protocol conversion, etc. connected to a home network under a home gateway connected to a wide area network is provided. It is easy to manage application software in the home gateway function by collectively arranging it as a virtual execution environment in a server connected through a network, and eliminates hardware restrictions by the home gateway. One.
Moreover, it has the function which can manage the correspondence of the different service of a some service provider with respect to the various sensors and apparatus connected to each home network. As a result, it is not necessary to arrange a similar sensor or the like for each service provider, and information acquired from the sensor or the like is shared. In addition, the possibility of entry of new service providers can be expanded. Another feature is that redundant sensor data acquisition can be reduced and communication traffic can be reduced.
In the present invention, a plurality of operating systems can be executed in one virtual execution environment in a server connected via a wide area network, so that different application distribution platforms can be supported. One of the features is that an application that operates only in an environment can be executed, and the application can be provided to the end user even when there is a difference in the application update time of the application provider.
In addition, the present invention has a function for managing the service provided by the service provider and the user, various sensors and devices connected to each home network on the center side, so that One of the features is that it has a function of creating a report and can provide a user's usage status as statistical information to a service provider and other providers.

According to the solution of the present invention,
Virtual home gateways that perform one or more of control, information collection, and protocol conversion of devices and sensors distributed by one or a plurality of first providers and connected to each home network are collectively arranged to provide a plurality of homes. A virtualized home gateway server connected to the network;
A device database storing the type of the device and sensor connected to each home network, and the identification information of the first provider of the distribution source;
An operator billing database for storing billing information by using data of the device and sensor of the first operator by the second operator;
In response to a device use request from a second operator including the type of desired device and sensor, the device database of the first operator corresponding to the desired device and sensor is referred to by referring to the device database. With a management department to identify,
The management unit
Enter a subscription request from a user for a service by a second operator using the data of the device and sensor of the identified first operator,
There is provided a virtualized home gateway system that stores billing information in which the first business is the billing source and the second business is the billing destination in the business billing database.

  According to the present invention, an operator that provides a new service to a user using devices and sensors arranged in a home network effectively uses the existing devices and sensors deployed by the first operator. A virtual home gateway system that can be provided can be provided.

1 is a conceptual diagram of a system that facilitates service provision by a plurality of service providers. The structural example of a service management part. The structural example of a HGW-VM and a HGW-IF part. The example of a flow of a service management part. The example of an application update flow of a service management part. Example of configuration of subscriber database (1). Configuration example (2) of the subscriber database. Example of device / sensor database. Example service database. An example of a billing database. An example of a shared database. Example (1) of sensor sharing business model between services. Service management unit flow example (1) until service provision using devices and sensors of other business operators. Service management unit flow example (2) up to service provision using devices and sensors of other companies. An example of the flow of a service management unit for providing candidate devices / sensor lists to other businesses. Examples of available device / sensor files. An example of a service enabler file. An example (2) of a sensor sharing business model between services. The structural example of a provider accounting database.

FIG. 1 is a block configuration diagram showing an example of a virtualized home gateway system according to the present embodiment. This system includes a virtualized home gateway server 1, a virtualized home gateway interface unit (HGW-IF unit) 2, a home network 3, various household devices / sensors 4, a wide area network 5, and a plurality of It comprises a service provider device 6 and a service management unit 10.
A virtual machine VM 7 in the virtual home gateway server 1 is connected to a virtual home gateway interface unit 2 disposed in each home / office via a wide area network 5. The virtual machine VM7 and the virtualized home gateway interface unit 2 have a one-to-one correspondence when the service is executed. Various home appliances / sensors 4 are connected to the virtual home gateway interface unit 2 via a home network 3.
The virtual home gateway server 1 includes a CPU, a memory, and an external storage device for executing a virtual gateway application. The virtual home gateway server 1 simultaneously includes a plurality of virtual machines VM7 that are execution environments of the home gateway. It is executable.
In response to a user request, the service provider's device 6 distributes and manages applications to the virtual machine VM7 in the service center 8, and enables execution of the application on the virtual machine VM7. At this time, the service management unit 10 manages application distribution.
The virtualized home gateway interface unit 2 and the virtual machine VM7 are connected via the wide area network 5. At this time, in order to clarify the correspondence between the virtualized home gateway interface unit 2 and the virtual machine VM7 in the wide area network 5, the point network is connected to the wide area network 5 using point-to-point PPP, or tunneling is performed by IPsec. Can be used.
When the device 4a (for example, a mobile terminal) in the home network 3 controls the device 4 in the same home network 3, the control command of the device 4a passes through the home network 3 and the virtual home gateway interface unit 2 After being processed by the application on the virtual machine VM7, the reverse route is followed to the device 4b for control. The home network 3 may be configured as a single network, but may be configured with networks having a plurality of different protocols and interfaces. Note that the processing by this application includes control calculation, protocol conversion, address conversion, and the like.

FIG. 2 is a detailed configuration example of the service management unit 10 according to the present embodiment.
The service management unit 10 includes, for example, a CPU (management unit) 201, a memory 202, an external storage device 203, and an interface unit 204. Software is stored in the memory 202 and is read and executed by the CPU 201. A subscriber database 221, a device / sensor database (device database) 222, a service database 223, a charging database 231 and a shared database are connected via the interface unit. The charging database 231 includes a subscriber charging database 231-1 and a business charging database 231-2. In addition, the service provider device 6 and the home gateway server 1 are connected via an interface unit. Each database may be configured by one or a plurality of storage devices, or may be provided in the external storage device 203. The configuration of each database will be described later.
As shown in FIG. 3, the virtual home gateway interface unit 2 includes, for example, an Ether net driver that is an interface for connecting to the home network 3, a USB driver, and hardware of both, as well as a voice interface. A sound driver and a sound generator are mounted. It also has a voice codec and protocol processing function for an IP phone, a SIP protocol stack, an interface unit with the wide area network 5, and a common control unit for overall control.
The virtual home gateway server 1 includes, for example, a CPU, a memory, a storage device, and an interface unit. The virtual home gateway server 1 can execute a plurality of virtual machines VM7, and each virtual machine VM7 has an interface unit for connecting to the virtualized home gateway interface unit 2 via the wide area network 5, a virtual machine OS, and OSGi. It consists of a framework, applications, and a management unit. Software for realizing each function is stored in, for example, a memory or a storage device, and is read and executed by the CPU.
The management center 8 (sometimes referred to as a service center in the present embodiment) includes a virtual home gateway server 1 and a service management unit 10. The service management unit 10 manages the distribution of applications to the virtual machine VM7, manages which application is installed in each user's virtual machine VM7, and the version. The VM management unit manages the virtual machine VM 7 in the virtual home gateway server 1.

FIG. 6 shows an example of the configuration of the subscriber database 221.
In this example, the subscriber identifier is used as a key, and the HGW address of the subscriber, home network connection device information (connection hardware information), and installed application information are stored. In addition, information on whether or not to disclose information to other companies such as data of connected hardware can be included. The subscriber (user) here corresponds to a home / office where the home gateway interface unit 2 is installed. The home network connection device information is information on one or a plurality of devices connected to the home network managed by the home gateway interface unit 2 corresponding to the subscriber. For example, model information (device and sensor identification information), device Includes address and device type. As the model information, for example, information that can identify the provider of the distribution source and the types of devices and sensors can be used. The installed application information includes, for example, a device application name, device application version information, and billing information. A plurality of installed application information may be stored for the home network connection device information. In each database, an entry number (No) may be assigned to each entry.
FIG. 7 shows another configuration example of the subscriber database 221.
Similarly to FIG. 6, this example also stores, for example, the management of the device, etc., using the subscriber identifier as a key and storing the subscriber's HGW address, device information, home gateway interface information, and the like. Yes. The device information includes, for example, home gateway model information, a home gateway serial number, and firmware version information.
Note that FIGS. 6 and 7 can be independent databases or a single database.

FIG. 8 is an example of the device / sensor database 222.
This database is intended to enable services to share device / sensor data among multiple business operators. The purpose, function, performance, number of users, availability of other business operators, Consists of usage patterns and fees for using other businesses. For example, the device / sensor database 222 includes classification information of services to be provided to subscribers, service provider identifiers for services, device / sensor identification symbols, functions / names of devices / sensors, devices / sensors. It includes performance information, the number of users, availability information of other companies, usage form information of other companies, and fee information when using other companies.
The performance information stores, for example, a sensor measurement target, a measurable range, accuracy, a device function, and the like. The number of users is, for example, the number of users of the service corresponding to the classification information, or the number of devices / sensors stored in the function information. The other company's use form shows a form in which the C company shares the sensor data distributed by the A company, for example. In the unique access, for example, each of the A company and the C company acquires user data at a unique timing (actually, the application can acquire and upload). On the other hand, in data sharing, for example, data acquired by the A company is placed in a temporary file described later, and the C company uses the data. The charge information when using another company indicates, for example, the charge when the other company uses the device / sensor. For example, the charge per device, such as the fee per device / sensor, the monthly fee, etc. The charge per period is stored.

FIG. 9 is an example of the service database 223.
This database, for example, corresponds to the identifier of the service provider and the service name, the name of the application used by the service, the latest version information, and the application file name (may include information specifying the file storage location) Including the identification symbol of the device / sensor to be used, the information acquisition frequency, and the usage fee. These pieces of information are registered as appropriate, for example, at the start of service provision.
FIG. 10 is an example of the subscriber billing database 231-1.
The subscriber charging database 231-1 includes one or a plurality of subscription service information to which the subscriber subscribes and a total charge, with the subscriber identifier as a key. The subscription service information includes, for example, an identifier of a service provider, a service name, and fee information. In addition to these, it is also possible to add a charging method, payment status, and the like. Each of these pieces of information can be stored, for example, when the service is subscribed.
FIG. 19 is an example of the provider billing database 231-2.
The provider billing database 231-2 is a database for paying a usage fee between providers when, for example, a certain provider provides services using devices and sensors of other providers.
The business billing database 231-2 includes, for example, a billing business identifier (for example, business operator C), a service name, a billing business operator identifier (for example, business operators A, B, etc.), and the service. The number of subscribers and the total billed amount are stored. The billing business operator is a business operator (second business operator) that provides services by using devices and sensors of other business operators. The billing company is a company (first company) that uses the devices and sensors distributed by itself. The unit price corresponds to the other company's usage fee in FIG. The total amount charged is determined by, for example, the unit price and the number of subscribers. For example, the number of subscribers is updated every time when the use of the corresponding service is accepted, and the total billed amount is updated. Further, if the use start date is stored for each subscriber, it can be used, for example, when a daily calculation is performed.

FIG. 11 is an example of the shared database 241.
This database is used when a subscriber stores and manages data such as photographs through the HGW as a home server function. For this reason, as a database structure, one or a plurality of file information including a file name, a size, a creation date, an update date, and the like are stored for each subscriber. By installing this database in the service center 8, there is no capacity limitation by the subscriber premises equipment. The service provider can provide the subscriber with a highly reliable data storage environment by performing appropriate management such as backup.
FIG. 4 shows an example of an execution flow for accepting a new service according to the present embodiment.
The use reception of the procedure 401 can be implemented by various means such as Web, Mail, telephone, and mail. For example, the service management unit 10 receives an application for service start of a certain business from a subscriber. The application for starting service use includes, for example, a subscriber identifier, an identifier of a business providing service, and a service name. When using Web or e-mail, the service management unit 10 receives a use start application and extracts such information. When using telephone or mail, the information is input through the input unit by an operator's operation. When there is an application, an application file necessary for executing the service is extracted from the service database 223 by the service application extraction in step 402. For example, the service management unit 10 refers to the service database 223 based on the service provider identifier and the service name included in the application for starting use, and extracts a corresponding application file. Also, the corresponding application name, latest version information, sensor / device information, usage fee information, etc. are extracted. The service management unit 10 distributes the extracted service application to the virtual machine VM7 of the subscriber who has applied for use in step 403. The distributed application is confirmed in step 404 to be surely distributed, and then executed in step 405 to start providing a service.
In response to the start of service provision, the service management unit 10 registers in the subscriber information database 221 that the service is being used in step 406. For example, the service management unit 10 stores application information corresponding to a subscriber identifier and sensor / device information (home network connection device information). The application information includes, for example, the application name acquired from the service database 223 in step 403, the latest version information, and billing information based on the usage fee information. Thereafter, in step 407, the subscriber registers the use of the service in the charging database 231, and information necessary for charging is generated. For example, the service management unit 10 stores, in the subscriber billing database 231-1, a service provider identifier, a service name, and fee information (the above-mentioned usage fee information) corresponding to the subscriber identifier. To do. For convenience of explanation, the procedure 404 to the procedure 407 are defined as a procedure 420 as a series of procedures from application distribution confirmation to billing information update.

FIG. 5 shows a procedure in the case where there is an application update request from the service provider 6.
In step 501, when the service provider 6 offers an application update by means such as Web or Mail, the latest application file from the service provider is written on the service database 223. For example, the service management unit 10 receives an application update instruction including an application name, latest version information, and an application file from the service provider's device 6. The service management unit 10 overwrites the application file corresponding to the application name to be updated on the service database 223. The latest version information is also updated.
In step 502, the service management unit 10 extracts subscribers that need to update the application from the subscriber database 221. For example, the subscriber identifier of the subscriber in which the application name included in the application update instruction is stored is extracted. In step 503, the updated application file is extracted. For example, the service management unit 10 refers to the service database 223 based on the application name and extracts a corresponding application file. In addition, the operator identifier and service name are extracted. In step 504, the service management unit 10 distributes the new version of the application to the virtual machine VM7 of the subscriber. Thereafter, application distribution confirmation, service provision start, update of the subscriber database 222, and update of the charging database 231 are performed according to the procedure 420 defined as described above. In step 505, it is confirmed whether all the target persons have been updated. If there is a remaining target person, the process returns to step 502, and the next target person is updated. Moreover, when all the target persons have completed the update, the process ends.

Next, the operation of the embodiment that facilitates service provision by a plurality of service providers 6 will be described below. As shown in FIG. 1 and as described above, the service center 8 grasps service provision contents of a plurality of service providers 6, information on devices / sensors 4 connected to the user's home network 3, and application correspondence status for each user. A service management unit 10 exists. The service management unit 10 grasps and manages the information of the device / sensor 4 and the application correspondence status for each user with respect to the corresponding virtual machine VM 7 of the virtual home gateway interface unit 2 in the virtual server 1.
When the service provider 6 develops a new service, it is necessary to place a new device / sensor in each home network 3, but there are already providers that provide other services using similar sensors. In this case, the new service provider can reduce the capital investment by providing services using the devices / sensors that have already been placed, and by sharing the information collected from the devices / sensors. Communication traffic can be reduced.
FIG. 12 shows that when the service provider B uses the sensor information distributed by the investment of the service provider A to perform a new service, the service provider B is appropriate. This is an example in which a mechanism for paying the service provider A to the service provider A is constructed. First, an overview of the service will be described, and the processing of each device will be described later.
For example, charge of usage fees between service providers according to the frequency, amount, etc. used by service provider B, distributed to subscribers by investment of service provider A, and information of sensors installed in the home network. This is an example in which payment is possible.
The user X receives a sensor (eg, a blood pressure monitor) from the service provider A and provides information to the service provider A to receive a predetermined service (eg, health management). The user X provides the service. Consideration is paid to the operator A.
When the user X newly receives a value-added service (eg, meal guidance) from the service provider B, the data provided by the service provider A using the sensor (eg, blood pressure monitor) distributed to the service provider B To provide value-added services (eg, meal guidance) and pay service provider B to service provider B.
The service management unit 10 charges and pays the sensor usage fee according to the usage fee of the sensor belonging to the service provider A used by the service provider B.
This function makes it easier for service providers to enter the service business. Further, the user does not need to arrange a plurality of sensors of the same type. Businesses that distribute equipment and sensors have an opportunity to recover their investment in distribution. In addition, when a plurality of service providers can exchange the acquired sensor information, the user does not need to transmit information of the same contents a plurality of times, and a reduction in communication traffic can be expected.

FIG. 13 shows an example of a flow from the service management unit 10 to using a device / sensor of another business operator until a business operator starts a service.
Before starting the processing of this flow, a certain business operator (business operator C in this example) notifies the service center 8 by some means that a service using a device / sensor that has already been distributed is desired. Yes.
In step 1301, required specifications of devices and sensors necessary for providing the service of the operator C are registered. This required specification includes, for example, specifications of devices and sensors. For example, the type of device / sensor (eg, blood pressure monitor or blood pressure) is included. Moreover, the performance (eg, required measurement range, required accuracy) of devices and sensors may be included. For example, the service management unit 10 may receive this request from the device 6 of the business operator C, or when notified by mail or the like, the service management unit 10 may input the request from the input unit by an operation to the operator. Good.
Based on this information, available devices / sensors are extracted from the device / sensor database 222. Specifically, the service management unit 10 sets the device number to an initial value 0 so that the devices and sensors can be checked in order from the beginning in step 1302, and adds 1 to the device number in step 1303. In step 1304, the service management unit 10 compares the device / sensor database 222 with the request obtained in step 1301. If the service management unit 10 is available, the service management unit 10 proceeds to step 1305. Add 1 to, and proceed to check the next device. More specifically, the service management unit 10 refers to the entry in the sensor database 222 corresponding to the set device number, and stores the device / sensor identification symbol, the function / name of the device sensor, the device / Based on the sensor performance information, it is determined whether the use request of the device / sensor is satisfied (can be used), and the procedure proceeds to steps 1305 and 1303 according to the determination result. In this example, in addition to the specifications of the devices / sensors, whether or not others can be used specified by the device / sensor distributor is also used as a criterion. For example, when the other person availability information stored in the entry is “No”, it is determined that the device / sensor use request is not satisfied regardless of whether the request for using the device / sensor is satisfied, and the process returns to Step 1303.
In step 1305, a list 1307 of devices / sensors available to the operator C is generated. FIG. 16 shows an example of an available device / sensor file 1307. In this example, it is configured by adding a flag indicating whether or not the item 1601 business operator C is appropriate for use to each device in the device / sensor database 222. In addition to this, the available device / sensor file 1307 may be created in an appropriate form. If all the devices / sensors stored in the device / sensor database 222 have not been processed, the process returns to step 1303, and when all the devices / sensors have been processed, the process proceeds to step 1310.
In step 1310, the names, symbols, and the like of the devices and sensors extracted in the above procedure (in the example of FIG. 16, devices and sensors for which the operator C use suitability flag is “suitable”) are extracted. In step 1316, subscribers using the device are extracted from the subscriber database 221, and a service provider file 1315 is generated. More specifically, the service management unit 10 extracts the identification symbol of the device / sensor that is determined to be usable by the operator C from, for example, the available device / sensor file 1307. Further, similarly to the procedures 1302 and 1303, the service management unit 10 sets the subscriber number to the initial value 0 in the procedure 1311 and adds 1 to the subscriber number in the procedure 1312. In step 1313, the service management unit 10 refers to the entry in the subscriber database 221 corresponding to the set subscriber number, and determines whether the extracted identification symbol exists in the device information of the entry. If it exists, the service management unit 10 registers the subscriber in the service provider file 1315.

FIG. 17 shows an example of the service provider file 1315. In this example, an item 1701 C operator use suitability flag is added to each subscriber in the subscriber database 221. In addition to this, the service provider file 1315 may be created in an appropriate form. If all the subscribers stored in the subscriber database 221 have not been processed, the process returns to step 1312. When the process is completed for all subscribers, the process proceeds to step 1321.
Procedures 1321 to 1325 are procedures for soliciting service usage for all the service provider files 1315. For example, the service management unit 10 extracts each user whose propriety C use suitability information in the service provider file 1315 is “suitable” (procedure 1323), and sends a service use solicitation (guidance information) to each user. . In this example, e-mail solicitation is performed for the target person in step 1326. It is also possible to obtain a list and solicit by other means such as direct mail. Note that the destination mail address and direct mail destination can be stored in advance in correspondence with the user.
The solicited subscriber makes a use application at his / her will, and the application is accepted in step 1327. The flow from the acceptance of the application to the start of the service is the same as in FIG.
Next, distribution of data to the business operator C that uses the data of the devices / sensors of the business operators A and B, and processing of payment of usage fees (charges between business operators) from the business operator C to the business operators A and B Will be described.
The service management unit 10 stores, in the service database 223, the information on the available devices / sensors identified in the process of FIG. 13 and the service name newly provided by the business operator C in correspondence with the business operator identifier. For example, when different provider sensors can be used for the same service, they are stored as separate entries. In this case, adding a branch number to the service name facilitates subsequent processing such as user billing. The application name, latest version, application file, frequency information, usage fee, and the like can be appropriately registered from the service provider's device 6. As described above, processing similar to that shown in FIG. 4 is executed in response to the use application from the subscriber, and the application is distributed to the subscriber's virtual machine VM7. The application uses data of the device / sensor of the business operator A, for example. Which device / sensor of which business operator is used can be specified with reference to the service database 223, for example.
Moreover, the service management part 10 updates the provider charge database 231-2 with respect to the use application from a subscriber. For example, the use application from the subscriber here includes the subscriber identifier, the provider identifier of the service provider (here, the provider C) and the service name, as well as the provider identifier of the device / sensor to be used (for example, the project). Person A or B). Based on the service provider's business operator identifier, service name, and the business device identifier of the device / sensor to be used, the service management unit 10 bills business operator information in the business billing database 231-2, service name, billing business operator By referring to the information, the number of subscribers of the corresponding entry is increased by one. Thereby, the total billing amount can also be updated.
If there is no corresponding entry, the service management unit 10 uses the provider identifier of the service provider, the service name, the provider identifier of the device / sensor to be used, and the billing provider information in the provider billing database 231-2. The service name and the billing company information are stored, and the number of subscribers is set to 1. The unit price of the provider billing database 231-2 is based on the provider identifier of the service provider and the information on the available equipment / sensors identified in the processing of FIG. 13 and refers to the equipment / sensor database 222. , Memorize the corresponding usage fees of other companies.

(Utilization of equipment / sensors of specified companies)
FIG. 14 is an example of a flow in the case where a certain business operator (business operator A in this example) uses the devices / sensors distributed by the company to other business operators.
Prior to the start of the processing of this flow, the business operator A has applied to the service center 8 to consider the use of other company-distributed equipment / sensors. In addition, it is assumed that the target company (company C in this example) has applied to the service center 8 for the use of other company's devices and sensors. In this flow, each business operator checks whether the business operator A can use the equipment / sensors, and even solicits subscribers. The difference from the flow of FIG. 13 is that only the information on the device / sensor of the business operator A is filtered and output from the device / sensor database 222 in step 1404 before considering the match with the business operator C request. is there. Other processing is the same as the flow of FIG.
In this way, the business operator A can expand the use of the devices and sensors distributed by the business operator A to other business operators.

(Recommendation of available device / sensor information)
FIG. 15 shows that the service center 8 extracts information about devices / sensors that can be used for business by the business operator (the business operator C in this example) from the devices / sensors distributed to the business operator by other business operators. It is an example of a flow to recommend.
In this flow example, it is assumed that there is a recommendation request in step 1501. The recommendation request may be received from a device 6 (for example, the device of the business operator C) of a business operator who is considering starting a new service, or may be input from the input unit by the operation of the operator of the service center 8. Sometimes it is done. This request includes, for example, a recommended business identifier (business C in this case).
Procedures 1502 to 1507 are the same as those described above. The output available device / sensor file 1307 according to this procedure is processed into only information that can be presented to the operator C in step 1510. For example, only entries whose operator C usage suitability flag indicates “suitable” are extracted. In addition, information that can be presented among the information of the available device / sensor file 1307 may be determined in advance. The information that can be presented may be different for each company that distributes devices and sensors, for example. Information that can be presented is presented to the recommended business operator C in step 1511. This presentation may be online or offline.
If the business operator C is interested in the presented content, the business operator C will obtain a new business opportunity. After that, for example, as shown in FIG.

(Modification)
FIG. 18 shows another form of data acquisition. In the example of FIG. 18, when the business operator A acquires the sensor data of the user X, the data is temporarily stored in the temporary file 1801. The temporary file 1801 can be provided in the service management unit 10, for example. The business operator B can acquire the sensor data of the user X from the temporary file 1801 without acquiring the sensor data again. Therefore, the user X can provide data to a plurality of businesses by using the data only once, which is effective in the case of data that takes a long time for measurement or data acquisition with a large user burden. In addition, the frequency of use of the communication line is reduced, which is effective in reducing traffic. Other processing is the same as described above.
Temporary files can be deleted at the stage when data collection by the business operator using the data is completed, so that the capacity of the temporary files can be reduced and information leakage can be taken.
In this embodiment, the service provision status is provided to the service provider by using the user, various sensors, devices connected to each home network on the center side, and the function for managing the service correspondence provided by the service provider. It may have a function to create a report. In addition, the usage status of the user may be provided as statistical information to the service provider and other providers.
According to the present embodiment, the application execution environment of the home gateway is collectively arranged as a virtual execution environment in a server connected via a wide area network, so that application distribution management is facilitated. In addition, since the virtual execution environment is used, there is an advantage that the CPU capacity and memory capacity of the home gateway are not restricted.
Further, in this embodiment, by enabling execution of a plurality of operating systems in one virtual execution environment in the server, it becomes possible to cope with different application distribution platforms, so that the range of application selection can be expanded. It has the advantage of helping service providers expand opportunities and improve user convenience. In addition, if different versions of the OS can be operated simultaneously, it is possible to use an application that operates only in the old OS environment, and even if there is a difference between the OS update and the application update time of the application provider, the end user However, there is an advantage that the application can be continuously provided.

Also, in this embodiment, the service provider provides the service provision by having the function of managing the services provided by the service provider and the users, various sensors, and devices connected to each home network on the center side. There is an advantage that it is possible to obtain a status report and grasp the actual use of the service. In addition, it is effective for those who plan to enter the market or those who are trying to open the market by making it possible to provide the service provider and other companies with statistical information such as user usage. Advantageous information can be provided.
In addition, it has a function that can manage the correspondence of different services of multiple service providers to various sensors and devices connected to each home network, eliminating the need for overlapping arrangements of similar sensors for each service provider And there is an advantage that the capital investment of the service provider can be reduced. In addition, by sharing information acquired from sensors, there is an advantage that communication service can be reduced by expanding the possibility of entry of new service providers and reducing redundant sensor data acquisition. .

  INDUSTRIAL APPLICABILITY The present invention can be used, for example, in a home network system that provides a home network and a system that centrally installs an application execution function of a home gateway arranged in a user's home on the center side.

DESCRIPTION OF SYMBOLS 1 Virtualized home gateway server 2 Virtualized home gateway interface part 3 Home network 4 Various household devices and sensors 5 Wide area network 6 Multiple service providers 7 Virtual machine VM
8 Management Center 9 Storage Device 10 Service Management Department

Claims (9)

Virtual home gateways that perform one or more of control, information collection, and protocol conversion of devices and sensors distributed by one or a plurality of first providers and connected to each home network are collectively arranged to provide a plurality of homes. A virtualized home gateway server connected to the network;
A device database storing the type of the device and sensor connected to each home network, and the identification information of the first provider of the distribution source;
An operator billing database for storing billing information by using data of the device and sensor of the first operator by the second operator;
In response to a device use request from a second operator including the type of desired device and sensor, the device database of the first operator corresponding to the desired device and sensor is referred to by referring to the device database. With a management department to identify,
The management unit
Enter a subscription request from a user for a service by a second operator using the data of the device and sensor of the identified first operator,
A virtual home gateway system that stores billing information in which a first business is a billing source and a second business is a billing destination in the business billing database. The device database further stores other business operator availability information corresponding to the identification information of the first business operator and the type of the device and sensor,
The management unit refers to the device database and identifies the device and sensor of the first business operator that corresponds to the desired device and sensor and whose other business operator availability information indicates availability. Item 2. The virtual home gateway system according to Item 1. The device database further stores usage fee information when the second company uses the device and the sensor in correspondence with the identification information of the first company,
The billing information stored in the billing database includes billing amount information in which the first business is billed and the second business is billed.
The virtual home gateway system according to claim 1, wherein the management unit updates billing amount information of the billing database based on the usage fee information of the first operator in response to the subscription request. A subscriber database in which identification information of users corresponding to the home network and identification information of the devices and sensors connected to the home network are stored correspondingly;
The management unit identifies the corresponding user by referring to the subscriber database based on the identified identification information of the device and sensor,
The virtual home gateway system according to claim 1, wherein service guidance information by a second operator is transmitted to the user. The device database further stores measurement range information and / or accuracy information of the device and sensor corresponding to the identification information of the first business operator and the type of the device and sensor,
The device usage request from the second operator includes a desired device and sensor type, a required measurement range and / or required accuracy of the sensor,
The management unit
In response to the device use request, the device database is specified, and the device and sensor of the first operator corresponding to the desired device and sensor and satisfying the required measurement range and / or required accuracy are specified. The virtual home gateway system according to claim 1. The management unit transmits an application for acquiring data of the device and sensor of the identified first operator to the virtualized home gateway server,
The virtual home gateway system according to claim 1, wherein the data of the device and sensor of the first operator acquired by executing the application is used for a service by the second operator. The data of the device and sensor of the first operator are stored in a temporary file,
The virtual home gateway system according to claim 6, wherein the data of the device and the sensor of the first operator stored in the temporary file is used for a service by the second operator.   The virtual home gateway system according to claim 1, wherein the management unit transmits information related to the device and sensor of the identified first business operator to a device of the second business operator. The virtual home gateway system according to claim 1, further comprising a home gateway interface unit that is arranged in each home network and connects the home network and the virtual home gateway server via a wide area network.

Images