WO2006126355A1 - Gateway device and control device - Google Patents

Abstract

Provided is a gateway device for opening information on devices or services to a device to be connected with the networks of protocols of different kinds. The gateway device (11) includes a device description creation processing unit (24), a device description template holding unit (25), a service description creation processing unit (26) and a service description template holding unit (27). The service description creation processing unit (26) classifies the services and attributes corresponding to the individual devices, into property types or corresponding control models, and creates the service information description or the public information automatically, according to the rules regulated for every property types.

Description

 Specification

 Gateway device and control device

 Technical field

 TECHNICAL FIELD [0001] The present invention relates to a gateway device or the like in which a control device and a terminal device that is a non-control device are connected to networks of different protocols, respectively, and are connected to networks of both protocols. This relates to a gateway device having a method for disclosing the connection status to the network to which the device is connected and the services and attributes that can be supported by each terminal device to the control device connected to the network of a different protocol.

 Background art

 [0002] Traditionally, applications, services, and device capabilities Describe your capabilities, publish them to other applications, services, and devices, and integrate different networks into a unified framework It describes the mechanism by which various network entities located in different networks discover and interact with each other.

 [0003] Then, for example, a method is disclosed in which a plurality of networks having different communication protocols are integrated into a single unified framework to enable a user application to discover and use various network devices. (For example, see Patent Document 1).

 [0004] More specifically, in recent years, network support for information equipment and AV equipment has progressed. For example, UPnP (Universal Plug and Play) power has attracted attention as its communication protocol, and product applications have already advanced. It is out. In the future, when ECHONET devices that use ECHONET, which is a communication protocol in the home, will be systematically integrated with information devices and AV devices, system coexistence with UP nP devices is also desired.

 Patent Document 1: Japanese Patent Laid-Open No. 2001-290724

 Disclosure of the invention

 Problems to be solved by the invention

[0005] However, conventionally, information on devices connected to its own network and information on attributes and data supported by the devices are disclosed to networks of different protocols. In this case, since the data to be disclosed for each device is defined, there is a problem that if the same device is defined by different protocols, not only the work becomes enormous, but the definition becomes different. There is a problem that it is very difficult to develop a controller that controls devices connected to the protocol network.

 [0006] More specifically, the above-mentioned home ECHONET device and AV device interoperability requires a gateway function that interconnects the ECHONET protocol and the UPnP protocol for AV devices. In the ECHONET standard, a specific gateway function has been standardized! /, So there is also a problem that mutual cooperation between ECHONET equipment and AV equipment in the home cannot be realized.

 [0007] The present invention is for solving the above-mentioned problems, and it is possible to appropriately interconnect between terminal devices connected to a communication network based on a heterogeneous protocol by standardizing and specifying a gateway function. An object of the present invention is to provide a gateway device that can be realized.

 Means for solving the problem

In order to solve the above problems, a gateway device according to the present invention is a gateway device that connects two or more types of networks including at least different types of first protocol and second protocol. A template holding means for holding a template that is described based on a standard used for the second protocol and in which information on a terminal device connected to the network of the first protocol is written; and a network of the first protocol. An acquisition unit that acquires information on the terminal device based on the standard used in the first protocol and the template held by the template holding unit are acquired from a connected terminal device, and the acquisition unit acquires the template. By writing the acquired information about the terminal device, the terminal device information A template description creation processing means for creating a script, and a protocol conversion table for associating a representation format of information corresponding to the terminal device in the first protocol and the second protocol based on the name of the terminal device Between the control device connected to the network of the second protocol and the terminal device connected to the network of the first protocol with reference to the protocol conversion table. Protocol conversion means for converting the protocol when performing The description creation processing means comprises communication means capable of transmitting the updated terminal device information description to the control device connected to the network of the second protocol.

 [0009] Further, the template holding means of the gateway device according to the present invention is described based on a standard used for the second protocol, and device information of the terminal device connected to the network of the first protocol is written therein. Device description template holding unit for holding a device description template, and service description template holding unit for holding a service description template in which service information provided by the terminal device is written according to the standard used for the second protocol The template description creation processing means is configured to obtain the device description template from the device description template holding unit, and automatically write the device information obtained by the obtaining means in accordance with a prescribed rule. Repsion Device description to be created Creation processing unit and service description template holding unit The service description disk is obtained by acquiring the service description template and automatically writing the service information obtained by the obtaining unit according to a prescribed rule. It is composed of a service description creation processing unit that creates a repetition.

 [0010] With these configurations, the control device connected to the second protocol network is described in a template suitable for the standard of the first protocol that also acquired the terminal device power connected to the first protocol network. Based on the information about the terminal device, the template description creation processing means can automatically create a terminal device information distribution suitable for the second protocol standard and make it available to the control device. Therefore, it is possible to provide a gateway device that can realize interconnection between terminal devices connected to a communication network based on a heterogeneous protocol.

[0011] Further, the service description template holding unit of the gateway device according to the present invention is a control model classified into a pattern for controlling the terminal device connected to the network of the first protocol. A service description template defined for each property type is held, and the service description creation processing unit divides the information on the service acquired by the acquisition unit into the property type predetermined according to a predetermined rule. A service description template corresponding to the property type is selected from the service description template holding unit, and the service information description is created according to a rule defined for each service description template. To do.

 With this configuration, the service description creation processing unit classifies the attribute service held by each device into the property type that is the control model of the attribute information and service information of the device and the device, and the second protocol. By creating a service information description based on this standard and making this service information description available to control devices connected to the second protocol network, it is easy to connect to different networks. It is possible to publish information on devices including the network configuration and service information that can be supported by each device to the terminal devices being installed.

 [0013] Further, the gateway device according to the present invention is further connected to the Internet, and the protocol conversion table corresponding to the terminal device connected to the first protocol from a server device, the device description template, And Internet connection means for obtaining the service description template.

 [0014] With this configuration, in the Internet connection means, the protocol conversion table that associates the name of the terminal device via the Internet, the representation format for each protocol of the service supported by the terminal device, and the device information description The device description template for creating a case and the service description template for creating the service information description can be acquired. Even if a new service or a new terminal device is added, the latest template Can be obtained via the network, and it is possible to cope with connections between networks that appropriately use heterogeneous protocols.

