KR20060035177A - Service information update apparatus and method for controlling network using different protocol - Google Patents

Abstract

The present invention relates to an apparatus and method for updating service information of a heterogeneous network control system. In particular, when an environment in which different standards of a network exist simultaneously in a home is constructed, an IP standard-based network can control a network of another standard. The purpose is to generate information about devices of the specification. The present invention for this purpose is a home network system in which both the UPnP network 110 and NonUPnP network 120, the control point 111 is connected to the UPnP network 110 to control the UPnP and NonUPnP devices, Device XML information and service using the service XML DB means for storing the XML information of the NonUPnP device input by the user and the device information of the second communication standard input by the user on the user interface screen for generating the XML information for the NonUPnP device. Write XML information and store the created XML information in the service XML DB using the manufacturer and product model as a classification key, and extract the XML information of the corresponding device from the service XML DB as the user selects a NonUPnP device. 111 is transmitted between the control point 111 and the NonUPnP device. And a UPnP-NonUPnP bridge device 130 for converting the data into data of a mutually recognizable standard.

Description

SERVICE INFORMATION UPDATE APPARATUS AND METHOD FOR CONTROLLING NETWORK USING DIFFERENT PROTOCOL}

1 is a block diagram of a home network system in an embodiment of the present invention.

Figure 2 is an exemplary diagram of a user interface screen of the XML information generator in an embodiment of the present invention.

3 is an exemplary diagram of an XML document for device information in an embodiment of the present invention.

4 illustrates an XML document for a device service in the embodiment of the present invention.

5 is a block diagram of a home network control system to which an embodiment of the present invention is applied.

6 is an operational flowchart of the specification transmission step in FIG.

7 is an operational flowchart of a new specification transmission step after address release in FIG.

Explanation of symbols on the main parts of the drawings

110: UPnP network 111: control point (CP)

120: LnCP network 121-127,200: LnCP device

130: LnCP-UPnP bridge device 210: the user interface screen

220: service XML DB

The present invention relates to home networking technology, and more particularly, to an apparatus and method for updating service information of a heterogeneous network control system.

UPnP ^RM Device Architecture 1.0 is based on a distributed and open networking architecture that uses IP technology to enable each consumer appliance in the home network to be peerless to peer networking instead of centrally managed.

The UPnP network consists of a control point (CP) that controls the device and a device that provides a service.

The user can find (discovery, description), control (control) and receive events through the interface provided by the control point (CP).

The UPnP device describes its service description in the form of XML (eXtensible Markup Language) at the time of operation, and provides the user with an interface according to the device by UPnP control point (CP) interpreting the device after discovery.

On the other hand, home appliances such as refrigerators, washing machines, microwave ovens, and the like, lamps, gas alarms, stands, boilers, etc. generally employs a relatively low-performance microcomputer of 8Bit or less.

In a network consisting of these products, small data transmissions such as remote control and operation status monitoring are the main communication targets. Therefore, unlike a network consisting of a personal computer (PC) or multimedia products, A protocol is needed to communicate using resources.

LG Electronics has developed LnCP (Living Network Control Protocol) as a protocol for providing Internet services to home appliances installed in homes.

The Living Network Control Protocol (LnCP) defines the method of connecting signal lines, defining control / event messages, and the order of signal flow for communication between products in a home network employing a relatively low-cost microcomputer. It is a communication standard to provide.

In general, LnCP-based networks support power line-based communication for white appliances in the home.

Therefore, if the UPnP network and the LnCP network exist simultaneously, the UPnP Control Point (CP) can control the Non-UPnP device by being located at the boundary between the IP-based UPnP device and the LnCP protocol-based Non-UPnP device. UPnP-Non UPnP bridge devices that provide bridge services are included.

In addition, Home Network Control Protocol (HnCP) has been proposed as a home network technical standard. The HNCP standard defines the command system and communication protocols for peripherals for consumer electronics with power line communication.

However, in the related art, when a plurality of devices are connected to one network, one communication standard must be supported for data transmission and reception between each other.

If a device controlled according to a communication standard different from an existing device is connected to a network, there is a problem in that a home network system cannot be integrated into a single network because data transmission and reception through the network are not possible.

Accordingly, the present invention has been made to develop an apparatus and method for updating service information of a heterogeneous network control system in order to improve a conventional problem, which is different from an IP standard based network when an environment in which different standards networks exist simultaneously in a home is constructed. The purpose is to generate information on devices of different standards so as to control a network of standards.

