Method and apparatus for transmitting messages associated with internet protocol version 4 (IPv4) addresses on an internet protocol version 6 (IPv6) network

A computer-implemented method for transmitting messages associated with IPv4 addresses on an IPv6 network comprising: receiving, in a first message from an IPv4 network, an IPv4 address of a component in the IPv4 network; parsing the IPv4 address into a plurality of elements; creating a new host name for the IPv4 address based on the parsed plurality of elements; sending, to a domain name server (DNS) associated with the IPv6 network, a request to perform a DNS lookup of the host name; responsive to the DNS lookup request, receiving an IPv6 address; and processing the first message as if it were originally received with the IPv6 address.

BACKGROUND OF THE INVENTION

Field of the Invention

Embodiments of the present invention generally relate to a voice over internet protocol (VoIP) service, and more specifically, to methods and apparatus for transmitting messages associated with IPv4 addresses on an IPv6 network.

Description of the Related Art

Internet Protocol version 6 (IPv6) is the most recent version of the Internet Protocol (IP), the communications protocol that provides an identification and location system for computers on networks, and routes traffic across the Internet. IPv6 is meant to replace IPv4 due to the depletion of the pool of unallocated IPv4 addresses. Although many service providers currently use servers in the IPv4 network, some mobile device manufacturers require that the apps developed for their devices use the IPv6-only network.

A Domain Name System 64 (DNS64)/Network Address Translation 64 (NAT64) network, described in Internet Engineering Task Force (IETF) Request for Comments (RFC) Paper No. 3261 entitled, “DNS64: DNS Extensions for Network Address Translation from IPv6 Clients to IPv4 Servers,” incorporated herein by reference, is a technology to allow IPv6-only clients to receive special IPv6 addresses that are proxied to IPv4 addresses. This proxy service is then called NAT64. In other words, using the DNS64/NAT64 network, messages (i.e., IPv4 packets) may continue to be sent to clients over an IPv4 network even if the client sending the messages is on an IPv6 network. In current routing solutions, address mapping is performed between the physical layers and transport layers of a protocol stack on a packet-by-packet basis, such that each packet that is received with an IPv4 address, is modified and transmitted with an IPv6 address. However, the above IPv4 to IPv6 routing solution requires extensive modification of a provider's back-end systems where the translation is performed, as well as modification of each individual packet.

Therefore, there is a need in the art for an improved method and apparatus for transmitting messages associated with IPv4 addresses on an IPv6 network that builds on the above techniques.

SUMMARY

Embodiments of the present invention relate to a method for transmitting messages associated with IPv4 addresses on an IPv6 network, when an IPv4 address for a network component is received on an IPv6 network device is provided. The method comprises receiving, in a first message from an IPv4 network, an IPv4 address of a component in the IPv4 network, parsing the IPv4 address into a plurality of elements; creating a new host name for the IPv4 address based on the parsed plurality of elements, and sending to a domain name server (DNS) associated with the IPv6 network, a request to perform a DNS lookup of the host name. In response to the DNS lookup request, an IPv6 address is received. The first message is processed as if it were originally received with the IPv6 address.

Further embodiments relate to a client device that is connected to an IPv6 network, wherein the client application is preconfigured with an IP address conversion format and configured to receive, in a first message from the IPv4 network, an IPv4 address of a component in the IPv4 network; parse the IPv4 address into a plurality of elements; create a new host name for the IPv4 address based on the parsed plurality of elements; send, to a domain name server (DNS) associated with the IPv6 network, a request to perform a DNS lookup of the host name; responsive to the DNS lookup request, receive an IPv6 address; and process the first request as if it were received with the IPv6 address.