[0015] The control device according to the present invention is a control device for controlling a terminal device connected to the network of the second protocol and connected to the network of the first protocol. Confirming the connection status of the terminal device connected to the network of one protocol, detecting that the terminal device to be controlled is connected to the network, and device information description that is the device information of the acquired terminal device Device description detection processing means for holding the device, and a device for analyzing the device information description Requesting and obtaining service information description describing the service information held by the analysis processing means and the terminal device to be controlled from the terminal device connected to the network of the first protocol A description detection processing means; a service analysis processing means for analyzing the service information description; and a notification data on the terminal device power status to be controlled when receiving notification data about the terminal device power status from the device description detection processing means. An event reception processing means for analyzing the content of the received notification data by acquiring the repetition and acquiring the service information description by the service description detection processing means, and the terminal device to be controlled. In order to control, the device description detection processing means Device control processing means for acquiring communication information dispersion, acquiring the service information dispersion from the service description detection processing means, and creating communication data for control, and at least all of the terminal devices to be controlled Data holding means for holding the device information description and the service information description, and the device information description and the service information description power of the terminal device to be controlled. Screen display means for displaying a screen for checking and controlling the state.

 [0016] In addition, the screen display unit of the control device according to the present invention holds a widget set that generates a screen framework for each property type of the service information description, and applies the widget set to the screen. Thus, a screen frame mark is generated, and the screen is generated by writing data included in the service information description into the widget set according to the rules of the widget set.

[0017] With these configurations, when the control device connected to the heterogeneous network receives this published service information description, the control device transmits to the screen display means for each property type that is each control model. A user interface can be easily created by using the corresponding widget set. Further, the method in the control device according to the present invention is not limited to a specific protocol, and can be used for interconnections between all kinds of different protocols. [0018] In order to achieve the above object, the present invention is realized as a network connection method using the characteristic means of the gateway device as a step, or as a program for causing a computer to execute each step. You can also. It goes without saying that such a program can be distributed through a recording medium such as a CD-ROM and a transmission medium such as the Internet.

 The invention's effect

 [0019] According to the method of publishing a service that can be supported by each device, such as the connection status of the device to devices on different protocols in the gateway device of the present invention, the service of each device is classified into a property type that is a control model. As a result, services that can be handled by each device can be easily disclosed to devices using different protocols, and interconnection between terminal devices connected to a communication network based on different protocols can be realized appropriately.

 [0020] Also, a control device that receives service information of a device connected to a heterogeneous network can easily execute an application by holding a user interface component corresponding to a property type as each control model. Can be created.

 Brief Description of Drawings

FIG. 1 is a system configuration diagram when different protocols are linked.

 FIG. 2 is a functional block diagram held by the gateway device.

 FIG. 3 is a functional block diagram held by the controller device.

 FIG. 4 is a functional block diagram held by the controller device.

 FIG. 5 is a device name conversion diagram of the protocol conversion table.

 FIG. 6 is a device common attribute and data conversion diagram of the protocol conversion table.

 FIG. 7 is a device conversion attribute and data conversion diagram of the protocol conversion table.

 [FIG. 8] FIG. 8 is a configuration diagram of an address translation tape glue.

 FIG. 9 is a system configuration diagram when connected to a server outside the house.

 [FIG. 10] FIG. 10 is an image diagram when an ECHONET device is disclosed to UPnP.

 FIG. 11 is a diagram showing an example of ECHONET property types classified by the gateway device according to the first embodiment.

[Figure 12] Figure 12 shows the classification and naming rules by ECHONET property type. Reference diagram showing the relationship between the party type, type classification, object, Action prefix, and datatype. [FIG. 13] FIG. 13 is a diagram of the device description template held in the device description template holding unit of the gateway device of the first embodiment. It is a figure which shows an example of a format.

FIG. 14 is a diagram showing an example of a format description of a service description template held in a service description template holding unit of the gateway device according to the first embodiment.

FIG. 15 is a flowchart showing an operation procedure of the gateway device according to the first embodiment.

 FIG. 16 (a) is a diagram showing an example of a level type screen displayed on the screen display unit of the controller device according to the second embodiment. FIG. 16 (b) is a diagram illustrating an example of a selection type screen displayed on the screen display unit of the controller device according to the second embodiment. FIG. 16 (c) is a diagram illustrating an example of a switching screen displayed on the screen display unit of the controller device according to the second embodiment. FIG. 16 (d) is a diagram illustrating an example of a character notation type screen displayed on the screen display unit of the controller device according to the second embodiment.

FIG. 17 is a flowchart showing an operation procedure in the screen display of the controller device according to the second embodiment. Explanation of symbols

 11 Gateway device

 12 Protocol A

 13 Pro = 3 Le B

 14 Controller device

 15, 16, 17 terminal

 21 Protocol A Communication processor

 22 Protocol B communication processor

 23 Protocol conversion processor

 24 Device description creation processing section

 25 Device description template storage

 26 Service description creation processing part

27 Service description template holding part 28 Protocol conversion table storage

 29 Device Configuration Management Department

 31 Device description detection processor

 32 Device analysis processor

 33 Service description detection processor

 34 Service analysis processing department

 35 Event reception processor

 36 Device control processing section

 37 Data holding part

 41 Screen display

 91 Center server

 101 root device

 102 Service type

 BEST MODE FOR CARRYING OUT THE INVENTION

Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[Embodiment 1]

 FIG. 1 is a system configuration diagram of a home network configured with a plurality of types of protocols in the home network according to Embodiment 1 of the present invention.

 [0025] For the two types of protocols shown in Fig. 1, for example, protocol A12 is UPnP and protocol B13 is ECHONET. As the home network configuration, controller device 14 is connected to protocol A12, and terminal 15, terminal 16, and terminal 17 are connected to protocol B13.

 [0026] The terminal 15, the terminal 16, and the terminal 17 are devices such as an air conditioner and a refrigerator-freezer, for example.

 Further, the gateway device 11 connected to both the protocol A12 and the protocol B13 constitutes a home network system. The controller device 14 connected to the protocol A12 and the terminals 15, 16, and 17 connected to the protocol B13 realize the interconnection between different protocols via the gateway device 11.

