System and method for routing IP packets

• US 20020141389A1
• Filed: 07/11/2001
• Published: 10/03/2002
• Est. Priority Date: 04/03/2001
• Status: Active Grant

• Current Assignee: RPX Corporation
• Original Assignee: VoxPath Networks, Inc (IPNav)
• Inventors: Preston, Jason D., Fangman, Richard E.
• Granted Patent: US 7,068,647 B2
• Time in Patent Office: Days
• US Class Current: 370/352
• CPC Class Codes: H04L 61/2514 between local and global IP addresses
• CPC Class Codes: H04L 61/2517 using port numbers
• CPC Class Codes: H04L 61/2564 for a higher-layer protocol, e.g. for session initiation protocol [SIP]
• CPC Class Codes: H04L 61/5007 Internet protocol [IP] addresses
• CPC Class Codes: H04L 61/5014 using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
• CPC Class Codes: H04L 61/5038 for local use, e.g. in LAN or USB networks, or in a controller area network [CAN]
• CPC Class Codes: H04L 63/0272 Virtual private networks
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 65/1043 Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/65 Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
• CPC Class Codes: H04M 7/006 Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42
• CPC Class Codes: H04M 7/1285 Details of finding and selecting a gateway for a particular call

Abstract

System and method for routing packets for IP telephony. The system includes an IP telephone (IPT) and a Service Gateway (SG) coupled via a network. The SG receives a data packet from the IPT, including a private source IP address (SIPA), source port number (SPN), and destination information for an IP device, performs network address persistent port translation (NAPPT) on the data packet, and sends it to the IP device. NAPPT changes the private SIA to a public SIA, leaving the SPN unchanged. The SG receives a data packet from the IP device, including a public destination IP address (DIPA, i.e., said public SIPA), a destination port number (DPN, i.e., said SPN), and source information, NAPPTs the data packet, using the public DIPA and the DPN to identify the IPT, changing the public DIPA to the private SIPA, leaving the DPN unchanged, and sends the data packet to the IPT.

Claims

1. A method for performing IP telephony, comprising:

receiving a data packet from an IP telephone, wherein the data packet comprises a private source IP address, a source port number, and destination information associated with an IP device;

performing a network address persistent port translation (NAPPT) on the data packet; and

sending the data packet to the IP device.

2. The method of claim 1, wherein said performing a network address persistent port translation (NAPPT) on the data packet comprises changing the private source IP address to a public source IP address while leaving the source port number unchanged, and wherein the public source IP address and the source port number may be used to uniquely identify the IP telephone.

3. The method of claim 1, further comprising:

receiving a data packet from the IP device, wherein the data packet comprises a public destination IP address, a destination port number, and source information, wherein said public destination IP address comprises said public source IP address, and wherein said destination port number comprises said source port number;

performing a network address persistent port translation (NAPPT) on the data packet received from the IP device; and

sending the data packet received from the IP device to the IP telephone.

4. The method of claim 3, wherein said performing a network address persistent port translation (NAPPT) on the data packet received from the destination comprises using the public destination IP address and the destination port number to uniquely identify the IP telephone, and changing the public destination IP address to the private source IP address while leaving the destination port number unchanged.

5. The method of claim 3, wherein said source port number and said destination port number are in an assigned range of port numbers comprising ports which are not reserved for use by other IP protocols.

6. The method of claim 1, further comprising performing the following steps prior to said receiving said packet:

receiving an identifier from the IP telephone;

determining if the identifier is valid; and

if the identifier is valid, assigning a range of port numbers to the IP telephone based on the identifier, wherein the IP telephone is operable to use at least a subset of the range of port numbers to send or receive IP communications.

7. The method of claim 6, wherein said range of port numbers comprises ports which are not reserved for use by other IP protocols.

8. The method of claim 6, wherein the identifier comprises a vendor class identifier.

9. The method of claim 6, wherein said determining comprises:

determining if a MAC ID for the IP telephone is valid; and

if the MAC ID is determined to be valid, then determining if the identifier is valid.

10. The method of claim 6, wherein said identifier is comprised in a DHCP discover message, the method further comprising:

issuing a DHCP offer to the IP telephone if the identifier is determined to be valid, wherein the DHCP offer comprises DHCP lease information based on the validated identifier;

the IP telephone issuing a DHCP request in response to the issued DHCP offer;

