Network Based Service Profile Management with User Preference, Adaptive Policy, Network Neutrality, and User Privacy

• US 20120134291A1
• Filed: 02/07/2012
• Published: 05/31/2012
• Est. Priority Date: 01/28/2009
• Status: Active Grant

• Current Assignee: Headwater Research LLC (Greg Raleigh)
• Original Assignee: Headwater Partners I LLC (Greg Raleigh)
• Inventors: Raleigh, Gregory G.
• Granted Patent: US 9,014,026 B2
• Time in Patent Office: Days
• US Class Current: 370/252
• CPC Class Codes: G06F 15/177 Initialisation or configuration control processor initialisation G06F9/4405
• CPC Class Codes: G06Q 10/06315 Needs-based resource requirements planning or analysis
• CPC Class Codes: G06Q 10/06375 Prediction of business process outcome or impact based on a proposed change
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/32 using wireless devices
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 30/0207 Discounts or incentives, e.g. coupons or rebates
• CPC Class Codes: G06Q 30/0241 Advertisements
• CPC Class Codes: G06Q 30/0283 Price estimation or determination
• CPC Class Codes: G06Q 30/0284 Time or distance, e.g. usage of parking meters or taximeters
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/12 Accounting
• CPC Class Codes: H04L 12/14 Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 12/1407 Policy-and-charging control [PCC] architecture
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/0876 Aspects of the degree of configuration automation
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0894 : Policy-based network configuration management
• CPC Class Codes: H04L 41/5003 : Managing SLA; Interaction between SLA and QoS
• CPC Class Codes: H04L 41/5025 : by proactively reacting to service quality change, e.g. by reconfiguration after service quality degradation or upgrade
• CPC Class Codes: H04L 41/5054 : Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
• CPC Class Codes: H04L 47/20 : Traffic policing
• CPC Class Codes: H04L 47/2408 : for supporting different services, e.g. a differentiated services [DiffServ] type of service
• CPC Class Codes: H04L 51/046 : Interoperability with other network applications or services
• CPC Class Codes: H04L 63/0236 : Filtering by address, protocol, port number or service, e.g. IP-address or URL
• CPC Class Codes: H04L 63/04 : for providing a confidential data exchange among entities communicating through data packet networks
• CPC Class Codes: H04L 63/0428 : wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/08 : for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0853 : using an additional device, e.g. smartcard, SIM or a different communication terminal cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234
• CPC Class Codes: H04L 63/0892 : by using authentication-authorization-accounting [AAA] servers or protocols
• CPC Class Codes: H04L 63/10 : for controlling access to devices or network resources
• CPC Class Codes: H04L 63/20 : for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 67/145 : avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
• CPC Class Codes: H04L 67/306 : User profiles
• CPC Class Codes: H04L 67/34 : involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/51 : Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/55 : Push-based network services
• CPC Class Codes: H04L 67/564 : Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/63 : Routing a service request depending on the request content or context
• CPC Class Codes: H04L 9/32 : including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
• CPC Class Codes: H04L 9/3247 : involving digital signatures
• CPC Class Codes: H04M 15/00 : Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
• CPC Class Codes: H04M 15/49 : Connection to several service providers
• CPC Class Codes: H04M 15/58 : based on statistics of usage or network monitoring
• CPC Class Codes: H04M 15/61 : based on the service used
• CPC Class Codes: H04M 15/66 : Policy and charging system
• CPC Class Codes: H04M 15/80 : Rating or billing plans; Tariff determination aspects
• CPC Class Codes: H04M 15/8055 : Selecting cheaper transport technology for a given service
• CPC Class Codes: H04M 15/88 : Provision for limiting connection, or expenditure
• CPC Class Codes: H04M 2215/0188 : Network monitoring; statistics on usage on called/calling number
• CPC Class Codes: H04W 12/00 : Security arrangements; Authentication; Protecting privacy or anonymity
• CPC Class Codes: H04W 12/02 : Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
• CPC Class Codes: H04W 12/037 : of the control plane, e.g. signalling traffic
• CPC Class Codes: H04W 12/06 : Authentication
• CPC Class Codes: H04W 12/08 : Access security
• CPC Class Codes: H04W 12/37 : Managing security policies for mobile devices or for controlling mobile applications
• CPC Class Codes: H04W 24/08 : Testing, supervising or monitoring using real traffic
• CPC Class Codes: H04W 28/02 : Traffic management, e.g. flow control or congestion control
• CPC Class Codes: H04W 28/0215 : based on user or device properties, e.g. MTC-capable devices services for machine-to-machine communication [M2M] or machine type communication [MTC] H04W4/70; wireless resource selection or allocation plan definition based on terminal or device properties H04W72/51
• CPC Class Codes: H04W 28/0268 : using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR] negotiating SLA or negotiating QoS H04W28/24
• CPC Class Codes: H04W 28/12 : using signalling between network elements
• CPC Class Codes: H04W 4/02 : Services making use of location information
• CPC Class Codes: H04W 4/12 : Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 4/18 : Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
• CPC Class Codes: H04W 4/20 : Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
• CPC Class Codes: H04W 4/24 : Accounting or billing
• CPC Class Codes: H04W 4/50 : Service provisioning or reconfiguring
• CPC Class Codes: H04W 48/14 : using user query or user detection
• CPC Class Codes: H04W 48/16 : Discovering, processing access restriction or access information
• CPC Class Codes: H04W 72/0453 : Resources in frequency domain, e.g. a carrier in FDMA
• CPC Class Codes: H04W 8/02 : Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
• CPC Class Codes: H04W 8/18 : Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
• CPC Class Codes: H04W 8/20 : Transfer of user or subscriber data
• CPC Class Codes: H04W 84/04 : Large scale networks; Deep hierarchical networks
• CPC Class Codes: H04W 84/042 : Public Land Mobile systems, e.g. cellular systems
• CPC Class Codes: H04W 84/12 : WLAN [Wireless Local Area Networks]
• CPC Class Codes: H04W 88/06 : adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
• CPC Class Codes: H04W 88/08 : Access point devices
• CPC Class Codes: Y02P 90/80 : Management or planning

