IP Library Granted Patent US 10,798,254
Granted Patent B2
US 10,798,254 · App. 16/216,479 · Granted Oct 6, 2020

Service design center for device assisted services

Inventors: Gregory G. Raleigh (Woodside, CA); James Lavine (Corte Madera, CA); Alireza Raissinia (Monte Sereno, CA); Justin James (Poway, CA); Jeffrey Green (Sunnyvale, CA)
Assignee: HEADWATER RESEARCH LLC
H04M15/723H04M15/70H04M15/72H04M15/80H04W4/24H04M15/46H04M15/58H04M15/66
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,798,254
App. No.
16/216,479
Filed
Dec 11, 2018
Granted
Oct 6, 2020
Kind
B2
Art Unit
3687
USPC
705/26.1
Abstract

A technique involves modular storage of network service plan components and provisioning of same. A subset of the capabilities of a service design system can be granted to a sandbox system to enable customization of service plan offerings or other controls.

Claims (21)

1. A method of operating a network provisioning system to provision wireless network service plans for a network provider network, the method comprising:

obtaining and storing, a first service plan component and a second service plan component,

the first service plan component comprising (i) information specifying a first traffic classification filter for filtering network traffic events and (ii) information specifying a first network policy enforcement action to be taken when a network traffic event possesses a characteristic that matches the first traffic classification filter,

the second service plan component comprising (a) information specifying a second traffic classification filter for filtering network traffic events, and (b) information specifying a second network policy enforcement action to be taken when a network traffic event possesses a characteristic that matches the second traffic classification filter,

wherein the sets of network traffic event characteristics that respectively match the first and second traffic classification filters are overlapping but not identical in extent;

receiving a user selection to, for a grouping of the first service plan component and the second service plan component as both applicable to a given wireless service plan, create a prioritization of the first traffic classification filter over the second traffic classification filter;

processing the first service plan component, the second service plan component, and the prioritization to create a service plan provisioning instruction set applicable to at least one wireless device; and

deploying the service plan provisioning instruction set to one or more devices in a network, such that for a network traffic event associated with the at least one wireless device and that matches both the first and second traffic classification filters, the one or more devices perform the first network policy enforcement action and do not perform the second network policy enforcement action.

2. The method of claim 1 , further comprising obtaining the first and second service plan components from a user operating a graphical user interface of the network service plan provisioning system.

3. The method of claim 1 , wherein processing the first service plan component, the second service plan component, and the prioritization to create a service plan provisioning instruction set applicable to at least one wireless device comprises creating the service plan provisioning instruction set such that after deployment to the one or more devices in the network, the one or more devices perform traffic inspection comparison operations such that the traffic inspection provisioning instructions determine whether a given network traffic event matches the first traffic classification filter before determining whether the given network traffic event matches the second traffic classification filter.

4. The method of claim 1 , wherein processing the first service plan component, the second service plan component, and the prioritization to create a service plan provisioning instruction set applicable to at least one wireless device comprises creating the service plan provisioning instruction set such that after deployment to the one or more devices in the network, the one or more devices perform traffic inspection comparison operations such that the traffic inspection provisioning instructions determine whether a given network traffic event matches the second traffic classification filter only after determining that the network traffic event does not match the first traffic classification filter.

5. The method of claim 1 , wherein processing the first service plan component, the second service plan component, and the prioritization to create a service plan provisioning instruction set applicable to at least one wireless device comprises creating the service plan provisioning instruction set such that after deployment to the one or more devices in the network, the one or more devices perform traffic inspection comparison operations such that the traffic inspection provisioning instructions determine whether a given network traffic event matches the second traffic classification filter, after determining that the given network traffic event matches the first traffic classification filter.

6. The method of claim 1 , and wherein receiving a user selection to create a prioritization of the first traffic classification filter over the second traffic classification filter comprises operating a graphical user interface to provide user selection of a policy enforcement priority rule from a policy enforcement priority rule datastore for application to the first and second service plan components.

7. The method of claim 6 , wherein the policy enforcement priority rule comprises a priority order for a plurality of traffic classification filters, the plurality of traffic classification filters including the first traffic classification filter and the second traffic classification filter.