The controller device 14 acquires information on devices connected to the protocol B13 from the gateway device 11 and information on services that can be executed by each device. From this information, The roller device 14 transmits communication data for controlling the device connected to the protocol B13 to the gateway device 11, and the gateway device 11 converts the received communication data into communication data corresponding to the protocol B and applies the corresponding protocol. Connect to B13 and send 1§ data to terminal 15.

 [0028] In addition, the terminal 15 connected to the protocol B13 may notify the state when its own state changes or periodically. The gateway device 11 converts the received communication data into communication data corresponding to the protocol A, and transmits the communication data to the controller device 14 connected to the protocol A13.

 [0029] When the gateway device 11 detects that a new device is connected to the protocol B13, the gateway device 11 transmits notification data indicating that the new device is connected to the protocol B13, and receives the notification data. The controller device 14 thus inquired of the gateway device 11 for a service that can be handled by the new device and obtains the service, thereby enabling control of the newly connected device.

 FIG. 2 is a diagram showing a protocol stack of gateway apparatus 11 connected to a network of a plurality of types of protocols in the home network according to Embodiment 1 of the present invention. In FIG. 2, as an example, the gateway device 11 is connected to two different types of protocols A12 and B13.

 [0031] The gateway device 11 includes a protocol A communication processing unit 21, a protocol B communication processing unit 22, a protocol conversion processing unit 23, a device description creation processing unit 24, a device description template holding unit 25, a service A description creation processing unit 26, a service description template holding unit 27, a protocol conversion table holding unit 28, and a device configuration management unit 29 are provided.

 [0032] The protocol A communication processing unit 21 has a function of transmitting / receiving communication data to / from other devices connected to the protocol A12. When data is received from the protocol conversion processing unit 23, the communication data is transmitted to the protocol A 12 communication template. Change and send communication data to other devices connected to protocol A12. In addition, when communication data is received from another device connected to the protocol A12, the received communication data is analyzed and passed to the protocol conversion processing unit 23.

[0033] The protocol B communication processing unit 22 has a function of transmitting / receiving communication data to / from other devices connected to the protocol B 13, and receives data from the protocol conversion processing unit 23. Change the communication data to the communication template of 13 and send the communication data to other devices connected to protocol B13. In addition, when the other equipment connected to the protocol B 13 also receives communication data, it passes the received communication data to the protocol conversion processing unit 23 after analyzing it.

 [0034] Next, a case where information and services of devices connected to the protocol B13 are disclosed to the protocol A will be described.

 [0035] The controller device connected to the protocol A12 also transmits communication data requesting device information data (specifically, a device information description described below) describing the configuration of the device connected to the protocol B to the gateway. When the device 11 receives the data, the protocol conversion processing unit 23 receives the device information data in which the device information connected to the protocol B13 is described in XML from the device description creation processing unit 24, and transmits the device information data of the transmission source. The data is transferred to the protocol A communication processing unit 21 in order to return the device information data to the controller device that requested the data.

 [0036] Next, service information data describing services that can be supported by each device connected to the protocol B13 from the controller device connected to the protocol A12 (specifically, service information description described below) When the gateway device 11 receives the communication data requesting the service, the protocol conversion processing unit 23 sends service information described in XML to the service information held by each device connected to the protocol B13 from the service description creation processing unit 26. The data is received, and the data is passed to the protocol A communication processing unit 21 to return the service information data to the controller device that requested the service information data of the transmission source.

[0037] Next, when the gateway device 11 receives control data for requesting control of a device connected to the protocol B as well as the controller device connected to the protocol A12, the protocol conversion processing unit 23 performs a protocol conversion table described later. Information for converting control data from data for protocol A12 to data for protocol B13 is received from holding unit 28, and the address for protocol B13 of the corresponding device is received from device configuration management unit 29 described later. Receives, converts the address, converts the device name, attribute, data, etc., and passes control data to the protocol B communication processing unit 22 to control the device connected to protocol B13. [0038] Next, when the gateway device 11 receives notification data for notifying the state of the device from a device connected to the protocol B13, the protocol conversion processing unit 23 performs control from the protocol conversion table holding unit 28. Receives information for converting data from data for protocol B 13 to data for protocol A12, and receives information for converting the address for protocol B13 of the corresponding device from the device configuration management unit 29 to the address for protocol A12. In order to notify the data of the device connected to the protocol B13 to the controller connected to the protocol A12, the notification data is sent to the protocol A communication processing unit 21 to receive, convert the address, convert the device name, attribute, data, etc. hand over.

 In addition, when the protocol conversion processing unit 23 receives information that the device is connected to the protocol B13 from the protocol B communication processing unit 22, the protocol conversion processing unit 23 passes the information to the device description creation processing unit 24 and the device configuration management unit 17.

 In addition, when the protocol conversion processing unit 23 receives device information such as a device manufacturer and a manufacturing number, it similarly passes the received data to the device description creation processing unit 24.

 In addition, when the protocol conversion processing unit 23 receives information that the device is connected to the protocol B13 from the protocol B communication processing unit 22, the protocol conversion processing unit 23 passes the information to the device description creation processing unit 24 and the device configuration management unit 17.

 [0042] Further, when the protocol conversion processing unit 23 obtains information on data that can also control the device power connected to the protocol B13, the protocol conversion processing unit 23 passes the received data to the service description creation processing unit 26.