Abstract

Various embodiments are disclosed for a services policy communication system and method. In some embodiments, a network device implements a service profile for assisting control of a communications device use of a service on a network, in which the service profile includes service policy settings for the communications device; monitors use of the service by the communications device based on the service profile; and modifies a service policy setting to achieve a service usage goal.

Claims

1. A method comprising:

receiving at a server a first usage measure from a communication device, the server being remote from the communications device, the first usage measure specifying the communications device'"'"'s use of one or more network services over an access network and corresponding to a first data usage classification;

receiving at the server a second usage measure from a network element, the second usage measure specifying the communications device'"'"'s use of the one or more network services over the access network and corresponding to a second data usage classification, the second data usage classification being different than the first data usage classification; and

synchronizing the first and second usage measures, the synchronization including adjusting at least one of the first usage measure and the second usage measure to account for a difference between the first data usage classification and the second data usage classification.

2. The method of claim 1, further comprising:

subsequent to the adjusting, comparing the first usage measure to the second usage measure to determine whether the communications device is properly determining the first usage measure.

3. The method of claim 1, wherein the adjusting at least one of the first usage measure and the second usage measure includes:

aggregating the first usage measure with a plurality of other measures received from the communications device.

4. The method of claim 1, wherein the adjusting at least one of the first usage measure and the second usage measure includes:

aggregating the second usage measure with a plurality of other measures received from the network element.

5. The method of claim 1, wherein the first data usage classification includes a first time period and the second data usage classification includes a second time period, and further comprising:

receiving a first time stamp corresponding to the first usage measure; and

determining the first time period based on the first time stamp.

6. The method of claim 5, wherein the first data classification includes a first time period and the second data classification includes a second time period, and further comprising:

receiving a second time stamp corresponding to the second usage measure; and

determining the second time period based on the second time stamp, the first time stamp being different than the second time stamp.

7. The method of claim 6, wherein the adjusting at least one of the first usage measure and the second usage measure includes:

projecting a value for a device-assisted measure at the second time stamp based on the first and second measures and the first and second time stamps.

