CA2742282A1 - User interface and method of viewing unified communications events on a mobile device - Google Patents
User interface and method of viewing unified communications events on a mobile device Download PDFInfo
- Publication number
- CA2742282A1 CA2742282A1 CA2742282A CA2742282A CA2742282A1 CA 2742282 A1 CA2742282 A1 CA 2742282A1 CA 2742282 A CA2742282 A CA 2742282A CA 2742282 A CA2742282 A CA 2742282A CA 2742282 A1 CA2742282 A1 CA 2742282A1
- Authority
- CA
- Canada
- Prior art keywords
- wireless device
- communications
- events
- communication
- mobile device
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/26—Devices for calling a subscriber
- H04M1/27—Devices whereby a plurality of signals may be stored simultaneously
- H04M1/274—Devices whereby a plurality of signals may be stored simultaneously with provision for storing more than one subscriber number at a time, e.g. using toothed disc
- H04M1/2745—Devices whereby a plurality of signals may be stored simultaneously with provision for storing more than one subscriber number at a time, e.g. using toothed disc using static electronic memories, e.g. chips
- H04M1/27453—Directories allowing storage of additional subscriber data, e.g. metadata
- H04M1/2746—Sorting, e.g. according to history or frequency of use
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/57—Arrangements for indicating or recording the number of the calling subscriber at the called subscriber's set
- H04M1/575—Means for retrieving and displaying personal data about calling party
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
- H04M1/7243—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
- H04M1/7243—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages
- H04M1/72436—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages for text messaging, e.g. SMS or e-mail
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
- H04M1/72445—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality for supporting Internet browser applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2250/00—Details of telephonic subscriber devices
- H04M2250/60—Details of telephonic subscriber devices logging of communication history, e.g. outgoing or incoming calls, missed calls, messages or URLs
Abstract
A user interface and method for viewing communications events on a mobile device includes a user interface, a communications event handler, and a communications event database is disclosed herein. The communications event handler interfaces with the database and the user interface to provide a user of the mobile device with a communications event history associated with the correspondent of an incoming communications event. Additionally the communications event handler interfaces with the database and the user interface to provide a user of the mobile device with a communications event history for a specified correspondent.
Description
USER INTERFACE AND METHOD OF VIEWING UNIFIED
COMMUNICATIONS EVENTS ON A MOBILE DEVICE
[0001] This application is a divisional application of Canadian application serial No. 2,471,831 filed December 23, 2002.
FIELD OF THE INVENTION
COMMUNICATIONS EVENTS ON A MOBILE DEVICE
[0001] This application is a divisional application of Canadian application serial No. 2,471,831 filed December 23, 2002.
FIELD OF THE INVENTION
[0002] This invention relates generally to a user interface for messaging.
More particularly, the invention relates to user interfaces for displaying a communications event in context with select stored communications events.
BACKGROUND OF THE INVENTION
More particularly, the invention relates to user interfaces for displaying a communications event in context with select stored communications events.
BACKGROUND OF THE INVENTION
[0003] Most cellular networks such as Code Division Multiple Access (CDMA) and Global Service Mobile (GSM) networks support data services in addition to standard telephony based services. Short Messaging Service (SMS) and Wireless Application Protocol (WAP) are data centric services available on many cellular networks. Data networks, such as MobiTexTM, DatatacTM, as well as advanced networks such as General Packet Radio Service (GPRS), Universal Mobile Telecommunications System (UMTS), Enhanced Data for GSM Enhancement (EDGE) and Ix that overlay cellular networks, allow an appropriately configured mobile device to offer data services such as e-mail, web browsing, as well as SMS and Multimedia messaging service (MMS) messaging, and WAP data sessions.
[0004] Communications events include telephone calls, both sent and received, SMS messages both sent and received, e-mail correspondences both sent and received, and wireless application protocol sessions, among other data based transactions. Each communications event has at least two parties, the user of the mobile device and at least one correspondent. Each correspondent can have multiple contact addresses, such a work phone number, a home phone number, a mobile phone number, an SMS address, and a plurality of email addresses.
[0005] Mobile devices were originally intended to provide telephony services, and have, with the addition of data centric features, become complex to operate.
The user interfaces currently available for viewing the history of communications events on a mobile device, typically only enable a user to view a history of one type of communications events, or a subset thereof, and from that history view the contents of a communications event. This makes sense in a voice only environment, but the addition of data services has exposed this interface paradigm as insufficient.
The user interfaces currently available for viewing the history of communications events on a mobile device, typically only enable a user to view a history of one type of communications events, or a subset thereof, and from that history view the contents of a communications event. This makes sense in a voice only environment, but the addition of data services has exposed this interface paradigm as insufficient.
[0006] Figure 1 illustrates a user interface 10 of the prior art. User interface 10 displays a notification 12 that a new message, such as an e-mail or SMS message has been received. The user of the mobile device is presented with the option to either exit the notification 14, or read the received message 16. This user interface does not permit the user to view the context in which the received message should be interpreted.
[0007] Figure 2 illustrates a second user interface of the prior art 18. User interface 18 illustrates a list of recent telephone calls. Once again the user is presented with the option to exit 14, and additionally is given the option to place a call 22 to one of the recent callers, or to delete 20 a caller from the list of recent calls. Call lists of this type provide either separate lists of sent and received calls, or provide an integrated list of sent at received calls.
[0008] Presently, when a mobile device receives an incoming communications event, such as an SMS message, the only information provided to the user is that an SMS message has been received. This notification may indicate the originating SMS address. The user can then either view the SMS message, or scroll through a collective in-box of SMS messages to determine the last SMS
message received from the same originating address. If the user wishes to view the last SMS message sent to the party originating the incoming SMS message, the user must check the SMS out box on the mobile device. Additionally, if the user would like to check to see when the last call made to the SMS originating address, or received from the originating SMS address occurred on, the user must check either the incoming or outgoing call logs. If email services are integrated in the mobile device, an additional list must be examined. This provides a plurality of different lists that a user must examine to determine the communications event history concerning a correspondent. If a correspondent has multiple contact addresses, viewing all communications events with the correspondent is further complicated.
message received from the same originating address. If the user wishes to view the last SMS message sent to the party originating the incoming SMS message, the user must check the SMS out box on the mobile device. Additionally, if the user would like to check to see when the last call made to the SMS originating address, or received from the originating SMS address occurred on, the user must check either the incoming or outgoing call logs. If email services are integrated in the mobile device, an additional list must be examined. This provides a plurality of different lists that a user must examine to determine the communications event history concerning a correspondent. If a correspondent has multiple contact addresses, viewing all communications events with the correspondent is further complicated.
[0009] It is, therefore, desirable to provide a method and system for handling communications events in a manner that provides the user of a mobile device with the context of the communications event through a presentation of the communications event history associated with a given correspondent.
SUMMARY OF THE INVENTION
SUMMARY OF THE INVENTION
[0010] It is an object of the present invention to obviate or mitigate at least one disadvantage of previous communications event handling systems.
[0011] According to one example embodiment, there is provided a wireless device that includes a viewing screen; a processor; a memory device that stores communication events, wherein the communication events include at least two different communication types; and a communication event software interface module executed by the processor that (a) filters each of the communication events stored in the memory device to identify one or more select communication events meeting a pre-set criteria, and (b) displays the one or more select communication events on the viewing screen.
[0016] Other aspects and features of the present invention will become apparent to those ordinarily skilled in the art upon review of the following description of specific embodiments of the invention in conjunction with the accompanying figures.
BRIEF DESCRIPTION OF THE DRAWINGS
[0017] Embodiments of the present invention will now be described, by way of example only, with reference to the attached Figures, wherein:
Figure 1 illustrates a communications event handling system of the prior art;
Figure 2 illustrates a communications event history listing of the prior art;
Figure 3 is a flow chart illustrating a method of the present invention;
Figure 4 is a flow chart illustrating an alternate method of the present invention;
Figure 5 illustrates an exemplary system of the present invention;
Figure 6 illustrates a data flow for a mobile device of the present invention; and Figure 7 illustrates a data flow for a mobile device of the present invention.
DETAILED DESCRIPTION
[0018] Generally, the present invention provides a method and system for tracking originating, and received, communications events on a mobile device.
By tracking received and transmitted communications events, a mobile device can provide a user with the context of the communication with any party.
[0019] In the present invention a mobile device provides an integrated user interface through which a user can view communications events in which a particular correspondent has partaken. A mobile device of the present invention makes use of a communications event database to track all incoming and outgoing communications events with various correspondents.
[0020] The present invention provides a unified view of communications events, so that a user can determine the context of any received communications event, or can determine the context of a communications event to be placed. Thus, upon receipt of a SMS message, or other communications events, after identifying the type of the communications event, in addition to notifying the user that a message has been received, the mobile device will present the user with a listing of the most recent communications events that are associated with the originating address of the message. The user is also given the option of viewing information about the prior communications events, which would include viewing prior SMS messages, viewing information about the data received for a wireless application protocol browsing session, or the call length and dates of any placed or received calls. This information will allow the user to better contextualise the content of the new message. In a presently preferred embodiment, the user is able to set criteria that must be matched by the properties of an incoming communications event in order for the retrieval of the communications event history to begin. This allows the user the ability to only be presented with a communications event history for selected correspondents, and selected types of communications events.
[0021] Figure 3 illustrates an exemplary method of the present invention. In step 100, the mobile device receives a communications event. Preferably, as a part of receiving the communications event in step 100, the mobile device identifies the communications event as one of a set of known communications event types including a phone call, an e-mail message and an SMS message, among other known types of communications events. Upon receipt of the communications event, the mobile device identifies the correspondent in the communications event in step 102. The identification of the correspondent is preferably carried out using call display, a signalling system 7 (SS7) type feature if the communications event is a phone call, through an analysis of an e-mail header if the communications event is an e-mail message or through parsing the header information in a SMS message. Upon identifying the correspondent in step 102, the mobile device uses the correspondent's identification to retrieve and display a communications event history detailing the communications event the correspondent has been involved with in step 104. The communications event history retrieved in step 104 is typically retrieved from a database either in the mobile device, or accessible to the mobile device, that is used to track communications events. Upon retrieval of the communications event history from the database, the mobile device displays the communications event history to the user. Preferably, the displaying of the information to the user allows the user to view prior SMS and e-mail messages to determine the context of a received message. Additionally, the user is preferably able to view a listing of all sent and received calls involving the correspondent along with the time and date at which the call occurred, the length of the call if the call was answered, and an indication if the call was or was not answered. In a presently preferred embodiment of the present method of the invention, the mobile device displays a summary of communications events with the correspondent that both originated from, and were received by the mobile device. It is, however, fully contemplated that in certain embodiments the user is presented with only incoming, or outgoing communications events in the summary. It is preferable that the user be provided with an option to view incoming and outgoing messages on a single display, only incoming messages, or only outgoing communications events.
[0022] One skilled in the art will readily appreciate that when the mobile device of the present invention receives a communications event in step 100 the communications event can be any of a number of event types. Typically, upon receiving a communications event in step 100, the mobile device analyses the incoming event and determines its specific type. This determination of the communications event type can be performed in numerous ways understood by those skilled in the art. One such method involves determining the communications event type based on the channel over which the communications event was received. For example, if the device supports GSM
communications as well as GPRS communications, and the mobile device is capable of supporting voice, SMS, e-mail and WAP type communications events, a communications event received over a GPRS communications channel will be either a WAP or e-mail based communication, whereas a communications event received over the GSM communications channel will be either an SMS or voice type communications event. After narrowing the selection to the two choices based on the communications channel, the mobile device can parse the header associated with the incoming communications event to determine its specific type. For example, a WAP data session and an email message typically conform to different standard formats, and based on an analysis of the format, a determination can be made. The differentiation between an SMS message and a telephony based voice communications event is known in the art, and can be easily implemented. It is envisioned that on advanced networks all data and voice traffic will be carried on the same channel, much as both voice and data are carried in a Voiceover-IP data network. In such a network, header information associated with datagrams, or other data units, provide identification of the different types of communications event. One skilled in the art will readily appreciate that a number of alternate method can be implemented without departing from the scope of the present invention.
[0023] Figure 4 illustrates a further embodiment of the method of Figure 3. In the method illustrated in Figure 4, steps 100, 102, and 104 remain the same.
Additionally, in step 106 after a communications event has been received the communications event is added to the database of the mobile device. This step can be performed at any point in the process, and is shown as following the receipt of the communications event as a matter of preference. In step 108, the mobile device presents a user interface that allows the user to either ignore or answer an incoming telephone call, or alternatively to either read a message or exit the notification in the case of a received SMS, or e-mail message. It is preferable that these options be presented along with the retrieved communications event history, so that the user can make a decision as to what to do with the incoming communications event based on the event history. In step 110, the database is updated to reflect the communications event status.
[0024] As described above, the user interface preferably indicates to the user whether or not a SMS or e-mail message has been read, or replied to, and whether or not a call was answered. These factors are collectively described as the status of a message. In step 110, the database is updated to reflect whether or not the user chose to ignore or answer a call in step 108, or whether the user chose to read the message or exit the notification in step 108. In a presently preferred embodiment, the identification of the correspondent in step 102 is preformed by cross-referencing the information obtained through either call display, the analysis of the e-mail header, or the analysis of the SMS message to determine the originating address from which the communications event was placed, with information contained in an address book accessible to the mobile device. It is common for numerous correspondents to have a variety of contact addresses, including telephone numbers corresponding to cellular phones, home phones, and office phones, as well as a plurality of e-mail, and SMS
addresses.
Through cross-linking of the correspondent identification information obtained in step 102 with the address book of the mobile device, it is possible to provide the user of the mobile device with a communications event history that includes all correspondence, and telephone calls made to, or answered from the identified correspondent.
[0025] Figure 5 illustrates an embodiment of mobile device 112 according to the present invention. Mobile device 112 preferably includes database 116, transceiver 118, processor 122, and display 120. In alternate embodiments of the present invention, mobile device 112 does not include database 116, and instead accesses a central server which hosts database 116 through a wireless link. In additional embodiment, mobile device 112 either includes an address book having a plurality of contact addresses for a variety of correspondents, or has access to such an address book using a wireless connection.
Communications event software interface module 126 is preferably a software application executed by processor 122, and is a specific example of a communications event handler according to the present invention. It is contemplated that the communications event handler can be implemented as a separate hardware component, which may or may not implement software based routines. In a further embodiment, the communications event handler can be hardware enabled and integrated with processor 122.
[0026] Database 116 is preferably structured to have at least one table 128.
In table 128, four data fields are identified. The first identified data field is status 130. Status field 130 indicates whether or not an e-mail or SMS message has been read, or whether or not a telephone call was answered. Type field 132 denotes the type of communications event of the record. Type 132 is used to identify whether the communications event was an e-mail message, a telephone call, or an SMS message. In a presently preferred embodiment, the type field also indicates whether the communications event originated from, or was received by mobile device 112. The third entry in table 128 is data field 134.
The data field 134 contains information about the communications event of this record. In a presently preferred embodiment, the data field for a SMS or e-mail message would include the body of the message. For a telephone call, in a presently preferred embodiment, data field 134 would indicate the time that the call was placed, and the duration of the call. The final field of Table 128 is index 138. One skilled in the art will readily appreciate that a number of indexing mechanisms can be employed in either relational, or flat file, database types.
The use of index 138 is to be able to easily identify and find a record related to a specific call. One skilled in the art will recognize that a number of entries in this Table will be introduced as the mobile device 112 begins communications events with various correspondents. One skilled in the art will recognize that in conjunction with an address book accessible by mobile device 112, the index field 138 and status field 130 can be correlated to determine a communications event history for a number of different correspondents. Transceiver 118 is used to both transmit and receive communications events. Upon receipt of a communications event, transceiver 118 begins to pass data to processor 122. In conjunction with communications event software interface module 126, processor 122 performs the method illustrated in Figure 3. As a result, processor 122 interacts with display 120 upon receipt of a communications event and after querying database 116. Thus, processor 122 uses display 120 to provide interface 124. Interface 124 illustrates a date and time, as well as the number of e-mail, SMS, WAP, and telephone call type communications events between the mobile device and the correspondent. As is illustrated in interface 124, the status field 130, the type field 132, and data field 134 of table 128 are used to provide the user with an indication that unread mail messages exist, sent mail messages, received mail messages and placed calls have been made between the mobile device and the correspondent.
[0027] Transceiver 118 can be replaced by separate transmitters and receivers, and is intended to allow the mobile device to receive communications over a wireless link. Presently preferred embodiments of the present invention employ transceivers capable of receiving CDMA voice communication as well as 1X data communications, in an alternate embodiment, the transceiver is designed to receive GPRS, and GSM data and voice services, respectively. One skilled in the art will readily appreciate that a transceiver capable of receiving a variety of other combinations of voice and data protocols are contemplated in the present invention. [0028] Display 120 is preferably a liquid crystal display, and may optionally be a touch sensitive liquid crystal display, so that a user can be provided with user interface acknowledgement buttons on the screen of the device itself. Implementations of graphical interfaces on liquid crystal displays, and touch sensitive liquid crystal displays will be well understood by those skilled in the art of mobile device design. It is fully contemplated that though mobile device 112 has been described herein as having display 120, that display 120 can be replaced with other user interfaces. Examples of such user interfaces include audio interfaces and dynamic Braille pads for use by individuals with visual impairments.
[0029] Processor 122 is connected to the database 116, and is capable of performing database queries on database 116 to obtain information from the call event database 116. Additionally, processor 122 is connected to an address book so that the identified correspondent from step 102 can be cross-referenced to the address book and match to a name in the address book. This will allow mobile device 112 to provide the user with a call event history from the call event database 116 that includes all communications events in which the identified correspondence has partaken, regardless of the communication address used by the correspondent. Upon identifying the correspondent through cross-referencing the address book, processor 122 queries communications event database 116 to obtain a listing of all communications events between the user of the mobile device and the identified correspondent. The results of this query are then formatted and provided to the user on display 120.
[0030] In a presently preferred embodiment of the system illustrated in Figure 4, the communications event software interface module 126 includes a communications event type identifier. The identifier is for determining the type associated with the communications event. The identified type is stored in type field 132 in database 116. In the illustrated embodiment, the identifier is preferably a software routine, and in a more generic implementation is, a module in the communications event handler.
[0031] Figure 6 illustrates an exemplary embodiment of a data flow of the present invention. A pre-defined trigger event 140, such as an incoming SMS
message is used as a preset criterion 142. At least one criterion 144 is set in the preset criteria 142. The at least one criteria 144 may be communication from a specific party. In this case, preset criteria 142 would correspond to both the triggered event, the receipt of a SMS message, and the at least one criterion 144, correspondence with a given individual. This would set the preset criteria 142 as correspondence with a certain individual via a SMS message. Preset criteria 142 is used, in a presently preferred embodiment, so that only communications events fitting a predefined profile will results in the retrieval of a communications event history from database 116. In alternate embodiments of the present inventions, all communications events will result in the retrieval of a communications event history from database 116 using a method, such as the one illustrated in Figure 3. Transceiver 118 is used by mobile device 112 to receive a communications event. Upon receipt of any communications event the' preset criteria is compared to the received communications event. If the preset criteria 142 and the received communications event from transceiver 118 match, the process proceeds through the flow to decision 148, where a determination is made of whether or not the communications event matches the preset criteria. If the communications event matches the preset criteria, mobile device 112 proceeds to step 150 where the selected communications event is added to the unified communications event list in step 156, which is stored in database 116. At this point, mobile device 112 marks the communications event as processed in step 152. If the next communications event did not match the preset criteria in decision 148, mobile device 112 would have proceeded to mark the communications event as processed 152 without selecting the communications event and adding it to the unified communications event list 156. Following the marking of the communications event as processed in step 152, a decision is made as to whether or not all communications events have been processed in decision 154. If all outstanding communications events have not been processed, mobile device 112 returns to step 148. Otherwise, in conjunction with the unified communications event list 156, which is obtained from database 116, user interface 124 is provided on display 120.
[0032] The comparison as illustrated, in Figure 6, to determine whether or not a set of criteria has been matched, will now be illustrated in Figure 7 in greater detail with reference to the embodiment of the table 128 as shown in Figure 5.
Figure 7 illustrates database 116 which has contains table 128 having fields for status 130, type 132, data 134 and an index 138. The at least one criteria 144 is predetermined by the user. Upon receipt of an incoming communications event, the at least one criteria is compared to the status 130, type 132, data 134, and index 138 of the incoming communications event. If the event matches the status criteria in 158, it is then compared to the type criteria in step 160.
If in step 160, the event matches the type criteria, it is further compared to the data criteria in 162, and pending successful completion of the event matching the data criteria, the event is matched to the index criteria in step 164. If in any of the comparisons 158, 160, 162 or 164, the event is not matched to one of the criteria, mobile device 112 proceeds to a does not match state 168. If all of these comparisons are successful, mobile device 112 proceeds to a match state 166. Upon reaching a match state 166, processor 122 queries database 116 to retrieve the communications event history. If does not match state 168 is reached, processor 122 waits for the next communications event. The order as implied by Figure 7 is not a required order, and the comparisons can be carried out in any order or in parallel. The presently illustrated order was selected for simplicity, and is to be considered merely exemplary in nature.
[0033] As described above, a presently preferred embodiment of the present invention cross-links the correspondent identification information with information contained in an address book accessible to mobile device 112. This allows the address book information to be used to link SMS addresses, telephone numbers for cellular, home and work phones, a plurality of e-mail addresses, and WAP accessible sites associated with a single individual or entity, to each other. This cross-linking of address based information allows a user to properly put in context all communication with the individual from whom a message has been received.
[0034] In many mobile devices 112, the ability to integrate with a centralized e-mail server, using such standard protocols as the point of presence (POP) protocol is used to provide a seamless transition between the mobile device and the central email account. In this case, a user of the mobile device 112 is able to reply to e-mail messages from either a desktop computer, or mobile device 112 seamlessly. In a presently preferred embodiment, the mobile device 112 is updated through contact with a central server to reflect that e-mail messages replied to from the desktop have been replied to. Thus, the user of the mobile device 112 will be able to completely determine the context of a received message.
[0035] In an exemplary embodiment, all communications events including messages and calls originating from the mobile device, messages received and sent from a desktop computer, and all other communications events accessible to the mobile device are stored in a database 116. Database 116 is preferably integrated with the mobile device 112, though it is fully contemplated that database 116 can reside in a central server and be accessed wirelessly by mobile device 112. The implementation of such a system will be well understood .
by those skilled in the art [0036] The database 112 preferably tracks the type 132 of communications event, the data 134 contained in the communications event, and preferably a status 130 of the event. The type of the event 132 typically denotes whether it was a telephone call, a SMS message, an e-mail message, a WAP data transmission, or other data based transaction. The type field 132 also indicates whether the communication was received by the user of the mobile device, or originated from the user of the mobile device. The data field 134 typically contains the body of an e-mail message, the body of a SMS message, information related to the WAP data transmission, or call length, as appropriate.
The status 130 of the message typically indicates whether a placed or received call was answered, or if a received message was replied to. One skilled in the art will readily appreciate that it is preferable to index this data with an index field 138, however, the implementation of an index is purely optional, though understood by one skilled in the art. Thus, in operation, a mobile device 112 of the present invention will receive a communications event and prior to displaying notification of this event, be it an e-mail message, a SMS message, or a telephone call, the processor of the mobile device queries the database 116 using the calling number as a key. The calling number is typically transmitted to the processor of the mobile device using such services as call display, or visual call waiting, which will be well understood to those skilled in the art. The query to the database 116 using the incoming number or address, as a search perimeter will result in a query response containing a list of all communications events between the mobile device 112 or any account associated with mobile device 112, and the incoming address. This information is then presented to the user on the display 120 of the mobile device so that prior to answering a telephone call the user will know the date of the last communication.
Alternatively, if a received SMS message is generating the notification, the user is provided with the context of the SMS message as a result of being able to view prior SMS messages, prior e-mail messages, and is also presented with the dates of the last call initiated to the SMS originating address.
[0037] In a presently preferred embodiment, the communications event history retrieved from database 116 is sorted chronologically, so that the newest information is presented at the top of the list. Additionally, a summary of the number of e-mail messages, SMS messages, WAP sessions, and telephone calls between the mobile device 112 or any account associated with it, and the party originating the message is presented.
[0038] One skilled in the art will readily appreciate that database 116 can be either a relational database, or a flat file database. Although the use of a relational database provides numerous benefits understood by those skilled in art, it is conceivable that an implementation of the present invention can be provided through the use of a flat file database. Additionally, one skilled in the art will readily appreciate that a number of methods of implementing the present invention using a relational database exist. For exemplary purposes, one such method is presented. It should be understood by those skilled in the art, that the presented method is intended to be exemplary, and not limiting of the scope of the present invention.
[0039] In a non-illustrated embodiment, any event, regardless of whether it is a communications event or any other event detectable by the mobile device 112, can trigger the message software interface module to use a particular pre-set criteria 142 to display select communications events in the communications event history. For example, in a mobile device 112 having an integrated date book, when a conference call scheduled in a datebook occurs, processor 122 triggers the communication software interface module 126 with pre-set criteria 142 to preferably select and represent a pending outgoing conference call communications event with higher priority than other select communications events. Alternatively, when mobile device 112 receives a communication, such as an e-mail message, SMS message, WAP page response, voice/video call, processor 122 triggers the communication software interface module 126 with pre-set criteria 142 to preferably select and represent the received communications event with higher priority than other select communications events.
[0040] The pre-set criteria can also match communications event data. For instance, to view all communications events sent to or received from a particular contact, the pre-set criteria may include matching select communications event data with all of the specific contact information found in an address book entry for the contact. As an example, consider all communications events sent to or received from a stockbroker. Contact information for the stockbroker is preferably kept in the address book. Preferably, each address book entry contains a variety of fields that can be mapped to one or more communications addresses supported by the mobile device. In the entry corresponding to the stockbroker, for example, if the following fields are defined: telephone number, mobile phone number, fax number, email address, and URL's; then an example preferable mapping to message types follows. The phone, mobile, and fax numbers are mapped to voice and/or video communications events. The mobile number is additionally mapped to an SMS address for SMS type communications events. The email address is mapped to email communications events. The URL's are mapped to corresponding communications event types. For instance an http URL can be mapped to web and/or WAP, whereas an FTP URL (File Transfer Protocol) can be mapped to an ftp communications event. All communications events, including phone calls, SMS communications events, emails, web communications events, WAP communications events or other communications events that match at least one field in the stockbroker contact entry of the address book would then be selected by the communications event software interface module 126, and would be displayed. Preferably, the presentation of the retrieved data from database 116 would show the contact name, such as "stockbroker" as defined by the preset criteria 142.
[0041] In another embodiment, the communications event software interface module 126 may identify related stored communications events by comparing the communications event data of each stored communications event 128 with keywords selected by the user. This alternative method of matching the current communications event with select stored communications events 128 may be implemented by itself, or as a means of further limiting the select communications events identified by the other methods described above. To continue the previous stockbroker example, further preset criteria can be added to create a further filter that operates on the select communications events, for instance. The communications event data in the new filter may include stock quotes obtained via WAP using an URL as well as notes taken during phone calls with the stockbroker. The user may therefore decide to choose preset criteria that, as well as matching contact information, further matches a regular expression, such as for example, the keywords "buy" or "sell". By allowing the user to configure the pre-set criteria, the communications event software interface module 126 unifies communications events based on pre-set criteria which are important to the user at a specific point in time, for instance, allowing the user to unify a stock pick provided by a stockbroker over a phone call or e-mail with a stock quote retrieved subsequently by the user via WAP in order to take a decision to either communicate a buy, sell, or hold directive to his stockbroker or to a trading system.
[0042] Thus far the system of the present invention has been described as integrated in mobile device 112, it will be understood by one skilled in the art that a software implementation of the present invention can be executed on a number of different platforms, or packaged for use on different platforms. In one such example, a desktop computer can be configured to use the communications event handler of the present invention to provide a communications event history for received email messages. Additionally, the desktop computer may be attached to an SMS modem so that it is capable of receiving SMS messages and can then provide a communications event history to a user to permit the user to determine the context of a received SMS message. Additionally, the desktop computer can be configured so that it is in communication with a Voice-over-Internet-Protocol (VoIP) telephone, so that all incoming and outgoing calls are recorded to the communications event database 116. In such an implementation, the communications event handler would use a communications event database interface to communicate with either a local or remote communications event database 116 to retrieve the communications event histories associated with correspondents identified using either call display information, or addressing information extracted from the header of an incoming email or SMS message.
[0043] The above-described embodiments of the present invention are intended to be examples only. Alterations, modifications and variations may be effected to the particular embodiments by those of skill in the art without departing from the scope of the invention, which is defined solely by the claims appended hereto.
[0016] Other aspects and features of the present invention will become apparent to those ordinarily skilled in the art upon review of the following description of specific embodiments of the invention in conjunction with the accompanying figures.
BRIEF DESCRIPTION OF THE DRAWINGS
[0017] Embodiments of the present invention will now be described, by way of example only, with reference to the attached Figures, wherein:
Figure 1 illustrates a communications event handling system of the prior art;
Figure 2 illustrates a communications event history listing of the prior art;
Figure 3 is a flow chart illustrating a method of the present invention;
Figure 4 is a flow chart illustrating an alternate method of the present invention;
Figure 5 illustrates an exemplary system of the present invention;
Figure 6 illustrates a data flow for a mobile device of the present invention; and Figure 7 illustrates a data flow for a mobile device of the present invention.
DETAILED DESCRIPTION
[0018] Generally, the present invention provides a method and system for tracking originating, and received, communications events on a mobile device.
By tracking received and transmitted communications events, a mobile device can provide a user with the context of the communication with any party.
[0019] In the present invention a mobile device provides an integrated user interface through which a user can view communications events in which a particular correspondent has partaken. A mobile device of the present invention makes use of a communications event database to track all incoming and outgoing communications events with various correspondents.
[0020] The present invention provides a unified view of communications events, so that a user can determine the context of any received communications event, or can determine the context of a communications event to be placed. Thus, upon receipt of a SMS message, or other communications events, after identifying the type of the communications event, in addition to notifying the user that a message has been received, the mobile device will present the user with a listing of the most recent communications events that are associated with the originating address of the message. The user is also given the option of viewing information about the prior communications events, which would include viewing prior SMS messages, viewing information about the data received for a wireless application protocol browsing session, or the call length and dates of any placed or received calls. This information will allow the user to better contextualise the content of the new message. In a presently preferred embodiment, the user is able to set criteria that must be matched by the properties of an incoming communications event in order for the retrieval of the communications event history to begin. This allows the user the ability to only be presented with a communications event history for selected correspondents, and selected types of communications events.
[0021] Figure 3 illustrates an exemplary method of the present invention. In step 100, the mobile device receives a communications event. Preferably, as a part of receiving the communications event in step 100, the mobile device identifies the communications event as one of a set of known communications event types including a phone call, an e-mail message and an SMS message, among other known types of communications events. Upon receipt of the communications event, the mobile device identifies the correspondent in the communications event in step 102. The identification of the correspondent is preferably carried out using call display, a signalling system 7 (SS7) type feature if the communications event is a phone call, through an analysis of an e-mail header if the communications event is an e-mail message or through parsing the header information in a SMS message. Upon identifying the correspondent in step 102, the mobile device uses the correspondent's identification to retrieve and display a communications event history detailing the communications event the correspondent has been involved with in step 104. The communications event history retrieved in step 104 is typically retrieved from a database either in the mobile device, or accessible to the mobile device, that is used to track communications events. Upon retrieval of the communications event history from the database, the mobile device displays the communications event history to the user. Preferably, the displaying of the information to the user allows the user to view prior SMS and e-mail messages to determine the context of a received message. Additionally, the user is preferably able to view a listing of all sent and received calls involving the correspondent along with the time and date at which the call occurred, the length of the call if the call was answered, and an indication if the call was or was not answered. In a presently preferred embodiment of the present method of the invention, the mobile device displays a summary of communications events with the correspondent that both originated from, and were received by the mobile device. It is, however, fully contemplated that in certain embodiments the user is presented with only incoming, or outgoing communications events in the summary. It is preferable that the user be provided with an option to view incoming and outgoing messages on a single display, only incoming messages, or only outgoing communications events.
[0022] One skilled in the art will readily appreciate that when the mobile device of the present invention receives a communications event in step 100 the communications event can be any of a number of event types. Typically, upon receiving a communications event in step 100, the mobile device analyses the incoming event and determines its specific type. This determination of the communications event type can be performed in numerous ways understood by those skilled in the art. One such method involves determining the communications event type based on the channel over which the communications event was received. For example, if the device supports GSM
communications as well as GPRS communications, and the mobile device is capable of supporting voice, SMS, e-mail and WAP type communications events, a communications event received over a GPRS communications channel will be either a WAP or e-mail based communication, whereas a communications event received over the GSM communications channel will be either an SMS or voice type communications event. After narrowing the selection to the two choices based on the communications channel, the mobile device can parse the header associated with the incoming communications event to determine its specific type. For example, a WAP data session and an email message typically conform to different standard formats, and based on an analysis of the format, a determination can be made. The differentiation between an SMS message and a telephony based voice communications event is known in the art, and can be easily implemented. It is envisioned that on advanced networks all data and voice traffic will be carried on the same channel, much as both voice and data are carried in a Voiceover-IP data network. In such a network, header information associated with datagrams, or other data units, provide identification of the different types of communications event. One skilled in the art will readily appreciate that a number of alternate method can be implemented without departing from the scope of the present invention.
[0023] Figure 4 illustrates a further embodiment of the method of Figure 3. In the method illustrated in Figure 4, steps 100, 102, and 104 remain the same.
Additionally, in step 106 after a communications event has been received the communications event is added to the database of the mobile device. This step can be performed at any point in the process, and is shown as following the receipt of the communications event as a matter of preference. In step 108, the mobile device presents a user interface that allows the user to either ignore or answer an incoming telephone call, or alternatively to either read a message or exit the notification in the case of a received SMS, or e-mail message. It is preferable that these options be presented along with the retrieved communications event history, so that the user can make a decision as to what to do with the incoming communications event based on the event history. In step 110, the database is updated to reflect the communications event status.
[0024] As described above, the user interface preferably indicates to the user whether or not a SMS or e-mail message has been read, or replied to, and whether or not a call was answered. These factors are collectively described as the status of a message. In step 110, the database is updated to reflect whether or not the user chose to ignore or answer a call in step 108, or whether the user chose to read the message or exit the notification in step 108. In a presently preferred embodiment, the identification of the correspondent in step 102 is preformed by cross-referencing the information obtained through either call display, the analysis of the e-mail header, or the analysis of the SMS message to determine the originating address from which the communications event was placed, with information contained in an address book accessible to the mobile device. It is common for numerous correspondents to have a variety of contact addresses, including telephone numbers corresponding to cellular phones, home phones, and office phones, as well as a plurality of e-mail, and SMS
addresses.
Through cross-linking of the correspondent identification information obtained in step 102 with the address book of the mobile device, it is possible to provide the user of the mobile device with a communications event history that includes all correspondence, and telephone calls made to, or answered from the identified correspondent.
[0025] Figure 5 illustrates an embodiment of mobile device 112 according to the present invention. Mobile device 112 preferably includes database 116, transceiver 118, processor 122, and display 120. In alternate embodiments of the present invention, mobile device 112 does not include database 116, and instead accesses a central server which hosts database 116 through a wireless link. In additional embodiment, mobile device 112 either includes an address book having a plurality of contact addresses for a variety of correspondents, or has access to such an address book using a wireless connection.
Communications event software interface module 126 is preferably a software application executed by processor 122, and is a specific example of a communications event handler according to the present invention. It is contemplated that the communications event handler can be implemented as a separate hardware component, which may or may not implement software based routines. In a further embodiment, the communications event handler can be hardware enabled and integrated with processor 122.
[0026] Database 116 is preferably structured to have at least one table 128.
In table 128, four data fields are identified. The first identified data field is status 130. Status field 130 indicates whether or not an e-mail or SMS message has been read, or whether or not a telephone call was answered. Type field 132 denotes the type of communications event of the record. Type 132 is used to identify whether the communications event was an e-mail message, a telephone call, or an SMS message. In a presently preferred embodiment, the type field also indicates whether the communications event originated from, or was received by mobile device 112. The third entry in table 128 is data field 134.
The data field 134 contains information about the communications event of this record. In a presently preferred embodiment, the data field for a SMS or e-mail message would include the body of the message. For a telephone call, in a presently preferred embodiment, data field 134 would indicate the time that the call was placed, and the duration of the call. The final field of Table 128 is index 138. One skilled in the art will readily appreciate that a number of indexing mechanisms can be employed in either relational, or flat file, database types.
The use of index 138 is to be able to easily identify and find a record related to a specific call. One skilled in the art will recognize that a number of entries in this Table will be introduced as the mobile device 112 begins communications events with various correspondents. One skilled in the art will recognize that in conjunction with an address book accessible by mobile device 112, the index field 138 and status field 130 can be correlated to determine a communications event history for a number of different correspondents. Transceiver 118 is used to both transmit and receive communications events. Upon receipt of a communications event, transceiver 118 begins to pass data to processor 122. In conjunction with communications event software interface module 126, processor 122 performs the method illustrated in Figure 3. As a result, processor 122 interacts with display 120 upon receipt of a communications event and after querying database 116. Thus, processor 122 uses display 120 to provide interface 124. Interface 124 illustrates a date and time, as well as the number of e-mail, SMS, WAP, and telephone call type communications events between the mobile device and the correspondent. As is illustrated in interface 124, the status field 130, the type field 132, and data field 134 of table 128 are used to provide the user with an indication that unread mail messages exist, sent mail messages, received mail messages and placed calls have been made between the mobile device and the correspondent.
[0027] Transceiver 118 can be replaced by separate transmitters and receivers, and is intended to allow the mobile device to receive communications over a wireless link. Presently preferred embodiments of the present invention employ transceivers capable of receiving CDMA voice communication as well as 1X data communications, in an alternate embodiment, the transceiver is designed to receive GPRS, and GSM data and voice services, respectively. One skilled in the art will readily appreciate that a transceiver capable of receiving a variety of other combinations of voice and data protocols are contemplated in the present invention. [0028] Display 120 is preferably a liquid crystal display, and may optionally be a touch sensitive liquid crystal display, so that a user can be provided with user interface acknowledgement buttons on the screen of the device itself. Implementations of graphical interfaces on liquid crystal displays, and touch sensitive liquid crystal displays will be well understood by those skilled in the art of mobile device design. It is fully contemplated that though mobile device 112 has been described herein as having display 120, that display 120 can be replaced with other user interfaces. Examples of such user interfaces include audio interfaces and dynamic Braille pads for use by individuals with visual impairments.
[0029] Processor 122 is connected to the database 116, and is capable of performing database queries on database 116 to obtain information from the call event database 116. Additionally, processor 122 is connected to an address book so that the identified correspondent from step 102 can be cross-referenced to the address book and match to a name in the address book. This will allow mobile device 112 to provide the user with a call event history from the call event database 116 that includes all communications events in which the identified correspondence has partaken, regardless of the communication address used by the correspondent. Upon identifying the correspondent through cross-referencing the address book, processor 122 queries communications event database 116 to obtain a listing of all communications events between the user of the mobile device and the identified correspondent. The results of this query are then formatted and provided to the user on display 120.
[0030] In a presently preferred embodiment of the system illustrated in Figure 4, the communications event software interface module 126 includes a communications event type identifier. The identifier is for determining the type associated with the communications event. The identified type is stored in type field 132 in database 116. In the illustrated embodiment, the identifier is preferably a software routine, and in a more generic implementation is, a module in the communications event handler.
[0031] Figure 6 illustrates an exemplary embodiment of a data flow of the present invention. A pre-defined trigger event 140, such as an incoming SMS
message is used as a preset criterion 142. At least one criterion 144 is set in the preset criteria 142. The at least one criteria 144 may be communication from a specific party. In this case, preset criteria 142 would correspond to both the triggered event, the receipt of a SMS message, and the at least one criterion 144, correspondence with a given individual. This would set the preset criteria 142 as correspondence with a certain individual via a SMS message. Preset criteria 142 is used, in a presently preferred embodiment, so that only communications events fitting a predefined profile will results in the retrieval of a communications event history from database 116. In alternate embodiments of the present inventions, all communications events will result in the retrieval of a communications event history from database 116 using a method, such as the one illustrated in Figure 3. Transceiver 118 is used by mobile device 112 to receive a communications event. Upon receipt of any communications event the' preset criteria is compared to the received communications event. If the preset criteria 142 and the received communications event from transceiver 118 match, the process proceeds through the flow to decision 148, where a determination is made of whether or not the communications event matches the preset criteria. If the communications event matches the preset criteria, mobile device 112 proceeds to step 150 where the selected communications event is added to the unified communications event list in step 156, which is stored in database 116. At this point, mobile device 112 marks the communications event as processed in step 152. If the next communications event did not match the preset criteria in decision 148, mobile device 112 would have proceeded to mark the communications event as processed 152 without selecting the communications event and adding it to the unified communications event list 156. Following the marking of the communications event as processed in step 152, a decision is made as to whether or not all communications events have been processed in decision 154. If all outstanding communications events have not been processed, mobile device 112 returns to step 148. Otherwise, in conjunction with the unified communications event list 156, which is obtained from database 116, user interface 124 is provided on display 120.
[0032] The comparison as illustrated, in Figure 6, to determine whether or not a set of criteria has been matched, will now be illustrated in Figure 7 in greater detail with reference to the embodiment of the table 128 as shown in Figure 5.
Figure 7 illustrates database 116 which has contains table 128 having fields for status 130, type 132, data 134 and an index 138. The at least one criteria 144 is predetermined by the user. Upon receipt of an incoming communications event, the at least one criteria is compared to the status 130, type 132, data 134, and index 138 of the incoming communications event. If the event matches the status criteria in 158, it is then compared to the type criteria in step 160.
If in step 160, the event matches the type criteria, it is further compared to the data criteria in 162, and pending successful completion of the event matching the data criteria, the event is matched to the index criteria in step 164. If in any of the comparisons 158, 160, 162 or 164, the event is not matched to one of the criteria, mobile device 112 proceeds to a does not match state 168. If all of these comparisons are successful, mobile device 112 proceeds to a match state 166. Upon reaching a match state 166, processor 122 queries database 116 to retrieve the communications event history. If does not match state 168 is reached, processor 122 waits for the next communications event. The order as implied by Figure 7 is not a required order, and the comparisons can be carried out in any order or in parallel. The presently illustrated order was selected for simplicity, and is to be considered merely exemplary in nature.
[0033] As described above, a presently preferred embodiment of the present invention cross-links the correspondent identification information with information contained in an address book accessible to mobile device 112. This allows the address book information to be used to link SMS addresses, telephone numbers for cellular, home and work phones, a plurality of e-mail addresses, and WAP accessible sites associated with a single individual or entity, to each other. This cross-linking of address based information allows a user to properly put in context all communication with the individual from whom a message has been received.
[0034] In many mobile devices 112, the ability to integrate with a centralized e-mail server, using such standard protocols as the point of presence (POP) protocol is used to provide a seamless transition between the mobile device and the central email account. In this case, a user of the mobile device 112 is able to reply to e-mail messages from either a desktop computer, or mobile device 112 seamlessly. In a presently preferred embodiment, the mobile device 112 is updated through contact with a central server to reflect that e-mail messages replied to from the desktop have been replied to. Thus, the user of the mobile device 112 will be able to completely determine the context of a received message.
[0035] In an exemplary embodiment, all communications events including messages and calls originating from the mobile device, messages received and sent from a desktop computer, and all other communications events accessible to the mobile device are stored in a database 116. Database 116 is preferably integrated with the mobile device 112, though it is fully contemplated that database 116 can reside in a central server and be accessed wirelessly by mobile device 112. The implementation of such a system will be well understood .
by those skilled in the art [0036] The database 112 preferably tracks the type 132 of communications event, the data 134 contained in the communications event, and preferably a status 130 of the event. The type of the event 132 typically denotes whether it was a telephone call, a SMS message, an e-mail message, a WAP data transmission, or other data based transaction. The type field 132 also indicates whether the communication was received by the user of the mobile device, or originated from the user of the mobile device. The data field 134 typically contains the body of an e-mail message, the body of a SMS message, information related to the WAP data transmission, or call length, as appropriate.
The status 130 of the message typically indicates whether a placed or received call was answered, or if a received message was replied to. One skilled in the art will readily appreciate that it is preferable to index this data with an index field 138, however, the implementation of an index is purely optional, though understood by one skilled in the art. Thus, in operation, a mobile device 112 of the present invention will receive a communications event and prior to displaying notification of this event, be it an e-mail message, a SMS message, or a telephone call, the processor of the mobile device queries the database 116 using the calling number as a key. The calling number is typically transmitted to the processor of the mobile device using such services as call display, or visual call waiting, which will be well understood to those skilled in the art. The query to the database 116 using the incoming number or address, as a search perimeter will result in a query response containing a list of all communications events between the mobile device 112 or any account associated with mobile device 112, and the incoming address. This information is then presented to the user on the display 120 of the mobile device so that prior to answering a telephone call the user will know the date of the last communication.
Alternatively, if a received SMS message is generating the notification, the user is provided with the context of the SMS message as a result of being able to view prior SMS messages, prior e-mail messages, and is also presented with the dates of the last call initiated to the SMS originating address.
[0037] In a presently preferred embodiment, the communications event history retrieved from database 116 is sorted chronologically, so that the newest information is presented at the top of the list. Additionally, a summary of the number of e-mail messages, SMS messages, WAP sessions, and telephone calls between the mobile device 112 or any account associated with it, and the party originating the message is presented.
[0038] One skilled in the art will readily appreciate that database 116 can be either a relational database, or a flat file database. Although the use of a relational database provides numerous benefits understood by those skilled in art, it is conceivable that an implementation of the present invention can be provided through the use of a flat file database. Additionally, one skilled in the art will readily appreciate that a number of methods of implementing the present invention using a relational database exist. For exemplary purposes, one such method is presented. It should be understood by those skilled in the art, that the presented method is intended to be exemplary, and not limiting of the scope of the present invention.
[0039] In a non-illustrated embodiment, any event, regardless of whether it is a communications event or any other event detectable by the mobile device 112, can trigger the message software interface module to use a particular pre-set criteria 142 to display select communications events in the communications event history. For example, in a mobile device 112 having an integrated date book, when a conference call scheduled in a datebook occurs, processor 122 triggers the communication software interface module 126 with pre-set criteria 142 to preferably select and represent a pending outgoing conference call communications event with higher priority than other select communications events. Alternatively, when mobile device 112 receives a communication, such as an e-mail message, SMS message, WAP page response, voice/video call, processor 122 triggers the communication software interface module 126 with pre-set criteria 142 to preferably select and represent the received communications event with higher priority than other select communications events.
[0040] The pre-set criteria can also match communications event data. For instance, to view all communications events sent to or received from a particular contact, the pre-set criteria may include matching select communications event data with all of the specific contact information found in an address book entry for the contact. As an example, consider all communications events sent to or received from a stockbroker. Contact information for the stockbroker is preferably kept in the address book. Preferably, each address book entry contains a variety of fields that can be mapped to one or more communications addresses supported by the mobile device. In the entry corresponding to the stockbroker, for example, if the following fields are defined: telephone number, mobile phone number, fax number, email address, and URL's; then an example preferable mapping to message types follows. The phone, mobile, and fax numbers are mapped to voice and/or video communications events. The mobile number is additionally mapped to an SMS address for SMS type communications events. The email address is mapped to email communications events. The URL's are mapped to corresponding communications event types. For instance an http URL can be mapped to web and/or WAP, whereas an FTP URL (File Transfer Protocol) can be mapped to an ftp communications event. All communications events, including phone calls, SMS communications events, emails, web communications events, WAP communications events or other communications events that match at least one field in the stockbroker contact entry of the address book would then be selected by the communications event software interface module 126, and would be displayed. Preferably, the presentation of the retrieved data from database 116 would show the contact name, such as "stockbroker" as defined by the preset criteria 142.
[0041] In another embodiment, the communications event software interface module 126 may identify related stored communications events by comparing the communications event data of each stored communications event 128 with keywords selected by the user. This alternative method of matching the current communications event with select stored communications events 128 may be implemented by itself, or as a means of further limiting the select communications events identified by the other methods described above. To continue the previous stockbroker example, further preset criteria can be added to create a further filter that operates on the select communications events, for instance. The communications event data in the new filter may include stock quotes obtained via WAP using an URL as well as notes taken during phone calls with the stockbroker. The user may therefore decide to choose preset criteria that, as well as matching contact information, further matches a regular expression, such as for example, the keywords "buy" or "sell". By allowing the user to configure the pre-set criteria, the communications event software interface module 126 unifies communications events based on pre-set criteria which are important to the user at a specific point in time, for instance, allowing the user to unify a stock pick provided by a stockbroker over a phone call or e-mail with a stock quote retrieved subsequently by the user via WAP in order to take a decision to either communicate a buy, sell, or hold directive to his stockbroker or to a trading system.
[0042] Thus far the system of the present invention has been described as integrated in mobile device 112, it will be understood by one skilled in the art that a software implementation of the present invention can be executed on a number of different platforms, or packaged for use on different platforms. In one such example, a desktop computer can be configured to use the communications event handler of the present invention to provide a communications event history for received email messages. Additionally, the desktop computer may be attached to an SMS modem so that it is capable of receiving SMS messages and can then provide a communications event history to a user to permit the user to determine the context of a received SMS message. Additionally, the desktop computer can be configured so that it is in communication with a Voice-over-Internet-Protocol (VoIP) telephone, so that all incoming and outgoing calls are recorded to the communications event database 116. In such an implementation, the communications event handler would use a communications event database interface to communicate with either a local or remote communications event database 116 to retrieve the communications event histories associated with correspondents identified using either call display information, or addressing information extracted from the header of an incoming email or SMS message.
[0043] The above-described embodiments of the present invention are intended to be examples only. Alterations, modifications and variations may be effected to the particular embodiments by those of skill in the art without departing from the scope of the invention, which is defined solely by the claims appended hereto.
Claims (15)
1. A wireless device, comprising:
a viewing screen;
a processor;
a memory device that stores communication events, wherein the communication events include at least two different communication types; and a communication event software interface module executed by the processor that (a) filters each of the communication events stored in the memory device to identify one or more select communication events meeting a pre-set criteria, and (b) displays the one or more select communication events on the viewing screen.
a viewing screen;
a processor;
a memory device that stores communication events, wherein the communication events include at least two different communication types; and a communication event software interface module executed by the processor that (a) filters each of the communication events stored in the memory device to identify one or more select communication events meeting a pre-set criteria, and (b) displays the one or more select communication events on the viewing screen.
2. The wireless device of claim 1, wherein the at least two different communication types are from the group comprising: e-mail, SMS, WAP, voice call, instant messaging session, SIP, calendar events, game turns, notes, tasks, and address cards.
3. The wireless device of claim 1, wherein the communication events include at least one communication event identifier selected from the group comprising: e-mail address, MSISDN, URI, IP address, PIN, and name.
4. The wireless device of claim 1, wherein the pre-set criteria for the one or more select communication events is configurable by a user of the wireless device.
5. The wireless device of claim 1, wherein the pre-set criteria for the one or more select communication events comprises a condition that the user has not attended to the communication events.
6. The wireless device of claim 1, wherein the communication event software interface module executed by the processor represents and displays the pre-set criteria.
7. The wireless device of claim 6, wherein the pre-set criteria representation comprises the number of unattended messages.
8. The wireless device of claim 6, wherein the pre-set criteria representation comprises the type of unattended messages.
9. The wireless device of claim 1, wherein the pre-set criteria is a contact matching condition between a contact in an address book and one or more select communication events.
10. The wireless device of claim 9, wherein the display of the one or more select communication events on the view screen is according to the contact in the address book.
11. The wireless device of any one of claims 1-10, wherein the stored communication events are communication events that have been transmitted or received by the wireless device.
12. The wireless device of any one of claims 1-11, wherein the at least two different types of communication events are displayed in a unified view.
13. The wireless device of any one of claims 1-12, wherein the communication event software interface module executed by the processor receives a request to display communication events based on an identified correspondent.
14. The wireless device of any one of claims 1-13, wherein the communication event software interface module executed by the processor filters each stored communication event to identify one or more communication events associated with the identified correspondent.
15. The wireless device of any one of claims 1-14, wherein the communication event software interface module executed by the processor to display the one or more filtered communication events having the identified correspondent associated therewith.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US34213001P | 2001-12-26 | 2001-12-26 | |
| US60/342,130 | 2001-12-26 | ||
| CA2471831A CA2471831C (en) | 2001-12-26 | 2002-12-23 | User interface and method of viewing unified communications events on a mobile device |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2471831A Division CA2471831C (en) | 2001-12-26 | 2002-12-23 | User interface and method of viewing unified communications events on a mobile device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2742282A1 true CA2742282A1 (en) | 2003-07-10 |
| CA2742282C CA2742282C (en) | 2014-12-16 |
Family
ID=23340467
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2742282A Expired - Lifetime CA2742282C (en) | 2001-12-26 | 2002-12-23 | User interface and method of viewing unified communications events on a mobile device |
| CA2471831A Expired - Lifetime CA2471831C (en) | 2001-12-26 | 2002-12-23 | User interface and method of viewing unified communications events on a mobile device |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2471831A Expired - Lifetime CA2471831C (en) | 2001-12-26 | 2002-12-23 | User interface and method of viewing unified communications events on a mobile device |
Country Status (10)
| Country | Link |
|---|---|
| US (4) | US20050130631A1 (en) |
| EP (1) | EP1461935B1 (en) |
| CN (2) | CN1625886A (en) |
| AT (1) | ATE357109T1 (en) |
| AU (1) | AU2002351644A1 (en) |
| CA (2) | CA2742282C (en) |
| DE (1) | DE60218899T2 (en) |
| ES (1) | ES2396560T3 (en) |
| HK (2) | HK1072333A1 (en) |
| WO (1) | WO2003056789A1 (en) |
Families Citing this family (275)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6826407B1 (en) | 1999-03-29 | 2004-11-30 | Richard J. Helferich | System and method for integrating audio and visual messaging |
| US6253061B1 (en) | 1997-09-19 | 2001-06-26 | Richard J. Helferich | Systems and methods for delivering information to a transmitting and receiving device |
| US6636733B1 (en) | 1997-09-19 | 2003-10-21 | Thompson Trust | Wireless messaging method |
| US7003304B1 (en) | 1997-09-19 | 2006-02-21 | Thompson Investment Group, Llc | Paging transceivers and methods for selectively retrieving messages |
| US6983138B1 (en) | 1997-12-12 | 2006-01-03 | Richard J. Helferich | User interface for message access |
| US8645137B2 (en) | 2000-03-16 | 2014-02-04 | Apple Inc. | Fast, language-independent method for user authentication by voice |
| US8615566B1 (en) | 2001-03-23 | 2013-12-24 | Synchronoss Technologies, Inc. | Apparatus and method for operational support of remote network systems |
| DE60218899T2 (en) * | 2001-12-26 | 2007-12-06 | Research In Motion Ltd., Waterloo | USER INTERFACE AND METHOD FOR LOOKING AT UNIFORM COMMUNICATION EVENTS IN A MOBILE DEVICE |
| US6873692B1 (en) * | 2002-03-29 | 2005-03-29 | Bellsouth Intellectual Property Corporation | Telephone synchronization with software applications and documents |
| GB0306937D0 (en) * | 2003-03-26 | 2003-04-30 | Intellprop Ltd | Telecommunications services apparatus |
| JP2004120555A (en) * | 2002-09-27 | 2004-04-15 | Hitachi Electronics Service Co Ltd | Cellular phone having communication information editing display function for each mail communication party |
| US7428580B2 (en) | 2003-11-26 | 2008-09-23 | Aol Llc | Electronic message forwarding |
| US7590696B1 (en) | 2002-11-18 | 2009-09-15 | Aol Llc | Enhanced buddy list using mobile device identifiers |
| US7219143B1 (en) * | 2002-12-04 | 2007-05-15 | Unisys Corporation | Automatic notification using specific log file for environmental condition via FTP server |
| US7116976B2 (en) | 2003-12-08 | 2006-10-03 | Thomas C Douglass | Adaptable communication techniques for electronic devices |
| US7669134B1 (en) | 2003-05-02 | 2010-02-23 | Apple Inc. | Method and apparatus for displaying information during an instant messaging session |
| US7684550B2 (en) * | 2003-05-20 | 2010-03-23 | Oc Concepts, Inc. | Customer information system |
| WO2005010715A2 (en) | 2003-07-21 | 2005-02-03 | Fusionone, Inc. | Device message management system |
| US7653693B2 (en) | 2003-09-05 | 2010-01-26 | Aol Llc | Method and system for capturing instant messages |
| EP1665745A1 (en) | 2003-09-02 | 2006-06-07 | Matsushita Electric Industrial Co., Ltd. | Mobile terminal and incoming/outgoing call history management method |
| TWI226181B (en) * | 2003-09-12 | 2005-01-01 | Asustek Comp Inc | Method for rapidly browsing call list and the device thereof |
| KR100697416B1 (en) * | 2003-09-30 | 2007-03-20 | 교세라 가부시키가이샤 | Mobile communication terminal, information providing system, and computer readable recording medium storing program |
| US7069003B2 (en) * | 2003-10-06 | 2006-06-27 | Nokia Corporation | Method and apparatus for automatically updating a mobile web log (blog) to reflect mobile terminal activity |
| KR20050053278A (en) * | 2003-12-02 | 2005-06-08 | 삼성전자주식회사 | Method for searching short message in mobile phone |
| US7729688B2 (en) | 2003-12-08 | 2010-06-01 | Ipventure, Inc. | Systems and processes to manage multiple modes of communication |
| US8005462B2 (en) * | 2004-02-17 | 2011-08-23 | Teamon Systems, Inc. | System and method of retrieving electronic mail |
| US7260383B1 (en) * | 2004-02-20 | 2007-08-21 | Sprint Spectrum L.P. | Method and system for wireline response to wireless message notification |
| US8739071B2 (en) * | 2004-02-27 | 2014-05-27 | Blackberry Limited | System and method for message display and management |
| US7512400B2 (en) * | 2004-04-30 | 2009-03-31 | Microsoft Corporation | Integrated messaging user interface with message-based logging |
| US20050245244A1 (en) * | 2004-05-03 | 2005-11-03 | Texas Instruments Incorporated | System and method for placing an inbound wireless call in context and wireless communication device incorporating the same |
| ES2585353T3 (en) | 2004-05-12 | 2016-10-05 | Synchronoss Technologies, Inc. | Advanced contact identification system |
| US9542076B1 (en) | 2004-05-12 | 2017-01-10 | Synchronoss Technologies, Inc. | System for and method of updating a personal profile |
| US20060020904A1 (en) | 2004-07-09 | 2006-01-26 | Antti Aaltonen | Stripe user interface |
| KR100651369B1 (en) * | 2004-07-27 | 2006-11-29 | 삼성전자주식회사 | Apparatus and method for management schedule information in mobile phone |
| US7630724B2 (en) * | 2004-09-21 | 2009-12-08 | Advanced Ground Information Systems, Inc. | Method of providing a cellular phone/PDA communication system |
| US7218943B2 (en) * | 2004-12-13 | 2007-05-15 | Research In Motion Limited | Text messaging conversation user interface functionality |
| US7535340B2 (en) * | 2004-12-20 | 2009-05-19 | Samsung Electronics Co., Ltd. | Apparatus and method for processing an application program-related event in a wireless terminal |
| KR100663277B1 (en) * | 2004-12-20 | 2007-01-02 | 삼성전자주식회사 | Device and?method for processing system-related event in wireless terminal |
| US7555308B2 (en) * | 2004-12-20 | 2009-06-30 | Samsung Electronics Co., Ltd. | Device and method for processing call-related events in mobile terminal |
| KR100750999B1 (en) * | 2004-12-20 | 2007-08-22 | 삼성전자주식회사 | Device and method for processing call/message-related event in wireless terminal |
| US20060156251A1 (en) * | 2004-12-20 | 2006-07-13 | Atiya Suhail | System and method for providing feature customization for a communications device based on an active communications session |
| EP1686524A1 (en) * | 2005-01-05 | 2006-08-02 | Alcatel Alsthom Compagnie Generale D'electricite | A method for network-assisted communication, a telecommunication service, a server, a terminal device, and a computer software product therefor |
| JP2006209462A (en) * | 2005-01-28 | 2006-08-10 | Kyocera Corp | Terminal device |
| US7860492B2 (en) * | 2005-01-31 | 2010-12-28 | Nokia Corporation | Method and device for inhibiting interruption of a running application by an event |
| KR100663491B1 (en) * | 2005-03-04 | 2007-01-02 | 삼성전자주식회사 | Device and method for processing multimedia broadcasting-related event in wireless terminal |
| US20060224985A1 (en) * | 2005-04-01 | 2006-10-05 | Samsung Electronics Co., Ltd. | Method of displaying an event in a mobile terminal and mobile terminal implementing the same |
| US20060224944A1 (en) | 2005-04-01 | 2006-10-05 | Samsung Electronics Co., Ltd. | Method of displaying an event in a mobile terminal and mobile terminal implementing the same |
| KR100640420B1 (en) * | 2005-04-06 | 2006-10-30 | 삼성전자주식회사 | Method and device for call infomation displaying of mobile |
| US20060245560A1 (en) * | 2005-04-29 | 2006-11-02 | Yau-Ren Jeng | Programable caller ID alerting indicator for handheld device |
| US20070053335A1 (en) * | 2005-05-19 | 2007-03-08 | Richard Onyon | Mobile device address book builder |
| DE102005023963B4 (en) * | 2005-05-20 | 2014-09-11 | Vodafone Holding Gmbh | Operation of a usable terminal in a telecommunication network |
| EP1725000A1 (en) * | 2005-05-20 | 2006-11-22 | Research In Motion Limited | Wireless handheld device and method for the creation and display of a contact list |
| US8751279B2 (en) | 2005-05-23 | 2014-06-10 | Blackberry Limited | System and method for preventing the lapse of a recurring event using electronic calendar system |
| EP1727082A1 (en) | 2005-05-23 | 2006-11-29 | Research In Motion Limited | System and method for preventing the lapse of a recurring event using electronic calendar system |
| WO2006133547A1 (en) * | 2005-06-13 | 2006-12-21 | E-Lane Systems Inc. | Vehicle immersive communication system |
| DE602005020123D1 (en) * | 2005-06-29 | 2010-05-06 | Sony Ericsson Mobile Comm Ab | Electronic device and corresponding method for providing a reminder message in a cordless communication system |
| US7610345B2 (en) | 2005-07-28 | 2009-10-27 | Vaporstream Incorporated | Reduced traceability electronic message system and method |
| US9282081B2 (en) | 2005-07-28 | 2016-03-08 | Vaporstream Incorporated | Reduced traceability electronic message system and method |
| US7680256B2 (en) * | 2005-08-18 | 2010-03-16 | One Number Corporation | Contact number encapsulation system |
| US8677377B2 (en) | 2005-09-08 | 2014-03-18 | Apple Inc. | Method and apparatus for building an intelligent automated assistant |
| US7894580B2 (en) * | 2005-10-26 | 2011-02-22 | Research In Motion Limited | Methods and apparatus for reliable voicemail message deletion alerts at mobile communication devices |
| US20090100010A1 (en) * | 2005-10-26 | 2009-04-16 | Zimbra, Inc. | System and method for seamlessly integrating separate information systems within an application |
| US20070115926A1 (en) * | 2005-10-27 | 2007-05-24 | 3Com Corporation | System and method for receiving a user message at a packet-network telephone |
| US20070099638A1 (en) * | 2005-10-28 | 2007-05-03 | Voltz Christopher D | Multi-number wireless communications system and method |
| US7697503B2 (en) * | 2005-12-16 | 2010-04-13 | Qwest Communications International Inc. | Dynamic speed-dial list |
| KR100663477B1 (en) | 2005-12-23 | 2007-01-02 | 삼성전자주식회사 | Apparatus and method for providing receiving/sending information |
| KR101142962B1 (en) * | 2006-01-25 | 2012-05-08 | 엘지전자 주식회사 | method for processing mobile phone call and mobile phone therefor |
| US8543161B2 (en) * | 2006-03-30 | 2013-09-24 | Sony Corporation | Method and apparatus for managing mobile terminal events |
| US20070276915A1 (en) * | 2006-04-04 | 2007-11-29 | Wireless Services Corp. | Managing messages between multiple wireless carriers to multiple enterprises using a relatively limited number of identifiers |
| US20070233795A1 (en) * | 2006-04-04 | 2007-10-04 | Wireless Services Corp. | Managing messages between multiple wireless carriers using a relatively limited number of identifiers |
| WO2007134302A2 (en) * | 2006-05-14 | 2007-11-22 | Palm Inc. | System, method and technique for enabling users to interact and edit address fields of messaging applications |
| US7779370B2 (en) * | 2006-06-30 | 2010-08-17 | Google Inc. | User interface for mobile devices |
| KR100783551B1 (en) * | 2006-07-06 | 2007-12-07 | 삼성전자주식회사 | Method of using history menu for mobile device |
| US9976865B2 (en) * | 2006-07-28 | 2018-05-22 | Ridetones, Inc. | Vehicle communication system with navigation |
| GB0615844D0 (en) * | 2006-08-09 | 2006-09-20 | Intuwave Ltd | Mobile telephone programmed with phone call logging capability |
| US8564544B2 (en) | 2006-09-06 | 2013-10-22 | Apple Inc. | Touch screen device, method, and graphical user interface for customizing display of content category icons |
| US9304675B2 (en) | 2006-09-06 | 2016-04-05 | Apple Inc. | Portable electronic device for instant messaging |
| US8233885B2 (en) * | 2006-09-08 | 2012-07-31 | Hewlett-Packard Development Company, L.P. | Apparatus and methods for providing enhanced mobile messaging services |
| US9318108B2 (en) | 2010-01-18 | 2016-04-19 | Apple Inc. | Intelligent automated assistant |
| US20080077704A1 (en) * | 2006-09-24 | 2008-03-27 | Void Communications, Inc. | Variable Electronic Communication Ping Time System and Method |
| US20100015968A1 (en) * | 2006-12-13 | 2010-01-21 | Sharp Kabushiki Kaisha | Mobile communication control system, method, and communication terminal |
| US20080244442A1 (en) * | 2007-03-30 | 2008-10-02 | Microsoft Corporation | Techniques to share information between application programs |
| US8977255B2 (en) | 2007-04-03 | 2015-03-10 | Apple Inc. | Method and system for operating a multi-function portable electronic device using voice-activation |
| US8064888B2 (en) | 2007-04-12 | 2011-11-22 | Apple Inc. | Communications system that provides user-selectable data when user is on-hold |
| US8320889B2 (en) * | 2007-04-12 | 2012-11-27 | Apple Inc. | Method for automatic presentation of information before connection |
| US20080313050A1 (en) * | 2007-06-05 | 2008-12-18 | Basir Otman A | Media exchange system |
| US9954996B2 (en) | 2007-06-28 | 2018-04-24 | Apple Inc. | Portable electronic device with conversation management for incoming instant messages |
| EP2023584A1 (en) | 2007-07-31 | 2009-02-11 | Research In Motion Limited | Electronic device and method of controlling the electronic device |
| US8233886B2 (en) | 2007-08-15 | 2012-07-31 | Sony Mobile Communications Ab | Accessing stored data objects using contact data corresponding to a remote communications party |
| CA2708073A1 (en) * | 2007-12-10 | 2009-06-18 | E-Lane Systems Inc. | Vehicle communication system with destination selection for navigation |
| EP2073517A1 (en) | 2007-12-21 | 2009-06-24 | Research In Motion Limited | Display of call context information such as appointments with or communication history related to the other party |
| US9106447B2 (en) * | 2008-01-03 | 2015-08-11 | Apple Inc. | Systems, methods and apparatus for providing unread message alerts |
| US9330720B2 (en) | 2008-01-03 | 2016-05-03 | Apple Inc. | Methods and apparatus for altering audio output signals |
| US8327272B2 (en) | 2008-01-06 | 2012-12-04 | Apple Inc. | Portable multifunction device, method, and graphical user interface for viewing and managing electronic calendars |
| US8407603B2 (en) | 2008-01-06 | 2013-03-26 | Apple Inc. | Portable electronic device for instant messaging multiple recipients |
| US8050666B2 (en) * | 2008-02-12 | 2011-11-01 | Sony Ericsson Mobile Communications Ab | Appointment application for use in electronic equipment |
| WO2009111884A1 (en) | 2008-03-12 | 2009-09-17 | E-Lane Systems Inc. | Speech understanding method and system |
| US7904459B2 (en) * | 2008-03-19 | 2011-03-08 | International Business Machines Corporation | Generating a recipient list for propagating contact information changes based on contact metrics involving a user and the recipients on the list |
| CA2719301C (en) * | 2008-03-25 | 2016-10-04 | E-Lane Systems Inc. | Multi-participant, mixed-initiative voice interaction system |
| US8996376B2 (en) | 2008-04-05 | 2015-03-31 | Apple Inc. | Intelligent text-to-speech conversion |
| US10496753B2 (en) | 2010-01-18 | 2019-12-03 | Apple Inc. | Automatically adapting user interfaces for hands-free interaction |
| CN101282361B (en) * | 2008-05-16 | 2010-12-08 | 腾讯科技（深圳）有限公司 | Operation interactive system and method for mobile communication terminal and electric mailbox |
| GB0811196D0 (en) * | 2008-06-18 | 2008-07-23 | Skype Ltd | Searching method and apparatus |
| CA2727951A1 (en) * | 2008-06-19 | 2009-12-23 | E-Lane Systems Inc. | Communication system with voice mail access and call by spelling functionality |
| US8250147B2 (en) * | 2008-06-25 | 2012-08-21 | Microsoft Corporation | Remote call control and conferencing using paired devices |
| US9652023B2 (en) * | 2008-07-24 | 2017-05-16 | Intelligent Mechatronic Systems Inc. | Power management system |
| US20100030549A1 (en) | 2008-07-31 | 2010-02-04 | Lee Michael M | Mobile device having human language translation capability with positional feedback |
| WO2010067118A1 (en) | 2008-12-11 | 2010-06-17 | Novauris Technologies Limited | Speech recognition involving a mobile device |
| CN101783827A (en) * | 2009-01-15 | 2010-07-21 | 深圳富泰宏精密工业有限公司 | Contact data management system and method for communication device |
| KR101596955B1 (en) * | 2009-02-20 | 2016-02-23 | 삼성전자주식회사 | Method for session transfer in a converged ip messaging system |
| TWI456971B (en) * | 2009-03-06 | 2014-10-11 | Chi Mei Comm Systems Inc | System and method for managing communication information of people in a communication device |
| US20120072534A1 (en) * | 2009-04-10 | 2012-03-22 | Research In Motion Limited | Method and System for the Exposure of Simplified Data-Service Facades Through a Context Aware Access Layer |
| JP5132629B2 (en) * | 2009-05-11 | 2013-01-30 | ソニーモバイルコミュニケーションズ， エービー | Information terminal, information presentation method of information terminal, and information presentation program |
| WO2010135837A1 (en) | 2009-05-28 | 2010-12-02 | Intelligent Mechatronic Systems Inc | Communication system with personal information management and remote vehicle monitoring and control features |
| US9858925B2 (en) | 2009-06-05 | 2018-01-02 | Apple Inc. | Using context information to facilitate processing of commands in a virtual assistant |
| US10241752B2 (en) | 2011-09-30 | 2019-03-26 | Apple Inc. | Interface for a virtual digital assistant |
| US20120311585A1 (en) | 2011-06-03 | 2012-12-06 | Apple Inc. | Organizing task items that represent tasks to perform |
| US10241644B2 (en) | 2011-06-03 | 2019-03-26 | Apple Inc. | Actionable reminder entries |
| US9667726B2 (en) | 2009-06-27 | 2017-05-30 | Ridetones, Inc. | Vehicle internet radio interface |
| US9431006B2 (en) | 2009-07-02 | 2016-08-30 | Apple Inc. | Methods and apparatuses for automatic speech recognition |
| US8768308B2 (en) * | 2009-09-29 | 2014-07-01 | Deutsche Telekom Ag | Apparatus and method for creating and managing personal schedules via context-sensing and actuation |
| US8255006B1 (en) | 2009-11-10 | 2012-08-28 | Fusionone, Inc. | Event dependent notification system and method |
| US9978272B2 (en) | 2009-11-25 | 2018-05-22 | Ridetones, Inc | Vehicle to vehicle chatting and communication system |
| FR2953053B1 (en) * | 2009-11-26 | 2012-07-13 | Alcatel Lucent | METHOD FOR SELECTING A COMMUNICATION MODE |
| CN102104667B (en) * | 2009-12-17 | 2013-10-09 | 深圳富泰宏精密工业有限公司 | Mobile phone and on-hook method thereof |
| US10679605B2 (en) | 2010-01-18 | 2020-06-09 | Apple Inc. | Hands-free list-reading by intelligent automated assistant |
| US10705794B2 (en) | 2010-01-18 | 2020-07-07 | Apple Inc. | Automatically adapting user interfaces for hands-free interaction |
| US10276170B2 (en) | 2010-01-18 | 2019-04-30 | Apple Inc. | Intelligent automated assistant |
| US10553209B2 (en) | 2010-01-18 | 2020-02-04 | Apple Inc. | Systems and methods for hands-free notification summaries |
| WO2011089450A2 (en) | 2010-01-25 | 2011-07-28 | Andrew Peter Nelson Jerram | Apparatuses, methods and systems for a digital conversation management platform |
| US8320896B1 (en) * | 2010-02-03 | 2012-11-27 | Sprint Communications Company L.P. | Unified communication access system |
| US8682667B2 (en) | 2010-02-25 | 2014-03-25 | Apple Inc. | User profiling for selecting user specific voice input processing information |
| US9501802B2 (en) * | 2010-05-04 | 2016-11-22 | Qwest Communications International Inc. | Conversation capture |
| US9559869B2 (en) | 2010-05-04 | 2017-01-31 | Qwest Communications International Inc. | Video call handling |
| US8472922B2 (en) * | 2010-05-24 | 2013-06-25 | International Business Machines Corporation | Enhanced communications log for a mobile communications device |
| CN101958955A (en) * | 2010-05-28 | 2011-01-26 | 宇龙计算机通信科技(深圳)有限公司 | Method and system for displaying phone number information and mobile terminal |
| CN102137179B (en) * | 2010-08-05 | 2015-07-08 | 华为终端有限公司 | Method and terminal for arranging address book information |
| CA2807956C (en) | 2010-08-09 | 2019-02-12 | Intelligent Mechatronic Systems Inc. | Interface for mobile device and computing device |
| US8380172B1 (en) * | 2010-09-01 | 2013-02-19 | Sprint Communications Company L.P. | Enhanced search user interface |
| US20120079008A1 (en) * | 2010-09-27 | 2012-03-29 | Research In Motion Limited | Method, apparatus and system for providing event notifications across a plurality of computers |
| US20120079063A1 (en) * | 2010-09-27 | 2012-03-29 | Research In Motion Limited | Method, apparatus and system for providing event notifications across a plurality of computers |
| US8943428B2 (en) | 2010-11-01 | 2015-01-27 | Synchronoss Technologies, Inc. | System for and method of field mapping |
| US10762293B2 (en) | 2010-12-22 | 2020-09-01 | Apple Inc. | Using parts-of-speech tagging and named entity recognition for spelling correction |
| DE102010055858A1 (en) * | 2010-12-22 | 2012-06-28 | Audi Ag | Output from a first receiving device and messages received from a second receiving device |
| WO2012097168A2 (en) * | 2011-01-12 | 2012-07-19 | Seven Networks, Inc. | Unified access and management of events across multiple applications and associated contacts thereof |
| CN102123383A (en) * | 2011-01-27 | 2011-07-13 | 北京播思软件技术有限公司 | Method and system for automatically acquiring personal information of unknown incoming call |
| EP2487881A1 (en) * | 2011-02-02 | 2012-08-15 | Research In Motion Limited | Communication device and method for displaying message information when receiving a call |
| US20120196575A1 (en) * | 2011-02-02 | 2012-08-02 | James Allen Hymel | Communication device and method for displaying message information when receiving a call |
| US9262612B2 (en) | 2011-03-21 | 2016-02-16 | Apple Inc. | Device access using voice authentication |
| US9225582B1 (en) * | 2011-03-31 | 2015-12-29 | Google Inc. | Managing and enabling interaction with communication information |
| US10057736B2 (en) | 2011-06-03 | 2018-08-21 | Apple Inc. | Active transport based notifications |
| US20150135284A1 (en) * | 2011-06-10 | 2015-05-14 | Aliphcom | Automatic electronic device adoption with a wearable device or a data-capable watch band |
| CN102624973B (en) * | 2011-06-14 | 2014-10-22 | 小米科技有限责任公司 | Method for client to display communication information |
| WO2011150881A2 (en) | 2011-06-22 | 2011-12-08 | 华为终端有限公司 | Contact card management method and device used for mobile terminal |
| US8994660B2 (en) | 2011-08-29 | 2015-03-31 | Apple Inc. | Text correction processing |
| EP2795440A4 (en) * | 2011-12-21 | 2015-08-19 | Nokia Technologies Oy | Apparatus and method for collating application events with contacts of an electronic device. |
| US9300621B2 (en) * | 2012-02-05 | 2016-03-29 | Apple Inc. | Communication history aggregation and presentation |
| US10134385B2 (en) | 2012-03-02 | 2018-11-20 | Apple Inc. | Systems and methods for name pronunciation |
| US9483461B2 (en) | 2012-03-06 | 2016-11-01 | Apple Inc. | Handling speech synthesis of content for multiple languages |
| US9602170B2 (en) * | 2012-03-27 | 2017-03-21 | Panasonic Intellectual Property Management Co., Ltd. | Electrical instrument |
| CN103369506A (en) * | 2012-03-29 | 2013-10-23 | 宇龙计算机通信科技(深圳)有限公司 | Card selection prompting method of multi-card terminal and multi-card mobile terminal |
| CN102811283A (en) * | 2012-04-18 | 2012-12-05 | 中兴通讯股份有限公司 | Terminal communication display method and terminal thereof |
| US9280610B2 (en) | 2012-05-14 | 2016-03-08 | Apple Inc. | Crowd sourcing information to fulfill user requests |
| US9721563B2 (en) | 2012-06-08 | 2017-08-01 | Apple Inc. | Name recognition system |
| US8855281B2 (en) | 2012-06-08 | 2014-10-07 | International Business Machines Corporation | Systems for retrieving content in a unified communications environment |
| CN102769696B (en) * | 2012-06-26 | 2014-11-05 | 北京奇虎科技有限公司 | System and method for displaying harassing calls |
| US9495129B2 (en) | 2012-06-29 | 2016-11-15 | Apple Inc. | Device, method, and user interface for voice-activated navigation and browsing of a document |
| US9361433B2 (en) | 2012-08-03 | 2016-06-07 | Synchronoss Technologies, Inc | Enterprise leasing license algorithm |
| US9576574B2 (en) | 2012-09-10 | 2017-02-21 | Apple Inc. | Context-sensitive handling of interruptions by intelligent digital assistant |
| US9547647B2 (en) | 2012-09-19 | 2017-01-17 | Apple Inc. | Voice-based media searching |
| KR102017845B1 (en) * | 2012-09-20 | 2019-09-03 | 삼성전자주식회사 | Method and apparatus for displaying missed calls on mobile terminal |
| CN103929519A (en) * | 2013-01-16 | 2014-07-16 | 三星电子（中国）研发中心 | Method for displaying contact information in call waiting process and mobile device |
| KR102516577B1 (en) | 2013-02-07 | 2023-04-03 | 애플 인크. | Voice trigger for a digital assistant |
| US9368114B2 (en) | 2013-03-14 | 2016-06-14 | Apple Inc. | Context-sensitive handling of interruptions |
| WO2014144579A1 (en) | 2013-03-15 | 2014-09-18 | Apple Inc. | System and method for updating an adaptive speech recognition model |
| US9871917B2 (en) * | 2013-03-15 | 2018-01-16 | Qula Inc. | System and methods to enable efficient and interactive management of communications |
| WO2014144949A2 (en) | 2013-03-15 | 2014-09-18 | Apple Inc. | Training an at least partial voice command system |
| US8983509B2 (en) * | 2013-03-22 | 2015-03-17 | Argela Yazilim ve Bilisim Teknolojileri San. ve Tic. A.S. | Internet-based short message retrieval and display system |
| US9582608B2 (en) | 2013-06-07 | 2017-02-28 | Apple Inc. | Unified ranking with entropy-weighted information for phrase-based semantic auto-completion |
| WO2014197334A2 (en) | 2013-06-07 | 2014-12-11 | Apple Inc. | System and method for user-specified pronunciation of words for speech synthesis and recognition |
| WO2014197336A1 (en) | 2013-06-07 | 2014-12-11 | Apple Inc. | System and method for detecting errors in interactions with a voice-based digital assistant |
| WO2014197335A1 (en) | 2013-06-08 | 2014-12-11 | Apple Inc. | Interpreting and acting upon commands that involve sharing information with remote devices |
| EP3008641A1 (en) | 2013-06-09 | 2016-04-20 | Apple Inc. | Device, method, and graphical user interface for enabling conversation persistence across two or more instances of a digital assistant |
| US10176167B2 (en) | 2013-06-09 | 2019-01-08 | Apple Inc. | System and method for inferring user intent from speech inputs |
| CN105265005B (en) | 2013-06-13 | 2019-09-17 | 苹果公司 | System and method for the urgent call initiated by voice command |
| KR20150007862A (en) * | 2013-07-12 | 2015-01-21 | 삼성전자주식회사 | Mobile terminal and method for controlling data providing |
| WO2015020942A1 (en) | 2013-08-06 | 2015-02-12 | Apple Inc. | Auto-activating smart responses based on activities from remote devices |
| US9866446B2 (en) * | 2013-08-26 | 2018-01-09 | Akarsh Belagodu | Data retrieval system |
| US20150119090A1 (en) * | 2013-10-24 | 2015-04-30 | Acer Incorporated | Method of handling rejections of sms messages and related communication system |
| US20150128058A1 (en) * | 2013-11-05 | 2015-05-07 | Avaya Inc. | System and method for predictive actions based on user communication patterns |
| CN103747132B (en) * | 2013-12-11 | 2016-05-04 | 宇龙计算机通信科技(深圳)有限公司 | The method of display message and terminal |
| US9215315B2 (en) * | 2014-01-07 | 2015-12-15 | Google Inc. | Systems and methods for contextual caller identification |
| US9485635B2 (en) * | 2014-03-14 | 2016-11-01 | Lenovo (Singapore) Pte. Ltd. | Displaying information associated with correspondence |
| GB201408302D0 (en) * | 2014-05-12 | 2014-06-25 | Jpy Plc | Unifying text and audio |
| US9620105B2 (en) | 2014-05-15 | 2017-04-11 | Apple Inc. | Analyzing audio input for efficient speech and music recognition |
| US10592095B2 (en) | 2014-05-23 | 2020-03-17 | Apple Inc. | Instantaneous speaking of content on touch devices |
| US9502031B2 (en) | 2014-05-27 | 2016-11-22 | Apple Inc. | Method for supporting dynamic grammars in WFST-based ASR |
| CN104009910A (en) * | 2014-05-28 | 2014-08-27 | 惠州Tcl移动通信有限公司 | Message pushing processing method and system based on mobile terminal and mobile terminal |
| US10170123B2 (en) | 2014-05-30 | 2019-01-01 | Apple Inc. | Intelligent assistant for home automation |
| US9633004B2 (en) | 2014-05-30 | 2017-04-25 | Apple Inc. | Better resolution when referencing to concepts |
| US10078631B2 (en) | 2014-05-30 | 2018-09-18 | Apple Inc. | Entropy-guided text prediction using combined word and character n-gram language models |
| US9734193B2 (en) | 2014-05-30 | 2017-08-15 | Apple Inc. | Determining domain salience ranking from ambiguous words in natural speech |
| US10289433B2 (en) | 2014-05-30 | 2019-05-14 | Apple Inc. | Domain specific language for encoding assistant dialog |
| US9430463B2 (en) | 2014-05-30 | 2016-08-30 | Apple Inc. | Exemplar-based natural language processing |
| US9842101B2 (en) | 2014-05-30 | 2017-12-12 | Apple Inc. | Predictive conversion of language input |
| US9785630B2 (en) | 2014-05-30 | 2017-10-10 | Apple Inc. | Text prediction using combined word N-gram and unigram language models |
| US9760559B2 (en) | 2014-05-30 | 2017-09-12 | Apple Inc. | Predictive text input |
| US9715875B2 (en) | 2014-05-30 | 2017-07-25 | Apple Inc. | Reducing the need for manual start/end-pointing and trigger phrases |
| EP3149728B1 (en) | 2014-05-30 | 2019-01-16 | Apple Inc. | Multi-command single utterance input method |
| US9185062B1 (en) | 2014-05-31 | 2015-11-10 | Apple Inc. | Message user interfaces for capture and transmittal of media and location content |
| US10659851B2 (en) | 2014-06-30 | 2020-05-19 | Apple Inc. | Real-time digital assistant knowledge updates |
| US9338493B2 (en) | 2014-06-30 | 2016-05-10 | Apple Inc. | Intelligent automated assistant for TV user interactions |
| US11157148B2 (en) | 2014-07-24 | 2021-10-26 | Blackberry Limited | System, method and device-readable medium for message composition within a unified event view |
| US10528234B2 (en) | 2014-07-24 | 2020-01-07 | Blackberry Limited | System, method and device-readable medium for last-viewed communication event interaction within a unified event view |
| US9800711B2 (en) | 2014-07-24 | 2017-10-24 | Blackberry Limited | System, method and device-readable medium for communication event interaction within a unified event view |
| US10446141B2 (en) | 2014-08-28 | 2019-10-15 | Apple Inc. | Automatic speech recognition based on user feedback |
| US9818400B2 (en) | 2014-09-11 | 2017-11-14 | Apple Inc. | Method and apparatus for discovering trending terms in speech requests |
| US9606986B2 (en) | 2014-09-29 | 2017-03-28 | Apple Inc. | Integrated word N-gram and class M-gram language models |
| US9668121B2 (en) | 2014-09-30 | 2017-05-30 | Apple Inc. | Social reminders |
| US9646609B2 (en) | 2014-09-30 | 2017-05-09 | Apple Inc. | Caching apparatus for serving phonetic pronunciations |
| US10127911B2 (en) | 2014-09-30 | 2018-11-13 | Apple Inc. | Speaker identification and unsupervised speaker adaptation techniques |
| US10074360B2 (en) | 2014-09-30 | 2018-09-11 | Apple Inc. | Providing an indication of the suitability of speech recognition |
| US9886432B2 (en) | 2014-09-30 | 2018-02-06 | Apple Inc. | Parsimonious handling of word inflection via categorical stem + suffix N-gram language models |
| US10552013B2 (en) | 2014-12-02 | 2020-02-04 | Apple Inc. | Data detection |
| US9711141B2 (en) | 2014-12-09 | 2017-07-18 | Apple Inc. | Disambiguating heteronyms in speech synthesis |
| US9865280B2 (en) | 2015-03-06 | 2018-01-09 | Apple Inc. | Structured dictation using intelligent automated assistants |
| US9886953B2 (en) | 2015-03-08 | 2018-02-06 | Apple Inc. | Virtual assistant activation |
| US9721566B2 (en) | 2015-03-08 | 2017-08-01 | Apple Inc. | Competing devices responding to voice triggers |
| US10567477B2 (en) | 2015-03-08 | 2020-02-18 | Apple Inc. | Virtual assistant continuity |
| US9899019B2 (en) | 2015-03-18 | 2018-02-20 | Apple Inc. | Systems and methods for structured stem and suffix language models |
| US9842105B2 (en) | 2015-04-16 | 2017-12-12 | Apple Inc. | Parsimonious continuous-space phrase representations for natural language processing |
| US10083688B2 (en) | 2015-05-27 | 2018-09-25 | Apple Inc. | Device voice control for selecting a displayed affordance |
| US10127220B2 (en) | 2015-06-04 | 2018-11-13 | Apple Inc. | Language identification from short strings |
| US9578173B2 (en) | 2015-06-05 | 2017-02-21 | Apple Inc. | Virtual assistant aided communication with 3rd party service in a communication session |
| US10101822B2 (en) | 2015-06-05 | 2018-10-16 | Apple Inc. | Language input correction |
| US11025565B2 (en) | 2015-06-07 | 2021-06-01 | Apple Inc. | Personalized prediction of responses for instant messaging |
| US10255907B2 (en) | 2015-06-07 | 2019-04-09 | Apple Inc. | Automatic accent detection using acoustic models |
| US10186254B2 (en) | 2015-06-07 | 2019-01-22 | Apple Inc. | Context-based endpoint detection |
| US10671428B2 (en) | 2015-09-08 | 2020-06-02 | Apple Inc. | Distributed personal assistant |
| US10747498B2 (en) | 2015-09-08 | 2020-08-18 | Apple Inc. | Zero latency digital assistant |
| US9697820B2 (en) | 2015-09-24 | 2017-07-04 | Apple Inc. | Unit-selection text-to-speech synthesis using concatenation-sensitive neural networks |
| US10366158B2 (en) | 2015-09-29 | 2019-07-30 | Apple Inc. | Efficient word encoding for recurrent neural network language models |
| US11010550B2 (en) | 2015-09-29 | 2021-05-18 | Apple Inc. | Unified language modeling framework for word prediction, auto-completion and auto-correction |
| US11587559B2 (en) | 2015-09-30 | 2023-02-21 | Apple Inc. | Intelligent device identification |
| US10691473B2 (en) | 2015-11-06 | 2020-06-23 | Apple Inc. | Intelligent automated assistant in a messaging environment |
| US10049668B2 (en) | 2015-12-02 | 2018-08-14 | Apple Inc. | Applying neural network language models to weighted finite state transducers for automatic speech recognition |
| US10223066B2 (en) | 2015-12-23 | 2019-03-05 | Apple Inc. | Proactive assistance based on dialog communication between devices |
| US10446143B2 (en) | 2016-03-14 | 2019-10-15 | Apple Inc. | Identification of voice inputs providing credentials |
| US9934775B2 (en) | 2016-05-26 | 2018-04-03 | Apple Inc. | Unit-selection text-to-speech synthesis based on predicted concatenation parameters |
| US9972304B2 (en) | 2016-06-03 | 2018-05-15 | Apple Inc. | Privacy preserving distributed evaluation framework for embedded personalized systems |
| US10249300B2 (en) | 2016-06-06 | 2019-04-02 | Apple Inc. | Intelligent list reading |
| US10049663B2 (en) | 2016-06-08 | 2018-08-14 | Apple, Inc. | Intelligent automated assistant for media exploration |
| DK179309B1 (en) | 2016-06-09 | 2018-04-23 | Apple Inc | Intelligent automated assistant in a home environment |
| US10067938B2 (en) | 2016-06-10 | 2018-09-04 | Apple Inc. | Multilingual word prediction |
| US10490187B2 (en) | 2016-06-10 | 2019-11-26 | Apple Inc. | Digital assistant providing automated status report |
| US10192552B2 (en) | 2016-06-10 | 2019-01-29 | Apple Inc. | Digital assistant providing whispered speech |
| US10586535B2 (en) | 2016-06-10 | 2020-03-10 | Apple Inc. | Intelligent digital assistant in a multi-tasking environment |
| US10509862B2 (en) | 2016-06-10 | 2019-12-17 | Apple Inc. | Dynamic phrase expansion of language input |
| DK179415B1 (en) | 2016-06-11 | 2018-06-14 | Apple Inc | Intelligent device arbitration and control |
| DK179049B1 (en) | 2016-06-11 | 2017-09-18 | Apple Inc | Data driven natural language event detection and classification |
| DK179343B1 (en) | 2016-06-11 | 2018-05-14 | Apple Inc | Intelligent task discovery |
| DK201670540A1 (en) | 2016-06-11 | 2018-01-08 | Apple Inc | Application integration with a digital assistant |
| EP3264733B1 (en) | 2016-06-29 | 2019-08-07 | Unify Patente GmbH & Co. KG | Method of providing a recent event list, software product, telecommunications device and system |
| JP6720755B2 (en) * | 2016-07-29 | 2020-07-08 | 富士ゼロックス株式会社 | Information processing apparatus and information processing program |
| US10043516B2 (en) | 2016-09-23 | 2018-08-07 | Apple Inc. | Intelligent automated assistant |
| US10593346B2 (en) | 2016-12-22 | 2020-03-17 | Apple Inc. | Rank-reduced token representation for automatic speech recognition |
| DK201770439A1 (en) | 2017-05-11 | 2018-12-13 | Apple Inc. | Offline personal assistant |
| DK179745B1 (en) | 2017-05-12 | 2019-05-01 | Apple Inc. | SYNCHRONIZATION AND TASK DELEGATION OF A DIGITAL ASSISTANT |
| DK179496B1 (en) | 2017-05-12 | 2019-01-15 | Apple Inc. | USER-SPECIFIC Acoustic Models |
| DK201770431A1 (en) | 2017-05-15 | 2018-12-20 | Apple Inc. | Optimizing dialogue policy decisions for digital assistants using implicit feedback |
| DK201770432A1 (en) | 2017-05-15 | 2018-12-21 | Apple Inc. | Hierarchical belief states for digital assistants |
| DK179560B1 (en) | 2017-05-16 | 2019-02-18 | Apple Inc. | Far-field extension for digital assistant services |
| US20200402006A1 (en) * | 2018-02-22 | 2020-12-24 | Gil MARGALIT | System and method for managing communications over an organizational data communication network |
| US11513667B2 (en) | 2020-05-11 | 2022-11-29 | Apple Inc. | User interface for audio message |
| CN112367423A (en) * | 2020-10-23 | 2021-02-12 | 珠海格力电器股份有限公司 | Method and device for managing notification information, storage medium, and electronic device |
Family Cites Families (88)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0474555B1 (en) * | 1990-09-05 | 1997-12-29 | Canon Kabushiki Kaisha | Multi-media communication apparatus and method |
| US5394140A (en) * | 1992-11-23 | 1995-02-28 | Motorola, Inc. | Method and apparatus for pre-programmed call-back-number-determined alert |
| US5394445A (en) * | 1993-06-25 | 1995-02-28 | Ball; Randel H. | Telephone call screening and answering device |
| JPH0795279A (en) * | 1993-09-20 | 1995-04-07 | Fujitsu Ltd | Memory dialing control system |
| US5634196A (en) * | 1994-10-19 | 1997-05-27 | Uniden America Corporation | Radio call history list |
| US5579472A (en) | 1994-11-09 | 1996-11-26 | Novalink Technologies, Inc. | Group-oriented communications user interface |
| US5862336A (en) | 1995-06-01 | 1999-01-19 | Fuji Xerox Co., Ltd. | Tracing system for analyzing an information distribution route by automatically gathering distribution histories from systems which the information is routed through |
| GB2301987B (en) * | 1995-06-05 | 2000-01-12 | Nokia Mobile Phones Ltd | Radio telephone text transmission system |
| JPH09134319A (en) * | 1995-10-03 | 1997-05-20 | Sony Electron Inc | User interface for personal communication routing system and rule processing |
| WO1997017682A1 (en) * | 1995-11-06 | 1997-05-15 | Motorola Inc. | Message storage in a selective call receiver |
| US5781857A (en) | 1996-06-28 | 1998-07-14 | Motorola, Inc. | Method of establishing an email monitor responsive to a wireless communications system user |
| JP3687811B2 (en) * | 1996-10-21 | 2005-08-24 | ソニー株式会社 | Communication terminal device and call history display method |
| EP0935425A4 (en) | 1996-10-25 | 2000-02-23 | Mccormick & Co Inc | Fat-coated encapsulation compositions and method for preparing the same |
| US5923327A (en) * | 1997-04-23 | 1999-07-13 | Bell-Northern Research Ltd. | Scrolling with automatic compression and expansion |
| US6178338B1 (en) * | 1997-04-28 | 2001-01-23 | Sony Corporation | Communication terminal apparatus and method for selecting options using a dial shuttle |
| JPH1141369A (en) * | 1997-07-18 | 1999-02-12 | Matsushita Electric Ind Co Ltd | Portable information terminal equipment |
| EP0920168A3 (en) | 1997-11-27 | 2003-05-21 | Samsung Electronics Co., Ltd. | Speed dialing method and telephone apparatus |
| CN1224294A (en) | 1997-11-27 | 1999-07-28 | 三星电子株式会社 | Speed dialing in telephone |
| JPH11177675A (en) * | 1997-12-15 | 1999-07-02 | Sony Corp | Telephone terminal and caller number utilizing method |
| DE19801563B4 (en) * | 1998-01-19 | 2006-04-20 | Telefonaktiebolaget Lm Ericsson (Publ) | Communication system with support of mobile participants and automatic information and media implementation |
| US6157630A (en) * | 1998-01-26 | 2000-12-05 | Motorola, Inc. | Communications system with radio device and server |
| AU2776899A (en) * | 1998-02-20 | 1999-09-06 | Fujitsu Network Communications, Inc. | Short message device for wireless telephone |
| US6173316B1 (en) * | 1998-04-08 | 2001-01-09 | Geoworks Corporation | Wireless communication device with markup language based man-machine interface |
| WO1999053670A2 (en) * | 1998-04-10 | 1999-10-21 | Landel Technology, Inc. | A proprietary information system and various methods of use connected therewith |
| US6340658B1 (en) | 1998-05-11 | 2002-01-22 | Wavely Light And Power | Vegetable-based transformer oil and transmission line fluid |
| US6266539B1 (en) * | 1998-06-12 | 2001-07-24 | Cisco Technology, Inc. | Telephone docking station for personal digital assistant |
| JP2000022855A (en) | 1998-06-26 | 2000-01-21 | Nec Corp | Telephone terminal and method for managing originating and incoming call history |
| US7225409B1 (en) | 1998-08-26 | 2007-05-29 | Microsoft Corporation | Graphical user interface for a screen telephone |
| US6792082B1 (en) * | 1998-09-11 | 2004-09-14 | Comverse Ltd. | Voice mail system with personal assistant provisioning |
| US7672879B1 (en) | 1998-12-08 | 2010-03-02 | Yodlee.Com, Inc. | Interactive activity interface for managing personal data and performing transactions over a data packet network |
| US6778642B1 (en) | 1999-03-23 | 2004-08-17 | Verizon Laboratories Inc. | Unified messaging system |
| US6571275B1 (en) | 1999-04-27 | 2003-05-27 | International Business Machines Corporation | Method and apparatus for filtering messages in a data processing system |
| US6604239B1 (en) | 1999-06-25 | 2003-08-05 | Eyescene Inc. | System and method for virtual television program rating |
| US7007239B1 (en) * | 2000-09-21 | 2006-02-28 | Palm, Inc. | Method and apparatus for accessing a contacts database and telephone services |
| US6628194B1 (en) | 1999-08-31 | 2003-09-30 | At&T Wireless Services, Inc. | Filtered in-box for voice mail, e-mail, pages, web-based information, and faxes |
| JP2001111672A (en) * | 1999-10-05 | 2001-04-20 | Kenwood Corp | Mobile communication terminal |
| US6640239B1 (en) | 1999-11-10 | 2003-10-28 | Garuda Network Corporation | Apparatus and method for intelligent scalable switching network |
| CN1335964A (en) * | 1999-11-10 | 2002-02-13 | 三菱电机株式会社 | Information terminal, server, information display system, and information display method |
| US6459782B1 (en) * | 1999-11-10 | 2002-10-01 | Goldstar Information Technologies, Llc | System and method of developing mapping and directions from caller ID |
| US6487278B1 (en) | 2000-02-29 | 2002-11-26 | Ameritech Corporation | Method and system for interfacing systems unified messaging with legacy systems located behind corporate firewalls |
| JP4462711B2 (en) | 2000-04-18 | 2010-05-12 | 株式会社日立製作所 | Storage system |
| WO2001089171A2 (en) * | 2000-05-16 | 2001-11-22 | Mshift, Inc. | System for providing network content to wireless devices |
| JP3738383B2 (en) * | 2000-05-26 | 2006-01-25 | 富士通株式会社 | Communication device |
| CA2310185A1 (en) * | 2000-06-05 | 2001-12-05 | T. A. Currier | Method and apparatus for modifying persistent storage |
| US7028263B2 (en) * | 2000-07-19 | 2006-04-11 | Research In Motion Limited | User interface and method for viewing short messages on a wireless device |
| CA2416253A1 (en) * | 2000-07-28 | 2002-02-07 | American Calcar Inc. | Technique for effective organization and communication of information |
| JP2002057759A (en) * | 2000-08-09 | 2002-02-22 | Nec Saitama Ltd | Foldable portable telephone set |
| JP3530475B2 (en) * | 2000-09-25 | 2004-05-24 | 三洋電機株式会社 | Foldable communication terminal device and information display method |
| KR100491606B1 (en) * | 2000-09-29 | 2005-05-27 | 산요덴키가부시키가이샤 | Folder type communication terminal device and the display control method of the same |
| US7289614B1 (en) * | 2000-09-29 | 2007-10-30 | Palmsource, Inc. | Making a call from an address list or a call history list |
| US6661877B1 (en) | 2000-09-29 | 2003-12-09 | Oracle International Corporation | System and method for providing access to a unified message store logically storing computer telephony messages |
| US6871214B2 (en) | 2000-10-30 | 2005-03-22 | Nortel Networks Limited | Generating and providing alert messages in a communications network |
| EP1205843A3 (en) * | 2000-11-13 | 2004-10-20 | Canon Kabushiki Kaisha | User interfaces |
| US6772143B2 (en) * | 2001-01-02 | 2004-08-03 | Sprint Spectrum L.P. | Method and system for managing messages |
| US6868283B1 (en) | 2001-01-16 | 2005-03-15 | Palm Source, Inc. | Technique allowing a status bar user response on a portable device graphic user interface |
| CA2368404C (en) | 2001-01-18 | 2005-08-09 | Research In Motion Limited | Unified messaging system and method |
| JP2002218095A (en) * | 2001-01-23 | 2002-08-02 | Matsushita Electric Ind Co Ltd | Telephone terminal device |
| US6778834B2 (en) * | 2001-02-27 | 2004-08-17 | Nokia Corporation | Push content filtering |
| US20020126814A1 (en) * | 2001-03-08 | 2002-09-12 | International Business Machines Corporation | Apparatus, method and computer program product for automatic directory entry generation via caller-id |
| US7096009B2 (en) | 2001-03-09 | 2006-08-22 | Research In Motion Limited | Advanced voice and data operations in a mobile data communication device |
| CA2641610C (en) * | 2001-03-09 | 2010-09-14 | Research In Motion Limited | Advanced voice and data operations in a mobile data communication device |
| JP4739564B2 (en) * | 2001-03-30 | 2011-08-03 | 株式会社日立国際電気 | Mobile phone |
| US20020151334A1 (en) * | 2001-04-11 | 2002-10-17 | Motorola, Inc | Communications device with call frequency analyzer |
| DE60230201D1 (en) | 2001-06-18 | 2009-01-15 | Research In Motion Ltd | System and method for managing message installations |
| US7389118B2 (en) * | 2001-06-29 | 2008-06-17 | Nokia Corporation | System and method for person-to-person messaging with a value-added service |
| US20030013483A1 (en) | 2001-07-06 | 2003-01-16 | Ausems Michiel R. | User interface for handheld communication device |
| US20030023688A1 (en) | 2001-07-26 | 2003-01-30 | Denenberg Lawrence A. | Voice-based message sorting and retrieval method |
| US6720863B2 (en) * | 2001-08-16 | 2004-04-13 | Wildseed Ltd. | Mobile electronic communication device with lights to indicate received messages |
| CN1411311A (en) * | 2001-10-01 | 2003-04-16 | 株式会社东芝 | Mobile wireless terminal apparatus |
| US20030078981A1 (en) * | 2001-10-24 | 2003-04-24 | Infowave Software, Inc. | System for and method of populating a contact list on a portable device |
| US6961420B2 (en) * | 2001-11-13 | 2005-11-01 | Danger, Inc. | Apparatus and method for recording incoming call information |
| CA2414964C (en) | 2001-12-26 | 2018-07-17 | Research In Motion Limited | Security interface for a mobile device |
| DE60218899T2 (en) * | 2001-12-26 | 2007-12-06 | Research In Motion Ltd., Waterloo | USER INTERFACE AND METHOD FOR LOOKING AT UNIFORM COMMUNICATION EVENTS IN A MOBILE DEVICE |
| KR20030069107A (en) * | 2002-02-18 | 2003-08-25 | 캐논 가부시끼가이샤 | Communication apparatus, information display method, incoming call display method, incoming call history display method, programs for implementing the methods, and storage medium in which the program is stored |
| US7689196B2 (en) * | 2002-06-26 | 2010-03-30 | Qualcomm Incorporated | Timer-based sleep for terminals in wireless communication systems |
| US8577983B2 (en) | 2002-07-12 | 2013-11-05 | Pace Plc | System and method for notifying an instant message recipient of receipt of a message |
| US7035674B1 (en) * | 2002-08-02 | 2006-04-25 | Bellsouth Intellectual Property Corporation | Methods and systems for enabling address book selection and communication with a wireless device |
| US6965786B2 (en) * | 2002-08-13 | 2005-11-15 | Qualcomm Incorporated | Annunciators for voice and data applications in wireless communication devices |
| GB0219155D0 (en) * | 2002-08-16 | 2002-09-25 | Sleepydog Ltd | Improvements relating to telecommunications |
| JP4140340B2 (en) * | 2002-10-24 | 2008-08-27 | 日本電気株式会社 | Mobile communication system, mobile station, base station, and packet communication method used therefor |
| EP1527774A1 (en) | 2003-11-03 | 2005-05-04 | Basilea Pharmaceutica AG | New formulation for retinoid-containing soft gelatin capsules |
| GB2402578A (en) | 2003-06-04 | 2004-12-08 | Research In Motion Ltd | Selection of message transport in a communication device |
| US20050239445A1 (en) * | 2004-04-16 | 2005-10-27 | Jeyhan Karaoguz | Method and system for providing registration, authentication and access via broadband access gateway |
| WO2005115035A1 (en) | 2004-05-20 | 2005-12-01 | Research In Motion Limited | Handling an audio conference related to a text-based message |
| AU2005254036B2 (en) | 2004-06-10 | 2011-02-03 | Kellogg Company | Topical application of marine oils to foods |
| ATE474405T1 (en) | 2004-12-03 | 2010-07-15 | Research In Motion Ltd | METHOD AND DEVICE FOR EFFICIENTLY REPEATEDLY SENDING MESSAGES USING A MESSAGE ID |
| US7764969B2 (en) * | 2006-02-13 | 2010-07-27 | Qualcomm Incorporated | Reduced paging cycles in a wireless communication system |
| US20100274792A1 (en) * | 2007-01-02 | 2010-10-28 | Bhangi Ashwini A | Enhanced address book for mobile wireless communication devices |
-
2002
- 2002-12-23 DE DE60218899T patent/DE60218899T2/en not_active Expired - Lifetime
- 2002-12-23 US US10/500,269 patent/US20050130631A1/en not_active Abandoned
- 2002-12-23 WO PCT/CA2002/002030 patent/WO2003056789A1/en active IP Right Grant
- 2002-12-23 AT AT02787317T patent/ATE357109T1/en not_active IP Right Cessation
- 2002-12-23 CA CA2742282A patent/CA2742282C/en not_active Expired - Lifetime
- 2002-12-23 EP EP02787317A patent/EP1461935B1/en not_active Expired - Lifetime
- 2002-12-23 AU AU2002351644A patent/AU2002351644A1/en not_active Abandoned
- 2002-12-23 CA CA2471831A patent/CA2471831C/en not_active Expired - Lifetime
- 2002-12-23 ES ES07002178T patent/ES2396560T3/en not_active Expired - Lifetime
- 2002-12-23 CN CNA028283112A patent/CN1625886A/en active Pending
- 2002-12-23 CN CNA2008100939086A patent/CN101291361A/en active Pending
-
2005
- 2005-03-11 HK HK05102189A patent/HK1072333A1/en not_active IP Right Cessation
-
2007
- 2007-12-06 HK HK07113329.8A patent/HK1105057A1/en not_active IP Right Cessation
-
2008
- 2008-09-16 US US12/211,223 patent/US8620273B2/en not_active Expired - Lifetime
-
2013
- 2013-11-18 US US14/083,029 patent/US9681276B2/en not_active Expired - Lifetime
-
2017
- 2017-02-24 US US15/441,922 patent/US11317254B2/en not_active Expired - Lifetime
Also Published As
| Publication number | Publication date |
|---|---|
| US20090011741A1 (en) | 2009-01-08 |
| ATE357109T1 (en) | 2007-04-15 |
| EP1461935B1 (en) | 2007-03-14 |
| WO2003056789A1 (en) | 2003-07-10 |
| CA2471831A1 (en) | 2003-07-10 |
| US20110195691A9 (en) | 2011-08-11 |
| US8620273B2 (en) | 2013-12-31 |
| US20050130631A1 (en) | 2005-06-16 |
| US9681276B2 (en) | 2017-06-13 |
| AU2002351644A1 (en) | 2003-07-15 |
| US20170171726A1 (en) | 2017-06-15 |
| HK1072333A1 (en) | 2005-08-19 |
| CN101291361A (en) | 2008-10-22 |
| US11317254B2 (en) | 2022-04-26 |
| DE60218899T2 (en) | 2007-12-06 |
| US20140080460A1 (en) | 2014-03-20 |
| CA2471831C (en) | 2011-07-19 |
| CA2742282C (en) | 2014-12-16 |
| EP1461935A1 (en) | 2004-09-29 |
| ES2396560T3 (en) | 2013-02-22 |
| DE60218899D1 (en) | 2007-04-26 |
| CN1625886A (en) | 2005-06-08 |
| HK1105057A1 (en) | 2008-02-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11317254B2 (en) | User interface and method of viewing unified communications events on a mobile device | |
| US8683356B2 (en) | User interface and method for viewing short messages on a wireless device | |
| US10728373B2 (en) | Identifying caller name for output on mobile phone devices | |
| US7511603B2 (en) | Filtered in-box for voice mail, e-mail, pages, web-based information, and faxes | |
| EP1784970B1 (en) | Method of obtaining caller information in a mobile terminal and mobile terminal therefore | |
| US8194828B2 (en) | Providing voice messages to an intended recipient | |
| US8363794B2 (en) | Voice mail extension | |
| US20030018695A1 (en) | Information display apparatus and method | |
| EP1793569B1 (en) | User interface and method of viewing unified communications events on a mobile device | |
| KR20040003644A (en) | Method for data search of mobile communication terminal |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKEX | Expiry |
Effective date: 20221223 |