KR101113541B1 - UPnP devices information relay method and system thereof - Google Patents

Abstract

UPnP device information relay method and system are provided. UPnP device information relay system according to the present invention is a RARS (Remote Access Relay Server), RAS (Remote Access Server) to receive the device advertisement information from the UPnP device connected via itself and the LAN to the RARS, and their dynamic IP And a Remote Access Client (RAC) for transmitting the session creation request message containing the information to the RARS and receiving the device advertisement information from the RARS. However, the RARS updates the session information data based on the received session creation request message, inquires the session information of the destination RAC of the device advertisement information received from the RAS in the session information data, and then inquires the Preferably, the device advertisement information is transmitted to the destination RAC using session information.

The present invention can enable interworking between UPnP devices based on UPnP RA architecture for RAC using dynamic IP.

UPnP, RA, RAS, RAC, Share

Description

UPnP devices information relay method and system

The present invention relates to a method and system for relaying UPnP (Universal Plug and Play) device information. More specifically, in relaying information about UPnP devices to RACs based on the technology described in the UPnP RA architecture, even when the RACs have a floating IP that is not fixed, information about the UPnP devices is relayed to the RACs. It relates to a method and a system that can be.

The Universal Plug and Play (UPnP) standard is based on distributed and open networking architectures, enabling each appliance in a home network to be peer to peer networking instead of being centrally managed. The UPnP device models the service as actions and state variables, and the UPnP Control Point can automatically discover the UPnP device and use the service.

According to the UPnP AV architecture established in the UPnP standard, in particular for sharing media content among UPnP devices in the home, the home terminal is a media server that serves as a source for storing and supplying media content, and a media server for playing the media content. It is divided into a media renderer and a control point that controls a media stream between the media server and the media renderer and provides a user interface (UI). This allows the user to play the content stored in the media server on the home network with the media renderer through the user interface manipulation of the control point. For example, by using a WI-FI mobile terminal as a control point, a video stored in a media server PC can be transferred to a media renderer set-top box for viewing on a TV.

UPnP device discovery in accordance with the UPnP standard occurs in a distributed and open networking fashion using IP multicast within the home network. However, since the current IP multicast service cannot be guaranteed to be normally performed in the Internet range, as a result, control of the UPnP device using information obtained through UPnP device discovery is not possible through the Internet. That is, when physically separated from the home network, the home network is inevitably connected through the Internet. Since this is impossible, the UPnP device constituting the home network cannot be controlled from the home network.

In order to solve the above problem, even when the UPnP device or the control point device is physically separated from the home network, the UPnP Remote Access (RA) architecture has been proposed to operate as if it is physically present in the same network. The UPnP RA architecture defines a RAS (Remote Access Server) device in a home network and a RAC (Remote Access Client) device in a remote network.

The UPnP RA architecture allows remote access clients (RACs) located outside the home to access the remote access servers (RAS) located in the home to provide services for UPnP devices located in the home. At this time, UPnP devices located in the home use the Simple Service Discovery Protocol (SSDP) to inform the RAS of its existence and the RAS forwards it to the RAC using a RADASync service action such as AddRemoteDevices (). The RAC converts the information transmitted through the AddRemoteDevices () service action into an SSDP message in the LAN to which the remote terminal belongs and transmits the multicast. Through this process, UPnP devices on the LAN to which the remote terminal belongs can also receive services provided by UPnP devices on the LAN to which the RAS belongs.

1 is a conceptual diagram of the UPnP RA architecture.

According to the UPnP RA architecture, other UPnP devices on the LAN to which the RAC belongs can also receive services provided by UPnP devices on the LAN to which the RAC belongs. In other words, assuming that the LAN to which the RAC belongs is Home A and the LAN to which the RAS belongs to Home B, the UPnP media renderer located in Home A can search and play video content from the media server located in Home B. . That is, by utilizing the RA function, the existing home area can be extended and utilized to the outside.