The present invention provides a device of a first communication standard for transmitting and receiving data according to a first communication standard with a home network, and a second communication standard for transmitting and receiving data according to a second communication standard with a home network in order to achieve the above object. A home network system including a device, comprising: a control point (CP) mounted on a device of the first or second communication standard to control a device of the first and second communication standard, and an XML of a device input by a user A service XML DB means for storing information and a device of a second communication standard input by a user on a user interface screen for generating XML information assuming that the control point CP is mounted on a device of a first communication standard. Device XML information and service XML information is created using the information, and the created XML information is classified as a manufacturer and product model. Stored in the service XML DB means, and as the user selects a device of the second communication standard, the service XML DB means extracts XML information of the corresponding device and provides it to the control point (CP) and communicates with the control point. And bridge device means for converting data transmitted between devices of a standard into data of a standard that can be mutually recognized.

The service XML DB means may be at least one or more portable storage media of a USB memory, an optical recording medium, or a flash memory, or a web server existing on the Internet.

In addition, the present invention is a device of the first communication standard that is equipped with a control point (CP) for transmitting and receiving data in accordance with the first communication standard and a home network to achieve the above object and the device in the home network, and the home A bridge that converts data transmitted between a device of a second communication standard that transmits and receives data in accordance with a network and a second communication standard, and between the control point CP and the device of the second communication standard into data of a mutually recognizable standard. A control method of a home network system including device means, the method comprising: displaying a user interface screen to obtain device information of a second communication standard, and based on the device information input from the user interface screen, Modeled as a basic device of the first communication standard and a diva of the second communication standard Modeling the device as an embedded device in a basic device to create XML information, storing the created XML information in a service XML DB means, and XML information about a device of a second communication standard selected by a user. Extracting from the service XML DB means and transmitting to the control point, converting a driving action for the device of the second communication standard transmitted from the control point into a second communication standard and transmitting the device to the device of the second communication standard. And transmitting, and updating the corresponding state variable by checking the driving of the device of the second communication standard and responding to the control point.

In the above, the first communication standard is UPnP, and the second communication standard is LnCP or HnCP.

Hereinafter, the present invention will be described in detail with reference to the drawings.

In the embodiments of the present invention, a detailed description of well-known functions and configurations that may unnecessarily obscure the subject matter of the present invention will be omitted.

In an embodiment of the present invention, information on non-UPnP devices is transmitted to a control point so that an IP-based UPnP control point (CP) can control the non-UPnP device in an environment in which both a UPnP network and a non-UPnP network exist at the same time. The operation to provide will be described. Here, Non-UPnP may be LnCP, HnCP and the like.

Particularly, in the embodiment of the present invention, a service specification of a company manufacturing various white home appliances and home automation equipment to optimally drive UPnP-Non UPnP bridge equipment in an environment in which both UPnP network and NonUPnP network exist simultaneously The operation of implementing an XML information generator for generating XML information optimized for XML will be described.

1 is a block diagram of a network control system according to an exemplary embodiment of the present invention, as shown in FIG. 1, which includes a control point 111, a media server 112, and a media player 113 to support UPnP-based home networking. NonUPnP devices such as the UPnP network 110, the refrigerator 121, the microwave oven 122, the rice cooker 123, the washing machine 124, the air conditioner 125, the kimchi refrigerator 126, and the gas range 127. NonUPnP network 120 that supports NonUPnP-based home networking, including, and UPNP control point 111 to model itself as a UPnP basic device to control NonUPnP devices (121 ~ 127) and the NonUPnP device Models 121 to 127 as an embedded device in the UPnP basic device and convert data transmitted between the NonUPnP devices 121 to 127 and the UPnP control point 111 into data of a corresponding standard (UPnP, NonUPnP). Ha Comprises a UPnP-NonUPnP bridge device 130.

The NonUPnP based network may be a network using a power line communication based protocol.

Referring to the operation and effect of the embodiment of the present invention configured as described above are as follows.

The UPnP-NonUPnP bridge device 130 is located at the boundary between the UPnP network 110 and the NonUPnP network 120 to provide a bridge service so that the UPnP control point 111 can control the NonUPnP devices 121 ˜ 127.

That is, the UPnP-NonUPnP bridge device 130 is located at the boundary between the UPnP control point 111 and NonUPnP devices 121 to 127 equipped with a low specification microcomputer to provide a bridge service.

