WO2012160861A1 - Software automatic deployment device - Google Patents

Abstract

When triggered by an M2M device being connected, the software automatic deployment device downloads a necessary program (serving software) and notifies or sets address information pertaining to the M2M device or identification information pertaining to the M2M device, or both the address information and the identification information, for the serving software.

Description

Software automatic deployment device

The present invention relates to an automatic software deployment apparatus that downloads and installs a required program.

In recent years, technologies for using sensor devices, actuator devices, and the like in smart grids, home networks, office networks, and the like have attracted attention. In smart grids and home networks, various types of information (power consumption information, temperature information, vibration information, sound information, etc.) that change every moment in each local area (office, factory, home, car, etc.) Sensor devices, known environmental measuring devices, and the like are used. Information obtained from these sensor devices and the like is not only processed by an information processing device such as a server provided in each local area, but also the Internet network, 3G network (or LTE (Long Term Evolution) network in the future), It is also considered that the data is transmitted to an external server via a Wimax (Worldwide Interoperability for Microwave Access) network and processed by the server. For example, the power consumption information of each home is stored and processed by an information processing device provided in each home, and transmitted to a server such as an operator (power generation company, power transmission company, power distribution company) that supplies power to each home. It is also under consideration to be managed by the server. Also, various actuators (devices that change the environment) installed in each local area are controlled by servers in each local area, as well as sensor devices, or external servers via the Internet network, etc. It is being considered to control from the beginning. Furthermore, in home networks and office networks, not only sensor devices and actuator devices, but also home appliances called black goods such as television receivers and audio equipment, and home appliances called white goods such as refrigerators and air conditioners. In addition, by connecting to a local network, it is considered that these home appliances are controlled by a server and other devices (any device connected to a network including a PC (Personal Computer)). Also, consider controlling these home appliances by connecting them to a server outside the local network via the Internet network, 3G network (or LTE network in the future), Wimax network, etc. Has been.

In this way, by connecting various devices that were not connected to the network to the network, or by connecting various devices to each other to form a network, various services that were not previously available M2M (Machine to Machine) technology aimed at realization is attracting attention.

Hereinafter, devices that can be connected to a network such as sensor devices, actuator devices, black appliances, and white appliances are collectively referred to as “M2M devices”. A service realized by the M2M device is referred to as an “M2M service”.

When an M2M device connected to a local network transmits / receives information to / from other M2M devices, servers, PCs, etc. connected to the local network, it is often difficult for these devices to communicate directly. For example, a sensor device that communicates according to the ZigBee protocol among M2M devices transmits and receives information to / from a server or PC that communicates according to TCP / IP (Transmission Control Protocol / Internet Protocol). Etc., it is necessary to provide a TCP / IP stack. On the other hand, even in the case of a device such as an air conditioner or a television receiver equipped with a TCP / IP stack, for example, in order to obtain room temperature information measured by the air conditioner with the television receiver, the air conditioner is connected to the television receiver. It is necessary to provide a function for acquiring conditioner information. In that case, the cost of the television receiver increases.

As described above, M2M devices often have difficulty in mounting functions for directly communicating with other M2M devices, servers, PCs, and the like due to device specifications and cost constraints, and are barriers to the spread of M2M services. It has become.

Therefore, a method to realize M2M service by providing a gateway (HGW: Home Gate Way, BGW: Building Gate Way, etc.) that relays communication between M2M devices or between M2M devices and servers and PCs in the network is considered. Has been.

For example, a sensor device that measures temperature / humidity sends temperature / humidity information measured according to the ZigBee communication protocol to the gateway, and the gateway sends the received temperature / humidity information to the server via TCP / IP communication, thereby directly transmitting the information. Enables communication between a sensor device that cannot send and receive and a server.

In addition, the gateway may have a function for providing various M2M services using the M2M device as well as relaying communication between the M2M devices or between the M2M device and the server or the PC. For example, a function of receiving temperature information from a sensor device and transmitting the temperature information to a specific server via the Internet network, or receiving detection information from a human sensor, and shooting direction of a network camera based on the detection information There is a function to control.

There are a wide variety of M2M devices, servers, and PCs, and the services that can be realized by communication between these devices or that can be provided by communication between these devices are even more diverse. Therefore, the gateway requires not only functions necessary for communication with various devices but also various programs (service software) for realizing various functions that can be provided by the communication.

However, if a lot of service software is installed in the gateway in advance, it requires high computing capacity and large storage capacity in the gateway. Therefore, in order to realize the M2M service, a technique for downloading and installing only the necessary service software on the gateway when necessary is required.

As such a technique, an automatic activation technique for downloading and installing only necessary service software from the distribution server to the gateway when the M2M device is connected to the gateway or when a service request using the M2M device is requested has been studied. Yes.

In the configuration using automatic activation technology, it is not necessary to install a lot of service software in the gateway in advance, so it is possible to reduce the storage capacity required for the gateway and increase the cost of the gateway. Can be suppressed.

The gateway described above can use the OSGi framework defined by the OSGi Alliance as a service software platform. The OSGi framework is a platform implemented on a Java VM (Java Virtual Machine: “Java” is a registered trademark), and can operate with Java (registered trademark) software called an OSGi bundle. The OSGi bundle can be plugged in on the OSGi framework, and can be installed or uninstalled as necessary. Therefore, it is suitable as a gateway platform equipped with automatic activation technology. In other words, the gateway may be configured to use the OSGi framework as a service software platform. However, the gateway can include other platforms for the service software, and the automatic activation technology is not limited to the OSGi framework or the OSGi bundle.

Note that Patent Document 1 allows communication between a gateway and each home appliance via a network by assigning an IP address to each home appliance such as a television receiver or an air conditioner connected to the gateway. The technology to do is described.

In the automatic activation technology described above, there is a problem that M2M devices, servers, PCs (hereinafter referred to as M2M service providing servers) that provide services cannot identify M2M devices that are used in the services.

When providing an M2M service using an M2M device, the M2M service providing servers need to communicate with the M2M device via the gateway according to service software distributed to the gateway. At this time, the M2M service providing servers must acquire the address information and the like of the M2M device used in the M2M service using some means.

If service software for providing M2M services has a function for acquiring address information of M2M devices and a function for notifying address information to M2M service providing servers, the scale of the service software increases. There's a problem. In addition, since the function for acquiring the address information of the M2M device and the function for notifying the address information to the M2M service providing servers can often be realized by a common program, the same function is provided to a plurality of service software. Providing is redundant and inefficient.

In the following, various devices including the gateway, which provide M2M service by downloading necessary service software from a server that distributes the service software and realizing communication between the M2M device and M2M service providing servers. Is called a software automatic deployment device. A system for providing an M2M service including the software automatic deployment apparatus, M2M device, M2M service providing servers, and a server that distributes the service software is referred to as a software automatic deployment system.

JP 2002-0778036 A

Therefore, an object of the present invention is to provide an automatic software deployment apparatus that enables communication between an M2M service providing server that provides an M2M service and an M2M device used in the M2M service, thereby realizing the M2M service.

In order to achieve the above object, a software automatic deployment apparatus of the present invention includes a software distribution processing unit that downloads service software for providing a service using a device connectable to a network,
An address notification setting unit for notifying or setting the address information of the device included in the management information of the device acquired using a protocol for managing the device or a function for managing the device to the downloaded service software; ,
Have

FIG. 1 is a block diagram illustrating a configuration example of a software automatic deployment system according to the first embodiment. FIG. 2 is a table diagram showing an example of group information stored in the group information DB shown in FIG. FIG. 3 is a block diagram illustrating another configuration example of the software automatic deployment system according to the first embodiment. FIG. 4 is a block diagram illustrating another configuration example of the software automatic deployment system according to the first embodiment. FIG. 5 is a flowchart illustrating an example of processing of the software automatic deployment apparatus according to the first embodiment. FIG. 6 is a schematic diagram illustrating a state in which the M2M service is provided by the software automatic deployment system according to the first embodiment. FIG. 7 is a block diagram illustrating a configuration of a modified example of the software automatic deployment system according to the first embodiment. FIG. 8 is a flowchart showing an example of processing of the address notification / setting processing apparatus shown in FIG. FIG. 9 is a block diagram illustrating a configuration example of the software automatic deployment system according to the second embodiment. FIG. 10 is a table diagram showing an example of group information stored in the group information DB shown in FIG. FIG. 11 is a block diagram illustrating another configuration example of the software automatic deployment system according to the second embodiment. FIG. 12 is a flowchart illustrating an example of processing of the software automatic deployment apparatus according to the second embodiment. FIG. 13 is a block diagram illustrating a configuration of a modified example of the software automatic deployment system according to the second embodiment. FIG. 14 is a flowchart illustrating an example of processing of the ID notification / setting processing apparatus illustrated in FIG. 13. FIG. 15 is a block diagram illustrating a configuration example of a software automatic deployment system according to the third embodiment. FIG. 16 is a table showing an example of group information stored in the group information DB shown in FIG. FIG. 17 is a flowchart illustrating an example of processing of the software automatic deployment apparatus according to the third embodiment. FIG. 18 is a block diagram illustrating a configuration of a modified example of the software automatic deployment system according to the third embodiment. FIG. 19 is a flowchart illustrating an example of processing of the address and ID notification / setting processing apparatus illustrated in FIG.

Next, the present invention will be described with reference to the drawings.

