Method and apparatus for resolving IP address collision in remote access service

US10091048B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10091048-B2
Application numberUS-57813609-A
CountryUS
Kind codeB2
Filing dateOct 13, 2009
Priority dateOct 10, 2008
Publication dateOct 2, 2018
Grant dateOct 2, 2018

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A method is provided for resolving a collision of Internet Protocol (IP) addresses between devices connected to a first server and a second server remotely accessed in a Universal Plug and Play (UPnP) remote access service. The second server receives address information of a network of the first server from the first server. The second server compares address information of a network of the second server with the received address information of the network of the first server, and determines whether a collision has occurred between addresses of the first server and the second server. A collided address is changed when the collision has occurred.

First claim

Opening claim text (preview).

What is claimed is: 1. A method for resolving a collision of Internet Protocol (IP) addresses between devices connected to a first remote access server and a second remote access server in a Universal Plug and Play (UPnP) network, the method comprising: generating, by the first remote access server corresponding to a first network having first IP addresses, a communication remote access transport (RAT) channel connected with the second remote access server; acquiring, by the first remote access server, device description documents (DDDs) for one or more devices of a second network corresponding to the second remote access server; receiving, by the first remote access server, second IP addresses of the second network, from the second remote access server; changing one of the first IP addresses, which is the same as one of the second IP addresses, into a new IP address different from the second IP addresses; and if the one of the first IP addresses exists in a hypertext transfer protocol (HTTP) message, updating a value of a body of the HTTP message or a value of a header of the HTTP message based on the new IP address. 2. The method of claim 1 , wherein the first IP addresses are first subnet addresses of the first network. 3. The method of claim 2 , further comprising: receiving, by the first remote access server, a list of the second IP addresses from the second remote access server. 4. The method of claim 1 , wherein changing the one of the first IP addresses comprises: changing, by an Application Level Gateway (ALG) of the first remote access server, the one of the first IP addresses into the new IP address. 5. The method of claim 1 , wherein the change of the one of the first IP addresses is performed by a Dynamic Host Configuration Protocol (DHCP) server. 6. A first remote access server for resolving a collision of Internet Protocol (IP) addresses between the first remote access server and a second remote access server in a Universal Plug and Play (UPnP) network, the first remote access server comprising: a Remote Access Transport Agent (RATA) configured to generate a communication remote access transport (RAT) channel remotely accessed with the second remote access server; a Remote Access Discovery Agent (RADA) configured to: acquire one or more device description documents (DDDs) of a second network corresponding to the second remote access server, and receive second IP addresses of the second network from the second remote access server; and an Application Level Gateway (ALG) configured to: change one of first IP addresses of a first network corresponding to the first remote access server, which is the same as one of the second IP addresses, into a new IP address different from the second IP addresses, and if the one of the first IP addresses exists in a hypertext transfer protocol (HTTP) message, updating a value of a body of the HTTP message or a value of a header of the HTTP message based on the new IP address. 7. The first remote access server of claim 6 , wherein each of the first IP addresses is a first subnet address of the first network. 8. The first remote access server of claim 7 , wherein the RADA is further configured to receive a list of the second IP addresses from the second remote access server. 9. A first remote access server for resolving a collision of Internet Protocol (IP) addresses between remote access servers in a Universal Plug and Play (UPnP) network, the first remote access server comprising: a Remote Access Transport Agent (RATA) configured to generate a communication remote access transport (RAT) channel remotely accessed with a second remote access server; and a Remote Access Discovery Agent (RADA) configured to: transmit device description documents (DDDs) for one or more devices to the second remote access server using the RAT channel, receive second IP addresses of a second network corresponding to the second remote access server from the second remote access server, and compare first IP addresses of a first network corresponding to the first remote access server with the second IP addresses; and an Application Level Gateway (ALG) configured to: change the first IP addresses, which is the same as one of the second IP addresses, into new IP addresses different from the second IP addresses, and if the one of the first IP addresses exists in a hypertext transfer protocol (HTTP) message, updating a value of a body of the HTTP message or a value of a header of the HTTP message based on the new IP address. 10. The first remote access server of claim 9 , wherein the first IP addresses are first subnet addresses of the first network and the second IP addresses are second subnet addresses of the second network. 11. The first remote access server of claim 10 , wherein the ALG is configured to: compare the first subnet addresses with the second subnet addresses, and change one of the first subnet addresses, which is the same as one of the second subnet addresses, into a new subnet address different from the second subnet addresses. 12. The first remote access server of claim 9 , wherein the first remote access server controls a Dynamic Host Configuration Protocol (DHCP) server to change a subnet address of a device included in the first network.

Assignees

Inventors

Classifications

  • Electricity · mapped topic

  • Electricity · mapped topic

  • for a higher-layer protocol, e.g. for session initiation protocol [SIP] · CPC title

  • for remote control or remote monitoring of applications · CPC title

  • Electricity · mapped topic

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10091048B2 cover?
A method is provided for resolving a collision of Internet Protocol (IP) addresses between devices connected to a first server and a second server remotely accessed in a Universal Plug and Play (UPnP) remote access service. The second server receives address information of a network of the first server from the first server. The second server compares address information of a network of the sec…
Who is the assignee on this patent?
Han Se Hee, Lee Joo Yeol, Jung Dong Shin, and 3 more
What technology area does this patent fall under?
Primary CPC classification H04L29/12424. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Oct 02 2018 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).