IP Library Granted Patent US 8,090,345
Granted Patent B2
US 8,090,345 · App. 11/973,762 · Granted Jan 3, 2012

Multiple channel automated refill system

Assignee: Accenture Global Services Limited
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 8,090,345
App. No.
11/973,762
Granted
Jan 3, 2012
Kind
B2
Abstract

An automatic refill system for pre-paid accounts provides enhanced funding flexibility for customers and additional revenue streams for a telecommunication service provider. The automatic refill system solves the technical challenges involved with implementing a scheduled refill channel co-existing with a triggered refill channel for funding a pre-paid account. The scheduled channel regularly refills the pre-paid account. The telecommunication service provider also coordinates funding through a triggered refill channel that refills the pre-paid account when specific conditions are met, such as account balance falling below a threshold.

Claims (131)

1. A telecommunication service provider automatic refill system comprising:

a customer account linked with a configuration record operable to identify whether only a triggered refill channel is activated on the customer account, whether only a scheduled refill channel is activated on the customer account, and whether both the triggered refill channel and scheduled refill channel are activated on the customer account;

a billing system operable to receive a customer account identifier that identifies the customer account and operable to analyze the configuration record linked to the customer account identifier to determine whether a triggered refill condition is met for the customer account, that a regularly scheduled refill condition is met for the customer account, or that both the regularly scheduled refill condition and triggered refill condition are met for the customer account;

a triggered refill channel in communication with the billing system, the triggered refill channel operable to execute a triggered refill funding procedure for the customer account when the triggered refill condition is met for the customer account; and

a scheduled refill channel in communication with the billing system, the scheduled refill channel operable to execute a scheduled refill funding procedure for the customer account when the regularly scheduled refill condition is met for the customer account.

2. The system of claim 1 where the configuration record comprises:

an executed date data field operable to store a calendar date representing when the scheduled refill funding procedure was executed;

a refill activation data field operable to store an identifier identifying whether only the triggered refill channel is activated, only the scheduled refill channel is activated, or the triggered refill channel and the scheduled refill channel are activated;

a refill status data field operable to store an identifier representative of a refill status;

a refill amount data field operable to store an identifier representative of a refill amount;

a scheduled condition data field operable to store a calendar date representative of the regularly scheduled refill condition; and

a triggered refill amount data field operable to store a value representative of the triggered refill condition.

3. The system of claim 1 where the triggered refill condition comprises a predetermined threshold of an amount representative of a monetary value for a balance remaining in a customer account.

4. The system of claim 1 where:

the customer account comprises a pre-paid customer account; and

the triggered refill channel is operable to execute the triggered refill funding procedure by being operable to:

determine an automatic refill payment to apply to the pre-paid customer account;

determine a post-paid account identifier associated with the pre-paid customer account; and,

determine whether a post-paid account associated with the post-paid account identifier is active; and,

the triggered refill channel is further operable to:

apply the automatic refill payment to the pre-paid customer account; and

apply an adjustment to a post-paid account corresponding to the post-paid account identifier in an amount equal to the automatic refill payment applied to the pre-paid customer account, when

the triggered refill channel determines that the post-paid account is active.

5. The system of claim 4 where the triggered refill channel is further operable to:

determine whether applying the adjustment to the post-paid account is successful; and

deduct the automatic refill payment from the pre-paid customer account when the adjustment applied to the post-paid account is not successful.

6. The system of claim 1 where the regularly scheduled refill condition comprises a calendar date.

7. The system of claim 1 where:

the customer account comprises a pre-paid customer account; and

the scheduled refill channel is operable to execute the scheduled refill funding procedure by being operable to:

determine an automatic refill payment to apply to the pre-paid customer account;

determine a post-paid account identifier associated with the pre-paid customer account; and,

determine whether a post-paid account associated with the post-paid account identifier is active; and,

the scheduled refill channel is further operable to:

apply the automatic refill payment to the pre-paid customer account; and

