GB2504145A

GB2504145A - A method of displaying called contacts in an itemised telephone bill by matching telephone numbers to associated contacts on a communications device

Info

Publication number: GB2504145A
Application number: GB201212982A
Authority: GB
Inventors: Bryan Hill; Matthew Holmes; Martin Fitzpatrick
Original assignee: Vodafone IP Licensing Ltd
Current assignee: Vodafone IP Licensing Ltd
Priority date: 2012-07-20
Filing date: 2012-07-20
Publication date: 2014-01-22
Also published as: GB201212982D0

Abstract

There is described a method of rendering data on a communications device, the method comprising the steps of: receiving at the device a data set of identification codes (telephone numbers); accessing a contacts store of the device, the contacts store comprising one or more contacts, wherein each contact is associatable in the contacts store with at least one identification code; for each identification code in the data set that has an associated contact in the contacts store, matching the identification code with its associated contact; and rendering the matched contacts on the communications device. Thus, raw billing or other data may be sent from a mobile network to the device, and the device may then process the data in order to match identification codes (telephone numbers) against contacts. The handset may use an on-board contacts store, or a contacts store otherwise accessible or available to the handset, to provide a view of a mobile telephone bill to the user that displays called contacts instead of, or as well as, called telephone numbers. Advantageously, there is no need to synchronise a phone book between the handset and central server, as the method may be carried out within the handset.

Description

RENDERING DATA ON A COMMUNICATIONS DEVICE

Field of the Invention

The present invention relates to a method of rendering data on a communications device, especially a mobile communications device such as a mobile telephone. The invention also relates to a communications device configured to render data. The rendered data may be displayed as part of a

mobile telephone statement or invoice.

Background to the Invention

Currently, itemised mobile telephone bills consist of a list of activities carried out on the mobile account. Where these involve contacting another party identified by a fixed or mobile telephone number, the bill contains the telephone number of the contacted party. With the advent of extensive phone books or contacts lists in mobile phones, people generally do not know to whom these numbers relate. Unless they recognise the number, one must manually access the contacts list in order to determine who they have called. This is at the very least very time-consuming. Other semi-manual solutions rely on the user typing in names against phone numbers in order to generate a personalised bill.

A proposed automatic solution to address the above problem is disclosed in US 2009/0016508 Al. The method relies on the telephone uploading the contacts directory to a central server or cloud storage. The central server then determines the name-and-number relationship and renders an itemised bill, thereby matching telephone numbers with their associated contact. However, this upload/synchronisation adds complexity and cost to the overall solution.

Furthermore, the system requires that personal contacts details be sent to a backend server. The user's contacts are therefore more susceptible to a security breach, which raises concerns with the user's privacy.

There is therefore a need in the art to provide a method and device that may more conveniently, safely and/or more efficiently render a data set of identification codes, such as telephone numbers, to include associated contacts.

The present invention seeks to address this need in the art.

Summary of the Invention

Against this background, and in a first aspect of the invention, there is provided a method of rendering data on a communications device. A data set of identification codes is received at the device. A contacts store of the device is then accessed. The contacts store comprises one or more contacts. Each contact is associatable in the contacts store with at least one identification code.

For each identification code in the data set that has an associated contact in the contacts store, the identification code is matched with its associated contact.

Then, the matched contacts are rendered on the communications device.

Thus, raw billing or other data may be sent from a mobile network to the device, and the device may then process the data in order to match identification codes (e.g. telephone numbers) against contacts. The handset may use an on-board contacts store, or a contacts store otherwise accessible or available to the handset (such as a set of externally stored contacts), to provide a view of a mobile telephone bill to the user that displays called contacts instead of, or as well as, called telephone numbers. Advantageously, there is no need to synchronise a phone book between the handset and a central server, as the method may be carried out within the handset. Not only does this reduce cost, but it increases the security around the sensitive nature of the contacts store, as the data does not need to be transmitted outside of the device.