[0043] The device description creation processing unit 24 creates device information data using the protocol B13 system as a root device and the terminal 15 connected to the protocol B13 as an embedded device. When the device description creation processing unit 24 obtains information that a device is newly connected to the protocol B13, the device description creation processing unit 24 obtains a template for creating device information data from the device description template holding unit 25, which will be described later, and follows a certain conversion rule. Create information data. When the device information data is created or updated, the device description creation processing unit 24 passes the device information data to the protocol conversion processing unit 23. When receiving a device information data acquisition request from the protocol conversion processing unit 23, the device information data is passed to the protocol conversion processing unit 23. For example, device information data is XML Data indicating the configuration of the device connected to protocol B13.

 [0044] The service description creation processing unit 17 creates service information data for services, attributes, and data values that can be supported by the terminal 15 connected to the protocol B13. The attribute is data indicating the control target such as the operation status and installation location, and the service that can be handled is the data indicating control, status reference, and the presence / absence of an event, and the data is the ON or OF F of the operation status. It shows a specific control value such as. When the service description creation processing unit 17 obtains information such as the service, attribute, and data of the device connected to protocol B 13, it passes the corresponding device and attribute to the service description template holding unit 27 described later, and the service description template In order to create service information data from the holding unit 27, a template corresponding to the device and attribute is acquired, and the service information data is created according to a certain conversion rule defined for each template. When the service information data acquisition request is received from the protocol conversion processing unit 23, the service information data is passed to the protocol conversion processing unit 23. For example, the service information data is data indicating services, attributes, and data values that can be supported by a device connected to the protocol B13 in XML.

 [0045] The device description template holding unit 25 uses the device description creation processing unit 24 to create a template for creating device information data using the protocol B 13 system as a root device and the terminal 15 connected to the protocol B 13 as an embedded device. keeping. Upon receiving a template acquisition request for creating device information data from the device description creation processing unit 24, the device description template holding unit 25 passes the template to the device description creation processing unit 24. For example, the template for creating device information data is described in XML.

 [0046] The service description template holding unit 27 holds a template of service information data created for services, attributes, and data values that can be supported by the terminal 15 connected to the protocol B13. Control patterns are modeled by classifying patterns that control equipment.

[0047] Further, the service description template holding unit 27 holds each modeled control pattern as a service information data template. For example, here are four templates. For attributes that hold ON / OFF switching type data, such as operating status Keep the template. In addition, a template for attributes that lists data corresponding to attributes such as living room, entrance, and kitchen, such as the installation location, is stored. It also holds a template for attributes that hold analog values as data, such as set temperature. Also, as with timers, the timer ON setting, timer ON setting time, timer one OFF setting, timer OFF setting time and multiple attributes are stored together as one template. The service description template holding unit 27 holds the template as described above. Upon receiving a template acquisition request for creating service information data together with data on devices and attributes from the service description creation processing unit 17, A template suitable for the attribute is passed to the service description creation processing unit 17. For example, the template for creating service information data is described in XML.

 [0048] The protocol conversion table holding unit 28 converts the description language of the protocol A12 into the description language of the protocol B13 according to the request of the protocol conversion processing unit 23, passes the data to the protocol conversion processing unit 23, The description language is converted to the description language of protocol A12, and the data is passed to the protocol conversion processing unit 23.

 [0049] The protocol conversion table holding unit 28 holds two types of tables. The first is the device name conversion table 51 created for the conversion rules in protocol A12 and protocol B12 for device names. An example of the device name conversion table 51 is shown in FIG. The second is attribute conversion tables 61 and 71 created for the conversion rules in protocol A12 and protocol B12 for the attribute and the data corresponding to that attribute. Specific examples of attribute conversion tables are shown in Figs. The attribute conversion table 71 summarizes the attribute and data conversion rules for each device. In addition, the attribute conversion table 61 created for attributes that are commonly used for all devices, such as operating status and installation location, should be common for device names, not device names. Write Common as shown.

 The device configuration management unit 29 holds the configuration of the device connected to the protocol B12 as the address conversion table 81. An example of the address translation table is shown in Fig. 8.

[0051] When the controller device 14 controls the terminal 15 or when the gateway device transfers the notification data transmitted from the terminal 15 to the controller device, the protocol conversion processing unit 23 is addressed from the device configuration management unit 29. Get information. What is address translation information? For example, when controller device 14 controls terminal 15, refer to address conversion table 81 to indicate that device information is converted to a pair of ECHONET address and ECHONET object, and terminal 15 notifies controller device 14 of the status Refers to the address conversion table 81 and indicates that the device information is converted from the combination of ECHONET address and ECHONET object.

 In the gateway device 11 according to the first embodiment, the ECHONET property is classified according to the property value content in consideration of building the application at the UPnP control point, and the classified result is defined as the property type. It is characterized by V. ECHONET properties can be classified into the following eight property types, and the classification is based on the classification rules described below. FIG. 11 is a diagram showing an example of ECHONET property types classified by the gateway device 11 according to the first embodiment. Hereinafter, each property type will be described.

 (1) Numeric type: A property that indicates a property value as a numeric value. Data Type varies depending on the range of numerical values. Specifically, the Data Type is determined depending on whether it is an integer value or a numerical value after the decimal point, the signed force unsigned force, and the data byte size.

 (2) Date type: A property that holds date data. Data Type is Date. The data format in XML Description conforms to ISO8601 format and is yyyy—mm—dd (January day).

 (3) Time type: A property that holds time and time. Data Type is Time. The data format in the XML Description conforms to the ISO8601 format and is hh-m m- ss (hour, minute, second).

 (4) Level type: A property that is not a numerical value, but controls the ECHONET device with data indicating the magnitude relationship, and refers to the status of the ECHONET device. For example, the detection threshold level applies. Data Type is String.

 (5) Character notation type: A property that the data acquired from the ECHONET device is a character string or the data controlled by the ECHONE T device is a character string. For example, a product code may be a production number. Data Type is String.

(6) Reset type: defined! Controls ECHONET devices using a single value. This property is used to reset a certain state. Data Type is String.

 (7) Switching type: A property that controls an ECHONET device by switching two values or acquires one of two values from an ECHONET device. For example, an operation state, an abnormality occurrence state, and the like can be given. Data Type is String.

(8) Selection type: A property that controls an ECHONET device by selecting three or more intermediate values, or acquires one of three or more intermediate values from an ECHONET device. For example, the installation location can be mentioned. Data Type is String.

 [0053] As described above, the gateway device 11 according to the first embodiment performs the classification by the ECHONET property type, and this "classification by the ECHONET property type" classifies the ECHONET property according to the contents of the property value. Each property type is specified. For each property type, specify the naming rules for VariableName and Action. In addition, an application that controls a device can automatically build an application even when a new device is added by holding a service description template that serves as a template for each specified property type.

 [0054] Figure 12 is a reference diagram showing the relationship between property type, type classification, object, Action prefix, and datatype for classification and naming rules by ECHONET property type.

[0055] In the gateway device 11, when the service executable by the ECHONET device is disclosed to the UPnP network, the XML Service can be mapped mechanically to the XML Service Description. It is necessary to define the description element structure, data type, variable name naming rules, and action naming rules. "VariableName naming rule, Action naming rule" can be mapped by classifying according to ECHONET property type. Also, “Element structure, dataTypeJ, can be mapped by classifying according to the data type of ECHONET property.

[0056] As a naming standard for VariableName, there is no sense of incongruity as the VariableName of UPnP. It can be named mechanically, its meaning can be inferred as English, and the number of characters, including the Action prefix, can be up to 32 characters. Therefore, it is created according to the following rules.

 [0057] First, for each property type, the “object” indicating the content of the property is set as described in FIG. VariableName divides the property name into meaningful word levels, arranges the front force in order, and sets the object defined in Figure 12 at the end. These naming results are described in Appendix B, the ECHONET standard.

[0058] Also, the Action naming rule is to add VariableName to the Action prefix.

[0059] DataType is defined based on the classification based on the data type. For AVR type and Value type dataType, it is determined by the value range and data size of the ECHONET property. Similarly, for the Date type, the Data type or Time type is identified from the contents of the ECHONET property.

 FIG. 13 is a diagram showing an example of a format of the device description template 1300 held in the device description template holding unit 25 of the gateway device 11 according to the first embodiment. The specifications of each element shall conform to UPnP Device Architechture Ver.1.0.

 [0061] As an ECHONET-specific element, the domain name described in the XML Device Description is "echonet-gr-jp". Describe the element name “UDN”. The ECHONET-UPnP gateway describes the UUID in the XML Device Description so that it becomes unique to the EC HONET device when it detects the connection of the ECHONET device to the network. In addition to the XML description of the conventional device template, 1301 which is a description for specifying the type of ECHONET device and 1302 to 1304 which is a description related to the address information of the ECHONET device are added.

[0062] Note that the device description template 1300 may be registered in advance when the gateway device 11 is manufactured, or may be acquired from the outside via a network. In addition, the gateway device 11 creates a device information description by writing the device information obtained also for the terminal device on the protocol A side to the device description template 1300 in the device description creation processing unit 24. Communication based on UPnP on protocol A side By disclosing this device information description to the control device, the control device is connected to the protocol B side, and the device information of the terminal device can be acquired.

FIG. 14 is a diagram showing an example of a format description of the service description template 1400 held in the service description template holding unit 27 of the gateway device according to the first embodiment.

 [0064] The format of the XML Service Description to be used is determined by the ECHONET property type. The specifications of each element shall conform to UPnP Device Architechture Ver.1.0.

 As an ECHONET-specific element, the domain name described in XML Device Description is "echonet-gr-jp". Also, as shown in the figure, <name> SetVariableName </ name> (1401) when the property type is numeric, date, time, and character notation, and < name> WriteVariableName </ name> (1402) is described, and this description is added to the template information described in the ECHONET standard obtained from the terminal device on the protocol B side in the service description creation processing unit 26 of the gateway device 11. Based on this, the service information description is automatically created by overwriting, and the service information description is disclosed to the control apparatus that performs communication based on UP nP on the protocol A side. You can get service information of the terminal device connected to the B side!

FIG. 15 is a flowchart showing an operation procedure of gateway apparatus 11 according to the first embodiment.

[0066] First, a template in which terminal information according to the ECHONET standard is described is acquired from a device on the ECHONET side (S1501). Next, the ECHONET property that is each terminal information is classified into eight property types in the gateway device 11 (S1502). Then, the device description creation processing unit 24 and the service description creation processing unit 26 obtain a template corresponding to each property type and write service information, attribute information, and the like (S1 503). Next, check whether there is a template acquisition request from the UPnP control device that is the protocol A side (S1504). If there is an acquisition request (Yes in S1504), the device information disk created in S1503 Reply and service information discipline Yong is transmitted to the control device (S1505).

 [0067] FIG. 10 describes a method for disclosing ECHONET device information to UPnP devices in the home network according to Embodiment 1 of the present invention.

 In FIG. 10, as an example, two air conditioners, one refrigerator / freezer, and one washing / drying machine are connected. A device template is created to compile information on each ECHONET device as information to be disclosed to devices connected on UPnP. As a design policy for publishing ECHONET device information to UPnP, each ECHONET device is designated as root device 101 and ECHONET device information is disclosed to UPnP. Each ECHONET device has a service type named ECHONET—Service102.

 [0069] First, define the name of the ECHONET device. In order to publish the root device, that is, ECHO NET equipment on UPnP, the device type is defined as ECHONET—Appliance. In fact, when each ECHONET device is published on UPnP, the name unique to the ECHONET device is written in the appliance of the device description template 1300 in Fig. 13 described above. For example, when opening an air conditioner, it is often necessary to write “ECHONET—HomeAirConditioner”.