storing the DHCP lease information in response to the issued DHCP request;

the IP telephone storing the DHCP lease information; and

the IP telephone enabling DHCP settings comprised in the DHCP lease information.

11. The method of claim 10,

wherein said DHCP lease information includes the range of port numbers and information indicating operational software for the IP telephone, the method further comprising:

the IP telephone executing the indicated operational software to enable said IP communications.

12. The method of claim 10,

wherein said DHCP lease information includes the range of port numbers and information indicating operational software for the IP telephone, the method further comprising:

the IP telephone issuing a request for the operational software;

providing the operational software to the IP telephone in response to the issued request; and

the IP telephone executing the provided operational software to enable said IP communications.

13. The method of claim 12, wherein the IP telephone issuing the request for the operational software comprises issuing a read request to a file transfer server, wherein said file transfer server performs said providing the operational software to the IP telephone.

14. The method of claim 13, wherein the file transfer server comprises a TFTP (Trivial File Transfer Protocol) server.

15. The method of claim 6, wherein the range of port numbers comprises one or more port numbers.

17. The system of claim 16, wherein, in performing a network address persistent port translation (NAPPT) on the data packet, the Service Gateway is operable to:

change the private source IP address to a public source IP address while leaving the source port number unchanged, and wherein the public source IP address and the source port number may be used to uniquely identify the IP telephone.

18. The system of claim 16, wherein the Service Gateway is further operable to:

receive a data packet from the IP device, wherein the data packet comprises a public destination IP address, a destination port number, and source information, wherein said public destination IP address comprises said public source IP address, and wherein said destination port number comprises said source port number;

perform a network address persistent port translation (NAPPT) on the data packet received from the IP device; and

send the data packet received from the IP device to the IP telephone.

19. The system of claim 18, wherein, in performing a network address persistent port translation (NAPPT) on the data packet received from the IP device, the Service Gateway is operable to:

use the public destination IP address and the destination port number to uniquely identify the IP telephone; and

change the public destination IP address to the private source IP address while leaving the destination port number unchanged.

20. The system of claim 18, wherein said source port number and said destination port number are in an assigned range of port numbers comprising ports which are not reserved for use by other IP protocols.

21. The system of claim 16, wherein, prior to said receiving said packet, the Service Gateway is further operable to:

receive an identifier from the IP telephone;

determine if the identifier is valid; and

if the identifier is valid, assign a range of port numbers to the IP telephone based on the identifier, wherein the IP telephone is operable to use at least a subset of the range of port numbers to send or receive IP communications.

22. The system of claim 21, wherein said range of port numbers comprises ports which are not reserved for use by other IP protocols.

23. The system of claim 21, wherein the identifier comprises a vendor class identifier.

24. The system of claim 21, wherein, in determining if the identifier is valid, the Service Gateway is operable to:

determine if a MAC ID for the IP telephone is valid; and

if the MAC ID is determined to be valid, then determine if the identifier is valid.

25. The system of claim 21, wherein said identifier is comprised in a DHCP discover message;

wherein the Service Gateway is further operable to issue a DHCP offer to the IP telephone if the identifier is determined to be valid, wherein the DHCP offer comprises DHCP lease information based on the validated identifier;

wherein the IP telephone is further operable to issue a DHCP request in response to the issued DHCP offer, store the DHCP lease information, and enable DHCP settings comprised in the DHCP lease information;

wherein the Service Gateway is further operable to store the DHCP lease information in response to the issued DHCP request.

26. The system of claim 25,

wherein said DHCP lease information includes the range of port numbers and information indicating operational software for the IP telephone;

wherein the IP telephone if further operable to execute the indicated operational software to enable said IP communications.

27. The system of claim 25,

wherein said DHCP lease information includes the range of port numbers and information indicating operational software for the IP telephone;

wherein the IP telephone is further operable to issue a request for the operational software;

wherein the Service Gateway is further operable to provide the operational software to the IP telephone in response to the issued request; and

wherein the IP telephone is further operable to execute the provided operational software to enable said IP communications.

28. The system of claim 27, further comprising:

a file transfer server;

wherein, in issuing the request for the operational software, the IP telephone is operable to issue a read request to the file transfer server, wherein said file transfer server is operable to provide the operational software to the IP telephone.