The identification codes may be subscriber identification codes capable of identifying a subscriber to a network. Alternatively, the identification codes may identify a fixed-line telephone number. More generally, an identification code may be any code capable of identifying a called party. Typically, the identification codes are telephone numbers. The data set of identification codes may be received at the device by any suitable means, and for example may be downloaded from the user's mobile network, or from the Internet. In some embodiments, the data may be transferred directly from a mass storage device such as USB key. The data set may comprise a list of identification codes, and may be received at the device in list form.

Typically, the data set may be transmitted from a communications server, such as a backend mobile network server, to a subscriber's mobile device. The contacts store of the device may be located in a memory component of the device. It may take the form of a database or directory within which details of the user's contacts are stored, such as name, telephone number (identification code), identifying picture, e-mail address, etc. In some embodiments, the contacts store does not have to be stored on the device but instead may be accessed from a location external to the device, e.g. from a remote database. Thus, contact data external to the communications device may be retrieved in order to access the contacts store of the device.

The association between the contacts within the contacts store and their identification codes is typically a direct, one-to-one association. In some embodiments, however, a contact may be associated with more than one identification code. When matching the identification codes of the data set with corresponding contacts in the contacts store, the method may select a identification code from the data set and determine whether the selected identification code has a contact associated with it in the contacts store. If not, the method may then move on to another identification code in the data set, until all the identification codes in the data set have been assessed.

The rendering of the matched contacts may take many forms, and for example includes converting the data set into a different format (such as a.pdf file format or Microsoft Word format), or displaying the data set on a screen or other display means.

The matching step may comprise comparing a portion of the identification code in the data set to a corresponding portion of the identification code stored in the contacts store. For example, in one embodiment, only the last six digits of a telephone number in the data set are compared to the corresponding last six digits of a telephone number in the contacts store, to determine whether a match can be made. Fewer or greater portions of the identification codes may be compared or contrasted in order to determine a match.

The data set of identification codes may be part of a statement, such as a financial statement comprising information such as account activity, etc. For example, a subscriber's monthly mobile telephone usage and associated charges may be displayed to them in the form of a statement or invoice received on their mobile telephone. The statement or invoice may list the subscriber's monthly airtime usage, and display the telephone numbers contacted by the user next to the amount of airtime spent with each contacted party.

APIs may be used to extract identification codes from the data set. For example, the data set may be received in XML format, and the APIs may drill down the data set in order to locate and extract the identification codes from the data set, for subsequent processing (e.g. for matching of the identification codes to contacts in the contacts store).

The identification codes forming part of the statement may be replaced with the matched contacts before rendering the statement on the communications device. For example, the file containing the data set of identification codes may be replaced with a file containing the rendered matched contacts, showing the matches between identification codes and associated contacts.

The method may render or generate a statement having thereon the matched contacts. For example, instead of receiving the data set as part of a statement, the device may generate its own statement (or invoice) displaying the matched contacts.

The user of the mobile communications device may be prompted to associate a identification code in the data set with a contact if the identification code is not associated with a contact in the contacts store. Thus, if it is found that a identification code in the data set does not have an associated contact in the contacts store, then the device may be arranged to prompt or invite the user to enter the identification code and an associated contact into the contacts store.

The identification code and its associated contact may then be stored in the contacts store. In other words, a bill presentation application on the handset could prompt the user to add contact details if there was a billing record without a matching contact directory entry. New contacts added into the directory on the handset can easily be reflected in the view of the bill on the handset.

In a second aspect of the present invention, there is provided a computer-readable medium for storage on a mobile device. The computer-readable medium comprises executable code configured such that, when executed on a computer, the code will perform any of the above-described methods. The code may be stored on any suitable medium, such as a flash drive, a CD-ROM, a hard disk, etc., or may be sent as a signal.

In a third aspect of the invention, there is provided a communications device. The device comprises logic configured to receive a data set of identification codes. The logic is further configured to access contacts of the communications device. Each contact is associatable with at least one identification code. For each identification code in the data set that has an associated contact of the communications device, the logic is yet further configured to match the identification code with its associated contact. The logic is still further configured to render the matched contacts.