The software automatic deployment apparatus of the present invention downloads a necessary program (service software) when the M2M device is connected, and addresses the M2M device, identification information of the M2M device, or both address information and identification information. Is notified or set to the service software.
(First embodiment)
When the M2M device is connected, the software automatic deployment apparatus according to the first embodiment acquires address information from the M2M device using the M2M device management function prepared in advance, and the acquired M2M device address information and A set information including service software information, which is a program for realizing the M2M service, used in the M2M device or used in the M2M device is generated and stored. Then, when the download of the service software is completed, or when the service software has already been downloaded, the address information of the M2M device, the identification information generated from the address information, or the address information and the identification based on the stored set information Both information is notified or set to the service software.

The address information of the M2M device is information similar to a network address used for communication with the M2M device via the network, such as an IP address or a ZigBee network address.

The identification information of the M2M device is information similar to an ID (identifier) for uniquely identifying the M2M device, which is generated from a MAC (Media Access Control) address, a network address, and other device information. Various types of information such as a URL (Uniform Resource Locator) and a numeric string can be used as the identification information, and the present invention does not limit the format of the identification information. Further, if the M2M device can be uniquely identified even with address information such as a MAC address, the address information can be used as the identification information.

FIG. 1 is a block diagram illustrating a configuration example of a software automatic deployment system according to the first embodiment. A solid line arrow shown in FIG. 1 indicates a transmission / reception direction of information (including commands), and a broken line arrow shown in FIG. 1 indicates a distribution direction of service software.

As shown in FIG. 1, the software automatic deployment system of this embodiment includes an M2M device 51, a software distribution server 52, and a software automatic deployment apparatus 1A.

The M2M device 51 is a device that realizes an M2M service, such as a sensor device, an actuator device, a black appliance, a white appliance, or the like.

The software distribution server 52 is a server that distributes required service software in accordance with a request from the software automatic deployment apparatus 1A. When the distribution of the service software is completed, the software distribution server 52 transmits information indicating the distribution completion to the software automatic deployment apparatus 1A that requested the distribution.

The software automatic deployment apparatus 1A notifies or sets the address information of the M2M device 51 to the service software for realizing the M2M service distributed from the software distribution server 52. The software distribution server 52 and the software automatic deployment apparatus 1A shown in FIG. 1 can be realized by a known information processing apparatus.

As shown in FIG. 1, the software automatic deployment apparatus 1A includes a device driver 11 that is an interface for communicating with a connected M2M device 51, a device management unit 12 that manages the M2M device 51, and service software distribution processing. M2M by executing processing in accordance with the software distribution processing unit 13 that performs communication, the external connection interface 14 that is a communication interface for communicating with an external device, such as a TCP / IP stack, and the distributed service software A service software unit 16 that implements a service using a device, and an address notification / setting processing unit 15 that notifies or sets the address information of the M2M device to the service software executed by the service software unit 16.

The software distribution processing unit 13 includes a software distribution management unit 131, a software selection unit 132, and a distribution DB 133. The address notification / setting processing unit 15 includes an address notification / setting management unit 151, a database creation unit 152, an address selection unit 153, and a set information DB 154.

The device driver 11 is an interface that directly transmits and receives information to and from the M2M device 51 according to a protocol such as ZigBee, and is used when the service software unit 16 communicates with the M2M device 51 according to the distributed service software. The device driver 11 obtains device management information (address information, manufacturer code, device name, device identifier such as a MAC address, manufacturing number, etc., information indicating the device status, etc. acquired from the M2M device in response to a request from the device management unit 12 Are notified to the device management unit 12. In addition, the device driver 11 transmits a management message notified from the device management unit 12 to the M2M device. Furthermore, the device driver 11 implements communication between the service software unit 16 and the M2M device. The device driver 11 is provided corresponding to the type of M2M device. That is, the software automatic deployment apparatus 1A includes a plurality of device drivers 11.

The device management unit 12 manages the M2M device 51 connected via the device driver 11. The device management unit 12 is a management function such as UPnP (Universal Plug and Play) protocol, ZigBee protocol, Z-Wave protocol, or TR-069 (Technical Report 069) protocol, OMA-DM (Open Mobile Alliance-Device Management) protocol. The M2M device 51 is managed by a management function according to a communication stack and protocol provided in the M2M device 51, such as a remote management function such as. The device management unit 12 may have all of these various management functions, or may have only some management functions. The device management unit 12 notifies the software distribution management unit 131 included in the software distribution processing unit 13 of the device management information acquired from the M2M device 51 using the management function.

Based on the device management information acquired from the M2M device 51, the software distribution processing unit 13 is necessary for the M2M service using the M2M device 51, such as software and management software for providing the service, or services such as driver software Software is selected, and the software distribution server 52 is requested to distribute the service software via the external connection interface 14. Further, the software distribution processing unit 13 receives information indicating completion of distribution of the service software notified from the software distribution server 52. Further, the software distribution processing unit 13 sends the distributed service software and the address information of the M2M device necessary for the M2M service using the service software to the address notification / setting management unit 151 provided in the address notification / setting processing unit 15. Notice.

The software distribution management unit 131 notifies the device selection information acquired from the device management unit 12 to the software selection unit 132, and acquires information on the service software requested to be distributed to the software distribution server 52 determined by the software selection unit 132. . Based on the service software information, the software distribution management unit 131 requests the software distribution server 52 to distribute the service software via the external connection interface 14. Further, it notifies the address notification / setting management unit 151 included in the address notification / setting processing unit 15 of the service software information and the address information of the M2M device necessary for the service using the service software. When the software distribution management unit 131 receives information indicating the completion of the distribution of the service software from the software distribution server 52, the software distribution management unit 131 notifies the address notification / setting management unit 151 of the distribution completion of the service software. Also, the software distribution management unit 131 notifies the device selection information acquired from the device management unit 12 to the software selection unit 132. If the service software selected by the software selection unit 132 has already been downloaded, address notification / setting management is performed. Registration to the group information DB 154 is completed at any timing after notifying the unit 151 of the service software information and the address information of the M2M device necessary for the M2M service using the service software, or from the address notification / setting management unit 151 At the timing when the notification is received, the address notification / setting management unit 151 is notified of the completion of distribution of the service software.

The software selection unit 132 determines service software necessary for providing a service using the M2M device 51 based on the device management information acquired from the software distribution management unit 131. The service software is selected using set information including device management information and service software information stored in the distribution DB 133 using any information included in the device management information as a key. The software selection unit 132 notifies the software distribution management unit 131 of information on the selected service software.

The distribution DB 133 stores set information including device management information and service software information for providing the M2M service.

The external connection interface 14 is a communication interface between the software automatic deployment apparatus 1A and the external apparatus. The external connection interface 14 of the present embodiment serves as a communication interface with the software distribution server 52 or M2M service providing servers (not shown).

The address notification / setting processing unit 15 acquires the information of the distributed service software received from the software distribution management unit 131 and the address information of the M2M device necessary for the service using the service software, and sets the combination information. Generate. When the address notification / setting processing unit 15 receives the information indicating the completion of the distribution of the service software from the software distribution management unit 131, the address notification / setting processing unit 15 extracts the address information of the M2M device 51 necessary for the service using the service software. It notifies or sets the address information of the M2M device to the software unit 16.

The address notification / setting management unit 151 notifies the database creation unit 152 of the service software information acquired from the software distribution management unit 131 and the address information of the M2M device necessary for the service using the service software. When the address notification / setting management unit 151 receives the information indicating the completion of the distribution of the service software from the software distribution management unit 131, the address notification / setting management unit 151 notifies the address selection unit 153 of the information of the service software that has been distributed, and the service software unit 16 The address information of the M2M device to be notified or set is acquired. The address notification / setting management unit 151 notifies or sets the acquired address information of the M2M device to the service software unit 16.

The database creation unit 152 generates, for example, set information as illustrated in FIG. 2 from the service software information received from the address notification / setting management unit 151 and the address information of the M2M device, and registers the generated set information in the set information DB 154. As shown in FIG. 2, the group information includes service software used or address information of an M2M device used in the service software, and distribution completion information indicating whether the service software has already been downloaded. Configured and registered for each service software.

Since the service software can normally be used in a plurality of M2M devices, the database creation unit 152 receives information on the service software already registered in the group information DB 154 from the address notification / setting management unit 151 and the service software. When the address information of the M2M device corresponding to the software is acquired, the address information of the M2M device is added to the corresponding service software set information registered in the set information DB 154.

Upon receiving the service software delivery completion notification from the address notification / setting management unit 151, the address selection unit 153 acquires the address information of the M2M device necessary for the service using the service software from the set information DB 154, and receives the address notification / The setting management unit 151 is notified.

The set information DB 154 stores set information 6A including the service software information 61, the M2M device address information 62, and the distribution completion information 63 illustrated in FIG.

The service software information 61 uses information for identifying service software such as a program name and a program identification number. The address information 62 is address information of the M2M device 51. As described above, a plurality of address information 62 of the M2M device 51 can be provided corresponding to the service software information 61. The distribution completion information 63 is information indicating whether the service software has already been distributed to the software automatic deployment apparatus 1A.

The service software unit 16 implements an M2M service using the M2M device 51 by executing processing according to the distributed program (service software). The service software unit 16 exists for each M2M service, each combination of M2M services, each M2M device, or each combination of M2M devices. That is, the software automatic deployment apparatus 1 </ b> A may include a plurality of service software units 16.

The distribution DB 133 shown in FIG. 1 may be provided outside the software distribution processing unit 13, and the set information DB 154 shown in FIG. 1 may be provided outside the address notification / setting processing unit 15. Further, the distribution DB 133 and the set information DB 154 may be provided outside the software automatic deployment apparatus 1A. Unless otherwise specified, databases such as the distribution DB 133 and the set information DB 154 can be provided outside the software distribution processing unit 13 and address notification / setting processing unit 15 or outside the software automatic deployment apparatus 1A. And

The M2M device 51 and the software distribution server 52 correspond not only to the software automatic deployment apparatus 1A shown in FIG. 1 but also to other configuration examples (software automatic deployment apparatuses 1B and 1C) described later. .

FIG. 3 is a block diagram illustrating another configuration example of the software automatic deployment system according to the first embodiment. 3 indicates the transmission / reception direction of information (including commands), and the dashed arrow illustrated in FIG. 3 indicates the distribution direction of the service software.

The software automatic deployment system shown in FIG. 3 includes a software automatic deployment apparatus 1B instead of the software automatic deployment apparatus 1A shown in FIG. The software automatic deployment apparatus 1B converts the address information of the M2M device 51 into identification information, and notifies or sets the identification information of the M2M device 51 or the identification information and address information of the M2M device 51 to the corresponding service software unit 16. The software automatic deployment apparatus 1B shown in FIG. 3 has a configuration in which an ID generation / management unit 17 is added to the software automatic deployment apparatus 1A shown in FIG. The software automatic deployment apparatus 1B can be realized by a known information processing apparatus.

In addition to the same function as the software automatic deployment apparatus 1A shown in FIG. 1, the device driver 11 sends device management information including address information of the M2M device 51 to the ID generation / management unit 17 in accordance with a request from the device management unit 12. Notice.

The device management unit 12 notifies the ID generation / management unit 17 of the device management information of the M2M device 51 including the address information in addition to the same function as the software automatic deployment apparatus 1A shown in FIG. The automatic software deployment apparatus 1B illustrated in FIG. 3 is configured to be able to notify the ID generation / management unit 17 of device management information of the M2M device 51 from the device driver 11 and the device management unit 12, respectively. The device management information of the M2M device 51 may be notified to the ID generation / management unit 17 from either the device driver 11 or the device management unit 12, and the ID generation / management unit 17 from the device driver 11 and the device management unit 12. May be notified respectively.

The address notification / setting processing unit 15 shown in FIG. 3 is different from the software automatic deployment apparatus 1A shown in FIG. 1 in the function of the address notification / setting management unit 151. Other functions and configurations are the same as those of the software automatic deployment apparatus 1A.

The address notification / setting management unit 151 notifies the database creation unit 152 of the service software information acquired from the software distribution management unit 131 and the address information of the M2M device necessary for the service using the service software. When the address notification / setting management unit 151 receives information indicating the completion of the distribution of the service software from the software distribution management unit 131, the address notification / setting management unit 151 notifies the address selection unit 153 of the information of the service software that has been distributed, and the corresponding service software The address information of the M2M device 51 to be notified or set to the unit 16 is acquired. Further, the address notification / setting management unit 151 notifies the ID generation / management unit 17 of the address information of the M2M device acquired from the address selection unit 153.

The ID generation / management unit 17 generates M2M device identification information based on the device management information including the address information of the M2M device acquired from either or both of the device driver 11 and the device management unit 12, and addresses information And set information consisting of the identification information. Also, the ID generation / management unit 17 extracts identification information corresponding to the address information acquired from the address notification / setting management unit 151 based on the set information, and sends the address information or the identification information to the corresponding service software unit 16. Either one of them, or address information and identification information is notified or set.

The functions of the software distribution processing unit 13, the external connection interface 14, and the service software unit 16 included in the software automatic deployment apparatus 1B illustrated in FIG. 3 are the same as those of the software automatic deployment apparatus 1A illustrated in FIG.

FIG. 4 is a block diagram illustrating another configuration example of the software automatic deployment system according to the first embodiment. The solid arrows shown in FIG. 4 indicate the transmission / reception direction of information (including commands), and the broken arrows shown in FIG. 4 indicate the distribution direction of the service software.

The software automatic deployment system shown in FIG. 4 includes a software automatic deployment apparatus 1C instead of the software automatic deployment apparatus 1A shown in FIG. The software automatic deployment apparatus 1C has the same configuration as the software automatic deployment apparatus 1B shown in FIG. However, in the software automatic deployment apparatus 1C, when the address information of the M2M device is notified to the service software unit 16 and the reference of the identification information of the M2M device is requested from the service software unit 16, the request is responded. The service software unit 16 is notified of the identification information of the M2M device. The software automatic deployment apparatus 1C can be realized by a known information processing apparatus.

The function of the address notification / setting processing unit 15 is the same as that of the software automatic deployment apparatus 1A shown in FIG.

The service software unit 16 is notified or set of the address information of the M2M device 51 by the address notification / setting management unit 151, as in the software automatic deployment apparatus 1A shown in FIG. The service software unit 16 requests the ID generation / management unit 17 to refer to the identification information of the M2M device 51 based on the notified or set address information. The service software unit 16 acquires the identification information of the M2M device by referring to the identification information of the M2M device.

Similar to the software automatic deployment apparatus 1B illustrated in FIG. 3, the ID generation / management unit 17 uses the M2M device 51 acquired from either the device driver 11 or the device management unit 12, or the device driver 11 and the device management unit 12. Identification information of the M2M device 51 is generated based on the device management information including the address information, and the address information and the combination information of the identification information are managed. Further, when the service software unit 16 requests reference (inquiry) of identification information using the address information as a key, the ID generation / management unit 17 provides the identification information corresponding to the requested address information to the service software unit 16. Return to

The functions of the device driver 11, the device management unit 12, the software distribution processing unit 13, and the external connection interface 14 included in the software automatic deployment apparatus 1C illustrated in FIG. 4 are the same as those of the software automatic deployment apparatus 1A illustrated in FIG.

Next, operations of the software automatic deployment apparatuses 1A, 1B, and 1C according to the first embodiment will be described with reference to FIG. Hereinafter, the software automatic deployment apparatuses 1A, 1B, and 1C are collectively referred to as “software automatic deployment apparatus 1”.

FIG. 5 is a flowchart illustrating an example of processing of the software automatic deployment apparatus according to the first embodiment.

As shown in FIG. 5, the software automatic deployment apparatus 1 monitors whether or not the M2M device 51 is connected (step S10). If the M2M device 51 is not connected, the process of step S10 is repeated.

When the M2M device 51 is connected, the software automatic deployment apparatus 1 acquires device management information from the connected M2M device 51 and requests a software distribution server for distribution based on the device management information (service) Software) is determined (step S11).