apply an adjustment to a post-paid account corresponding to the post-paid account identifier in an amount equal to the automatic refill payment applied to the pre-paid customer account, when

the scheduled refill channel determines that the post-paid account is active.

8. The system of claim 7 where the scheduled refill channel is further operable to:

determine whether applying the adjustment to the post-paid account is successful; and

deduct the automatic refill payment from the pre-paid customer account when the adjustment applied to the post-paid account is not successful.

9. A telecommunication service provider automatic refill method comprising:

receiving a customer account identifier for a customer account;

querying a configuration record linked to the customer account identifier to determine that only a triggered refill channel is activated on the customer account, that only a scheduled refill channel is activated on the customer account, or that both the triggered refill channel and scheduled refill channel are activated on the customer account;

implementing multiple refill channel configuration options for the customer account by:

determining when only the triggered refill channel is activated, or when both the triggered refill channel and scheduled refill channel are activated, and in response:

establishing a triggered refill condition for the customer account;

determining that the triggered refill condition is met; and

responsively executing a triggered refill funding procedure for the customer account; and

determining when only the scheduled refill channel configuration is activated, or when both the triggered refill channel and scheduled refill channel are activated, and in response:

establishing a regularly scheduled refill condition for the customer account;

determining that the regularly scheduled refill condition is met; and

responsively executing a scheduled refill funding procedure for the customer account.

10. The method of claim 9 where the configuration record comprises:

an executed date data field operable to store a calendar date representing when the scheduled refill funding procedure was executed;

a refill activation data field operable to store an identifier identifying whether only the triggered refill channel is activated, only the scheduled refill channel is activated, or the triggered refill channel and the scheduled refill channel are activated;

a refill status data field operable to store an identifier representative of a refill status;

a refill amount data field operable to store an identifier representative of a refill amount;

a scheduled condition data field operable to store a calendar date representative of the regularly scheduled refill condition; and

a triggered refill amount data field operable to store value representative of the triggered refill condition.

11. The method of claim 9 where the triggered refill condition comprises a predetermined threshold of an amount representative of a monetary value for a balance remaining in a customer account.

12. The method of claim 11 where establishing a triggered refill condition for the customer account comprises:

receiving the predetermined threshold amount; and

storing the predetermined threshold amount in the configuration record linked to the customer account identifier.

13. The method of claim 9 where responsively executing a triggered refill funding procedure comprises:

determining an automatic refill payment to apply to the customer account;

determining a post-paid account identifier associated with the customer account; and,

determining whether a post-paid account associated with the post-paid account identifier is active, and

where the post-paid account is active:

applying the automatic refill payment to the customer account; and,

applying an adjustment to a post-paid account corresponding to the post-paid account identifier in an amount equal to the automatic refill payment applied to the customer account.

14. The method of claim 13 further comprising:

determining whether the adjustment applied to the post-paid account was successful; and

where the adjustment applied to the post-paid account was not successful, deducting the automatic refill payment from the customer account.

15. The method of claim 9 where the regularly scheduled refill condition comprises a calendar date.

16. The method of claim 15 where establishing the regularly scheduled refill condition for the customer account comprises:

receiving the calendar date; and

storing the calendar date in the configuration record linked to the customer account identifier.

17. The method of claim 9 where responsively executing the scheduled refill funding procedure comprises:

determining an automatic refill payment to apply to the customer account;

determining a post-paid account identifier associated with the customer account; and,

determining whether a post-paid account associated with the post-paid account identifier is active, and where the post-paid account is active:

applying the automatic refill payment to the customer account; and

applying an adjustment to a post-paid account corresponding to the post-paid account identifier in an amount equal to the automatic refill payment applied to the customer account.

18. The method of claim 9 further comprising:

determining whether the adjustment applied to the post-paid account was successful; and

where the adjustment applied to the post-paid account was not successful, deducting the automatic refill payment from the customer account.

19. A product comprising:

a machine readable medium; and

logic stored on the medium operable to:

receive a customer account identifier for a customer account;

query a configuration record linked to the customer account identifier to determine that only a triggered refill channel is activated on the customer account, that only a scheduled refill channel is activated on the customer account, or that both the triggered refill channel and scheduled refill channel are activated on the customer account;

implement multiple refill channel configuration options for the customer account by being operable to:

determine when only the triggered refill channel is activated, or when both the triggered refill channel and scheduled refill channel are activated, and responsively operable to:

establish a triggered refill condition for the customer account;

determine that the triggered refill condition is met; and

execute a triggered refill funding procedure for the customer account; and

determine when only the scheduled refill channel configuration is activated, or when both the triggered refill channel and scheduled refill channel are activated, and responsively operable to:

establish a regularly scheduled refill condition for the customer account;

determine that the regularly scheduled refill condition is met; and

execute a scheduled refill funding procedure for the customer account.

20. The product of claim 19 where the configuration record comprises:

an executed date data field operable to store a calendar date representing when the scheduled refill funding procedure was executed;

a refill activation data field operable to store an identifier identifying whether only the triggered refill channel is activated, only the scheduled refill channel is activated, or the triggered refill channel and the scheduled refill channel are activated;

a refill status data field operable to store an identifier representative of a refill status;

a refill amount data field operable to store an identifier representative of a refill amount;

a scheduled condition data field operable to store a calendar date representative of the regularly scheduled refill condition; and

a triggered refill amount data field operable to store a value representative of the triggered refill condition.

21. The product of claim 19 where:

the customer account comprises a pre-paid customer account; and

the logic is further operable to execute the triggered refill funding procedure by being operable to:

determine an automatic refill payment to apply to the pre-paid customer account;

determine a post-paid account identifier associated with the pre-paid customer account; and,

determine whether a post-paid account associated with the post-paid account identifier is active; and,

the logic is further operable to:

apply the automatic refill payment to the pre-paid customer account; and

apply an adjustment to a post-paid account corresponding to the post-paid account identifier in an amount equal to the automatic refill payment applied to the pre-paid customer account, when the logic determines that the post-paid account is active.

22. The product of claim 21 where the logic is further operable to:

determine whether applying the adjustment to the post-paid account is successful; and

deduct the automatic refill payment from the pre-paid customer account when the logic determines that the adjustment applied to the post-paid account is not successful.

23. The product of claim 19 where:

the customer account comprises a pre-paid customer account; and

the logic is operable to execute the scheduled refill funding procedure by being operable to:

determine an automatic refill payment to apply to the pre-paid customer account;

determine a post-paid account identifier associated with the pre-paid customer account; and,

determine whether a post-paid account associated with the post-paid account identifier is active; and,

the logic is further operable to:

apply the automatic refill payment to the pre-paid customer account; and

apply an adjustment to a post-paid account corresponding to the post-paid account identifier in an amount equal to the automatic refill payment applied to the pre-paid customer account, when the logic determines that the post-paid account is active.

24. The product of claim 23 where the logic is further operable to:

determine whether applying the adjustment to the post-paid account is successful; and

deduct the automatic refill payment from the pre-paid customer account when the logic determines that the adjustment applied to the post-paid account is not successful.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 26, 2011
From: ACCENTURE GLOBAL SERVICES GMBH
To: ACCENTURE GLOBAL SERVICES LIMITED
Reel/Frame 025700/0287 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 2, 2008
From: ACCENTURE S.P.A.
To: ACCENTURE GLOBAL SERVICES GMBH
Reel/Frame 020895/0087 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 9, 2007
From: MASTRANTUONO, DOMENICO; CLEMENZI, JACOPO
To: ACCENTURE S.P.A.
Reel/Frame 020011/0381 →
Priority Claims (1)
EP 07425536 · Aug 17, 2007 · regional
Continuity (1)
Related Publication 20090047926A1 · Feb 19, 2009