IP Library › Granted Patent US 10,263,886
Granted Patent B2
US 10,263,886 · App. 15/051,624 · Granted Apr 16, 2019

Mobile endpoint network interface selection using merged policies

Inventors: Parameshwaran Krishnan (Basking Ridge, NJ); Prithviraj P. Patil (Nashville, TN); Navjot Singh (Somerset, NJ)
Assignee: Avaya Inc.
H04L45/56H04L45/306H04L47/20H04W76/10H04L45/42
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,263,886
App. No.
15/051,624
Granted
Apr 16, 2019
Kind
B2
Abstract

Methods, systems and computer readable media for mobile endpoint network interface selection using merged policies.

Claims (61)

1. A method comprising:

providing a mobile network switch (mNS) coupled to a mobile software defined network controller (mSDNC) and one or more network interfaces within a user device, wherein the mSDNC and the mNS are both housed within the user device;

receiving an indication at the mSDNC that the user device has connected to an enterprise network;

transmitting from the mSDNC to an enterprise software defined network controller (eSDNC) a request for policies of the enterprise network;

receiving at the mSDNC policies of the enterprise network from the eSDNC;

obtaining user preferences from the user device;

merging the policies and the user preferences into a set of merged policies;

configuring, at the mSDNC, the mNS based on the merged policies, wherein the mNS includes a first route that uses the enterprise network, and a second route that does not use the enterprise network; and

routing application traffic, using the mNS, within the user device based on configuration information from the mSDNC, wherein a first application traffic is routed via the first route to a first network interface associated with the enterprise network, and a second application traffic is routed via the second route to a second network interface not associated with the enterprise network.

2. The method of claim 1 , further comprising:

identifying, at the mSDNC, one or more applications within the user device associated with a given stream of message traffic based on information from an operating system of the user device.

3. The method of claim 1 , further comprising:

receiving, at the mSDNC, requirements for one or more applications from an operating system of the user device, the requirements provided by the applications to the operating system.

4. The method of claim 1 , further comprising:

obtaining application requirements from the user device; and

merging the application requirements with the policies and user preferences to generate the set of merged policies.

5. The method of claim 1 , wherein the network interfaces include a cellular network interface and a wireless network (WiFi) interface.

6. A system comprising:

one or more processors coupled to a nontransitory computer readable medium having stored thereon on software instructions that, when executed by the one or more processors, cause to perform operations including:

providing a mobile network switch (mNS) coupled to a mobile software defined network controller (mSDNC) and one or more network interfaces within a user device, wherein the mSDNC and the mNS are both housed within the user device;

receiving an indication at the mSDNC that the user device has connected to an enterprise network;

transmitting from the mSDNC to an enterprise software defined network controller (eSDNC) a request for policies of the enterprise network;

receiving at the mSDNC policies of the enterprise network from the eSDNC;

obtaining user preferences from the user device;

merging the policies and the user preferences into a set of merged policies;

configuring, at the mSDNC, the mNS based on the merged policies, wherein the mNS includes a first route that uses the enterprise network, and a second route that does not use the enterprise network; and

routing application traffic, using the mNS, within the user device to one of a plurality of network interfaces based on configuration information from the mSDNC, wherein a first application traffic is routed via the first route to a first network interface associated with the enterprise network, and a second application traffic is routed via the second route to a second network interface not associated with the enterprise network.

7. The system of claim 6 , wherein the operations further includes:

identifying, at the mSDNC, one or more applications within the user device associated with a given stream of message traffic based on information from an operating system of the user device.

8. The system of claim 6 , wherein the operations further include:

receiving at the mSDNC requirements for one or more applications from an operating system of the user device, the requirements provided by the applications to the operating system.

9. The system of claim 6 , wherein the operations further include:

obtaining application requirements from the user device; and

merging the application requirements with the policies and user preferences to generate the set of merged policies.

10. The system of claim 6 , wherein the network interfaces include a cellular network interface and a wireless network (WiFi) interface.

11. A nontransitory computer readable medium having stored thereon software instructions that, when executed by one or more processors, cause the one or more processors to perform operations including:

providing a mobile network switch (mNS) coupled to a mobile software defined network controller (mSDNC) and one or more network interfaces within a user device, wherein the mSDNC and the mNS are both housed within the user device;

receiving an indication at the mSDNC that the user device has connected to an enterprise network;

transmitting from the mSDNC to an enterprise software defined network controller (eSDNC) a request for policies of the enterprise network;

receiving at the mSDNC policies of the enterprise network from the eSDNC;

obtaining user preferences from the user device;

merging the policies and the user preferences into a set of merged policies;

configuring, at the mSDNC, the mNS based on the merged policies, wherein the mNS includes a first route that uses the enterprise network, and a second route that does not use the enterprise network; and

routing application traffic, using the mNS, within the user device to one of a plurality of network interfaces based on configuration information from the mSDNC, wherein a first application traffic is routed via the first route to a first network interface associated with the enterprise network, and a second application traffic is routed via the second route to a second network interface not associated with the enterprise network.

12. The nontransitory computer readable medium of claim 11 , wherein the operations further include:

identifying, at the mSDNC, one or more applications within the user device associated with a given stream of message traffic based on information from an operating system of the user device.

13. The nontransitory computer readable medium of claim 11 , wherein the operations further include:

receiving at the mSDNC requirements for one or more applications from an operating system of the user device, the requirements provided by the applications to the operating system.

14. The nontransitory computer readable medium of claim 11 , wherein the operations further include:

obtaining application requirements from the user device; and

merging the application requirements with the policies and user preferences to generate the set of merged policies.

15. The nontransitory computer readable medium of claim 11 , wherein the network interfaces include a cellular network interface and a wireless network (WiFi) interface.

16. The method of claim 1 , further comprising:

receiving, at the mSDNC, an indication from the eSDNC that the network inspects secure traffic; and

routing traffic for an application indicating a preference for direct communication when using a secure protocol to a network interface other than a network interface corresponding to the eSDNC.

17. The method of claim 4 , wherein obtaining application requirements from the user device includes obtaining application requirements corresponding to a given application from an operating system of the user device, where the application requirements are provided to the operation system by the given application during one or more of installation time, execution time, or update time of the given application.

18. The system of claim 6 , wherein the operations further include:

receiving, at the mSDNC, an indication from the eSDNC that the network inspects secure traffic; and

routing traffic for an application indicating a preference for direct communication when using a secure protocol to a network interface other than a network interface corresponding to the eSDNC.

19. The system of claim 9 , wherein obtaining application requirements from the user device includes obtaining application requirements corresponding to a given application from an operating system of the user device, where the application requirements are provided to the operation system by the given application during one or more of installation time, execution time, or update time of the given application.

20. The method of claim 1 , wherein configuring the mNS to include the first route is based at least on a first user preference of the user preferences, and configuring the mNS to include the second route is based at least on an access restriction policy of the mSDNC policies.

Assignments (17)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 14, 2026
From: AVAYA LLC
To: PULSELINK SYSTEMS LLC
Reel/Frame 074909/0627 →
INTELLECTUAL PROPERTY PARTIAL RELEASE AND REASSIGNMENT Recorded Feb 4, 2026
From: WILMINGTON SAVINGS FUND SOCIETY, FSB
To: AVAYA LLC (F/K/A AVAYA INC.); AVAYA MANAGEMENT L.P.
Reel/Frame 074981/0940 →
INTELLECTUAL PROPERTY PARTIAL RELEASE AND REASSIGNMENT Recorded Feb 4, 2026
From: CITIBANK, N.A.
To: AVAYA LLC (F/K/A AVAYA INC.); AVAYA MANAGEMENT L.P.
Reel/Frame 074944/0573 →
(SECURITY INTEREST) GRANTOR'S NAME CHANGE Recorded Sep 21, 2023
From: AVAYA INC.
To: AVAYA LLC
Reel/Frame 065019/0231 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 61087/0386) Recorded May 18, 2023
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063690/0359 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 53955/0436) Recorded May 18, 2023
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063705/0023 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001) Recorded May 18, 2023
From: GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT
To: AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC. (FORMER NAME OF AVAYA CLOUD INC.); HYPERQUALITY, INC.; HYPERQUALITY II, LLC; CAAS TECHNOLOGIES, LLC; AVAYA MANAGEMENT L.P.
Reel/Frame 063779/0622 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded May 4, 2023
From: AVAYA INC.; AVAYA MANAGEMENT L.P.; INTELLISIST, INC.
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 063542/0662 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded May 3, 2023
From: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; KNOAHSOFT INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB [COLLATERAL AGENT]
Reel/Frame 063742/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124/FRAME 0026 Recorded Apr 26, 2023
From: CITIBANK, N.A., AS COLLATERAL AGENT
To: AVAYA HOLDINGS CORP.; AVAYA INC.; AVAYA MANAGEMENT L.P.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063457/0001 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Aug 5, 2022
From: AVAYA INC.; INTELLISIST, INC.; AVAYA MANAGEMENT L.P.; AVAYA CABINET SOLUTIONS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 061087/0386 →
SECURITY INTEREST Recorded Sep 25, 2020
From: AVAYA INC.; AVAYA MANAGEMENT L.P.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION
Reel/Frame 053955/0436 →
SECURITY INTEREST Recorded Jan 23, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 045124/0026 →
SECURITY INTEREST Recorded Jan 10, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 045034/0001 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001 Recorded Dec 15, 2017
From: CITIBANK, N.A.
To: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS LLC (FORMERLY KNOWN AS OCTEL COMMUNICATIONS CORPORATION); VPNET TECHNOLOGIES, INC.
Reel/Frame 044893/0531 →
SECURITY INTEREST Recorded Jan 27, 2017
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS CORPORATION; VPNET TECHNOLOGIES, INC.
To: CITIBANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 041576/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 23, 2016
From: KRISHNAN, PARAMESHWARAN; PATIL, PRITHVIRAJ P.; SINGH, NAVJOT
To: AVAYA INC.
Reel/Frame 037805/0130 →
Continuity (1)
Related Publication 20170244633A1 · Aug 24, 2017