IP Library › Granted Patent US 9,967,241
Granted Patent B2
US 9,967,241 · App. 13/843,605 · Granted May 8, 2018

Persona based billing

Inventors: Uma V. Raman (Somerset, NJ); Eric R. Koob (Somerset, NJ); Paul M. Decker (Red Hill, PA); Steven Mancuso (Lebanon, NJ); Satish Kumar Hosanagara (Flanders, NJ); Shashi Neelakantan (Irving, TX); Bilal Wahid (Bedford, MA); William D. Versen (Prospect Heights, IL)
Assignees: Verizon Patent and Licensing Inc.; Cellco Partnership
H04L63/08G06Q30/04H04L45/00H04L63/0428H04L63/102H04L67/14H04W12/08
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 9,967,241
App. No.
13/843,605
Granted
May 8, 2018
Kind
B2
Abstract

A mobile device receives from a first client application a request to exchange first data over a mobile communication network. The mobile device determines whether the first client application is associated with a first persona or a second persona of a user. Upon determining the first client application is associated with the first persona, the mobile device establishes a first data connection based on a first Access Point Name (APN) network identifier with the mobile communication network and routes the first data over the first data connection. The mobile device also receives from a second client device a request to exchange second data over the mobile communication network. Upon determining the second client application is associated with the second persona, the mobile device establishes a second data connection based on a second APN network identifier with the mobile communication network and routes the second data over the second data connection.

Claims (66)

1. A method comprising:

receiving, from a first client application on a mobile device, a request to exchange first data over a mobile communication network;

upon receiving the request to exchange first data from the first client application, determining whether the first client application is associated with a first persona or a second persona of a user of the mobile device;

upon determining the first client application is associated with the first persona, establishing a first data connection based on a first Access Point Name (APN) network identifier between the device and the mobile communication network and routing the first data over the first data connection;

receiving, from a second client application on the mobile device, a request to exchange second data over a mobile communication network;

upon receiving the request to exchange second data from the second client application, determining whether the second client application is associated with the first persona or the second persona of the user of the mobile device; and

upon determining the second client application is associated with the second persona, establishing a second data connection based on a second APN network identifier between the device and the mobile communication network and routing the second data over the second data connection;

wherein the second persona corresponds to a business persona of the user; and

wherein one or more elements within the mobile communication network are configured to override the first persona by routing the first data over the second data connection, when it is determined that the first data cannot be routed over the first data connection because of insufficient funds in an account associated with the first persona.

2. The method of claim 1 , wherein the first persona corresponds to a personal persona of the user, the business persona is associated with work-related applications of the user and the personal persona is associated with applications other than work-related applications.

3. The method of claim 2 , wherein:

determining whether the first client application is associated with the personal persona or the business persona includes determining whether the first client application is housed within the second client application configured to house work-related applications of the user and establish an 800 PDN connection with the mobile communication network, and

determining the first client application is associated with the personal persona if the first client application is housed outside of the business data application on the mobile device.

4. The method of claim 2 , wherein:

determining whether the second client application is associated with the personal persona or the business persona includes determining whether the second client application is housed a business data application configured to establish an 800 PDN connection with the mobile communication network, and

determining the second client application is associated with the business persona if the second client application is housed within the business data application on the mobile device.

5. The method of claim 1 , wherein:

the first APN includes an Internet APN and the first data connection includes a connection to an Internet PDN, and

the second APN includes an 800 APN and the second data connection includes a connection to an 800 PDN.

6. The method of claim 1 , wherein the second client application is configured to house work-related applications and establish an 800 PDN connection with the network.

7. The method of claim 6 , wherein each application housed within the second client application is configured to access an IP address authorized to use the 800 PDN connection.

8. The method of claim 6 , further comprising:

requesting the user of the mobile device to provide authentication information for accessing the second client application;

receiving the authentication information; and

upon determining the received authentication information corresponds to authentication information associated with the second client application, enabling the user of the mobile device to access the second client application.

9. A mobile device comprising:

a processor; and

a memory storing executable instructions for causing the processor to:

receive, from a first client application on the mobile device, a request to exchange first data over a mobile communication network;

upon receiving the request to exchange first data from the first client application, determine whether the first client application is associated with a first persona or a second persona of a user of the mobile device;

upon determining the first client application is associated with the first persona, establish a first data connection based on a first APN network identifier between the device and the mobile communication network and route the first data over the first data connection;

receive, from a second client application on the mobile device, a request to exchange second data over a mobile communication network;

upon receiving the request to exchange second data from the second client application, determine whether the second client application is associated with the first persona or the second persona of the user of the mobile device; and

upon determining the second client application is associated with the second persona, establish a second data connection based on a second APN network identifier between the device and the mobile communication network and route the second data over the second data connection;

wherein the second persona corresponds to a business persona of the user; and