A computer-implemented method for transmitting messages associated with IPv4 addresses on an IPv6 network, when an IPv4 address for a network component is received on an IPv6 network device is provided. The computer-implemented method comprises: receiving, in a first message from an IPv4 network, an IPv4 address of a component in the IPv4 network, parsing the IPv4 address into a plurality of elements; creating a new host name for the IPv4 address based on the parsed plurality of elements, and sending to a domain name server (DNS) associated with the IPv6 network, a request to perform a DNS lookup of the host name. In response to the DNS lookup request, an IPv6 address is received. The first message is processed as if it were originally received with the IPv6 address.

DETAILED DESCRIPTION

Embodiments of the present invention generally relate to methods and apparatus for transmitting messages/packets associated with IPv4 addresses on an IPv6 network. According to an exemplary embodiment, when a message, for example, a request, response, media, or the like is received on a client device, the message includes an address where a response is to be sent. A response, as used herein, includes a message response, media, future requests, and the like. The client device is on an IPv6 network however, the address is typically an IPv4 address. An application on the client device converts the IPv4 address to a new host name, and sends the converted host name to a DNS64 server, which returns an IPv6 address. The client application transmits the response message to the returned IPv6 address as if the received message were originally received with the IPv6 address. From then on, when the client device sends a message on the IPv6 network, the message is routed to the network component associated with the IPv4 address originally received in the message. As used herein, messages and packets associated with IPv4 addresses include, but are not limited to, SIP responses, requests, media packets, and the like that include or are otherwise directed to IPv4 addresses.

Some exemplary embodiments described below are with respect to a mobile Voice over Internet Protocol (VOIP) telecommunication app. However, one skilled in the art will readily recognize from the following description that any native application may be used in embodiments consistent with the present invention without departing from the principles of the disclosure described herein.

In the following description, the terms VOIP system, VOIP telephony system, IP system and IP telephony system are all intended to refer to a system that connects callers and that delivers data, text, video, and voice communications using Internet protocol data communications. Those of ordinary skill in the art will recognize that embodiments of the present invention are not limited to use with IP telephony systems and may also be used in other systems.

As illustrated inFIG. 1, a communications environment100is provided to facilitate IP enhanced communications. An IP telephony system120enables connection of telephone calls between its own customers and other parties via data communications that pass over a data network110. The data network110is commonly the Internet, although the IP telephony system120may also make use of private data networks. The IP telephony system120is connected to the Internet110. In addition, the IP telephony system120is connected to a publicly switched telephone network (PSTN)130via a gateway122. The PSTN130may also be directly coupled to the Internet110through one of its own internal gateways (not shown). Thus, communications may pass back and forth between the IP telephony system120and the PSTN130through the Internet110via a gateway maintained within the PSTN130.

The gateway122allows users and devices that are connected to the PSTN130to connect with users and devices that are reachable through the IP telephony system120, and vice versa. In some instances, the gateway122would be a part of the IP telephony system120. In other instances, the gateway122could be maintained by a third party.

Customers of the IP telephony system120can place and receive telephone calls using an IP telephone108that is connected to the Internet110. Such an IP telephone108could be connected to an Internet service provider via a wired connection or via a wireless router. In some instances, the IP telephone108could utilize a packet-switched network of a cellular telephone system to access the Internet110.

Alternatively, a customer could utilize an analog telephone102which is connected to the Internet110via a telephone adapter104. The telephone adapter104converts analog signals from the telephone102into data signals that pass over the Internet110, and vice versa. Analog telephone devices include but are not limited to standard telephones and document imaging devices such as facsimile machines. A configuration using a telephone adapter104is common where the analog telephone102is located in a residence or business. Other configurations are also possible where multiple analog telephones share access through the same IP adaptor. In those situations, all analog telephones could share the same telephone number, or multiple communication lines (e.g., additional telephone numbers) may provisioned by the IP telephony system120.

In addition, a customer could utilize a soft-phone client running on a computer106or a television109to place and receive IP based telephone calls, and to access other IP telephony systems (not shown). The computer106may be a personal computer (PC), a tablet device, a gaming system, and the like. In some instances, the soft-phone client could be assigned its own telephone number. In other instances, the soft-phone client could be associated with a telephone number that is also assigned to an IP telephone108, or to a telephone adaptor104that is connected to one or more analog telephones102.