However, in order for RAS located in Home B to transmit device information such as AddRemoteDevices () to Home A's RAC, it must know the IP address used by Home A's RAC. Typically, devices in a home network are assigned a floating IP from a service provider, so the IP address can change without notice. The UPnP RA Architecture 1.0 standard proposes to use DDNS (Dynamic Domain Name Service) for this purpose, but this causes problems such as subscribing to a separate DDNS service and maintaining a user account for it. In addition, in order to support free content sharing among users, RAS must deliver device information to a plurality of RACs individually, and there is a problem in that the sharing authority setting for each user must be set and operated on the RAS side.

The technical problem to be solved by the present invention is to solve the above-mentioned problems, and in relaying information about UPnP devices to the RAC based on the technology described in the UPnP RA architecture, the floating IP is not fixed to the RAC It is to provide a method and system that can relay information about the UPnP device to the RAC even if it has.

Another technical problem to be solved by the present invention is to provide a method and system for relaying information on a UPnP device to sharers of a predetermined UPnP device based on the technology described in the UPnP RA architecture.

The technical problems of the present invention are not limited to the above-mentioned technical problems, and other technical problems not mentioned will be clearly understood by those skilled in the art from the following description.

The UPnP device information relay system according to an aspect of the present invention for achieving the technical problem is a RARS (Radio Access Relay Server), RAS for receiving device advertisement information from the UPnP device connected via itself and LAN to the RARS ( Remote Access Server) and a RAC (Remote Access Client) for transmitting a session creation request message containing its own dynamic IP information to the RARS and receiving the device advertisement information from the RARS. However, the RARS updates the session information data based on the received session creation request message, inquires the session information of the destination RAC of the device advertisement information received from the RAS in the session information data, and then the Preferably, the device advertisement information is transmitted to the destination RAC using session information.

According to another aspect of the present invention, a UPnP device information relay method includes receiving a session creation request message containing dynamic IP information of a remote access client (RAC) from the RAC, and receiving a regular session creation request message. Updating the session information data based on the step; when the device advertisement information is received from the remote access server (RAS), determining the destination RAC of the device advertisement information; and determining the session information of the determined destination RAC in the session information data. After querying, transmitting the device advertisement information to the destination RAC using the inquired session information.

According to the present invention as described above, based on the technology described in the UPnP RA architecture in relaying information about UPnP devices to the RAC, even if the RAC has a fixed IP, the information about the UPnP devices Since a Remote Aceess Server (RAS) relays to the RAC via the RARS, UPnP devices connected to a local area network (LAN) to which the RAC belongs also are provided by UPnP devices connected to a local area network (LAN) to which the RAS belongs. It is effective to receive services.

In addition, according to the present invention, by managing the data for the sharer Remote Access Client (RAC) that can use each UPnP device to relay information about each UPnP device to the sharer RAC, access to the UPnP device The policy can be applied in various ways, and there is an effect of providing a service (eg, a home-to-home service) based on the access policy.

Advantages and features of the present invention, and methods for achieving them will be apparent with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but can be implemented in various forms. The embodiments of the present invention make the posting of the present invention complete and the general knowledge in the technical field to which the present invention belongs. It is provided to fully convey the scope of the invention to those skilled in the art, and the present invention is defined only by the scope of the claims. Like reference numerals refer to like elements throughout.

Hereinafter, the present invention will be described with reference to a block diagram or a process flow chart for explaining a UPnP device information relay method and system. At this point, it will be understood that each block of the flowchart illustrations and combinations of flowchart illustrations may be performed by computer program instructions. Since these computer program instructions may be mounted on a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, those instructions executed through the processor of the computer or other programmable data processing equipment may be described in flow chart block (s). It creates a means to perform the functions. These computer program instructions may be stored in a computer usable or computer readable memory that can be directed to a computer or other programmable data processing equipment to implement functionality in a particular manner, so that the computer available or computer readable It is also possible for the instructions stored in the memory to produce an article of manufacture containing instruction means for performing the functions described in the flowchart block (s). Computer program instructions may also be mounted on a computer or other programmable data processing equipment, such that a series of operating steps are performed on the computer or other programmable data processing equipment to create a computer-implemented process to generate a computer or other programmable data. Instructions for performing the processing equipment may also provide steps for performing the functions described in the flowchart block (s).