8. The method of claim 1 , wherein the information specifying the first traffic classification filter comprises an inspection criterion selected from a group of inspection criteria consisting of: a specific device application, a specific network destination, a specific network source, a specific traffic type, a specific content type, a specific traffic protocol, and a combination of two or more of the inspection criteria.

9. The method of claim 1 , wherein the first or second policy enforcement action is an action selected from a group of actions consisting of: apply a traffic control policy; apply a service usage accounting, charging, or billing policy; apply a service notification policy; and a combination of two or more of the actions.

10. The method of claim 1 , further comprising facilitating user grouping of the first and second service plan components into a larger service plan object definition.

11. The method of claim 1 , wherein the one or more devices in the network comprise the at least one wireless device.

12. The method of claim 1 , wherein the first network policy enforcement action comprises a traffic control action.

13. The method of claim 12 , wherein the traffic control action specifies to allow, block, throttle, delay, or defer a network traffic event.

14. The method of claim 12 , wherein the traffic control action is conditionally applicable based on a network state, a device state, a service-plan-usage state, or a combination of these.

Assignments (4)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 4, 2022
From: RALEIGH, GREGORY; LAVINE, JAMES; RAISSINIA, ALIREZA; GREEN, JEFFREY; JAMES, JUSTIN
To: HEADWATER PARTNERS I LLC
Reel/Frame 058545/0627 →
CORRECTIVE ASSIGNMENT TO CORRECT THE NAME OF ASSIGNEE PREVIOUSLY RECORDED ON REEL 047769 FRAME 0398. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded May 12, 2020
From: RALEIGH, GREGORY; RAISSINIA, ALIREZA; LAVINE, JAMES; JAMES, JUSTIN
To: HEADWATER PARTNERS I LLC
Reel/Frame 052635/0762 →
MERGER AND CHANGE OF NAME Recorded Dec 13, 2018
From: HEADWATER PARTNERS I LLC; HEADWATER MANAGEMENT LLC
To: HEADWATER RESEARCH LLC
Reel/Frame 047768/0831 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 13, 2018
From: RALEIGH, GREGORY G.; RAISSINIA, ALIREZA; LAVINE, JAMES; JAMES, JUSTIN
To: HEADWATER RESEARCH LLC
Reel/Frame 047769/0398 →
Continuity (33)
Continuation 15446291 · Mar 1, 2017
Continuation 14541628 · Nov 14, 2014
Continuation 13248025 · Sep 28, 2011
Continuation In Part 13134028 · May 25, 2011
Continuation In Part 13134005 · May 25, 2011
Continuation In Part 12695021 · Jan 27, 2010
Continuation In Part 12380780 · Mar 2, 2009
Continuation In Part 12380780
Continuation In Part 12380778 · Mar 2, 2009
Provisional Application 61389547 · Oct 4, 2010
Provisional Application 61387243 · Sep 28, 2010
Provisional Application 61387247 · Sep 28, 2010
Provisional Application 61407358 · Oct 27, 2010
Provisional Application 61418507 · Dec 1, 2010
Provisional Application 61418509 · Dec 1, 2010
Provisional Application 61420727 · Dec 7, 2010
Provisional Application 61422565 · Dec 13, 2010
Provisional Application 61422572 · Dec 13, 2010
Provisional Application 61422574 · Dec 13, 2010
Provisional Application 61435564 · Jan 24, 2011
Provisional Application 61472606 · Apr 6, 2011
Provisional Application 61348022 · May 25, 2010
Provisional Application 61381159 · Sep 9, 2010
Provisional Application 61381162 · Sep 9, 2010
Provisional Application 61384456 · Sep 20, 2010
Provisional Application 61385020 · Sep 21, 2010
Provisional Application 61252151 · Oct 15, 2009
Provisional Application 61252153 · Oct 15, 2009
Provisional Application 61206354 · Jan 28, 2009
Provisional Application 61206944 · Feb 4, 2009
Provisional Application 61207393 · Feb 10, 2009
Provisional Application 61207739 · Feb 13, 2009
Related Publication 20190124209A1 · Apr 25, 2019
Cited By (3)
US 12,389,218 US 12,452,377 US 12,543,031