The communications device may be a mobile telephone, a communications tablet, a personal digital assistance, etc. In some embodiments, the device may be mobile, such as a laptop computer. Equally, the device need not be easily portable and, for example, could be a desktop computer.

The device may comprise a network interface. The logic may be even further configured to receive the contacts of the mobile communications from a network, using the network interface. The device may comprise a memory for storing one or more contacts. The logic may be still further configured to render the matched contacts on a display of the communications device.

Other features of the invention include the following, although this should not be construed as being an exhaustive list.

An application on the device may provide different views and summaries of the rendered data set, such as the contact called the most, the contact incurring the highest cost for the week/month/year, etc., the total cost incurred for calling national/international contacts, the total number of calls made to contacts subscribed to the same mobile network as the user, etc. The application may further provide a summary for any given contact: number of times called, total call cost, number of SMSs sent, total SMS cost, total overall cost, etc. The application may also make use of any group information in the contacts store to provide summaries for friends, colleagues, family, etc. This may depend on the grouping functions set up in the contacts store. The application may insert photographs of particular contacts into the rendered data set. The application may interact with an enhanced call log application, to populate the call log with the cost of each call. The user may then access the call log on the device and see how much each call came to. The application may store all historic information, thereby allowing the user to go back and look at totals over the past three months or past year (for example). The application may receive billing data as soon as it becomes available -the data need not be monthly data, but instead may be accessed in near real-time, daily, weekly, etc. The application may work for pay-as-you-go as well as contract subscribers.

It should be noted that any feature described above may be used with any particular aspect or embodiment of the invention.

Brief Summary of the Drawings

Several embodiments of the present invention will now be described by way of example and with reference to the following drawings, in which: Figure 1 is a schematic view of a mobile communications device communicating with a communications server, in accordance with a preferred embodiment of the present invention; Figure 2 shows a list of identification codes, shown in a pre-rendered state; Figure 3 shows the list of identification codes of Figure 2, shown in a rendered state; and Figure 4 is a flow diagram illustrating the steps taken by a method of rendering a list of matched contacts, according to a preferred embodiment of the present invention.

Detailed Description of Preferred Embodiments

Whilst various embodiments of the present invention are described below, the invention is not limited to these embodiments and variations of these embodiments may well fall within the scope of the invention which is to be limited only by the appended claims.

The invention provides a method of matching existing contacts information with billing records to allow display of billing records that refer to people/contacts rather than telephone numbers. This makes it much easier for people to understand who they have been communicating with, and how much it has cost them.

In accordance with a preferred embodiment of the present invention, Figure 1 shows a mobile device communicating with a communications server.

Mobile device 10 comprises a memory, a processor, a display and a power source, for example a battery. The processor is able to access data from the memory and manipulate it in order to carry out particular functions, as described below. Communications server 12, in the present embodiment, is a backend server of a mobile communications network. It stores network usage records of subscribers using the network to place calls, communicate with other mobile devices, etc. In the memory of mobile device 10 is located contacts store 14. Contacts store 14 comprises a data set of contacts (which in the present embodiment is a list of contacts) that the user of mobile device 10 typically communicates with.

Each contact in contacts store 14 is associated with one or more telephone numbers.

In order to render a set of matched contacts, mobile device 10 and communications server 12 interact in the following fashion. Firstly, as indicated by arrow A, communications server 12 transmits over the mobile network a list (e.g. data set) of telephone numbers that mobile device 10 has been used to contact in the past month. In the present embodiment, the list of telephone numbers form part of a monthly bill, and comprises both a subscriber identification code (Bryan Hill (M)) and fixed-line identification codes (British Gas Help and Bengal Spice). Figure 2 shows list 20 of telephone numbers 22 in the bill. Next to each telephone number is listed the time spent 24 contacting the telephone number as well as the associated cost 26.