In addition, each block may represent a portion of a module, segment, or code that includes one or more executable instructions for executing a specified logical function (s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of order. For example, the two blocks shown in succession may in fact be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending on the corresponding function.

Hereinafter, a UPnP device information relay system according to an embodiment of the present invention will be described with reference to FIG. 2. As shown in FIG. 2, the UPnP device information relay system according to the present embodiment includes a RARS 102, a RAS 106, and a RAC 100. For convenience of description, FIG. 2 shows one RAC 100 and one RAS 106, but it should be noted that two or more RAC 100 and RAS 106 may be included. The UPnP device information relay system according to the present embodiment may further include a DB server 104 and a UPnP device 108.

The DB server 104 is a device that stores sharing relationship data and session information data, and includes a cache, a read only memory (ROM), a programmable ROM (PROM), and an erasable programmable ROM (EPROM). , Nonvolatile memory devices such as electrically erasable programmable ROM (EEPROM) and flash memory, volatile memory devices such as random access memory (RAM), and hard disk drives (such as hard disk drives). It may be implemented as at least one of the storage media, but is not limited thereto. It should be noted that the DB server 104 may be a separate device from the RARS 102 that is controlled by the RARS 102 and manages the sharing relationship data and session information data, but may be configured inside the RARS 102. do.

2 is a configuration diagram of the UPnP device information relay system according to the present embodiment. The RAS 106 and the UPnP device 108 connected to the home network 110 are located in the home, and the RARS 102 and the DB server 104 are located in addition to the home for the remote access service. The user uses the remote access service through the RAC (100).

The UPnP device 108 refers to a UPnP standard based device connected to the home network 110.

The RAS 106 receives device advertisement information from the UPnP device connected with itself and the LAN, and transmits the device advertisement information to the RARS 102.

The device advertisement information may be transmitted in the form of an alive message of a simple service description protocol (SSDP) in the LAN. Upon receiving the SSDP: alive message, the RAS 106 converts the SSDP: alive message into an AddRemoteAccess message according to the UPnP RA architecture and transmits the message to the RARS 102. When the destination RAC 100 of the device advertisement message is determined, the RARS 102 transmits the device advertisement information in the form of the AddRemoteAccess message to the destination RAC 100.

The device advertisement information may include identification information and access information of the UPnP device 108. The identification information of the UPnP device 108 may be a universally unique identifier (UUID), and the access information may be a URL.

The RAC 100 transmits a session creation request message containing its dynamic IP information to the RARS 102 and receives the device advertisement information from the RARS 102. As mentioned above, the device advertisement information received from the RARS 102 is in the form of AddRemoteAccess. In the session creation request message, device identification information and IP address information of the RAC 100 may be stored.

The RAC 100 may transmit the session creation request message to the RARS 102 upon initialization according to the power-on of the RAC 100. For example, the session creation request message may be transmitted by a program installed in the RAC 100 and automatically executed when the power of the RAC 100 is turned on. When the RARS 102 access signal is input from the user, the RAC 100 may transmit the session creation request message to the RARS 102. For example, when accessing the RARS 102 through the RARS 102 access program, the session creation request message may be transmitted to the RARS 102.

The RAC 100 may use the device identification information and the device access information included in the device advertisement information for the purpose of controlling the device. For example, if the RAC 100 is a mobile phone and the information included in the device advertisement information is information on a UPnP-supported PC installed in the home, the mobile device can view contents stored in the PC installed in the home. have.

On the other hand, the RAC 100 transmits the received device advertisement message to the UPnP device connected to itself and the LAN, so that the UPnP device 108 connected to the LAN can be linked with the UPnP device 108 in the home. can do. In this case, the RAC 100 may convert the received device advertisement message into an alive message format of a simple service discovery protocol (SSDP) and transmit it to a UPnP device connected to itself through a LAN.

The RARS 102 updates the session information data based on the received session creation request message, and inquires the session information of the destination RAC of the device advertisement information received from the RAS 106 in the session information data. The device advertisement information may be transmitted to the destination RAC 100 using the session information. The RARS 102 may identify the RAC 100 using the RAC device identification information stored in the session creation request message, and update the session information for the RAC 100 in the session information data.

An example of session information data is shown in FIG. 3. First, the session information data may be in a form in which the user and the session IP address correspond one-to-one (200). In this case, it is assumed that one user uses one RAC 100. On the other hand, one user may use more than one RAC 100. In this case, even one user may have a different session IP address according to the RAC 100. In this case, the RAC and the session IP address may correspond to one-to-one (220). The RARS 102 may store the session information data itself, or may store and manage the session information data in a separate DB server 104.

By managing the session information data, even when a dynamic IP is assigned to the RAC 100 via a DHCP server, the RAS 106 receives device advertisement information of the UPnP device 108 through the RARS 102 to the destination RAC 100. ) Can be transmitted accurately.

