CA2642027A1 - Embedded dns - Google Patents
Embedded dns Download PDFInfo
- Publication number
- CA2642027A1 CA2642027A1 CA002642027A CA2642027A CA2642027A1 CA 2642027 A1 CA2642027 A1 CA 2642027A1 CA 002642027 A CA002642027 A CA 002642027A CA 2642027 A CA2642027 A CA 2642027A CA 2642027 A1 CA2642027 A1 CA 2642027A1
- Authority
- CA
- Canada
- Prior art keywords
- dns
- remote
- request
- link
- dns server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
Abstract
An embodiment is directed to a method for selectively routing a DNS request in which a DNS request to translate a domain name is received from a local client device. The DNS request is directed to a remote DNS server on a remote network. A link status to the remote network is identified. If the link status indicates that a connection to the remote network is not possible, the DNS
request is routed to a locally embedded DNS server. If the link status indicates that a connection to the remote network is possible, the DNS request is routed to the remote DNS server on the remote network.
request is routed to a locally embedded DNS server. If the link status indicates that a connection to the remote network is possible, the DNS request is routed to the remote DNS server on the remote network.
Description
PATENT APPLICATION
DOCKET NO. CRAD105 EMBEDDED DNS
INVENTOR(S):
Pat Sewall Dave Johnson EMBEDDED DNS
CROSS REFERENCE TO RELATED APPLICATIONS
[0001] This application claims the priority of provisional applications 60/772,783 entitled Embedded DNS Server filed February 13, 2006 and hereby incorporated by reference. Application 60/722,783 is incorporated herein by reference. This application is a continuation in part of application number 10/936,124 entitled Device Cradle filed September 8, 2004.
Application 10/936,124 is incorporated herein by reference.
BACKGROUND
DOCKET NO. CRAD105 EMBEDDED DNS
INVENTOR(S):
Pat Sewall Dave Johnson EMBEDDED DNS
CROSS REFERENCE TO RELATED APPLICATIONS
[0001] This application claims the priority of provisional applications 60/772,783 entitled Embedded DNS Server filed February 13, 2006 and hereby incorporated by reference. Application 60/722,783 is incorporated herein by reference. This application is a continuation in part of application number 10/936,124 entitled Device Cradle filed September 8, 2004.
Application 10/936,124 is incorporated herein by reference.
BACKGROUND
[0002] Domain Name Servers (DNS) translate domain names such as google.com into Internet Protocol (IP) numerical addresses such as 64.233.161.147. DNS servers typically reside on a remote network. When a user of a client computer needs to retrieve content from a remote web server, the user types the domain name in a browser's address bar, and presses the enter key. The client computer sends a request to the DNS
server to return an IP address associated with the domain name. The DNS
server replies with the IP address. Using the IP address, the client computer generates a request for the content from the remote web server. The remote web server returns the content to the client computer. The IP address is temporarily cached by the browser so that when the same domain name is requested in the future, the IP address is already known by the browser, so the browser can make future requests without first having to consult with the DNS server to obtain the IP address.
server to return an IP address associated with the domain name. The DNS
server replies with the IP address. Using the IP address, the client computer generates a request for the content from the remote web server. The remote web server returns the content to the client computer. The IP address is temporarily cached by the browser so that when the same domain name is requested in the future, the IP address is already known by the browser, so the browser can make future requests without first having to consult with the DNS server to obtain the IP address.
[0003] If there is a problem with the network, the translation request to the DNS server will not succeed. Generally, the network status is not available to the client computer, so it is not possible to distinguish between a non-functional network, and a slow response from the DNS server on a functional network. In such cases, browsers typically wait for a period of time and send repeated DNS requests. If the waiting and repeated requests fail to elicit a response from the DNS server in a specified period of time, the browser concludes that something is wrong with the network, times out, and displays an error message.
[0004] Likewise, if the browser is using a cached IP address, and there is a problem with the network, the browser cannot distinguish between a non-functional network and a slow response from the remote web server. In such cases, the browser waits for a period of time to receive a response, before timing out and displaying an error message.
DESCRIPTION OF THE DRAWINGS
DESCRIPTION OF THE DRAWINGS
[0005] Figs. 1 and 2 illustrate an exemplary block diagrams of environments in which embodiments of the present invention can be implemented.
[0006] Fig. 3 is a block diagram showing physical and logical components of a personal hotspot with embedded DNS server according to an embodiment of the present invention.
[0007] Figs. 4-5 are exemplary flow diagram illustrating steps taken in performance of various embodiments of the present invention.
DETAILED DESCRIPTION
DETAILED DESCRIPTION
[0008] INrRODucrIoN: Embodiments of the present invention allow a user to connect to the Internet using a device such as an Internet enabled cellular telephone. Embodiments may be incorporated into a device referred to as a personal hotspot that acts as a router and couples to device capable of internet communication such a cellular telephone. With a personal hotspot, users of computing devices such as lap top computers, desktop computers, and personal digital assistants (PDAs) can access the internet through the data capabilities of the cellular telephone. The combination of the personal hotspot and the Internet enabled cellular telephone can create an internet-connected wireless network anywhere that there is cellular data coverage.
[0009] The user's Internet access is dependent upon an active link between the personal hotspot and an active link between the cellular telephone and the Internet. Typically, a user accesses the Internet using a browser. A conventional browser, when connected to the personal hotspot, cannot efficiently or accurately detect and inform a user of a link fault between the personal hotspot and the cellular telephone or a link fault between the cellular telephone and the Internet. When a browser makes a request to a DNS server for an IP address or to a remote web server for content, the browser typically is not equipped to determine the difference between a slow response and a link fault. A browser typically waits for a period of time and sends repeated DNS or content requests. If the waiting and repeated requests fail to elicit a response from the DNS server or remote web server within a specified period of time, the browser concludes that something is wrong with the network, times out, and displays an error message. Various embodiment embodiments operate to more efficiently inform a user of link faults.
[0010] ENVIRONMENr: Fig. 1 illustrates exemplary environment 1 in which various embodiments of the present invention may be implemented.
Environment 1 includes personal hotspot 10 and client devices 12, 14, and 16 and local link 18. Personal hotspot 10, discussed in more detail later, represents generally any combination of hardware and/or programming capable functioning as a router for exchanging network data between client devices 12, 14, and 16 and the Internet via a data exchanger 20 . Client devices 12, 14, and 16 represent generally any computing devices capable of communicating with personal hotspot 10.
Environment 1 includes personal hotspot 10 and client devices 12, 14, and 16 and local link 18. Personal hotspot 10, discussed in more detail later, represents generally any combination of hardware and/or programming capable functioning as a router for exchanging network data between client devices 12, 14, and 16 and the Internet via a data exchanger 20 . Client devices 12, 14, and 16 represent generally any computing devices capable of communicating with personal hotspot 10.
[0011] Local link 18 interconnects personal hotspot 10 and client devices 12, 14, 16. Local link 18 represents generally a cable, wireless, or remote link via a telecommunication link, an infrared link, a radio frequency link, or any other connector or system that provides electronic communication between devices 10, 12, 14, and 16. The path followed by link 18 between devices 10, 12, 14, and 16 in the schematic view of Fig. 1 represents the logical communication path between these devices, not necessarily the physical path between the devices. Devices 10, 12, 14, and 16 can be connected at any point and the appropriate communication path established logically between the devices.
[0012] Environment 1 also includes data exchanger 20, web sites 22, 24, and 26, Remote DNS server 54, and remote link 30. Data exchanger (20) represents generally and combination of hardware and/or programming that can be utilized by personal hotspot 10 to connect to a remote network such as the Internet. Examples include but are not limited to Internet enabled cellular telephones, DSL modems, and cable modems. Web sites 22, 24, and 26 represent generally any web sites equipped to serve content at the request of a computing device such as client devices 12, 14, and 16.
Remote DNS server 54 represents generally any network service capable of translating domain names into IP addresses on request.
Remote DNS server 54 represents generally any network service capable of translating domain names into IP addresses on request.
[0013] Remote link 30 interconnects data exchanger 20, websites 22, 24, and 26, and Remote DNS server 54. Remote link 30 represents generally any combination of a cable, wireless, or remote connection via a telecommunication link, an infrared link, a radio frequency link, or any other connector or system that provides electronic communication between devices 20, 22, 24, 26, and 28. Remote link 30 may represent an intranet, an Internet, or a combination of both. The path followed by remote link 30 between devices 20, 22, 24, 26, and 28 in the schematic view of Fig. 1 represents the logical communication path between these devices, not necessarily the physical path between the devices. Devices 20, 22, 24, 26, and 28 can be connected to the network at any point and the appropriate communication path established logically between the devices.
[0014] In the embodiment illustrated in environment 1, device link 32 interconnects personal hotspot 10 and data exchanger. Device link 32 represents generally any combination of a cable, wireless, or remote connection via a telecommunication link, an infrared link, a radio frequency link, or any other connector or system that provides electronic communication between devices 10 and 20. As examples, device link 32 may incorporate a physical cable or radio waves carrying Bluetooth communications.
[0015] Looking at Figure 1, remote DNS server 25 and websites 22, 24, and 26 can be said to be located on one or more remote networks with respect to personal hotspot 10. Client devices 12, 14, and 16 can be said to be on a local network with respect to personal hotspot 10. As used through this specification, the terms local and remote are used in this context. In the example of Fig. 1, a component or device that is local is a component or device that is local with respect to the local network of personal hotspot 10.
A component that is remote is a component such as remote DNS server 28 that is remote with respect to personal hotspot 10.
A component that is remote is a component such as remote DNS server 28 that is remote with respect to personal hotspot 10.
[0016] Communication between client devices 12, 14, and 16 and remote devices such as remote DNS server 54 and websites 22, 24, and 26 is dependent upon local link 18, device link 32, and remote link 30. Typically, applications such as browsers operating on client devices 12, 14, and 16 can detect a fault in local link 18 because communication with personal hotspot 10 will not be possible. However, such applications will not be able to identify faults in device link 32 and remote link 30. As will be discussed below with respect to Fig. 3, personal hotspot 10 is configured to identify faults in device link 32 and remote link 30 and to inform client devices 12, 14, and 16 of any such faults.
[0017] Fig. 2 illustrates another exemplary environment 2 in which various embodiments of the present invention may be implemented. In the example of Fig. 2, Data exchanger 20 and personal hotspot 10 are incorporated within the same device. In such a configuration, device link 32 (shown in Fig. 1) is eliminated and replaced with internal connections.
[0018] Viewing the environment 2 in Fig. 2, communications between client devices 12, 14, and 16 and remote devices such as Remote DNS server 54 and websites 22, 24, and 26 is dependent upon local link 18 and remote link 30. Typically, applications such as browsers operating on client devices 12, 14, and 16 can detect a fault in local link 18 because communication with personal hotspot 10 will not be possible. However, such applications will not be able to identify faults in remote link 30. As will be discussed below with respect to Fig. 3, personal hotspot 10 is configured to identify faults in remote link 30 and to inform client devices 12, 14, and 16 of any such faults.
[0019] PERSONAL HorsPor: Fig. 3 is a block diagram illustrating physical and logical components of personal hotspot 10. As described above, personal hotspot 10 represents generally any combination of hardware and/or programming capable of functioning as a router for exchanging network data between client devices and the Internet via a data exchanger such as an Internet enabled cellular telephone, DSL modem, or cable modem.
[0020] In the example of Fig. 3 personal hotspot 10 includes local network interface 42 and data exchanger interface 44. Local network interface 42 represents generally any combination of hardware and/or program instructions capable of supplying a communication interface between personal hotspot 10 and client devices 12, 14, and 16 shown in Figures 1 and 2. Data exchanger interface 44 represents any combination of hardware and/or programming enabling data to be communicated between personal hotspot 10 and a data exchanger 20 shown in Figs 1 and 2. For example, interfaces 42 and 44 may include a transceiver operable to exchange network communications utilizing a wireless protocol such as ultrawideband (UWB), Bluetooth, or 802.11. Alternatively, interfaces 42 and 44 may include physical ports or other physical connection points enabling wired communication.
[0021] Personal hotspot 10 also includes DNS database 48, connector 50, link monitor 52, router 54, activity monitor 56, DNS server 58, and web server 60. DNS database 48 represents generally any memory configured to store DNS translation data, that is, a listing of IP addresses and an associated domain name for each. DNS database 48 may initially contain a set of default IP addresses and corresponding domain names. Later, based on user activity, it may be desirable to add to that default set or to replace certain items in that set.
[0022] Connector 50 represents generally any combination of hardware and/or programming for sending a signal to data exchanger 20 to connect to the Internet. For example, where a data exchanger 20 is a cellular telephone, connector 50 may send a signal causing the cellular telephone to establish a data link to the Internet.
[0023] Router 52 represents generally any combination of hardware and/or programming for routing outbound network communication received through network interface 42 to be transmitted by data exchanger 20 to a remote network. Router 52 is also responsible for routing inbound network communications received from the remote network and directed via network interface 42 to a specified client device 12, 14, or 16. Outbound and inbound network communications, for example can be an IP (internet Protocol) packets directed to a target on a remote network or to a particular network device on the local area network.
[0024] Embedded DNS server 54 represents generally a combination of hardware and/or programming embedded in personal hotspot 10.
Embedded DNS server 54 is responsible for translating domain names into IP addresses. When a user of a client device 12, 14, or 16 desires to retrieve content from a website 22, 24, or 26, the user types the domain name in a browser's address bar, and presses the enter key. The client device 12, 14, or 16 sends a request to embedded DNS server 54 to return an IP address associated with the domain name. Embedded DNS server 54 determines if it is able to translate the domain name. For example, embedded DNS server 54 determines if an IP address associated with the domain name can be found in DNS database 48. If so, embedded DNS
server 54 obtains the associated IP address and returns it to the requesting client device 12, 14, or 16. If a link fault exists and the requested domain name cannot be translated, embedded DNS server returns a local address for personal hotspot 10.
Embedded DNS server 54 is responsible for translating domain names into IP addresses. When a user of a client device 12, 14, or 16 desires to retrieve content from a website 22, 24, or 26, the user types the domain name in a browser's address bar, and presses the enter key. The client device 12, 14, or 16 sends a request to embedded DNS server 54 to return an IP address associated with the domain name. Embedded DNS server 54 determines if it is able to translate the domain name. For example, embedded DNS server 54 determines if an IP address associated with the domain name can be found in DNS database 48. If so, embedded DNS
server 54 obtains the associated IP address and returns it to the requesting client device 12, 14, or 16. If a link fault exists and the requested domain name cannot be translated, embedded DNS server returns a local address for personal hotspot 10.
[0025] In one embodiment, local translation using embedded DNS server 54 occurs only when a link fault exists. In other embodiments remote DNS
server 28 is used only when necessary, that is, when embedded DNS server 58 is not able to translate a particular domain name.
server 28 is used only when necessary, that is, when embedded DNS server 58 is not able to translate a particular domain name.
[0026] Activity monitor 56 represents generally any combination of hardware and/or programming capable of monitor outbound network request activity of client devices 12, 14, and 16. Activity monitor 56 is also responsible for updating DNS database 48 according to the monitored activity. The memory available for DNS database 48 is limited, so DNS database 48 cannot store all the data needed to translate every possible domain name. In fact, DNS
database 48 can only store information for limited number of domain names.
As noted above, personal hotspot may be used to access a wide variety of web sites having domain names not represented in DNS database 48.
Activity monitor 56 is responsible for generating activity data representing information concerning domain names and IP addresses requested by client devices 12, 14, and 16 that are not represented in DNS database 48. For each such domain name or IP address, activity monitor 56 may record the number of times each site has been visited in a given period. This activity information can then be used to update the DNS database 48 to include additional IP addresses and domain names based on user activity. Where memory availability is a concern, the activity information could be used to replace IP addresses and domain names that are not being used or are of an otherwise low priority indicated by user activity.
database 48 can only store information for limited number of domain names.
As noted above, personal hotspot may be used to access a wide variety of web sites having domain names not represented in DNS database 48.
Activity monitor 56 is responsible for generating activity data representing information concerning domain names and IP addresses requested by client devices 12, 14, and 16 that are not represented in DNS database 48. For each such domain name or IP address, activity monitor 56 may record the number of times each site has been visited in a given period. This activity information can then be used to update the DNS database 48 to include additional IP addresses and domain names based on user activity. Where memory availability is a concern, the activity information could be used to replace IP addresses and domain names that are not being used or are of an otherwise low priority indicated by user activity.
[0027] Web server 58 represents generally any combination of hardware and/or programming capable of serving an interface such as a web page to client devices 12, 14, and 16. Such web pages may include error messages, instructions, and various user accessible controls for selecting configuration settings related to the operation of personal hotspot 10.
[0028] Link monitor 60 represents generally any combination of hardware and/or programming capable of identifying a link status for personal hotspot 10. The link status is information that can be used by router 52 to determine the existence of faults in device link 32 and remote link 30. Where a fault exists, router 52 can cause web server 58 to return link fault content to a source of a communication that would otherwise be routed to a remote network. The link fault content, for example, can be a web page containing data identifying the nature of the fault and any instructions for correcting the fault.
[0029] In the Example of Fig. 1, personal hotspot 10 couples to data exchanger 20 via device link 32. Device link 32 may be a wired link utilizing a protocol such as USB or a wireless link utilizing a protocol such as Bluetooth. Personal hotspot 10 and data exchanger 20 negotiate a link according the particular protocol in use. As part of that protocol, the data exchanger 20 identifies itself to personal hotspot 10. In the absence of such an identification, link monitor 60 can determine that a device link fault exists.
[0030] Using the identification information received to establish device link 32, personal hotspot 10 can identify a particular set of commands supported by data exchanger 20. With that information connector 50 can issue a command for data exchanger 20 to connect to the Internet via remote link 30. Data exchanger 20 responds with an indication of a success or failure to connect. Upon receiving a failure to connect response, link monitor 60 can determine that a remote link fault exists. Moreover, data exchangers such as internet enabled cellular telephones are typically aware if they are in a cellular coverage area, and if so, what kind of service is available, including the type of data service. Such devices can also identify when connections drop out. This status information has traditionally been displayed to the user through the cellular telephone's user interface. However, the same status information can be obtained by link monitor 60 via device link 32 to identify the existence of a remote link fault.
[0031] OPERATION: The operation of embodiments of the present invention will now be described with reference to Figs. 4-5. Fig. 4 is an exemplary flow diagram that helps illustrate actions taken by personal hotspot 10 upon receiving a DNS request. Fig. 5 is an exemplary flow diagram that helps illustrate actions taken by personal hotspot 10 upon receiving a request for content.
[0032] Starting with Fig. 4, personal hotspot 10 receives a DNS request directed to a remote DNS server (step 62). A link status is then identified (step 64). A link status is an indication of whether or not a connection can be made between personal hotspot 10 and the Internet. When connection is not possible, a link fault exists. Step 64, for example, may be performed by link monitor 60. In the Example of Fig. 1, a link fault may be a fault in remote link 30 fault or a fault in a device link 32. Based on the identified link status, it is determined whether a connection to the remote DNS server is possible (step 66). If a connection is possible, the DNS request is routed to the remote DNS server (step 68). Based on this outbound activity and previously monitored personal hotspot activity, DNS database 48 may be updated (step 70).
[0033] For example, activity monitor 56 may determine that the domain name provided in the DNS request has been requested before and based on some predetermined criteria can be considered a popular domain with respect to client devices 12, 14, and 16. As such, activity monitor may update DNS database 48 to include that domain name and its corresponding IP address returned from remote DNS server 28. In other words, step 70 may be accomplished based on an evaluation of the domain name in a DNS
request routed in step 68, a translated address returned from remote DNS
server 28, and previously monitored network request activity received from client devices 12, 14, and 16.
request routed in step 68, a translated address returned from remote DNS
server 28, and previously monitored network request activity received from client devices 12, 14, and 16.
[0034] Where, in step 66, it is determined that a connection is not possible, the DNS request is instead routed to a locally embedded DNS server such as embedded DNS server 54 shown in Fig. 3. The locally embedded DNS
server determines whether it is able to translate the domain name in the DNS request. In the Example of Fig. 3, it is determined if that domain named can be found in DNS database 48 (step 72). If found, the locally embedded DNS server returns the IP address associated with the domain name (step 74). If the domain name is not found in step 72, the locally embedded DNS server returns an alternate IP address (step 76). The alternate IP address may, for example, be the local address for personal hotspot 76.
server determines whether it is able to translate the domain name in the DNS request. In the Example of Fig. 3, it is determined if that domain named can be found in DNS database 48 (step 72). If found, the locally embedded DNS server returns the IP address associated with the domain name (step 74). If the domain name is not found in step 72, the locally embedded DNS server returns an alternate IP address (step 76). The alternate IP address may, for example, be the local address for personal hotspot 76.
[0035] In this manner, when a client device 12, 14, or 16 communicates a DNS request, that client device receives a prompt response providing the requested IP address or an alternate IP address even in the presence of a link fault. The client device 12, 14, or 16 need not send repeated DNS
requests that ultimately result in a time-out response.
requests that ultimately result in a time-out response.
[0036] Moving to Fig. 5, personal hotspot receives a request for content (step 78). Step 78, for example, may occur when client device 12, 14, or 16 sends an IP request directed to website 22, 24, or 26. Step 78 may occur after the requesting client device 12, 14, or 16 has received a response to a previous DNS request such as a DNS request communicated in step 62 of Fig. 4. The IP request may instead be for the local address of personal hotspot 10 or that of another of client devices 12, 14, and 16. It is determined if the IP request is for a local address (step 80) and if so the local content is returned (step 82).
[0037] If the IP request is not for a local address, a link status is then identified (step 84). A link status is an indication of whether or not a connection can be made between personal hotspot 10 and the Internet.
When connection is not possible, a link fault exists. Step 84, for example, may be performed by link monitor 60. In the Example of Fig. 1, a link fault may be a fault in remote link 30 or a fault in a device link 32. Based on the determination of step 64, it is determined whether a device link fault exists (step 86). If so, device link fault content is returned (step 88). For example, where link monitor 60 identifies a device link fault, link monitor 60 causes web server 58 to return a web page containing content explaining the fault and providing guidance for correcting the fault. Where data exchanger is a cellular telephone, a device fault may exist when personal hotspot is not physically connected to the cellular telephone or the cellular telephone is turned off. The returned web page may contain information instructing a user to turn on the telephone or establish a connection between the telephone and personal hotspot 10.
When connection is not possible, a link fault exists. Step 84, for example, may be performed by link monitor 60. In the Example of Fig. 1, a link fault may be a fault in remote link 30 or a fault in a device link 32. Based on the determination of step 64, it is determined whether a device link fault exists (step 86). If so, device link fault content is returned (step 88). For example, where link monitor 60 identifies a device link fault, link monitor 60 causes web server 58 to return a web page containing content explaining the fault and providing guidance for correcting the fault. Where data exchanger is a cellular telephone, a device fault may exist when personal hotspot is not physically connected to the cellular telephone or the cellular telephone is turned off. The returned web page may contain information instructing a user to turn on the telephone or establish a connection between the telephone and personal hotspot 10.
[0038] If no device link fault exists, it is determined if a remote link fault exists (Step 90). If so, remote link fault content is returned (step 92). For example, where link monitor 60 identifies a remote link fault, link monitor 60 causes web server 58 to return a web page containing content explaining the fault and providing guidance for correcting the fault. Where data exchanger is a cellular telephone, a remote fault may exist when the cellular telephone is in a non-transmission mode often referred to as "Flight Mode"
allowing the phone to be used during commercial airline flights. A remote fault can also exist when the cellular telephone is out of a coverage area for cellular data service or if the cellular telephone does not have an active data plan. The returned web page may contain information identifying the possible causes of the remote link fault as well as suggested solutions.
allowing the phone to be used during commercial airline flights. A remote fault can also exist when the cellular telephone is out of a coverage area for cellular data service or if the cellular telephone does not have an active data plan. The returned web page may contain information identifying the possible causes of the remote link fault as well as suggested solutions.
[0039] In the absence of a device link fault and remote link fault, the request for content is routed to its intended recipient (step 94). Based on this outbound activity and previously monitored personal hotspot activity, DNS database 48 may be updated (step 70). For example, activity monitor 56 may determine that the IP address provided in the DNS request has been requested before and based on some predetermined criteria can be considered a popular address with respect to client devices 12, 14, and 16.
As such, activity monitor may update DNS database 48 to include that IP
address and its corresponding domain name.
As such, activity monitor may update DNS database 48 to include that IP
address and its corresponding domain name.
[0040] CoNCLusIoN: The schematic diagrams of Figs. 1 and 2 illustrate exemplary environments in which embodiments of the present invention may be implemented. Implementation, however, is not limited to these environments. The diagram of Fig. 3 shows the architecture, functionality, and operation of various embodiments of the present invention. A number of the blocks are defined as programs. Each of those blocks may represent in whole or in part a module, segment, or portion of code that comprises one or more executable instructions to implement the specified logical function(s).
Each block may represent a circuit or a number of interconnected circuits to implement the specified logical function(s).
Each block may represent a circuit or a number of interconnected circuits to implement the specified logical function(s).
[0041] Also, the present invention can be embodied in any computer-readable media for use by or in connection with an instruction execution system such as a computer/processor based system or an ASIC (Application Specific Integrated Circuit) or other system that can fetch or obtain the logic from computer-readable media and execute the instructions contained therein. "Computer-readable media" can be any media that can contain, store, or maintain programs and data for use by or in connection with the instruction execution system. Computer readable media can comprise any one of many physical media such as, for example, electronic, magnetic, optical, electromagnetic, or semiconductor media. More specific examples of suitable computer-readable media include, but are not limited to, a portable magnetic computer diskette such as floppy diskettes or hard drives, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory, or a portable compact disc.
[0042] Although the flow diagrams of Figs. 4-5 show specific orders of execution, the orders of execution may differ from that which is depicted.
For example, the order of execution of two or more blocks may be scrambled relative to the order shown. Also, two or more blocks shown in succession may be executed concurrently or with partial concurrence. All such variations are within the scope of the present invention.
For example, the order of execution of two or more blocks may be scrambled relative to the order shown. Also, two or more blocks shown in succession may be executed concurrently or with partial concurrence. All such variations are within the scope of the present invention.
[0043] The present invention has been shown and described with reference to the foregoing exemplary embodiments. It is to be understood, however, that other forms, details and embodiments may be made without departing from the spirit and scope of the invention that is defined in the following claims.
Claims (30)
1. A method for selectively routing a DNS request, comprising:
receiving a DNS request to translate a domain name, the DNS
request being received from a local client device and directed to a remote DNS server on a remote network;
identifying a link status to the remote network; and if the link status indicates that a connection to the remote network is not possible, routing the DNS request to a locally embedded DNS server.
receiving a DNS request to translate a domain name, the DNS
request being received from a local client device and directed to a remote DNS server on a remote network;
identifying a link status to the remote network; and if the link status indicates that a connection to the remote network is not possible, routing the DNS request to a locally embedded DNS server.
2. The method of Claim 1, further comprising, if the link status indicates that a connection to the remote network is possible, routing the DNS request to the remote DNS server on the remote network
3. The method of Claim 1, further comprising after routing the DNS request to the locally embedded DNS server, determining if the domain name can be translated locally by the embedded DNS server, returning the translated address to the client device if the domain name can be translated locally, and returning an alternate address to the client device if the domain name cannot be translated locally.
4. The method of Claim 3, wherein returning an alternate address comprises returning a local address of a device containing the locally embedded DNS server.
5. The method of Claim 1, further comprising, if the DNS request is routed to the remote DNS server, updating a DNS database utilized by the locally embedded DNS server.
6. The method of Claim 5, wherein updating comprises updating the DNS database based on an evaluation of the domain name in the DNS
request, a translated address returned from the remote DNS server, and previously monitored network request activity received from the client device.
request, a translated address returned from the remote DNS server, and previously monitored network request activity received from the client device.
7. The method of Claim 6, wherein updating comprises updating the DNS database to include information reflective of domain name and the translated address, the updated information being for use by the locally embedded DNS server in translating a DNS request for the domain name.
8. The method of Claim 1, further comprising:
receiving a request for content, the request for content being a request received from the local client device and directed to a translated address on the remote network returned in response to the DNS request;
and if the link status indicates that a connection to the remote network is not possible, returning link fault content to the local client device
receiving a request for content, the request for content being a request received from the local client device and directed to a translated address on the remote network returned in response to the DNS request;
and if the link status indicates that a connection to the remote network is not possible, returning link fault content to the local client device
9. The method of Claim 8, wherein identifying a link status to the remote network comprises determining the existence of a device link fault or a remote link fault.
10. The method of Claim 9, wherein returning link fault content comprises returning device link fault content upon determining a device link fault and returning remote link fault content upon determining the existence of a remote link fault.
11. A computer readable medium having computer executable instructions for:
receiving a DNS request to translate a domain name, the DNS
request being received from a local client device and directed to a remote DNS server on a remote network;
identifying a link status to the remote network; and if the link status indicates that a connection to the remote network is not possible, routing the DNS request to a locally embedded DNS server..
receiving a DNS request to translate a domain name, the DNS
request being received from a local client device and directed to a remote DNS server on a remote network;
identifying a link status to the remote network; and if the link status indicates that a connection to the remote network is not possible, routing the DNS request to a locally embedded DNS server..
12. The medium of Claim 11, having further instructions for routing the DNS request to the remote DNS server on the remote network if the link status indicates that a connection to the remote network is possible.
13. The medium of Claim 11, having further instructions for determining if the domain name can be translated locally by the embedded DNS server, returning the translated address to the client device if the domain name can be translated locally, and returning an alternate address to the client device if the domain name cannot be translated locally.
14. The medium of Claim 13, wherein the instructions for returning an alternate address include instructions for returning a local address of a device containing the locally embedded DNS server.
15. The medium of Claim 11, having further instructions for updating a DNS database utilized by the locally embedded DNS server.
16. The medium of Claim 15, wherein the instructions for updating include instructions for updating the DNS database based on an evaluation of the domain name in the DNS request, a translated address returned from the remote DNS server, and previously monitored network request activity received from the client device.
17. The medium of Claim 16, wherein the instructions for updating include instructions for updating the DNS database to include information reflective of domain name and the translated address, the updated information being for use by the locally embedded DNS server in translating a DNS request for the domain name.
18. The medium of Claim 11, further comprising:
receiving a request for content, the request for content being a request received from the local client device and directed to a translated address on the remote network returned in response to the DNS request;
and if the link status indicates that a connection to the remote network is not possible, returning link fault content to the local client device..
receiving a request for content, the request for content being a request received from the local client device and directed to a translated address on the remote network returned in response to the DNS request;
and if the link status indicates that a connection to the remote network is not possible, returning link fault content to the local client device..
19. The medium of Claim 18, wherein the instructions for identifying a link status to the remote network include instructions for determining the existence of a device link fault or a remote link fault.
20. The medium of Claim 19, wherein the instructions for returning link fault content include instructions for returning device link fault content upon determining a device link fault and returning remote link fault content upon determining the existence of a remote link fault.
21. A system for selectively routing a DNS request, comprising:
a locally embedded DNS server;
a router operable to receive a DNS request to translate a domain name, the DNS request being received from a local client device and directed to a remote DNS server on a remote network; and a link monitor operable to identify a link status between the system and the remote network;
wherein router is operable to route the DNS request to a locally embedded DNS server if the link status indicates that a connection to the remote network is not possible.
a locally embedded DNS server;
a router operable to receive a DNS request to translate a domain name, the DNS request being received from a local client device and directed to a remote DNS server on a remote network; and a link monitor operable to identify a link status between the system and the remote network;
wherein router is operable to route the DNS request to a locally embedded DNS server if the link status indicates that a connection to the remote network is not possible.
22. The system of Claim 21, wherein the locally embedded DNS
server is operable to rout the DNS request to the remote DNS server on the remote network if the link status indicates that a connection to the remote network is possible.
server is operable to rout the DNS request to the remote DNS server on the remote network if the link status indicates that a connection to the remote network is possible.
23. The system of Claim 21, wherein the locally embedded DNS
server is operable to determine if the domain name can be translated locally, to return the translated address to the client device if the domain name can be translated locally, and to return an alternate address to the client device if the domain name cannot be translated locally.
server is operable to determine if the domain name can be translated locally, to return the translated address to the client device if the domain name can be translated locally, and to return an alternate address to the client device if the domain name cannot be translated locally.
24. The system of Claim 23, wherein the locally embedded DNS
server is operable to return the alternate address in the form of a local address of a device containing the locally embedded DNS server.
server is operable to return the alternate address in the form of a local address of a device containing the locally embedded DNS server.
25. The system of Claim 21, wherein the locally embedded DNS
server is operable to translate domain names identified in a DNS database, the system further comprising an activity monitor operable to update the DNS database.
server is operable to translate domain names identified in a DNS database, the system further comprising an activity monitor operable to update the DNS database.
26. The system of Claim 25, wherein the activity monitor is operable to update the DNS database based on an evaluation of the domain name in the DNS request, a translated address returned from the remote DNS server, and previously monitored network request activity received from the client device.
27. The system of Claim 26, wherein the activity monitor is operable to update the DNS database to include information reflective of the domain name received in a DNS request and a translated address returned from the remote DNS server.
28. The system of Claim 21, wherein the router is operable to:
receive a request for content, the request for content being a request received from the local client device and directed to a translated address on the remote network returned in response to a DNS request;
if the link status indicates that a connection to the remote network is not possible, cause link fault content to be returned to the local client device;
and if the link status indicates that a connection to the remote network is possible, route the request for content to the translated address.
receive a request for content, the request for content being a request received from the local client device and directed to a translated address on the remote network returned in response to a DNS request;
if the link status indicates that a connection to the remote network is not possible, cause link fault content to be returned to the local client device;
and if the link status indicates that a connection to the remote network is possible, route the request for content to the translated address.
29. The system of Claim 28, wherein the fault monitor is operable to identify a link status by determining the existence of a device link fault or a remote link fault.
30. The system of Claim 29, wherein the link fault content includes device link fault content when the link status indicates a device link fault, and the link fault content includes remote link fault content when the link status indicates the existence of a remote link fault.
Applications Claiming Priority (5)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US77278306P | 2006-02-13 | 2006-02-13 | |
| US60/772,783 | 2006-02-13 | ||
| US11/673,973 US7962569B2 (en) | 2004-09-08 | 2007-02-12 | Embedded DNS |
| US11/673,973 | 2007-02-12 | ||
| PCT/US2007/062078 WO2007095545A2 (en) | 2006-02-13 | 2007-02-13 | Embedded dns |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA2642027A1 true CA2642027A1 (en) | 2007-08-23 |
Family
ID=38372220
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002642027A Abandoned CA2642027A1 (en) | 2006-02-13 | 2007-02-13 | Embedded dns |
Country Status (4)
| Country | Link |
|---|---|
| US (1) | US7962569B2 (en) |
| EP (1) | EP1999623A2 (en) |
| CA (1) | CA2642027A1 (en) |
| WO (1) | WO2007095545A2 (en) |
Families Citing this family (145)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| AU2003209194A1 (en) | 2002-01-08 | 2003-07-24 | Seven Networks, Inc. | Secure transport for mobile communication network |
| US7917468B2 (en) | 2005-08-01 | 2011-03-29 | Seven Networks, Inc. | Linking of personal information management data |
| US8468126B2 (en) | 2005-08-01 | 2013-06-18 | Seven Networks, Inc. | Publishing data in an information community |
| US7853563B2 (en) | 2005-08-01 | 2010-12-14 | Seven Networks, Inc. | Universal data aggregation |
| US20070254727A1 (en) * | 2004-09-08 | 2007-11-01 | Pat Sewall | Hotspot Power Regulation |
| US9584406B2 (en) * | 2004-09-08 | 2017-02-28 | Cradlepoint, Inc. | Data path switching |
| US9232461B2 (en) | 2004-09-08 | 2016-01-05 | Cradlepoint, Inc. | Hotspot communication limiter |
| US8477639B2 (en) * | 2004-09-08 | 2013-07-02 | Cradlepoint, Inc. | Communicating network status |
| US8249052B2 (en) * | 2004-09-08 | 2012-08-21 | Cradlepoint, Inc. | Automated access of an enhanced command set |
| US9294353B2 (en) | 2004-09-08 | 2016-03-22 | Cradlepoint, Inc. | Configuring a wireless router |
| US9237102B2 (en) | 2004-09-08 | 2016-01-12 | Cradlepoint, Inc. | Selecting a data path |
| US8732808B2 (en) * | 2004-09-08 | 2014-05-20 | Cradlepoint, Inc. | Data plan activation and modification |
| WO2006045102A2 (en) | 2004-10-20 | 2006-04-27 | Seven Networks, Inc. | Method and apparatus for intercepting events in a communication system |
| US7706781B2 (en) | 2004-11-22 | 2010-04-27 | Seven Networks International Oy | Data security in a mobile e-mail service |
| FI117152B (en) | 2004-12-03 | 2006-06-30 | Seven Networks Internat Oy | E-mail service provisioning method for mobile terminal, involves using domain part and further parameters to generate new parameter set in list of setting parameter sets, if provisioning of e-mail service is successful |
| US7752633B1 (en) | 2005-03-14 | 2010-07-06 | Seven Networks, Inc. | Cross-platform event engine |
| US8438633B1 (en) | 2005-04-21 | 2013-05-07 | Seven Networks, Inc. | Flexible real-time inbox access |
| WO2006136660A1 (en) | 2005-06-21 | 2006-12-28 | Seven Networks International Oy | Maintaining an ip connection in a mobile network |
| US7769395B2 (en) | 2006-06-20 | 2010-08-03 | Seven Networks, Inc. | Location-based operations and messaging |
| US8293040B2 (en) | 2006-12-11 | 2012-10-23 | The Curators Of The University Of Missouri | Homogeneous mesoporous nanoenergetic metal oxide composites and fabrication thereof |
| US8644272B2 (en) | 2007-02-12 | 2014-02-04 | Cradlepoint, Inc. | Initiating router functions |
| US9021081B2 (en) | 2007-02-12 | 2015-04-28 | Cradlepoint, Inc. | System and method for collecting individualized network usage data in a personal hotspot wireless network |
| US8693494B2 (en) | 2007-06-01 | 2014-04-08 | Seven Networks, Inc. | Polling |
| US8805425B2 (en) | 2007-06-01 | 2014-08-12 | Seven Networks, Inc. | Integrated messaging |
| US8364181B2 (en) | 2007-12-10 | 2013-01-29 | Seven Networks, Inc. | Electronic-mail filtering for mobile devices |
| US9002828B2 (en) | 2007-12-13 | 2015-04-07 | Seven Networks, Inc. | Predictive content delivery |
| US7949724B1 (en) * | 2007-12-28 | 2011-05-24 | Yahoo! Inc. | Determining attention data using DNS information |
| US8862657B2 (en) | 2008-01-25 | 2014-10-14 | Seven Networks, Inc. | Policy based content service |
| US20090193338A1 (en) | 2008-01-28 | 2009-07-30 | Trevor Fiatal | Reducing network and battery consumption during content delivery and playback |
| US8340634B2 (en) | 2009-01-28 | 2012-12-25 | Headwater Partners I, Llc | Enhanced roaming services and converged carrier networks with device assisted services and a proxy |
| US8275830B2 (en) | 2009-01-28 | 2012-09-25 | Headwater Partners I Llc | Device assisted CDR creation, aggregation, mediation and billing |
| US8391834B2 (en) | 2009-01-28 | 2013-03-05 | Headwater Partners I Llc | Security techniques for device assisted services |
| US8832777B2 (en) | 2009-03-02 | 2014-09-09 | Headwater Partners I Llc | Adapting network policies based on device service processor configuration |
| US8725123B2 (en) | 2008-06-05 | 2014-05-13 | Headwater Partners I Llc | Communications device with secure data path processing agents |
| US8548428B2 (en) | 2009-01-28 | 2013-10-01 | Headwater Partners I Llc | Device group partitions and settlement platform |
| US8924469B2 (en) | 2008-06-05 | 2014-12-30 | Headwater Partners I Llc | Enterprise access control and accounting allocation for access networks |
| US8635335B2 (en) | 2009-01-28 | 2014-01-21 | Headwater Partners I Llc | System and method for wireless network offloading |
| US8924543B2 (en) | 2009-01-28 | 2014-12-30 | Headwater Partners I Llc | Service design center for device assisted services |
| US8406748B2 (en) | 2009-01-28 | 2013-03-26 | Headwater Partners I Llc | Adaptive ambient services |
| US8402111B2 (en) | 2009-01-28 | 2013-03-19 | Headwater Partners I, Llc | Device assisted services install |
| US8023425B2 (en) | 2009-01-28 | 2011-09-20 | Headwater Partners I | Verifiable service billing for intermediate networking devices |
| US8589541B2 (en) | 2009-01-28 | 2013-11-19 | Headwater Partners I Llc | Device-assisted services for protecting network capacity |
| US8346225B2 (en) | 2009-01-28 | 2013-01-01 | Headwater Partners I, Llc | Quality of service for device assisted services |
| US8626115B2 (en) | 2009-01-28 | 2014-01-07 | Headwater Partners I Llc | Wireless network service interfaces |
| US8898293B2 (en) | 2009-01-28 | 2014-11-25 | Headwater Partners I Llc | Service offer set publishing to device agent with on-device service selection |
| US8787947B2 (en) | 2008-06-18 | 2014-07-22 | Seven Networks, Inc. | Application discovery on mobile devices |
| US8078158B2 (en) | 2008-06-26 | 2011-12-13 | Seven Networks, Inc. | Provisioning applications for a mobile device |
| US20100010992A1 (en) * | 2008-07-10 | 2010-01-14 | Morris Robert P | Methods And Systems For Resolving A Location Information To A Network Identifier |
| US20100011048A1 (en) * | 2008-07-10 | 2010-01-14 | Morris Robert P | Methods And Systems For Resolving A Geospatial Query Region To A Network Identifier |
| US20100010975A1 (en) * | 2008-07-10 | 2010-01-14 | Morris Robert P | Methods And Systems For Resolving A Query Region To A Network Identifier |
| US8909759B2 (en) | 2008-10-10 | 2014-12-09 | Seven Networks, Inc. | Bandwidth measurement |
| US20100145963A1 (en) * | 2008-12-04 | 2010-06-10 | Morris Robert P | Methods, Systems, And Computer Program Products For Resolving A Network Identifier Based On A Geospatial Domain Space Harmonized With A Non-Geospatial Domain Space |
| US8300637B1 (en) * | 2009-01-05 | 2012-10-30 | Sprint Communications Company L.P. | Attribute assignment for IP dual stack devices |
| US10237757B2 (en) | 2009-01-28 | 2019-03-19 | Headwater Research Llc | System and method for wireless network offloading |
| US9392462B2 (en) | 2009-01-28 | 2016-07-12 | Headwater Partners I Llc | Mobile end-user device with agent limiting wireless data communication for specified background applications based on a stored policy |
| US10064055B2 (en) | 2009-01-28 | 2018-08-28 | Headwater Research Llc | Security, fraud detection, and fraud mitigation in device-assisted services systems |
| US9755842B2 (en) | 2009-01-28 | 2017-09-05 | Headwater Research Llc | Managing service user discovery and service launch object placement on a device |
| US10715342B2 (en) | 2009-01-28 | 2020-07-14 | Headwater Research Llc | Managing service user discovery and service launch object placement on a device |
| US10248996B2 (en) | 2009-01-28 | 2019-04-02 | Headwater Research Llc | Method for operating a wireless end-user device mobile payment agent |
| US9954975B2 (en) | 2009-01-28 | 2018-04-24 | Headwater Research Llc | Enhanced curfew and protection associated with a device group |
| US9858559B2 (en) | 2009-01-28 | 2018-01-02 | Headwater Research Llc | Network service plan design |
| US8606911B2 (en) | 2009-03-02 | 2013-12-10 | Headwater Partners I Llc | Flow tagging for service policy implementation |
| US9351193B2 (en) | 2009-01-28 | 2016-05-24 | Headwater Partners I Llc | Intermediate networking devices |
| US9578182B2 (en) | 2009-01-28 | 2017-02-21 | Headwater Partners I Llc | Mobile device and service management |
| US10492102B2 (en) | 2009-01-28 | 2019-11-26 | Headwater Research Llc | Intermediate networking devices |
| US10841839B2 (en) | 2009-01-28 | 2020-11-17 | Headwater Research Llc | Security, fraud detection, and fraud mitigation in device-assisted services systems |
| US10057775B2 (en) | 2009-01-28 | 2018-08-21 | Headwater Research Llc | Virtualized policy and charging system |
| US10783581B2 (en) | 2009-01-28 | 2020-09-22 | Headwater Research Llc | Wireless end-user device providing ambient or sponsored services |
| US10798252B2 (en) | 2009-01-28 | 2020-10-06 | Headwater Research Llc | System and method for providing user notifications |
| US9955332B2 (en) | 2009-01-28 | 2018-04-24 | Headwater Research Llc | Method for child wireless device activation to subscriber account of a master wireless device |
| US9270559B2 (en) | 2009-01-28 | 2016-02-23 | Headwater Partners I Llc | Service policy implementation for an end-user device having a control application or a proxy agent for routing an application traffic flow |
| US10779177B2 (en) | 2009-01-28 | 2020-09-15 | Headwater Research Llc | Device group partitions and settlement platform |
| US8793758B2 (en) | 2009-01-28 | 2014-07-29 | Headwater Partners I Llc | Security, fraud detection, and fraud mitigation in device-assisted services systems |
| US9706061B2 (en) | 2009-01-28 | 2017-07-11 | Headwater Partners I Llc | Service design center for device assisted services |
| US9980146B2 (en) | 2009-01-28 | 2018-05-22 | Headwater Research Llc | Communications device with secure data path processing agents |
| US10200541B2 (en) | 2009-01-28 | 2019-02-05 | Headwater Research Llc | Wireless end-user device with divided user space/kernel space traffic policy system |
| US9565707B2 (en) | 2009-01-28 | 2017-02-07 | Headwater Partners I Llc | Wireless end-user device with wireless data attribution to multiple personas |
| US10326800B2 (en) | 2009-01-28 | 2019-06-18 | Headwater Research Llc | Wireless network service interfaces |
| US9572019B2 (en) | 2009-01-28 | 2017-02-14 | Headwater Partners LLC | Service selection set published to device agent with on-device service selection |
| US9253663B2 (en) | 2009-01-28 | 2016-02-02 | Headwater Partners I Llc | Controlling mobile device communications on a roaming network based on device state |
| US9557889B2 (en) | 2009-01-28 | 2017-01-31 | Headwater Partners I Llc | Service plan design, user interfaces, application programming interfaces, and device management |
| US8745191B2 (en) | 2009-01-28 | 2014-06-03 | Headwater Partners I Llc | System and method for providing user notifications |
| US9647918B2 (en) | 2009-01-28 | 2017-05-09 | Headwater Research Llc | Mobile device and method attributing media services network usage to requesting application |
| US10484858B2 (en) | 2009-01-28 | 2019-11-19 | Headwater Research Llc | Enhanced roaming services and converged carrier networks with device assisted services and a proxy |
| US11218854B2 (en) | 2009-01-28 | 2022-01-04 | Headwater Research Llc | Service plan design, user interfaces, application programming interfaces, and device management |
| US8351898B2 (en) | 2009-01-28 | 2013-01-08 | Headwater Partners I Llc | Verifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account |
| US8893009B2 (en) | 2009-01-28 | 2014-11-18 | Headwater Partners I Llc | End user device that secures an association of application to service policy with an application certificate check |
| US10264138B2 (en) | 2009-01-28 | 2019-04-16 | Headwater Research Llc | Mobile device and service management |
| US7933272B2 (en) * | 2009-03-11 | 2011-04-26 | Deep River Systems, Llc | Methods and systems for resolving a first node identifier in a first identifier domain space to a second node identifier in a second identifier domain space |
| US20100250777A1 (en) * | 2009-03-30 | 2010-09-30 | Morris Robert P | Methods, Systems, And Computer Program Products For Resolving A First Source Node Identifier To A Second Source Node Identifier |
| KR101613170B1 (en) * | 2009-10-13 | 2016-04-18 | 삼성전자주식회사 | Apparatus and method for providing access point function in portable communication system |
| US8971209B2 (en) * | 2009-12-04 | 2015-03-03 | Cradlepoint, Inc. | System to configure and manage routers through wireless communication |
| US8406207B2 (en) | 2010-07-02 | 2013-03-26 | At&T Mobility Ii Llc | Digital surveillance |
| WO2012018477A2 (en) | 2010-07-26 | 2012-02-09 | Seven Networks, Inc. | Distributed implementation of dynamic wireless traffic policy |
| WO2012018556A2 (en) | 2010-07-26 | 2012-02-09 | Ari Backholm | Mobile application traffic optimization |
| US8838783B2 (en) | 2010-07-26 | 2014-09-16 | Seven Networks, Inc. | Distributed caching for resource and mobile network traffic management |
| PL3407673T3 (en) | 2010-07-26 | 2020-05-18 | Seven Networks, Llc | Mobile network traffic coordination across multiple applications |
| WO2012060997A2 (en) | 2010-11-01 | 2012-05-10 | Michael Luna | Application and network-based long poll request detection and cacheability assessment therefor |
| US8843153B2 (en) | 2010-11-01 | 2014-09-23 | Seven Networks, Inc. | Mobile traffic categorization and policy for network use optimization while preserving user experience |
| WO2012060995A2 (en) | 2010-11-01 | 2012-05-10 | Michael Luna | Distributed caching in a wireless network of content delivered for a mobile application over a long-held request |
| EP2635973A4 (en) | 2010-11-01 | 2014-01-15 | Seven Networks Inc | Caching adapted for mobile application behavior and network conditions |
| US8484314B2 (en) | 2010-11-01 | 2013-07-09 | Seven Networks, Inc. | Distributed caching in a wireless network of content delivered for a mobile application over a long-held request |
| EP2596658B1 (en) | 2010-11-22 | 2018-05-09 | Seven Networks, LLC | Aligning data transfer to optimize connections established for transmission over a wireless network |
| WO2012071384A2 (en) | 2010-11-22 | 2012-05-31 | Michael Luna | Optimization of resource polling intervals to satisfy mobile device requests |
| GB2501416B (en) * | 2011-01-07 | 2018-03-21 | Seven Networks Llc | System and method for reduction of mobile network traffic used for domain name system (DNS) queries |
| US9949309B2 (en) * | 2011-02-19 | 2018-04-17 | Nomad Spectrum Limited | Methods, computer readable mediums, and apparatuses for providing communication to a mobile device using virtual connections |
| US9154826B2 (en) | 2011-04-06 | 2015-10-06 | Headwater Partners Ii Llc | Distributing content and service launch objects to mobile devices |
| GB2517815A (en) | 2011-04-19 | 2015-03-04 | Seven Networks Inc | Shared resource and virtual resource management in a networked environment |
| GB2504037B (en) | 2011-04-27 | 2014-12-24 | Seven Networks Inc | Mobile device which offloads requests made by a mobile application to a remote entity for conservation of mobile device and network resources |
| US8621075B2 (en) | 2011-04-27 | 2013-12-31 | Seven Metworks, Inc. | Detecting and preserving state for satisfying application requests in a distributed proxy and cache system |
| US20140089503A1 (en) * | 2011-04-29 | 2014-03-27 | Telefonaktiebolaget L M Ericsson (Publ) | Automatic Connection Selection |
| WO2013015995A1 (en) | 2011-07-27 | 2013-01-31 | Seven Networks, Inc. | Automatic generation and distribution of policy information regarding malicious mobile traffic in a wireless network |
| US9203704B2 (en) * | 2011-08-22 | 2015-12-01 | Verizon Patent And Licensing Inc. | Discovering a server device, by a non-DLNA device, within a home network |
| WO2013086225A1 (en) | 2011-12-06 | 2013-06-13 | Seven Networks, Inc. | A mobile device and method to utilize the failover mechanisms for fault tolerance provided for mobile traffic management and network/device resource conservation |
| US8934414B2 (en) | 2011-12-06 | 2015-01-13 | Seven Networks, Inc. | Cellular or WiFi mobile traffic optimization based on public or private network destination |
| WO2013086447A1 (en) | 2011-12-07 | 2013-06-13 | Seven Networks, Inc. | Radio-awareness of mobile device for sending server-side control signals using a wireless network optimized transport protocol |
| EP2788889A4 (en) | 2011-12-07 | 2015-08-12 | Seven Networks Inc | Flexible and dynamic integration schemas of a traffic management system with various network operators for network traffic alleviation |
| US8861354B2 (en) | 2011-12-14 | 2014-10-14 | Seven Networks, Inc. | Hierarchies and categories for management and deployment of policies for distributed wireless traffic optimization |
| WO2013090834A1 (en) | 2011-12-14 | 2013-06-20 | Seven Networks, Inc. | Operation modes for mobile traffic optimization and concurrent management of optimized and non-optimized traffic |
| US20130159511A1 (en) | 2011-12-14 | 2013-06-20 | Seven Networks, Inc. | System and method for generating a report to a network operator by distributing aggregation of data |
| WO2013103988A1 (en) | 2012-01-05 | 2013-07-11 | Seven Networks, Inc. | Detection and management of user interactions with foreground applications on a mobile device in distributed caching |
| US20140059071A1 (en) * | 2012-01-11 | 2014-02-27 | Saguna Networks Ltd. | Methods, circuits, devices, systems and associated computer executable code for providing domain name resolution |
| US9642169B2 (en) * | 2012-01-11 | 2017-05-02 | Saguna Networks Ltd. | Methods, circuits, devices, systems and associated computer executable code for facilitating access to a content source through a wireless mobile network |
| WO2013116856A1 (en) | 2012-02-02 | 2013-08-08 | Seven Networks, Inc. | Dynamic categorization of applications for network access in a mobile network |
| WO2013116852A1 (en) | 2012-02-03 | 2013-08-08 | Seven Networks, Inc. | User as an end point for profiling and optimizing the delivery of content and data in a wireless network |
| US8812695B2 (en) | 2012-04-09 | 2014-08-19 | Seven Networks, Inc. | Method and system for management of a virtual network connection without heartbeat messages |
| US20130268656A1 (en) | 2012-04-10 | 2013-10-10 | Seven Networks, Inc. | Intelligent customer service/call center services enhanced using real-time and historical mobile application and traffic-related statistics collected by a distributed caching system in a mobile network |
| US9444779B2 (en) * | 2012-06-04 | 2016-09-13 | Microsoft Technology Lincensing, LLC | Dynamic and intelligent DNS routing with subzones |
| US8775631B2 (en) | 2012-07-13 | 2014-07-08 | Seven Networks, Inc. | Dynamic bandwidth adjustment for browsing or streaming activity in a wireless network based on prediction of user behavior when interacting with mobile applications |
| US9161258B2 (en) | 2012-10-24 | 2015-10-13 | Seven Networks, Llc | Optimized and selective management of policy deployment to mobile clients in a congested network to prevent further aggravation of network congestion |
| US9818151B2 (en) * | 2012-12-04 | 2017-11-14 | I.D. Systems, Inc. | Remote vehicle rental systems and methods |
| US20140177497A1 (en) | 2012-12-20 | 2014-06-26 | Seven Networks, Inc. | Management of mobile device radio state promotion and demotion |
| US9271238B2 (en) | 2013-01-23 | 2016-02-23 | Seven Networks, Llc | Application or context aware fast dormancy |
| US8874761B2 (en) | 2013-01-25 | 2014-10-28 | Seven Networks, Inc. | Signaling optimization in a wireless network for traffic utilizing proprietary and non-proprietary protocols |
| US8750123B1 (en) | 2013-03-11 | 2014-06-10 | Seven Networks, Inc. | Mobile device equipped with mobile network congestion recognition to make intelligent decisions regarding connecting to an operator network |
| WO2014159862A1 (en) | 2013-03-14 | 2014-10-02 | Headwater Partners I Llc | Automated credential porting for mobile devices |
| US9634935B2 (en) | 2013-04-24 | 2017-04-25 | Secured Connectivity, Llc | Method, name server, and system for directing network traffic utilizing profile records |
| US9065765B2 (en) | 2013-07-22 | 2015-06-23 | Seven Networks, Inc. | Proxy server associated with a mobile carrier for enhancing mobile traffic management in a mobile network |
| US10924452B1 (en) * | 2013-08-30 | 2021-02-16 | Amazon Technologies, Inc. | Auditing IP address assignments |
| US10122630B1 (en) * | 2014-08-15 | 2018-11-06 | F5 Networks, Inc. | Methods for network traffic presteering and devices thereof |
| US10530852B2 (en) * | 2016-05-19 | 2020-01-07 | Level 3 Communications, Llc | Network mapping in content delivery network |
| US10791088B1 (en) | 2016-06-17 | 2020-09-29 | F5 Networks, Inc. | Methods for disaggregating subscribers via DHCP address translation and devices thereof |
| US10826820B2 (en) * | 2017-05-09 | 2020-11-03 | Cisco Technology, Inc. | Routing network traffic based on DNS |
| US11122083B1 (en) | 2017-09-08 | 2021-09-14 | F5 Networks, Inc. | Methods for managing network connections based on DNS data and network policies and devices thereof |
| RU2726879C2 (en) * | 2018-12-28 | 2020-07-16 | Акционерное общество "Лаборатория Касперского" | System and method of connecting secure dns resolution protocol |
Family Cites Families (108)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO1995019030A1 (en) | 1994-01-05 | 1995-07-13 | Pois, Inc. | Apparatus and method for a personal onboard information system |
| US6948070B1 (en) | 1995-02-13 | 2005-09-20 | Intertrust Technologies Corporation | Systems and methods for secure transaction management and electronic rights protection |
| US5594946A (en) | 1995-02-28 | 1997-01-14 | Motorola, Inc. | Method and apparatus for mitigating interference produced by a communication unit in a communication system |
| TW309685B (en) | 1996-12-24 | 1997-07-01 | Yng-Dar Lin | Control method of upstream multi-access of transmission system |
| US6094659A (en) * | 1997-09-26 | 2000-07-25 | 3Com Corporation | Web server for use in a LAN modem |
| US6028848A (en) | 1997-09-26 | 2000-02-22 | 3Com Corporation | Apparatus and methods for use therein for an ISDN LAN modem utilizing internal DNS and DHCP servers for transparent translation of local host names to IP addresses |
| ATE429080T1 (en) | 1997-10-14 | 2009-05-15 | Cypress Semiconductor Corp | DIGITAL RADIO TRANSMITTER |
| US6611861B1 (en) * | 1998-02-27 | 2003-08-26 | Xo Communications, Inc. | Internet hosting and access system and method |
| AU771269B2 (en) | 1998-03-13 | 2004-03-18 | Schlumberger Technology Corporation | Providing secure access to network services |
| US6389462B1 (en) * | 1998-12-16 | 2002-05-14 | Lucent Technologies Inc. | Method and apparatus for transparently directing requests for web objects to proxy caches |
| US6334059B1 (en) | 1999-01-08 | 2001-12-25 | Trueposition, Inc. | Modified transmission method for improving accuracy for e-911 calls |
| JP2000353143A (en) | 1999-04-08 | 2000-12-19 | Seiko Epson Corp | Method and device for retrieving node on network and recording medium recording program for searching node |
| US6609197B1 (en) | 1999-04-22 | 2003-08-19 | 3Com Corporation | Method and system for secure emergency access to network devices |
| US6957255B1 (en) | 1999-06-28 | 2005-10-18 | Amdocs (Israel) Ltd. | Method and apparatus for session reconstruction and accounting involving VoIP calls |
| US6560442B1 (en) | 1999-08-12 | 2003-05-06 | Ericsson Inc. | System and method for profiling the location of mobile radio traffic in a wireless communications network |
| US6735447B1 (en) | 1999-12-08 | 2004-05-11 | Telefonaktiebolaget Lm Ericsson (Publ) | Transmission power control of a mobile station |
| JP3350012B2 (en) | 1999-12-24 | 2002-11-25 | 埼玉日本電気株式会社 | Mobile terminal authentication method |
| US20020025832A1 (en) | 2000-02-18 | 2002-02-28 | Durian Michael B. | Controlling data transmission involving a wireless telephone |
| US6377825B1 (en) | 2000-02-18 | 2002-04-23 | Cellport Systems, Inc. | Hands-free wireless communication in a vehicle |
| JP4068780B2 (en) | 2000-02-24 | 2008-03-26 | 富士通株式会社 | COMMUNICATION STATUS NOTIFICATION DEVICE, COMMUNICATION STATUS DISPLAY DEVICE, COMMUNICATION STATUS NOTIFICATION METHOD, AND MEDIUM CONTAINING COMMUNICATION STATUS NOTIFICATION PROGRAM IN VoIP COMMUNICATION SYSTEM |
| US20030046396A1 (en) | 2000-03-03 | 2003-03-06 | Richter Roger K. | Systems and methods for managing resource utilization in information management environments |
| CA2303000A1 (en) | 2000-03-23 | 2001-09-23 | William M. Snelgrove | Establishing and managing communications over telecommunication networks |
| US7539749B2 (en) | 2000-04-20 | 2009-05-26 | Amdocs (Israel) Ltd. | Method and apparatus for session reconstruction |
| US6975617B2 (en) | 2000-05-03 | 2005-12-13 | Agilent Technologies, Inc. | Network monitoring system with built-in monitoring data gathering |
| US7693976B2 (en) * | 2000-07-11 | 2010-04-06 | Ciena Corporation | Granular management of network resources |
| US7228350B2 (en) * | 2000-08-04 | 2007-06-05 | Avaya Technology Corp. | Intelligent demand driven recognition of URL objects in connection oriented transactions |
| US6850495B1 (en) | 2000-08-31 | 2005-02-01 | Verizon Communications Inc. | Methods, apparatus and data structures for segmenting customers using at least a portion of a layer 2 address header or bits in the place of a layer 2 address header |
| US6873839B2 (en) | 2000-11-13 | 2005-03-29 | Meshnetworks, Inc. | Prioritized-routing for an ad-hoc, peer-to-peer, mobile radio access system |
| US6757269B2 (en) | 2001-02-27 | 2004-06-29 | Motorola, Inc. | Mobile wireless router |
| JP3744375B2 (en) | 2001-04-03 | 2006-02-08 | オムロン株式会社 | Cradle, security system, mobile phone, and monitoring method |
| JP2003023444A (en) | 2001-07-06 | 2003-01-24 | Fujitsu Ltd | Dynamic load distribution system utilizing virtual router |
| EP1289191A1 (en) | 2001-09-03 | 2003-03-05 | Agilent Technologies, Inc. (a Delaware corporation) | Monitoring communications networks |
| JP2005502239A (en) * | 2001-09-05 | 2005-01-20 | エリ・アビル | Method and apparatus for client side dynamic load balancing system |
| US20030059005A1 (en) | 2001-09-24 | 2003-03-27 | Teleware, Inc. | Multi-media communication management system with dynamic bypass routing of real time streaming media |
| DE10148985A1 (en) * | 2001-10-04 | 2003-04-10 | Deutsche Telekom Ag | Output of personalized information in a customized web page or site when a user requests information from a web server, whereby personal preferences are stored in an ISP database and are then accessed by other web servers |
| US7617317B2 (en) | 2001-12-03 | 2009-11-10 | Sprint Spectrum L.P. | Method and system for allowing multiple service providers to serve users via a common access network |
| US7155608B1 (en) * | 2001-12-05 | 2006-12-26 | Bellsouth Intellectual Property Corp. | Foreign network SPAM blocker |
| US7400903B2 (en) | 2002-04-16 | 2008-07-15 | Texas Instruments Incorporated | Wireless communications system using both licensed and unlicensed frequency bands |
| US7421491B2 (en) | 2002-04-23 | 2008-09-02 | Seer Insight Security K.K. | Method and system for monitoring individual devices in networked environments |
| US6879574B2 (en) | 2002-06-24 | 2005-04-12 | Nokia Corporation | Mobile mesh Ad-Hoc networking |
| US7050405B2 (en) | 2002-08-23 | 2006-05-23 | Qualcomm Incorporated | Method and system for a data transmission in a communication system |
| US6885859B2 (en) | 2002-09-12 | 2005-04-26 | Broadcom Corporation | Apparatus for controlling and monitoring a wireless hotspot through an interface with a cellular telephone network |
| US6795700B2 (en) | 2002-09-12 | 2004-09-21 | Broadcom Corporation | Method of creating incentives for establishing hotspot locations |
| US6862444B2 (en) | 2002-09-12 | 2005-03-01 | Broadcom Corporation | Billing control methods in wireless hot spots |
| KR100819678B1 (en) | 2002-09-28 | 2008-04-04 | 주식회사 케이티 | Authentification Method of Public Wireless LAN Service using CDMA authentification information |
| US7499401B2 (en) * | 2002-10-21 | 2009-03-03 | Alcatel-Lucent Usa Inc. | Integrated web cache |
| JP2004172983A (en) | 2002-11-20 | 2004-06-17 | Ntt Docomo Inc | Mail server, mobile communication terminal, and program |
| AU2003297433A1 (en) | 2002-12-24 | 2004-07-22 | Samrat Vasisht | Method, system and device for automatically configuring a communications network |
| US20040139170A1 (en) * | 2003-01-15 | 2004-07-15 | Ming-Teh Shen | Method and apparatus for management of shared wide area network connections |
| US7340615B2 (en) | 2003-01-31 | 2008-03-04 | Microsoft Corporation | Method and apparatus for managing power in network interface modules |
| KR101009384B1 (en) | 2003-02-18 | 2011-01-19 | 도쿄엘렉트론가부시키가이샤 | Method for automatic configuration of a processing system |
| US20060171402A1 (en) * | 2003-03-06 | 2006-08-03 | Moore John A | Method and system for providing broadband multimedia services |
| US7634252B2 (en) | 2003-03-07 | 2009-12-15 | Computer Assocaites Think, Inc. | Mobility management in wireless networks |
| US7382771B2 (en) | 2003-03-13 | 2008-06-03 | In Motion Technology, Inc. | Mobile wireless hotspot system |
| US20040205154A1 (en) | 2003-03-26 | 2004-10-14 | Lockheed Martin Corporation | System for integrated mobile devices |
| US20040218544A1 (en) | 2003-05-02 | 2004-11-04 | Ray Lee | Router capable of displaying network system |
| US7346344B2 (en) | 2003-05-30 | 2008-03-18 | Aol Llc, A Delaware Limited Liability Company | Identity-based wireless device configuration |
| JP2005039649A (en) | 2003-07-17 | 2005-02-10 | Hitachi Ltd | Base station apparatus and wireless radio |
| US8838772B2 (en) | 2003-08-29 | 2014-09-16 | Ineoquest Technologies, Inc. | System and method for analyzing the performance of multiple transportation streams of streaming media in packet-based networks |
| EP1665715B1 (en) | 2003-09-11 | 2019-05-22 | Bae Systems Plc | Real-time network monitoring and security |
| US20050101340A1 (en) | 2003-11-10 | 2005-05-12 | Archiable Donald P. | Wireless power control |
| US7187923B2 (en) | 2003-11-20 | 2007-03-06 | Research In Motion Limited | Seamless call switching in a dual mode environment |
| JP5047455B2 (en) | 2004-03-31 | 2012-10-10 | 京セラ株式会社 | Identifier assignment method and wireless communication system |
| US20050246434A1 (en) | 2004-04-05 | 2005-11-03 | International Business Machines Corporation | Services for capturing and modeling computer usage |
| US7623518B2 (en) * | 2004-04-08 | 2009-11-24 | Hewlett-Packard Development Company, L.P. | Dynamic access control lists |
| US7283803B2 (en) | 2004-04-16 | 2007-10-16 | Broadcom Corporation | Location-aware application based quality of service (QOS) via a broadband access gateway |
| US8972576B2 (en) | 2004-04-28 | 2015-03-03 | Kdl Scan Designs Llc | Establishing a home relationship between a wireless device and a server in a wireless network |
| US20050267965A1 (en) | 2004-05-13 | 2005-12-01 | Ixi Mobile (R&D) Ltd. | Mobile router graceful shutdown system and method |
| US7523193B2 (en) | 2004-05-18 | 2009-04-21 | International Business Machines Corporation | Method and apparatus for DNS pre-fetching for multiple clients |
| US7372809B2 (en) | 2004-05-18 | 2008-05-13 | Time Warner Cable, Inc. | Thwarting denial of service attacks originating in a DOCSIS-compliant cable network |
| US7467405B2 (en) * | 2004-06-22 | 2008-12-16 | Taiwan Semiconductor Manufacturing Company, Ltd. | Method and apparatus for detecting an unauthorized client in a network of computer systems |
| US7764784B2 (en) | 2004-09-08 | 2010-07-27 | Cradlepoint, Inc. | Handset cradle |
| US9237102B2 (en) | 2004-09-08 | 2016-01-12 | Cradlepoint, Inc. | Selecting a data path |
| US9232461B2 (en) | 2004-09-08 | 2016-01-05 | Cradlepoint, Inc. | Hotspot communication limiter |
| US20070254727A1 (en) | 2004-09-08 | 2007-11-01 | Pat Sewall | Hotspot Power Regulation |
| US20090172658A1 (en) | 2004-09-08 | 2009-07-02 | Steven Wood | Application installation |
| US9294353B2 (en) | 2004-09-08 | 2016-03-22 | Cradlepoint, Inc. | Configuring a wireless router |
| US8732808B2 (en) | 2004-09-08 | 2014-05-20 | Cradlepoint, Inc. | Data plan activation and modification |
| US8249052B2 (en) | 2004-09-08 | 2012-08-21 | Cradlepoint, Inc. | Automated access of an enhanced command set |
| US9584406B2 (en) | 2004-09-08 | 2017-02-28 | Cradlepoint, Inc. | Data path switching |
| US8477639B2 (en) | 2004-09-08 | 2013-07-02 | Cradlepoint, Inc. | Communicating network status |
| BRPI0515159A (en) | 2004-09-10 | 2008-07-08 | Cooper Technologies Co | system and method for circuit protector monitoring and management |
| GB2418795A (en) | 2004-10-01 | 2006-04-05 | Agilent Technologies Inc | Monitoring traffic in a packet switched network |
| CN101053213B (en) | 2004-11-04 | 2011-06-22 | 松下电器产业株式会社 | Multi-interface communication equipment, terminal and path switching method |
| US7742455B2 (en) | 2004-11-19 | 2010-06-22 | Telefonaktiebolaget Lm Ericsson (Publ) | Scheduling method for wireless packet data channel |
| US8380158B2 (en) | 2004-12-06 | 2013-02-19 | Edward A. McCulloch | System and method for vital communications connectivity |
| US7577458B2 (en) | 2005-01-30 | 2009-08-18 | Cisco Technology, Inc. | LCD display on wireless router |
| US7421265B1 (en) | 2005-03-04 | 2008-09-02 | Cisco Technology, Inc. | Selectable network antenna systems and methods |
| US7522569B2 (en) | 2005-06-30 | 2009-04-21 | Netgear, Inc. | Peripheral device with visual indicators to show utilization of radio component |
| US7620065B2 (en) | 2005-07-22 | 2009-11-17 | Trellia Networks, Inc. | Mobile connectivity solution |
| US7813314B2 (en) | 2005-08-02 | 2010-10-12 | Waav Inc. | Mobile router device |
| US20070081469A1 (en) | 2005-10-11 | 2007-04-12 | Sbc Knowledge Ventures L.P. | System and methods for wireless fidelity (WIFI) venue utilization monitoring and management |
| US20070147324A1 (en) | 2005-11-29 | 2007-06-28 | Mcgary Faith | System and method for improved WiFi/WiMax retail installation management |
| US9794272B2 (en) | 2006-01-03 | 2017-10-17 | Alcatel Lucent | Method and apparatus for monitoring malicious traffic in communication networks |
| WO2007136620A2 (en) | 2006-05-16 | 2007-11-29 | Autonet Mobile, Inc. | Mobile router with serial device interface |
| US20070291711A1 (en) | 2006-06-14 | 2007-12-20 | Ibahn General Holdings Corporation | Techniques for wireless deployment |
| US20080005108A1 (en) | 2006-06-28 | 2008-01-03 | Microsoft Corporation | Message mining to enhance ranking of documents for retrieval |
| US20080043673A1 (en) | 2006-08-18 | 2008-02-21 | Johnson Michael D | Cellular mobile gateway with signal quality indicator |
| US8064391B2 (en) | 2006-08-22 | 2011-11-22 | Embarq Holdings Company, Llc | System and method for monitoring and optimizing network performance to a wireless device |
| US7821987B2 (en) | 2006-11-22 | 2010-10-26 | Kyocera Corporation | Wireless wide area network (WWAN) mobile gateway with communication protocol management |
| JP4773946B2 (en) | 2006-12-28 | 2011-09-14 | 富士通株式会社 | MONITOR CONTROL SYSTEM, MONITOR DEVICE, MONITOR CONTROL METHOD, AND MONITOR CONTROL PROGRAM |
| WO2008085204A2 (en) * | 2006-12-29 | 2008-07-17 | Prodea Systems, Inc. | Demarcation between application service provider and user in multi-services gateway device at user premises |
| US8644272B2 (en) | 2007-02-12 | 2014-02-04 | Cradlepoint, Inc. | Initiating router functions |
| US9021081B2 (en) | 2007-02-12 | 2015-04-28 | Cradlepoint, Inc. | System and method for collecting individualized network usage data in a personal hotspot wireless network |
| US20080259841A1 (en) | 2007-04-17 | 2008-10-23 | Parag Deshpande | Subscription aggregation and load balancing in a broadband router |
| US8194657B2 (en) * | 2007-05-22 | 2012-06-05 | Actiontec Electronics, Inc. | Systems and methods for dynamic quality of service |
| US8421637B2 (en) | 2007-07-13 | 2013-04-16 | Cradlepoint, Inc. | Multipurpose indicator lights |
| US8108517B2 (en) | 2007-11-27 | 2012-01-31 | Umber Systems | System and method for collecting, reporting and analyzing data on application-level activity and other user information on a mobile data network |
-
2007
- 2007-02-12 US US11/673,973 patent/US7962569B2/en active Active
- 2007-02-13 CA CA002642027A patent/CA2642027A1/en not_active Abandoned
- 2007-02-13 WO PCT/US2007/062078 patent/WO2007095545A2/en active Application Filing
- 2007-02-13 EP EP07756936A patent/EP1999623A2/en not_active Withdrawn
Also Published As
| Publication number | Publication date |
|---|---|
| US20070255848A1 (en) | 2007-11-01 |
| US7962569B2 (en) | 2011-06-14 |
| EP1999623A2 (en) | 2008-12-10 |
| WO2007095545A3 (en) | 2008-05-02 |
| WO2007095545A2 (en) | 2007-08-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7962569B2 (en) | Embedded DNS | |
| EP1875725B1 (en) | Process for managing resource address requests and associated gateway device | |
| US20060039348A1 (en) | System, device and method for data transfer | |
| CN1890942B (en) | Method of redirecting client requests to web services | |
| US20070142036A1 (en) | Provision of content in mobile environments | |
| KR19990083616A (en) | Method and Apparatus for Flexibly Linking Using Aliases | |
| JP2001154969A (en) | Method and system for providing resources access in mobile environment | |
| JP2010273045A (en) | Server apparatus | |
| JP2002540677A (en) | Data network load management | |
| CN100465950C (en) | Web browser command button for client support | |
| JP3770801B2 (en) | Proxy server, server and recording medium recording program for realizing the same | |
| JP3953950B2 (en) | Server system using local address | |
| CN102598637A (en) | Communications system | |
| CN105338187A (en) | Information processing method and electronic equipment | |
| TW200417261A (en) | An apparatus and method for coupling a network data device to a digital network | |
| US8560701B2 (en) | Method and apparatus for web service communication | |
| KR20020076891A (en) | Wireless-internet connection system | |
| JP4988307B2 (en) | Context-based navigation | |
| JP2014049807A (en) | Communication packet processing device | |
| WO2002013026A1 (en) | A method for controlling data at a client device | |
| JP4633034B2 (en) | Information processing system, information processing method, and information processing program | |
| CN115996237B (en) | Remote management method, processor and storage medium for terminal of Internet of things | |
| KR20020084374A (en) | Discrimination And Display Method Of Abnormal URL In Wireless Internet | |
| US8458296B2 (en) | Computer system with simplified server access and corresponding process | |
| JP4665063B2 (en) | COMMUNICATION SYSTEM, TERMINAL REGISTRATION METHOD, AND SERVER |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| FZDE | Discontinued |
Effective date: 20130213 |