Next, in order to collect the service information held by the ECHONET device as information to be disclosed to the device connected to UPnP, a service description template 1400 as shown in FIG. 14 is defined. The name of the service type held by the ECHONET device is specified as ECHONET—Servicel02. For the service type, a variable name is defined for each pattern that controls the ECHONET device. The Variable Name is described as a combination of the name of the pattern that controls the device and the ECH ONET property name. For example, in the case of a pattern that controls equipment by switching two values with toggles, such as ONZOFF, the Variable Name is defined as Switch-property. For example, the operation state is applied to this control pattern. In the case of a pattern that uses a positive integer to control the device, Variable Name is defined as AnalogValue-uil-property. For example, the set temperature of an air conditioner applies to this control pattern. Also, in the case of a pattern that uses positive and negative integers to control devices, the Variable Name is defined as AnalogValue—il—property. For example, the outdoor temperature is applied to this control turn. In addition, data can be collected from multiple choices. In the case of a pattern that controls one device, select Variable Name as DataList—property. For example, the control mode setting of the air conditioner is applicable to this control pattern. It should be noted that the control described here includes referring to the state of the device simply by controlling the device. For the character string to be entered in "Property", enter the name of the ECHONET property. For example, if the name of the ECHONET property in the operating status is Status, Variable Name will be described as “Switch-Status”.

 [0071] Next, for the defined VariableName, the action for controlling the device, the action for referring to the state, and its arguments are specified.

 [0072] First of all, the naming convention for actions when controlling a device is that Set is a prefix of "name of pattern to be controlled". For example, the actions “SetSwitch”, “SetAnalogValue—ui 1”, “SetAnalogValue—il”, “SetDataList”. Then, define the naming conventions for Argument and relatedStateVariable, which are necessary arguments for controlling the device. The naming convention of Argument is New as a prefix of “control pattern name and proper ty”. For example, if the name of the pattern that controls the device is Switch, it is NewSwitch-property. Also, in the case of patterns that control other devices, they are “NewAnalogValue—ml—propertyj,” “NewAnalogValue—il—propertyj,” “New DataList—property. The character string entered in“ property ”is the ECHONET property name. As an example, the property is Status, so the argument is NewSwitch—Status The relatedStateVariable naming convention is the same as Variable Name, the name of the pattern that controls the device, the name of the ECHONET property, Describe in combination.

[0073] Next, as a naming rule for actions when referring to the state of a device, Get is a prefix of "name of a controlled pattern". Examples include the actions “GetSwitch”, “GetAnalogValue—uil”, “GetAnalogValue—il”, “GetDataList”. Then, define the naming rules for Argument and relatedStateVariable, which are arguments required when controlling the device. The naming rule of Argument is that Current is “the name of the pattern to be controlled and the prefix of propertyj. For example, if it is the name of the pattern that controls the device Switch, it is CurrentSwitch—property. Also, it controls other devices. In the case of patterns, each “CurrentAnalogValue—uil—propertyj”, “CurrentAnalogValue—il—propertyj” and “CurrentDataList—property. For the character string to be entered in“ property ”, enter the ECHONET property name. Therefore, Argum ent is CurrentSwitch-Status The naming rules for relatedStateVariable are described in combination with the name of the pattern that controls the device and the name of the ECHONET property, just like Variablé Name.

 [0074] As described above, in the gateway device 11 according to the first embodiment, parameters such as Appliance and property can be defined for each device for the ECHONET device information and the service information held by the device. Instead, device templates and service templates common to ECHONET devices can be created by defining them as common parameters.

 [0075] Furthermore, by automatically mapping the ECHONET device information and the service information held by the device, it is possible to create information that is automatically disclosed to devices connected to UPnP. Therefore, even when new device information and services held by the device are defined in the ECHONET protocol, device information and service information can be disclosed to the UPnP side by automatic mapping.

 [0076] Further, as described above, the service information description for publishing the device information and service information of the UPnP virtual device in the gateway device 11 is created in accordance with a certain rule. Specified for each property type that classifies ECHONET properties. Therefore, even when a new device standard is used, the ECHONE T property can be mechanically mapped from the ECHONET property to the XML information description by simply classifying the ECHONE T property into a property type at the time of standard creation. Can be interconnected between terminal devices connected to communication networks based on heterogeneous protocols.

 [0077] (Embodiment 2)

 The second embodiment of the present invention will be described below with reference to the drawings.

FIG. 3 shows a protocol of the controller device 14 connected to a network having a protocol different from that of the terminal 15 to be controlled in the home network according to the second embodiment of the present invention. It is the block diagram which showed the coll stack.

 [0079] The controller device 14 includes a protocol A communication processing unit 30, a device description detection processing unit 31, a device analysis processing unit 32, a service description detection processing unit 33, a service analysis processing unit 34, and an event reception processing unit. 35, a device control processing unit 36, and a data holding unit 37.

 [0080] When the controller device 14 is connected to the network, the device description detection processing unit 31 transmits the disk scanner request data and receives the discovery response data in order to detect a device connected to the network. The analysis processing unit 32 passes the force burr response data and receives the result of analysis by the device analysis processing unit 32. In addition, when the device description detection processing unit 31 receives the information that the device is connected to the network, the device description detection processing unit 31 passes the received data to the device analysis processing unit 32 and receives the result of the device analysis processing unit 32 praying.

 The device analysis processing unit 32 analyzes the data received from the device description detection processing unit 31, analyzes the system configuration and connected devices, and passes the analysis result to the device description detection processing unit 31. For example, this data is created in XML, and the device analysis processing unit 32 holds the XML parser function for analyzing XML.

 [0082] After the controller device 14 detects a device connected to the network or after detecting information notifying that the device connected to the network is connected to the network, the service description detection processing unit 33 detects the corresponding device. Requests and obtains publicly available attributes and services. The acquired public information such as attributes and services is passed to the service analysis processing unit 34, and the analysis result of the service analysis processing unit 34 is received.

 [0083] The service analysis processing unit 34 prays the data received from the service description detection processing unit 33, analyzes attributes and services that can be supported by the control target device, and sends the analysis results to the service description detection processing unit 33. hand over. For example, this data is created in XML, and even with the XML parser function that parses XML, the service analysis processing unit 34 retains it.

When the event reception processing unit 35 receives notification data transmitted by another device, the event reception processing unit 35 passes the notification data to the device description detection processing unit 31 and the service description detection processing unit 33, thereby notifying the notification data. Acquires information on the data transmission source device, notification data attributes, and data values, and passes them to the data holding unit 37 described later.

When controlling the device, the device control processing unit 36 obtains information such as the address of the control target device from the device description detection processing unit 31, and the control target device attribute and data value from the service description detection processing unit 33. And send control request data to the control target device. The device control processing unit 36 receives a response from the control target device.

The control result is passed to the data holding unit 37.

[0086] The data holding unit 37 holds the attribute of the device controlled by the controller device 14 and the current data value corresponding to the attribute.