Next, the software automatic deployment apparatus 1 determines whether or not the service software determined in step S11 has been downloaded (step S12).

When the service software determined in step S11 has already been downloaded, the software automatic deployment apparatus 1 includes a set of the service software information and the address information of the M2M device 51 necessary for the M2M service using the service software. The address information of the M2M device 51 extracted from the device management information acquired in step S10 is added to the information to update the set information (step S16). Thereafter, the process proceeds to step S17.

If the service software determined in step S11 has not been downloaded, the software automatic deployment apparatus 1 requests the software distribution server 52 to distribute the service software (step S13). Also, pair information composed of the service software information determined in step S11 and the M2M device address information necessary for the M2M service using the service software is generated and stored (step S14).

Next, the software automatic deployment apparatus 1 determines whether or not the distribution of the service software requested in step S13 is completed (step S15), and if the distribution is completed, the process proceeds to step S17. If the distribution has not been completed, the process of step S15 is repeated.

In step S17, the software automatic deployment apparatus 1 obtains the address information of the M2M device necessary for the M2M service using the service software determined in step S11 from the pair information created in step S14 or the pair information updated in step S16. get.

Then, the service software determined in step S11 includes the address information of the M2M device 51 acquired in step S17, the identification information of the M2M device 51 converted from the address information of the M2M device 51, or both the address information and the identification information. Accordingly, the service software unit 16 that executes the process is notified or set (step S18).

In the process shown in FIG. 5, the order of the processes in steps S13 and S14 may be reversed.

FIG. 6 is a schematic diagram illustrating a state in which the M2M service is provided by the software automatic deployment system according to the first embodiment. FIG. 6 shows how an M2M service is provided using service software distributed to the software automatic deployment apparatuses 1A, 1B, and 1C. 6 indicates the transmission / reception direction of information (including commands) of the M2M device 51 and the M2M service providing servers, and the dashed arrow illustrated in FIG. 6 indicates the distribution direction of the service software.

As shown in FIG. 6, a program (service software) for realizing an M2M service is distributed from the software distribution server 52 to the software automatic deployment apparatuses 1A, 1B, and 1C via, for example, the Internet network. The software automatic deployment apparatuses 1A, 1B, and 1C have the service software unit 16 corresponding to the service software distributed from the software distribution server 52 by using the address information, identification information, or both address information and identification information of the connected M2M device 51. Is communicated with the M2M device 51.

The M2M service is realized by communication between the M2M device 51 and the M2M service providing servers 55 via the software automatic deployment apparatuses 1A, 1B, and 1C.

6 shows a configuration example in which the software automatic deployment apparatuses 1A, 1B, and 1C, the M2M service providing servers 55, and the software distribution server 52 are connected via the Internet network. The 1A, 1B, 1C, the M2M service providing server 55 and the software distribution server 52 are not limited to the Internet network, but are a LAN (Local Area Network) network, a WAN (Wide Area Network) network, or a PAN (Personal Area Network) network. It may be connected via. As a network used for communication, there are a LAN network and a WAN network using a TCP / IP protocol, a PAN network using a protocol such as ZigBee and Z-Wave, a 3G network, a next generation LTE network, and a WiMax network.