When the RARS 102 receives the device advertisement information from the RAS 106, the RARS 102 identifies the RAS 106 and the UPnP device 108 using information and sender information included in the device advertisement information. can do. In more detail, the UPnP device 108 may be identified using the UUID information of the UPnP device 108 included in the device advertisement information, and the RAS 106 transmits the device advertisement information to the RARS 102. In this case, since the transmission will be performed using the TCP / IP protocol, the RAS 106 may be identified using the ID information of the sender included in the IP packet. The identification operation of the RAS 106 may be performed in advance by an authentication procedure performed between the RARS 102 and the RAS 106.

When the RARS 102 receives the device advertisement information from the RAS 106, the RARS 102 should determine to which RAC 100 the device advertisement information should be delivered. That is, the destination RAC 100 of the device advertisement information should be determined. Hereinafter, the criteria for determining the destination RAC 100 will be described with reference to FIGS. 4 to 6. Data on the criteria for determining the destination RAC 100 (hereinafter, sharing relationship data) may be input through a web page. The web page is a membership module, a module in which a member inputs information about his own RAC (100), RAS (106), UPnP device 108, the member requests to share the device owned by other members, The owner may include a module for inputting whether to approve the request. The UPnP device information relay system according to the present embodiment may further include a web server (not shown) serving the web page. In addition, the sharing relationship data may be stored in the DB server 104. That is, the RARS 102 may determine the destination RAC based on the sharing relationship data stored in the DB server 104.

As a first method of determining the destination RAC 100, there is a method of determining the destination RAC 100 based on sharing relationship data set based on the owner of the RAS 106. That is, the device advertisement information is relayed based on the sharing relationship for each service subscriber.

According to this, the RARS 106 determines the destination RAC 100 of the device advertisement information received from the RAS 106, wherein the destination RAC 100 is the owner of the RAS 106 and the owner of the RAC 100. It can be determined according to the relationship. The sharing relationship data 300 of FIG. 4 is an example of sharing relationship data when the device advertisement information is relayed based on a sharing relationship previously agreed between the owner of the RAS 106 and the owner of the RAC 100.

According to the sharing relationship data 300 of FIG. 4, when device advertisement information is received from the user A-owned RAS 106, the device advertisement information is relayed to the user B, C, and D-owned RAC 100. In addition, when the device advertisement information is received from the user B owned RAS 106, the device advertisement information is relayed only to the user A owned RAC (100). At this time, it should be noted that the destination terminal is all RAC (100) owned by the sharer.

Further, according to some embodiments, the RARS 102 determines the destination RAC 100 of the device advertisement information received from the RAS 106, wherein the destination RAC 100 determines the owner and RAC of the RAS 106. 100 can be determined according to the relationship. The sharing relationship data 320 of FIG. 3 is an example of sharing relationship data when the device advertisement information is relayed based on a sharing relationship previously agreed between the owner of the RAS 106 and the RAC 100.

According to the sharing relationship data 320 of FIG. 4, when device advertisement information is received from the user A-owned RAS 106, the device advertisement information is relayed to RAC # 1, RAC # 2, and RAC # 4. In addition, when the device advertisement information is received from the user C owned RAS 106, the device advertisement information is relayed only to the RAC # 5 (100). That is, the device advertisement information received from the RAS 106 of a specific owner may be set to be relayed to the specific RAC 100.