29. The system of claim 28, wherein the file transfer server comprises a TFTP (Trivial File Transfer Protocol) server.

30. The system of claim 29, wherein the file transfer server is comprised in the Service Gateway.

31. The system of claim 21, wherein the range of port numbers comprises one or more port numbers.

16. A system for performing IP telephony, comprising:

a network;

an IP telephone;

a Service Gateway, wherein the Service Gateway is operable to couple to the IP telephone through the network;

wherein the Service Gateway is further operable to;

receive a data packet from an IP telephone, wherein the data packet comprises a private source IP address, a source port number, and destination information associated with an IP device;

perform a network address persistent port translation (NAPPT) on the data packet; and

send the data packet to the IP device.

32. A memory medium, wherein the memory medium is operable to store program instructions which are executable to perform:

receiving a data packet from an IP telephone, wherein the data packet comprises a private source IP address, a source port number, and destination information associated with an IP device;

performing a network address persistent port translation (NAPPT) on the data packet; and

sending the data packet to the IP device.

33. The memory medium of claim 32, wherein said performing a network address persistent port translation (NAPPT) on the data packet comprises changing the private source IP address to a public source IP address while leaving the source port number unchanged, and wherein the public source IP address and the source port number may be used to uniquely identify the IP telephone.

34. The memory medium of claim 32, wherein the program instructions are further executable to perform:

receiving a data packet from the IP device, wherein the data packet comprises a public destination IP address, a destination port number, and source information, wherein said public destination IP address comprises said public source IP address, and wherein said destination port number comprises said source port number;

performing a network address persistent port translation (NAPPT) on the data packet received from the IP device; and

sending the data packet received from the IP device to the IP telephone.

35. The memory medium of claim 34, wherein said performing a network address persistent port translation (NAPPT) on the data packet received from the destination comprises using the public destination IP address and the destination port number to uniquely identify the IP telephone, and changing the public destination IP address to the private source IP address while leaving the destination port number unchanged.

36. The memory medium of claim 34, wherein said source port number and said destination port number are in an assigned range of port numbers comprising ports which are not reserved for use by other IP protocols.

37. The memory medium of claim 32, wherein the program instructions are further executable to perform the following steps prior to said receiving said packet:

receiving an identifier from the IP telephone;

determining if the identifier is valid; and

if the identifier is valid, assigning a range of port numbers to the IP telephone based on the identifier, wherein the IP telephone is operable to use at least a subset of the range of port numbers to send or receive IP communications.

38. The memory medium of claim 37, wherein said range of port numbers comprises ports which are not reserved for use by other IP protocols.

39. The memory medium of claim 37, wherein the identifier comprises a vendor class identifier.

40. The memory medium of claim 37, wherein said determining comprises:

determining if a MAC ID for the IP telephone is valid; and

if the MAC ID is determined to be valid, then determining if the identifier is valid.

41. The memory medium of claim 37, wherein said identifier is comprised in a DHCP discover message, and wherein the program instructions are further executable to perform:

issuing a DHCP offer to the IP telephone if the identifier is determined to be valid, wherein the DHCP offer comprises DHCP lease information based on the validated identifier;

receiving a DHCP request from the IP telephone in response to the issued DHCP offer; and

storing the DHCP lease information in response to the issued DHCP request;

wherein the DHCP lease information comprises DHCP settings which may be enabled by the IP telephone.

42. The memory medium of claim 41,

wherein said DHCP lease information includes the range of port numbers and information indicating operational software for the IP telephone;

and

wherein the indicated operational software is executable by the IP telephone to enable said IP communications.

43. The memory medium of claim 41,

wherein said DHCP lease information includes the range of port numbers and information indicating operational software for the IP telephone;

wherein the program instructions are further executable to perform;

receiving a request from the IP telephone for the operational software; and

providing the operational software to the IP telephone in response to the issued request;

wherein the indicated operational software is executable by the IP telephone to enable said IP communications.

44. The memory medium of claim 43, wherein the IP telephone issuing the request for the operational software comprises issuing a read request to a file transfer server, wherein said file transfer server performs said providing the operational software to the IP telephone.

45. The memory medium of claim 44, wherein the file transfer server comprises a TFTP (Trivial File Transfer Protocol) server.

46. The memory medium of claim 37, wherein the range of port numbers comprises one or more port numbers.