SYSTEM AND METHOD FOR GENERATING A PERSONALIZED BILL USING A PERSONAL ADDRESS BOOK

• US 20090016508A1
• Filed: 07/12/2007
• Published: 01/15/2009
• Est. Priority Date: 07/12/2007
• Status: Active Grant

• Current Assignee: Amdocs Development Limited (Amdocs Ltd.)
• Original Assignee: Comverse Limited (Mavenir Group Holdings Ltd.)
• Inventors: KRUSHNAKANT, Chavan
• Granted Patent: US 8,184,787 B2
• Time in Patent Office: Days
• US Class Current: 379/114.50
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• 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/06 Recording class or number of calling , i.e. A-party or called party , i.e. B-party
• CPC Class Codes: H04M 15/44 Augmented, consolidated or itemized billing statement or bill presentation
• CPC Class Codes: H04M 2215/0104 Augmented, consolidated or itemised billing statement, e.g. additional billing information, bill presentation, layout, format, e-mail, fax, printout, itemised bill per service or per account, cumulative billing, consolidated billing

Abstract

A system and method is disclosed for creating a personalized phone bill populated with names from a subscriber'"'"'s personal address book on the subscriber'"'"'s device. A billing application receives a request to generate a phone bill for a subscriber, and obtains usage data for that subscriber'"'"'s device. In one embodiment, the billing application then sends a request to a translation server to search a network address book, which is synchronized with the personal address book on a subscriber'"'"'s device, to match the usage data with the names from the network address book. The matched names are then transmitted from the translation server to the billing application, where the billing application includes the matched names in a usage section of the bill, thereby generating a personalized phone bill that a subscriber can more easily review and understand.

Claims

1. A method of creating a personalized phone bill using a subscriber'"'"'s personal address book, comprising:

obtaining usage data for a subscriber'"'"'s activity on a device;

obtaining entries from a subscriber'"'"'s personal address book;

comparing the usage data with the entries in the subscriber'"'"'s personal address book to find matching entries; and

listing the matching entries from the personal address book in a usage section of a subscriber'"'"'s phone bill, thereby creating a personalized phone bill.

2. The method of claim 1, further comprising obtaining the usage data for a subscriber'"'"'s activity on a device from a billing application.

3. The method of claim 1, further comprising obtaining the entries in the subscriber'"'"'s personal address book from a network address book stored on a network database, wherein the network address book is synchronized with the personal address book of the device.

4. The method of claim 3, further comprising synchronizing the subscriber'"'"'s personal address book with the network address book using a synchronization server.

5. The method of claim 4, further comprising communicating between the subscriber'"'"'s personal address book and the synchronization server using a Synchronization Markup Language (“

SyncML”

) message.

6. The method of claim 3, further comprising first determining if a subscriber has a network address book before obtaining the entries therefrom.

7. The method of claim 2, further comprising comparing the usage data with the entries in the subscriber'"'"'s personal address book using a translation server.

8. The method of claim 7, further comprising first sending a request from a billing application to the translation server to compare the usage data with the entries in a subscriber'"'"'s personal address book.

9. The method of claim 7, further comprising communicating the information on the matched entries from the translation server to the billing application, wherein the billing application generates the personalized phone bill.

10. The method of claim 7, further comprising using an Extensible Markup Language (“

XML”

) Data Management Service (“

DMS”

) server (collectively, “

XDMS server”

) as the translation server.

11. The method of claim 10, further comprising communicating between the translation server and the billing application using an XML Configuration Access Protocol (“

XCAP”

) message.

12. The method of claim 11, further comprising using a Java Database Connectivity (“

JDBC”

) message for communicating between the network database and the synchronization server, and for communicating between the translation server and the network database.

13. The method of claim 1, further comprising comparing the usage data with a system address book stored on a system database.

14. The method of claim 1, further comprising replacing the usage data on the personalized phone bill with the matching entries from the subscriber'"'"'s personal address book.

15. A system for creating a personalized phone bill using a subscriber'"'"'s personal address book, comprising:

a synchronization server to synchronize a subscriber'"'"'s personal address book with a network address book, wherein the network address book is stored on a network database;

a translation server for comparing a subscriber'"'"'s usage data with the information on the network address book to find matching entries;

a billing application for providing the subscriber'"'"'s usage data to the translation server, and for receiving the matching entries from the translation server to generate a personalized bill by listing the matching entries in a usage section of a subscriber'"'"'s phone bill.

16. The system of claim 15, further comprising a system address book stored on a system database for comparing a subscriber'"'"'s usage data thereto.

17. The system of claim 15, wherein the synchronization server communicates with the subscriber'"'"'s personal address book using a Synchronization Markup Language (“

SyncML”

) message.

18. The system of claim 15, wherein the translation server is an Extensible Markup Language (“

XML”

) Data Management Service (“

DMS”

) server (collectively, “

XDMS server”

).

19. The system of claim 15, wherein the translation communicates with the billing application using an XML Configuration Access Protocol (“

XCAP”

) message.

20. The system of claim 15, wherein the network database and the synchronization server and the translation server and the network database communicate using a Java Database Connectivity (“

JDBC”

) message.