In short, the relationship between the owner of the RAS 106 and the owner of the RAC 100 and the relationship between the owner of the RAS 106 and the RAC 100 may be a one-to-one relationship or a one-to-one N (N> 2) relationship.

As a second method of determining the destination RAC 100, there is a method of determining the destination RAC 100 based on the sharing relationship data set based on each RAS. That is, since each RAS 106 serves as a gateway for one home network, it is possible to designate to which RAC 100 the UPnP device 108 belonging to a specific home network is provided.

According to this, the RARS 102 determines the destination RAC 100 of the device advertisement information received from the RAS 106, wherein the destination RAC 100 determines the relationship between the RAS 106 and the owner of the RAC 100. Can be determined accordingly. The sharing relationship data 400 of FIG. 5 is an example of sharing relationship data when the device advertisement information is relayed based on a sharing relationship previously agreed between the RAS 106 and the owner of the RAC 100.

According to the sharing relationship data 400 of FIG. 5, for example, when device advertisement information is received from RAS # 1 relaying data of UPnP devices 108 installed in home network # 1, the device advertisement information is transmitted to the user B, C, and the like. It relays to D-owned RAC 100. In addition, when device advertisement information is received from RAS # 2 relaying data of UPnP devices 108 installed in home network # 1, the device advertisement information is relayed only to user A's own RAC 100. At this time, it should be noted that the destination terminal is all RAC (100) owned by the sharer.

Further, according to some embodiments, the RARS 102 determines the destination RAC 100 of the device advertisement information received from the RAS 106, wherein the destination RAC 100 determines the RAS 106 and the RAC 100. ) Can be determined according to the relationship. The sharing relationship data 420 of FIG. 5 is an example of sharing relationship data when the device advertisement information is relayed based on a sharing relationship previously agreed between the RAS 106 and the RAC 100.

According to the sharing relationship data 420 of FIG. 5, when device advertisement information is received from RAS # 1 relaying data of UPnP devices 108 installed in home network # 1, the device advertisement information is converted into RAC # 1, RAC # 2, Relay to RAC # 4. Further, when device advertisement information is received from RAS # 3 relaying data of UPnP devices 108 installed in home network # 3, the device advertisement information is relayed only to RAC # 5. That is, the device advertisement information received from the specific RAS 106 may be set to be relayed to the specific RAC 100.

In short, the relationship between the owner of the RAS 106 and the RAC 100 and the relationship between the RAS 106 and the RAC 100 may be a one-to-one relationship or a one-to-one N (N> 2) relationship.

As a third method of determining the destination RAC 100, there is a method of determining the destination RAC 100 based on sharing relationship data set based on each UPnP device 108. That is, it is possible to designate which RAC 100 to provide the device advertisement information to each UPnP device 108.

According to this, the RARS 102 determines the destination RAC 100 of the device advertisement information received from the RAS 106, wherein the destination RAC 100 determines the owner of the UPnP device 108 and the RAC 100. It can be determined according to the relationship. The sharing relationship data 500 of FIG. 6 is an example of sharing relationship data when the device advertisement information is relayed to the RAC 100 owned by the sharer designated for each UPnP device 108.

Hereinafter, a case where the UPnP device 108 is a network attached storage (NAS) will be described as an example. According to the sharing relationship data 500 of FIG. 6, when device advertisement information for NAS # 1 is received, the device advertisement information is relayed to the RAC 100 owned by users B, C, and D. When the device advertisement information for NAS # 2 is received, the device advertisement information is relayed only to the user A owned RAC 100. Note that the RAS 106 transmitting the device advertisement information is irrelevant.

Further, according to some embodiments, the RARS 102 determines the destination RAC 100 of the device advertisement information received from the RAS 106, wherein the destination RAC 100 determines the UPnP device 108 and the RAC. 100 can be determined according to the relationship. The sharing relationship data 520 of FIG. 6 is an example of sharing relationship data when the device advertisement information is relayed based on a sharing relationship previously agreed between the UPnP device 108 and the RAC 100.