Users of the IP telephony system120are able to access the service from virtually any location where they can connect to the Internet110. Thus, a customer could register with an IP telephony system provider in the U.S., and that customer could then use an IP telephone108located in a country outside the U.S. to access the services. Likewise, the customer could also utilize a computer outside the U.S. that is running a soft-phone client to access the IP telephony system120.

A third party using an analog telephone132which is connected to the PSTN130may call a customer of the IP telephony system120. In this instance, the call is initially connected from the analog telephone132to the PSTN130, and then from the PSTN130, through the gateway122to the IP telephony system120. The IP telephony system120then routes the call to the customer's IP telephony device. A third party using a cellular telephone134could also place a call to an IP telephony system customer, and the connection would be established in a similar manner, although the first link would involve communications between the cellular telephone134and a cellular telephone network. For purposes of this explanation, the cellular telephone network is considered part of the PSTN130.

In the following description, references will be made to an “IP telephony device.” This term is used to refer to any type of device which is capable of interacting with an IP telephony system to complete an audio or video telephone call or to send and receive text messages, and other forms of communications. An IP telephony device could be an IP telephone, a computer running IP telephony software, a telephone adapter which is itself connected to a normal analog telephone, or some other type of device capable of communicating via data packets. An IP telephony device could also be a cellular telephone or a portable computing device that runs a software application that enables the device to act as an IP telephone. Thus, a single device might be capable of operating as both a cellular telephone that can facilitate voice based session calls, and an IP telephone that can facilitate data based session calls.

The following description will also refer to a mobile telephony device. The term “mobile telephony device” is intended to encompass multiple different types of devices. In some instances, a mobile telephony device could be a cellular telephone. In other instances, a mobile telephony device may be a mobile computing device, such as the APPLE IPHONE, that includes both cellular telephone capabilities and a wireless data transceiver that can establish a wireless data connection to a data network. Such a mobile computing device could run appropriate application software to conduct VoIP telephone calls via a wireless data connection. Thus, a mobile computing device, such as an APPLE IPHONE, a RIM BLACKBERRY or a comparable device running GOOGLE ANDROID operating system could be a mobile telephony device.

In still other instances, a mobile telephony device may be a device that is not traditionally used as a telephony device, but which includes a wireless data transceiver that can establish a wireless data connection to a data network. Examples of such devices include the APPLE IPOD TOUCH and the IPAD. Such a device may act as a mobile telephony device once it is configured with appropriate application software.

FIG. 1illustrates that a mobile computing device with cellular capabilities136A(e.g., a smartphone) is capable of establishing a first wireless data connection A with a first wireless access point140, such as a wireless local area network (WLAN) based on the Institute of Electrical and Electronics Engineers' (IEEE) 802.11 and 802.13 standards router. The first wireless access point140is coupled to the Internet110. Thus, the mobile computing device136Acan establish a VOIP telephone call with the IP telephony system120via a path through the Internet110and the first wireless access point140.

FIG. 1also illustrates that the mobile computing device136Acan establish a second wireless data connection B with a second wireless access point142that is also coupled to the Internet110. Further, the mobile computing device136Acan establish either a third wireless data connection C via a packet-switched network provided by a cellular service provider130using its cellular telephone capabilities, or establish a voice based session telephone call via a circuit-switched network provided by a cellular service provider130. The mobile computing device136Acould also establish a VoIP telephone call with the IP telephony system120via the second wireless connection B or the third wireless connection C.

Similarly, mobile computing device with cellular capabilities136Bmay also be coupled to internet110and/or cellular service provider130. In some embodiments, mobile computing device136Bmay be connected to internet110via a wireless local area network (WLAN) based on the Institute of Electrical and Electronics Engineers' (IEEE) 802.11 and 802.13 standards connection, and the like, and can also establish a VOIP telephone call with the IP telephony system120similar to mobile computing device136A. In embodiments of the present invention, communications environment100may be used to establish voice based or data based telecommunications sessions between mobile computing device136Aand mobile computing device136B, depending on various criteria associated with each of the mobile computing devices, as will be described below in more detail.

