CN105979020B - Method and device for improving DNS availability - Google Patents
Method and device for improving DNS availability Download PDFInfo
- Publication number
- CN105979020B CN105979020B CN201610138347.1A CN201610138347A CN105979020B CN 105979020 B CN105979020 B CN 105979020B CN 201610138347 A CN201610138347 A CN 201610138347A CN 105979020 B CN105979020 B CN 105979020B
- Authority
- CN
- China
- Prior art keywords
- consumer device
- dns server
- list
- address
- request
- 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.)
- Active
Links
Images
Classifications
-
- 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]
-
- 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/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
- H04L61/5014—Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/30—Services specially adapted for particular environments, situations or purposes
- H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
- H04W4/44—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/005—Moving wireless networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention relates to improving DNS availability. A system and method for providing an address for a Domain Name System (DNS) server to a consumer device, wherein the consumer device is connected to the internet by a vehicle, comprising: providing an address for a default DNS server to a consumer device; receiving a request from a consumer device to convert a domain name to an Internet Protocol (IP) address using a default DNS server; forwarding the request to the default DNS server; determining whether the request has been resolved by a default DNS server within a response time limit; and if the request is not resolved within the response time limit, updating the consumer device with a different address for the DNS server retrieved from the list stored in the vehicle hardware.
Description
Technical Field
The present invention relates to connecting consumer devices to the internet via a vehicle, and more particularly to increasing the speed and reliability of the internet connection.
Background
Most vehicles are today equipped with hardware, such as a telematics unit, that enables various wireless communications (including connecting consumer devices to the internet). The telematics unit can act as a wireless access point between the consumer device and a wireless carrier system (e.g., a cellular network) that provides access to the internet.
Devices connected to the internet use digitally represented Internet Protocol (IP) addresses to communicate requests from consumer devices to specific servers hosting the site on the internet. However, requests from devices are typically in a human-readable domain name format (e.g., www.xxx.com), which cannot be read directly by a computer. To address this format difference, the Domain Name System (DNS) protocol is used to translate user-friendly domain names into IP addresses, a process known as DNS name resolution. Such a process utilizes a DNS server that manages a large database that maps domain names to IP addresses. In practice, when a consumer device, such as a computer on a home network, connects to an Internet Service Provider (ISP), or through a WiFi network, the modem or router that assigns the network address of the device also provides configuration data that includes one or more DNS servers used by the device to translate DNS names into IP addresses.
Similarly, when a consumer device is connected to the internet through a vehicle, the hardware of the vehicle is typically preloaded with a default DNS server to be used by the consumer device. However, if the default DNS server stored on the vehicle hardware is no longer valid or otherwise unavailable, the consumer device is unable to connect to the internet causing delays and poor performance.
Disclosure of Invention
According to an embodiment of the present invention, a method for providing an address for a Domain Name System (DNS) server to a consumer device is provided, wherein the consumer device is connected to the internet by a vehicle. The method comprises the following steps: providing an address for a default DNS server to a consumer device; receiving a request from a consumer device to convert a domain name to an Internet Protocol (IP) address using a default DNS server; forwarding the request to a default DNS server; determining whether the request has been resolved by a default DNS server within a response time limit; and if the request is not resolved within the response time limit, updating the consumer device with a different address for the DNS server retrieved from the list stored in the vehicle hardware.
According to another aspect of the present invention, a method for providing an address for a Domain Name System (DNS) server to a consumer device is provided, wherein the consumer device is connected to the internet via a vehicle. The method comprises the following steps: providing an address and lease time for a default DNS server to a consumer device via a Dynamic Host Configuration Protocol (DHCP); receiving a request from a consumer device to convert a domain name to an Internet Protocol (IP) address using a default DNS server; maintaining a list of DNS servers in the vehicle hardware, wherein the DNS servers are ranked according to performance characteristics; and updating the consumer device via DHCP with the different address for the DNS server retrieved from the list.
According to yet another aspect of the present invention, a system for connecting a consumer device to the internet and for providing an address for a Domain Name System (DNS) server to the consumer device is provided. The system includes vehicle hardware and/or a vehicle telematics unit, individually or in combination, configured to provide an address and lease time for a default DNS server to a consumer device via Dynamic Host Configuration Protocol (DHCP); receiving a request from a consumer device to convert a domain name to an Internet Protocol (IP) address using a default DNS server; maintaining a list of DNS servers in the vehicle hardware, wherein the DNS servers are ranked according to performance characteristics; and updating the consumer device with the DNS server retrieved from the list via DHCP.
The invention also discloses the following technical scheme.
Scheme 1. a method for providing an address for a Domain Name System (DNS) server to a consumer device, wherein the consumer device is connected to the internet by a vehicle, the method comprising the steps of:
providing an address for a default DNS server to the consumer device;
receiving a request from the consumer device to convert a domain name to an Internet Protocol (IP) address using the default DNS server;
forwarding the request to the default DNS server;
determining whether the request has been resolved by the default DNS server within a response time limit; and
if the request is not resolved within the response time limit, updating the consumer device with a different address for a DNS server retrieved from a list stored in vehicle hardware.
Scheme 2. the method of scheme 1, further comprising ranking entries in the list based on a performance characteristic associated with each DNS server in the list.
Scheme 3. the method of scheme 2, wherein updating the consumer device with the DNS server address comprises retrieving a highest ranked DNS server record in the list from the list.
Scheme 4. the method of scheme 2, wherein the performance characteristic of each DNS server in the list comprises a domain name resolution time.
Scheme 5. the method of scheme 1, further comprising adding to the list one or more DNS servers received from a wireless carrier system.
Scheme 6. the method of scheme 1, further comprising updating the DNS server entry in the list when a new DNS server is received and when new performance information is available.
Scheme 7. the method of scheme 1, wherein updating the consumer device with the DNS server from the list is accomplished via Dynamic Host Configuration Protocol (DHCP).
Scheme 8. the method of scheme 6, further comprising providing, to the consumer device via DHCP, a lease time associated with the default DNS server.
Scheme 9. the method of scheme 7, further comprising receiving a request to renew the consumer device via DHCP when half of the lease time has elapsed.
providing, to the consumer device via Dynamic Host Configuration Protocol (DHCP), an address and lease time for a default DNS server;
receiving a request from the consumer device to convert a domain name to an Internet Protocol (IP) address using the default DNS server;
maintaining a list of DNS servers within the vehicle hardware, wherein the DNS servers are ranked according to performance characteristics; and
updating the consumer device via DHCP with a different address for a DNS server retrieved from the list.
Scheme 11 the method of scheme 10, further comprising adding to the list one or more DNS servers received from a wireless carrier system.
Scheme 12. the method of scheme 10, wherein updating the consumer device with the DNS server address comprises retrieving a highest ranked DNS server record in the list from the list.
Scheme 13. the method of scheme 10, wherein the performance characteristic of each DNS server in the list comprises a domain name resolution time.
Scheme 15. the method of scheme 10, further comprising receiving a request to renew the consumer device via DHCP when half of the lease time has elapsed.
A system for connecting a consumer device to the internet and for providing an address for a Domain Name System (DNS) server to the consumer device, the system comprising:
vehicle hardware and/or a vehicle telematics unit, alone or in combination, configured to:
providing, to the consumer device via Dynamic Host Configuration Protocol (DHCP), an address and lease time for a default DNS server;
receiving a request from the consumer device to convert a domain name to an Internet Protocol (IP) address using the default DNS server;
maintaining a list of DNS servers in the vehicle hardware, wherein the DNS servers are ranked according to performance characteristics; and
updating the consumer device via DHCP with the DNS server retrieved from the list.
Scheme 17. the system of scheme 16, wherein updating the consumer device with the DNS server address comprises retrieving a highest ranked DNS server record in the list from the list.
Scheme 19. the method of scheme 16, further comprising updating the DNS server entry in the list when a new entry is received and when new capability information is available.
Drawings
One or more embodiments of the present invention will hereinafter be described in conjunction with the appended drawings, wherein like designations denote like elements, and wherein:
FIG. 1 is a block diagram depicting an embodiment of a communication system capable of using the methods disclosed herein; and
FIG. 2 is a flow chart depicting a method for improving DNS availability in accordance with an embodiment of the disclosed invention.
Detailed Description
The systems and methods described below pertain to connecting consumer devices to the internet through a vehicle, and in particular through vehicle hardware as a wireless access point. The disclosed method optimizes Domain Name System (DNS) server availability and domain name resolution time by retaining DNS server performance information in the vehicle hardware and by utilizing this information to rank entries in the DNS server list. Further, the method utilizes Dynamic Host Configuration Protocol (DHCP) to continuously update the consumer device with the highest ranked DNS server in the DNS server list.
Communication system
Referring to fig. 1, an operating environment is shown that includes a mobile vehicle communication system 10, which communication system 10 can be used to implement the methods disclosed herein. The communication system 10 generally includes a vehicle 12, one or more wireless carrier systems 14, and the internet 16. It should be understood that the disclosed methods can be used in many different systems and are not specifically limited to the operating environments illustrated herein. Moreover, the architecture, construction, arrangement, and operation of the system 10 and its various components are generally known in the art. Thus, the following paragraphs simply provide a brief overview of one such communication system 10; however, other systems not shown here may also employ the disclosed methods.
The vehicle 12 is depicted in the illustrated embodiment as a passenger car, but it should be appreciated that any other vehicle can be used, including motorcycles, trucks, Sport Utility Vehicles (SUVs), Recreational Vehicles (RVs), marine vessels, aircraft, and so forth. The vehicle hardware 18 is generally shown in fig. 1 and includes a telematics unit 20, which may be an OEM (original equipment manufacturer) installed (embedded) device or aftermarket device (aftermarket device) installed in the vehicle and which is capable of wireless voice and/or data communication over the wireless carrier system 14 and via a wireless network. This enables the vehicle 12 to communicate with a vehicle call center (not shown), other telematics-enabled vehicles, or some other entity or device, such as the consumer device 30. Telematics unit 20 preferably uses radio transmissions to establish a communication channel (voice channel and/or data channel) with wireless carrier system 14 so that voice and/or data transmissions can be sent and received over the channel. By providing both voice and data communications, the telematics unit 20 enables the vehicle to provide a number of different services, including those related to navigation, telephony, emergency assistance, diagnostics, infotainment, and the like. Data can be sent over any of a data connection (such as via packet data transmission over a data channel) or over a voice channel using techniques well known in the art. For integrated services involving both voice and data communications, the system can utilize a single call over the voice channel and switch between voice and data transmissions over the voice channel as needed, and this can be accomplished using techniques well known to those skilled in the art.
According to one embodiment, telematics unit 20 utilizes cellular communications according to any of the GSM, CDMA, or LTE standards, and thus includes a standard cellular chipset 22 for voice communications such as hands-free calls, a wireless modem 24 for data transfer, a Dynamic Host Configuration Protocol (DHCP) server 25, electronic processing device 26, one or more digital storage devices 28 including volatile and non-volatile memory, and dual antennas 32. It should be appreciated that the modem 24 can be either of two cases: it can be implemented in software stored in the telematics unit 20 and executed by the processor 26, or it can be a separate hardware component located external to the telematics unit 20. The modem 24 is capable of operating with many different standards or protocols, such as LTE, EVDO, CDMA, GPRS, and EDGE. Wireless networks between vehicles and other network devices, including consumer devices 30, can also be implemented with the telematics unit 20. To this end, telematics unit 20 can be configured to wirelessly communicate according to one or more wireless protocols, including short-range wireless communications (SRWC), such as any of the IEEE802.11 protocols, WiMAX, ZigBee systems, Wi-Fi direct, Bluetooth, or Near Field Communications (NFC). When used for packet-switched data communications such as TCP/IP, the telematics unit 20 can be configured with a static IP address or can be set to automatically receive a specified IP address from another device on the network (such as a router) or from a network address server (such as DHCP server 25).
DHCP employs a client/server model in which, when connected to a network, a DHCP client sends a request to a DHCP server, which manages a pool of IP addresses and configuration parameters. In response to a request from a DHCP client, the DHCP server grants the request and returns corresponding configuration information including an IP address and an address for the DNS server. This request-and-grant process uses a lease concept with a configurable time period for which the allocation of IP addresses is valid. This procedure allows the DHCP server to reclaim and then reassign IP addresses and update DNS servers that did not renew at the expiration of the lease time.
The DHCP request-and-grant procedure typically includes four phases to dynamically obtain an IP address from the DHCP server: a discovery phase, a provisioning phase, a selection phase, and a validation phase. Referring to fig. 1, in the discovery phase, the DHCP client (in this case consumer device 30) broadcasts a DHCP-DISCOVER packet to DHCP server 25. After receiving the DHCP-DISCOVER packet, the DHCP server 25 selects an unassigned IP address according to the priority order of IP address assignment and then sends a DHCP-OFFER packet to the consumer device 30, which includes the IP address and other configuration information such as lease time and address for the DNS server, during the provisioning phase. The DNS server manages a large database that maps domain names to IP addresses. Although not aware of the user, when the consumer device 30 attempts to connect to a particular site (e.g., www.google.com) on the internet, a DNS request will be sent from the consumer device 30 to the DNS server to request the IP address corresponding to the particular domain name. The DNS server maps the domain name and returns the corresponding IP address (e.g., 173.194.115.10) for the requested site to the consumer device 30. In one embodiment, the DNS server provided in the provisioning phase is a default DNS server address stored in memory 28.
In the selection phase, the consumer device 30 selects an IP address and then broadcasts a DHCP-REQUEST packet containing the assigned IP address and DNS server address carried in a DHCP-OFFER packet. In the acknowledgement phase, when a DHCP-REQUEST packet is received, the DHCP server 25 returns a DHCP-ACK packet to the consumer device 30 to confirm the assignment of the IP address and DNS server. After DHCP server 25 dynamically assigns an IP address to consumer device 30, the IP address remains valid for the specified lease time and will be reclaimed by DHCP server 25 when the lease expires. If consumer device 30 wishes to use the IP address for a longer period of time, consumer device 30 must update the IP lease. Typically, by default, consumer device 30 will automatically renew the IP address lease by unicasting a DHCP-REQUEST packet to DHCP server 25 when half of the lease time elapses. If the server is able to re-assign the same IP address to the client, DHCP server 25 responds with a DHCP-ACK packet to notify consumer device 30 of the new lease. Otherwise, DHCP server 25 responds with a DHCP-NAK packet to inform consumer device 30 that the IP address will be reclaimed when the lease time expires. This lease renewal process can also be used to update the DNS server for the consumer device 30, as described below.
The processor 26 can be any type of device capable of processing electronic instructions, including a microprocessor, a microcontroller, a host processor, a controller, a vehicle communication processor, and an Application Specific Integrated Circuit (ASIC). The processor 26 can be a dedicated processor for the telematics unit 20 only or can be shared with other vehicle systems. Processor 26 executes various types of digitally stored instructions, such as software or firmware programs stored in memory 28, which enable telematics unit 20 to provide a wide variety of services. For example, the processor 26 may be capable of executing programs or processing data in order to implement at least a portion of the methods discussed herein.
The storage device 28 includes both volatile memory and non-volatile memory. In one embodiment, the non-volatile memory of the device 28 stores a list of DNS servers used by the vehicle hardware 18 when connecting the consumer device 30 to the internet through the vehicle 12. Entries in the DNS server list are continually updated and ranked based on criteria such as prior DNS server performance characteristics (e.g., DNS resolution time) and other information provided by wireless carrier system 14.
In addition to utilizing wireless carrier system 14, a different wireless carrier system in the form of satellite communications can be used to provide one-way or two-way communications with the vehicle. This can be accomplished using one or more communication satellites 44 and uplink transmission stations 46. The one-way communication can be, for example, a satellite broadcast service, wherein programming content (news, music, etc.) is received by a transmission station 46, packaged for upload, and then transmitted to a satellite 44, which satellite 44 broadcasts the programming to subscribers. The two-way communication can be, for example, a satellite telephone service that utilizes a satellite 44 to relay telephone communications between the vehicle 12 and a station 46. Such satellite phones, if used, can be used in addition to or in place of wireless carrier system 14.
The internet 16 is a global infrastructure of interconnected computer networks that use the standard internet protocol suite (TCP/IP) to link billions of devices worldwide. The internet 16 is an international network of networks consisting of millions of private, public, educational, business, and government packet-switched networks linked by a wide range of electronic, wireless, and fiber optic networking technologies. These computer networks may be accessed by the vehicle 12 via the telematics unit 20 and the wireless carrier system 14 and include, but are not limited to, all web-hosted servers, dedicated servers, and DNS servers.
The operating environment may further include one or more Consumer Devices (CDs) 30. In one embodiment, consumer device 30 may be an electronic device used to place mobile phones over a wide geographic area, with transmissions being facilitated by wireless carrier system 14 (i.e., when consumer device 30 is connected to wireless carrier system 14 through telematics unit 20).
The consumer device 30 may include: hardware, software, and/or firmware enabling cellular telecommunications and communications via short-range wireless communications (e.g., Wi-Fi direct and bluetooth) and other mobile consumer device applications. Such device applications may include software applications that may be pre-installed or installed by a user. One commercial implementation of a vehicle-mobile application may be RemoteLinkTMEnabling a vehicle user to communicate with the vehicle 12 and/or control various aspects or functions of the vehicle, such as, among other things, allowing the user to remotely lock/unlock vehicle doors, start/shut the vehicle on/off, check vehicle tire pressure, fuel level, oil life, etc.
The hardware of the consumer device 30 may have electronics as known to those skilled in the art, including a communication interface, an antenna, and the like. In addition, modern consumer devices 30 may also support additional services and/or functions such as short message service (SMS or text), Multimedia Message Service (MMS), email, Internet access, and commerce and gaming applications. Non-limiting examples of consumer devices 30 include mobile cellular telephones, Personal Digital Assistants (PDAs), smart phones, tablet computers, personal notebook computers with two-way communication capabilities, netbook computers, or any suitable combination thereof. The consumer device 30 may be used inside or outside of a vehicle (such as the vehicle 12 shown in fig. 1) and may be coupled to the vehicle by wire or wirelessly (e.g., with short-range wireless communication). The consumer device 30 may also be configured to provide services under a subscription contract with a third party organization or wireless/telephony service provider. It should be appreciated that various service providers may utilize wireless carrier system 14 and that the service provider of telematics unit 20 may not necessarily be the same service provider as the service provider of consumer device 30.
The consumer device 30 and the vehicle 12 may be used together by a person who is considered to be a vehicle user, such as a driver. However, the vehicle user need not be the driver of the vehicle 12, nor does the vehicle user need to have ownership of the consumer device 30 or the vehicle 12 (e.g., the vehicle user may be the owner or licensee of either or both).
Method-
Turning now to fig. 2, there is a method for connecting a consumer device 30 to the internet through a vehicle 12, and in particular for optimizing DNS server availability and resolution time according to the exemplary embodiments described below. The method 200 begins at step 205 with initialization of the vehicle hardware 18 including the telematics unit 20. Such initialization may include a start-up procedure in which data stored in the memory 28 is read by the processing device 26. The retrieved data may include a default DNS server address used by the consumer device 30 for domain name resolution, as described below.
At step 210, secure short-range wireless communication is established between the vehicle hardware 18, and in one particular example, the telematics unit 20, and one or more nearby consumer devices 30, linking the consumer devices with the vehicle 12. Telematics unit 20 and consumer device 30 are capable of communicating with each other via any suitable short-range wireless communication technology using a standardized protocol, such as bluetooth or others, some of which are listed above. In one non-limiting example, the consumer device 30 and the vehicle telematics unit 20 (here, a wireless access point) utilize the association and authentication procedures set forth in IEEE802.11 to establish a connection. Briefly, the consumer device 30 and the telematics unit 20 exchange a series of management frameworks to achieve an authenticated and associated state between the consumer device 30 and the telematics unit 20.
In another embodiment, telematics unit 20 may also be linked or paired to a software application ("app") installed on consumer device 30. After the initial linking or pairing to the telematics unit 20, the app on the consumer device 30 may automatically communicate with the telematics unit 20 through any suitable wireless communication technology as listed above, or there may be an authentication mechanism such as requiring a password or other identifying information prior to connecting with the telematics unit 20.
At step 215, the vehicle telematics unit 20 requests a data connection with the wireless carrier system 14 and initiates a Dynamic Host Configuration Protocol (DHCP) to establish data communications between the vehicle telematics unit 20 and the consumer device 30, and ultimately the internet. Telematics unit 20 has a pre-configured carrier profile that it uses to register with the preferred wireless carrier. Telematics unit 20 also has the ability to store more than one wireless carrier profile. Thus, it is possible to change the preferred operator using remote functionality if required. Further, if a signal from the preferred carrier is not available, the telematics unit 20 can choose to register with a carrier that has a service agreement with the preferred carrier. This function is the same as that of the wireless mobile phone operator. As described above, DHCP employs a request-and-grant procedure in which DHCP server 25 provides configuration information including an IP address and a DNS server address to consumer device 30. In one embodiment, the initial DNS server address provided to the consumer device 30 refers to the default DNS server read from the memory 28 when the vehicle hardware 18 is initialized in step 205. As part of the DHCP process, DHCP 25 specifies lease times for which the consumer device 30 may use an IP address and a default DNS server. As will be appreciated by those skilled in the art, the lease time is configurable and may vary, although in at least one example, the initial lease time may be 60 seconds. In general, consumer device 30 will begin initiating a request for renewal or initiate a new lease, as described in further detail below.
At step 220, the consumer device 30 sends a DNS request to a default DNS server via the telematics unit 20. Before forwarding the DNS request, telematics unit 20 determines whether a connection to the internet through wireless carrier system 14 is functional at step 225. If the connection is not functional, the telematics unit 20 waits until the connection is functional and then forwards the DNS request to a default DNS server at step 230.
At step 235, the DNS list stored in memory 28 is updated to ensure that the default DNS server retrieved at step 205 is included as one of the entries in the DNS list. However, one of ordinary skill in the art will recognize that the DNS list is continuously updated while the connection between the vehicle hardware 18 and the wireless carrier system 14 is active. For example, when a data connection is requested at step 215, a variety of information used by the vehicle hardware 18 is returned in response to the request, including a new DNS server. However, the response from wireless carrier system 14 may not be immediate and may not be received by vehicle hardware 18 until after the DNS request is forwarded with the address for the default DNS server at step 230. Thus, while the DNS request is being processed, new updated DNS server information may be received by the vehicle hardware 18, but cannot be forwarded to the consumer device 30 until the consumer device 30 communicates with the telematics unit to renew the current lease, as will be explained in more detail below. However, the DNS list and the arrangement of entries in the DNS list are continuously updated in the background. The arrangement of each entry in the list is based on historical performance characteristics such as prior concatenation power, domain name resolution time, etc., and current performance characteristics. The performance characteristics monitored will be success rate, response time and time since last use. The use criteria can be any combination of the above factors.
Referring back to step 230, the vehicle hardware 18 tracks the DNS requests with a timer that starts when the DNS request is sent and records the amount of time it takes for the DNS server to successfully resolve the domain name. This timing information is used to rank the entries in the DNS list. The timing function is also used to determine whether the DNS request has been resolved within a predetermined resolution time (TTR) limit. In step 240, the system determines whether the DNS request has been resolved within the TTR limits. If the DNS request has been resolved, then at step 245, the DNS list is updated to reflect the resolution time of the current DNS server and the DNS list arrangement is updated accordingly. If the TTR limit has expired and the DNS request has not been resolved, then the next available, highest ranked server in the DNS list is enqueued for transmission to the consumer device 30 via DHCP, at step 250.
In most cases, the consumer device 30, acting as a DHCP client, is configured to automatically update the lease by unicasting a DHCP-REQUEST packet to the DHCP server 25 when half of the lease time elapses. In other words, regardless of whether the default DNS server used in step 230 successfully resolves the domain name, or whether the TTR limit has expired and the new DNS server is already in the queue according to step 250, when about half of the lease time has elapsed, the consumer device 30 issues a DHCP-REQUEST packet at step 255 so that the DNS server can be updated with the next server in the DNS list and the assigned new lease time. In this way, the system always uses the most recent efficient DNS server. In one scenario, the default DNS server or, alternatively, the current DNS server may already be the highest ranked server in the DNS list. In this case, DHCP server 25 may respond with a DHCP-ACK packet to acknowledge receipt of the request and to assign a new lease time to the default and/or current DNS server.
It is to be understood that the foregoing is a description of one or more embodiments of the invention. The present invention is not limited to the specific embodiments disclosed herein, but is only limited by the claims that follow. Furthermore, statements contained in the foregoing description relate to particular embodiments and are not to be construed as limitations on the scope of the invention or on the definition of terms used in the claims, except where a term or phrase is expressly defined above. Various other embodiments and various changes and modifications to the disclosed embodiments will be apparent to those skilled in the art. All such other embodiments, changes, and modifications are intended to fall within the scope of the appended claims.
As used in this specification and claims, the terms "for example," "such as," "like," and the verbs "comprising," "having," "including," and their other verb forms, when used in conjunction with a listing of one or more components or other items, are each to be construed as open-ended, meaning that the listing is not to be considered as excluding other, additional components or items. Other terms are to be understood using their broadest reasonable meaning unless they are used in a context that requires a different interpretation.
Claims (14)
1. A method for providing an address for a domain name system, DNS, server to a consumer device, wherein the consumer device is connected to the internet by a vehicle, the method comprising the steps of:
providing an address for a default DNS server to the consumer device;
receiving a request from the consumer device to convert a domain name to an internet protocol, IP, address using the default DNS server;
forwarding the request to the default DNS server;
determining whether the request has been resolved by the default DNS server within a response time limit; and
if the request is not resolved within the response time limit, updating the consumer device with a different address for a DNS server retrieved from a list stored in vehicle hardware.
2. The method of claim 1, further comprising ranking entries in the list based on performance characteristics associated with each DNS server in the list.
3. The method of claim 2, wherein updating the consumer device with the DNS server address comprises retrieving a highest-ranked DNS server record entry in the list from the list.
4. The method of claim 2, wherein the performance characteristic of each DNS server in the list comprises a domain name resolution time.
5. The method of claim 1, further comprising adding to the list one or more DNS servers received from a wireless carrier system.
6. The method of claim 1, further comprising updating the DNS server entry in the list when a new DNS server is received and when new performance information is available.
7. The method of claim 1, wherein updating the consumer device with the DNS server from the list is accomplished via dynamic host configuration protocol, DHCP.
8. The method of claim 6, further comprising providing, to the consumer device via DHCP, a lease time associated with the default DNS server.
9. The method of claim 8, further comprising receiving a request to renew the consumer device via DHCP when half of the lease time has elapsed.
10. A system for connecting a consumer device to the internet and for providing an address for a domain name system, DNS, server to the consumer device, the system comprising:
vehicle hardware and/or a vehicle telematics unit, alone or in combination, configured to:
providing an address and lease time for a default DNS server to the consumer device via a dynamic host configuration protocol, DHCP;
receiving a request from the consumer device to convert a domain name to an internet protocol, IP, address using the default DNS server;
determining whether the request has been resolved by the default DNS server within a response time limit; and
if the request is not resolved within the response time limit, updating the consumer device with a different address for a DNS server retrieved from a list stored in vehicle hardware.
11. The system of claim 10, wherein updating the consumer device comprises retrieving a highest-ranked DNS server record entry in the list from the list.
12. The system of claim 10, wherein the performance characteristic of each DNS server in the list comprises a domain name resolution time.
13. The system of claim 10, further comprising updating the DNS server entry in the list when a new entry is received and when new performance information is available.
14. The system of claim 10, further comprising receiving a request to renew the consumer device via DHCP when half of the lease time has elapsed.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US14/656,060 US9912634B2 (en) | 2015-03-12 | 2015-03-12 | Enhancing DNS availability |
| US14/656060 | 2015-03-12 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105979020A CN105979020A (en) | 2016-09-28 |
| CN105979020B true CN105979020B (en) | 2020-02-18 |
Family
ID=56801204
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610138347.1A Active CN105979020B (en) | 2015-03-12 | 2016-03-11 | Method and device for improving DNS availability |
Country Status (3)
| Country | Link |
|---|---|
| US (1) | US9912634B2 (en) |
| CN (1) | CN105979020B (en) |
| DE (1) | DE102016104152B4 (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10388162B2 (en) | 2017-01-23 | 2019-08-20 | Veniam, Inc. | Systems and methods for utilizing mobile access points as fixed access points in a network of moving things, for example including autonomous vehicles |
| US10356616B2 (en) * | 2017-02-14 | 2019-07-16 | GM Global Technology Operations LLC | Identifying external devices using a wireless network associated with a vehicle |
| US10574316B1 (en) * | 2018-05-23 | 2020-02-25 | Amazon Technologies, Inc. | Antenna switching for device with multiple antennas |
| CN111092963B (en) * | 2019-12-02 | 2024-03-22 | 珠海市魅族科技有限公司 | Domain name service response method |
| EP3965394A1 (en) * | 2020-09-07 | 2022-03-09 | Volkswagen Ag | Method for controlling an internet-based communication |
| CN114401140B (en) * | 2022-01-13 | 2022-11-11 | 腾讯科技（深圳）有限公司 | Access processing method, related device and storage medium |
| CN115225645A (en) * | 2022-07-29 | 2022-10-21 | 天翼云科技有限公司 | Service updating method, device, system and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101764855A (en) * | 2009-12-30 | 2010-06-30 | 福建星网锐捷网络有限公司 | Method, device and system for providing domain name resolution services |
| CN101827136A (en) * | 2010-03-30 | 2010-09-08 | 联想网御科技(北京)有限公司 | Defense method for domain name system server buffer infection and network outlet equipment |
| CN102572014A (en) * | 2012-03-07 | 2012-07-11 | 华为终端有限公司 | Message processing method and device and system thereof |
| CN103916490A (en) * | 2014-04-03 | 2014-07-09 | 深信服网络科技（深圳）有限公司 | DNS tamper-proof method and device |
Family Cites Families (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7484008B1 (en) * | 1999-10-06 | 2009-01-27 | Borgia/Cummins, Llc | Apparatus for vehicle internetworks |
| US20060277278A1 (en) | 2005-06-06 | 2006-12-07 | International Business Machines Corporation | Distributing workload among DNS servers |
| DE102006011829B4 (en) * | 2006-03-13 | 2015-10-22 | Bayerische Motoren Werke Aktiengesellschaft | Method for data communication |
| US20070253377A1 (en) * | 2006-04-28 | 2007-11-01 | Motorola, Inc. | Apparatus and method for name resolution in an aggregation of mobile networks |
| US8219710B2 (en) * | 2006-10-28 | 2012-07-10 | General Motors Llc | Method of establishing a data connection with a telematics-equipped vehicle |
| US8134969B2 (en) * | 2006-11-10 | 2012-03-13 | Motorola Solutions, Inc. | IP layer-handoff using mobility domains and IP caching |
| US20080194246A1 (en) * | 2007-02-12 | 2008-08-14 | Thierry Etienne Klein | Apparatus and Method for Providing a Rapidly Deployable Wireless Network |
| US8266324B2 (en) * | 2008-06-12 | 2012-09-11 | International Business Machines Corporation | Domain specific domain name service |
| US8423607B2 (en) * | 2010-06-01 | 2013-04-16 | Qualcomm Incorporated | Fallback procedures for domain name server update in a mobile IP registration |
| US8681995B2 (en) * | 2010-12-21 | 2014-03-25 | Microsoft Corporation | Supporting DNS security in a multi-master environment |
| US8799518B2 (en) | 2012-04-04 | 2014-08-05 | Verisign, Inc. | Process for selecting an authoritative name server |
| US10164989B2 (en) * | 2013-03-15 | 2018-12-25 | Nominum, Inc. | Distinguishing human-driven DNS queries from machine-to-machine DNS queries |
| US9419937B2 (en) * | 2014-01-29 | 2016-08-16 | Vmware, Inc. | System and method for dynamically configuring a DNS server in a virtual network environment |
| CN105323173B (en) * | 2014-07-18 | 2019-02-12 | 中兴通讯股份有限公司 | The setting method and device of networking rule entry |
| US20160056975A1 (en) * | 2014-08-25 | 2016-02-25 | Conexlink, LLC | System and Method for Virtualizing an IT Infrastructure with Remotely Accessible Virtual Desktops |
-
2015
- 2015-03-12 US US14/656,060 patent/US9912634B2/en active Active
-
2016
- 2016-03-08 DE DE102016104152.1A patent/DE102016104152B4/en active Active
- 2016-03-11 CN CN201610138347.1A patent/CN105979020B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101764855A (en) * | 2009-12-30 | 2010-06-30 | 福建星网锐捷网络有限公司 | Method, device and system for providing domain name resolution services |
| CN101827136A (en) * | 2010-03-30 | 2010-09-08 | 联想网御科技(北京)有限公司 | Defense method for domain name system server buffer infection and network outlet equipment |
| CN102572014A (en) * | 2012-03-07 | 2012-07-11 | 华为终端有限公司 | Message processing method and device and system thereof |
| CN103916490A (en) * | 2014-04-03 | 2014-07-09 | 深信服网络科技（深圳）有限公司 | DNS tamper-proof method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| US20160269356A1 (en) | 2016-09-15 |
| DE102016104152A1 (en) | 2016-09-15 |
| US9912634B2 (en) | 2018-03-06 |
| DE102016104152B4 (en) | 2024-01-18 |
| CN105979020A (en) | 2016-09-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105979020B (en) | Method and device for improving DNS availability | |
| US8195196B2 (en) | Mobility based service in wireless environment | |
| US8199731B2 (en) | Method and apparatus for facilitating switched packet data services on multiple networks | |
| US10084879B2 (en) | Virtual subscriber identity module for mobile communication device | |
| KR101715974B1 (en) | Machine type communication preregistration | |
| RU2339188C2 (en) | Organisation of internetworking between first network and second network | |
| CN109964468B (en) | Session processing method, device and system | |
| US20180317074A1 (en) | Control beacons for wireless devices | |
| JP2007511141A (en) | Network selection method and apparatus for prioritizing domestic networks in border areas | |
| CN111527777B (en) | PLMN selection for mission critical devices | |
| AU2006214317A1 (en) | Methods and apparatus for machine-to-machine communications | |
| JP2005512408A (en) | Method for enabling communication with a wireless communication device | |
| US11283756B2 (en) | EPDG selection | |
| US20170171832A1 (en) | Cellular connectivity following a volte connectivity failure | |
| CN102123362A (en) | Method for automatically acquiring mobile phone number by mobile equipment | |
| US20160135039A1 (en) | Remote telematics unit band control with dynamic memory | |
| WO2022215331A1 (en) | Method of user equipment (ue), method of access and mobility management function (amf), method of unified data management (udm), ue, amf and udm | |
| CN108124296B (en) | Controlling use of an onboard WI-FI hotspot via a handheld wireless device | |
| US10383045B2 (en) | Wireless service discovery | |
| US9467856B2 (en) | Secure mechanism for obtaining authorization for a discovered location server | |
| WO2012016688A1 (en) | Method, public land mobile network and user equipment | |
| KR102394511B1 (en) | Apparatus and method for controlling vehicle communication based on location | |
| US9420411B2 (en) | Method and apparatus for configuring secure user plane location (SUPL) enabled terminals | |
| JP6062653B2 (en) | Communication system, telephone directory server, wireless communication terminal, and communication method | |
| WO2023120045A1 (en) | Method of communication apparatus, method of user equipment (ue), communication apparatus, ue, method for first communication apparatus, method for communication terminal and method for first communication apparatus |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |