GB2514744A

GB2514744A - Mobile telephone app

Info

Publication number: GB2514744A
Application number: GB1212839.3A
Authority: GB
Inventors: Louis Raphael Yadgaroff
Original assignee: SAMPOL Ltd
Current assignee: SAMPOL Ltd
Priority date: 2012-07-19
Filing date: 2012-07-19
Publication date: 2014-12-10
Also published as: GB201212839D0

Abstract

A mobile device 2 includes a call log application 4, the call log application detecting telephone calls or SMS messages sent or received using the mobile device. The call log application detects each telephone call and SMS and sends a call message to a server 8, the message including call log information for the respective telephone call or SMS message. By intercepting the end of each telephone call and sending a message to the server with call information, it is possible to collect information centrally and not through the network operator of the mobile device. It is possible to keep the server updated continually without requiring access to the call information which may be stored either on the mobile network or on the mobile device. Instead, the information is immediately available on the server.

Description

MOBILE TELEPHONE APP

The invention relates to an application stored on a mobile telephone, a network comprising a mobile telephone with such an application and a log server, and a method of operating a mobile telephone in conjunction with a server.

Related Art Storing information regarding incoming calls is known. The information may include the telephone number from which the incoming call is sent, and other information such as the time and duration of the call. Such information may be stored in a call log.

On a mobile device, the call log may be stored in the memory of the mobile device or a SIM card and accessed via the screen of that device.

An alternative way of capturing call information is that the mobile network provider also maintains a call log. In this case, calls are logged as they pass through the mobile network and recorded in a central server from which information is extracted, for example for billing purposes.

A hybrid call log is described by EP 1 662 764 which describes a number of such call logs and which also describes merging multiple call logs to form a single log in a single server.

Summary of Invention

According to the invention there is provided a call log application, the call log application being arranged to detect telephone calls or SMS message sent or received using the mobile device; to detect when each telephone call ends or the SMS is sent or received, and to send a call message to a server, the message including call log information for the respective telephone call or SMS message.

By intercepting the end of each telephone call and sending a message to the server with call information, it is possible to collect information centrally and not through the network operator of the mobile device.

This allows for improved collection of information. This can be very valuable, for example in a corporate environment, since the server can contain information from other sources and allow better integration of the mobile device use into other services.

In embodiments, the server also collects data from other sources, including in particular phone calls made on conventional telephone lines, or IP phone calls made using IF phone services. By adding mobile telephony data into this database, improved integration is possible.

By recording the information in a message sent after each telephone call, it is possible to keep the server updated continually without requiring access to the call information which may be stored either on the mobile network or on the mobile device. Instead, the information is immediately available on the server.

For a better understanding of the invention, embodiments will now be described with respect to the following drawings, in which: Figure 1 shows a schematic drawing of a system according to the invention; and Figure 2 is a flow chart illustrating the method.

Detailed Description

A mobile device 2, for example a mobile telephone, especially a so-called "smart phone", has an installed call log application, or call log app 4.

The call log app 4 is activated as each reportable event occurs. In the embodiment described, there are four such reportable events: Incoming call Outgoing call Incoming SMS Outgoing SMS.

The way in which this occurs depends on the environment of the particular call log application.

In the case that the mobile device is an Android (RTM) device or an iPhone (RTM) the application is triggered at the end of each call and the SMS is received, and the application then reads the relevant data from the call og database and transmits it as will be described below.

In the case that the mobile device is a Blackberry (RIM), the application is triggered when an SMS is received or sent. In the case of an incoming or outgoign call the application "Listens" to the call and is triggered upon completion. When the application is triggered it gathers information from the log and uploads to server, again using a message as described below.

On each event trigger, the app 4 sends a call message 6 to a server 8 including the telephone number of the call or SMS, the time, the duration of the incoming or outgoing call and the location of the mobile device 2 at the time of the call. This may be generated from the location services available in the mobile device, typically GPS. Alternatively or additionally the identifier of the base station to which the mobile device 2 is in wireless connection may be used as a location identifier.

In the embodiment, the call message is a data string transmitted by HTTP. A number of data items are sent in a string with a header, and various values separated by separators. The string includes one or more records, each record starting with a unique record identifier identifying the mobile device and also identifying the record number, so each record has a separate record number.

The data string is transmitted by the mobile device to a predetermined server.

The domain name of the server is included in the application and DNS-lookup (Domain name system lookup) is used to route the data string. This allows the server to be moved to a different IF (Internet protocol) address if required.

Thus, the data is effectively stored "in the cloud".

The server responds with an acknowledgement message (ACK).

A particular benefit in this embodiment is that the app 4 sends the message promptly after the end of the call or receipt of the SMS. Typically, assuming that the mobile device 2 has an internet connection, the app 4 will send the message within 10 seconds, preferably 5 seconds, of the end of the call though slightly longer time periods, for example up to a minute, may also be possible.

If no ACK is received the mobile device assumes that the message has not been received and resends the message. This is repeated until an ACK has been received. If there is no internet connectivity to the mobile device, the mobile device waits until there is an internet connection before sending the message.

The further values in the record include an identifier indicating whether the record relates to an incoming call, an outgoing call, an incoming SMS or an outgoing SMS.

In the case of a call, the record further includes values representing the call date, the call time, the length of the call, the telephone number of the other party to the call, and the location of the mobile device. In the case of a SMS message, the record includes values representing the SMS date, the SMS time, the length of the SMS message (in bytes), the telephone number of the other party to the SMS and the location of the mobile device.