wherein one or more elements within the mobile communication network are configured to override the first persona by routing the first data over the second data connection, when it is determined that the first data cannot be routed over the first data connection because of insufficient funds in an account associated with the first persona.

10. The mobile device of claim 9 , wherein the first persona corresponds to a personal persona of the user, the business persona is associated with work-related applications of the user and the personal persona is associated with applications other than work-related applications.

11. The mobile device of claim 10 , wherein:

to determine whether the first client application is associated with the personal persona or the business persona the memory stores executable instructions for causing the processor to determine whether the first client application is housed within the second client application configured to house work-related applications of the user and establish an 800 PDN connection with the mobile communication network, and

the memory stores executable instructions for causing the processor to determine the first client application is associated with the personal persona if the first client application is housed outside of the business data application on the mobile device.

12. The mobile device of claim 10 , wherein:

to determine whether the second client application is associated with the personal persona or the business persona the memory stores executable instructions for causing the processor to determine whether the second client application is housed within a business data application configured to house work-related applications of the user and establish an 800 PDN connection with the mobile communication network, and

the memory stores executable instructions for causing the processor to determine the second client application is associated with the business persona if the second client application is housed within the business data application on the mobile device.

13. The mobile device of claim 9 , wherein:

the first APN includes an Internet APN and the first data connection includes a connection to an Internet PDN, and

the second APN includes an 800 APN and the second data connection includes a connection to an 800 PDN.

14. The mobile device of claim 9 , wherein the memory stores executable instructions for causing the processor to:

request the user of the mobile device to provide authentication information for accessing the second client application;

receive the authentication information; and

upon determining the received authentication information correspond to authentication information associated with the second client application, enable the user of the mobile device to access the second client application.

15. At least one non-transitory computer readable medium on which are stored instructions comprising instructions that when executed cause a programmable device to:

receive, from a first client application on a mobile device, a request to exchange first data over a mobile communication network;

upon receiving the request to exchange first data from the first client application, determine whether the first client application is associated with a first persona or a second persona of a user of the mobile device;

upon determining the first client application is associated with the first persona, establish a first data connection based on a first Access Point Name (APN) network identifier between the device and the mobile communication network and route the first data over the first data connection;

receive, from a second client application on the mobile device, a request to exchange second data over a mobile communication network;

upon receiving the request to exchange second data from the second client application, determine whether the second client application is associated with the first persona or the second persona of the user of the mobile device; and

upon determining the second client application is associated with the second persona, establish a second data connection based on a second APN network identifier between the device and the mobile communication network and route the second data over the second data connection;

wherein the second persona corresponds to a business persona of the user; and

wherein one or more elements within the mobile communication network are configured to override the first persona by routing the first data over the second data connection, when it is determined that the first data cannot be routed over the first data connection because of insufficient funds in an account associated with the first persona.

16. The computer readable medium of claim 15 , wherein the first persona corresponds to a personal persona of the user, the business persona is associated with work-related applications of the user and the personal persona is associated with applications other than work-related applications.

17. The computer readable medium of claim 15 , wherein: the first APN includes an Internet APN and the first data connection includes a connection to an Internet PDN, and the second APN includes an 800 APN and the second data connection includes a connection to an 800 PDN.

18. The computer readable medium of claim 15 , wherein the second client application is configured to house work-related applications and establish an 800 PDN connection with the network.

19. The computer readable medium of claim 15 , wherein the instructions when executed further cause the programmable device to:

request the user of the mobile device to provide authentication information for accessing the second client application;

receive the authentication information; and

upon determining the received authentication information corresponds to authentication information associated with the second client application, enable the user of the mobile device to access the second client application.

Assignments (2)
CORRECTIVE ASSIGNMENT TO CORRECT THE CONVEYING PARTY'S NAMES AND TO ADD AN 8TH INVENTOR OMITTED PREVIOUSLY PREVIOUSLY RECORDED AT REEL: 039607 FRAME: 0635. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT . Recorded Jan 17, 2018
From: RAMAN, UMA V.; KOOB, ERIC R.; DECKER, PAUL M.; MANCUSO, STEVEN; HOSANAGARA, SATISH KUMAR; NEELAKANTAN, SHASHI; WAHID, BILAL; VERSEN, WILLIAM D.
To: CELLCO PARTNERSHIP D/B/A VERIZON WIRELESS; VERIZON PATENT AND LICENSING INC.
Reel/Frame 045080/0530 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 31, 2016
From: RAMAN, UMA V; KOOB, ERIC R; DECKER, PAUL M; MANCUSO, STEVEN; HOSANAGARA, SATISH KUMAR; NEELAKANTAN, SASHI; WAHID, BILAL
To: CELLCO PARTNERSHIP D/B/A VERIZON WIRELESS
Reel/Frame 039607/0635 →
Continuity (1)
Related Publication 20140279454A1 · Sep 18, 2014