Source: https://patents.google.com/patent/US20030158956A1/en
Timestamp: 2018-04-25 18:39:58
Document Index: 138008795

Matched Legal Cases: ['art 220', 'art 221', 'art 222', 'art 220', 'art 221', 'art 222', 'art 223', 'art 221', 'art.\n2', 'art.\n3']

US20030158956A1 - Network device and network device control method - Google Patents
US20030158956A1
US20030158956A1 US10289897 US28989702A US2003158956A1 US 20030158956 A1 US20030158956 A1 US 20030158956A1 US 10289897 US10289897 US 10289897 US 28989702 A US28989702 A US 28989702A US 2003158956 A1 US2003158956 A1 US 2003158956A1
US10289897
US7403982B2 (en )
[0008]FIG. 1 is a drawing showing a network device control system configured with network devices according to an embodiment of the present invention;
[0009]FIG. 2 is a drawing showing a software configuration of a controller and a network device according to an embodiment of the present invention;
[0010]FIG. 3 is a drawing showing information of target service, provided to a controller by a target device according to an embodiment of the present invention;
[0011]FIG. 4 is a drawing showing messages exchanged between the controller and the target device according to an embodiment of the present invention;
[0012]FIG. 5 is a drawing showing a software configuration of the controller according to an embodiment of the present invention and a network device having gateway functions;
[0013]FIG. 6 is a drawing showing device list information of target services provided to the controller by the target device according to an embodiment of the present invention;
[0014]FIG. 7 is a drawing showing device function list information of target services provided to the controller by the target device according to an embodiment of the present invention;
[0015]FIG. 8 is a drawing showing messages exchanged between the controller and the target device according to an embodiment of the present invention; and
[0016]FIG. 9 is a drawing showing a configuration of access URLs of appliances managed by a target GW device according to an embodiment of the present invention.
Hereinafter, an embodiment of the present invention will be described in detail with reference to the accompanying drawings. FIG. 1 shows an example of a network device control system configured with network devices according to the embodiment of the present invention. The reference numeral 100 designates an IP network to which the network devices are connected; 110, a network device (hereinafter referred to as a controller) having a function for controlling other network devices connected to the IP network 100; 120, a digital camera (D-CAM) as an example of network devices of an AV system; and 130, a washer as an example of network devices of a home appliances system. An AV device gateway 140 (hereinafter referred to as an AV device GW) is a network device having gateway functions for networks of an AV device system and has the ability to control digital AV devices connected over 1394IF 143. A home appliance GW 150 is a network device having gateway functions for networks of a home appliance system and has the ability to control home appliances connected over ECHONET 153.
Hereinafter, a description is made of a control method of the present invention and the configuration of the network devices with reference to the drawings. FIG. 2 shows a software configuration of the controller and the network devices according to the present invention. In the drawing, components that have the same function as those of FIG. 1 are identified by the same reference numbers and a description of them is omitted. The reference numeral 100 designates an IP network to which the network devices are connected; 110, a function; an information exchange protocol processing part 220 comprising a message creation/interpretation part 221 that interprets a received message, determines a protocol processing part to pass it to, distributes the message, receives a return value, and returns it to a message transmission source, an device control protocol processing part 222 that interprets a message received from the message creation/interpretation 221, presents parameters to a corresponding function, receives processing results, and returns them to the message creation/interpretation 221, and the device information provision protocol 223; and the network driver 210.
As described above, the controller 110, by message exchange with the target device 120, obtains information such as the functions of the target device, URLs and function names for accessing the functions, and parameters, and controls the target device. Therefore, according to this method, since the controller does not need to know information for controlling the target device in advance and only a message exchange protocol and a data representation format have only to be shared between the controller and the target device, a network device control system can be built which is flexible to an increase or decrease in network devices and differences of types of devices such as AV devices and home appliances.
[0024]FIG. 5 shows a software configuration of the controller according to an embodiment of the present invention and a network device having gateway functions. In the drawing, components having the same function are identified by the same reference numerals. The reference numeral 100 designates a controller, and 140 designates STB, which is one of network devices having GW functions controlled, hereinafter referred to as a target GW device. The functions of the controller are the same as those in FIG. 2; a description of them is omitted. The target GW device 140 comprises: a target service 240 that provides services for controlling the target device itself and devices under management of the gateway, wherein the target service 240 comprises an device control service 241 that provides an interface for controlling the target GW device itself and devices (141 and 142 in FIG. 1) under management of a gateway, and an device information service 242 that provides information required to control the target GW device itself and devices (141 and 142 in FIG. 1) under management of the gateway; an information exchange protocol processing part 220 comprising a message creation/interpretation part 221 that creates messages according to an information processing protocol and interprets a received message and passes it to a corresponding object, an device control protocol processing part 222 that accesses a corresponding device control service according to a control message received from the device control protocol processing 222, and an device information protocol processing part 223 that accesses an device information acquisition service according to an information request message received from the message creation/interpretation part 221, and acquires and returns device information; a network driver 210; a network 2 driver 520 that sends and receives data through devices under management of the gateway and a second network 143; and a network 2 middleware 510 used in the second network.
Referring to FIGS. 6, 7, and 8, a description is made of the procedure in which the controller according to one embodiment of the present invention collects information about an device to be controlled to control the device.
[0027]FIG. 6 shows an example of device list information, represented by an XML data structure. The device list information contains device information of the network device itself (140) and devices (141, 142) connected to the second network (143). In the drawing, the notation of an enclosure constituted of “<” and “>”, referred to as a tag, denotes the meaning of described information. In this example, <target list> indicates a target device managed by the target GW device 140, <device> indicates isolating physical devices, and <target> indicates an operable function of individual devices. <device name> indicates a name for identifying an device, <device display name> indicates a display name shown to users. The device list information comprises a combination of device information of the device 2 (141) and device 3 (142) connected to the second network (143), acquired or created using the device 2 information 541 and the device 3 information 542 by the device information provision service 240.
[0028]FIG. 7 shows an example of a device function list. In this embodiment, a device function list is provided for each of <target> tags of FIG. 6, and below <function list>, detailed information of each function is given under a <function> tag. As an example of detailed information of functions, there are provided <function name> to indicate a function name, <function type> to indicate whether the operation of the function is control or status inquiry, and <parameter name> to indicate the name of a parameter used, followed by detailed information of the parameter such as <parameter direction> to indicate whether the parameter is an input parameter, output parameter, or input output parameter, and <parameter type> to indicate the type of the parameter. The device function list, like the device list information, is acquired or created and managed using the device 2 information 541 and the device 3 information 542 of the device 2 (141) and device 3 (142) connected to the second network (143) by the device information provision service 240.
[0029]FIG. 8 shows a procedure in which the controller 110 obtains information of the target device 140 and operates a desired target function. Upon detecting the target device 140 on the network, the controller 110 transmits a message to the target device ((1) of FIG. 8), and as a response, obtains information for accessing the device information provision service. If the target device 140 discloses the device information provision service as Web service, the response is a WSDL address for using the device information provision service ((2) of FIG. 8). The controller obtains service provided by the device information provision service 242 and its interface information from WSDL. Service provided here is the same as that shown in FIG. 3 (242). The controller 110 transmits a device list acquisition request, using the device information provision service ((3) of FIG. 8). The device information provision service 242 of the target device refers to created device list information (FIG. 6), creates an device list, including information of devices connected to the second network, and returns a response ((4) of FIG. 8).
The controller transmits ((9) of FIG. 8) getPowerState for consulting a power state to an access destination obtained in (8) of FIG. 8, and from a response, can recognize that the power to the TV is on ((10) of FIG. 8). The function getPowerState transmitted according to a protocol common to the first network is interpreted by the device control protocol 222 and passed to a corresponding control object device 2 control 531 of the device control service 241. The device 2 control converts the function into a protocol interpretable to the device 2 (141) and transmits the resulting function to the device 2 (141). A response from the device 2 (141) is received in the device 2 control 531 and converted into a protocol common to the first network, and passed to the controller through the information exchange protocol 220. That is, the controller can obtain information of devices connected to the second network in the same procedure for devices connected to the second network, to control the devices.
Access URL of devices managed by the target GW device may, as shown in FIG. 9, take a form 620 that follows a directory structure from the IP address 610 of the target GW device, or
a target service part that
creates function information owned by the network device, control information constituted of information for controlling the network device and control function invocation information, function information owned by network devices connected to the second network, and control information constituted of information for controlling the network devices connected to the second network and control function invocation information, in a data format accessible in a message format common to the first network, according to requests of other network devices, provides pertinent device information and pertinent control information without distinguishing between the network device and the network devices connected to the second network, managed by the network device, and converts control functions of network devices connected to the second network, invoked in the message format common to the first network, into a command format known in the second network; and
an information exchange protocol processing part that creates and transmits messages in the message format common to the first network, interprets received messages created in the message format common to the first network, and passes them to the target service part.
2. A network device having a communication interface for connecting to a first network, comprising:
a control part that transmits messages of a message format common to the first network to other network devices, obtains function information owned by the other network devices and control information constituted of information for controlling the other network devices and control function invocation information, and creates and transmits messages for controlling the other network devices, based on the obtained function information and control information, to control the other network devices; and
an information exchange protocol processing part that, according to requests of the control part, creates messages in a message format common to the first network and transmits them to the other network devices, and interprets received messages created in the message format common to the first network and passes them to the control part.
3. A network device having a communication interface for connecting to a first network, comprising:
creates function information owned by the network device, and control information constituted of information for controlling the network device and control function invocation information in a data format accessible in a message format common to the first network, according to requests of other network devices, provides pertinent device information and pertinent control information, and converts control functions invoked in a message format common to the first network into a command format specific to the network device; and
4. The network device according to claim 1, 2, or 3, exchanging messages between the network devices to invoke functions provided by the network devices and obtain information owned by the network devices.
5. The network device according to claim 1, 2, or 3, wherein information of messages exchanged between the network devices is described in XML (Extensible Markup Language) format.
6. The network device according to claim 1, 2, or 3, wherein SOAP (Simple Object Access Protocol) is used for a communication protocol for information of messages exchanged between the network devices.
7. The network device according to claim 1, 2, or 3, wherein functions and arguments of messages exchanged between the network devices are described using WSDL (Web Service Description Language).
8. The network device according to claim 1, 2, or 3, wherein inquiry message transmission and response by multicast messages of UDP (User Datagram Protocol) are used to search for a network device capable of exchanging messages according to a message format common to the first network.
9. The network device according to claim 1, wherein function information owned by network devices connected to the second network, and control information constituted of information for controlling the network devices connected to the second network and control function invocation information are invoked by URL (Uniform Resource Locator) hierarchically formed by a name, function, and the like of the network devices connected to the second network with the IP address of the network device as a root.
10. The network device according to claim 1, wherein function information owned by network devices connected to the second network, and control information constituted of information for controlling the network devices connected to the second network and control function invocation information are invoked using IP addresses virtually assigned to the network devices connected to the second network by the network device.
11. A network device control method used in a network system in which plural network devices are connected to a first network, wherein at least one network device in the network system has gateway functions, is connectable with a second network, and has the function of managing and controlling network devices connected to the second network, the network device:
creates function information owned by the network device, control information constituted of information for controlling the network device and control function invocation information, function information owned by network devices connected to the second network, and control information constituted of information for controlling the network devices connected to the second network and control function invocation information, in a data format accessible in a message format common to the first network, according to requests of other network devices;
according to requests of other network devices, provides pertinent device information and pertinent control information without distinguishing between the network device and the network devices connected to the second network, managed by the network device; and
converts control functions of network devices connected to the second network, invoked in the message format common to the first network, into a command format known in the second network, and transmits control commands produced as a result of the conversion to the network devices connected to the second network to control the network devices connected to the second network.
12. A network device control method used in a network system in which plural network devices are connected to a first network, wherein the network devices have the function of exchanging messages in a message format common to a first network, and network devices having the function of controlling other network devices:
transmit messages of the message format common to the first network to other network devices;
obtain function information owned by the network devices and control information constituted of information for controlling the network devices and control function invocation information;
create messages for controlling the network devices, based on the obtained function information and control information;
and create messages in the message format common to the first network and transmit them to the network devices to control the other network devices.
13. A network device control method used in a network system in which plural first network devices are connected, wherein the network devices:
have the function of exchanging messages in a common message format;
create function information owned by the network devices and control information constituted of information for controlling the network devices and control function invocation information, in a data format accessible in a message format common to a first network;
provide pertinent device information and pertinent control information according to requests of other network devices; and
convert control functions invoked in the message format common to the first network into a command format specific to the network devices to control the network devices.
US10289897 2002-02-15 2002-11-06 Network device and network device control method Active 2024-06-13 US7403982B2 (en)
US20030158956A1 true true US20030158956A1 (en) 2003-08-21
US7403982B2 US7403982B2 (en) 2008-07-22
US8443055B2 (en) 2005-02-18 2013-05-14 Fujitsu Limited System and method to provide device control service, and computer product
US7912928B2 (en) 2011-03-22 grant
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:TANAKA, MAYUKO;KUDO, YOSHIMICHI;OEDA, SHIGETO;AND OTHERS;REEL/FRAME:013476/0798;SIGNING DATES FROM 20020930 TO 20021007