Next, a modification of the software automatic deployment system according to the first embodiment will be described with reference to FIG.

The software automatic deployment system shown in FIG. 7 has the functions of the device management unit 12, the software distribution processing unit 13, and the address notification / setting processing unit 15 included in the software automatic deployment apparatuses 1A, 1B, and 1C as external devices. It is.

The software automatic deployment apparatuses 1A ′, 1B ′, and 1C ′ are configured by removing the functions of the device management unit 12, the software distribution processing unit 13, and the address notification / setting processing unit 15 from the software automatic deployment apparatuses 1A, 1B, and 1C. Yes, the address information, identification information, or address information and identification information of the M2M device 51 is notified or set to the service software unit 16 corresponding to the distributed program (service software).

The software distribution processing server 54 is a server that realizes the function of the software distribution processing unit 13. The software distribution processing server 54 requests the software distribution server 52 to distribute service software necessary for the software automatic deployment apparatuses 1A ′, 1B ′, and 1C ′. Further, the software distribution processing server 54 notifies and sets the address information of the service software to be distributed to the software automatic deployment apparatuses 1A ′, 1B ′ and 1C ′ and the address information of the M2M device necessary for the M2M service using the service software. In addition to notifying the processing device 4A, when the distribution of the service software to the software automatic deployment devices 1A ′, 1B ′, 1C ′ is completed, information indicating the completion of distribution is transmitted to the address notification / setting processing device 4A.

The device remote management server 53 is a server that realizes the function of the device management unit 12. The device remote management server 53 manages the M2M device 51 via the software automatic deployment apparatuses 1A ′, 1B ′, and 1C ′, and notifies the software distribution processing server 54 of device management information.

The address notification / setting processing device 4A is a device that realizes the function of the address notification / setting processing unit 15, and includes an address notification / setting management unit 41, a database creation unit 42, an address selection unit 43, a set information DB 44, and an external connection. An interface 45 is provided.

The address notification / setting management unit 41 has the same function as the address notification / setting management unit 151, and the database creation unit 42 has the same function as the database creation unit 152. The address selection unit 43 has the same function as the address selection unit 153, and the set information DB 44 has the same function as the set information DB 154. The external connection interface 45 is a communication interface that realizes communication with an external device.

Note that the software automatic deployment system shown in FIG. 7 does not have to include all the functions of the device management unit 12, the software distribution processing unit 13, and the address notification / setting processing unit 15 as external devices. It may be configured to have a function. In that case, the software automatic deployment apparatuses 1A ′, 1B ′, and 1C ′ may have a function that is not realized by an external apparatus.

Next, the operation of the address notification / setting processing device 4A shown in FIG. 7 will be described with reference to FIG.

FIG. 8 is a flowchart showing an example of processing of the address notification / setting processing apparatus shown in FIG.

As shown in FIG. 8, the address notification / setting processing device 4A generates, from the software distribution processing server 54, set information including service software and address information of the M2M device 51 necessary for the M2M service using the service software. Is monitored (step S40). When the creation of the group information is requested, it is determined whether or not the group information requested to be created already exists (step S41).

If the group information requested to be created does not exist, the address notification / setting processing device 4A includes the requested service software information and the address information of the M2M device 51 required for the M2M service using the service software. Information is generated and stored (step S42).

If the set information requested to be created already exists, the address notification / setting processing device 4A adds the address information of the M2M device 51 to the set information and updates the set information (step S43).

If it is determined in step S40 that creation of group information has not been requested, the address notification / setting processing device 4A determines whether or not the distribution of service software has been notified from the software distribution processing server (step S44). When the service software distribution completion is not notified, the address notification / setting processing device 4A repeats the processing from step S40.

When the service software distribution completion is notified, the address notification / setting processing device 4A uses the service software notified of the distribution completion based on the group information created in step S42 or the group information updated in step S43. The address information of the M2M device necessary for the existing M2M service is acquired (step S45).

Then, the address information of the M2M device acquired in step S45 is notified to the software automatic deployment apparatuses 1A ′, 1B ′, 1C ′, the address information of the M2M device 51, the identification information of the M2M device 51 converted from the address information, Alternatively, both the address information and the identification information are notified or set to the service software unit 16 corresponding to the service software distributed to the software automatic deployment apparatuses 1A ′, 1B ′, 1C ′ (step S46).

According to the present embodiment, the address information of the M2M device 51 and the M2M device 51 which are acquired by using the M2M device management function by the software automatic deployment apparatuses 1A, 1B, 1C or 1A ′, 1B ′, 1C ′ are used. M2M service for providing M2M service by storing set information with service software for realizing the service and notifying or setting address information of the M2M device 51 to the corresponding service software unit 16 based on the stored set information The providing servers can identify the M2M device 51 used in the M2M service and can communicate with the M2M device 51. Accordingly, the M2M service providing servers can provide the M2M service using the M2M device 51. Further, since the service software does not need to have a function for acquiring the address information of the M2M device and a function for notifying the address information to the M2M service providing servers, the development cost of the service software can be reduced.
(Second Embodiment)
Next, a second embodiment of the present invention will be described with reference to the drawings.

When the M2M device is connected, the software automatic deployment apparatus according to the second embodiment acquires address information from the M2M device using the management function of the M2M device prepared in advance, and from the acquired address information of the M2M device Identification information is generated, and combination information composed of the identification information and service software information, which is a program for realizing the M2M service, used in the M2M device or used in the M2M device is generated and stored. When the download of the service software is completed, or when the service software has already been downloaded, the identification information of the M2M device based on the stored set information, or the address information requested based on the identification information, Notify or set the service software.

FIG. 9 is a block diagram illustrating a configuration example of the software automatic deployment system according to the second embodiment. The solid arrows shown in FIG. 9 indicate the transmission / reception direction of information (including commands), and the broken arrows shown in 9 indicate the distribution direction of the service software.

As shown in FIG. 9, the software automatic deployment system of this embodiment includes an M2M device 51, a software distribution server 52, and a software automatic deployment apparatus 2A.

The M2M device 51 is a device that realizes an M2M service, such as a sensor device, an actuator device, a black appliance, a white appliance, or the like.

The software distribution server 52 is a server that distributes service software in accordance with a request from the software automatic deployment apparatus 2A. When the distribution of the service software is completed, the software distribution server 52 transmits information indicating the completion of distribution to the software automatic deployment apparatus 2A that requested the distribution.

The software automatic deployment apparatus 2A notifies or sets the identification information of the M2M device 51 to the service software unit that executes processing according to the service software distributed from the software distribution server 52.

The software distribution server 52 and the software automatic deployment apparatus 2A can be realized by a known information processing apparatus.

The software automatic deployment apparatus 2A includes a device driver 21 that is an interface for communicating with the connected M2M device 51, a device management unit 22 that manages the M2M device 51, and a software distribution processing unit 23 that performs service software distribution processing. A service using an M2M device is realized by executing processing according to the external connection interface 24 realized by a TCP / IP stack or the like, which is a communication interface for communicating with an external device, and the distributed service software A service software unit 26, an ID notification / setting processing unit 25 that notifies or sets identification information of the M2M device to the service software unit 26, and an ID generation / management unit 27 that generates and manages the identification information of the M2M device. Have.

The software distribution processing unit 23 includes a software distribution management unit 231, a software selection unit 232, and a distribution DB 233.

The ID notification / setting processing unit 25 includes an ID notification / setting management unit 251, a database creation unit 252, an ID selection unit 253, and a set information DB 254.

The device driver 21 is an interface for directly transmitting / receiving information to / from the M2M device 51 according to a protocol such as ZigBee, and is used when the service software unit 26 communicates with the M2M device 51. The device driver 21 notifies the device management unit 22 and the ID generation / management unit 27 of the device management information acquired from the M2M device. In addition, the device driver 21 notifies the management message transmitted from the device management unit 22 to the M2M device. Furthermore, the device driver 21 implements communication between the service software unit 26 and the M2M device. The device driver 21 is provided corresponding to the type of M2M device. That is, the software automatic deployment apparatus 2A includes a plurality of device drivers 21.

The device management unit 22 manages the M2M device 51 connected via the device driver 21. The device management unit 22 corresponds to the communication stack and protocol of the M2M device 51, such as a management function such as UPnP protocol, ZigBee protocol, Z-Wave protocol, or a remote management function such as TR-069 protocol or OMA-DM protocol. The M2M device 51 is managed by the management function. The device management unit 22 may have all of these various management functions, or may have only some management functions. The device management unit 22 uses device management information acquired from the M2M device 51 using the management function (address information, manufacturer code, device name, device identifier such as a MAC address, production number, etc., information indicating the device status, etc.) Various information) is notified to the ID generation / management unit 27. The software automatic deployment apparatus 2A shown in FIG. 9 is configured to be able to notify the ID generation / management 27 of the device management information of the M2M device 51 from the device driver 21 and the device management unit 22, respectively. The device management information of the M2M device 51 may be notified to the ID generation / management unit 27 from either the device driver 21 or the device management unit 22, and the ID generation / management unit 27 from the device driver 21 and the device management unit 22. May be notified respectively.

The device management unit 22 notifies the ID generation / management unit 27 of the device management information, acquires the identification information of the M2M device 51 from the ID generation / management unit 27, and the software distribution processing unit 23 acquires the acquired device management information. The software distribution management unit 231 provided is notified.