FIG. 4 is a configuration diagram showing a protocol stack of the controller device 14 connected to a network having a protocol different from that of the terminal 15 to be controlled in the home network according to Embodiment 2 of the present invention.

The controller device 14 shown in FIG. 4 holds a screen display unit 41 for displaying the configuration and state of the device to the user in addition to the configuration of the controller device 14 shown in FIG. The screen display unit 41 has a function of displaying a screen for the user to control the terminal 15, the terminal 16, and the terminal 17.

 The screen display unit 41 determines the screen configuration to be displayed by receiving service information data from the service description detection processing unit 33. In other words, the service information data is a control model in which patterns to be controlled are classified, and the screen display unit 41 holds a widget set for each control model. By applying this widget set to the screen, the screen display unit 41 A framework can be generated. Furthermore, the screen display unit 41 includes information such as the device name acquired from the device description detection processing unit 31, the attribute of the control target device acquired from the service description detection processing unit 33, and the control target device acquired from the data holding unit 37. A screen can be generated by writing this data to the widget set.

FIG. 16 is a diagram showing an example of a screen displayed on the screen display unit 41 of the controller device 14 according to the second embodiment. The screen created by the above method is displayed on the screen corresponding to the ECHONET property type (level type, selection type, switching type, character notation type), for example, as shown in Fig. 16 (a) to (d). And can. FIG. 17 is a flowchart showing an operation procedure in screen display of the controller device 14 according to the second embodiment.

 First, a service information description described in XML is acquired from the gateway device (S1701). Next, the contents of the service information description are analyzed (S 1702), and the ECHONET property type associated with the terminal device on the ECHONET side is specified (S1703). The screen is displayed using the widget set for each ECHONET property type (S 1704).

 [0093] As described above, in the controller device according to the second embodiment, the screen can be freely generated if the widget set for each ECHONET property that is the control model is retained for the screen. Therefore, it is possible to easily generate a screen for indicating the status of the device and controlling the device on the screen of the device connected to the network of any protocol.

 [Embodiment 3]

 The third embodiment of the present invention will be described below with reference to the drawings.

 FIG. 9 is a system configuration diagram of a home network configured with a plurality of types of protocols in the home network according to Embodiment 3 of the present invention.

 The gateway device 11 receives from the center server 91 via the Internet 92 a protocol conversion table 51 related to device names, a conversion table 61 related to attributes and data common to devices, and a conversion table 71 related to attributes and data for each device. Then, each table held in the protocol conversion table holding unit 28 is updated.

 Similarly, when the gateway apparatus 11 receives a template of device information data from the center server 91 through the Internet 92, the device description template holding unit 25 adds a template update force as a new template.

 When the gateway apparatus 11 receives a service information data template from the center server 91 through the Internet 92, the service description template holding unit 19 updates the service information data template, new service information data Add as a template.

[0099] As described above, in the gateway device 11 according to the third embodiment, a device to be controlled. Increased vessel type, attributes, and data! ], Or even if it is changed, interconnection between heterogeneous networks can be realized simply by adding a protocol conversion table, a device information data template, or a service information data template.

Industrial applicability

 The gateway device of the present invention is useful, for example, as a device for connecting networks in a home network system in which different protocols are mixed.

Claims