Typically, each transmitted call message string simply relates to one telephone call or SMS and so each transmitted data string only includes one record, but the format of the string allows for multiple records to be transmitted in a single string, for example when multiple text messages are received at the same time which can occur for example when switching on the mobile device.

The data collected by the call log app 4 is not directly viewable locally and is only viewable by accessing the server 8.

Accordingly, the mobile telephone also includes a server access application 10. This may be implented using web browser functionality already included in smart phones.

Users may also access the data by a fixed web browser.

The information available from the server access application includes details of the user, voice calls, SMS messages and location.

The server 8 may in embodiments be a PBX call logger of the type used on local PBX exchanges to monitor calls on fixed line networks of traditional type or of IP calls. This allows integration of mobile call data with data on calls made on the fixed lines.

The PBX -type server, or indeed any server 8, may interface with the mobile device using an "API" (application programming interface) system to deliver the data via an IP socket or ODBC link with an FTP retrieval system.

The server 8 includes data access software to allow access to the data. The data access software has the following functionality.

A main screen is in "dashboard" format and lists calls made, received, missed, SMS made, received, and also optionally data sent and received.

Additionally, alerts may be displayed. These may be programmed by the user. For example, an alert may be generated if the mobile device calls a premium rate number.

Alerts may also be generated if the user calls specific numbers, for example a service department or a sales department.

The main screen also allows access to a searching functionality to allow the call records to be searched. For example, it is possible to search for calls made on specific dates, or at a specific location.

Location information may also be displayed on a map.

The embodiment accordingly delivers excellent integrated call logging of mobile devices.

Further, the embodiment allows timely access to the information, almost "live", and backing up of the information in case the mobile device is lost, damaged, or erased.

In a specific embodiment, the following fields are recorded for each call or SMS.

Note that the device ID is obtained from the mobile device by the application 4 and included in the message sent. Indeed, in this example all of the data in the server record is included in the message except for the record date which is added at the server.

Field Data Type Length Description

Record Date Date/Time Serves as a time stamp for when the record was created, it is automatically populated by the database server using local time Call Date Date/Time Date/Time for start of call or SMS Device ID Character 50 Unique device identifier Mobile No. Character 50 Mobile telephone number Record Type Character 1 C = Call, S = SMS Direction Character 1 I = Incoming, 0= Outgoing Duration in seconds for a call and blank for Duration Integer an SMS record U = Unanswered, A = Answered and blank Call Completed Character 1 for an SMS record Called/Callers Dialled number or Calling number if No. Character 50 presented, can be blank on incoming.

Longitude and latitude coordinates if GE'S GPS Character 250 enabled on mobile device Cell ID Integer Cell tower ID together with LAC, MNC and MCC can be used to give approximate location LAC Integer Location area code for cell tower MNC Integer Mobile network code identifies mobile carrier MCC Integer Mobile country code identifies country The record may also include a unique message identifier in the form of an integer value that increments on each message.

Those skilled in the art will realise that modifications of this may be used. In particular, the skilled person will adapt the workings of the application for different mobile devices as appropriate.

Claims

CLAIMS1. A mobile device, comprising a call log application, the call log application being arranged: to detect telephone calls or SMS message sent or received using the mobile device; to detect when each telephone call ends or the SMS is sent or received, and to send a call message to a server, the message including call log information for the respective telephone call or SMS message.
2. A mobile device according to claim 1, wherein the call log information for a telephone call included in the call message includes call time, and, where available, the telephone number of the other party to the call.
3. A mobile device according to claim 1 or 2, wherein the call log information further comprises the location of the mobile device.
4. A mobile device according to claim 1, 2 or 3 wherein the call message is sent within 10 s of the end of the call or the time the SMS is sent or received.
5. A mobile device according to any preceding claim wherein the call message includes at least some of the following fields: Call Date, Device ID, the ID of the mobile device, Mobile Number, the mobile number of the mobile device, Record Type, call or SMS, Direction, incoming or outgoing Duration, Call Completed, yes or no, Called/Callers Number, GPS, location by GPS Cell ID, LAO, location area code for base station, MNC, mobile network code, and MCO mobile country code.
6. A system, comprising: at least one mobile device according to any preceding claim; and a server containing a call database; wherein the server is arranged to receive call messages from the mobile and to store the call log information in the call database.
7. A system according to claim 6 wherein the server is additionally arranged to receive call log information from devices other than mobile devices.
8. A method of operation of a mobile device, comprising detecting telephone calls or SMS messages made using the mobile device using a call log application; detecting the end of each telephone call or SMS message with the call log application and then sending a call message to a server, the call message including call log information for the respective telephone call.
9. A method of operation of a mobile device according to claim 6, wherein the call log information included in the message includes call time, and, where available, the telephone number of the other party to the call.
10. A method of operation of a mobile device according to claim 6 or 7 wherein the call log information further comprises the location of the mobile device.
11. A method according to claim 8, 9 or 10 wherein the call message is sent within 10 s of the end of the call or the time the SMS is sent or received.
12. A method according to any of claims 8to llwherein the call messageincludes at least some of the following fields:Call Date, Device ID, the ID of the mobile device, Mobile Number, the mobile number of the mobile device, Record Type, call or SMS, Direction, incoming or outgoing Duration, Call Completed, yes or no, Called/Callers Number, GPS, location by GPS Cell ID, LAC, location area code for base station, MNC, mobile network code, and MCC mobile country code.
13. A method of operation of a system, comprising: operating at least one mobile device according to any of claims 8 to 12; receiving call messages from the mobile in the server; and storing the call log information from the received call messages in a call database in the server.
14. A computer program application, arranged to cause a mobile device to carry out a method according to any of claims 8 to 12 when run on the mobile device.