In the embodiments described above, a device may act as a mobile telephony device once it is configured with appropriate application software that may be downloaded from an app distribution platform144. For example, mobile computing device136Amay download a VOIP mobile app from app distribution platform144and install the VOIP mobile app locally making the app a native application running on mobile computing device136A.

FIG. 2is a more detailed depiction of the communication system200including components used to transmit messages associated with IPv4 addresses on an IPv6 network, according to one or more embodiments of the invention. The exemplary communication system200includes an IPv6 network202and an IPv4 network204, wherein communication is facilitated via a DNS64/NAT64206. The IPv6 network202includes a first client device208(i.e., an IPv6 client) and a DNS server210. The IPv4 network204includes a second client device212(i.e., an IPv4 client), a service provider system214, and a DNS server216.

The two devices208and212are connected to their respective IP networks202.204that may use Session Initiation Protocol (SIP), Voice over Internet Protocol (VoIP), and the like to form a communication session. The details and functionality of SIP can be found in the Internet Engineering Task Force (IETF) Request for Comments (RFC) Paper No. 3261 entitled, “SIP: Session Initiation Protocol,” that is herein incorporated in its entirety by reference. The first and second devices (208,212) may be electronic user devices (e.g., telephones, personal computers, laptops, smart phones, mobile phones, tablets, and the like).

Each IP network202,204allows for user devices (wired or wireless) to exchange data and voice communications, and is capable of processing the sending and receiving of both voice and data streams between the first client device208and the second client device212.

The first client device208includes a CPU220, support circuits222, and memory224. The memory224includes an operating system226, a communication module228, and a mobile app230. The mobile app230includes an IPv4 address converter232and an IPv6 address format234. The IPv4 address converter232includes instructions executable by the CPU220to modify SIP signaling information to allow the first client device208on the IPv6 network202to communicate with the second client device212on the IPv4 network204. The DNS64/NAT64206is a DNS64 server which generates IPv6 addresses from IPv4 addresses. The NAT64 component stores the mapping of the addresses, such that it can later perform a translation of IPv6 to IPv4 in order to route messages between the IPv6 network202and the IPv4 network204. The service provider system214includes other servers218which may include, but are not limited to proxy servers, registrars, media relays, gateways, or other components on an IPv4 network used to facilitate communication between the first client device208and the second client device212. The DNS server216includes a database with entries that identify host names, and convert from the host name to a physical IPv4 address or a Canonical Name (CNAME) for each of the service provider's back-end components on the IPv4 network through which the client may communicate.

When the client device208receives a message, for example, a SIP signaling request or the message may be SIP message with SDP in the message body, the message includes an address that identifies the location of a component in the IPv4 network where a response to the SIP request or future requests are to be sent (or where to send media packets to and/or expect to receive media packets from). The message may be a request, a response, media, or the like. The address may be anywhere in the message and may be in plain text, Extensible Markup Language (XML), JavaScript Object Notation (JSON), or the like. The address is typically an IPv4 address. Since the client device208is on an IPv6-only network, the client device208cannot send a response to the IPv4 address. Although the present disclosure is written using a SIP request as an exemplary embodiment, the terms message and response apply to all signaling and media packets that are received on an IPv6 network and transmitted to an IPv4 network.

The IPv4 address converter232extracts the IPv4 address from the message and parses the IPv4 address to generate a new host name using the IPv4 address. The new host name is formatted in accordance with the IPv6 address format234. The IPv4 converter232sends the new host name to the NAT64/DNS64206. The NAT64/DNS64206accesses the service provider's DNS server216to extract the information in the DNS record associated with the host name/IPv4 address. The NAT64/DNS64206generates a new IPv6 address from the retrieved information, stores a mapping to/from the IPv4 and IPv6 addresses and returns the IPv6 address to the mobile app230. The communication module228transmits the response message as usual, as if the original message included to IPv6 address. Because the NAT64206stored the mapping of the addresses when the IPv6 address was created, the NAT64206can translate the IPv6 address back to the IPv4 address, such that the NAT64206can forward any messages to the IPv4 address from the IPv6 network202.