Based on the device management information acquired from the M2M device 51, the software distribution processing unit 23 is necessary for a service using the M2M device 51, and software for providing the service, management software, or service software such as driver software And requests the software distribution server 52 to distribute the service software via the external connection interface 24. Further, the software distribution processing unit 23 receives information indicating completion of distribution of the service software notified from the software distribution server 52. Further, the software distribution processing unit 23 notifies the ID notification / setting management unit 251 of the distributed service software and the identification information of the M2M device necessary for the M2M service using the service software.

The software distribution management unit 231 notifies the software selection unit 232 of the device management information acquired from the device management unit 22, and information on service software requested to be distributed to the software distribution server 52 determined by the software selection unit 232. get. The software distribution management unit 231 requests the software distribution server 52 to distribute service software via the external connection interface 24 based on the service software information. Further, it notifies the ID notification / setting management unit 251 of the service software information and the identification information of the M2M device necessary for the service using the service software. When the software distribution management unit 231 receives information indicating the completion of distribution of the service software from the software distribution server 52, the software distribution management unit 231 notifies the ID notification / setting management unit 251 of the completion of distribution of the service software. The software distribution management unit 231 notifies the software selection unit 232 of the device management information acquired from the device management unit 22, and if the service software selected by the software selection unit 232 has already been downloaded, ID notification / setting management Registration completion notification from the ID notification / setting management unit 251 to the set information DB 254 at any timing after notifying the unit 251 of the service software information and the identification information of the M2M device necessary for the service using the service software Is received, the ID notification / setting management unit 251 is notified of the completion of distribution of the service software.

The software selection unit 232 determines service software necessary for providing a service using the M2M device 51 based on the device management information acquired from the software distribution management unit 231. The service software is selected using set information including device management information and service software information held in the distribution DB 233, using arbitrary information included in the device management information as a key. The software selection unit 232 notifies the software distribution management unit 231 of information on the selected service software.

The distribution DB 233 stores set information including device management information and service software information for providing the M2M service.

The external connection interface 24 is a communication interface between the software automatic deployment device 2A and the external device. The external connection interface 24 of the present embodiment serves as a communication interface with the software distribution server 52 or M2M service providing servers (not shown).

The ID notification / setting processing unit 25 acquires the distributed service software information received from the software distribution management unit 231 and the identification information of the M2M device necessary for the service using the service software, and sets the combination information. Generate. When the ID notification / setting processing unit 25 receives the information indicating the completion of the distribution of the service software from the software distribution management unit 231, the ID notification / setting processing unit 25 selects the address information of the M2M device 51 necessary for the service using the service software, Notifying or setting the identification information of the M2M device to the service software unit 26 that executes processing according to the service software.

The ID notification / setting management unit 251 notifies the database creation unit 252 of the service software information acquired from the software distribution management unit 231 and the M2M device identification information necessary for the service using the service software. When the ID notification / setting management unit 251 receives information indicating the completion of the distribution of the service software from the software distribution management unit 231, the ID notification / setting management unit 251 notifies the ID selection unit 253 of the information of the service software that has been distributed. Acquire identification information of the corresponding M2M device. The ID notification / setting management unit 251 notifies or sets the acquired M2M device identification information to the service software unit 26.

The database creation unit 252 generates, for example, set information as illustrated in FIG. 10 from the service software information and the M2M device identification information received from the ID notification / setting management unit 251 and registers them in the set information DB 254. As shown in FIG. 10, the set information includes identification information of an M2M device that uses or is used in service software, and distribution completion information that indicates whether the service software has already been downloaded. Configured and registered for each service software.

Since the service software can normally be used in a plurality of M2M devices, the database creation unit 252 receives information on the service software already registered in the set information DB 254 from the ID notification / setting management unit 251 and the service software. When the identification information of the M2M device corresponding to the software is acquired, the identification information of the M2M device is added to the corresponding service software set information registered in the set information DB 254.

Upon receiving the information indicating the completion of distribution from the ID notification / setting management unit 251, the ID selection unit 253 acquires the identification information of the M2M device necessary for the service using the service software whose distribution is completed from the set information DB 254, Notification / setting management unit 251 is notified.

The set information DB 254 stores set information 6B including service software information 61, M2M device identification information 64, and distribution completion information 63 as shown in FIG.

The service software information 61 uses information for identifying service software such as a program name and a program identification number. The identification information 64 is identification information of the M2M device. As described above, a plurality of M2M device identification information 64 can be provided corresponding to the service software information 61. The distribution completion information 63 is information indicating whether or not the corresponding program (service software) has already been distributed to the software automatic deployment apparatus 2A.

The service software unit 26 implements an M2M service using the M2M device 51 by executing processing according to the distributed program (service software). The service software unit 26 exists for each M2M service, each combination of M2M services, each M2M device, or each combination of M2M devices. That is, the software automatic deployment apparatus 2A may include a plurality of service software units 26.

The distribution DB 233 shown in FIG. 9 may be provided outside the software distribution processing unit 23, and the set information DB 254 shown in FIG. 9 may be provided outside the ID notification / setting processing unit 25. Further, the distribution DB 233 and the set information DB 254 may be provided outside the software automatic deployment apparatus 2A. Hereinafter, unless otherwise specified, the database such as the distribution DB 233 and the set information DB 254 can be provided outside the software distribution processing unit 23 and ID notification / setting processing unit 25 or outside the software automatic deployment apparatus 2A. And

The service software unit 26 requests the ID generation / management unit 27 to refer to the address information of the M2M device 51 based on the notified or set identification information. The service software unit 26 acquires the address information of the M2M device by referring to the address information of the M2M device.

The ID generation / management unit 27 generates identification information of the M2M device based on the device management information including the address information of the M2M device acquired from one or both of the device driver 21 and the device management unit 22, and addresses information And set information consisting of the identification information. Also, the ID generation / management unit 27 notifies the device management unit 22 of the generated identification information of the M2M device. Further, when the service software unit 26 requests reference (inquiry) of identification information using the identification information as a key, the ID generation / management unit 27 returns identification information corresponding to the requested address information.

FIG. 11 is a block diagram illustrating another configuration example of the software automatic deployment system according to the second embodiment. The solid arrows shown in FIG. 11 indicate the transmission / reception direction of information (including commands), and the broken arrows shown in FIG. 11 indicate the distribution direction of the service software.

The software automatic deployment system shown in FIG. 11 has a configuration having a software automatic deployment apparatus 2B instead of the software automatic deployment apparatus 2A shown in FIG. The software automatic deployment device 2B has the same configuration as the software automatic deployment device 2A shown in FIG.

In the software automatic deployment apparatus 2B, the address notification / setting management unit 251 notifies or sets the address information of the M2M device or both the address information and the identification information to the service software unit 26 via the ID generation / management unit 27. The The software automatic deployment apparatus 2B can be realized by a known information processing apparatus.

The ID generation / management unit 27 generates identification information of the M2M device based on the device management information including the address information of the M2M device acquired from one or both of the device driver 21 and the device management unit 22, and addresses information And set information consisting of the identification information. Also, the ID generation / management unit 27 notifies the device management unit 22 of the generated identification information of the M2M device. Further, the ID generation / management unit 27 extracts address information corresponding to the identification information acquired from the ID notification / setting management unit 251 based on the set information, and sends either the address information or the identification information to the service software unit 26. On the other hand, address information and identification information are notified or set.

The functions of the device driver 21, device management unit 22, software distribution processing unit 23, external connection interface 24, ID notification / setting processing unit 25, and service software unit 26 provided in the software automatic deployment apparatus 2B shown in FIG. 11 are shown in FIG. This is the same as the software automatic deployment apparatus 2A shown.

Next, operations of the software automatic deployment apparatuses 2A and 2B according to the second embodiment will be described with reference to FIG. Hereinafter, the software automatic deployment apparatuses 2A and 2B are collectively referred to as “software automatic deployment apparatus 2”.

FIG. 12 is a flowchart illustrating an example of processing of the software automatic deployment apparatus according to the second embodiment.

As shown in FIG. 12, the software automatic deployment apparatus 2 monitors whether or not the M2M device 51 is connected (step S20). When the M2M device 51 is not connected, the software automatic deployment apparatus 2 repeats the process of step S20.

When the M2M device 51 is connected, the software automatic deployment apparatus 2 acquires device management information from the connected M2M device 51, and based on the device management information, service software that requests distribution to the software distribution server ( Service software) is determined (step S21).

Next, the software automatic deployment apparatus 2 determines whether or not the service software determined in step S21 has been downloaded (step S22).

When the service software determined in step S21 has already been downloaded, the software automatic deployment apparatus 2 includes a set of the service software information and identification information of the M2M device 51 necessary for the M2M service using the service software. The identification information of the M2M device 51 extracted from the M2M device management information acquired in step S20 is added to the information to update the set information (step S26). Thereafter, the process proceeds to step S27.

If the service software determined in step S21 has not been downloaded, the software automatic deployment apparatus 2 requests the software distribution server 52 to distribute the service software (step S23). Also, pair information composed of the service software information determined in step S21 and the M2M device identification information necessary for the M2M service using the service software is generated and stored (step S24).

Next, the software automatic deployment apparatus 2 determines whether or not the distribution of the service software requested in Step S23 is completed (Step S25), and when the distribution is completed, the process proceeds to Step S27. When the distribution is not completed, the software automatic deployment apparatus 2 repeats the process of step S25.

In step S27, the software automatic deployment apparatus 2 receives the M2M device identification information necessary for the M2M service using the service software determined in step S21 from the pair information created in step S24 or the pair information updated in step S26. get.

