Adapting network policies based on device service processor configuration

• US 9,591,474 B2
• Filed: 08/29/2014
• Issued: 03/07/2017
• 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., Lavine, James
• Primary Examiner(s): RUDY, ANDREW J
• Application Number:
  US14/473,137
• Publication Number:
  US 20150111528A1
• Time in Patent Office: 921 Days
• Field of Search: 455/411, 455/414.1, 455/435, 455/556, 455/405, 370/252, 709/217, 709/220, 709/223, 709/224
• US Class Current: 1/1
• CPC Class Codes: H04L 12/14 Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 12/1403 Architecture for metering, charging or billing
• CPC Class Codes: H04L 41/0816 the condition being an adaptation, e.g. in response to network events
• 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: 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/58 based on statistics of usage or network monitoring
• CPC Class Codes: H04M 2215/0188 Network monitoring; statistics on usage on called/calling number
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 12/08 Access security
• CPC Class Codes: H04W 24/10 Scheduling measurement reports ; Arrangements for measurement reports
• CPC Class Codes: H04W 4/24 Accounting or billing
• 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

Abstract

Disclosed herein are various embodiments to prevent, detect, or take action in response to the moving a device credential from one device to another, the improper configuration of a service processor, a missing service processor, or the tampering with a service processor in device-assisted services (DAS) systems.

Claims

1. A method of operating a network system comprising at least one server, the method comprising:

receiving a notification from a cellular data network that a mobile device has gained or requested access to a cellular network data service;

in association with the notification, and during an authentication time period related to the receipt of the notification, wait for a corresponding request from a mobile device data traffic characterization agent for login and/or authentication;

when the mobile device data traffic characterization agent requests login and/or authentication during the authentication time period and properly logs in or authenticates, set up a data rating service for cellular data traffic of the mobile device in a first configuration that relies on data traffic characterization from the mobile device agent; and

when the mobile device agent fails to make during the authentication time period or successfully complete the corresponding request, set up the data rating service for cellular data traffic of the mobile device in a second configuration that operates without reliance on data traffic characterization from the mobile device agent.

2. The method of claim 1, wherein the first configuration receives records of data usage from the mobile device data traffic characterization agent, and the second configuration receives records of data usage from one or more network measurement points.

3. The method of claim 1, wherein data traffic characterization comprises records of data usage, the method further comprising classifying cellular data network usage into several categories based on the records.

4. The method of claim 1, wherein data traffic characterization comprises records of data usage, the method further comprising incrementing cellular data network usage limits for the mobile device based on the records.

5. The method of claim 1, further comprising, for determining that the device agent has failed to make the corresponding request, imposing a time limit between receiving the notification and receiving the corresponding request.

6. The method of claim 1, further comprising determining whether the device agent is properly providing data characterization.

7. The method of claim 6, wherein determining whether the device agent is properly providing data characterization comprises:

receiving first data records generated by the mobile device and purporting to indicate cellular data network usage by the mobile device;

receiving second data records generated by one or more network measurement points and indicating cellular data network usage by the mobile device; and

comparing usages derived respectively from the first and second data records; and

deciding that the device agent is not properly providing data characterization when the comparing shows a significant difference between the compared usages.

8. The method of claim 6, wherein determining whether the device agent is properly providing data categorization comprises tracking the number of Subscriber Identity Modules that have been associated with the mobile device, and when the number exceeds a limit deciding that the device agent is not properly providing data characterization.