8. The method of claim 7, wherein the projecting includes estimating that the usage rate remains consistent for the time between the first time stamp and the second time stamp.

9. The method of claim 6, wherein the adjusting at least one of the first usage measure and the second usage measure includes adding an amount of usage to the first measure to account for a difference between the first time stamp and the second time stamp.

10. The method of claim 6, further comprising:

receiving one or more additional first usage measures from the communication device, each additional first usage measure corresponding to a different time stamp; and

receiving one or more additional second usage measures from the network element, each additional second usage measure corresponding to a different time stamp,

wherein the adjusting at least one of the first usage measure and the second usage measure includes aggregating a first portion of first usage measures and/or a second portion of the second usage measures.

11. The method of claim 10, wherein the number of first usage measures in the first portion is based on the second time stamps.

12. The method of claim 1, wherein the adjusting at least one of the first usage measure and the second usage measure includes:

applying a multiplier to the first measure or the second measure.

13. The method of claim 12, wherein the multiplier accounts for a systematic offset between device-based measures and network-based measures.

14. The method of claim 12, wherein the adjusting at least one of the first usage measure and the second usage measure includes:

adding or subtracting a constant offset from the first measure or the second measure.

15. The method of claim 1, wherein a difference in data usage classification between the first usage measure and the second usage measure is a difference in measurement time period.

16. The method of claim 1, wherein a difference in data usage classification between the first usage measure and the second usage measure is a difference in the network communications protocol layer where the measurements take place.

17. The method of claim 1, further comprising analyzing the first and second usage measures to determine if they are mutually consistent within a specified tolerance with a proper service policy intended to be implemented on the device.

18. The method of claim 1, wherein a difference in data usage classification between the first usage measure and the second usage measure is a difference in the level of detail.

19. The method of claim 1, wherein the usage measure classification provided by the communications device includes classification of a data flow based on the device application accessing the data flow.

20. The method of claim 1, wherein a difference in data usage classification between the first usage measure and the second usage measure is a difference in the level of address classification for data flows, IP layer classification of data flows, IP/socket tuple classification of data flows, OSI layer 3 classification of data flows, or OSI layer 4 classification of data flows.

21. The method of claim 1, wherein a difference in data usage classification between the first usage measure and the second usage measure is a difference in HTTP layer classification of data flows, HTML layer classification of data flows, domain name classification of data flows, URL classification of data flows, server name classification of data flows, or OSI layer 7 classification of data flows.

22. The method of claim 1, wherein a difference in data usage classification between the first usage measure and the second usage measure is a difference in level of information provided to characterize network type, network identity, network carrier, home network information or roaming network that is associated with a data flow.

23. The method of claim 1, wherein a difference in data usage classification between the first usage measure and the second usage measure is a difference in level of information provided to characterize QoS state that is associated with a data flow.

24. The method of claim 1, wherein a difference in data usage classification between the first usage measure and the second usage measure is a difference in level of information provided to characterize whether the usage is terminated in the communications device itself or whether the communications device forwards the data flow between the network and another communications device.

25. The method of claim 1, wherein a difference in data usage classification between the first usage measure and the second usage measure is a difference in level of information provided to characterize usage for a usage account associated with a data flow.

26. The method of claim 25, wherein the usage account is associated with a member of a corporate IT service account.

27. The method of claim 25, wherein the usage account is associated with a member of a family plan service account.

28. The method of claim 1, wherein a difference in data usage classification between the first usage measure and the second usage measure is a difference in level of information provided to characterize usage for an ambient service associated with a data flow.

29. The method of claim 1, wherein a difference in data usage classification between the first usage measure and the second usage measure is a difference in level of information provided to characterize usage for a special purpose service plan or service profile provided to the device that is associated with a data flow.

30. The method of claim 1, wherein a difference in data usage classification between the first usage measure and the second usage measure is a difference in level of information provided to characterize usage at a device location associated with a data flow.

31. The method of claim 1, wherein a difference in data usage classification between the first usage measure and the second usage measure is a difference in level of information provided to characterize usage for a type of content or a type of content service associated with data being transmitted in a data flow.