Then, the service software in which the identification information of the M2M device 51 acquired in step S27, the address information of the M2M device 51 converted from the identification information of the M2M device 51, or both the address information and the identification information is determined in step S21. The service software unit 26 that executes the process is notified or set according to (step S28).

In the process shown in FIG. 11, the order of the processes in steps S23 and S24 may be reversed.

Next, a modification of the software automatic deployment system according to the second embodiment will be described with reference to FIG.

The software automatic deployment system shown in FIG. 13 is configured to have the functions of the device management unit 22, the software distribution processing unit 23, and the ID notification / setting processing unit 25 of the software automatic deployment apparatuses 2A and 2B as external devices.

The software automatic deployment apparatuses 2A ′ and 2B ′ are configured by removing the functions of the device management unit 22, the software distribution processing unit 23, and the ID notification / setting processing unit 25 from the software automatic deployment apparatuses 2A and 2B, and the M2M device 51 Address information, identification information, or address information and identification information is notified or set to the service software section 26 that executes processing according to the distributed program (service software).

The software distribution processing server 54 is a server that realizes the function of the software distribution processing unit 23. The software distribution processing server 54 requests the software distribution server 52 to distribute service software necessary for the software automatic deployment apparatuses 2A ′ and 2B ′. Also, the software distribution processing server 54 provides ID notification / setting processing apparatus 4B with information on service software distributed to the software automatic deployment apparatuses 2A ′ and 2B ′ and identification information of M2M devices necessary for the M2M service using the service software. When the service software distribution to the software automatic deployment apparatuses 2A ′ and 2B ′ is completed, information indicating the distribution completion is transmitted to the ID notification / setting processing apparatus 4B.

The device remote management server 53 is a server that realizes the function of the device management unit 22. The device remote management server 53 manages the M2M device 51 via the software automatic deployment apparatuses 2A ′ and 2B ′, and notifies the software distribution processing server 54 of device management information.

The ID notification / setting processing device 4B is a device that realizes the function of the ID notification / setting processing unit 25, and includes an ID notification / setting management unit 41, a database creation unit 42, an ID selection unit 43, a set information DB 44, and an external connection. An interface 45 is provided.

The ID notification / setting management unit 41 has the same function as the ID notification / setting management unit 251, and the database creation unit 42 has the same function as the database creation unit 252. The ID selection unit 43 has the same function as the ID selection unit 253, and the set information DB 44 has the same function as the set information DB 254. The external connection interface 45 is a communication interface that realizes communication with an external device.

The software automatic deployment system shown in FIG. 13 does not have to include all the functions of the device management unit 22, the software distribution processing unit 23, and the ID notification / setting processing unit 25 as external devices, and some of these functions are included. The structure provided may be sufficient. In that case, the software automatic deployment apparatuses 2A 'and 2B' need only have a function that is not realized by an external apparatus.

Next, the operation of the ID notification / setting processing device 4B shown in FIG. 13 will be described with reference to FIG.

FIG. 14 is a flowchart showing an example of processing of the ID notification / setting processing apparatus shown in FIG.

As shown in FIG. 14, the ID notification / setting processing device 4B generates, from the software distribution processing server 54, set information including service software and identification information of the M2M device 51 necessary for the M2M service using the service software. Is monitored (step S50). When the creation of the group information is requested, the ID notification / setting processing device 4B determines whether or not the group information requested to be created already exists (step S51).

If the group information requested to be created does not exist, the ID notification / setting processing device 4B determines from the service software information requested to be created and the identification information of the M2M device 51 required for the M2M service using the service software. The set information is generated and stored (step S52).

If the group information requested to be created already exists, the ID notification / setting processing device 4B adds the identification information of the M2M device 51 to the group information and updates the group information (step S53).

If it is determined in step S50 that creation of group information has not been requested, the ID notification / setting processing device 4B determines whether or not the distribution of service software has been notified from the software distribution processing server (step S54). If the service software distribution completion is not notified, the ID notification / setting processing device 4B repeats the processing from step S50.

When the service software distribution completion is notified, the ID notification / setting processing device 4B uses the service software notified of the distribution completion based on the group information created in step S52 or the group information updated in step S53. The identification information of the M2M device necessary for the existing M2M service is acquired (step S55).

Then, the ID notification / setting processing device 4B notifies the identification information of the M2M device acquired in step S55 to the software automatic deployment devices 2A ′ and 2B ′, and the identification information of the M2M device 51 and the M2M converted from the identification information The address information of the device 51 or both the address information and the identification information is notified or set to the service software unit 26 that executes processing according to the service software distributed to the software automatic deployment apparatuses 2A ′ and 2B ′ (step S56).

According to this embodiment, the software automatic deployment apparatuses 2A, 2B or 2A ′, 2B ′ use the identification information generated from the address information of the M2M device 51 acquired using the management function of the M2M device, and the M2M device 51. The service software unit 26 that stores the set information including the information of the service software that realizes the received service and notifies the identification information of the M2M device 51 based on the stored set information to the service software unit 26 that executes processing according to the distributed service software. Alternatively, by setting, the M2M service providing servers that provide the M2M service can identify the M2M device 51 used in the M2M service and can communicate with the M2M device 51. Accordingly, the M2M service providing servers can provide the M2M service using the M2M device 51. Further, since the service software does not need to have a function for acquiring the identification information of the M2M device and a function for notifying the identification information to the M2M service providing servers, the development cost of the service software can be reduced.
(Third embodiment)
Next, a third embodiment of the present invention will be described with reference to the drawings.

When the M2M device is connected, the software automatic deployment apparatus according to the third embodiment acquires address information and identification information from the M2M device using a management function of the M2M device prepared in advance, and the acquired M2M device A set information including address information and identification information, and service software information that is a program for realizing the M2M service used in the M2M device or used in the M2M device is generated and stored. When the download of the service software is completed, or when the service software has already been downloaded, the address information and identification information of the M2M device are notified or set to the service software based on the stored set information. .

FIG. 15 is a block diagram illustrating a configuration example of the software automatic deployment system according to the third embodiment. The solid arrows shown in FIG. 15 indicate the transmission / reception direction of information (including commands), and the broken arrows shown in FIG. 15 indicate the distribution direction of the service software.

As shown in FIG. 15, the software automatic deployment system of this embodiment includes an M2M device 51, a software distribution server 52, and a software automatic deployment apparatus 3.

The M2M device 51 is a device that realizes an M2M service, such as a sensor device, an actuator device, a black appliance, a white appliance, or the like.

The software distribution server 52 is a server that distributes service software in accordance with a request from the software automatic deployment apparatus 1A. When the distribution of the service software is completed, the software distribution server 52 transmits information indicating the distribution completion to the software automatic deployment apparatus 3 that requested the distribution.

The software automatic deployment apparatus 3 notifies or sets the address information and identification information of the M2M device 51 to the service software distributed from the software distribution server 52. The software distribution server 52 and the software automatic deployment apparatus 3 shown in FIG. 15 can be realized by a known information processing apparatus.

The software automatic deployment apparatus 3 includes a device driver 31 that is an interface for communicating with the connected M2M device 51, a device management unit 32 that manages the M2M device 51, and a software distribution processing unit 33 that performs service software distribution processing. A service using an M2M device is realized by executing processing according to the external connection interface 34 realized by a TCP / IP stack or the like, which is a communication interface for communicating with an external device, and the distributed service software Service software unit 36, an address and ID notification / setting processing unit 35 for notifying or setting the address information and identification information of the M2M device to the service software unit 36, and ID generation for generating and managing the identification information of the M2M device - and a management unit 37.

The software distribution processing unit 33 includes a software distribution management unit 331, a software selection unit 332, and a distribution DB 333.

The address and ID notification / setting processing unit 35 includes an address and ID notification / setting management unit 351, a database creation unit 352, an address and ID selection unit 353, and a set information DB 354.

Based on the device management information acquired from the M2M device 51, the software distribution processing unit 33 is necessary for a service using the M2M device 51, such as software for providing the service, management software, or service software such as driver software. And requests the software distribution server 52 to distribute the service software via the external connection interface 14. Further, the software distribution processing unit 33 receives information indicating completion of distribution of the service software notified from the software distribution server 52. Further, the software distribution processing unit 33 notifies the address and ID notification / setting management unit 351 of the distributed service software and the address information and identification information of the M2M device necessary for the service using the service software.

The software distribution management unit 331 notifies the software selection unit 332 of the device management information acquired from the device management unit 32, and information on the service software requested to be distributed to the software distribution server 52 determined by the software selection unit 332. get. The software distribution management unit 331 requests the software distribution server 52 to distribute service software via the external connection interface 34 based on the service software information. Also, the address and ID notification / setting management unit 351 is notified of the service software information and the address information and identification information of the M2M device necessary for the service using the service software. When the software distribution management unit 331 receives information indicating the completion of distribution of the service software from the software distribution server 52, the software distribution management unit 331 notifies the address and ID notification / setting management unit 351 of the completion of distribution of the service software. The software distribution management unit 331 notifies the device selection information acquired from the device management unit 32 to the software selection unit 332. If the service software selected by the software selection unit 332 has already been downloaded, the address and ID notification / From the address and ID notification / setting management unit 351 at an arbitrary timing after notifying the setting management unit 351 of the service software information and the address information and identification information of the M2M device necessary for the service using the service software When the registration completion notification for the set information DB 354 is received, the address and ID notification / setting management unit 351 is notified of the completion of distribution of the service software.