Although the UPnP network 110 and the NonUPnP network 120 are divided into separate networks in FIG. 1, in practice, a plurality of devices having different specifications may be connected to one network.

The UPnP-NonUPnP bridge device 130 notifies the UPnP control point 111 by modeling the device type it serves as a UPnP basic device. This applies the UPnP basic device defined in the UPnP Forum to recognize NonUPnP devices as UPnP devices.

That is, XML information defining the UPnP-NonUPnP bridge device 130 as a UPnP basic device can be written as "urn: schemas-upnp-org: device: Basic: 1" 311 of FIG. 3 illustrates an XML document in a case where the NonUPnP network is based on a power line communication protocol called LnCP.

In addition, the UPnP-NonUPnP bridge device 130 models each NonUPnP device 121 to 127 present in the NonUPnP network 120 as an embedded device in the UPnP basic device, and provides the UPnP control point 111 to the UPnP control point 111. do.

XML information defining the NonUPnP device as an embedded device of the UPnP basic device is shown in FIG. 3 as "urn: schemas-upnp-org: device: WasherDrumDevice: 1" 312 and "urn: schemas-upnp-org: device: LightDevice It can be written as: 1 "(313). The contents of 312 and 313 of FIG. 3 exemplify information in which " drum washing machine " and " light " are defined as embedded devices of the UPnP basic device.

In addition, the UPnP-NonUPnP bridge device 130 specifies its existence as a UPnP basic device, and the type of NonUPnP devices 121 to 127 present in the NonUPnP network 120 in embedded device information therein is shown in FIG. In addition to writing in XML (311 to 313) as well as service information in XML as shown in (411 to 414) of Figure 4 to inform the UPnP control point 111 in the UPnP description step (description) step.

In FIG. 4, reference numerals 411 and 412 denote service state information indicating power on and state variables.

According to the current UPnP device architecture, the UPnP device specifies its device type and service information in the form of the example of FIGS. 3 and 4 and informs the UPnP control point (CP) through the UpnP description step during operation.

Similarly, in the embodiment of the present invention, the UPnP-NonUPnP bridge device 130 may provide the device XML information of FIG. 3 and the service XML information of the NonUPnP device of FIG. 4 to the UPnP control point 111 to drive the system.

To this end, the UPnP-Non UPnP bridge device 130 includes an XML information generator to generate XML information according to a service specification of each manufacturer of the NonUPnP devices 121 to 127 existing in the home.

2 illustrates a user interface of an XML information generator used when a user generates XML information for a NonUPnP device existing in a home.

When the user wants to add a NonUPnP device, the user inputs a device type, a friendly name, a manufacturer, and a model name in the user interface 210.

The XML information input to the user interface 210 is added to the embedded device area in the UPnP-NonUPnP bridge device as shown in FIG. 3. At this time, the service XML information for each NonUPnP device input by the user is stored in the service XML DB 220 using the manufacturer and product model as a record classification key, for example, the product information input by the user.

The service XML DB 220 may be stored in a portable storage medium that can be connected to the UPnP-NonUPnP bridge device 130 or exist in a web server on the Internet to be serviced through a network. The portable storage medium may be a USB memory, a CD, a flash memory, or the like.

Thereafter, the user may extract the corresponding service XML information from the service XML DB 220 using the product information (manufacturer, product model).

If the user selects the lamp, assuming that the lamp of the LG-Light10 model of LG Electronics is installed in the home, the service XML information provided by the model extracted from the service XML DB 220 is illustrated in the example of FIG. same.

In addition, the UPnP-NonUPnP bridge device 130 provides the device XML information and the service XML information of the NonUPnP device to the UPnP control point 111 to drive the system. It includes the state variable 412 called "DeviceExist" to reflect whether the device is plugged in or out in the NonUPnP network 120.

At this time, the UPnP-NonUPnP bridge device 130 sets the "DeviceExist" state variable to "yes" when receiving an event indicating that the PlugnP is plugged into the network from the NonUPnP device.

Accordingly, the UPnP control point 111 may determine whether to provide an interface of the corresponding NonUPnP device to the user by querying the "DeviceExist" state variable of the embedded device provided by the UPnP-NonUPnP bridge device 130.

Accordingly, when the UPnP-NonUPnP bridge device 130 receives an UPnP action for a specific NonUPnP device from the UPnP control point 111 or receives an event informing a state change from the NonUPnP device, the UPnP-NonUPnP bridge device 130 converts it into a form suitable for the network. It performs a bridge function.

The process is described in more detail as follows.