Claims [1] A gateway device for connecting networks of two or more protocols including at least different types of first protocol and second protocol, which are described based on a standard used for the second protocol, Based on a standard used for the first protocol from a template holding means for holding a template in which information related to a terminal device connected to the network of the first protocol is written, and a terminal device connected to the network of the first protocol An acquisition unit that acquires information on the terminal device; and the template stored in the template storage unit is acquired, and the terminal device information description is created by writing information on the terminal device acquired in the acquisition unit Template description creation process A protocol conversion table holding means for holding a protocol conversion table for associating an expression format of information corresponding to the terminal device in the first protocol and the second protocol based on the name of the terminal device; Protocol conversion means for performing protocol conversion when communication is performed between the control device connected to the second protocol network and the terminal device connected to the first protocol network with reference to a protocol conversion table And a communication means capable of transmitting the terminal device information description updated in the template description creation processing means to the control device connected to the network of the second protocol. apparatus. 2. The gateway device according to claim 1, further comprising device configuration management means for managing a configuration of the terminal device connected to the network of the first protocol. [3] The template holding means is a device that holds a device description template that is described based on a standard used for the second protocol and in which device information of the terminal device connected to the network of the first protocol is written. The template includes a description template holding unit and a service description template holding unit that holds a service description template that is described based on a standard used for the second protocol and in which service information provided by the terminal device is written. The description creation processing means obtains the device description template from the device description template holding unit, automatically writes the device information obtained by the obtaining means in accordance with a prescribed rule, and creates a device information description. A device description creation processing unit, and Service description creation processing for obtaining the service description template from the service description template holding unit and automatically writing the service information obtained by the obtaining means in accordance with a prescribed rule to create a service information description The gateway device according to claim 1, wherein the gateway device is configured by a unit. [4] The device information description created by the device description creation processing unit uses the first protocol network system as a root device to connect the terminal device connected to the first protocol network. The gateway device according to claim 3, wherein the gateway device is disclosed as device information of the terminal device to the control device connected to the network of the second protocol through the communication means as an embedded device. . [5] The gateway device is further connected to the Internet, and the server device power is connected to the first protocol, the protocol conversion table corresponding to the terminal device, the device description template, and the service description template. The gateway device according to claim 3, further comprising an internet connection means for obtaining. [6] The service description template holding unit further includes a service description template defined for each property type that is a control model classified into a pattern for controlling the terminal device connected to the network of the first protocol. The service description creation processing unit classifies the information about the service acquired by the acquisition unit into the property type set in advance according to a predetermined rule, and corresponds to the property type from the service description template storage unit. 4. The gateway device according to claim 3, wherein a service description template to be selected is selected, and the service information description is created according to a rule defined for each service description template. [7] The property type includes  (1) Numeric type that indicates a property value as a numeric value  (2) Date type that holds date data  (3) Time and time type that holds time  (4) Level type that refers to the size relationship, not the numerical value, or the state of the terminal device connected to the first protocol.  (5) Terminal equipment connected to the first protocol Character notation type in which data to be acquired is a character string or data for controlling the terminal equipment is a character string  (6) A reset type used to reset a certain state by controlling a terminal device connected to the first protocol using only one defined value.  (7) A switching type that controls a terminal device connected to the first protocol by switching two values or acquires one of two values from the terminal device (8) Control the terminal device connected to the first protocol by selecting from among three or more values, or acquire any value from the three or more values from the terminal device Select type to  The gateway device according to claim 6, wherein at least one of the following is included. [8] The service description template holding unit includes, as the property type for creating the service information description, on / off switching type data, enumeration type data, analog numeric type data, step value type data, 7. The gateway device according to claim 6, further comprising a service description template having at least one of a template composed of a plurality of attributes as a data value. [9] A control device for controlling a terminal device connected to the second protocol network and connected to the first protocol network, Check the connection status of the terminal device connected to the network of the first protocol to be controlled, and detect that the terminal device to be controlled is connected to the network. V, device description detection processing means for holding device information description that is device information of the acquired terminal device;  Device analysis processing means for analyzing the device information description, and a terminal for connecting the service information description describing the service information held by the terminal device to be controlled to the network of the first protocol A service description detection processing means for requesting and obtaining a device;  Service analysis processing means for analyzing the service information description, and when receiving notification data regarding the terminal device power status to be controlled, the device description detection processing means power, acquiring the device information description, By acquiring the service information description from the service description detection processing means, event reception processing means for analyzing the content of the received notification data, and for controlling the terminal device to be controlled In addition, the device description processing means obtains the device information description from the device description detection means, and the service description detection processing means. The device control processing means obtains the service information description and creates communication data for control. When,  Data holding means for holding at least the device information description and service information description of all the terminal devices to be controlled; and the device information description and service of the terminal device to be controlled Information description power comprises screen display means for displaying a screen for a user to confirm and control the state of the terminal device.  A control device characterized by that.  [10] The screen display means holds a widget set that generates a screen framework for each property type of the service information description, and generates a screen framework by applying the widget set to the screen. In accordance with the rules of the widget set, the screen is generated by writing the data included in the service information description into the widget set.  The control device according to claim 9. [11] Terminal equipment connected to the first protocol network and the second protocol network A home network system comprising a control device connected to the network and a gateway device connecting at least a second protocol network and a first protocol network,  The gateway device is  A template holding means for holding a template written based on a standard used for the second protocol and in which information about a terminal device connected to the network of the first protocol is written;  Obtaining means for obtaining information of the terminal device based on a standard used for the first protocol from a terminal device connected to the network of the first protocol;  Template description creation processing means for obtaining terminal device information description by acquiring the template held by the template holding means and writing information on the terminal device obtained by the obtaining means;  A protocol conversion table holding means for holding a protocol conversion table for associating a representation format of information corresponding to the terminal device in the first protocol and the second protocol based on the name of the terminal device;  Protocol conversion for referring to the protocol conversion table and performing protocol conversion when communication is performed between the control device connected to the second protocol network and the terminal device connected to the first protocol network. Means,  Communication means capable of transmitting the terminal device information description updated in the template description creation processing means to the control device connected to the network of the second protocol.  A home network system characterized by that. The template holding means of the gateway device is a device information description for holding a device information description based on a standard used for the second protocol relating to device information of the terminal device connected to the network of the first protocol. And a service information discretion holding unit that holds a service information description based on the standard used for the second protocol related to the service provided by the terminal device, The template description creation processing means acquires a template for creating device information of the terminal device connected to the first protocol from the device information description holding unit, and automatically according to a prescribed rule. A device description creation processing unit that describes device information acquired by the acquisition unit to generate a device information description, and a service of the terminal device connected to the first protocol from the service information description holding unit A service description creation processing unit configured to obtain a template for creating information, automatically describe the service information obtained by the obtaining unit according to the prescribed rule, and generate a service information description;  The control device includes:  Screen display means for displaying a screen for the user to check and control the status of the terminal device from at least the device information description and the service information description of the terminal device to be controlled; Prepare  12. The home network system according to claim 11, wherein:  A network connection method used in a gateway device for connecting between networks of two or more protocols including at least different types of first protocol and second protocol,  A template holding step for holding a template that is described based on a standard used for the second protocol and in which information about a terminal device connected to the network of the first protocol is written;  An acquisition step of acquiring information of the terminal device based on a standard used for the first protocol from a terminal device connected to the network of the first protocol; A template description creation processing step of creating a terminal device information description by acquiring the template to be held in the template holding step and writing information on the terminal device acquired in the acquisition step. And a protocol conversion table holding step for holding a protocol conversion table for associating a representation format of information corresponding to the terminal device in the first protocol and the second protocol based on the name of the terminal device; Protocol conversion for referring to the protocol conversion table and performing protocol conversion when communication is performed between the control device connected to the second protocol network and the terminal device connected to the first protocol network. Steps,  A communication step capable of transmitting the terminal device information description updated in the template description creation processing step to the control device connected to the network of the second protocol.  A network connection method characterized by the above.  A program used in a gateway device for connecting between networks of two or more protocols including at least different types of first protocol and second protocol, written according to the standard used for the second protocol, A template holding step for holding a template in which information about terminal devices connected to the protocol network is written;  An acquisition step of acquiring information of the terminal device based on a standard used for the first protocol from a terminal device connected to the network of the first protocol;  A template description creation processing step of creating a terminal device information description by acquiring the template to be held in the template holding step and writing information on the terminal device acquired in the acquisition step. And a protocol conversion table holding step for holding a protocol conversion table for associating a representation format of information corresponding to the terminal device in the first protocol and the second protocol based on the name of the terminal device;  Protocol conversion for referring to the protocol conversion table and performing protocol conversion when communication is performed between the control device connected to the second protocol network and the terminal device connected to the first protocol network. Steps,  A communication step capable of transmitting the terminal device information description updated in the template description creation processing step to the control device connected to the network of the second protocol;  A program that causes a computer to execute.