Upon receiving list 20 of telephone numbers, mobile device 10 accesses contacts store 14 stored on its memory, as seen by arrow B. The processor of mobile device 10 then uses APIs to compare sections or portions of telephone numbers 22 on the bill to corresponding portions of the telephone numbers stored in contacts store 14. When a match is found, the processor of mobile device 10 is able to associate the contact in contacts store 14 with the telephone number on list 20. The processor runs through the entire list of telephone numbers that are on the bill.

When all the telephone numbers on list 20 have been processed, mobile device 10 renders a list of matched contacts, as seen by arrow C. Rendered list 16 is shown in more detail in Figure 3. The rendered list may be displayed on the display screen of mobile device 10.

Rendered list 30 is similar to list 20 apart from telephone numbers 22 having been replaced by contacts 32. Call times 34 and cost listings 36 remain unchanged. Therefore, the user of mobile device 10 is able to determine the contacts with whom he has been in communication instead of being presented with an eleven-digit telephone number. In the present embodiment, rendered list also includes metadata 38, in this case a pie chart illustrating the split in airtime between the three contacts featuring on rendered list 30.

Figure 4 illustrates the method steps taken by mobile device 10 in order to render list 20. In step 40, list 20 of telephone numbers is received at mobile device 10 from communications server 12, as shown by arrow A in Figure 1. In step 42, mobile device 10 accesses contacts store 14, as shown by arrow B in Figure 1. In step 44, portions of telephone numbers 22 in list 20 are compared to corresponding portions of telephone numbers in contacts store 14. In step 46, when a match is made, the contacts in contacts store 14 that are associated with the telephone numbers in list 20 are matched to those telephone numbers.

Finally, in step 48, mobile device 10 renders list 32 of contacts matched with their associated telephone numbers.

Many combinations, modifications, or alterations to the features of the above embodiments will be readily apparent to the skilled person and are intended to form part of the invention. Furthermore, a person skilled in the art will recognise that any of the features described as specifically relating to one embodiment may be used in any other embodiment, by making the appropriate changes.

Claims

CLAIMS1. A method of rendering data on a communications device, the method comprising the steps of: receiving at the device a data set of identification codes; accessing a contacts store of the device, the contacts store comprising one or more contacts, wherein each contact is associatable in the contacts store with at least one identification code; for each identification code in the data set that has an associated contact in the contacts store, matching the identification code with its associated contact; and rendering the matched contacts on the communications device.
2. The method of claim 1, wherein the matching step comprises comparing a portion of the identification code in the data set to a corresponding portion of the identification code stored in the contacts store.
3. The method of any preceding claim, wherein the one or more identification codes in the data set are telephone numbers.
4. The method of any preceding claim, wherein the data set of identification codes is received from a communications server.
5. The method of any previous claim, further comprising using APIs to extract the identification codes from the data set.
6. The method of any preceding claim, wherein the data set of identificationcodes is part of a statement.
7. The method of claim 6, further comprising replacing the identification codes forming part of the statement with the matched contacts before renderingthe statement on the communications device.
8. The method of any preceding claim, further comprising rendering astatement having thereon the matched contacts.
9. The method of any preceding claim, further comprising prompting a user of the mobile communications device to associate a identification code in the data set with a contact if the identification code is not associated with a contact in the contacts store.
10. The method of claim 9, further comprising storing the identification code and its associated contact in the contacts store.
11. The method according to any previous claim, wherein the step of accessing the contacts store comprises retrieving contact data external to the communications device.
12. A computer-readable medium having instructions stored thereon which, when executed on a computer, are configured to carry out the method of any of claims 1 -11.
13. A communications device comprising logic configured to: receive a data set of identification codes; access contacts of the communications device, wherein each contact is associatable with at least one identification code; for each identification code in the data set that has an associated contact of the communications device, matching the identification code with its associated contact; and render the matched contacts.
14. The communications device of claim 13, further comprising a memory for storing one or more contacts.
15. The communications device of claim l3or 14, wherein the logic is further configured to render the matched contacts on a display of the communications device.