First, the UPnP-NonUPnP bridge device 130 configures an embedded device for each device type and initially drives it. This includes dynamically reflecting the presence or absence of a NonUPnP device in the NonUPnP network 120 by including a state variable called 'DeviceExist' in the service description of each device.

Thereafter, when the UPnP-NonUPnP bridge device 130 receives a NonUPnP event informing that the UPnP-NonUPnP bridge device is added to the network, the UPnP-NonUPnP bridge device 130 sets and updates the state variable 'DeviceExist' to 'yes'.

At this time, the UPnP-NonUPnP bridge device 130 transmits a status information update event to the UPnP control point 111.

Accordingly, the UPnP control point 111 may determine whether to provide the user with the interface of the embedded device by querying the state variable 'DeviceExist' for each embedded device 121 to 127. For example, if the user sets the power-on for the NonUPnP devices 121 to 127, the UPnP control point 111 may perform the UPnP 'power on' action for the NonUPnP devices 121 to 127 and the UPnP-NonUPnP bridge device 130. To transmit.

At this time, when the UPnP-NonUPnP bridge device 130 receives a UPnP action for a specific embedded device from the UPnP control point 111, the UPnP-NonUPnP bridge device 130 converts the non-UPnP control message into a corresponding NonUPnP device 121 to 127 in the NonUPnP network 120. Perform the transmitting bridge function. For example, the UPnP-NonUPnP bridge device 130 converts the UPnP power on action received from the UPnP control point 111 into a NonUPnP power on action and transmits it to the NonUPnP devices 121 to 127.

When the UPnP-NonUPnP bridge device 130 receives a response to the control message from the NonUPnP devices 121 to 127, the UPnP-NonUPnP bridge device 130 updates the corresponding state variable and converts the UPnP response message to the UPnP action to the UPnP control point 111. Send.

Since the above assumes the power-on of the NonUPnP devices 121 to 127, the UPnP-NonUPnP bridge device 130 updates the state variable "PowerEnabled" with respect to the NonUPnP action response of the NonUPnP devices 121 to 127 and corresponds thereto. The UPnP action response is transmitted to the UPnP control point 111.

If the nonUPnP devices 121 to 127 in the NonUPnP network 120 change their state by a self-control operation such as a remote controller, the nonUPnP devices 121 to 127 transmit a corresponding state change event to the UPnP-NonUPnP bridge device 130.

At this time, if the power-on state is assumed in the above, if the power-off state is changed, the UPnP-NonUPnP bridge device 130 updates the state variable "PowerEnabled" when receiving the NonUPnP event from the NonUPnP devices 121 to 127.

Accordingly, the UPnP-NonUPnP bridge device 130 transmits an event to the UPnP control point 111 indicating that the non-UPnP devices 121 to 127 are powered off to update the state variable "PowerEnabled".

Accordingly, the UPnP-NonUPnP bridge device 130 performs the above operation to operate the NonUPnP devices 121-127 according to the UPnP action and the information of the NonUPnP devices 121-127 present in the NonUPnP network 120. By providing a state to the UPnP control point 111 allows the UPnP control point 111 to control the NonUPnP devices 121 to 127.

Meanwhile, in the present invention, when NonUPnP is assumed to be LnCP, an operation for controlling the LnCP device through the Internet will be described with reference to FIGS. 5 to 7.

In the following description, only LnCP device control will be described.

5 is a block diagram of a home network control system using the Internet for an embodiment of the present invention, as shown therein, an LnCP-UPnP bridge device 510 for providing a LnCP device control service through the Internet, and a home network. An access server (UServer: UPnP Server) 530 that stores specification information of the LnCP-UPnP bridge device 510 in the network and provides the corresponding specification information when a user accesses and authenticates on the web, and address information in the specification information. LnCP-UPnP bridge device 510 to change the domain name (domain name) and to connect to the access server 530, the authentication information is transmitted and stored and then disconnected from the access server 530 The LnCP-UPnP bridge device 510 connects the LnCP-UPnP bridge device 510 to the connection server 530 at the request of the LnCP-UPnP bridge device 510. When connected from the remote device 540 using the domain name-based presentation URL of the identified device, and comprises a home gateway 520 to connect to the corresponding device in the home network.

The LnCP-UPnP bridge device 510 may control a device using a device control protocol (DCP) function 513 for notifying a bridge device to a UPnP device based on the UPnP device architecture 1.0 standard 514 and a domain name. Dynamic domain name service client function 512, and discovery extension function 511 for providing device description information to an external access server 530.

