CA2479937C - Facilitating instant messaging outside of user-defined buddy group in a wireless and non-wireless environment - Google Patents
Facilitating instant messaging outside of user-defined buddy group in a wireless and non-wireless environment Download PDFInfo
- Publication number
- CA2479937C CA2479937C CA002479937A CA2479937A CA2479937C CA 2479937 C CA2479937 C CA 2479937C CA 002479937 A CA002479937 A CA 002479937A CA 2479937 A CA2479937 A CA 2479937A CA 2479937 C CA2479937 C CA 2479937C
- Authority
- CA
- Canada
- Prior art keywords
- user
- message
- routing
- mobile
- personal identifier
- 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.)
- Expired - Fee Related
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/18—Service support devices; Network management devices
- H04W88/184—Messaging devices, e.g. message centre
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/58—Message adaptation for wireless communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/48—Message addressing, e.g. address format or anonymous messages, aliases
-
- 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
Abstract
A method, system and computer program product for instant message communication in a wireless and non-wireless environment. The invented system includes an apparatus that facilitates conversation with individuals not included in the user's buddy group, non-buddies (183). The system includes at least one additional routing code (4561) reserved for conversing with non-buddies. The first time during a user session that the system receives a message originating from or destined for a non-buddy, before routing the message, the non-buddy's personal identifier is associated with one of the reserved routing codes (4561). The mobile user can then reply to the message using the same automated «reply» function available for replies to buddies.
The nonbuddy routing code assignment is only for the duration of a user session. When the mobile user signs off from the system, the routing code becomes available for reassignment.
The nonbuddy routing code assignment is only for the duration of a user session. When the mobile user signs off from the system, the routing code becomes available for reassignment.
Description
FACILITATING INSTANT MESSAGING OUTSIDE OF
USER-DEFINED BUDDY GROUP IN A WIRELESS AND
NON-WIRELESS ENVIRONMENT
BACKGROUND OF THE INVENTION
FIELD OF THE INVENTION
The present invention generally relates to non-voice message transmission and reception across cellular and public or private data networks and, more particularly to a method and system for instant message delivery between a cellular and public data network that facilitates communication outside of user-defined buddy groups.
DESCRIPTION OF RELATED ART
Around the world, tens of millions of users are using software that enables them to be alerted when friends, family and colleagues go on-line for real-time exchange of messages. A commonly used term for this type of real-time exchange is instant messaging. Instant messaging is extremely low-cost, with most vendors giving away the product and others charging nominal licensing fees. It is also powerful, allowing users to exchange messages in one window without interrupting a task in progress in another window; for example, looking over a document. Team members in different locations can set up impromptu conversations, bouncing ideas and strategies off each other. It provides quick and dirty collaboration, with little to buy and not much to set up.
The best-known instant messaging system is the AMERICA ONLINEO INSTANT
MESSENGERO (AIMO) that was originally designed as a feature for AOLO's pay service. AIM is software that anyone with an Internet connection can download, whether or not he or she is an AOL@ (AMERICA ONLINE ) subscriber. After registering a person identifier such as a SCREEN NAMEO or a ICQ number, the user can maintain lists of other AfM users, referred to herein as buddies, and be alerted whenever one of those in the list comes on-line. When one of those in the list comes on-line, the corresponding personal identifier appears with an audiovisual alert in an AIM interface window on the screen. By clicking on the name appearing in the AlM interface window, the user may then send an instant message and initiate a conversation session. Users can also sort their buddies into groups. For example, a lawyer could create separate groups for partners, associates, in-house counsel.
Despite the apparent success of instant messaging, it has, untii now, been limited to a user accessing the service through computer-based systems hardwired to the Internet. A co-pending U.S. Patent Application, C. Carey, B.
Robinson, Method and system for messaging across cellular networks and a public data network, U.S. Patent Application Ser. No. 09/519,525 (March 6, 2000), now U.S Patent No. 6,714,793, describes a system and method for instant message communication in wireless and non-wireless environments; thus extending the benefits of instant messaging to wireless environments, such as cellular phone systems. Using this system, an instant messaging subscriber can send and receive instant messages by means of a mobile unit device, such as a cell phone. Messages received may originate from a computer on a public data network, such as the Internet, or from other mobile unit devices. Furthermore, other instant messaging systems are known. For example, there are known instant messaging systems that send and receive messages by means of a command-line interface.
USER-DEFINED BUDDY GROUP IN A WIRELESS AND
NON-WIRELESS ENVIRONMENT
BACKGROUND OF THE INVENTION
FIELD OF THE INVENTION
The present invention generally relates to non-voice message transmission and reception across cellular and public or private data networks and, more particularly to a method and system for instant message delivery between a cellular and public data network that facilitates communication outside of user-defined buddy groups.
DESCRIPTION OF RELATED ART
Around the world, tens of millions of users are using software that enables them to be alerted when friends, family and colleagues go on-line for real-time exchange of messages. A commonly used term for this type of real-time exchange is instant messaging. Instant messaging is extremely low-cost, with most vendors giving away the product and others charging nominal licensing fees. It is also powerful, allowing users to exchange messages in one window without interrupting a task in progress in another window; for example, looking over a document. Team members in different locations can set up impromptu conversations, bouncing ideas and strategies off each other. It provides quick and dirty collaboration, with little to buy and not much to set up.
The best-known instant messaging system is the AMERICA ONLINEO INSTANT
MESSENGERO (AIMO) that was originally designed as a feature for AOLO's pay service. AIM is software that anyone with an Internet connection can download, whether or not he or she is an AOL@ (AMERICA ONLINE ) subscriber. After registering a person identifier such as a SCREEN NAMEO or a ICQ number, the user can maintain lists of other AfM users, referred to herein as buddies, and be alerted whenever one of those in the list comes on-line. When one of those in the list comes on-line, the corresponding personal identifier appears with an audiovisual alert in an AIM interface window on the screen. By clicking on the name appearing in the AlM interface window, the user may then send an instant message and initiate a conversation session. Users can also sort their buddies into groups. For example, a lawyer could create separate groups for partners, associates, in-house counsel.
Despite the apparent success of instant messaging, it has, untii now, been limited to a user accessing the service through computer-based systems hardwired to the Internet. A co-pending U.S. Patent Application, C. Carey, B.
Robinson, Method and system for messaging across cellular networks and a public data network, U.S. Patent Application Ser. No. 09/519,525 (March 6, 2000), now U.S Patent No. 6,714,793, describes a system and method for instant message communication in wireless and non-wireless environments; thus extending the benefits of instant messaging to wireless environments, such as cellular phone systems. Using this system, an instant messaging subscriber can send and receive instant messages by means of a mobile unit device, such as a cell phone. Messages received may originate from a computer on a public data network, such as the Internet, or from other mobile unit devices. Furthermore, other instant messaging systems are known. For example, there are known instant messaging systems that send and receive messages by means of a command-line interface.
Messaging between the user and buddies is easy and efficient. Sending a message to a buddy merely requires that the mobile unit user select a buddy from a list of personal identifiers displayed on the user interface of the mobile unit, compose the message and send it. A means is provided for the mobile user to reply to an instant message from a buddy quickly and easily, merely requiring the user to select a `reply' function.
Messaging between a mobile user and a non-buddy, that is someone not on the user's BUDDY LIST , is somewhat more complicated, requiring the user to manually key in the non-buddy's personal identifier for each message sent from the phone. Figure 8 provides a message flow diagram between a mobile unit 36 and a non-buddy 183. Step 181 illustrates the process of sending a message to a non-buddy. The system includes an `unlisted' function for communicating with non-buddies, having a unique routing code. The user composes the message 181A, including the non-buddy personal identifier in the body of the message, followed by a colon and a blank space, and sends it, using the `unlisted' function. Upon receipt by the short message service center 32, the message is forwarded 181 B to the instant message routing system 22. The instant message routing server captures the non-buddy personal indentifier and forwards the message to the desired recipient.
Step 182 illustrates the process of sending a message to a mobile unit 36 from a non-buddy 183. As shown at 182A, reply to the message may be made only by way of an entirely new message, requiring the user to manually key in the non-buddy's personal identifier correctly and compose the message in an operation identical to that of 181A. If the personal identifier is incorrectly typed, the message will be rejected or lost, requiring that the user retype the entire message.
Messaging between a mobile user and a non-buddy, that is someone not on the user's BUDDY LIST , is somewhat more complicated, requiring the user to manually key in the non-buddy's personal identifier for each message sent from the phone. Figure 8 provides a message flow diagram between a mobile unit 36 and a non-buddy 183. Step 181 illustrates the process of sending a message to a non-buddy. The system includes an `unlisted' function for communicating with non-buddies, having a unique routing code. The user composes the message 181A, including the non-buddy personal identifier in the body of the message, followed by a colon and a blank space, and sends it, using the `unlisted' function. Upon receipt by the short message service center 32, the message is forwarded 181 B to the instant message routing system 22. The instant message routing server captures the non-buddy personal indentifier and forwards the message to the desired recipient.
Step 182 illustrates the process of sending a message to a mobile unit 36 from a non-buddy 183. As shown at 182A, reply to the message may be made only by way of an entirely new message, requiring the user to manually key in the non-buddy's personal identifier correctly and compose the message in an operation identical to that of 181A. If the personal identifier is incorrectly typed, the message will be rejected or lost, requiring that the user retype the entire message.
Given the variety of environments in which wireless devices are deployed and the small size of the keypads typically found on wireless devices, such operation is extremely cumbersome and time-consuming. Keying in the personal identifier and the message may require the user to key in tens of separate characters. An equally tedious alternative to keying in the personal identifier involves the use of the mobile unit's `forward' feature. The user edits the received message to ieave only the non-buddy personal identifier of the original message, the reply is composed and the message is forwarded to the unlisted routing code, requiring the mobile user to remember the routing code of the `unlisted' function and key it in manually.
An embedded client (built into the handset of a wireless device, for example a Nokia 3390 Gold phone) assigns an index to all listed names and each unlisted name that is in conversation. Alternately, the unlisted name (unique ID) is associated with the conversation and attached to each reply message.
Other wireless instant messenging systems may use a single routing number for all mobile-originated requests. They require the user to enter a command code at the beginning of some or all messages to specify the action, and enter the ID of the recipient in each message.) An index is assigned to all listed names and each unlisted name that is in conversation. Alternately, the unlisted name (unique ID) is associated with the conversation and attached to each reply message.
It would be a great advantage to provide a method and system for messaging across cellular networks and a public data network that included a feature for easy reply to instant messages from a non-buddy, greatly facilitating instant messaging between a mobile unit user and parties not listed in the user-defined list.
An embedded client (built into the handset of a wireless device, for example a Nokia 3390 Gold phone) assigns an index to all listed names and each unlisted name that is in conversation. Alternately, the unlisted name (unique ID) is associated with the conversation and attached to each reply message.
Other wireless instant messenging systems may use a single routing number for all mobile-originated requests. They require the user to enter a command code at the beginning of some or all messages to specify the action, and enter the ID of the recipient in each message.) An index is assigned to all listed names and each unlisted name that is in conversation. Alternately, the unlisted name (unique ID) is associated with the conversation and attached to each reply message.
It would be a great advantage to provide a method and system for messaging across cellular networks and a public data network that included a feature for easy reply to instant messages from a non-buddy, greatly facilitating instant messaging between a mobile unit user and parties not listed in the user-defined list.
SUMMARY OF THE INVENTION
In a system for instant message communication in a wireless and non-wireless environment, messages are sent from and received by a mobile unit device over a wireless communication network. A registered user of the instant messaging system creates a list, for example an AIMO BUDDY LlSTO, of people with whom the user frequently exchanges instant messages, by providing the buddies' instant message personal identifiers. Each instant message personal identifier is associated with a destination address, also known as a routing code, at the instant message system.
This association is saved in memory in the instant message system and conserves phone number addresses in the telephone network. An address loading program is sent through the wireless environment to the mobile unit device of the registered user and loads the list, including personal identifiers and the associated routing numbers into the memory of the mobile unit. When the mobile unit user wishes to send a message to someone on his or her list, the user merely selects the personal identifier from the displayed list, composes the message and sends it. When the mobile unit user wishes to reply to a message received from a sender on the name list, the user merely selects a`reply' function and the reply is processed by the system in accordance with the previously saved information.
Within the above system, a method and apparatus for facilitating instant messaging outside of a user-defined buddy group provides a feature that allows easy reply to a sender not in the user's buddy group, i.e. a "non-buddy." The instant messaging system provides at least one additional routing code reserved for conversing with non-buddies. When the system receives an instant message for a user from a non-buddy, before routing the message to the user's mobile device, the non-buddy's personal identifier is associated with a reserved routing code. The mobile user then may reply to the message using the same `reply' function available for replies to buddies. Likewise, when the mobile user initiates a message to a non-buddy, the system captures the non-buddy's personal identifier and associates it with a reserved routing code. Thereafter, the user can reply to messages from the non-buddy by using an automated 'reply' function on the wireless device. The non-buddy routing code assignment is usually only for the duration of a user session, or until reassigned. When the mobile user signs off from the system, the routing code becomes available for reassignment.
BRIEF DESCRIPTION OF THE DRAWINGS
FIGURE 1 is a block diagram of a system for instant message communication in a wireless and non-wireless environment according to the invention;
FIGURE 2 is a flow diagram illustrating a process for remotely creating an instant message name list for a cellular phone according to the invention;
FIGURES 3-7 are flow diagrams illustrating processes for instant message function delivery, message delivery and instant message reception using a mobile unit device across a wireless and non-wireless network according to the invention;
FIGURE 8 provides a message flow diagram between a mobile unit and a non-buddy according to the invention;
FIGURE 9 provides a message flow diagram between a mobile unit and non-buddy using a non-buddy easy reply feature according to the invention; and FIGURE 10 shows a table of exemplary routing codes for use by users of mobile units according to the invention.
DETAILED DESCRIPTION
Described herein are an integrated wireless and traditional instant messaging system and method. As shown in FIGURE 1, the system 20 includes an instant message routing system 22 that inciudes a routing server 24 and a database 26 for storing a profile for each subscribing user. Each user profile includes a list of instant message names with each name assigned to an address (phone number). The routing server 24 is in communication with one or more short message service centers (SMSC) 32 that are in communication with one or more wireless mobile carriers 34. Each wireless mobile carrier 34 supports subscribing users operating mobile unit devices 36, such as a hand-held cell phone, a two-way pager or other SMS-based device. The routing server 24 is also coupled to a public or private data network 30, such as the Internet. Also coupled to the public or private data network 30 are an instant message server 40 and one or more traditional systems 42, such as a personal computer.
The communication link between the routing server 24 and the short message service center 32 is also either a public or private data network, such as the Internet or a private dedicated circuit. A protocol residing over the communication link defines the structure of information communicated between the routing server and the short message service center 32. Preferably, this link is the Internet with TCP/IP operating thereon. Operating over TCP/IP is another protocol that allows the routing server 24 to identify the effectiveness of communications to the mobile unit devices 36. An example protocol residing over TCP/IP is the short message peer-to-peer (SMPP) protocol or configuration or data management procedure (CDMP) protocol. These protocols provide visibility of the status of message deliveries to the mobile unit devices 36.
A data bearer protocol defines the structure of data messages communicated between the mobile unit devices 36, the mobile carrier 34 and the short message service center 32. The global system for mobile communications (GSM) environment, used as the primary digital wireless standard throughout Europe, uses the short message service (SMS) standard data bearer protocol for formatting data for delivery between the mobile unit devices 36, wireless mobile carrier 34 and the short message service center 32. The SMS protocol describes the format of data, called SMS packages, sent or received through the system. The format of data messages, i.e. SMS package, sent from the mobile unit device includes the phone number of the mobile unit device, a destination phone number, the short message service center address (preferably a number), a validity period value and message content. The validity period value informs the short message service center 32 how long to attempt delivery. Each data message (SMS package) is preferably a single block of information. As can be readily appreciated by those of ordinary skill in the art of wireless communication, the SMS package may be divided up into multiple packets of data and sent at various intervals.
In a system for instant message communication in a wireless and non-wireless environment, messages are sent from and received by a mobile unit device over a wireless communication network. A registered user of the instant messaging system creates a list, for example an AIMO BUDDY LlSTO, of people with whom the user frequently exchanges instant messages, by providing the buddies' instant message personal identifiers. Each instant message personal identifier is associated with a destination address, also known as a routing code, at the instant message system.
This association is saved in memory in the instant message system and conserves phone number addresses in the telephone network. An address loading program is sent through the wireless environment to the mobile unit device of the registered user and loads the list, including personal identifiers and the associated routing numbers into the memory of the mobile unit. When the mobile unit user wishes to send a message to someone on his or her list, the user merely selects the personal identifier from the displayed list, composes the message and sends it. When the mobile unit user wishes to reply to a message received from a sender on the name list, the user merely selects a`reply' function and the reply is processed by the system in accordance with the previously saved information.
Within the above system, a method and apparatus for facilitating instant messaging outside of a user-defined buddy group provides a feature that allows easy reply to a sender not in the user's buddy group, i.e. a "non-buddy." The instant messaging system provides at least one additional routing code reserved for conversing with non-buddies. When the system receives an instant message for a user from a non-buddy, before routing the message to the user's mobile device, the non-buddy's personal identifier is associated with a reserved routing code. The mobile user then may reply to the message using the same `reply' function available for replies to buddies. Likewise, when the mobile user initiates a message to a non-buddy, the system captures the non-buddy's personal identifier and associates it with a reserved routing code. Thereafter, the user can reply to messages from the non-buddy by using an automated 'reply' function on the wireless device. The non-buddy routing code assignment is usually only for the duration of a user session, or until reassigned. When the mobile user signs off from the system, the routing code becomes available for reassignment.
BRIEF DESCRIPTION OF THE DRAWINGS
FIGURE 1 is a block diagram of a system for instant message communication in a wireless and non-wireless environment according to the invention;
FIGURE 2 is a flow diagram illustrating a process for remotely creating an instant message name list for a cellular phone according to the invention;
FIGURES 3-7 are flow diagrams illustrating processes for instant message function delivery, message delivery and instant message reception using a mobile unit device across a wireless and non-wireless network according to the invention;
FIGURE 8 provides a message flow diagram between a mobile unit and a non-buddy according to the invention;
FIGURE 9 provides a message flow diagram between a mobile unit and non-buddy using a non-buddy easy reply feature according to the invention; and FIGURE 10 shows a table of exemplary routing codes for use by users of mobile units according to the invention.
DETAILED DESCRIPTION
Described herein are an integrated wireless and traditional instant messaging system and method. As shown in FIGURE 1, the system 20 includes an instant message routing system 22 that inciudes a routing server 24 and a database 26 for storing a profile for each subscribing user. Each user profile includes a list of instant message names with each name assigned to an address (phone number). The routing server 24 is in communication with one or more short message service centers (SMSC) 32 that are in communication with one or more wireless mobile carriers 34. Each wireless mobile carrier 34 supports subscribing users operating mobile unit devices 36, such as a hand-held cell phone, a two-way pager or other SMS-based device. The routing server 24 is also coupled to a public or private data network 30, such as the Internet. Also coupled to the public or private data network 30 are an instant message server 40 and one or more traditional systems 42, such as a personal computer.
The communication link between the routing server 24 and the short message service center 32 is also either a public or private data network, such as the Internet or a private dedicated circuit. A protocol residing over the communication link defines the structure of information communicated between the routing server and the short message service center 32. Preferably, this link is the Internet with TCP/IP operating thereon. Operating over TCP/IP is another protocol that allows the routing server 24 to identify the effectiveness of communications to the mobile unit devices 36. An example protocol residing over TCP/IP is the short message peer-to-peer (SMPP) protocol or configuration or data management procedure (CDMP) protocol. These protocols provide visibility of the status of message deliveries to the mobile unit devices 36.
A data bearer protocol defines the structure of data messages communicated between the mobile unit devices 36, the mobile carrier 34 and the short message service center 32. The global system for mobile communications (GSM) environment, used as the primary digital wireless standard throughout Europe, uses the short message service (SMS) standard data bearer protocol for formatting data for delivery between the mobile unit devices 36, wireless mobile carrier 34 and the short message service center 32. The SMS protocol describes the format of data, called SMS packages, sent or received through the system. The format of data messages, i.e. SMS package, sent from the mobile unit device includes the phone number of the mobile unit device, a destination phone number, the short message service center address (preferably a number), a validity period value and message content. The validity period value informs the short message service center 32 how long to attempt delivery. Each data message (SMS package) is preferably a single block of information. As can be readily appreciated by those of ordinary skill in the art of wireless communication, the SMS package may be divided up into multiple packets of data and sent at various intervals.
FIGURE 2 illustrates a method for remotely creating an instant message name list for a cellular phone. First, a user, who is a subscriber to a wireless instant message service, uses a traditional system 42 coupled to the network 30 to sign on to a web site supported or generated by the routing server 24. A user becomes a subscriber by completing a registration process that can be performed during online communication with either servers 24 or 40 or through other means, such as e-mail, conventional mail or telephonic communication. Once the user has entered into the routing server's web site by preferably completing a sign-on or logon with password verification, the user begins instant message name list creation for the user's mobile unit device 36. If the cell phone user knows the instant message name that corresponds to a desired recipient, decision block 50, the user enters the instant message name. The entered instant message name is then saved in a look-up table at a location in the database 26, block 52. The look-up table is stored in relation to predefined user profile information. Each instant message name stored in the look-up table has a corresponding destination address, preferably a phone number.
For example, the routing server 24 receives from the mobile carrier 34 or a telecommunications controlling agency a set of n telephone numbers. In the database 26 for each user profile, the server 24 associates a number from the set of n telephone numbers to an entered instant message name. As a result, the routing system 22 reuses a limited number of phone numbers.
If the cell phone user does not know the instant message name that corresponds to a desired recipient, decision block 50, the user enters information that corresponds to the desired recipient, such as an e-mail address, block 54. The server hosting the name list creation website then searches for an instant message name that corresponds to the entered information, block 60. If, at decision block 60, there is a corresponding instant message name, the corresponding instant message name is entered and saved, see block 52 above. If, at decision block 60, the search fails to find a corresponding instant message name, no name entry occurs and the user is given the opportunity to enter more instant message names, decision block 62.
The user is also given the opportunity to enter more instant message names after block 52.
If, at decision block 62, the user does not wish to enter more instant message names, a program is generated by the server hosting the name list creation website for programming the created instant message name list into the user's mobile unit device 36, block 68. Next, at block 70, the generated program is sent through the short message service center 32, where it is formatted according to the proper protocol, and then through the mobile carrier 34 to the user's mobile unit device 36.
At block 72, the user's mobile unit device 36 receives and executes the program, thus saving the instant message name list in an address book stored in memory.
In other words, the mobile unit device is programmed in an over-the-air-programming manner to include the instant message name list within the mobile unit device's instant message listings (i.e. address book).
In an alternative embodiment, if the mobile carrier 34 and corresponding mobile unit devices 36 do not include the hardware or software components for receiving and executing the program for loading the saved instant message name list, the loading of instant message names and corresponding phone numbers that are stored at the routing system 22 are manually entered into the address book of the user's mobile unit device 36.
FIGURES 3-7 illustrate the process of instant message function delivery, message delivery and instant message reception using a mobile unit device across a wireless and non-wireless network. First, at block 80 of FIGURE 3, through a user interface on the mobile unit device 36 the user selects an instant message function or an instant message name(s) from the mobile unit device's address book based on the latest stored instant message name status information received from the instant message name routing server 24 as a result of a sign on, a status update or the last communication with the instant message routing server 24 (see FIGURE 5 below).
Then, the user enters message content information (either function related information or a message accordingly). Alternatively, the message content information is entered first, then an instant message function or an instant message name is selected. Next, at block 82, the user's selection and entered information is formatted according to the predefined protocol and sent to the mobile carrier 34. At block 84, the mobile carrier 34 receives the formatted data and sends the formatted data to a short message service center 32 according to the included short message service center address information. At decision block 86, the short message service center 32 determines if the received formatted data includes address data assigned to an instant message routing server 24, i.e. an address field or phone number. If the formatted data does not include address data assigned to an instant message routing server 24, the formatted data is probably an phone-to-phone short message and is processed according to known cellular Short Message processing methods, block 88; also commonly referred to as email for cell phones. If the formatted data does include address data assigned to an instant message routing server 24, the formatted data is reformatted according to the predefined protocol used to communicate information between the short message service center 32 and the instant message routing server 24 and then sent to the instant message routing server 24, block 90.
As shown in FIGURE 4, at decision block 102, the instant message routing server 24 compares the destination number included in the reformatted data to the look-up table in the user profile location in the database 26 that corresponds to the mobile unit device phone number included with the received data. The comparison determines what action corresponds to the destination number. If the action corresponding to the destination number is an instant message function, the instant message routing server 24 executes the instant message function, see FIGURE 5 below. If the action corresponding to the destination number is an instant message name, the instant message routing server 24 repackages the formatted data as an instant message and sends it to the recipient associated with instant message name, block 104. Before or after the repackaging occurs, the instant message routing server 24 determines if the recipient that corresponds to the instant message name is signed on to the instant message system, i.e. the instant message server 40, decision block 106. If the recipient is not signed on, the instant message routing server 24 sends a failure message to the user's mobile unit device 36 through the short message service center 32 and mobile carrier 34, block 108. In a first alternate embodiment, if the recipient is not signed on, the instant message server 40 stores the instant message until the instant message server 40 detects that the recipient has signed on through an instant message routing server 24 or a traditional system 42. In a second alternate embodiment, if the 'recipient is not signed on, the instant message is forwarded to a previously designated e-mail address.
If the recipient is signed on, the instant message routing server 24 sends the instant message to the recipient through the instant message server 40 over the network 30, block 110. The process of sending an instant message to a mobile unit device recipient is described in more detail below in FIGURES 6 and 7.
FIGURE 5 illustrates the process of processing data received from a mobile unit device 36 that corresponds to an instant message function, from B of FIGURE 4.
First, at decision block 120, if the function is a sign on function, the instant message routing server 24 establishes a new instant message session with the instant message server 40 for the user associated with the mobile unit device 36 that send the sign on function. The establishment of a new instant message session is done in accordance with the proper password(s) that was included in the message content sent from the mobile unit device 36, block 122. The instant message routing server 24 checks with instant message server 40 to determine which of the names in the instant message name list associated with the user and stored in the database 26 are available or signed on, block 124. This determination of who is available is then sent to the mobile unit device 36 through the short message service center 32 and the mobile carrier 34, block 126. Once the mobile unit device 36 receives the availability determination, the device 36 process it and makes the availability information available for use by the user, block 127.
If the instant message function is not the sign on (sign on) function and if no instant message session is presently active for the user at the instant message routing server 24, decision block 128, a message informing the user that sign on must occur first is presented, block 130. If an instant message session exists and the function is a sign off (sign off) function, decision block 132, the instant message routing server 24 ends the corresponding instant message session, block 134. However, if the function is not the sign off function, the function is processed according to instant message rules, block 136. The following other functions are available: delete;
add;
and check status. With regards to the delete function, the instant message routing server 24 deletes each instant message name included in the message content from the instant message name list stored with the user's profile information in the database 26. With regards to the add function, the instant message routing server 24 adds each instant message name included in the message content to the instant message name list stored with the user's profile information in the database 26. During instant message session the instant message routing server 24, like an instant message session on a traditional system 42, continually receives connection status information of each instant message name in the instant message name list. With regards to the check status function, the instant message routing server 24 sends the latest received connection status information to the mobile user device 36 through the short message service center 32 and the mobile carrier 34.
FIGURES 6 and 7 illustrate the process of sending an instant message to a recipient signed on to the instant message service from a mobile unit device 36 through an instant message routing server 24. The process of FIGURE 6 occurs when an instant message is sent from another user of a mobile unit device 36, C from FIGURE 4, or from a user of a traditional system 42, such as a desktop or laptop computer. First, at block 140, the instant message server 40 receives an instant message and, at block 142, sends it to the signed on recipient identified in the instant message. If, at decision block 144, the recipient is a normal instant message recipient, i.e. not a recipient with an instant message session active through the instant message routing server 24, the recipient receives and views the instant message as per instant message procedures, block 146. If, on the other hand, at decision block 144, the recipient is a user with an instant message session active through the instant message routing server 24, the instant message routing server 24 receives the instant message, block 148. Then, at block 150, the instant message routing server 24 prepares the received instant message according to the predefined protocol and sends the prepared instant message to the short message service center 32, where the short message service center 32 stores and forwards the instant message to the mobile carrier 36 according to the predefined wireless protocol, block 152.
As shown in FIGURE 7, at block 160, the mobile carrier 36 prepares the instant message received from the short message service center 32 for transmission and sends the prepared transmission to the mobile unit device 36. lf, at decision block 162, the mobile unit device 36 successfully receives the prepared transmission of the instant message, the mobile unit device 36 replies to the short message service center 32 that the transmission was received, block 164. Then, at block 166, the short message service center 32 receives the mobile unit device's successful reply and deletes the stored instant message.
If, however, at decision block 162, the mobile unit device 36 did not successfully receive the prepared transmission of the instant message and if, at decision block 168, a transmission delivery threshold has not been reached, a message is sent to the short message service center 32 that the mobile unit device 36 did not successfully receive the instant message, block 170. This message of unsuccessful reception is sent by the mobile carrier 34. When the short message service center 32 receives a message of unsuccessful reception, the short message service center 32 retrieves the stored instant message that corresponds to the unsuccessfully sent transmission and resends the transmission to the mobile unit device 36 through the mobile carrier 34, blocks 172 and 160.
Again, at decision block 162, if the mobile unit device 36 did not successfully receive the prepared transmission of the instant message and if, at decision block 168, a transmission delivery threshold has been reached, the mobile carrier 34 sends a message to the instant message routing server 24 through the short message service center 32 that the mobile unit device 36 is not connected or not receiving instant messages, block 174. When the instant message routing server receives a message of this type, the instant message routing server 24 signs off or logs off the mobile unit device 36 that failed to receive the transmission, block 176.
Alternatively, the user may undergo a change of presence status, such as "busy" or "unavailable:"
The transmission delivery threshold is preferably a predefined number of delivery attempts. Once the number of attempts have been reached or exceeded, the mobile carrier 34 assumes the mobile user device 36 is off or out of reception range.
It can be readily appreciated by those of ordinary skill in the art of cell phone communication, that various data delivery methods can be used for insuring information gets delivered during temporary periods of time when the cell phone is out of communication with the mobile carrier. In addition to those functions previously described, the mobile unit provides at least the following additional functions:
= `unlisted;' = `forward;' and = `reply.' It is noted that `unlisted' is conceptually different from `forward' and `reply' in that `unlisted' denotes an instant messaging user class, and the system function required to interact with that class, whereas `forward' and `reply' constitute message manipulation functions built into the device itself.
Figures 8 and 9 illustrate the flow of messages between mobile units 36 and traditional system 42 users who are not identified as preferred friends of the mobile unit 36 instant messaging user. Figure 8 depicts the message flow under existing systems, while Figure 9 depicts the message flow in accordance with the invention.
Figure 8 shows a message flow diagram between a mobile unit 36 and a non-buddy 183 using a conventional system 42. The body of the message 181 is explicitly targeted to the non-buddy 183 with the text "NonBudB:" at the beginning of the message, as seen in 181A. The message 181A travels from the mobile unit 36 to the short message service center (SMS-C) 32, such that the Destination Address of 4654 is not analyzed until received by the short message service center 32.
The short message service center 32 recognizes that the destination address belongs to the family of addresses for instant messaging and the message 181 B is forwarded to the instant message routing system 22. The instant message routing system 22 reformats the message by extracting the non-buddy's instant message address of "NonBudB" and forwards the reformatted message 181 C to the traditional system 42, either directly or through the instant messenger server 40.
The messages in 182 indicate the process in reverse of 181, wherein a traditional system 42 non-buddy 183 sends a message 182A to mobile unit 36 by addressing the message to "PhoneA" as a normal instant message. The instant message routing system 22 reformats the message 182B by prefixing the non-buddy's instant message address "NonBudB" to the message body, also by attaching the telephone number of "PhoneA" which in this example is 12345678901, and forwards the reformatted message 182C to the short message service center 32. The short message service center 32 stores the message and attempts delivery. For the purposes of Figure 8 the message is delivered to the mobile unit 36. The mobile unit 36 presents the message to the user. For the mobile unit 36 to send a message back to non-buddy 183, the entire process of 181 is repeated, including the re-entering of the traditional system 42 personal identifier.
The instant message routing system 22 reformats the message 182B by prefixing the non-buddy's instant message address "NonBudB" to the message body, also by attaching the telephone number of "PhoneA" which in this example is 12345678901, and forwards the reformatted message 182C to the short message service center 32.
In accordance with the invention, Figure 9 shows a message flow diagram between a mobile unit 36 and a non-buddy in which message flow is faciliated by a non-buddy easy reply feature. Step 191 illustrates the process of sending a message to the non--buddy from the mobile unit. As in 181A, The user composes the message 191A, including the non-buddy personal identifier in the body of the message, followed by a colon and a blank space, and sends it, using the `unlisted' function. The message is received at the short message service center 32 and forwarded 191 B to the instant message routing system 22. The instant message routing system provides at least one routing code reserved for the non-buddy easy reply feature, denoted in FIGURE
9 by the code `4561.' Upon receipt of the message, the instant message routing server 24 captures the non-buddy's name from the body of the message and assigns an easy-reply routing code, e.g. `4561.' Subsequently, the message is forwarded 191 C to its destination, non-buddy NonBudB183. In an optional step 192, the instant message routing server 24 returns a notification of the easy-reply routing code assignment to the mobile unit 36 to aid in subsequent messaging.
In an aiternative emobidment, the `unlisted' routing code becomes associated with a non-buddy, for easy-reply, until a second non-buddy exchange is started. This association can be automatically reset by a period of inactivity.
As step 193 shows, when the non-buddy 183 is the first to send a message, the instant message routing server 24 immediately assigns an easy-reply routing code, whereupon the mobile unit 36 and the non-buddy 183 are able to exchange messages readily and efficiently, as shown in step 194, with no greater effort than required of two SMS phone users.
One can easily imagine a second non-buddy 195 sending a message to the mobile user 36 during a conversation with the first non-buddy 183, creating a race condition.
In the event that the available routing codes have all been assigned when the system receives the message from the second non-buddy, the system recycle's routing codes. Thus, a situation may occur in which the mobile user has sent a message using an easy-repiy routing code, but the code is reassigned before the message reaches the instant message routing server, with the result that the non-buddy the code has been reassigned to receives the message intended for the first non-buddy. Because experience shows that a mobile user typically starts a non-buddy conversation approximately once in a twelve-hour period, the possibility of a race condition occurring is slight. Nevertheless, the possibility of a race condition occurring is minimized in one or both of two ways:
= The instant messaging server can hold the non-buddy message pending confirmation of the mobile user's interest in receiving the message; and = A bank of easy reply routing codes are provisioned, minimizing the possibility that the system will be faced with the necessity of recycling routing codes during a user session.
Easy reply routing code assignments usually persist only for the duration of a user session, or until reassignment, for example when there are more buddies than routing codes. When the mobile user signs off from the system, the routing code becomes available for reassignment. An embodiment is also possible in which routing code assignments survive logoff.
Figure 10 provides a table of exemplary routing codes. As previously explained, the invention uses such codes for messaging with non-buddies, as well as for messaging with buddies, and system commands.
In an alternative embodiment, the wireless instant messaging system may use a single routing number for all mobile-originated requests, and then assign another routing number for each sender in the manner described above to simplify the exchange of further messages.
The invention is embodied as a method, an apparatus and a computer program product. Implementation of the invention is accomplished by means of conventional methods of computer programming using one or more commonly known programming languages.
Although the invention has been described herein with reference to certain preferred embodiments, one skilled in the art will readily appreciate that other applications may be substituted for those set forth herein without departing from the spirit and scope of the present invention. Accordingly, the invention should only be limited by the Claims included below.
For example, the routing server 24 receives from the mobile carrier 34 or a telecommunications controlling agency a set of n telephone numbers. In the database 26 for each user profile, the server 24 associates a number from the set of n telephone numbers to an entered instant message name. As a result, the routing system 22 reuses a limited number of phone numbers.
If the cell phone user does not know the instant message name that corresponds to a desired recipient, decision block 50, the user enters information that corresponds to the desired recipient, such as an e-mail address, block 54. The server hosting the name list creation website then searches for an instant message name that corresponds to the entered information, block 60. If, at decision block 60, there is a corresponding instant message name, the corresponding instant message name is entered and saved, see block 52 above. If, at decision block 60, the search fails to find a corresponding instant message name, no name entry occurs and the user is given the opportunity to enter more instant message names, decision block 62.
The user is also given the opportunity to enter more instant message names after block 52.
If, at decision block 62, the user does not wish to enter more instant message names, a program is generated by the server hosting the name list creation website for programming the created instant message name list into the user's mobile unit device 36, block 68. Next, at block 70, the generated program is sent through the short message service center 32, where it is formatted according to the proper protocol, and then through the mobile carrier 34 to the user's mobile unit device 36.
At block 72, the user's mobile unit device 36 receives and executes the program, thus saving the instant message name list in an address book stored in memory.
In other words, the mobile unit device is programmed in an over-the-air-programming manner to include the instant message name list within the mobile unit device's instant message listings (i.e. address book).
In an alternative embodiment, if the mobile carrier 34 and corresponding mobile unit devices 36 do not include the hardware or software components for receiving and executing the program for loading the saved instant message name list, the loading of instant message names and corresponding phone numbers that are stored at the routing system 22 are manually entered into the address book of the user's mobile unit device 36.
FIGURES 3-7 illustrate the process of instant message function delivery, message delivery and instant message reception using a mobile unit device across a wireless and non-wireless network. First, at block 80 of FIGURE 3, through a user interface on the mobile unit device 36 the user selects an instant message function or an instant message name(s) from the mobile unit device's address book based on the latest stored instant message name status information received from the instant message name routing server 24 as a result of a sign on, a status update or the last communication with the instant message routing server 24 (see FIGURE 5 below).
Then, the user enters message content information (either function related information or a message accordingly). Alternatively, the message content information is entered first, then an instant message function or an instant message name is selected. Next, at block 82, the user's selection and entered information is formatted according to the predefined protocol and sent to the mobile carrier 34. At block 84, the mobile carrier 34 receives the formatted data and sends the formatted data to a short message service center 32 according to the included short message service center address information. At decision block 86, the short message service center 32 determines if the received formatted data includes address data assigned to an instant message routing server 24, i.e. an address field or phone number. If the formatted data does not include address data assigned to an instant message routing server 24, the formatted data is probably an phone-to-phone short message and is processed according to known cellular Short Message processing methods, block 88; also commonly referred to as email for cell phones. If the formatted data does include address data assigned to an instant message routing server 24, the formatted data is reformatted according to the predefined protocol used to communicate information between the short message service center 32 and the instant message routing server 24 and then sent to the instant message routing server 24, block 90.
As shown in FIGURE 4, at decision block 102, the instant message routing server 24 compares the destination number included in the reformatted data to the look-up table in the user profile location in the database 26 that corresponds to the mobile unit device phone number included with the received data. The comparison determines what action corresponds to the destination number. If the action corresponding to the destination number is an instant message function, the instant message routing server 24 executes the instant message function, see FIGURE 5 below. If the action corresponding to the destination number is an instant message name, the instant message routing server 24 repackages the formatted data as an instant message and sends it to the recipient associated with instant message name, block 104. Before or after the repackaging occurs, the instant message routing server 24 determines if the recipient that corresponds to the instant message name is signed on to the instant message system, i.e. the instant message server 40, decision block 106. If the recipient is not signed on, the instant message routing server 24 sends a failure message to the user's mobile unit device 36 through the short message service center 32 and mobile carrier 34, block 108. In a first alternate embodiment, if the recipient is not signed on, the instant message server 40 stores the instant message until the instant message server 40 detects that the recipient has signed on through an instant message routing server 24 or a traditional system 42. In a second alternate embodiment, if the 'recipient is not signed on, the instant message is forwarded to a previously designated e-mail address.
If the recipient is signed on, the instant message routing server 24 sends the instant message to the recipient through the instant message server 40 over the network 30, block 110. The process of sending an instant message to a mobile unit device recipient is described in more detail below in FIGURES 6 and 7.
FIGURE 5 illustrates the process of processing data received from a mobile unit device 36 that corresponds to an instant message function, from B of FIGURE 4.
First, at decision block 120, if the function is a sign on function, the instant message routing server 24 establishes a new instant message session with the instant message server 40 for the user associated with the mobile unit device 36 that send the sign on function. The establishment of a new instant message session is done in accordance with the proper password(s) that was included in the message content sent from the mobile unit device 36, block 122. The instant message routing server 24 checks with instant message server 40 to determine which of the names in the instant message name list associated with the user and stored in the database 26 are available or signed on, block 124. This determination of who is available is then sent to the mobile unit device 36 through the short message service center 32 and the mobile carrier 34, block 126. Once the mobile unit device 36 receives the availability determination, the device 36 process it and makes the availability information available for use by the user, block 127.
If the instant message function is not the sign on (sign on) function and if no instant message session is presently active for the user at the instant message routing server 24, decision block 128, a message informing the user that sign on must occur first is presented, block 130. If an instant message session exists and the function is a sign off (sign off) function, decision block 132, the instant message routing server 24 ends the corresponding instant message session, block 134. However, if the function is not the sign off function, the function is processed according to instant message rules, block 136. The following other functions are available: delete;
add;
and check status. With regards to the delete function, the instant message routing server 24 deletes each instant message name included in the message content from the instant message name list stored with the user's profile information in the database 26. With regards to the add function, the instant message routing server 24 adds each instant message name included in the message content to the instant message name list stored with the user's profile information in the database 26. During instant message session the instant message routing server 24, like an instant message session on a traditional system 42, continually receives connection status information of each instant message name in the instant message name list. With regards to the check status function, the instant message routing server 24 sends the latest received connection status information to the mobile user device 36 through the short message service center 32 and the mobile carrier 34.
FIGURES 6 and 7 illustrate the process of sending an instant message to a recipient signed on to the instant message service from a mobile unit device 36 through an instant message routing server 24. The process of FIGURE 6 occurs when an instant message is sent from another user of a mobile unit device 36, C from FIGURE 4, or from a user of a traditional system 42, such as a desktop or laptop computer. First, at block 140, the instant message server 40 receives an instant message and, at block 142, sends it to the signed on recipient identified in the instant message. If, at decision block 144, the recipient is a normal instant message recipient, i.e. not a recipient with an instant message session active through the instant message routing server 24, the recipient receives and views the instant message as per instant message procedures, block 146. If, on the other hand, at decision block 144, the recipient is a user with an instant message session active through the instant message routing server 24, the instant message routing server 24 receives the instant message, block 148. Then, at block 150, the instant message routing server 24 prepares the received instant message according to the predefined protocol and sends the prepared instant message to the short message service center 32, where the short message service center 32 stores and forwards the instant message to the mobile carrier 36 according to the predefined wireless protocol, block 152.
As shown in FIGURE 7, at block 160, the mobile carrier 36 prepares the instant message received from the short message service center 32 for transmission and sends the prepared transmission to the mobile unit device 36. lf, at decision block 162, the mobile unit device 36 successfully receives the prepared transmission of the instant message, the mobile unit device 36 replies to the short message service center 32 that the transmission was received, block 164. Then, at block 166, the short message service center 32 receives the mobile unit device's successful reply and deletes the stored instant message.
If, however, at decision block 162, the mobile unit device 36 did not successfully receive the prepared transmission of the instant message and if, at decision block 168, a transmission delivery threshold has not been reached, a message is sent to the short message service center 32 that the mobile unit device 36 did not successfully receive the instant message, block 170. This message of unsuccessful reception is sent by the mobile carrier 34. When the short message service center 32 receives a message of unsuccessful reception, the short message service center 32 retrieves the stored instant message that corresponds to the unsuccessfully sent transmission and resends the transmission to the mobile unit device 36 through the mobile carrier 34, blocks 172 and 160.
Again, at decision block 162, if the mobile unit device 36 did not successfully receive the prepared transmission of the instant message and if, at decision block 168, a transmission delivery threshold has been reached, the mobile carrier 34 sends a message to the instant message routing server 24 through the short message service center 32 that the mobile unit device 36 is not connected or not receiving instant messages, block 174. When the instant message routing server receives a message of this type, the instant message routing server 24 signs off or logs off the mobile unit device 36 that failed to receive the transmission, block 176.
Alternatively, the user may undergo a change of presence status, such as "busy" or "unavailable:"
The transmission delivery threshold is preferably a predefined number of delivery attempts. Once the number of attempts have been reached or exceeded, the mobile carrier 34 assumes the mobile user device 36 is off or out of reception range.
It can be readily appreciated by those of ordinary skill in the art of cell phone communication, that various data delivery methods can be used for insuring information gets delivered during temporary periods of time when the cell phone is out of communication with the mobile carrier. In addition to those functions previously described, the mobile unit provides at least the following additional functions:
= `unlisted;' = `forward;' and = `reply.' It is noted that `unlisted' is conceptually different from `forward' and `reply' in that `unlisted' denotes an instant messaging user class, and the system function required to interact with that class, whereas `forward' and `reply' constitute message manipulation functions built into the device itself.
Figures 8 and 9 illustrate the flow of messages between mobile units 36 and traditional system 42 users who are not identified as preferred friends of the mobile unit 36 instant messaging user. Figure 8 depicts the message flow under existing systems, while Figure 9 depicts the message flow in accordance with the invention.
Figure 8 shows a message flow diagram between a mobile unit 36 and a non-buddy 183 using a conventional system 42. The body of the message 181 is explicitly targeted to the non-buddy 183 with the text "NonBudB:" at the beginning of the message, as seen in 181A. The message 181A travels from the mobile unit 36 to the short message service center (SMS-C) 32, such that the Destination Address of 4654 is not analyzed until received by the short message service center 32.
The short message service center 32 recognizes that the destination address belongs to the family of addresses for instant messaging and the message 181 B is forwarded to the instant message routing system 22. The instant message routing system 22 reformats the message by extracting the non-buddy's instant message address of "NonBudB" and forwards the reformatted message 181 C to the traditional system 42, either directly or through the instant messenger server 40.
The messages in 182 indicate the process in reverse of 181, wherein a traditional system 42 non-buddy 183 sends a message 182A to mobile unit 36 by addressing the message to "PhoneA" as a normal instant message. The instant message routing system 22 reformats the message 182B by prefixing the non-buddy's instant message address "NonBudB" to the message body, also by attaching the telephone number of "PhoneA" which in this example is 12345678901, and forwards the reformatted message 182C to the short message service center 32. The short message service center 32 stores the message and attempts delivery. For the purposes of Figure 8 the message is delivered to the mobile unit 36. The mobile unit 36 presents the message to the user. For the mobile unit 36 to send a message back to non-buddy 183, the entire process of 181 is repeated, including the re-entering of the traditional system 42 personal identifier.
The instant message routing system 22 reformats the message 182B by prefixing the non-buddy's instant message address "NonBudB" to the message body, also by attaching the telephone number of "PhoneA" which in this example is 12345678901, and forwards the reformatted message 182C to the short message service center 32.
In accordance with the invention, Figure 9 shows a message flow diagram between a mobile unit 36 and a non-buddy in which message flow is faciliated by a non-buddy easy reply feature. Step 191 illustrates the process of sending a message to the non--buddy from the mobile unit. As in 181A, The user composes the message 191A, including the non-buddy personal identifier in the body of the message, followed by a colon and a blank space, and sends it, using the `unlisted' function. The message is received at the short message service center 32 and forwarded 191 B to the instant message routing system 22. The instant message routing system provides at least one routing code reserved for the non-buddy easy reply feature, denoted in FIGURE
9 by the code `4561.' Upon receipt of the message, the instant message routing server 24 captures the non-buddy's name from the body of the message and assigns an easy-reply routing code, e.g. `4561.' Subsequently, the message is forwarded 191 C to its destination, non-buddy NonBudB183. In an optional step 192, the instant message routing server 24 returns a notification of the easy-reply routing code assignment to the mobile unit 36 to aid in subsequent messaging.
In an aiternative emobidment, the `unlisted' routing code becomes associated with a non-buddy, for easy-reply, until a second non-buddy exchange is started. This association can be automatically reset by a period of inactivity.
As step 193 shows, when the non-buddy 183 is the first to send a message, the instant message routing server 24 immediately assigns an easy-reply routing code, whereupon the mobile unit 36 and the non-buddy 183 are able to exchange messages readily and efficiently, as shown in step 194, with no greater effort than required of two SMS phone users.
One can easily imagine a second non-buddy 195 sending a message to the mobile user 36 during a conversation with the first non-buddy 183, creating a race condition.
In the event that the available routing codes have all been assigned when the system receives the message from the second non-buddy, the system recycle's routing codes. Thus, a situation may occur in which the mobile user has sent a message using an easy-repiy routing code, but the code is reassigned before the message reaches the instant message routing server, with the result that the non-buddy the code has been reassigned to receives the message intended for the first non-buddy. Because experience shows that a mobile user typically starts a non-buddy conversation approximately once in a twelve-hour period, the possibility of a race condition occurring is slight. Nevertheless, the possibility of a race condition occurring is minimized in one or both of two ways:
= The instant messaging server can hold the non-buddy message pending confirmation of the mobile user's interest in receiving the message; and = A bank of easy reply routing codes are provisioned, minimizing the possibility that the system will be faced with the necessity of recycling routing codes during a user session.
Easy reply routing code assignments usually persist only for the duration of a user session, or until reassignment, for example when there are more buddies than routing codes. When the mobile user signs off from the system, the routing code becomes available for reassignment. An embodiment is also possible in which routing code assignments survive logoff.
Figure 10 provides a table of exemplary routing codes. As previously explained, the invention uses such codes for messaging with non-buddies, as well as for messaging with buddies, and system commands.
In an alternative embodiment, the wireless instant messaging system may use a single routing number for all mobile-originated requests, and then assign another routing number for each sender in the manner described above to simplify the exchange of further messages.
The invention is embodied as a method, an apparatus and a computer program product. Implementation of the invention is accomplished by means of conventional methods of computer programming using one or more commonly known programming languages.
Although the invention has been described herein with reference to certain preferred embodiments, one skilled in the art will readily appreciate that other applications may be substituted for those set forth herein without departing from the spirit and scope of the present invention. Accordingly, the invention should only be limited by the Claims included below.
Claims (54)
1. A method of facilitating instant messaging outside of a user-defined buddy group, comprising the steps of:
providing a plurality of reserved routing codes on a computer-readable medium for exchanging instant messages with users not included in said user-defined buddy group;
exchanging instant messages between a user of a mobile unit device and a second user, said second user not included in said mobile user's buddy group;
assigning one of said routing codes to a message directed to said second user by said mobile unit user; and temporarily assigning one of said routing codes to said second user's personal identifier so that said mobile user can easily reply to said second user without originating a new message.
providing a plurality of reserved routing codes on a computer-readable medium for exchanging instant messages with users not included in said user-defined buddy group;
exchanging instant messages between a user of a mobile unit device and a second user, said second user not included in said mobile user's buddy group;
assigning one of said routing codes to a message directed to said second user by said mobile unit user; and temporarily assigning one of said routing codes to said second user's personal identifier so that said mobile user can easily reply to said second user without originating a new message.
2. The method of Claim 1, wherein said step of exchanging instant messages comprises the steps of:
composing a message for said second user by said mobile user, said message including at least said second user's personal identifier in body of said message;
sending said message to a routing code assigned to an 'unlisted' function on said mobile device;
receiving said message at said instant messaging system;
capturing said second user's personal identifier by said instant messaging system;
assigning a routing code to said second users personal identifier; and sending said message to said second user; and optionally returning notice of said assignment to said mobile user, so that future messaging is facilitated.
composing a message for said second user by said mobile user, said message including at least said second user's personal identifier in body of said message;
sending said message to a routing code assigned to an 'unlisted' function on said mobile device;
receiving said message at said instant messaging system;
capturing said second user's personal identifier by said instant messaging system;
assigning a routing code to said second users personal identifier; and sending said message to said second user; and optionally returning notice of said assignment to said mobile user, so that future messaging is facilitated.
3. The method of Claim 1, wherein said step of exchanging instant messages comprises the steps of sending a message to said mobile user by said second user;
receiving said message at said instant messaging system;
capturing said second user's personal identifier by said instant messaging system;
assigning a routing code to said second user's personal identifier; and sending said message to said mobile user.
receiving said message at said instant messaging system;
capturing said second user's personal identifier by said instant messaging system;
assigning a routing code to said second user's personal identifier; and sending said message to said mobile user.
4. The method of Claim 1, wherein said step of exchanging instant messages comprises the steps of:
receiving a message at said mobile unit from said second user, wherein said second user's personal identifier has previously been associated with a second routing code; and replying to said received message by said mobile user by means of an automated 'reply' function on said mobile unit.
receiving a message at said mobile unit from said second user, wherein said second user's personal identifier has previously been associated with a second routing code; and replying to said received message by said mobile user by means of an automated 'reply' function on said mobile unit.
5. The method of Claim 1, wherein assignment of a routing code to said second user persists for the duration of a user session.
6. The method of Claim 1, wherein routing codes for assignment to a second user are recycled during a user session if the number of second users exceeds the routing codes available for second users.
7. The method of Claim 6, further comprising the step of:
preventing occurrence of a condition wherein different second users are associated with the same routing code.
preventing occurrence of a condition wherein different second users are associated with the same routing code.
8. The method of Claim 7, wherein said step of preventing comprises any of the steps of:
delaying delivery of a message from said second user pending confirmation of said mobile user's interest in receiving said message; and providing sufficient routing codes that recycling of codes is unlikely to be necessary.
delaying delivery of a message from said second user pending confirmation of said mobile user's interest in receiving said message; and providing sufficient routing codes that recycling of codes is unlikely to be necessary.
9. A computer program product, said computer program product comprising a tangible medium with computer-readable code embodied thereon, said computer-readable code including code means for performing the steps of a method for facilitating instant messaging outside of a user-defined buddy group;
the method comprising the steps of:
providing a plurality of reserved routing codes for exchanging instant messages with users not included in said user-defined buddy group;
exchanging instant messages between a user of a mobile unit device and a second user, said second user not included in said mobile user's buddy group;
assigning one of said routing codes to a message directed to said second user by said mobile unit user; and temporarily assigning one of said routing codes to said second user's personal identifier so that said mobile user can easily reply to said second user without originating a new message.
the method comprising the steps of:
providing a plurality of reserved routing codes for exchanging instant messages with users not included in said user-defined buddy group;
exchanging instant messages between a user of a mobile unit device and a second user, said second user not included in said mobile user's buddy group;
assigning one of said routing codes to a message directed to said second user by said mobile unit user; and temporarily assigning one of said routing codes to said second user's personal identifier so that said mobile user can easily reply to said second user without originating a new message.
10. The computer program product of Claim 9, wherein said step of exchanging instant messages comprises the steps of composing a message for said second user by said mobile user, said message including said second user's personal identifier in body of said message;
sending said message to a routing code assigned to an 'unlisted' function on said mobile device;
receiving said message at said instant messaging system;
capturing said second user's personal identifier by said instant messaging system;
assigning a routing code to said second user's personal identifier;
sending said message to said second user; and optionally returning notice of said assignment to said mobile user, so that future messaging is facilitated.
sending said message to a routing code assigned to an 'unlisted' function on said mobile device;
receiving said message at said instant messaging system;
capturing said second user's personal identifier by said instant messaging system;
assigning a routing code to said second user's personal identifier;
sending said message to said second user; and optionally returning notice of said assignment to said mobile user, so that future messaging is facilitated.
11. The computer program product of Claim 9, wherein said step of exchanging instant messages comprises the steps of sending a message to said mobile user by said second user;
receiving said message at said instant messaging system;
capturing said second user's personal identifier by said instant messaging system;
assigning said a routing code to said second user's personal identifier;
and sending said message to said mobile user.
receiving said message at said instant messaging system;
capturing said second user's personal identifier by said instant messaging system;
assigning said a routing code to said second user's personal identifier;
and sending said message to said mobile user.
12. The computer program product of Claim 9, wherein said step of exchanging Instant messages comprises the steps of:
receiving a message at said mobile unit from said second user, wherein said second user's personal identifier has previously been associated with a routing code; and replying to said received message by said mobile user by means of an automated 'reply' function on said mobile unit.
receiving a message at said mobile unit from said second user, wherein said second user's personal identifier has previously been associated with a routing code; and replying to said received message by said mobile user by means of an automated 'reply' function on said mobile unit.
13. The computer program product of Claim 9, wherein assignment of a routing code to said second user persists for the duration of a user session.
14. The computer program product of Claim 9, wherein routing codes for assignment to a second user are recycled during a user session If the number of second users exceeds the available second routing codes.
15. The computer program product of Claim 9, said method further comprising the step of:
preventing occurrence of a condition wherein different second users are associated with the same routing code.
preventing occurrence of a condition wherein different second users are associated with the same routing code.
16. The computer program product of Claim 15, wherein said step of preventing comprises any of the steps of:
delaying delivery of a message from a second user pending confirmation of said mobile user's interest in receiving said message; and providing sufficient routing codes for assignment to said second user that recycling of codes Is unlikely to be necessary.
delaying delivery of a message from a second user pending confirmation of said mobile user's interest in receiving said message; and providing sufficient routing codes for assignment to said second user that recycling of codes Is unlikely to be necessary.
17. An apparatus for facilitating instant messaging outside of a user-defined buddy group comprising:
a plurality of reserved routing codes on a computer-readable medium for exchanging instant messages with users not included in said user-defined buddy group;
means for exchanging instant messages between a user of a mobile unit device and a second user, said second user not included in said mobile user's buddy group;
means for assigning one of said routing codes to a message directed to said second user by said mobile unit user, and means for temporarily assigning one of said routing codes to said second user's personal identifier so that said mobile user can easily reply to said second user without originating a new message.
a plurality of reserved routing codes on a computer-readable medium for exchanging instant messages with users not included in said user-defined buddy group;
means for exchanging instant messages between a user of a mobile unit device and a second user, said second user not included in said mobile user's buddy group;
means for assigning one of said routing codes to a message directed to said second user by said mobile unit user, and means for temporarily assigning one of said routing codes to said second user's personal identifier so that said mobile user can easily reply to said second user without originating a new message.
18. The apparatus of Claim 17, wherein said means for exchanging instant messages comprises means for:
composing a message for said second user by said mobile user, said message including said second user's personal identifier in body of said message;
sending said message to a routing code assigned to an 'unlisted' function on said mobile device;
receiving said message at said instant messaging system;
capturing said second user's personal identifier by said instant messaging system;
assigning a routing code to said second user's personal identifier;
sending said message to said second user; and optionally returning notice of said assignment to said mobile user, so that future messaging is facilitated.
composing a message for said second user by said mobile user, said message including said second user's personal identifier in body of said message;
sending said message to a routing code assigned to an 'unlisted' function on said mobile device;
receiving said message at said instant messaging system;
capturing said second user's personal identifier by said instant messaging system;
assigning a routing code to said second user's personal identifier;
sending said message to said second user; and optionally returning notice of said assignment to said mobile user, so that future messaging is facilitated.
19. The apparatus of Claim 17, wherein said means for exchanging instant messages comprises the means for:
sending a message to said mobile user by said second user;
receiving said message at said Instant messaging system;
capturing said second user's personal Identifier by said instant messaging system;
assigning a routing code to said second user's personal identifier, and sending said message to said mobile user.
sending a message to said mobile user by said second user;
receiving said message at said Instant messaging system;
capturing said second user's personal Identifier by said instant messaging system;
assigning a routing code to said second user's personal identifier, and sending said message to said mobile user.
20. The apparatus of Claim 17, wherein said means for exchanging instant messages comprises means for receiving a message at said mobile unit from said second user, wherein said second user's personal identifier has previously been associated with a routing code; and replying to said received message by said mobile user by means of an automated 'reply' function on said mobile unit.
21. The apparatus of Claim 17, wherein assignment of a routing code to said second user persists for the duration of a user session.
22. The apparatus of Claim 17, wherein routing codes for assignment to said second user are recycled during a user session if the number of second users exceeds the available second routing codes.
23. The apparatus of Claim 22, further comprising means for:
preventing occurrence of a condition wherein different second users are associated with the same routing code.
preventing occurrence of a condition wherein different second users are associated with the same routing code.
24. The apparatus of Claim 23, wherein said means for preventing comprises means for any of:
delaying delivery of a message from a second user pending confirmation of said mobile user's interest in receiving said message; and providing sufficient routing codes for assignment to said second users that recycling of codes Is unlikely to be necessary.
delaying delivery of a message from a second user pending confirmation of said mobile user's interest in receiving said message; and providing sufficient routing codes for assignment to said second users that recycling of codes Is unlikely to be necessary.
25. A method of facilitating messaging between a mobile device and a user, the method comprising steps of:
providing a plurality of reserved routing codes on a computer-readable medium for exchanging messages between users and mobile devices;
in response to receiving a message from the user directed to the mobile device, temporarily associating one of the routing codes with the user;
including the temporarily associated routing code in the message as a reply address; and transmitting the message with the included temporarily associated routing codes to the mobile device.
providing a plurality of reserved routing codes on a computer-readable medium for exchanging messages between users and mobile devices;
in response to receiving a message from the user directed to the mobile device, temporarily associating one of the routing codes with the user;
including the temporarily associated routing code in the message as a reply address; and transmitting the message with the included temporarily associated routing codes to the mobile device.
26. The method of claim 25, further comprising:
receiving a reply message from the mobile device directed to the temporarily associated routing code; and transmitting the reply message to the user.
receiving a reply message from the mobile device directed to the temporarily associated routing code; and transmitting the reply message to the user.
27. The method of claim 26, wherein said messages comprise instant messages.
28. The method of claim 26, wherein said step of temporarily associating one of the routing codes with the user comprises the steps of:
composing a message for the user at said mobile device, said message including at least said user's personal identifier in body of said message;
sending said message to a routing code assigned to an 'unlisted' function on said mobile device;
receiving said message at an Instant messaging system;
capturing said user's personal identifier by said instant messaging system;
assigning a routing code to said user's personal Identifier;
sending said message to said user; and optionally returning notice of said assignment to said mobile unit, so that future messaging Is facilitated.
composing a message for the user at said mobile device, said message including at least said user's personal identifier in body of said message;
sending said message to a routing code assigned to an 'unlisted' function on said mobile device;
receiving said message at an Instant messaging system;
capturing said user's personal identifier by said instant messaging system;
assigning a routing code to said user's personal Identifier;
sending said message to said user; and optionally returning notice of said assignment to said mobile unit, so that future messaging Is facilitated.
29. The method of claim 26, further comprising steps of:
sending a message to said mobile device by said user;
receiving said message at said instant messaging system;
capturing said user's personal identifier by an instant messaging system;
assigning a routing code to said user's personal identifier; and sending said message to said mobile device.
sending a message to said mobile device by said user;
receiving said message at said instant messaging system;
capturing said user's personal identifier by an instant messaging system;
assigning a routing code to said user's personal identifier; and sending said message to said mobile device.
30. The method of claim 26, wherein said step of transmitting the reply message to the user comprises steps of:
receiving a message at said mobile device from said user, wherein said user's personal identifier has previously been associated with a routing code;
and repiying to said received message by means of a 'reply' function on said mobile unit.
receiving a message at said mobile device from said user, wherein said user's personal identifier has previously been associated with a routing code;
and repiying to said received message by means of a 'reply' function on said mobile unit.
31. The method of daim 26, wherein assignment of a routing code to said user persists for the duration of a user session.
32. The method of claim 26, wherein routing codes for assignment are recycled during a user session if the number of users exceeds the routing codes available.
33. The method of claim 26, further comprising the step of:
preventing occurrence of a condition wherein different users are associated with the same routing code.
preventing occurrence of a condition wherein different users are associated with the same routing code.
34. The method of claim 33, wherein said step of preventing comprises any of the steps of:
delaying delivery of a message from said user pending confirmation of a mobile user's interest in receiving said message; and providing sufficient routing codes that recycling of codes is unlikely to be necessary.
delaying delivery of a message from said user pending confirmation of a mobile user's interest in receiving said message; and providing sufficient routing codes that recycling of codes is unlikely to be necessary.
35. A computer program product, said computer program product comprising a tangible medium with computer-readable code embodied thereon said computer-readable code including code means for performing the steps of a method of facilitating messaging between a mobile device and a user the method comprising the steps of:
providing a plurality of reserved routing codes for exchanging messages between users and mobile devices;
in response to receiving a message from the user directed to the mobile device, temporarily associating one of the routing codes with the user;
including the temporarily associated routing code in the message as a reply address; and transmitting the message with the included temporarily associated routing codes to the mobile device.
providing a plurality of reserved routing codes for exchanging messages between users and mobile devices;
in response to receiving a message from the user directed to the mobile device, temporarily associating one of the routing codes with the user;
including the temporarily associated routing code in the message as a reply address; and transmitting the message with the included temporarily associated routing codes to the mobile device.
36. The computer program product of claim 36, the method further comprising:
receiving a reply message from the mobile device directed to the temporarily associated routing code; and transmitting the reply message to the user.
receiving a reply message from the mobile device directed to the temporarily associated routing code; and transmitting the reply message to the user.
37. The computer program product of claim 36, wherein said messages comprise instant messages.
38. The computer program product of claim 36, wherein said step of exchanging messages comprises steps of:
composing a message for said user at said mobile device, said message including at least said user's personal identifier in body of said message;
sending said message to a routing code assigned to an 'unlisted' function on said mobile device;
receiving said message at an instant messaging system;
capturing said user's personal identifier by said Instant messaging system;
assigning a routing code to said user's personal identifier;
sending said message to said user; and optionally returning notice of said assignment to said mobile unit, so that future messaging is facilitated.
composing a message for said user at said mobile device, said message including at least said user's personal identifier in body of said message;
sending said message to a routing code assigned to an 'unlisted' function on said mobile device;
receiving said message at an instant messaging system;
capturing said user's personal identifier by said Instant messaging system;
assigning a routing code to said user's personal identifier;
sending said message to said user; and optionally returning notice of said assignment to said mobile unit, so that future messaging is facilitated.
39. The computer program product of claim 36, said method further comprising steps of:
sending a message to said mobile device by said user;
receiving said message at said instant messaging system;
capturing said user's personal identifier by an instant messaging system;
assigning a routing code to said user's personal identifier; and sending said message to said mobile unit.
sending a message to said mobile device by said user;
receiving said message at said instant messaging system;
capturing said user's personal identifier by an instant messaging system;
assigning a routing code to said user's personal identifier; and sending said message to said mobile unit.
40. The computer program product of claim 36, wherein said step of transmitting the reply message to the user comprises steps of:
receiving a message at said mobile unit from said user, wherein said user"s personal identifier has previously been associated with a routing code;
and replying to said received message by means of a 'reply' function on said mobile unit.
receiving a message at said mobile unit from said user, wherein said user"s personal identifier has previously been associated with a routing code;
and replying to said received message by means of a 'reply' function on said mobile unit.
41. The computer program product of claim 36, wherein assignment of a routing code to said user persists for the duration of a user session.
42. The computer program product of claim 36, wherein routing codes for assignment are recycled during a user session if the number of users exceeds the routing codes available.
43. The computer program product of claim 36, said method further comprising the step of:
preventing occurrence of a condition wherein different users are associated with the same routing code.
preventing occurrence of a condition wherein different users are associated with the same routing code.
44. The computer program product of claim 43, wherein said step of preventing comprises any of the steps of:
delaying delivery of a message from said user pending confirmation of a mobile user's interest in receiving said message; and providing sufficient routing codes that recycling of codes is unlikely to be necessary.
delaying delivery of a message from said user pending confirmation of a mobile user's interest in receiving said message; and providing sufficient routing codes that recycling of codes is unlikely to be necessary.
45. An apparatus for facilitating messaging between a mobile device and a user comprising:
a plurality of reserved routing codes on a computer-readable medium for exchanging messages between users and mobile devices;
in response to receiving a message from the user directed to the mobile device, temporarily associating one of the routing codes with the user;
means for including the temporarily associated routing code in the message as a reply address; and transmitting the message with the included temporarily associated routing codes to the mobile device.
a plurality of reserved routing codes on a computer-readable medium for exchanging messages between users and mobile devices;
in response to receiving a message from the user directed to the mobile device, temporarily associating one of the routing codes with the user;
means for including the temporarily associated routing code in the message as a reply address; and transmitting the message with the included temporarily associated routing codes to the mobile device.
46. The apparatus of daim 45, further comprising:
means for receiving a reply message from the mobile device directed to the temporarily associated routing code; and means for transmitting the reply message to the user.
means for receiving a reply message from the mobile device directed to the temporarily associated routing code; and means for transmitting the reply message to the user.
47. The apparatus of claim 46, wherein said messages comprise instant messages.
48. The apparatus of claim 46, wherein said means for temporarily associating the routing codes with the user comprises means for:
composing a message for said user at said mobile device, said message including said user's personal identifier in body of said message;
sending said message to a routing code assigned to an 'unlisted' function on said mobile device;
receiving said message at an instant messaging system;
capturing said user's personal identifier by said instant messaging system;
assigning a routing code to said user's personal identifier;
sending said message to said user; and optionally returning notice of said assignment to said mobile unit, so that future messaging is facilitated.
composing a message for said user at said mobile device, said message including said user's personal identifier in body of said message;
sending said message to a routing code assigned to an 'unlisted' function on said mobile device;
receiving said message at an instant messaging system;
capturing said user's personal identifier by said instant messaging system;
assigning a routing code to said user's personal identifier;
sending said message to said user; and optionally returning notice of said assignment to said mobile unit, so that future messaging is facilitated.
49. The apparatus of claim 46, wherein said means for exchanging messages comprises means for:
sending a message to said mobile device by said user, receiving said message at said Instant messaging system;
capturing said user's personal identifier by said instant messaging system;
assigning a routing code to said user's personal identifier; and sending said message to said mobile unit.
sending a message to said mobile device by said user, receiving said message at said Instant messaging system;
capturing said user's personal identifier by said instant messaging system;
assigning a routing code to said user's personal identifier; and sending said message to said mobile unit.
50. The apparatus of claim 46, wherein said means for transmitting the reply message to the user comprises means for:
receiving a message at said mobile unit from said user, wherein said users personal identifier has previously been associated with a routing code;
and replying to said received message user by means of a 'reply' function on said mobile unit.
receiving a message at said mobile unit from said user, wherein said users personal identifier has previously been associated with a routing code;
and replying to said received message user by means of a 'reply' function on said mobile unit.
51. The apparatus of daim 46, wherein assignment of a routing code to said user persists for the duration of a user session.
52. The apparatus of claim 46, wherein routing codes for assignment are recycled during a user session if the number of users exceeds the routing codes available.
53. The apparatus of claim 46, further comprising means for:
preventing occurrence of a condition wherein different users are associated with the same routing code.
preventing occurrence of a condition wherein different users are associated with the same routing code.
54. The apparatus of claim 53, wherein said means for preventing comprises means for any of:
delaying delivery of a message from a user pending confirmation of a mobile user's interest in receiving said message; and providing sufficient routing codes for assignment to said users that recycling of codes is unlikely to be necessary.
delaying delivery of a message from a user pending confirmation of a mobile user's interest in receiving said message; and providing sufficient routing codes for assignment to said users that recycling of codes is unlikely to be necessary.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US10/114,869 | 2002-04-01 | ||
| US10/114,869 US6760580B2 (en) | 2000-03-06 | 2002-04-01 | Facilitating instant messaging outside of user-defined buddy group in a wireless and non-wireless environment |
| PCT/US2003/009911 WO2003085996A1 (en) | 2002-04-01 | 2003-03-31 | Facilitating instant messaging outside of user-defined buddy group in a wireless and non-wireless environment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2479937A1 CA2479937A1 (en) | 2003-10-16 |
| CA2479937C true CA2479937C (en) | 2009-09-08 |
Family
ID=28789806
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002479937A Expired - Fee Related CA2479937C (en) | 2002-04-01 | 2003-03-31 | Facilitating instant messaging outside of user-defined buddy group in a wireless and non-wireless environment |
Country Status (8)
| Country | Link |
|---|---|
| US (2) | US6760580B2 (en) |
| EP (1) | EP1491061A4 (en) |
| JP (1) | JP3914921B2 (en) |
| CN (1) | CN1303829C (en) |
| AU (1) | AU2003218478A1 (en) |
| BR (1) | BRPI0308934A2 (en) |
| CA (1) | CA2479937C (en) |
| WO (1) | WO2003085996A1 (en) |
Families Citing this family (146)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7783508B2 (en) | 1999-09-20 | 2010-08-24 | Numerex Corp. | Method and system for refining vending operations based on wireless data |
| WO2001059569A2 (en) * | 2000-02-09 | 2001-08-16 | Apriva, Inc. | Communication systems, components, and methods with programmable wireless devices |
| US6714793B1 (en) | 2000-03-06 | 2004-03-30 | America Online, Inc. | Method and system for instant messaging across cellular networks and a public data network |
| US6760580B2 (en) * | 2000-03-06 | 2004-07-06 | America Online, Incorporated | Facilitating instant messaging outside of user-defined buddy group in a wireless and non-wireless environment |
| US7624172B1 (en) | 2000-03-17 | 2009-11-24 | Aol Llc | State change alerts mechanism |
| US9246975B2 (en) | 2000-03-17 | 2016-01-26 | Facebook, Inc. | State change alerts mechanism |
| US7146404B2 (en) * | 2000-08-22 | 2006-12-05 | Colloquis, Inc. | Method for performing authenticated access to a service on behalf of a user |
| US7290041B2 (en) * | 2000-08-28 | 2007-10-30 | Chikka Pte Ltd | Instant messaging system and method for remote networks using a sequential message handshaking protocol |
| US7245928B2 (en) | 2000-10-27 | 2007-07-17 | Cellemetry, Llc | Method and system for improved short message services |
| US7190956B2 (en) * | 2001-05-15 | 2007-03-13 | Motorola Inc. | Instant message proxy for circuit switched mobile environment |
| US20020174248A1 (en) * | 2001-05-16 | 2002-11-21 | Motorola, Inc. | Method and system for communicating chat and game messages in a wireless network |
| US7188143B2 (en) * | 2001-07-06 | 2007-03-06 | Yahoo! Inc. | Messenger-controlled applications in an instant messaging environment |
| US7133900B1 (en) * | 2001-07-06 | 2006-11-07 | Yahoo! Inc. | Sharing and implementing instant messaging environments |
| US7200590B2 (en) * | 2001-08-15 | 2007-04-03 | Yahoo! Inc. | Data sharing |
| US7120672B1 (en) | 2001-08-15 | 2006-10-10 | Yahoo! Inc. | Method and system for sharing information in an instant messaging environment |
| US20030046273A1 (en) * | 2001-08-28 | 2003-03-06 | Intel Corporation | Personal assistance service with instant messaging |
| US7349700B1 (en) | 2001-08-30 | 2008-03-25 | Aol Llc | Communication system and method |
| US7793334B2 (en) | 2001-11-16 | 2010-09-07 | At&T Mobility Ii Llc | System and method for password protecting a distribution list |
| US20030095555A1 (en) * | 2001-11-16 | 2003-05-22 | Mcnamara Justin | System for the validation and routing of messages |
| US8660537B2 (en) | 2001-11-16 | 2014-02-25 | At&T Mobility Ii Llc | System for the storage and retrieval of messages |
| US20030097406A1 (en) * | 2001-11-16 | 2003-05-22 | Ben Stafford | Method of exchanging messages |
| US7454195B2 (en) * | 2001-11-16 | 2008-11-18 | At&T Mobility Ii, Llc | System for the centralized storage of wireless customer information |
| US7657253B2 (en) * | 2001-11-16 | 2010-02-02 | At&T Mobility Ii Llc | System and method for providing message notification |
| US20030096605A1 (en) * | 2001-11-16 | 2003-05-22 | Schlieben Karl J. | System for handling proprietary files |
| AU2002349407A1 (en) * | 2001-12-05 | 2003-06-17 | Cybird Co., Ltd. | Communication information sharing system, communication information sharing method, communication information sharing program |
| US6718237B1 (en) * | 2002-03-28 | 2004-04-06 | Numerex Investment Corp. | Method for reducing capacity demands for conveying geographic location information over capacity constrained wireless systems |
| US20040103157A1 (en) * | 2002-04-17 | 2004-05-27 | Nokia Corporation | Store-and-forward server and method for storing and forwarding for instant messaging service implemented in IP multimedia core network subsystem (IMS) |
| US20030204741A1 (en) * | 2002-04-26 | 2003-10-30 | Isadore Schoen | Secure PKI proxy and method for instant messaging clients |
| US7321969B2 (en) * | 2002-04-26 | 2008-01-22 | Entrust Limited | Secure instant messaging system using instant messaging group policy certificates |
| US20030204722A1 (en) * | 2002-04-26 | 2003-10-30 | Isadore Schoen | Instant messaging apparatus and method with instant messaging secure policy certificates |
| US7016978B2 (en) * | 2002-04-29 | 2006-03-21 | Bellsouth Intellectual Property Corporation | Instant messaging architecture and system for interoperability and presence management |
| US6957077B2 (en) * | 2002-05-06 | 2005-10-18 | Microsoft Corporation | System and method for enabling instant messaging on a mobile device |
| PL373340A1 (en) * | 2002-06-28 | 2005-08-22 | T-Mobile Deutschland Gmbh | Method and arrangement for the treatment of short messages with directory number portability |
| US7640293B2 (en) * | 2002-07-17 | 2009-12-29 | Research In Motion Limited | Method, system and apparatus for messaging between wireless mobile terminals and networked computers |
| US8150922B2 (en) * | 2002-07-17 | 2012-04-03 | Research In Motion Limited | Voice and text group chat display management techniques for wireless mobile terminals |
| US7657598B2 (en) * | 2002-09-17 | 2010-02-02 | At&T Intellectual Property I, L.P. | Address book for integrating email and instant messaging (IM) |
| US7035942B2 (en) * | 2002-09-17 | 2006-04-25 | Bellsouth Intellectual Property Corp. | Server-based message protocol translation |
| US7921160B2 (en) * | 2002-09-17 | 2011-04-05 | At&T Intellectual Property I, L.P. | Initiating instant messaging (IM) chat sessions from email messages |
| WO2004027561A2 (en) * | 2002-09-17 | 2004-04-01 | Bellsouth Intellectual Property Corporation | Client-based message protocol translation |
| US7640306B2 (en) | 2002-11-18 | 2009-12-29 | Aol Llc | Reconfiguring an electronic message to effect an enhanced notification |
| US8965964B1 (en) | 2002-11-18 | 2015-02-24 | Facebook, Inc. | Managing forwarded electronic messages |
| US8122137B2 (en) | 2002-11-18 | 2012-02-21 | Aol Inc. | Dynamic location of a subordinate user |
| US8701014B1 (en) | 2002-11-18 | 2014-04-15 | Facebook, Inc. | Account linking |
| US7428580B2 (en) * | 2003-11-26 | 2008-09-23 | Aol Llc | Electronic message forwarding |
| US7899862B2 (en) | 2002-11-18 | 2011-03-01 | Aol Inc. | Dynamic identification of other users to an online user |
| US8005919B2 (en) | 2002-11-18 | 2011-08-23 | Aol Inc. | Host-based intelligent results related to a character stream |
| AU2003287671A1 (en) | 2002-11-18 | 2004-06-15 | America Online, Inc. | People lists |
| US7590696B1 (en) * | 2002-11-18 | 2009-09-15 | Aol Llc | Enhanced buddy list using mobile device identifiers |
| US7434169B2 (en) * | 2002-11-25 | 2008-10-07 | Aol Llc, A Delaware Limited Liability Company | Facilitating communications between computer users across a network |
| US7769811B2 (en) | 2003-03-03 | 2010-08-03 | Aol Llc | Instant messaging sound control |
| US7406501B2 (en) * | 2003-03-24 | 2008-07-29 | Yahoo! Inc. | System and method for instant messaging using an e-mail protocol |
| US20040210639A1 (en) | 2003-03-26 | 2004-10-21 | Roy Ben-Yoseph | Identifying and using identities deemed to be known to a user |
| US20040260698A1 (en) * | 2003-06-23 | 2004-12-23 | Macmillan Bruce Daniel | Method and apparatus for accessing information in a private database |
| US7653693B2 (en) | 2003-09-05 | 2010-01-26 | Aol Llc | Method and system for capturing instant messages |
| US20050050151A1 (en) * | 2003-08-29 | 2005-03-03 | Accenture Global Services Gmbh | Scalable instant messaging architecture |
| US20050085246A1 (en) * | 2003-10-16 | 2005-04-21 | Benco David S. | Network support for computerized event input and notification |
| US7451190B2 (en) * | 2003-11-26 | 2008-11-11 | Yahoo! Inc. | Associating multiple visibility profiles with a user of a real-time communication system |
| US20050114777A1 (en) * | 2003-11-26 | 2005-05-26 | Yahoo, Inc. | Calendar integration with instant messaging |
| US20050125496A1 (en) * | 2003-12-03 | 2005-06-09 | International Business Machines Corporation | Automatically initiating an instant messaging action when a subscriber's availability status changes |
| US20050125500A1 (en) * | 2003-12-08 | 2005-06-09 | Wu Winfred W. | Instant messenger(s) extension and system thereof |
| CN100413293C (en) * | 2003-12-24 | 2008-08-20 | 华为技术有限公司 | A method of automatic instant message reply |
| GB2409787B (en) * | 2003-12-29 | 2007-10-03 | Nokia Corp | A communications system |
| US7323970B1 (en) | 2004-01-21 | 2008-01-29 | Numerex Corporation | Method and system for remote interaction with a vehicle via wireless communication |
| US7675903B2 (en) | 2004-02-06 | 2010-03-09 | Alcatel Lucent | Dynamic contact list management system and method |
| US20050185634A1 (en) * | 2004-02-24 | 2005-08-25 | Benco David S. | Method and system for providing network support for messaging between short message service (SMS) subscribers and instant messaging (IM) subscribers |
| US20050204007A1 (en) * | 2004-03-12 | 2005-09-15 | International Business Machines Corporation | Apparatus method and system for automatically populating an interactive messaging contact list |
| US7672255B2 (en) * | 2004-04-05 | 2010-03-02 | Oomble, Inc. | Mobile instant messaging conferencing method and system |
| US7961663B2 (en) * | 2004-04-05 | 2011-06-14 | Daniel J. LIN | Peer-to-peer mobile instant messaging method and device |
| US7817606B2 (en) * | 2004-04-05 | 2010-10-19 | Daniel J. LIN | Method for establishing network connections between stationary terminals and remote devices through mobile devices |
| US7773550B2 (en) * | 2004-04-05 | 2010-08-10 | Daniel J. LIN | Peer-to-peer mobile data transfer method and device |
| US7764637B2 (en) * | 2004-04-05 | 2010-07-27 | Daniel J. LIN | Peer-to-peer mobile instant messaging method and device |
| US7607096B2 (en) * | 2004-05-01 | 2009-10-20 | Microsoft Corporation | System and method for a user interface directed to discovering and publishing presence information on a network |
| US7698307B2 (en) | 2004-05-01 | 2010-04-13 | Microsoft Corporation | System and method for synchronizing between a file system and presence of contacts on a network |
| US8239452B2 (en) * | 2004-05-01 | 2012-08-07 | Microsoft Corporation | System and method for discovering and publishing of presence information on a network |
| US7656870B2 (en) * | 2004-06-29 | 2010-02-02 | Damaka, Inc. | System and method for peer-to-peer hybrid communications |
| US7921163B1 (en) | 2004-07-02 | 2011-04-05 | Aol Inc. | Routing and displaying messages for multiple concurrent instant messaging sessions involving a single online identity |
| US20060026237A1 (en) * | 2004-07-30 | 2006-02-02 | Wang Richard G | Method and system for instant message using HTTP URL technology |
| US20060041848A1 (en) * | 2004-08-23 | 2006-02-23 | Luigi Lira | Overlaid display of messages in the user interface of instant messaging and other digital communication services |
| US7818379B1 (en) | 2004-08-31 | 2010-10-19 | Aol Inc. | Notification and disposition of multiple concurrent instant messaging sessions involving a single online identity |
| US7587482B2 (en) * | 2004-09-08 | 2009-09-08 | Yahoo! Inc. | Multimodal interface for mobile messaging |
| US7975009B2 (en) * | 2004-10-25 | 2011-07-05 | Aspect Software, Inc. | Instant message contact router |
| DE102004053597B4 (en) * | 2004-11-05 | 2008-05-29 | Infineon Technologies Ag | A method for automatically generating and / or controlling a telecommunications conference with a plurality of subscribers, telecommunication conference terminal and telecommunication conference server |
| US20060168204A1 (en) * | 2004-12-01 | 2006-07-27 | Barry Appelman | Mobile blocking indicators on a contact list |
| US7730143B1 (en) | 2004-12-01 | 2010-06-01 | Aol Inc. | Prohibiting mobile forwarding |
| US9002949B2 (en) | 2004-12-01 | 2015-04-07 | Google Inc. | Automatically enabling the forwarding of instant messages |
| US8060566B2 (en) | 2004-12-01 | 2011-11-15 | Aol Inc. | Automatically enabling the forwarding of instant messages |
| US7356567B2 (en) | 2004-12-30 | 2008-04-08 | Aol Llc, A Delaware Limited Liability Company | Managing instant messaging sessions on multiple devices |
| US7483899B2 (en) | 2005-01-11 | 2009-01-27 | International Business Machines Corporation | Conversation persistence in real-time collaboration system |
| US20060161631A1 (en) * | 2005-01-18 | 2006-07-20 | Luigi Lira | Revisions of already sent messages in an instant messaging communication |
| US7286820B2 (en) * | 2005-02-24 | 2007-10-23 | Research In Motion Limited | Handheld electronic device providing an alert when additional user action is required to initiate an outgoing phone call, and associated method |
| US20060212143A1 (en) * | 2005-03-01 | 2006-09-21 | Nguyen Dung H | Apparatus and methods for instant messaging feature for communication between users in multiple-user information handling system |
| US7664820B2 (en) * | 2005-03-15 | 2010-02-16 | International Business Machines Corporation | RFID wireless control of instant messaging |
| US8266207B2 (en) * | 2005-04-13 | 2012-09-11 | Dugan Casey A | Systems and methods for online information exchange using server-mediated communication routing |
| US20060277262A1 (en) * | 2005-06-06 | 2006-12-07 | Boss Gregory J | Session management enhancements for instant messaging applications |
| US20070005763A1 (en) * | 2005-07-01 | 2007-01-04 | Cisco Technology, Inc. | Method and system for using load information in an instant messaging system |
| US20070016484A1 (en) * | 2005-07-12 | 2007-01-18 | Waters Timothy M | Method for facilitating authorized online communication |
| US7519672B2 (en) * | 2005-07-14 | 2009-04-14 | International Business Machines Corporation | Active session queue management using contextual systems with an instant messaging proxy service |
| US8266219B2 (en) | 2005-07-20 | 2012-09-11 | Research In Motion Limited | Method and system for instant messaging conversation security |
| US20070050488A1 (en) * | 2005-09-01 | 2007-03-01 | Joyner Wilbert R Jr | Broadcast with private reply control in a real-time messaging system |
| KR100617677B1 (en) * | 2005-09-02 | 2006-08-28 | 삼성전자주식회사 | Method for processing the instant massage in wireless terminal |
| US20090144626A1 (en) * | 2005-10-11 | 2009-06-04 | Barry Appelman | Enabling and exercising control over selected sounds associated with incoming communications |
| US20070101009A1 (en) * | 2005-10-27 | 2007-05-03 | Yen-Fu Chen | Method and system for automatic/dynamic instant messaging location switch |
| KR100774933B1 (en) * | 2005-10-28 | 2007-11-09 | 엘지전자 주식회사 | Mobile Communication Terminal and Link Management Method |
| US8090082B2 (en) | 2006-01-23 | 2012-01-03 | Icall, Inc. | System, method and computer program product for extracting user profiles and habits based on speech recognition and calling history for telephone system advertising |
| US20070174405A1 (en) * | 2006-01-23 | 2007-07-26 | Yen-Fu Chen | Remote operation of instant messaging systems |
| US7962159B2 (en) * | 2006-04-25 | 2011-06-14 | International Business Machines Corporation | Method and system for receiving data on a portable device |
| US8327024B2 (en) * | 2006-04-29 | 2012-12-04 | 724 Solutions Software, Inc. | System and method for SMS/IP interoperability |
| WO2007127422A2 (en) * | 2006-04-29 | 2007-11-08 | 724 Solutions Software Inc. | Platform for interoperability |
| WO2007130312A2 (en) * | 2006-04-29 | 2007-11-15 | 724 Solutions Software Inc. | Channel selection/translation based on user-preference |
| US9252975B2 (en) | 2006-05-03 | 2016-02-02 | International Business Machines Corporation | Computer-implemented method, tool, and program product for automatically replying to an instant message |
| WO2007136723A2 (en) | 2006-05-17 | 2007-11-29 | Numerex Corp. | System and method for prolonging wireless data product's life |
| CA2658056A1 (en) * | 2006-07-13 | 2008-01-17 | Mobivox Corporation | Method and system for auto-login by calling line identification |
| US20080065758A1 (en) * | 2006-09-12 | 2008-03-13 | International Business Machines Corporation | Dynamic transient buddy and contact lists |
| US20080207233A1 (en) * | 2007-02-28 | 2008-08-28 | Waytena William L | Method and System For Centralized Storage of Media and for Communication of Such Media Activated By Real-Time Messaging |
| US20080096588A1 (en) * | 2006-10-19 | 2008-04-24 | Waytena William L | Telecommunication System |
| US20080096592A1 (en) * | 2006-10-19 | 2008-04-24 | Waytena William L | Systems and Methods for Providing Communications Services Using Assigned Codes |
| US8074172B2 (en) * | 2007-01-05 | 2011-12-06 | Apple Inc. | Method, system, and graphical user interface for providing word recommendations |
| KR101437711B1 (en) | 2007-01-31 | 2014-09-03 | 메르크 파텐트 게엠베하 | Chroman compounds for use as components in liquid-crystalline media, for example in electrooptical display elements |
| EP2118858A4 (en) | 2007-02-06 | 2010-03-31 | Numerex Corp | Service escrowed transportable wireless event reporting system |
| US9998956B2 (en) * | 2007-02-12 | 2018-06-12 | Sigram Schindler Beteiligungsgesellschaft Mbh | Managed handover process |
| WO2008124829A1 (en) * | 2007-04-10 | 2008-10-16 | Markettools, Inc. | Session management system and method for use with stateless messaging services |
| US8001249B2 (en) * | 2007-04-10 | 2011-08-16 | Markettools, Inc. | Session management system and method for use with stateless messaging services |
| US7970421B2 (en) * | 2007-04-10 | 2011-06-28 | Markettools, Inc. | Session management system and method for use with stateless messaging services |
| US8060568B2 (en) * | 2007-05-29 | 2011-11-15 | SAP Portal Israel Ltd. | Real time messaging framework hub to intercept and retransmit messages for a messaging facility |
| US20080301239A1 (en) * | 2007-05-31 | 2008-12-04 | Microsoft Corporation | Remote administration of devices and resources using an instant messenger service |
| US20090037595A1 (en) * | 2007-07-31 | 2009-02-05 | Sprint Communications Company L.P. | Selecting and applying a communication version |
| US8645970B1 (en) * | 2007-09-12 | 2014-02-04 | Sprint Communications Company, L.P. | Method to route notifications to designated responder |
| US8161106B2 (en) * | 2007-10-30 | 2012-04-17 | Microsoft Corporation | Supporting serendipitous group interaction based on user activities |
| US8232973B2 (en) | 2008-01-09 | 2012-07-31 | Apple Inc. | Method, device, and graphical user interface providing word recommendations for text input |
| US8762205B2 (en) * | 2008-01-17 | 2014-06-24 | International Business Machines Corporation | Method for delivering businesses enterprises advertising via instant messaging |
| US7831675B2 (en) * | 2008-01-17 | 2010-11-09 | International Business Machines Corporation | Method for interacting with infrastructure devices via instant messaging |
| US8200258B2 (en) * | 2008-09-15 | 2012-06-12 | Microsoft Corporation | System and methods for communication between instant message users and short message service users |
| US20100125580A1 (en) * | 2008-11-04 | 2010-05-20 | Westen Peter T | Automatic buddy management |
| US8630683B2 (en) * | 2008-11-24 | 2014-01-14 | Centurylink Intellectual Property Llc | System and method for displaying information associated with a cellular device on a user specified display unit |
| US20110055309A1 (en) * | 2009-08-30 | 2011-03-03 | David Gibor | Communication in Context of Content |
| US20120045049A1 (en) * | 2010-08-17 | 2012-02-23 | Avaya, Inc. | Self-organizing directory display |
| JP5861471B2 (en) * | 2012-01-25 | 2016-02-16 | 富士通株式会社 | Base station, communication system and communication method |
| EP2823662A4 (en) * | 2012-03-08 | 2016-12-21 | Empire Technology Dev Llc | Measuring quality of experience associated with a mobile device |
| US9092282B1 (en) | 2012-08-14 | 2015-07-28 | Sprint Communications Company L.P. | Channel optimization in a messaging-middleware environment |
| US9560595B2 (en) * | 2012-12-03 | 2017-01-31 | Broadcom Corporation | Dynamic operating bandwidth configuration for an envelope tracker |
| US9992021B1 (en) | 2013-03-14 | 2018-06-05 | GoTenna, Inc. | System and method for private and point-to-point communication between computing devices |
| US9264338B1 (en) | 2013-04-08 | 2016-02-16 | Sprint Communications Company L.P. | Detecting upset conditions in application instances |
| US9465985B2 (en) | 2013-06-09 | 2016-10-11 | Apple Inc. | Managing real-time handwriting recognition |
| US9554240B2 (en) * | 2015-03-30 | 2017-01-24 | Nxp Usa, Inc. | Multiple connection management for bluetooth low energy devices |
| DK179329B1 (en) | 2016-06-12 | 2018-05-07 | Apple Inc | Handwriting keyboard for monitors |
| CN110048862B (en) * | 2019-03-08 | 2021-07-09 | 北京三快在线科技有限公司 | Message display method and device and electronic equipment |
Family Cites Families (91)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5726984A (en) | 1989-01-31 | 1998-03-10 | Norand Corporation | Hierarchical data collection network supporting packetized voice communications among wireless terminals and telephones |
| US5025252A (en) * | 1989-11-03 | 1991-06-18 | Motorola, Inc. | Paging receiver with over-the-air characterization of call signal processing |
| ES2080302T3 (en) * | 1990-03-08 | 1996-02-01 | Ericsson Telefon Ab L M | DYNAMIC ALLOCATION OF THE ROAD NUMBER SYSTEM OF DEAMBULANTS AND BACKGROUND OF THE METHOD OF THE INVENTION. |
| FI94581C (en) | 1991-02-12 | 1995-09-25 | Nokia Telecommunications Oy | System for automatically communicating contact information in a mobile telephone network or the like |
| US5438611A (en) | 1991-05-20 | 1995-08-01 | Ntp Incorporated | Electronic mail system with RF communications to mobile processors originating from outside of the electronic mail system and method of operation thereof |
| US5436960A (en) | 1991-05-20 | 1995-07-25 | Campana, Jr.; Thomas J. | Electronic mail system with RF communications to mobile processors and method of operation thereof |
| US5479472A (en) | 1991-05-20 | 1995-12-26 | Ntp Incorporated | System for interconnecting electronic mail systems by RF communications and method of operation thereof |
| CA2145874C (en) | 1992-09-30 | 1999-09-21 | John Richard Kane | Electronic mail message delivery system |
| EP0658298A4 (en) * | 1993-07-06 | 1999-04-21 | Motorola Inc | Virtual pager for general purpose data terminal. |
| AU697210B2 (en) * | 1993-11-01 | 1998-10-01 | Telefonaktiebolaget Lm Ericsson (Publ) | A message transmission system and method for a radiocommunication system |
| US5812865A (en) | 1993-12-03 | 1998-09-22 | Xerox Corporation | Specifying and establishing communication data paths between particular media devices in multiple media device computing systems based on context of a user or users |
| SE9304119D0 (en) | 1993-12-10 | 1993-12-10 | Ericsson Ge Mobile Communicat | Devices and mobile stations for providing packaged data communication in digital TDMA cellular systems |
| US5793762A (en) | 1994-04-12 | 1998-08-11 | U S West Technologies, Inc. | System and method for providing packet data and voice services to mobile subscribers |
| US5561703A (en) | 1994-07-06 | 1996-10-01 | Rolm Company | System and method for integration of a paging server into a private branch exchange environment |
| US5568536A (en) | 1994-07-25 | 1996-10-22 | International Business Machines Corporation | Selective reconfiguration method and apparatus in a multiple application personal communications device |
| US5742905A (en) | 1994-09-19 | 1998-04-21 | Bell Communications Research, Inc. | Personal communications internetworking |
| DE69427404T2 (en) * | 1994-10-26 | 2001-11-08 | Ibm | Allocation method and apparatus for reusing network resources in a wireless communication system |
| US5579472A (en) | 1994-11-09 | 1996-11-26 | Novalink Technologies, Inc. | Group-oriented communications user interface |
| CA2139081C (en) | 1994-12-23 | 1999-02-02 | Alastair Gordon | Unified messaging system and method |
| US5557320A (en) | 1995-01-31 | 1996-09-17 | Krebs; Mark | Video mail delivery system |
| US5706211A (en) | 1995-03-02 | 1998-01-06 | Motorola, Inc. | Message communications system |
| US5604788A (en) | 1995-03-16 | 1997-02-18 | Motorola, Inc. | Wireless messaging system with electronic mail replication |
| JPH09134319A (en) | 1995-10-03 | 1997-05-20 | Sony Electron Inc | User interface for personal communication routing system and rule processing |
| FI112895B (en) * | 1996-02-23 | 2004-01-30 | Nokia Corp | A method for obtaining at least one user-specific identifier |
| US5697060A (en) * | 1996-03-25 | 1997-12-09 | Sony Corporation | Portable voice message terminal capable of transmitting pre-set text-based information |
| JP3781213B2 (en) * | 1996-06-20 | 2006-05-31 | ソニー株式会社 | E-mail system, computer apparatus and incoming call notification method |
| US5903726A (en) * | 1996-06-26 | 1999-05-11 | Mci Communications Corporation | System using portion of a short message payload to identify short message service types and delivering the message if user subscribes to the services |
| US5802466A (en) * | 1996-06-28 | 1998-09-01 | Mci Communications Corporation | Personal communication device voice mail notification apparatus and method |
| US5878397A (en) * | 1996-07-10 | 1999-03-02 | Telefonaktiebolaget L M Ericsson (Publ) | Method for transporting short messages in a wireless telecommunications system |
| US5970122A (en) | 1996-07-24 | 1999-10-19 | Lucent Technologies Inc. | Two-way wireless messaging system having user agent |
| US6014429A (en) | 1996-08-12 | 2000-01-11 | Lucent Technologies, Inc. | Two-way wireless messaging system with transaction server |
| US5960074A (en) * | 1996-09-23 | 1999-09-28 | Curtis Clark | Mobile tele-computer network for motion picture, television and tv advertising production |
| US5966663A (en) * | 1997-01-14 | 1999-10-12 | Ericsson Messaging Systems Inc. | Data communications protocol for facilitating communications between a message entry device and a messaging center |
| US5940496A (en) * | 1997-02-10 | 1999-08-17 | Gewesys Telecommunications Laboratories, Inc. | Apparatus and methods enhancing call routing within and between call-centers |
| FI104873B (en) | 1997-04-16 | 2000-04-14 | Nokia Networks Oy | Data service in a mobile network |
| US6212175B1 (en) * | 1997-04-22 | 2001-04-03 | Telxon Corporation | Method to sustain TCP connection |
| NZ330703A (en) * | 1997-06-17 | 2000-03-27 | Telecom Wireless Solutions Inc | Electronic mail system for interconnecting computer networks with digital mobile phone network |
| JPH1141643A (en) | 1997-07-04 | 1999-02-12 | Internatl Business Mach Corp <Ibm> | Radio information processing terminal and control method therefor |
| US5940379A (en) * | 1997-07-23 | 1999-08-17 | Motorola, Inc. | Apparatus and method for using multiple spreading codes for data transmission in a satellite communication system |
| US6115605A (en) * | 1997-08-29 | 2000-09-05 | Ppm, Inc. | Communication system and device using dynamic receiver addressing |
| US6169911B1 (en) | 1997-09-26 | 2001-01-02 | Sun Microsystems, Inc. | Graphical user interface for a portable telephone |
| US6512930B2 (en) * | 1997-12-30 | 2003-01-28 | Telefonaktiebolaget Lm Ericsson (Publ) | On-line notification in a mobile communications system |
| US6259911B1 (en) | 1998-01-06 | 2001-07-10 | Wireless Access | Network operations center hardware and software design |
| US6138158A (en) * | 1998-04-30 | 2000-10-24 | Phone.Com, Inc. | Method and system for pushing and pulling data using wideband and narrowband transport systems |
| US6243759B1 (en) * | 1998-05-08 | 2001-06-05 | International Business Machines Corporation | Method and system for configuring dynamic interfaces |
| WO2000005990A1 (en) | 1998-07-28 | 2000-02-10 | Samsonite Corporation | Softside luggage case having a single peripheral frame and two side-by-side compartments |
| US6212548B1 (en) * | 1998-07-30 | 2001-04-03 | At & T Corp | System and method for multiple asynchronous text chat conversations |
| JP3865946B2 (en) * | 1998-08-06 | 2007-01-10 | 富士通株式会社 | CHARACTER MESSAGE COMMUNICATION SYSTEM, CHARACTER MESSAGE COMMUNICATION DEVICE, CHARACTER MESSAGE COMMUNICATION SERVER, COMPUTER-READABLE RECORDING MEDIUM CONTAINING CHARACTER MESSAGE COMMUNICATION PROGRAM, COMPUTER-READABLE RECORDING MEDIUM RECORDING CHARACTER MESSAGE COMMUNICATION MANAGEMENT PROGRAM Message communication management method |
| US6192396B1 (en) | 1998-08-11 | 2001-02-20 | Canon Kabushiki Kaisha | Electronic mail with recipient-specific content |
| US6067529A (en) * | 1998-08-12 | 2000-05-23 | Ericsson Inc. | System and method for sending a short message containing purchase information to a destination terminal |
| US6256381B1 (en) * | 1998-10-30 | 2001-07-03 | Avaya Technology Corp. | System and method for identifying a data record associated with a transferred telephone call |
| US7239618B1 (en) | 1998-12-11 | 2007-07-03 | Lucent Technologies Inc. | Single phase local mobility scheme for wireless access to packet-based networks |
| US6801659B1 (en) | 1999-01-04 | 2004-10-05 | Zi Technology Corporation Ltd. | Text input system for ideographic and nonideographic languages |
| FI990049A (en) | 1999-01-13 | 2000-07-14 | Jaakko Olavi Pentikaeinen | Modular wireless network / concept |
| WO2000043892A1 (en) | 1999-01-21 | 2000-07-27 | Universal Music Group, Inc. | Method and system for transmitting media information through a network |
| US6301609B1 (en) * | 1999-07-07 | 2001-10-09 | Lucent Technologies Inc. | Assignable associate priorities for user-definable instant messaging buddy groups |
| KR20010021111A (en) | 1999-07-23 | 2001-03-15 | 스테븐 디.피터스 | Messaging and status indication for wireless communication devices |
| US6430604B1 (en) * | 1999-08-03 | 2002-08-06 | International Business Machines Corporation | Technique for enabling messaging systems to use alternative message delivery mechanisms |
| US6674767B1 (en) | 1999-10-04 | 2004-01-06 | Microsoft Corporation | Flexible system and method for communicating between a broad range of networks and devices |
| ES2237022T3 (en) | 1999-12-02 | 2005-07-16 | Sony International (Europe) Gmbh | INSTANT MESSAGING. |
| EP1104965B1 (en) | 1999-12-02 | 2007-02-28 | Sony Deutschland GmbH | Protocol for instant messaging |
| EP1104961A1 (en) | 1999-12-03 | 2001-06-06 | Hewlett-Packard Company, A Delaware Corporation | Deferral of transmissions in wireless local area network |
| WO2001041477A1 (en) | 1999-12-03 | 2001-06-07 | Arreo Communications Inc. | Instant messenger system and instant message transfer method using phone number as instant messenger address |
| FI109319B (en) * | 1999-12-03 | 2002-06-28 | Nokia Corp | Filtering of electronic information to be transmitted to a terminal |
| US7809382B2 (en) * | 2000-04-11 | 2010-10-05 | Telecommunication Systems, Inc. | Short message distribution center |
| CA2326294A1 (en) | 1999-12-30 | 2001-06-30 | At&T Corp. | Personal ip toll-free number |
| US6252952B1 (en) | 1999-12-30 | 2001-06-26 | At&T Corp | Personal user network (closed user network) PUN/CUN |
| CA2325670C (en) | 1999-12-30 | 2003-12-30 | At&T Corp. | Method for performing roaming amongst multiple ip networks |
| CA2326230C (en) | 1999-12-30 | 2008-04-29 | At&T Corp. | Integrated multimedia messaging service |
| US7120139B1 (en) | 1999-12-30 | 2006-10-10 | At&T Corp. | Broadband cable telephony network architecture IP ITN network architecture reference model |
| US7075918B1 (en) | 1999-12-30 | 2006-07-11 | At&T Corp. | BRG with PBX capabilities |
| CA2326070C (en) | 1999-12-30 | 2007-10-02 | At&T Corp. | Handheld integrated ip device |
| US6760754B1 (en) * | 2000-02-22 | 2004-07-06 | At&T Corp. | System, method and apparatus for communicating via sound messages and personal sound identifiers |
| US6760580B2 (en) * | 2000-03-06 | 2004-07-06 | America Online, Incorporated | Facilitating instant messaging outside of user-defined buddy group in a wireless and non-wireless environment |
| US6714793B1 (en) * | 2000-03-06 | 2004-03-30 | America Online, Inc. | Method and system for instant messaging across cellular networks and a public data network |
| AU2001240154A1 (en) | 2000-03-15 | 2001-09-24 | Telecommunication Systems, Inc. | Mobile originated internet relay chat |
| US7200634B2 (en) | 2000-05-10 | 2007-04-03 | Chikka Pte Ltd. | Instant messaging account system |
| US7218921B2 (en) | 2000-05-12 | 2007-05-15 | Chikka Pte Ltd | Method and system for inviting and creating accounts for prospective users of an instant messaging system |
| US7146404B2 (en) * | 2000-08-22 | 2006-12-05 | Colloquis, Inc. | Method for performing authenticated access to a service on behalf of a user |
| AU2000274681A1 (en) | 2000-08-28 | 2002-03-13 | Chikka.Com Pte Ltd | Instant messaging system and method for remote networks using a sequential message handshaking protocol |
| US6650890B1 (en) * | 2000-09-29 | 2003-11-18 | Postini, Inc. | Value-added electronic messaging services and transparent implementation thereof using intermediate server |
| US6917813B2 (en) * | 2001-05-31 | 2005-07-12 | Telefonaktiebolaget Lm Ericsson (Publ) | Provision of short message services |
| US6864809B2 (en) | 2002-02-28 | 2005-03-08 | Zi Technology Corporation Ltd | Korean language predictive mechanism for text entry by a user |
| US7016978B2 (en) * | 2002-04-29 | 2006-03-21 | Bellsouth Intellectual Property Corporation | Instant messaging architecture and system for interoperability and presence management |
| US7020849B1 (en) | 2002-05-31 | 2006-03-28 | Openwave Systems Inc. | Dynamic display for communication devices |
| JP5087273B2 (en) | 2003-06-18 | 2012-12-05 | ザイ コーポレイション オブ カナダ インコーポレイテッド | Configurable information identification system and method |
| EP1634153A2 (en) | 2003-06-18 | 2006-03-15 | ZI Corporation | Text entry system and method |
| WO2005008432A2 (en) * | 2003-07-11 | 2005-01-27 | Sonolink Communications Systems, Llc | System and method for advanced rule creation and management within an integrated virtual workspace |
| US7142642B2 (en) * | 2003-11-04 | 2006-11-28 | Mci, Llc | Systems and methods for facilitating communications involving hearing-impaired parties |
| WO2006026908A1 (en) | 2004-08-25 | 2006-03-16 | Dong Li | A chinese characters inputting method which uses continuous phonetic letters in a portable terminal |
| WO2006048759A1 (en) * | 2004-11-08 | 2006-05-11 | Nokia Corporation | Method enabling sessions and applications in instant messaging and presence serviced |
-
2002
- 2002-04-01 US US10/114,869 patent/US6760580B2/en not_active Expired - Lifetime
-
2003
- 2003-03-31 WO PCT/US2003/009911 patent/WO2003085996A1/en active Application Filing
- 2003-03-31 BR BRPI0308934A patent/BRPI0308934A2/en not_active IP Right Cessation
- 2003-03-31 JP JP2003583040A patent/JP3914921B2/en not_active Expired - Fee Related
- 2003-03-31 CA CA002479937A patent/CA2479937C/en not_active Expired - Fee Related
- 2003-03-31 EP EP03714482A patent/EP1491061A4/en not_active Withdrawn
- 2003-03-31 AU AU2003218478A patent/AU2003218478A1/en not_active Abandoned
- 2003-03-31 CN CNB038076942A patent/CN1303829C/en not_active Expired - Fee Related
-
2004
- 2004-02-04 US US10/773,064 patent/US8019363B2/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| JP2005522155A (en) | 2005-07-21 |
| JP3914921B2 (en) | 2007-05-16 |
| AU2003218478A1 (en) | 2003-10-20 |
| US20040157586A1 (en) | 2004-08-12 |
| US20020155826A1 (en) | 2002-10-24 |
| CN1303829C (en) | 2007-03-07 |
| WO2003085996A8 (en) | 2003-11-27 |
| CN1647554A (en) | 2005-07-27 |
| WO2003085996A1 (en) | 2003-10-16 |
| US6760580B2 (en) | 2004-07-06 |
| US8019363B2 (en) | 2011-09-13 |
| EP1491061A1 (en) | 2004-12-29 |
| EP1491061A4 (en) | 2009-01-07 |
| BRPI0308934A2 (en) | 2017-10-10 |
| CA2479937A1 (en) | 2003-10-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2479937C (en) | Facilitating instant messaging outside of user-defined buddy group in a wireless and non-wireless environment | |
| KR100693681B1 (en) | Facilitating instant messaging outside of user-defined buddy group in a wireless and non-wireless environment | |
| AU2001245497A1 (en) | Method and system for messaging across cellular networks and a public data network | |
| US7546117B2 (en) | Method and apparatus for blocking ID information associated with a sender of a short messaging service (SMS) message | |
| US8014757B1 (en) | System and method for anonymous exchange of multimedia content utilizing a wireless network | |
| CA2547294C (en) | Method and system for messaging across cellular networks and a public data network | |
| CN1652617A (en) | Facilitating instant messaging outside of user-defined buddy group in a wireless and non-wireless environment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKLA | Lapsed |