Method and system of providing carrier grade NAT (CGN) to a subset of a subscriber base

Patent metadata

Field	Value
Publication number	US-9860195-B2
Application number	US-201514986583-A
Country	US
Kind code	B2
Filing date	Dec 31, 2015
Priority date	Dec 31, 2015
Publication date	Jan 2, 2018
Grant date	Jan 2, 2018

Abstract

A method and system are disclosed for providing a service to bypass carrier grade network address translation (NAT), or CGN. A first and second range of private IPv4 addresses are generated for mapping to public IPv4 addresses. Subscribers to the service are provided terminals with a status code which indicates its status with respect to the service. The terminal is assigned a private internet protocol (IP) subnet within the first range of private IPv4 addresses, if the status code is indicative of a bypass status and the terminal identifies a bypass device that requires access to inbound traffic from the public network. Each bypass device is assigned a private IPv4 address from the first range, and the bypass device's private IPv4 address is mapped to a public IPv4 address. Inbound traffic having a matching public IPv4 destination address is subsequently directed to the bypass device.

First claim

What is claimed is:

1. A method comprising:
generating a first range of private internet protocol (IP) addresses for mapping to public IP addresses;
generating a second range of private IP addresses for mapping to the public IP addresses;
setting a status code for a terminal which facilitates communication between one or more devices and a public network, the status code being indicative of a predetermined status for the terminal;
identifying a bypass device configured to access the public network through the terminal and requiring access to inbound traffic from the public network, if the status code is indicative of a bypass status;
assigning a private IP subnet within the first range of private IP addresses to the terminal, if the status code is indicative of a bypass status;
assigning a private IP address from the subnet of the first range of private IP addresses to the bypass device;
mapping a public IP address to the private IP address assigned to the bypass device; and
directing inbound traffic whose destination address matches the public IP address mapped to the private IP address of the bypass device to the terminal, if the status code is indicative of a bypass status.

2. The method of claim 1 , further comprising validating the status code assigned to the terminal using a master list of active status codes.

3. The method of claim 1 , wherein the bypass device is identified using at least one of a media access control (MAC) address and a host name assigned thereto.

4. The method of claim 1 , wherein the bypass device is a router, and further comprising:
configuring virtual IP addresses for devices connected to the router; and
configuring port mapping rules between the devices connected to the router and the terminal.

5. The method of claim 1 , wherein:
the first range of private IP addresses supports 1:1 mapping with public IP addresses; and
the second range of private IP addresses supports 1:N mapping with public IP addresses.

6. The method of claim 5 , wherein the status code is indicative of non-bypass status, and further comprising:
assigning a private IP subnet within the second range of private IP addresses to the terminal;
assigning a private IP address within the subnet of the second range of private IP addresses to each of the one or more devices; and
mapping an available public IP address to the private IP address assigned to each device.

7. The method of claim 6 , further comprising directing inbound traffic whose destination address matches the public IP address mapped to the private IP address of a particular device to the terminal, only in response to outbound traffic initiated by the particular device.

8. The method of claim 1 , wherein:
the terminal performs a dynamic domain name server (DNS) request to achieve at least one of registering the public IP address mapped to a bypass device, updating the public IP address mapped to a bypass device, registering a hostname mapped to a bypass device, and updating a hostname mapped to a bypass device; and
the public IP address or hostname of the bypass device is obtainable from a DNS query.

9. The method of claim 1 , wherein directing inbound traffic comprises applying a 1:1 network address translation rule to map at least one of the public IP address and port number of the inbound traffic to at least one of the private IP address and port number assigned to the bypass device.

10. The method of claim 1 , wherein the bypass device exceeds a predetermined idle time period, and further comprising:
assigning a new private IP address from the subnet of the first range of private IP addresses to the bypass device;
mapping a new public IP address to the new private IP address assigned to the bypass device; and
performing a dynamic DNS request to achieve at least one of registering the new public IP address mapped to a bypass device, updating the new public IP address mapped to a bypass device, registering a new hostname mapped to a bypass device, and updating a new hostname mapped to a bypass device.

11. A system comprising:
a plurality of terminals, each terminal having one or more devices associated therewith, each terminal facilitating communication between the one or more devices and a public network, and each terminal being assigned status code indicative of a predetermined status therefor;
a gateway configured to route traffic between the plurality of terminals and the public network, the gateway comprising:
one or more first ports for at least one of transmitting to and receiving from the plurality of terminals,
one or more second ports for transmitting/receiving data to/from the public network; and
at least one processor configured to:
generate a first range of private internet protocol (IP) addresses for mapping to public IP addresses,
generate a second range of private IP addresses for mapping to the public IP addresses,
receive the status code of each terminal, and
assign a private IP subnet within the first range of private IP addresses to selected terminals having a status code is indicative of a bypass status,

wherein each terminal is configured to:
identify a bypass device configured to access the public network through the terminal and requiring access to inbound traffic from the public network, if the status code is indicative of a bypass status, and
assign a private IP address from the subnet of the first range of private IP addresses to the bypass device, and

wherein the gateway is further configured to:
map a public IP address to the private IP address assigned to the bypass device, and
direct inbound traffic whose destination address matches the public IP address mapped to the private IP address of the bypass device to the terminal, if the status code is indicative of a bypass status.

12. The system of claim 11 , wherein:
the gateway is configured to receive a master list of active status codes for the plurality of terminals; and
the at least one processor is further configured to validate the status code assigned to the plurality of terminals based, at least in part, on the received master list of active status codes.

13. The system of claim 11 , wherein the terminal is further configured to identify the bypass device using at least one of a media access control (MAC) address and a host name.

14. The system of claim 11 , wherein:
the bypass device is a router; and
the router is configured to generate virtual IP addresses for devices connected thereto, and generate port mapping rules between the devices connected thereto and the terminal.

15. The system of claim 11 , wherein:
the first range of private IP addresses supports 1:1 mapping with public IP addresses; and
the second range of private IP addresses supports 1:N mapping with public IP addresses.

16. The system of claim 15 , wherein:
the status code of a selected is indicative of non-bypass status, and the at least one processor is further configured to assign a private IP subnet within the second range of private IP addresses to the selected terminal;
the selected terminal is further configured to assign a private IP address within the subnet of the second range of private IP addresses to each of the one or more devices; and
the gateway is further configured to map an available public IP address to the private IP address assigned to each device.

17. The system of claim 16 , wherein the gateway is further configured to direct inbound traffic whose destination address matches the public IP address mapped to the private IP address of a particular device to the terminal, onl

Assignees

• Hughes Network Systems Llc

Inventors

• Javali Nagesh
• Jayant Ramakrishnan
• Torres Rob

Classifications

• H04L61/6095

  Electricity · mapped topic

• H04L49/25 Primary

  Routing or path finding in a switch fabric · CPC title

• H04L61/1511

  Electricity · mapped topic

• H04L61/6068

  Electricity · mapped topic

• H04L61/2553 Primary

  Binding renewal aspects, e.g. using keep-alive messages · CPC title