The operation of the system of the embodiment configured as described above will be described with reference to FIGS. 6 and 7.

In FIG. 5, the remote device 540 may be configured as a portable terminal such as a desktop PC, a notebook PC, a PDA, and a mobile communication terminal. In the embodiment of the present invention, a laptop PC will be described.

First, while the LnCP-UPnP bridge device 510 is present in the home network, the LnCP-UPnP bridge device 510 advertises its presence in the discovery phase of the UPnP device architecture 1.0 to perform a discovery interworking function with the access server 530.

At this time, when the URL-based address information in the description information is private address information due to the use of NAT, the LnCP-UPnP bridge device 510 obtains public address information from the NAT module of the home gateway 520 to display the public address information in the specification information. Replace address information with public address information. That is, when the URL-based address information in the specification information is an IP address, especially when the private address information is due to the use of NAT, the LnCP-UPnP bridge device 510 receives public address information (public address) from the NAT module of the home gateway 520. Port number) and change the IP address and port number in the specification information into a domain name for the corresponding device and an authorized port number assigned from the home gateway 520, respectively. Here, the domain name may be provided as a user-friendly name by configuring the device model and an identifier for identifying the home network.

Thereafter, the LnCP-UPnP bridge device 510 establishes a connection to the access server 530 to authenticate based on the authentication information, and then transmits its specification information to the access server 530.

Thereafter, the LnCP-UPnP bridge device 510 transmits the specification information to the access server 530 and releases the connection with the access server 530.

Accordingly, the access server 530 classifies and manages device specification information transmitted from the LnCP-UPnP bridge device 510 based on HomeNetBind table information using the user authentication information as a search key. Here, the homenet bind table includes user authentication information to the server, device authentication information to the server, and device specification information. The homenet bind table is managed using an insert, delete, and retrieve function.

Thereafter, the user accesses the access server 530 using the notebook PC 540 and performs user authentication. At this time, the user authentication information (username) used when accessing the access server 530 is used as a search key of the homenet bind table in the access server 530 so that the LnCP-UPnP bridge device 510 authenticates with the access server 530. It is used to retrieve the device specification information along with the authentication information transmitted when passing through the step.

Subsequently, if the user authentication succeeds, the user checks the presentation URL based on the domain name in the specification information and connects to the corresponding LnCP device in the home network through the corresponding domain name of the device to be controlled currently.

In other words, in the embodiment of the present invention, the LnCP-UPnP bridge device 510 has a client function of dynamic domain name service to generate a domain name in advance, and the access server 530 is the LnCP-UPnP bridge device 510. In order to handle the client functions of the dynamic domain name service, the DNS server function and domain name generation interface are provided directly. However, depending on the implementation, the DNS server function and domain name generation interface provided by the external service may be used.

That is, in the embodiment of the present invention, the networking process between the LnCP-UPnP bridge device 510 and the access server 530 is operated in three stages of description, home network connection, and remote control. In detail, each step is as follows.

The description step is a step in which the LnCP-UPnP bridge device 510 informs the access server 530 of the device specification information. It is confirmed whether or not the UPnP device uses a private address and according to a result of the confirmation. It performs the same operation as the operation flowchart of 6.

When the LnCP-UPnP bridge device 510 uses a private address, the LnCP-UPnP bridge device 510 obtains a public address from the NAT module of the home gateway 520 and converts the address information (IP address, port number) in the specification information. It converts the domain name assigned to the device and converts the port number into the authorized port number obtained from the home gateway 520. At this time, if the home gateway 520 is an UPnP IGD (Internet Gateway Device), the public address is given using the AddPortMapping action. If the home gateway 520 is a general gateway other than the UPnP IGD, the public gateway is given a public address using telnet communication.

The home network connection (HomeNetworkBind) step is the specification of the device corresponding to the home network to which the user belongs based on the HomeNetBind table information that uses the user authentication information as the search key from the specification information provided by the LnCP-UPnP bridge device 510 It is a step of dividing and discovering information. This means that a user remotely located outside the home network accesses the access server 530 using the notebook PC 540 and succeeds in user authentication, thereby inquiring device specification information in the home network classified based on user identification. Means that.

The remote control step is to directly control a device by accessing a corresponding UPnP device in a home network by using a presentation URL based on a domain name in a device specification retrieved remotely.

However, when a service provider provides a home network, the user releases an address in order to alleviate the IPv4 address shortage problem if the user does not use the network connection for a certain period of time.