According to the sharing relationship data 520 of FIG. 6, when device advertisement information for NAS # 1 is received, the device advertisement information is relayed to RAC # 1, RAC # 2, and RAC # 4. In addition, when device advertisement information for NAS # 3 is received, the device advertisement information is relayed only to RAC # 5. That is, the device advertisement information for the specific UPnP device 108 may be set to be relayed to the specific RAC 100.

In short, the relationship between the UPnP device 108 and the owner of the RAC 100 and the relationship between the UPnP device 108 and the RAC 100 may be in a one-to-one relationship or a one-to-one N (N> 2) relationship.

Hereinafter, a UPnP device information relay method according to another embodiment of the present invention will be described with reference to FIG. 7.

First, session information data and sharing relationship data for performing UPnP device information relay according to the present embodiment are updated or generated.

In more detail, the session creation request message containing the dynamic IP information of the remote access client (RAC) is received from the RAC, and the session information data is updated based on the session creation request message. In addition, the sharing relationship data which is the data for determining the destination RAC is input.

The sharing relationship data may be input through a web page. More specifically, receiving a signal requesting sharing all UPnP devices of the owner from the share requester, post a message asking the owner whether to allow sharing all UPnP devices, and a signal indicating that the message is allowed to receive In this case, the sharing request data may be updated by adding the sharing requester RAC to the destination RAC list of all the UPnP devices of the owner. In addition, receiving a signal requesting sharing of all UPnP devices connected to the specific RAS of the owner from the share requester, and posts a message asking the other subscribers whether to allow sharing of all UPnP devices connected to the RAS, and with respect to the message If a signal indicating to allow is received, the sharing request data may be updated by adding the sharing requester's RAC to the destination RAC list of all UPnP devices connected to the corresponding RAS. In addition, when receiving a signal requesting the owner to share a specific UPnP device from the share requester, and posts a message asking whether to share the UPnP device to the other subscriber, and receives a signal that means to allow the message The sharing relationship data may be updated by adding the sharing requester's RAC to the destination RAC list of the UPnP device.

Next, when device advertisement information is received from the RAS 106, the destination RAC of the device advertisement information may be determined. In determining the destination RAC, the sharing relationship data is referred to. More specifically, when the UPnP device 108 transmits the SSDP: alive signal to the home network in a multicast manner (S700), the RAS 106 transmits to the RARS 102 through the Internet in the form of an AddRemoteDevices message (S702, S704), the RARS 102 determines the destination RAC with reference to the sharing relationship data (S706), and inquires the determined session information of the destination RAC in the session information data (S708), and then retrieves the inquired session information. The device advertisement information is transmitted to the destination RAC in the form of AddRemoteDevices (S710).

The destination RAC 100 converts the device advertisement message of the AddRemoteDevices type into an SSDP: alive type signal and transmits the same to the home network 110 of the home B 620 to transmit the UPnP device 108 included in the home B 620. ) May operate in conjunction with the UPnP devices 108 included in the home A 600 based on the UPnP RA architecture.

While the present invention has been described in connection with what is presently considered to be practical exemplary embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, You will understand. It is therefore to be understood that the above-described embodiments are illustrative in all aspects and not restrictive.

1 is a conceptual diagram of the UPnP RA architecture.

2 is a block diagram of a UPnP device information relay system according to an embodiment of the present invention.

3 is a configuration example of session information data according to an embodiment of the present invention.

4 is a first structural example of sharing relationship data according to an embodiment of the present invention.

5 is a second configuration example of sharing relationship data according to an embodiment of the present invention.

6 is a third configuration example of sharing relationship data according to an embodiment of the present invention.

7 is a diagram to help understand a UPnP device information relay method according to an embodiment of the present invention.

Claims (20)

