# US 10,321,320 B2 · Wireless network buffered message system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 10,321,320 B2
- Document ID: US10321320B2
- Status: Granted
- Kind: B2
- Application number: 15/582,350
- Filed: 2017-04-28
- Published: 2017-11-16
- Granted: 2019-06-11
- Earliest claimed: 2009-01-28
- Assignees: Headwater Research LLC
- Applicants: Headwater Research LLC
- Inventors: Gregory G. Raleigh
- Web page: https://patentgrep.com/patent/US10321320B2

## CPC

- H04W 12/08: Access security
- G06F 15/177: Initialisation or configuration control {(processor initialisation G06F9/4405)}
- G06Q 10/06315: {Needs-based resource requirements planning or analysis}
- G06Q 10/06375: {Prediction of business process outcome or impact based on a proposed change}
- G06Q 20/102: {Bill distribution or payments}
- G06Q 20/20: Point-of-sale [POS] network systems
- G06Q 20/32: using wireless devices
- 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
- G06Q 30/0207: Discounts or incentives, e.g. coupons or rebates
- G06Q 30/0241: Advertisements
- G06Q 30/0283: Price estimation or determination
- G06Q 30/0284: {Time or distance, e.g. usage of parking meters or taximeters}
- G06Q 30/04: Billing or invoicing
- G06Q 30/0601: Electronic shopping [e-shopping]
- G06Q 40/00: Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q 40/12: Accounting
- 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}
- H04L 9/3247: {involving digital signatures}
- H04L 12/14: Charging, metering or billing arrangements specially adapted for data communications, e.g. authentication, authorisation and accounting [AAA] framework
- H04L 12/1407: {Policy-and-charging control [PCC] architecture}
- H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play
- H04L 41/0894: Policy-based network configuration management
- H04L 41/5003: Managing SLA; Interaction between SLA and QoS
- H04L 41/5054: Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
- H04L 47/20: Traffic policing
- H04L 47/2408: for supporting different services, e.g. a differentiated services [DiffServ] type of service
- H04L 51/046: Interoperability with other network applications or services
- H04L 63/0236: {Filtering by address, protocol, port number or service, e.g. IP-address or URL}
- H04L 63/04: {for providing a confidential data exchange among entities communicating through data packet networks}
- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- 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)}
- H04L 63/0892: {by using authentication-authorization-accounting [AAA] servers or protocols}
- H04L 63/10: {for controlling access to devices or network resources}
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- H04L 67/145: avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
- H04L 67/306: User profiles
- H04L 67/51: Discovery or management thereof, e.g. service location protocol [SLP] or web services
- H04L 67/55: Push-based network services
- H04L 67/63: Routing a service request depending on the request content or context
- 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}
- H04M 15/49: {Connection to several service providers}
- H04M 15/58: {based on statistics of usage or network monitoring}
- H04M 15/61: {based on the service used}
- H04M 15/66: {Policy and charging system}
- H04M 15/80: {Rating or billing plans; Tariff determination aspects}
- H04M 15/8055: {Selecting cheaper transport technology for a given service}
- H04M 15/88: {Provision for limiting connection, or expenditure}
- H04W 4/02: Services making use of location information
- H04W 4/12: Messaging; Mailboxes; Announcements
- 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
- H04W 4/20: Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
- H04W 4/24: Accounting or billing
- H04W 4/50: Service provisioning or reconfiguring
- H04W 8/18: Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
- H04W 8/20: Transfer of user or subscriber data
- H04W 12/00: Security arrangements; Authentication; Protecting privacy or anonymity
- H04W 12/02: Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
- H04W 12/037: of the control plane, e.g. signalling traffic
- H04W 12/06: Authentication
- H04W 12/37: Managing security policies for mobile devices or for controlling mobile applications
- H04W 24/08: Testing, {supervising or monitoring} using real traffic
- H04W 28/02: Traffic management, e.g. flow control or congestion control
- 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)}
- 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)}
- H04W 28/12: using signalling between network elements
- H04W 48/14: using user query {or user detection}
- H04W 48/16: Discovering, processing access restriction or access information
- H04W 72/0453: Resources in frequency domain, e.g. a carrier in FDMA
- H04W 88/08: Access point devices
- H04L 41/0876: {Aspects of the degree of configuration automation}
- H04L 41/5025: by proactively reacting to service quality change, e.g. by reconfiguration after service quality degradation or upgrade
- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- H04L 67/564: Enhancement of application control based on intercepted application data
- H04M 2215/0188: Network monitoring; statistics on usage on called/calling number
- 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
- H04W 84/04: Large scale networks; Deep hierarchical networks
- H04W 84/042: {Public Land Mobile systems, e.g. cellular systems}
- H04W 84/12: WLAN [Wireless Local Area Networks]
- H04W 88/06: adapted for operation in multiple networks {or having at least two operational modes}, e.g. multi-mode terminals
- Y02P 90/80: Management or planning
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- Y02P: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS

## Abstract

A network server system maintains secure Internet data message links with respective device link agents on each of many wireless end-user devices. Through a network interface, the server system receives messages from network elements, for which delivery is requested to specific software components on specific ones of the devices. A message buffer system buffers such messages for delivery, and logic determines whether one of several potential triggers has happened to cause the system to deliver buffered messages to a particular one of the devices. For at least some messages, receiving the message at the buffer will not trigger delivery. At least one trigger identifies a time-critical message, however, which can cause all buffered messages for a particular device to be delivered. Such a system balances wireless network efficiency and opportunistic delivery with a potential for fast message delivery, when needed.

## Claims

### Claim 1

