# US 2009/0276386 A1 · Control of Real Time Services

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

- Number: US 2009/0276386 A1
- Document ID: US20090276386A1
- Status: Published application
- Kind: A1
- Application number: 12/226,054
- Filed: 2007-03-30
- Published: 2009-11-05
- Earliest claimed: 2006-04-07
- Inventors: Mark Greening; Nicholas Jones; Simon Smith; David Spann; Ralph Woodman
- Web page: https://patentgrep.com/patent/US20090276386A1

## CPC

- H04L 47/762: triggered by the network
- H04L 47/15: {in relation to multipoint traffic (arrangements for broadcast or multicast in data networks H04L12/18)}
- H04L 47/801: {Real time traffic}
- H04L 47/808: {User-type aware}
- H04L 47/83: based on usage prediction
- H04M 15/77: {involving multiple accounts per user}
- H04M 15/775: {Account specifications on parallel communications}
- H04M 15/78: {Redistributing amount between accounts}
- 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)

## Abstract

A real time monitoring and control system (101) interfaces with service supply entities such as SMSC, MSC, GGSN, SGSN, and IP probe entities. A data manager (104) maintains account resource data associating each of a plurality of accounts with one or more services, in which at least one account is associated with a plurality of services. Each account may have multiple pots, each associated with a type of resource such as bytes, packets, or time. A session manager (102) monitors concurrent service usage in real time and generates messages or control instructions for account modification and for account resource re-allocation across services in real time according to service usage. The session manager (102) dynamically re-distributes available account resources to sessions as the sessions occur, including resource re-allocation during a plurality of sessions including scalar and event-based sessions.

## Claims

### Claim at position 1

1-31. (canceled)

### Claim 32

A real time service supply monitoring and control system comprising:
a data manager comprising means for maintaining account resource data associating each of a plurality of resource accounts with one or more services, in which at least one account is associated with a plurality of services; and
a session manager comprising:
functions for interfacing with a plurality of service supply entities;
functions for processing requests from said entities for resources to establish and maintain service supply sessions;
functions for monitoring concurrent sessions in real time;
a rule base for, in real time, re-allocating resources from said accounts to concurrent sessions according to service usage; and
functions to notify service supply entities of re-allocation of resources.

### Claim 33 (depends on 32)

The system as claimed in claim 32, wherein the service supply entities are communication network entities and the service usage is in communication sessions.

### Claim 34 (depends on 32)

The system as claimed in claim 32, wherein the service supply entities are communication network entities and the service usage is in communication sessions; and wherein the data manager maintains accounts for scalar and event-based resources.

### Claim 35 (depends on 32)

The system as claimed in claim 32, wherein the session manager maintains a running estimate of total resources for concurrent sessions, and allocates resources to each session to minimise number of requests for fresh resources.

### Claim 36 (depends on 35)

The system as claimed in claim 35, wherein the session manager generates a resource requirement estimate upon commencement of a fresh session.

### Claim 37 (depends on 32)

The system as claimed in claim 32, wherein the session manager comprises means for using historical data to calculate an initial resource allocation for a session.

### Claim 38 (depends on 37)

The system as claimed in claim 37, wherein the historical data is per subscriber and the session manager calculates the initial resource allocation upon detection of subscriber identity.

### Claim 39 (depends on 32)

The system as claimed in claim 32, wherein the session manager comprises means for using historical data to calculate an initial resource allocation for a session; and wherein the historical data is per service and the session manager calculates the initial resource allocation according to the service.

### Claim 40 (depends on 32)

The system as claimed in claim 32, wherein the session manager generates a message for a service entity to either request additional resources for an account if it estimates that the resources will be exhausted during a current session or informs the entity of a new quota of resources.

### Claim 41 (depends on 32)

The system as claimed in claim 32, wherein the session manager interfaces with a service supply entity for resource allocation negotiation.

### Claim 42 (depends on 32)

The system as claimed in claim 32, wherein the data manager maintains at least one pot for each account, wherein each pot is associated with a resource unit.

### Claim 43 (depends on 42)

The system as claimed in claim 42, wherein the units include time, volume of bytes, number of messages, and number of program or content downloads.

### Claim 44 (depends on 42)

The system as claimed in claim 42, wherein at least one pot is associated by the session manager with a plurality of service types.

### Claim 45 (depends on 32)

The system as claimed in claim 32, wherein the session manager associates a resource account with a group of subscribers.

### Claim 46 (depends on 32)

The system as claimed in claim 32, wherein the session manager determines priorities for resource allocation, and uses the priorities to determine the order in which pots are to be exhausted according to the priority.

### Claim 47 (depends on 46)

The system as claimed in claim 46, wherein the data manager associates a priority with each pot.

### Claim 48 (depends on 32)

The system as claimed in claim 32, wherein the session manager comprises means for dynamically re-evaluating all current instances upon commencement of a fresh session, and determining according to said re-evaluation if there are sufficient resources for the fresh instance.

### Claim 49 (depends on 48)

The system as claimed in claim 48, wherein the session manager comprises means for denying a service request if it determines that there are insufficient resources to satisfy all sessions.

### Claim 50 (depends on 48)

The system as claimed in claim 48, wherein the session manager re-allocates all concurrent sessions according to a policy which determines a target end time for the sessions.

### Claim 51 (depends on 48)

The system as claimed in claim 48, wherein the session manager re-allocates all concurrent sessions according to a policy which determines target data volumes for sessions.

### Claim 52 (depends on 48)

The system as claimed in claim 48, wherein the re-allocation is performed on the basis that all concurrent sessions end at approximately the same time.

### Claim 53 (depends on 48)

The system as claimed in claim 48, wherein the session manager comprises means for interfacing with service supply entities according to a reserve-capture scheme.

### Claim 54 (depends on 32)

The system as claimed in claim 32, wherein the session manager comprises means for flagging resources which are amenable to modification for re-allocation.

### Claim 55 (depends on 54)

The system as claimed in claim 54, wherein the session manager does not flag some software downloads as being amenable to modification as they are atomic in nature.

### Claim 56 (depends on 32)

The system as claimed in claim 32, wherein the data manager comprises means for dynamically modifying accounts during sessions drawing resources from said accounts.

### Claim 57 (depends on 32)

The system as claimed in claim 32, wherein the session manager comprises means for interfacing with service entities in parallel.

### Claim 58 (depends on 32)

The system as claimed in claim 32, wherein the session manager comprises a session controller object linked with a resource re-allocation policy object having at least one re-allocation algorithm, method, and the session controller object has methods for calling the re-allocation policy object for making decisions for resource re-allocation.

### Claim 59 (depends on 58)

The system as claimed in claim 58, wherein the session controller object contains a plurality of session objects, each containing at least one reservation token object, and the session controller object dynamically performs resource re-allocation by instructing a session object to modify a contained reservation token object.

### Claim 60 (depends on 58)

The system as claimed in claim 58, wherein the session controller object contains a plurality of session objects, each containing at least one reservation token object, and the session controller object dynamically performs resource re-allocation by instructing a session object to modify a contained reservation token object; and wherein the session object modifies the reservation token object by modifying an attribute of the reservation token object.

### Claim 61 (depends on 58)

The system as claimed in claim 58, wherein the session manager comprises an interface for modification of attributes of the session controller and policy objects to implement configuration settings.

### Claim 62 (depends on 32)

The computer readable medium comprising software code for performing operations of a system as claimed in claim 32 when executing on a digital processor.
