| Remote access to local network -> Monitor Keywords |
|
Remote access to local networkRelated Patent Categories: Electrical Computers And Digital Processing Systems: Multicomputer Data Transferring, Remote Data AccessingRemote access to local network description/claimsThe Patent Description & Claims data below is from USPTO Patent Application 20070168458, Remote access to local network. Brief Patent Description - Full Patent Description - Patent Application Claims CROSS REFERENCE TO RELATED APPLICATION [0001] This application claims priority under 35 USC .sctn.119 to International Patent Application No. PCT/IB2006/000066 filed on Jan. 16, 2006. FIELD OF THE INVENTION [0002] The invention relates to a remote access to a local network. The invention relates more specifically to methods, chipsets, mobile devices, remote access devices, software program products and systems enabling a remote access to a local network via a remote access device of the local network. The invention relates equally to a method, a mobile device, a remote access device, a dynamic domain name system service server, a system and a software program product supporting a configuration of a dynamic domain name system service at a remote access device of a local area network. BACKGROUND OF THE INVENTION [0003] Local networks can be established for interconnecting several devices in order to enable an interaction between these devices. [0004] The UPnP.TM. (Universal Plug and Play) technology defines an architecture for pervasive peer-to-peer network connectivity of intelligent appliances, wireless devices, PCs (personal computers), etc. It is designed to bring easy-to-use, flexible, standards-based connectivity to ad-hoc or unmanaged networks at home, in a small business, in public spaces, or attached to the Internet, etc. UPnP.TM. technology provides a distributed, open networking architecture that leverages TCP/IP (Transmission Control Protocol/Internet Protocol) and the Web technologies to enable as well seamless proximity networking as controlling and effecting a data transfer among networked devices. [0005] The UPnP.TM. Device Architecture (UDA) is designed to support zero-configuration, `invisible` networking, and automatic discovery for a breadth of device categories from a wide range of vendors. This means a device can dynamically join a network, obtain an IP address, convey its capabilities, and learn about the presence and capabilities of other devices. [0006] An established local network may also comprise a gateway or another connecting component, which enables a communication with external devices, for instance via the Internet. [0007] All existing gateway functionality is targeted to allow connectivity from within the local network to outside services, for instance web access, services provided by content providers, etc. [0008] The remote access in existing UPnP.TM. and DLNA (Digital Living Network Alliance) forum is targeted on enabling an access to a local network by external devices. The UPnP.TM. Remote Access Task Force is defining how remote devices can access a local network in such a way that they appear to the network devices as if they were a part of the UPnP.TM. local network. The remote access is using VPN (Virtual Private Network) as the underlying technology. [0009] In order to enable a remote access to a local network via the Internet, the local network has to be provided with an IP address. [0010] Shortage of available public IP addresses does not allow all devices to have their own IP address, though. In order to overcome this problem, Internet Service Providers (ISP) dynamically allocate a public IP address from their own address pool to devices that are connected at that time to the Internet. [0011] For enabling a remote access to a local network, an ISP will thus dynamically allocate an IP address to the gateway or another remote access device of the local network. In order to be able to connect to the local network, a remote device must have prior knowledge of the public IP address of the gateway, which is not an easy task in view of the varying IP addresses. [0012] The Dynamic Domain Name System (DynDNS) is a system facilitating this task, as it allows a fixed Internet domain name to be assigned to varying IP addresses. A Dynamic DNS server takes care of the mapping between a Fully Qualified Domain Name (FQDN) and a dynamic IP address. This makes it possible for other sites on the Internet to establish connections to a machine having a dynamic IP address, for example a cable or DSL (Digital Subscriber Line) service where the IP address of the modem is changed by the Internet service provider occasionally, without having to track the IP address themselves. To implement dynamic DNS, it is necessary to set the maximum caching time of the domain to an unusually short period of typically a few minutes. This prevents other sites on the Internet from retaining the old address in their cache, so that they will typically contact the DynDNS server of the domain for each new connection. [0013] When a local network makes use of a DynDNS service, also a remote device trying to access the local network via a gateway is thus not required to know the actual IP address but only the FQDN of the gateway. [0014] In order to use DynDNS in a local network, it is necessary to configure DynDNS parameters in the gateway. Such a configuration has to indicate, for example, which DynDNS server has to be informed about changes in the IP address. [0015] However, there are no conventional generic mechanisms to configure DynDNS parameters in such a gateway. Currently, each service provider offers its own proprietary client that can be used for taking care of the updating. Due to the lack of standards in the DynDNS space, it is rather complicated for an average user to configure his/her home gateway with the DynDNS settings. [0016] The existing IGDs (Internet Gateway Devices) support a service that enables a configuration of a WLAN (Wireless Local Access Network), but it does not include actions for triggering the registration of a local network gateway into an external server or DynDNS service that will allow the gateway to be accessible from outside using public addresses. [0017] The Cable Television Laboratories, Inc., have introduced a new gateway device functionality in their CableHome 1.1 Specification CH-SP-CH1.1-I10-051214, Dec. 14, 2005, which includes an IGD functionality for interacting with UPnP.TM. devices. [0018] Still, also this IGD does not provide a service for initiating the registration in external servers. [0019] Moreover, it does not provide a security mechanism that will allow a device to access the gateway when being at a remote location. SUMMARY OF THE INVENTION [0020] It is an object of the invention to facilitate and improve a remote access to a local network. Continue reading about Remote access to local network... Full patent description for Remote access to local network Brief Patent Description - Full Patent Description - Patent Application Claims Click on the above for other options relating to this Remote access to local network patent application. ### 1. Sign up (takes 30 seconds). 2. Fill in the keywords to be monitored. 3. Each week you receive an email with patent applications related to your keywords. Start now! - Receive info on patent apps like Remote access to local network or other areas of interest. ### Previous Patent Application: Forensics tool for examination and recovery of computer data Next Patent Application: Syndicating surgical data in a healthcare environment Industry Class: Electrical computers and digital processing systems: multicomputer data transferring or plural processor synchronization ### FreshPatents.com Support Thank you for viewing the Remote access to local network patent info. IP-related news and info Results in 0.23368 seconds Other interesting Feshpatents.com categories: Software: Finance , AI , Databases , Development , Document , Navigation , Error 174 |
* Protect your Inventions * US Patent Office filing
PATENT INFO |
|