FIG. 3depicts a flow diagram for a method300for transmitting messages associated with IPv4 addresses on an IPv6 network, in accordance with previous embodiment of the present invention as depicted inFIG. 2. The method300is performed by the mobile app230on the client device208.

The method300begins at step302and proceeds to step304. At step304, a message is received on a client device, where the client device is on an IPv6-only network. The message may be a SIP signaling message used for setting up a communication session. The message may be SIP message with SDP in the message body. For example, the message may be a SIP message that includes the address of the initiating mobile device that is on an IPv4 network. Alternately, the message may be received from a proxy server, registrar, media relay, gateway, or other component on an IPv4 network. The message includes the address that identifies the location of the transmitting component on the IPv4 network. The IPv4 address received by the client on the IPv6-only network cannot be used on the IPv6-only network to send and receive media, messages, and the like. An IPv6 address associated with the component is required.

At step306, the IPv4 address received in the SIP message is parsed and translated into a host name. An IPv4 address is in the form of a.b.c.d. The IPv4 address is translated into a host name using the IPv6 address format. The IPv6 address format may be determined using an API call or hard-coded into the mobile application. For example, the IPv6 address may be in the format prefix_a_b_c_d_posfix.vonage.com, thereby creating a new host name for the IPv4 address. In some embodiments, the components of the IPv4 address are hashed and the new host name is constructed using the hash.

At step308, the new host name is used to send a query through a DNS64 server. The DNS64 server includes a NAT64 component. The NAT64 takes the IPv4 address and, using the host name, performs a lookup for a DNS record that has been pre-configured on the service provider's DNS server. The DNS64 configures a new IPv6 address based on the DNS record. The NAT64 stores the IPv4 address with the IPv6 address, and returns the IPv6 address.

At step310, the IPv6 address is received from the NAT64/DNS64 server. At step312, message is processed as if it were originally received with the IPv6 address. The IPv4 address is replaced with the received IPv6 address on the client device. The address is changed internally on the client device, leaving the received message unchanged. The message is then processed using the received IPv6 address. For example, a response to the message may be sent to the IPv6 address. In the event the message was an SDP message, a connection on the IPv6 address may be opened for transmitting and receiving media. The mobile device may store the received IPv6 address in association with the original IPv4 address. The mobile device continues to transmit and receive messages, responses, media packets, and the like as if it received the IPv6 address in the original message. Since the IPv6 address was received from the NAT64, the NAT64 can forward each packet to the correct IPv4 address outside of the IPv6 network. The method ends at step314.

The present invention overcomes a number of limitations inherent in current solutions. The use of the IPv6 address format to create a new host name is in contrast to a reverse DNS lookup, where a query for an IPv4 address of a.b.c.d would result in a query of d.c.b.a.-in-addr.arpa. The use of the DNS host name format for reverse DNS lookups requires a service provider to perform some routing tasks, rather than having said tasks performed by the client device, as described in the present disclosure. In addition, the use of a tunneling server to tunnel communications from the IPv6 network to the IPv4 network may be used for various network protocols that are encapsulated using a Hypertext Transfer Protocol (HTTP) protocol. However, this solution requires IP address literals, meaning that if a device is on an IPv6 network and the device receives a Session Description Protocol (SDP) formatted with an IPv4 address, the device is unable to communicate without a tunneling solution. The present invention overcomes this limitation of the SDP protocol by dynamically generating a new host name and using the DNS64 for generating an IPv6 address. As such an IP address literal is not used, thereby alleviating the need to use the HTTP tunneling.