The software selection unit 332 determines service software necessary for providing a service using the M2M device 51 based on the device management information acquired from the software distribution management unit 331. The service software is selected using set information composed of device management information and service software information held in the distribution DB 333 using arbitrary information included in the device management information as a key. The software selection unit 332 notifies the software distribution management unit 331 of information on the selected service software.

The distribution DB 333 stores set information including device management information and service software information for providing the M2M service.

The external connection interface 34 is a communication interface between the software automatic deployment device 3 and the external device. The external connection interface 34 of the present embodiment serves as a communication interface with the software distribution server 52 or M2M service providing servers (not shown).

The address and ID notification / setting processing unit 35 acquires the information of the distributed service software received from the software distribution management unit 331 and the address information and identification information of the M2M device necessary for the service using the service software, The group information is generated. When the address and ID notification / setting processing unit 35 receives information indicating the completion of distribution of the service software from the software distribution management unit 331, the address information and identification information of the M2M device 51 necessary for the service using the service software And the address information and identification information of the M2M device are notified or set to the service software unit 36 that executes processing according to the service software.

The address and ID notification / setting management unit 351 notifies the database creation unit 352 of the service software information acquired from the software distribution management unit 331 and the address information and identification information of the M2M device necessary for the service using the service software. . Further, upon receiving information indicating the completion of the distribution of the service software from the software distribution management unit 331, the address and ID notification / setting management unit 351 notifies the address and ID selection unit 353 of the information on the service software that has been distributed, The address information and identification information of the M2M device to be notified or set to the service software are acquired. The address and ID notification / setting management unit 351 notifies or sets the acquired address information and identification information of the M2M device to the service software unit 36 that executes processing according to the distributed service software.

The database creation unit 352 generates, for example, set information as illustrated in FIG. 16 from the service software information received from the address and ID notification / setting management unit 351 and the address information and identification information of the M2M device, and sends the set information to the set information DB 354. sign up. As shown in FIG. 16, in the group information, the service software is used or the M2M device address information and identification information used in the service software, and the distribution completion indicating whether or not the service software has already been downloaded. And is registered corresponding to each service software.

Since the service software can normally be used in a plurality of M2M devices, the database creation unit 352 receives information on the service software already registered in the group information DB 354 from the address and ID notification / setting management unit 351, and When the address information and identification information of the M2M device corresponding to the service software are acquired, the address information and identification information of the M2M device are added to the corresponding service software set information registered in the set information DB 354.

When the address and ID selection unit 353 is notified of the information indicating the completion of distribution of the service software from the address and ID notification / setting management unit 351, the address information and identification information of the M2M device necessary for the service using the service software Is received from the set information DB 354 and notified to the address and ID notification / setting management unit 351.

The set information DB 354 stores set information 6C including service software information 61, M2M device address information and identification information 65, and distribution completion information 63 as shown in FIG.

The service software information 61 uses information for identifying service software such as a program name and a program identification number. The address information and identification information 65 are address information and identification information of the M2M device. As described above, a plurality of M2M device address information and identification information can be provided corresponding to the service software information 61. The distribution completion information 63 is information indicating whether the service software has already been distributed to the software automatic deployment apparatus 3.

The service software unit 36 implements an M2M service using the M2M device 51 by executing processing according to the distributed program (service software). The service software unit 36 exists for each M2M service, each combination of M2M services, each M2M device, or each combination of M2M devices. That is, the software automatic deployment device 3 may include a plurality of service software units 36.

16 may be provided outside the software distribution processing unit 33, and the set information DB 354 shown in FIG. 16 may be provided outside the address and ID notification / setting processing unit 35. Further, the distribution DB 333 and the set information DB 354 may be provided outside the software automatic deployment apparatus 3. Unless otherwise specified, databases such as the distribution DB 333 and the set information DB 354 can be provided outside the software distribution processing unit 33, the address and ID notification / setting processing unit 35, or outside the software automatic deployment apparatus 3. It shall be.

The functions of the device driver 31, the device management unit 32, the external connection interface 34, and the ID generation / management unit 37 included in the software automatic deployment apparatus 3 illustrated in FIG. 15 are the same as those of the software automatic deployment apparatus 2A illustrated in FIG.

Next, the operation of the software automatic deployment apparatus 3 according to the third embodiment will be described with reference to FIG.

FIG. 17 is a flowchart illustrating an example of processing of the software automatic deployment apparatus according to the third embodiment.

As shown in FIG. 17, the software automatic deployment apparatus 3 monitors whether or not the M2M device 51 is connected (step S30). When the M2M device 51 is not connected, the software automatic deployment apparatus 3 repeats the process of step S30.

When the M2M device 51 is connected, the software automatic deployment apparatus 3 acquires device management information from the connected M2M device 51, and obtains service software that requests distribution to the software distribution server based on the device management information. Determine (step S31).

Next, the software automatic deployment apparatus 3 determines whether or not the service software determined in step S31 has been downloaded (step S32).

When the service software determined in step S31 has already been downloaded, the software automatic deployment apparatus 3 includes the service software information, the address information and identification information of the M2M device 51 required for the M2M service using the service software, The set information is updated by adding the address information and identification information of the M2M device 51 extracted from the M2M device management information acquired in step S30 to the set information consisting of (step S36). Thereafter, the process proceeds to step S37.

If the service software determined in step S31 has not been downloaded, the software automatic deployment apparatus 3 requests the software distribution server 52 to distribute the service software (step S33). In addition, it generates and stores set information composed of the service software information determined in step S31 and the address information and identification information of the M2M device necessary for the M2M service using the service software (step S34).

Next, the software automatic deployment device 3 determines whether or not the distribution of the service software requested in step S33 is completed (step S35), and when the distribution is completed, the process proceeds to step S37. If the distribution has not been completed, the software automatic deployment apparatus 3 repeats the process of step S35.

In step S37, the software automatic deployment apparatus 3 uses the pair information created in step S34 or the pair information updated in step S36, and the M2M device address information necessary for the M2M service using the service software determined in step S31. And identification information is acquired.

Then, the address information and identification information of the M2M device 51 acquired in step S37 are notified or set to the service software unit 36 that executes processing according to the service software determined in step S31 (step S38).

In the process shown in FIG. 17, the order of the processes in steps S33 and S34 may be reversed.

Next, a modification of the software automatic deployment system according to the third embodiment will be described with reference to FIG.

The software automatic deployment system shown in FIG. 18 is configured to have the functions of the device management unit 32, software distribution processing unit 33, and address and ID notification / setting processing unit 35 of the software automatic deployment apparatus 3 as external devices.

The software automatic deployment device 3 ′ is configured by removing the functions of the device management unit 32, the software distribution processing unit 33, and the address and ID notification / setting processing unit 35 from the software automatic deployment device 3, and the address of the M2M device 51. Information or identification information is notified or set to the distributed program (service software).

The software distribution processing server 54 is a server that realizes the function of the software distribution processing unit 33. The software distribution processing server 54 requests the software distribution server 52 to distribute service software necessary for the software automatic deployment apparatus 3 ′. Further, the software distribution processing server 54 notifies the address and ID of the service software information distributed to the software automatic deployment apparatus 3 ′ and the address information and identification information of the M2M device 51 necessary for the M2M service using the service software. In addition to notifying the processing device 4C, when the distribution of the service software to the software automatic deployment device 3 ′ is completed, information indicating the completion of the transmission is transmitted to the address and ID notification / setting processing device 4C.

The device remote management server 53 is a server that realizes the function of the device management unit 32. The device remote management server 53 manages the M2M device 51 via the software automatic deployment apparatus 3 ′ and notifies the software distribution processing server 54 of device management information.

The address and ID notification / setting processing device 4C is a device that realizes the function of the address and ID notification / setting processing unit 35, and includes an address and ID notification / setting management unit 41, a database creation unit 42, an address and ID selection unit. 43, a set information DB 44 and an external connection interface 45 are provided.

The address and ID notification / setting management unit 41 has the same function as the address and ID notification / setting management unit 351, and the database creation unit 42 has the same function as the database creation unit 352. The address and ID selection unit 43 has the same function as the address and ID selection unit 353, and the set information DB 44 has the same function as the set information DB 354. The external connection interface 45 is a communication interface that realizes communication with an external device.

The software automatic deployment system shown in FIG. 18 does not need to include all the functions of the device management unit 32, the software distribution processing unit 33, and the address and ID notification / setting processing unit 35 as an external device. It may be configured to have a function. In that case, the software automatic deployment device 3 ′ only needs to have a function that is not realized by an external device.

Next, the operation of the address and ID notification / setting processing device 4C shown in FIG. 18 will be described with reference to FIG.

FIG. 19 is a flowchart showing an example of processing of the address and ID notification / setting processing apparatus shown in FIG.

As shown in FIG. 19, the address and ID notification / setting processing device 4C receives from the software distribution processing server 54 from the service software and the address information and identification information of the M2M device 51 necessary for the M2M service using the service software. It is monitored whether or not the creation of the group information is requested (step S60). When the creation of the set information is requested, the address and ID notification / setting processing device 4C determines whether or not the set information requested to be created already exists (step S61).

If the group information requested to be created does not exist, the address and ID notification / setting processing device 4C receives the requested service software information and the address information and identification of the M2M device 51 required for the M2M service using the service software. The set information composed of the information is generated and stored (step S62).

If the group information requested to be created already exists, the address and ID notification / setting processing device 4C adds the address information and identification information of the M2M device 51 to the group information and updates the group information (step S63).

