JP4745337B2 - Gateway device and control device - Google Patents

Description

  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 respectively connected to networks of different protocols and connected to networks of both protocols, and in particular, to a network to which the terminal devices are connected. The present invention relates to a gateway device having a method of disclosing connection status and services and attributes that can be handled by each terminal device to a control device connected to a network of a different protocol.

  Traditionally, applications, services, and devices describe their capabilities, publish them to other applications, services, and devices, integrate different networks into a unified framework, and different networks It describes the mechanism by which various network entities located within discover and interact with each other.

  For example, a method is disclosed in which a plurality of networks having different communication protocols are integrated into a single unified framework so that a user application can discover and use various network devices ( For example, see Patent Document 1).

More specifically, in recent years, network support for information devices and AV devices has progressed. For example, UPnP (Universal Plug and Play) has attracted attention as a communication protocol, and application of products has already progressed. In the future, when an ECHONET device that uses ECHONET, which is a communication protocol in the home, is integrated with information devices and AV devices to be systemized, system coexistence with UPnP devices is also desired.
JP 2001-290724 A

  However, conventionally, even when information on devices connected to its own network and information on attributes and data corresponding to the devices are disclosed to networks of different protocols, data to be disclosed for each device is defined. As a result, not only does the work become enormous, but there is a problem that when different devices define the same device, the definition becomes different, and a controller that controls devices connected to networks with different protocols has been developed. There is a problem that it is very difficult to do.

  Specifically, the above-mentioned home ECHONET devices and AV devices need a gateway function that interconnects the ECHONET protocol and the UPnP protocol for AV devices, but in the current ECHONET standard, There is also a problem that mutual cooperation between ECHONET devices and AV devices in the home cannot be realized because the concrete gateway function is not standardized.

  The present invention is for solving the above-described problems, and by making the gateway function common and standardizing, a gateway device that can appropriately realize interconnection between terminal devices connected to a communication network based on a heterogeneous protocol The purpose is to provide.

  In order to solve the above problems, a gateway device according to the present invention is a gateway device that connects networks of two or more types of protocols including at least different types of first and second protocols, A template holding means for holding a template that is described based on a standard used for a protocol and in which information about 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 based on a standard used for one protocol, and the template held by the template holding unit are acquired, and information on the terminal device acquired by the acquisition unit is written. Terminal equipment information discrepancy A template description creating processing means for creating a protocol and a protocol 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 A protocol for performing communication between the conversion table holding means and the control device connected to the second protocol network and the terminal device connected to the first protocol network with reference to the protocol conversion table. A protocol conversion means for performing the conversion, 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. It is characterized by.

  The template holding means of the gateway device according to the present invention is 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. A device description template holding unit for holding, and a service description template holding unit for holding a service description template written in accordance with a standard used for the second protocol and in which service information provided by the terminal device is written. The description creation processing unit acquires the device description template from the device description template holding unit, and automatically writes the device information acquired by the acquisition unit according to a prescribed rule to generate a device information description. A service that obtains the service description template from the device description creation processing unit and the service description template holding unit and automatically writes the service information obtained by the obtaining unit in accordance with a prescribed rule to create a service information description. It is characterized by comprising a description creation processing unit.

  With these configurations, the terminal device described in the template suitable for the first protocol standard acquired from the terminal device connected to the first protocol network with respect to the control device connected to the second protocol network. On the basis of the information related to the above, the terminal device information description suitable for the standard of the second protocol can be automatically created in the template description creation processing means and can be disclosed to the control device. Therefore, it is possible to provide a gateway device that can realize mutual connection between terminal devices connected to a communication network based on a different protocol.

  In addition, the service description template holding unit of the gateway device according to the present invention is further 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. A service description template is stored, and the service description creation processing unit classifies the information about the service acquired by the acquisition unit into the property type predetermined according to a predetermined rule, and the property description from the service description template storage unit. A service description template corresponding to the type is selected, and the service information description is created according to a rule defined for each service description template.

  With this configuration, the service description creation processing unit classifies the attributes and services held by each device into the property type that is the control model of the device and device attribute information and service information, and services based on the second protocol standard By creating an information description and disclosing this service information description to the control device connected to the network of the second protocol, the network is easily provided to the terminal device connected to the heterogeneous network. Information about the device including the configuration and service information that each device can handle can be disclosed.

  The gateway device according to the present invention further includes the protocol conversion table corresponding to the terminal device connected to the Internet and connected to the first protocol from the server device, the device description template, and the service description template. Internet connection means for acquiring

  With this configuration, in the Internet connection means, the name of the terminal device, the protocol conversion table that associates the expression format for each protocol of the service supported by the terminal device, and the device information description are created. Device description template, service description template for creating the service information description can be acquired, and even when a new service or a new terminal device is added, the latest template is acquired via the network, It is possible to cope with connections between networks that appropriately use different protocols.

  The control device according to the present invention is a control device for controlling a terminal device connected to the network of the first protocol and connected to the network of the first protocol, and the network of the first protocol to be controlled Device description detection that confirms the connection status of the terminal device connected to the device, detects that the terminal device to be controlled is connected to the network, and retains the device information description that is the device information of the acquired terminal device A processing means, a device analysis processing means for analyzing the device information description, and a service information description describing the service information held by the terminal device to be controlled are connected to the network of the first protocol. Service description detection process to request and acquire from terminal equipment A service analysis processing means for analyzing the service information description, and when receiving notification data regarding a state from the terminal device to be controlled, the device information description is obtained from the device description detection processing means, By acquiring the service information description from the service description detection processing means, the event description processing means for analyzing the content of the received notification data, and the device description for controlling the terminal device to be controlled Device control processing means for acquiring the device information description from the detection processing means, acquiring the service information description from the service description detection processing means, and creating communication data for control, and at least all control targets The terminal A data holding means for holding the device information description and the service information description, and the user confirms the state of the terminal device from the device information description and the service information description of the terminal device to be controlled, And screen display means for displaying a screen for control.

  Further, the screen display means 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 to apply a screen The framework 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.

  With these configurations, when a control device connected to a heterogeneous network receives this published service information description, the control device uses a widget set corresponding to each property type as each control model in the screen display means. Thus, a user interface can be easily created. Further, the method in the control device according to the present invention is not limited to a specific protocol, and can be used for interconnection between all kinds of different protocols.

  In order to achieve the above object, the present invention can be realized as a network connection method using characteristic means of the gateway device as steps, or as a program for causing a computer to execute each step. It goes without saying that such a program can be distributed through a recording medium such as a CD-ROM or a transmission medium such as the Internet.

  According to the method of disclosing the connection status of devices to devices on different protocols in the gateway device and the services that each device can handle in the present invention, it is easy to simply classify the services of each device into property types that are control models. Services that can be supported by each device can be disclosed to devices on different protocols, and interconnection between terminal devices connected to a communication network based on different protocols can be appropriately realized.

  In addition, with respect to a control device that receives service information of a device connected to a heterogeneous network, an application can be easily created if a user interface component corresponding to a property type that is each control model is held. .

  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.

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

  The terminal 15, the terminal 16, and the terminal 17 are devices such as an air conditioner and a refrigerator-freezer. 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 A 12 and the terminals 15, 16, and 17 connected to the protocol B 13 realize the interconnection between different types of 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 these pieces of information, the controller device 14 transmits communication data for controlling devices 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. The communication data is transmitted to the terminal 15 connected to the corresponding protocol B13.

  Further, the terminal 15 connected to the protocol B13 may notify the status when the status of the terminal 15 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.

  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 to the protocol A12, and the controller device 14 that has received the notification data transmits the notification data. The newly connected device can be controlled by inquiring the gateway device 11 about services that can be handled by the new device.

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

  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, and a service 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.

  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 the data is received from the protocol conversion processing unit 23, the protocol A communication processing unit 21 changes the communication data to the protocol A12 communication template. Send communication data to other devices connected to. Also, when communication data is received from another device connected to the protocol A12, the received communication data is passed to the protocol conversion processing unit 23 after being analyzed.

  The protocol B communication processing unit 22 holds a function of transmitting / receiving communication data to / from other devices connected to the protocol B13. When data is received from the protocol conversion processing unit 23, the protocol B communication processing unit 22 changes the communication data to the protocol B13 communication template. Send communication data to other devices connected to. When communication data is received from another device connected to the protocol B13, the received communication data is passed to the protocol conversion processing unit 23 after being analyzed.

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

  The gateway device 11 receives communication data for requesting device information data (specifically, device information description described below) describing the configuration of the device connected to the protocol B from the controller device connected to the protocol A12. In this case, the protocol conversion processing unit 23 receives the device information data in which the information of the device connected to the protocol B13 is described in XML from the device description creation processing unit 24, and sends the device information to the controller device that requested the source device information data. In order to respond with the information data, the data is passed to the protocol A communication processing unit 21.

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

  Next, when the gateway device 11 receives control data for requesting control from the controller device connected to the protocol A12 to the device connected to the protocol B, the protocol conversion processing unit 23 reads from the protocol conversion table holding unit 28 described later. , Receives information for converting the control data from data for protocol A12 to data for protocol B13, receives the address for the protocol B13 of the corresponding device from the device configuration management unit 29 described later, converts the address, and names the device Then, control data is passed to the protocol B communication processing unit 22 in order to convert attributes, data, and the like and to control devices connected to the protocol B13.

  Next, when the gateway device 11 receives notification data for notifying the state of the device from the device connected to the protocol B13, the protocol conversion processing unit 23 sends the control data for the protocol B13 from the protocol conversion table holding unit 28. Information for converting data to data for protocol A12 is received, information for converting the address for protocol B13 of the corresponding device from the address for protocol B12 to the address for protocol A12 is received from device configuration management unit 29, address conversion, device name In order to convert attributes, data, etc., and to notify the controller connected to the protocol A12 of the data of the device connected to the protocol B13, the notification data is passed to the protocol A communication processing unit 21.

  When the protocol conversion processing unit 23 receives information indicating that a device is connected to the protocol B 13 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.

  When the protocol conversion processing unit 23 receives device information such as a device manufacturer and serial number, the protocol conversion processing unit 23 similarly passes the received data to the device description creation processing unit 24.

  When the protocol conversion processing unit 23 receives information indicating that a device is connected to the protocol B 13 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 acquires information on data that can be controlled from a device connected to the protocol B13, the protocol conversion processing unit 23 passes the received data to the service description creation processing unit 26.

  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 acquires information that a device is newly connected to the protocol B13, the device description creation processing unit 24 acquires a template for creating device information data from the device description template holding unit 25 to be described later, and the device description according to 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. Further, when a device information data acquisition request is received from the protocol conversion processing unit 23, the device information data is transferred to the protocol conversion processing unit 23. For example, the device information data is data indicating the configuration of a device connected to the protocol B13 in XML.

  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. Attribute is data indicating the control target such as operation status and installation location, compatible service is data indicating control, status reference, presence / absence of event, data is concrete such as ON / OFF of operation status This indicates a typical control value. When the service description creation processing unit 17 acquires information such as the service, attribute, and data of the device connected to the protocol B13, the service description creation processing unit 17 passes the corresponding device and attribute to the service description template holding unit 27 described later, and the service description template holding unit 27 In order to create service information data from the template, 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 receiving a service information data acquisition request 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.

  The device description template holding unit 25 holds a template for creating device information data with the device description creation processing unit 24 using the protocol B13 system as a root device and the terminal 15 connected to the protocol B13 as an embedded device. When 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, a template for creating device information data is described in XML.

  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. A control pattern is formed into a control model by classifying patterns for controlling the devices.

  Also, the service description template holding unit 27 holds a service information data template for each modeled control pattern. For example, the following four points are given as examples of templates. Holds templates for attributes that hold ON / OFF switching type data as in the operation state. In addition, a template for attributes indicating a list of data corresponding to attributes such as a living room, an entrance, and a kitchen such as an installation location is held. Further, a template for an attribute that holds an analog numerical value as data, such as a set temperature, is held. In addition, as with the timer, timer ON setting, timer ON setting time, timer OFF setting, timer OFF setting time, and a plurality of attributes are collectively stored as one template. The service description template holding unit 27 holds a template as described above, and when 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 suitable template is passed to the service description creation processing unit 17. For example, a template for creating service information data is described in XML.

  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, and sets the description language of the protocol B13. The data is converted to the description language of the protocol A12 and passed to the protocol conversion processing unit 23.

  The protocol conversion table holding unit 28 holds two types of tables. The first is a device name conversion table 51 created for conversion rules in protocol A12 and protocol B12 with respect to 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 the protocol A12 and the protocol B12 regarding the attribute and the data corresponding to the attribute. Specific examples of the attribute conversion table are shown in FIGS. The attribute conversion table 71 summarizes attribute and data conversion rules for each device. Also, the attribute conversion table 61 created for attributes commonly used for all devices, such as the operating state and installation location, indicates that the device name is common instead of the device name. Is described as Common.

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

  When controlling the terminal 15 from the controller device 14 or when the gateway device transfers notification data transmitted from the terminal 15 to the controller device, the protocol conversion processing unit 23 acquires address conversion information from the device configuration management unit 29. . For example, when the controller device 14 controls the terminal 15, the address conversion information refers to conversion from the device information into a set of ECHONET address and ECHONET object with reference to the address conversion table 81, and the terminal 15 transmits to the controller device 14. When notifying the status, the address conversion table 81 is referred to indicate that a set of ECHONET address and ECHONET object is converted into device information.