FIG. 4depicts a computer system400that can be utilized in various embodiments of the present invention to implement the computer and/or the display, according to one or more embodiments.

Various embodiments of method and apparatus for converting from an IPv4 network to an IPv6 network, as described herein, may be executed on one or more computer systems, which may interact with various other devices. One such computer system is computer system400illustrated byFIG. 4, which may in various embodiments implement any of the elements or functionality illustrated inFIGS. 1-3. In various embodiments, computer system400may be configured to implement methods described above. The computer system400may be used to implement any other system, device, element, functionality or method of the above-described embodiments. In the illustrated embodiments, computer system400may be configured to implement the method300as processor-executable executable program instructions422(e.g., program instructions executable by processor(s)410) in various embodiments.

In the illustrated embodiment, computer system400includes one or more processors410a-410ncoupled to a system memory420via an input/output (I/O) interface430. Computer system400further includes a network interface440coupled to I/O interface430, and one or more input/output devices450, such as cursor control device460, keyboard470, and display(s)480. In various embodiments, any of the components may be utilized by the system to receive user input described above. In various embodiments, a user interface may be generated and displayed on display480. In some cases, it is contemplated that embodiments may be implemented using a single instance of computer system400, while in other embodiments multiple such systems, or multiple nodes making up computer system400, may be configured to host different portions or instances of various embodiments. For example, in one embodiment some elements may be implemented via one or more nodes of computer system400that are distinct from those nodes implementing other elements. In another example, multiple nodes may implement computer system400in a distributed manner.

In various embodiments, computer system400may be a uniprocessor system including one processor410, or a multiprocessor system including several processors410(e.g., two, four, eight, or another suitable number). Processors410may be any suitable processor capable of executing instructions. For example, in various embodiments processors410may be general-purpose or embedded processors implementing any of a variety of instruction set architectures (ISAs). In multiprocessor systems, each of processors410may commonly, but not necessarily, implement the same ISA.

System memory420may be configured to store program instructions422and/or data432accessible by processor410. In various embodiments, system memory420may be implemented using any suitable memory technology, such as static random access memory (SRAM), synchronous dynamic RAM (SDRAM), nonvolatile/Flash-type memory, or any other type of memory. In the illustrated embodiment, program instructions and data implementing any of the elements of the embodiments described above may be stored within system memory420. In other embodiments, program instructions and/or data may be received, sent or stored upon different types of computer-accessible media or on similar media separate from system memory420or computer system400.

In one embodiment, I/O interface430may be configured to coordinate I/O traffic between processor410, system memory420, and any peripheral devices in the device, including network interface440or other peripheral interfaces, such as input/output devices450. In some embodiments, I/O interface430may perform any necessary protocol, timing or other data transformations to convert data signals from one component (e.g., system memory420) into a format suitable for use by another component (e.g., processor410). In some embodiments, I/O interface430may include support for devices attached through various types of peripheral buses, such as a variant of the Peripheral Component Interconnect (PCI) bus standard or the Universal Serial Bus (USB) standard, for example. In some embodiments, the function of I/O interface430may be split into two or more separate components, such as a north bridge and a south bridge, for example. Also, in some embodiments some or all of the functionality of I/O interface430, such as an interface to system memory420, may be incorporated directly into processor410.

Input/output devices450may, in some embodiments, include one or more display terminals, keyboards, keypads, touchpads, scanning devices, voice or optical recognition devices, or any other devices suitable for entering or accessing data by one or more computer systems400. Multiple input/output devices450may be present in computer system400or may be distributed on various nodes of computer system400. In some embodiments, similar input/output devices may be separate from computer system400and may interact with one or more nodes of computer system400through a wired or wireless connection, such as over network interface440.

In some embodiments, the illustrated computer system may implement any of the operations and methods described above, such as the operations described with respect toFIG. 2and the method illustrated by the flowchart ofFIG. 3. In other embodiments, different elements and data may be included.