If it is determined in step S60 that creation of set information has not been requested, the address and ID notification / setting processing device 4C determines whether or not the distribution of service software has been notified from the software distribution processing server 54 (step S64). . If the service software distribution completion is not notified, the address and ID notification / setting processing device 4C repeats the processing from step S60.

When the service software distribution completion is notified, the address and ID notification / setting processing device 4C receives the service software notified of the distribution completion based on the group information created in step S62 or the group information updated in step S63. The address information and identification information of the M2M device necessary for the M2M service using is acquired (step S65).

Then, the address information and identification information of the M2M device acquired in step S65 are notified to the software automatic deployment apparatus 3 ′, and the address information and identification information of the M2M device 51 are transmitted according to the service software distributed to the software automatic deployment apparatus 3 ′. The service software unit 36 that executes the process is notified or set (step S66).

According to the present embodiment, the service software for realizing the address information and identification information of the M2M device 51 and the service using the M2M device 51 acquired by the software automatic deployment apparatus 3 or 3 ′ using the management function of the M2M device M2M service by storing or setting the address information and identification information of the M2M device 51 to the service software unit 36 that executes processing according to the distributed service software based on the stored set information The M2M service providing servers that provide the M2M service 51 can identify the M2M device 51 used in the M2M service and can communicate with the M2M device 51. Accordingly, the M2M service providing servers can provide the M2M service using the M2M device 51. In addition, since the service software does not need to have a function for acquiring the address information and identification information of the M2M device and a function for notifying the M2M service providing servers of the address information and identification information, the service software is developed. Cost can be reduced.

Further, by notifying or setting the address information and identification information of the M2M device to the service software, it is not necessary to provide the service software with a function for retrieving the identification information from the address information or a function for retrieving the address information from the identification information. . Therefore, the development cost of service software can be reduced as compared with the first embodiment and the second embodiment.

Furthermore, in the present embodiment, since the notification or setting of the address information and identification information of the M2M device for the service software does not need to go through the ID generation / management unit 37, the function of the ID generation / management unit 37 can be reduced.

As mentioned above, although this invention was demonstrated with reference to embodiment, this invention is not limited to the said embodiment. Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

This application claims priority based on Japanese Patent Application No. 2011-115896 filed on May 24, 2011, the entire disclosure of which is incorporated herein.

(Appendix 1)
A software distribution processing unit that downloads service software for providing a service using a device connectable to a network;
An address notification setting unit for notifying or setting the address information of the device included in the management information of the device acquired using a protocol for managing the device or a function for managing the device to the downloaded service software; ,
A software automatic deployment apparatus.

(Appendix 2)
The software distribution processing unit
The software automatic deployment device according to appendix 1, wherein the service software is downloaded from a server that distributes the service software when the device is connected.

(Appendix 3)
The address notification setting unit
3. The software automatic deployment apparatus according to appendix 1 or 2, which stores service software information to be downloaded selected from the device management information and set information including address information included in the device management information.

(Appendix 4)
The address notification setting unit
4. The automatic software deployment according to any one of appendices 1 to 3, wherein upon receiving a notification of completion of distribution of the service software from the software distribution processing unit, the address information corresponding to the service software is notified or set to the service software. apparatus.

(Appendix 5)
The address notification setting unit
The software automatic deployment device according to supplementary note 3 or 4, wherein address information notified or set to the service software is acquired by referring to the set information of the service software and the address information.

(Appendix 6)
The software distribution processing unit
6. The software automatic deployment apparatus according to any one of appendices 1 to 5, which notifies the address notification setting unit of set information of the service software and the address information.

(Appendix 7)
The software automatic deployment apparatus according to any one of appendices 1 to 6, wherein identification information for identifying the device extracted or generated from the management information of the device is used instead of the address information of the device.

(Appendix 8)
The software automatic deployment apparatus according to any one of appendices 1 to 7, wherein identification information for identifying the device extracted or generated from the management information of the device is used together with the address information of the device.

(Appendix 9)
The address notification setting unit
The selected address information is extracted or generated from the management information of the device and the identification information generation management function for managing the identification information together with the address information of the device is relayed to the identification information from the address information. The software automatic deployment apparatus according to any one of supplementary notes 1 to 6, wherein the service software is notified or set of the selected identification information or both the address information and the selected identification information.

(Appendix 10)
The address notification setting unit
The selected identification information is extracted or generated from the management information of the device, and the identification information generation management function for managing the identification information together with the address information of the device is relayed. The software automatic deployment apparatus according to appendix 7, wherein the service software is notified or set of the selected address information or both of the identification information and the selected address information.

(Supplementary note 11) The software automatic deployment device according to any one of supplementary notes 1 to 10, wherein at least one of the address notification setting unit or the software distribution processing unit provided in the software automatic deployment device is an external device.

(Supplementary note 12) The software automatic deployment apparatus according to any one of supplementary notes 1 to 11,
A software distribution server for distributing the service software;
A software automatic deployment system.

(Supplementary note 13) The software automatic deployment system according to supplementary note 12, wherein at least one of the address notification setting unit or the software distribution processing unit provided in the software automatic deployment device is an external device.

(Supplementary Note 14) A software distribution processing step of downloading service software for providing a service using a device connectable to a network;
An address notification setting step of notifying or setting the address information of the device included in the management information of the device acquired using a protocol for managing the device or a function for managing the device to the downloaded service software; ,
A software automatic deployment method comprising:

(Supplementary Note 15) The software distribution processing step includes:
15. The software automatic deployment method according to appendix 14, wherein the service software is downloaded from a server that distributes the service software when the device is connected.

(Supplementary Note 16) The address notification setting step includes:
16. The software automatic deployment method according to appendix 14 or 15, wherein information on service software to be downloaded selected from the management information of the device and set information including address information included in the management information of the device is stored.

(Supplementary Note 17) The address notification setting step includes:
The automatic software deployment according to any one of supplementary notes 14 to 16, wherein when receiving a notification of completion of distribution of the service software from the software distribution processing step, the address information corresponding to the service software is notified or set to the service software. Method.

(Supplementary Note 18) The address notification setting step includes:
18. The software automatic deployment method according to supplementary note 16 or 17, wherein address information notified or set to the service software is acquired by referring to the set information of the service software and the address information.

(Supplementary note 19) The software distribution processing step includes:
19. The software automatic deployment method according to any one of supplementary notes 14 to 18, wherein the set information of the service software and the address information is notified to the address notification setting step.

(Supplementary note 20) The software automatic deployment method according to any one of supplementary notes 14 to 19, wherein identification information for identifying the device extracted or generated from the management information of the device is used instead of the address information of the device.

(Supplementary note 21) The software automatic deployment method according to any one of supplementary notes 14 to 20, wherein the identification information for identifying the device extracted or generated from the management information of the device is used together with the address information of the device.

(Supplementary Note 22) The address notification setting step includes:
The selected address information is identified from the address information by extracting or generating the identification information from the management information of the device and relaying an identification information generating tube processing step for managing the identification information together with the address information of the device. 20. The software automatic deployment method according to any one of appendices 14 to 19, wherein information is selected, and the selected identification information, or both the address information and the selected identification information are notified or set to the service software.

(Supplementary Note 23) The address notification setting step includes:
The selected identification information is extracted or generated from the management information of the device, and the identification information generating tube processing step for managing the identification information together with the address information of the device is relayed to the address from the identification information. The software automatic deployment method according to appendix 22, wherein information is selected, and the selected address information or both the identification information and the selected address information are notified or set to the service software.

Claims (10)

A software distribution processing unit that downloads service software for providing a service using a device connectable to a network;
An address notification setting unit for notifying or setting the address information of the device included in the management information of the device acquired using a protocol for managing the device or a function for managing the device to the downloaded service software; ,
A software automatic deployment apparatus. The software distribution processing unit
The software automatic deployment apparatus according to claim 1, wherein the service software is downloaded from a server that distributes the service software when the device is connected. The address notification setting unit
3. The software automatic deployment apparatus according to claim 1 or 2, wherein information on the service software to be downloaded selected from the management information of the device and set information including address information included in the management information of the device is stored. The address notification setting unit
4. The software automatic according to claim 1, wherein upon receiving a notification of completion of distribution of the service software from the software distribution processing unit, address information corresponding to the service software is notified or set to the service software. 5. Deployment device. The address notification setting unit
5. The software automatic deployment apparatus according to claim 3, wherein address information notified or set to the service software is acquired by referring to the set information of the service software and the address information. The software distribution processing unit
The software automatic deployment apparatus according to any one of claims 1 to 5, wherein a set information of the service software and the address information is notified to the address notification setting unit. 7. The software automatic deployment apparatus according to claim 1, wherein identification information for identifying the device extracted or generated from the management information of the device is used instead of the address information of the device. The software automatic deployment apparatus according to any one of claims 1 to 7, wherein identification information for identifying the device extracted or generated from the management information of the device is used together with the address information of the device. The address notification setting unit
The selected address information is extracted or generated from the management information of the device and the identification information generation management function for managing the identification information together with the address information of the device is relayed to the identification information from the address information. 7. The software automatic deployment apparatus according to claim 1, wherein the service software is notified or set of the selected identification information, or both the address information and the selected identification information. The address notification setting unit
The selected identification information is extracted or generated from the management information of the device, and the identification information generation management function for managing the identification information together with the address information of the device is relayed. 8. The software automatic deployment apparatus according to claim 7, wherein the service software is notified or set of the selected address information or both of the identification information and the selected address information.

Images