In the gateway device 11 according to the first embodiment, the ECHONET property is classified according to the contents of the property value in consideration of the application construction at the UPnP control point, and the classified result is defined as the property type. It is a feature. 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 illustrating an example of ECHONET property types classified in the gateway device 11 according to the first embodiment. Hereinafter, each property type will be described.
(1) Numeric type: A property indicating a property value by a numerical 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, a numerical value after the decimal point, signed or unsigned, and the data byte size.
(2) Date type: A property that holds data indicating a date. Data Type is Date. The data format in the XML description conforms to the ISO 8601 format and is yyyy-mm-dd (year-month-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 ISO 8601 format and is hh-mm-ss (hour-minute-second).
(4) Level type: A property that is not a numerical value, but controls ECHONET devices with data indicating the magnitude relationship, and refers to the status of ECHONET devices. For example, the detection threshold level applies. Data Type is String.
(5) Character notation type: A property in which data acquired from an ECHONET device is a character string or data to be controlled by an ECHONET device is a character string. For example, a product code or a production number can be given. Data Type is String.
(6) Reset type: A property used when a certain state is reset by controlling the ECHONET device using only one defined value. 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 from three or more values, or acquires any value from three or more values from an ECHONET device. For example, the installation location can be mentioned. Data Type is String.

  As described above, the gateway device 11 according to the first embodiment performs classification based on the ECHONET property type. This “classification based on the ECHONET property type” classifies the ECHONET property according to the content of the property value, and sets the property type for each ECHONET property. Is specified. For each property type, the naming rules for Variable Name and Action are defined. In addition, an application that controls a device can automatically construct an application even when a new device is added by holding a service description template that is a template of the application for each specified property type.

  FIG. 12 is a reference diagram showing the relationship among property type, type classification, object, action prefix, and datatype for classification and naming rules by ECHONET property type.

  In the gateway device 11, when the service executable by the ECHONET device is disclosed to the UPnP network, the element configuration of the XML Service Description, the dataType, the data type, and the ECHONET property can be mechanically mapped to the XML Service Description. It is necessary to define a naming rule for Variable Name and a naming rule for Action. “Variable Name naming rules, Action naming rules” can be mapped by classifying them according to the ECHONET property type. Also, “element configuration, dataType” can be mapped by classifying according to the data type of the ECHONET property.

  The naming standard for Variable Name is that there is no sense of incongruity as UPnP Variable Name, it can be named mechanically, its meaning can be inferred as English, and the number of characters is 32 characters or less, including the Action prefix. . Therefore, it is created according to the following rules.

  First, for each property type, the “object” indicating the content of the property is set as described in FIG. In Variable Name, property names are divided into meaningful word levels, arranged in order from the front, and the object defined in FIG. 12 is set last. These naming results are described in Appendix B, the ECHONET standard.

  The Action naming rule is that Variable Name is added to the Action prefix.

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

  FIG. 13 is a diagram showing an example of the format of the device description template 1300 held in the device description template holding unit 25 of the gateway apparatus 11 according to the first embodiment. In addition, about the specification of each element, it shall be based on UPnP Device Architechture Ver.1.0.

  As an ECHONET-specific element, the domain name described in 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 is unique to the ECHONET 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 the ECHONET device and 1302 to 1304 which are descriptions regarding the address information of the ECHONET device are added.

  The device description template 1300 may be registered in advance when the gateway apparatus 11 is manufactured, or may be acquired from the outside via a network. Further, the gateway apparatus 11 creates a device information description by writing device information acquired from the terminal device on the protocol A side in the device description template 1300 in the device description creation processing unit 24, and based on UPnP on the protocol A side. The device information of the terminal device connected to the protocol B side can be acquired by disclosing the device information description to the control device that performs communication.

  FIG. 14 is a diagram illustrating an example of the 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.

  The format of the XML Service Description to be used is determined by the ECHONET property type. In addition, about the specification of each element, it shall be based on 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 this figure, <name> SetVariableName </ name> (1401) if the property type is numeric, date, time, or character notation, and <name> if it is a level type. WriteVariableName </ name> (1402) is described, and this description is automatically overwritten based on the template information described in the ECHONET standard acquired from the terminal device on the protocol B side in the service description creation processing unit 26 of the gateway apparatus 11. By creating a service information description, and publishing this service information description to the control device that performs communication based on UPnP on the protocol A side, the service of the terminal device to which the control device is connected to the protocol B side Information can be acquired.

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

  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, in the device description creation processing unit 24 and the service description creation processing unit 26, a template corresponding to each property type is acquired and service information, attribute information, etc. are written (S1503). Next, it is confirmed whether there is a template acquisition request from the UPnP side control device which is the protocol A side (S1504). If there is an acquisition request (Yes in S1504), the device information disk created in S1503 The description and service information description are transmitted to the control device (S1505).

  FIG. 10 describes a method for disclosing ECHONET device information to devices on UPnP in the home network according to the first embodiment of the present invention.

  In FIG. 10, as an example, two air conditioners, one refrigerator-freezer, and one washing dryer are connected. Create a device template to collect information on each ECHONET device as information to be disclosed to devices connected to UPnP. As a design policy for releasing ECHONET device information to UPnP, each ECHONET device is set as the root device 101, and ECHONET device information is released to UPnP. Each ECHONET device has a service type named ECHONET_Service102.

  First, define the name of the ECHONET device. In order to expose the root device, that is, the ECHONET device on UPnP, the device type is defined as ECHONET_Appliance. Actually, when each ECHONET device is disclosed on UPnP, a 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 the air conditioner is disclosed, “ECHONET_HomeAirConditioner” is described.

  Next, in order to collect the service information held by the ECHONET device as information to be disclosed to devices 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 defined as ECHONET_Service102. As the service type, a variable name is defined for each pattern that controls the ECHONET device. Variable Name is described with the combination of the name of the pattern that controls the device and the ECHONET property name. For example, in the case of a pattern in which a device is controlled by switching two values with toggle, such as ON / OFF, 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 in which a device is controlled using a positive integer, Variable Name is defined as AnalogValue_ui1_property. For example, a set temperature of an air conditioner is applied to this control pattern. Further, in the case of a pattern in which devices are controlled using positive and negative integers, Variable Name is defined as AnalogValue_i1_property. For example, an outdoor temperature or the like is applied to this control pattern. In addition, in the case of a pattern in which one piece of data is selected from a plurality of options and the device is controlled, Variable Name is defined as DataList_property. For example, an air conditioner operation mode setting or the like applies to this control pattern. The control described here includes not only controlling the device but also referring to the state of the device. For the character string to be entered in “Property”, enter the name of the ECHONET property. For example, when the name of the ECHONET property in the operation state is Status, Variable Name is described as “Switch_Status”.

  Next, the action for controlling the device, the action for referring to the state, and its argument are defined for the defined Variable Name.

  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”. As an example, there are actions “SetSwitch”, “SetAnalogValue_ui1”, “SetAnalogValue_i1”, and “SetDataList”. Then, naming conventions for Argument and relatedStateVariable, which are arguments necessary for controlling the device, are defined. The naming convention of Argument is that New is a prefix of “control pattern name and property”. For example, if the name of the pattern for controlling the device is Switch, it is NewSwitch_property. In the case of a pattern for controlling other devices, “NewAnalogValue_ui1_property”, “NewAnalogValue_i1_property”, and “NewDataList_property”, respectively. For the character string to be entered in “property”, enter the ECHONET property name. Taking the operating state as an example, since property is Status, Argument is NewSwitch_Status. The relatedStateVariable naming convention is described by the combination of the name of the pattern that controls the device and the ECHONET property name, just like Variable Name.

  Next, as a naming rule for actions when referring to the device status, Get is a prefix of “name of pattern to be controlled”. As an example, there are actions “GetSwitch”, “GetAnalogValue_ui1”, “GetAnalogValue_i1”, and “GetDataList”. Then, naming conventions for Argument and relatedStateVariable, which are arguments necessary for controlling the device, are defined. The naming convention of Argument is that Current is a prefix of “control pattern name and property”. For example, when the name of the pattern for controlling the device is Switch, CurrentSwitch_property. In the case of a pattern for controlling other devices, “CurrentAnalogValue_ui1_property”, “CurrentAnalogValue_i1_property”, and “CurrentDataList_property”, respectively. For the character string to be entered in “property”, enter the ECHONET property name. Taking the operation state as an example, since property is Status, Argument is CurrentSwitch_Status. The relatedStateVariable naming convention rule is described by the combination of the name of the pattern that controls the device and the ECHONET property name, just like Variable Name.

  As described above, in the gateway device 11 according to the first embodiment, the ECHONET device information and the service information held by the device do not define parameters such as Appliance and property for each individual device. Device templates and service templates common to ECHONET devices can be created.

  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 device information and services held by the device are newly defined in the ECHONET protocol, device information and service information can be disclosed to the UPnP side by automatic mapping.

  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 according to a certain rule, and this certain rule is classified into ECHONET properties. Specified for each property type. Therefore, even when a new device standard is used, the ECHONET property can be mechanically mapped to a service information description that becomes an XML Descritpion simply by classifying the ECHONET property into a property type at the time of standard creation. And mutual connection between terminal devices connected to a communication network based on a heterogeneous protocol can be realized.

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

  FIG. 3 is a configuration diagram illustrating 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 the second embodiment of the present invention.

  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, an event reception processing unit 35, A device control processing unit 36 and a data holding unit 37 are provided.

  When the controller device 14 is connected to the network, the device description detection processing unit 31 transmits discovery request data and receives discovery response data in order to detect a device connected to the network. The discovery response data is passed to 32, and the result analyzed by the device analysis processing unit 32 is received. 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 analysis result of the device analysis processing unit 32.

  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 also holds an XML parser function for analyzing XML.

  The service description detection processing unit 33 can cope with the corresponding device 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. Request and retrieve attributes and services. The acquired public information such as attributes and services is transferred to the service analysis processing unit 34, and the analysis result of the service analysis processing unit 34 is received.

  The service analysis processing unit 34 analyzes the data received from the service description detection processing unit 33, analyzes attributes and services that can be handled by the control target device, and passes the analysis result to the service description detection processing unit 33. For example, this data is created in XML, and the service analysis processing unit 34 also holds an XML parser function for analyzing XML.

  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, and transmits information on the notification data transmission source device and the notification data. Attributes and data values are acquired and passed to the data holding unit 37 described later.

  When controlling a device, the device control processing unit 36 acquires information such as the address of the control target device from the device description detection processing unit 31, and acquires the attribute and data value of the control target device from the service description detection processing unit 33. The control request data is transmitted to the control target device. In addition, when receiving a response from the control target device, the device control processing unit 36 passes the control result to the data holding unit 37.

  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 illustrating 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 the second embodiment of the present invention.

  The controller device 14 shown in FIG. 4 has 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. That is, 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 framework Can be generated. Further, 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 data to the widget set.

  FIG. 16 is a diagram illustrating 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, for example, a screen display corresponding to the ECHONET property type (level type, selection type, switching type, character notation type) as shown in FIGS. And can.

  FIG. 17 is a flowchart showing an operation procedure in the 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 (S1702), and the ECHONET property type associated with the terminal device on the ECHONET side is specified (S1703). Then, screen display is performed using the widget set for each ECHONET property type (S1704).

  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. Thus, it is possible to easily generate a screen for indicating the state of the device and controlling the device on the screen of the device connected to the network of any protocol.

(Embodiment 3)
Hereinafter, Embodiment 3 of the present invention will be described 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 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 from the center server 91 via the Internet 92 and retains the protocol conversion table. Each table held in the unit 28 is updated.

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

  When the gateway apparatus 11 receives the service information data template from the center server 91 via the Internet 92, the service description template holding unit 19 updates the service information data template or adds it as a new service information data template. To do.

  As described above, in the gateway device 11 according to the third embodiment, the protocol conversion table, the device information data template, and the service information even when the types, attributes, and data of devices to be controlled are increased or changed. Interconnection between heterogeneous networks can be realized simply by adding a data template.

  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.

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 is a configuration diagram of the address conversion table. FIG. 9 is a system configuration diagram when connected to a server outside the house. FIG. 10 is an image diagram when an ECHONET device is disclosed to UPnP. FIG. 11 is a diagram illustrating an example of ECHONET property types classified in the gateway device according to the first embodiment. FIG. 12 is a reference diagram showing the relationship among property type, type classification, object, action prefix, and datatype for classification and naming rules by ECHONET property type. FIG. 13 is a diagram illustrating an example of a format of a device description template held in the device description template holding unit of the gateway device according to the first embodiment. FIG. 14 is a diagram illustrating an example of a format description of a service description template held in the service description template holding unit of the gateway device according to the first embodiment. FIG. 15 is a flowchart illustrating an operation procedure of the gateway device according to the first embodiment. FIG. 16A is a diagram illustrating an example of a level-type screen displayed on the screen display unit of the controller device according to the second embodiment. FIG. 16B 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. 16C 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. 16D 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 illustrating an operation procedure in screen display of the controller device according to the second embodiment.

Explanation of symbols

11 Gateway device 12 Protocol A
13 Protocol B
DESCRIPTION OF SYMBOLS 14 Controller apparatus 15, 16, 17 Terminal 21 Protocol A communication process part 22 Protocol B communication process part 23 Protocol conversion process part 24 Device description creation process part 25 Device description template holding part 26 Service description creation process part 27 Service description template holding part 28 Protocol conversion table holding unit 29 Device configuration management unit 31 Device description detection processing unit 32 Device analysis processing unit 33 Service description detection processing unit 34 Service analysis processing unit 35 Event reception processing unit 36 Device control processing unit 37 Data holding unit 41 Screen display Part 91 Center server 101 Root device 102 Service type

Claims (14)

A gateway device for connecting two or more types of networks including at least different types of first and second protocols,
A template holding unit that holds 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 means for 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;
Template description creation processing means for obtaining the template held by the template holding means and writing terminal device information description by writing information on the terminal device obtained by the obtaining means;
Based on the name of the terminal device, a protocol conversion table holding unit that holds a protocol conversion table that associates an expression format of information corresponding to the terminal device in the first protocol and the second protocol;
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,
A gateway device comprising: communication means capable of transmitting the terminal device information description updated by the template description creation processing means to the control device connected to the network of the second protocol. The gateway device further includes:
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. The template holding unit is a device description template holding unit 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; It is described based on the standard used for the second protocol, and includes a service description template holding unit that holds a service description template in which service information provided by the terminal device is written,
The template 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 according to a prescribed rule, and creates a device information description A service description for acquiring the service description template from the description creation processing unit and the service description template holding unit, and automatically writing the service information acquired by the acquisition unit according to a prescribed rule to create a service information description The gateway device according to claim 1, comprising a creation processing unit. The device information description created by the device description creation processing unit uses the first protocol network system as a root device, the terminal device connected to the first protocol network as an embedded device, and the communication. 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 a means. The gateway device further includes:
Internet connection means for connecting to the Internet and acquiring the protocol conversion table, the device description template, and the service description template corresponding to the terminal device connected to the first protocol from a server device, The gateway device according to claim 3. The service description template holding unit further holds a service description template defined for each property type, which 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 predetermined according to a predetermined rule, and the service description template corresponding to the property type from the service description template holding unit. The gateway apparatus according to claim 3, wherein the service information description is created according to a rule defined for each service description template. The property type includes
(1) Numeric type indicating property value by numerical value (2) Date type holding data indicating date (3) Time type holding time and time (4) Connection to non-numeric relationship or the first protocol Level type that refers to the state of the terminal device (5) Character notation type (6) definition in which the data acquired from the terminal device connected to the first protocol is a character string or the data for controlling the terminal device is a character string By using only one value that is used to control the terminal device connected to the first protocol, the reset type used when resetting a certain state (7) by switching between two values, the first Control the terminal device connected to the protocol or select one of two values from the terminal device (8) Select from among three or more values And at least one of a selection type that controls a terminal device connected to the first protocol or obtains one of three or more values from the terminal device. The gateway device described. The service description template holding unit includes, as the property type for creating the service information description, on / off switching type data, enumerated type data, analog numeric type data, step value type data, and a plurality of attributes. The gateway device according to claim 6, wherein a service description template having at least one of the generated templates as a data value is held. 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,
The device information of the terminal device obtained by checking the connection status of the terminal device connected to the network of the first protocol to be controlled and detecting that the terminal device to be controlled is connected to the network. Device description detection processing means for holding a device information description;
Device analysis processing means for analyzing the device information description;
A service description detection processing means for requesting and acquiring a service information description describing the service information held by the terminal device to be controlled from a terminal device connected to the network of the first protocol;
Service analysis processing means for analyzing the service information description;
By receiving the device information description from the device description detection processing means and receiving the service information description from the service description detection processing means when receiving notification data about the state from the terminal device to be controlled Event reception processing means for analyzing the content of the received notification data;
Communication for acquiring and controlling the device information description from the device description detection processing means and acquiring the service information description from the service description detection processing means in order to control the terminal device to be controlled Device control processing means for creating data;
Data holding means for holding at least the device information description and the service information description of all the terminal devices to be controlled;
Screen display means for displaying a screen for a user to check and control the status of the terminal device from the device information description and the service information description of the terminal device to be controlled. Control device. The screen display means holds a widget set that generates a screen framework for each property type of the service information description, generates a screen framework by applying the widget set to the screen, and the widget set The control device according to claim 9, wherein the screen is generated by writing data included in the service information description in the widget set in accordance with a rule of: A home network system comprising a terminal device connected to a first protocol network, a control device connected to a second protocol network, and a gateway device connecting at least the second protocol network and the first protocol network Because
The gateway device is
A template holding unit that holds 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 means for 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;
Template description creation processing means for obtaining the template held by the template holding means and writing terminal device information description by writing information on the terminal device obtained by the obtaining means;
Based on the name of the terminal device, a protocol conversion table holding unit that holds a protocol conversion table that associates an expression format of information corresponding to the terminal device in the first protocol and the second protocol;
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,
A home network system comprising: communication means capable of transmitting the terminal device information description updated by the template description creation processing means to the control device connected to the network of the second protocol. The template holding unit of the gateway device includes a device information description holding unit that holds a device information description based on a standard used for the second protocol related to device information of the terminal device connected to the network of the first protocol, and A service information description holding unit for holding a service information description based on a standard used for the second protocol related to a 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 executes the template according to a prescribed rule. A device description creation processing unit that describes device information obtained by the obtaining unit and generates a device information description, and creates service information of the terminal device connected to the first protocol from the service information description holding unit. A service description creation processing unit that generates a service information description by automatically describing the service information obtained by the obtaining unit according to a prescribed rule.
The controller is
Screen display means for displaying a screen for the user to confirm and control the state of the terminal device from the device information description and the service information description of the terminal device to be controlled. The home network system according to claim 11. A network connection method for use in a gateway device that connects two or more types of networks including at least different types of first and second protocols,
A template holding step that holds a template that is described based on the standard used for the second protocol and in which information about terminal devices 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 acquiring the template to be held in the template holding step and creating a terminal device information description by writing information on the terminal device acquired in the acquisition step;
Based on the name of the terminal device, 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;
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 used in a gateway device that connects two or more types of networks including at least different types of first and second protocols,
A template holding step that holds a template that is described based on the standard used for the second protocol and in which information about terminal devices 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 acquiring the template to be held in the template holding step and creating a terminal device information description by writing information on the terminal device acquired in the acquisition step;
Based on the name of the terminal device, 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;
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 program for causing a computer to execute 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.

Images