If the public address used by the home gateway has been assigned a new public address after a certain idle period has been released, the LnCP-UPnP bridge device 510 should inform the DNS server of the changed address. That is, when using the private address of the UPnP device in the home network, the LnCP-UPnP bridge device 510 converts the domain name and the public port value, but if the address is changed to a new address after the address is released, the changed address is changed in the DNS server. The public address should be retransmitted. This will be described with reference to the operation flowchart of FIG. 7.

First, when the public address is released, if the home gateway 520 serving the home network is the UPnP IGD, the newly provided public address value is notified to the LnCP-UPnP bridge device 510 using the UPnP event.

At this time, when the LnCP-UPnP bridge device 510 receives the changed public address value from the home gateway 520 as an event, the LnCP-UPnP bridge device 510 transmits the changed public address value for the domain name registered in the DNS server.

In addition, in the above, when a new public address is allocated after the LnCP-UPnP bridge device 510 is disconnected from the access server 530, only the process of changing the public address value for the domain name in the DNS server has been described. Even when the device specification information in the network is changed, the changed device specification information is transmitted after authentication by connecting to the access server 530.

As described in detail above, the present invention can efficiently drive the UPnP-NonUPnP bridge device by providing an XML information generator to generate XML information optimized for each service specification of a manufacturer and a product for various NonUPnP devices in a home. A network of specifications can be combined into one home network. This achieves the effect of controlling the home network a single way.

In addition, the present invention can flexibly cope with the user environment in the home by updating the XML information on devices and services using the XML information generator even when adding / deleting non-UPnP devices in the home, thereby establishing a network of various communication standards. Even so, IP-based bridge devices can be easily extended.

Claims (10)

A device of a first communication standard for transmitting and receiving data according to a first communication standard with a home network; In the home network system comprising a device of the second communication standard for transmitting and receiving data in accordance with a second communication standard with the home network, A control point (CP) mounted on the device of the first or second communication standard to control the device of the first and second communication standard; A service XML DB means for storing XML information of a device input by a user; Assuming that the control point CP is mounted on the device of the first communication standard, the device XML information and the service XML using the device information of the second communication standard input by the user on the user interface screen for generating the XML information Create the information and store the created XML information in the service XML DB means using the manufacturer and product model as the classification keys, and extract the XML information of the device from the service XML DB means as the user selects the device of the second communication standard. Heterogeneous network characterized in that it comprises a bridge device means for providing to the control point (CP) and converts the data transmitted between the control point and the device of the second communication standard into data of a mutually recognizable standard An apparatus for updating service information of a control system. The method of claim 1 wherein the service XML DB means Apparatus for updating service information of a heterogeneous network control system, characterized in that the portable storage medium. The apparatus of claim 2, wherein the portable storage medium is at least one of a USB memory, an optical recording medium, and a flash memory. The method of claim 1 wherein the service XML DB means Apparatus for updating service information of a heterogeneous network control system, characterized in that the web server existing on the Internet. The apparatus of claim 1, wherein the first communication standard is UPnP. The apparatus of claim 1, wherein the second communication standard is LnCP or HnCP. A device of a first communication standard that transmits and receives data according to a first communication standard with a home network, and includes a control point (CP) for controlling a device in the home network, and transmits and receives data according to a second communication standard with the home network. A control method of a home network system including a device of a second communication standard and bridge device means for converting data transmitted between the control point (CP) and a device of the second communication standard into data of a standard that can be mutually recognized. To Displaying a user interface screen to obtain device information of a second communication standard; Creating device information input from the UI screen as XML information and storing the device information in a service XML DB means; Extracting XML information about a device of a second communication standard selected by a user from the service XML DB means and transmitting the extracted XML information to a control point; Converting a driving action for the device of the second communication standard transmitted from the control point into a second communication standard and transmitting the device to the device of the second communication standard; Confirming the driving of the device of the second communication standard, updating a corresponding state variable, and responding to the control point; and updating the service information of the heterogeneous network control system. The method of claim 7, wherein the XML information creation step Modeling the bridge device means as a basic device of a first communication standard, The service information update method of the heterogeneous network control system, characterized in that the step of modeling the second communication standard device as an embedded device (embedded device) in the basic device. 8. The method as claimed in claim 6 or 7, wherein the first communication standard is UPnP. 8. The method according to claim 6 or 7, wherein the second communication standard is LnCP or HnCP.

Images