SYSTEMS AND METHOD FOR OFFLOADING COMMUNICATION SESSIONS TO LOCAL NETWORK RESOURCES

• US 20170034761A1
• Filed: 07/27/2015
• Published: 02/02/2017
• Est. Priority Date: 07/27/2015
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Inventors: Narayanan, Ram Gopal Lakshmi
• Granted Patent: US 9,723,155 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 12/1407 Policy-and-charging control [PCC] architecture
• CPC Class Codes: H04L 45/74 Address processing for routing
• CPC Class Codes: H04M 15/66 Policy and charging system
• CPC Class Codes: H04M 15/8228 Session based
• CPC Class Codes: H04W 4/24 Accounting or billing
• CPC Class Codes: H04W 40/20 based on geographic position or location

Abstract

Techniques described herein may be used to identify communication sessions (e.g., voice calls, video calls, etc.) that can be routed using local network resources, such as a base station to which the user devices are attached, and cause routing responsibilities for the session to be offloaded to the local network resources. Doing so may conserve network resources by alleviating the core network from having to support communication sessions that do not need to be routed through the core network. In turn, this may reduce the potential for network latency since: 1) core network resources will be more available to support sessions that actually need to be routed through the core network; and 2) sessions that do not need to be routed through the core network can be routed over shorter distances that involve fewer network devices (e.g., a based station).

Claims

1. A method performed by one or more network devices, comprising:

establishing, by the one or more network devices, a communication session involving user devices by routing the communication session through a core network of a wireless telecommunications network;

determining, by the one or more network devices, that the user devices are both attached to a single radio access network (RAN) of the wireless telecommunications network;

identifying, by the one or more network devices, the RAN to which the user devices are attached; and

causing, by the one or more network devices, the communication session to be routed locally by the RAN such that information sent between user devices during a remainder of the communication session is not routed through the core network.

2. The method of claim 1, further comprising:

receiving a notification that the communication session has been terminated;

receiving charging information, from the RAN, corresponding to the communication session;

combining the charging information with charging information collected by the one or more network devices while the communication session was routed through the core network; and

providing the combined charging information to a network device designated for enforcing charging policies for the wireless telecommunications network.

3. The method of claim 1, further comprising:

maintaining network address translation (NAT) information for the communication session while the communication session is routed locally by the RAN;

receiving a notification that the communication session has been terminated; and

deleting the NAT information in response to the notification.

4. The method of claim 1, wherein causing the communication session to be routed locally by the RAN includes:

logically separating a control plane for the communication session and a user plane for the communication session; and

causing the user plane for the communication session to be routed locally by the RAN.

5. The method of claim 1, wherein the RAN include an Enhanced Node B and the user devices are both attached to the Enhanced Node B.

6. The method of claim 1, wherein causing the communication session to be routed locally by the RAN includes:

communicating a request to the RAN to implement a hairpin routing technique with respect to the communication session.

7. The method of claim 1, further comprising:

determining an operational state of the wireless telecommunications network; and

determining whether to cause the communication session to be routed locally by the RAN based on the operational state.

8. One or more network devices, comprising:

a non-transitory memory device storing a plurality of processor-executable instructions; and

a processor configured to execute the processor-executable instructions, wherein executing the processor-executable instructions causes the processor to;

establish a communication session involving user devices by routing the communication session through a core network of a wireless telecommunications network;

determine that the user devices are both attached to a single radio access network (RAN) of the wireless telecommunications network;

identify the RAN to which the user devices are attached; and

cause the communication session to be routed locally by the RAN such that information sent between the user devices during a remainder of the communication session is not routed through the core network.

9. The one or more network devices of claim 8, wherein executing the processor-executable instructions causes the processor further to:

receive a notification that the communication session has been terminated;

receive charging information, from the RAN, corresponding to the communication session;

combine the charging information with charging information collected by the one or more network devices while the communication session was routed through the core network; and

provide the combined charging information to a network device designated for enforcing charging policies for the wireless telecommunications network.

10. The one or more network devices of claim 8, wherein executing the processor-executable instructions causes the processor further to:

maintain network address translation (NAT) information for the communication session while the communication session is routed locally by the RAN;

receive a notification that the communication session has been terminated; and

delete the NAT information in response to the notification.

11. The one or more network devices of claim 8, wherein to cause the communication session to be routed locally by the RAN, the processor-executable instructions cause the processor to:

logically separate a control plane for the communication session and a user plane for the communication session; and

cause the user plane for the communication session to be routed locally by the RAN.

12. The one or more network devices of claim 8, wherein the RAN include an Enhanced Node B and the user devices are both attached to the Enhanced Node B.

13. The one or more network devices of claim 8, wherein to cause the communication session to be routed locally by the RAN, the processor-executable instructions cause the processor to:

communicate a request to the RAN to implement a hairpin routing technique with respect to the communication session.

14. The one or more network devices of claim 8, wherein executing the processor-executable instructions causes the processor further to:

determine an operational state of the wireless telecommunications network; and

determine whether to cause the communication session to be routed locally by the RAN based on the operational state.

15. One or more network devices, comprising:

a non-transitory memory device storing a plurality of processor-executable instructions; and

a processor configured to execute the processor-executable instructions, wherein executing the processor-executable instructions causes the processor to;

create network address translation (NAT) information describing information sent between user devices during a call involving a core network of a wireless telecommunications network;

determine, based on the NAT information, that the user devices are both attached to a single Enhanced Node B (eNB) of the wireless telecommunications network;

identify the eNB to which the user devices are attached; and

generate a notification that the users devices are both attached to the single eNB to enable the call to be routed locally by the eNB and not the core network.

16. The one or more network devices of claim 15, wherein executing the processor-executable instructions causes the processor further to:

cause the call to be transferred from the core network to the eNB such that information sent to and from the user devices during the rest of the call is routed locally by the eNB and not the core network.

17. The one or more network devices of claim 16, wherein executing the processor-executable instructions causes the processor further to:

receive a notification that the call has been terminated;

receive charging information, from the eNB, corresponding to the rest of the call;

combine the charging information with charging information collected by the one or more network devices while the call involved the core network; and

provide the combined charging information to a network device designated for enforcing charging policies for the wireless telecommunications network.

18. The one or more network devices of claim 16, wherein executing the processor-executable instructions causes the processor further to:

maintain network address translation (NAT) information for the communication session while the communication session is routed locally by the eNB;

receive a notification that the communication session has been terminated; and

delete the NAT information in response to the notification.

19. The one or more network devices of claim 16, wherein to cause the call to be routed locally by the eNB, the processor-executable instructions cause the processor to:

logically separate a control plane for the call and a user plane for the call; and

cause the user plane for the communication session to be routed locally by the eNB.

20. The one or more network devices of claim 16, wherein to cause the communication session to be routed locally by the eNB, the processor-executable instructions cause the processor to:

communicate a request to the eNB to implement a hairpin routing technique with respect to the call.