Remote Access Relay Server (RARS); A Remote Access Server (RAS) for receiving device advertisement information from a UPnP device connected to itself and a LAN and transmitting it to the RARS; And It includes a Remote Access Client (RAC) for transmitting a session creation request message containing its own dynamic IP information to the RARS, and receives the device advertisement information from the RARS, The RARS updates the session information data based on the received session creation request message, inquires the session information of the destination RAC of the device advertisement information received from the RAS in the session information data, and then inquires about the session information. UPnP device information relay system for transmitting the device advertisement information to the destination RAC by using. The method of claim 1, The RAC, UPnP device information relay system for transmitting the session creation request message to the RARS upon initialization according to the power-on of the RAC. The method of claim 1, The RAC, UPnP device information relay system for transmitting the session creation request message to the RARS when a RARS access signal is input from the user. The method of claim 1, The RARS, Determine a destination RAC of the device advertisement information received from the RAS, And the destination RAC is determined according to at least one of a relationship between an owner of the RAS and an owner of the RAC and a relationship between an owner of the RAS and the RAC. The method of claim 4, wherein UPnP device information relay system of the relationship between the owner of the RAS and the owner of the RAC and the relationship between the owner of the RAS and the RAC. The method of claim 4, wherein UPnP device information relay system of the relationship between the owner of the RAS and the owner of the RAC and the relationship between the owner of the RAS and the RAC is one-to-N (N> 2) relationship. The method of claim 1, The RARS, Determine a destination RAC of the device advertisement information received from the RAS, And the destination RAC is determined according to at least one of a relationship between the RAS and the owner of the RAC and a relationship between the RAS and the RAC. The method of claim 7, wherein UPnP device information relay system of the relationship between the owner of the RAS and the RAC and the relationship between the RAS and the RAC is a one-to-one relationship. The method of claim 7, wherein UPnP device information relay system of the relationship between the RAS and the owner of the RAC and the relationship between the RAS and the RAC is one-to-N (N> 2) relationship. The method of claim 1, The RARS, Determine a destination RAC of the device advertisement information received from the RAS, The destination RAC is determined according to at least one of the relationship between the UPnP device and the owner of the RAC and the relationship between the UPnP device and the RAC. The method of claim 10, The UPnP device information relay system having a one-to-one relationship between the UPnP device and the owner of the RAC and the UPnP device and the RAC. The method of claim 10, The UPnP device information relay system of the relationship between the UPnP device and the owner of the RAC and the relationship between the UPnP device and the RAC has a one-to-one N (N> 2) relationship. The method according to any one of claims 4, 7, and 10, And a web server configured to provide a web page for receiving data on the relationship as a reference for determining the destination RAC. The method according to any one of claims 4, 7, and 10, UPnP device information relay system further comprising a DB server that stores data on the relationship that is the basis of the destination RAC determination. 15. The method of claim 14, The RARS, UPnP device information relay system for determining the destination RAC based on the data stored in the DB server. Receiving, by a Remote Access Relay Server (RARS), a session creation request message containing dynamic IP information of a remote access client (RAC) from the RAC, and updating session information data based on a regular session creation request message; Determining, by the RARS, a destination RAC of the device advertisement information when the device advertisement information is received from a remote access server (RAS); And And the RARS inquires the determined session information of the destination RAC from the session information data, and then transmits the device advertisement information to the destination RAC using the inquired session information. . The method of claim 16, And receiving, by a web server, data that is a criterion for determining the destination RAC through a web page. The method of claim 17, Receiving the data that is the reference for determining the destination RAC, Receiving, by the web server, a signal for requesting sharing of all UPnP devices of a second user from a first user, and posting a message to the second user asking whether to allow sharing of all UPnP devices; And And when the web server receives a signal indicating that the message permits the message, adding the RAC of the first user to a destination RAC list of all UPnP devices owned by the second user. Information relay method. The method of claim 17, Receiving the data that is the reference for determining the destination RAC, Receiving, by the web server, a signal for requesting sharing of a UPnP device connected to a specific RAS from a first user, and posting a message to a second user who owns the RAS, asking whether to allow sharing; And If the web server receives a signal indicating to allow for the message, UPnP device information relay method comprising the step of adding the RAC of the first user to the destination RAC list of all UPnP devices connected to the RAS . The method of claim 17, Receiving the data that is the reference for determining the destination RAC, Receiving, by the web server, a signal for requesting sharing of a specific UPnP device from a first user, and posting a message to a second user asking whether to allow sharing of the UPnP device; And And receiving, by the web server, a signal indicating that the message is allowed to the message, adding the RAC of the first user to a destination RAC list of the corresponding UPnP device.

Images