A networked system comprising:
i) a network server system including
a link interface to maintain a respective secure Internet data message link between the link interface and a respective device link agent on each of a plurality of wireless end-user devices, each of the wireless end-user devices comprising multiple software components authorized to receive messages via the device link agent on that device;
a network interface to receive messages from a plurality of network elements, for delivery to respective ones of the software components identified in the messages, each network element authorized to send messages via the link interface to one or more of the software components on one or more of the wireless end-user devices; and
a message buffer system including a memory and logic,
the memory to buffer content from the received network element messages for which delivery is requested to any of the wireless end-user devices,
the logic to determine when one of a plurality of message delivery triggers for a given one of the wireless end-user devices has occurred, wherein for at least some of the received network element messages, the receipt of such a message by the message buffer system is not a message delivery trigger, and for at least one of the message delivery triggers, the trigger is an occurrence of an asynchronous event with time-critical messaging needs, and
upon determining that one of the message delivery triggers has occurred for the given one of the wireless end-user devices, the logic further to supply one or more messages comprising the buffered content for the given one of the wireless end-user devices to the transport services stack for delivery on the secure message link maintained between the transport services stack and a device link agent on the given one of the wireless end-user devices; and
ii) the device link agents on the respective wireless end-user devices, each of the device link agents configured to
maintain the respective secure Internet data message link over a wireless network to the link interface,
receive secure Internet data messages from the network server system over the respective secure Internet data message link, including messages collected from multiple ones of the network elements and messages corresponding to multiple ones of the software components authorized to receive messages via the device link agent on that respective device, wherein at least a first subset of the secure Internet data messages contain both a unique identifier for a corresponding one of the software agents and data to be consumed by that software component, the data supplied from a respective network element corresponding to that software component, and
for software components that are authorized to access messages received via the device link agent, cause messages with a unique identifier corresponding to a given one of those software applications to be securely delivered to a software process corresponding to the given software component.

### Claim 2 (depends on 1)

The networked system of claim 1, the message buffer system logic to determine, for each of the wireless end-user devices, when one of a plurality of message delivery triggers has occurred, at least one of the triggers for each given device specific to one or more states of that given device.

### Claim 3 (depends on 1)

The networked system of claim 1, wherein one of the message delivery triggers is the expiration of a periodic timer.

### Claim 4 (depends on 3)

The networked system of claim 3, wherein the period of the timer is fractionally shorter than a maximum data message interval beyond which the Internet data message link to the given device is taken down.

### Claim 5 (depends on 1)

The networked system of claim 1, wherein one of the message delivery triggers is the receipt of a transmission on the respective secure Internet data message link from the device link agent of the given one of the wireless end-user devices, or a response generated to a transmission received from that device link agent.

### Claim 6 (depends on 1)

The networked system of claim 1, wherein one of the message delivery triggers is a heartbeat message generated by the given device link agent, or a request received from the given device link agent.

### Claim 7 (depends on 1)

The networked system of claim 1, wherein one of the message delivery triggers is the receipt of a particular message from one of the network elements.

### Claim 8 (depends on 1)

The networked system of claim 1, further comprising a secure server to store a secure authorization list, the secure authorization list indicating the authorized software components and the authorized network elements that are allowed to communicate using the network server system.

### Claim 9 (depends on 8)

The networked system of claim 8, further comprising the respective device link agent on each wireless end-user device receiving access authorization information from the secure server, the access authorization indicating, respectively for each wireless end-user device, the software components authorized to receive messages via the device link agent on that device.

### Claim 10 (depends on 1)

The networked system of claim 1, wherein a second subset of the secure Internet data messages contain a user message from a network element, the user message intended for display on a user interface of a given one of the wireless end-user devices.

### Claim 11 (depends on 1)

The networked system of claim 1, wherein one of the software components on a given one of the wireless end-user devices is a policy control agent, and the data to be consumed by the policy control agent comprises service settings and/or configuration information for the given device.

### Claim 12 (depends on 1)

The networked system of claim 1, the link interface to encrypt messages identified for delivery to each given one of the wireless end-user devices to create secure Internet data messages, the device link agent on each given device further configured to decrypt the received secure Internet data messages for that device prior to delivering those messages to a respective software process.

### Claim 13 (depends on 12)

The networked system of claim 12, wherein the encrypted messages are transported to the device link agent using one or more of encryption on a transport services stack, IP (Internet Protocol) layer encryption, and tunneling.

### Claim 14 (depends on 1)

The networked system of claim 1, wherein the device link agent on a given device executes in a secure execution environment, and at least one of the software components on that device executes outside of the secure execution environment.

### Claim 15 (depends on 1)

The networked system of claim 1, wherein the device link agent on a given one of the devices is further configured to receive, from one or more of the software components on that device, upload messages, each of the upload messages identifying a corresponding one of the network elements to which the device respective software component has requested delivery, the device link agent on that device transmitting the upload messages to the network message server over the respective secure Internet data message link, for delivery by the network message server to the respective identified network elements.

### Claim 16 (depends on 15)

The networked system of claim 15, the device link agent on the given device further configured to buffer one or more of the upload messages for transmission to the network message server at a time selected by a heartbeat mechanism.

### Claim 17 (depends on 1)

The networked system of claim 1, at least a given one of the devices further comprising a secure interprocess communication service separately secured from the secure Internet data message link, the device link agent for the given device causing messages to be securely delivered to a software process by initiating delivery of each such message on the secure interprocess communication service.

### Claim 18 (depends on 1)

The networked system of claim 1, wherein at least one of the secure Internet data messages comprises multiple identifier/data pairs.