US20090082044A1 - Text messaging system and method - Google Patents
Text messaging system and method Download PDFInfo
- Publication number
- US20090082044A1 US20090082044A1 US12/149,951 US14995108A US2009082044A1 US 20090082044 A1 US20090082044 A1 US 20090082044A1 US 14995108 A US14995108 A US 14995108A US 2009082044 A1 US2009082044 A1 US 2009082044A1
- Authority
- US
- United States
- Prior art keywords
- status
- information terminal
- information
- text message
- text
- 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.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
-
- 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/21—Monitoring or handling of messages
- H04L51/214—Monitoring or handling of messages using selective forwarding
-
- 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/21—Monitoring or handling of messages
- H04L51/23—Reliability checks, e.g. acknowledgments or fault reporting
-
- 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
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/16—Communication-related supplementary services, e.g. call-transfer or call-hold
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
Definitions
- the present invention relates to a text messaging system for sending and receiving text messages among mobile terminals and information terminals connected via a network. More particularly, the present invention relates to a text messaging system for sending and receiving according to sender and receiver status text messages whose immediacy is strong, among multiple mobile terminals and information terminals connected to a computer network such as mobile a communication network or packet exchange network.
- Packet exchange networks mean networks for connecting personal computers (PC), workstations (WS), and PDAs (personal digital assistants); and the Internet, local area networks (LAN) and intranets can be cited as examples of packet exchange networks.
- Mobile terminals are not particularly limited as long as they can send and receive text information via a mobile communication network, and mobile phones, personal handyphone systems (PHS), car phones, and pocket beepers can be cited as examples of mobile terminals.
- Information terminals are not particularly limited as long as they can send and receive text information via a network, and PCs, WSs, and PDAs can be cited as examples of information terminals.
- FIG. 21 shows a conceptual structure of a conventional text messaging system using mobile phones, PHSs, and a center for relaying them.
- a mobile terminal A sends wirelessly to a text message center text messages addressed to a mobile terminal B ( 1 ).
- the center comprehends condition of each mobile terminal with a detection part of radio condition. If the mobile terminal B is receivable, the text message center transmits the text message to the mobile terminal B. If the mobile terminal B is unreceivable because it is out of the radio area, for example, the text message center stores the text message in the storage area ( 2 ). At the moment that the mobile terminal B becomes receivable the text message center transmits the text message ( 3 , 4 , 5 , 6 , 7 ). A part of the mobile terminals B may connect to the center and obtain the text message stored in the center. Furthermore, text messages may be transmitted from mobile terminal A to mobile terminal B directly, not via the center. In this case, if the destination terminal is out of the radio area or on the phone, text messages are not received.
- a setting that e-mail is forwarded to a designated address is previously made.
- e-mail is liaised with mobile terminals ( 9 ).
- sender, title, and importance level of e-mail are previously set.
- the center transmits text messages as e-mail ( 8 ).
- an e-mail server detects e-mail arrival and notifies a predetermined mobile terminal of incoming of mail with information such as a sender of the e-mail, the title, and the time.
- a monitor service of link state to the network As a means to detect other parties' statuses on a network, a monitor service of link state to the network, a busy condition management service of a service such as chat or electronic conference, an inventory management service, and a service computerized destination board are provided.
- a partner receiving text messages is connected to a network with a PC.
- receiving character messages on the PC instead of a mobile terminal is convenient for replying, enabling text messages to be immediately transmitted.
- Text messages of a mobile terminal are stored if the other party cannot receive them, but the sender cannot know that the messages are not immediately received. Under such circumstances, the sender cannot know if he/she needs to take another means or measure because the other party does not look at the sent text messages.
- an e-mail system can notify the sender a status that a sent e-mail did not reach the other party, for example.
- this system does not manage such dynamically-changing send result as the other party not having check the e-mail for certain time or the other party not having read it while he was using a network service.
- the present invention aims at providing technologies for sending and receiving text messages with mobile terminals such as mobile phones and PCs in real time according to the utilization status of dynamically-changing information terminals.
- a first aspect of the present invention provides a text messaging system comprising multiple information terminals having communication means, and a server connected to the above-mentioned information terminals via a communication line suitable to the above-mentioned communication means.
- the above-mentioned information terminals have send means, receive means, and status detection means.
- the send means sends to a server a text message addressed to another information terminal.
- the receive means receives from another information terminal the text message from another information terminal.
- the status detection means detects operational status including at least link state to the communication line and notifies the server of it.
- the server has receive means, send means, status administration means, and decision means.
- the receive means receives text messages from information terminals.
- the send means sends text messages received from information terminals to other information terminals.
- the status administration means retains operational statuses of information terminals notified from the status detection means for every users.
- the decision means determines send modes of text messages according to operational statuses of information terminals.
- a server comprehends operational statuses of information terminals because each information terminal reports operational status such as condition of connection to a communication line to the server. For example, assume that user A sends a text message from a PC on a communication line to another user B via a server. The server determines whether or not the PC of user B is connected to the communication line, and if it is connected, the server sends the text message to the PC of user B. If it is not connected to the communication line, the server transmits the text message to the mobile phone of user B.
- a second aspect of the present invention provides a text messaging system comprising one or more mobile terminals and information terminals respectively having communication means and a server connected to the above-mentioned mobile terminals and mobile information terminals via a communication line according to communication means.
- the information terminals have send means, receive means, and status detection means.
- the send means sends to the server text messages addressed to other mobile terminals or information terminals.
- the receive means receives from the server text messages sent from other mobile terminals or information terminals.
- the status detection means detects operational status including at least link state to the communication line and notifies the server of it.
- the server has receive means, send means, status administration means, and decision means.
- the receive means receives text messages from information terminals.
- the send means sends text messages received from mobile terminals or information terminals to other mobile terminals or information terminals.
- the status administration means retains operational statuses of information terminals notified from the status detection means for every users.
- the decision means determines send modes of text messages according to operational statuses of information terminals. PCs and WSs notify the server of at least the status of a link to a communication line and the server retains the notified status of the information terminal.
- a text message from a mobile terminal includes a telephone number of user B, ID, etc.
- the status administration means of the server obtains operational status of the user B's PC based on the information included in the text message.
- the decision means determines a send mode according to the present status of the PC if text messages can be sent to the user B's PC. Otherwise the decision means forwards the text message to the mobile terminal of user B.
- a third aspect of the present invention provides a text messaging system wherein the status detection means detects whether or not an information terminal is being used and notifies the server of it and the decision means determines the information terminal as a receiver of the text message if the information terminal is being used.
- the status detection means determines whether or not the information terminal is being used. The determination is performed by detecting operation of a mouse or a keyboard of the information terminal such as a PC or operational status of a screen saver. In this case, the decision means of the server sends a text message to the PC if the destination PC is being used. Otherwise a destination can be determined so that the text message is sent to a mobile terminal.
- a fourth aspect of the present invention provides a text messaging system wherein an information terminal further has service detection means which detects the operational status of a network application in the information terminal and notifies a server of it.
- the status administration means of the server retains the operational statuses of a notified network application, and if the network application can operate on the server, the decision means determines the sending of a text message with the network application when the network application is operating on the information terminal.
- the service detection means detects that a predetermined network application for utilizing WWW (World Wide Web), IRC (Internet Relay Chat), E-mail, etc. is started and notifies the server of it.
- the decision means determines the sending of a text message with a network application operating in a destination information terminal. For example, a text message is sent by e-mail if a destination PC is using an e-mail application or the text message is sent by chat if the destination PC is using a chat application.
- a fifth aspect of the present invention provides a text messaging system wherein the send means of an information terminal can notify a server that a text message was read, and the server further has reporting administration means which saves the text message sent to the information terminal and forwards the text message to the information terminal if that the text message was read is not notified.
- the receive means of a PC displays a received text message on the corner of the screen.
- the receive means determines that the text message is read and notifies the send means of it.
- the send means sends “already-read notification” to the receive means of the server.
- the sent text message, the sender, the name of the destination, etc. are notified reporting administration means from the decision means and the reporting administration means saves them.
- the saved text message is deleted when “already-read notification” is received from the information terminal.
- the saved text message is forwarded to a mobile terminal.
- a sixth aspect of the present invention provides a text messaging system wherein a reporting administration means forwards a text message sent to an information terminal according to the variation of the operational status of the information terminal.
- the status change of an information terminal is notified the reporting administration means from the status administration means. For example, if the notification of disconnection from a communication line is sent prior to “already-read notification”, the sent text message is forwarded to the mobile terminal.
- a seventh aspect of the present invention provides a text messaging system wherein if a text message sent to the information terminal is not read within a prescribed time period, the reporting administration means forwards the text message to the mobile terminal.
- the reporting administration means activates a timer when the sent text message is notified the reporting administration means from the decision means.
- the reporting administration means determines that the sent text message is not read in the information terminal if the text message is left after a prescribed time, and then sends the text message to the information terminal on the communication line.
- An eighth aspect of the present invention provides a text messaging system wherein the reporting administration means of the server notifies a text message sender that the text message is sent to a mobile terminal in a prescribed case.
- the reporting administration means notifies a text message sender that the text message is sent to a mobile terminal in a prescribed case.
- the prescribed case means a case that, for example, a text message was unable to be sent to an information terminal or a text message is not read in the information terminal.
- the prescribed case may include a case that, for example, a prescribed identifier is inserted into a text message. If a user needs the notification of a send result, he/she can hope for the notification by inserting an prescribed identifier into a text message to be sent.
- a ninth aspect of the present invention provides a text messaging system wherein the reporting administration means stores a text message and notifies the text message sender that the text message is stored if it cannot send the text message to a mobile terminal.
- a text message sent to a mobile terminal is stored in a server because the destination mobile terminal is out of the radio area or busy. If this is the case, the reporting administration means notifies the sending information terminal of it.
- a sending user can know if the text message is immediately transmitted. If the sending user requests the notification of a send result, he/she may add an identifier to a text message to be sent as described above.
- a tenth aspect of the present invention provides a text messaging system wherein the status detection means of an information terminal notifies a server of a phone number for contact, the status administration means of the server retains the notified phone number, and when a text message is sent from the information terminal to a mobile terminal, the decision means adds the phone number to a text message and sends it if the phone number of the sender for contact is set.
- the status detection means of the information terminal notifies the server of the phone number of the present whereabouts of a user.
- the status administration means of the server retains the notified phone number.
- the decision means refers to the status of a sending user when the destination of the text message from a PC such as a mobile terminal is selected. If the present phone number is set, the decision means adds the phone number to the text message as a callback phone number and sends it. If there is no present phone number, the decision means adds a default phone number of each user. This is convenient when a message receiver would like to inquire by phone instead of a character message.
- An eleventh aspect of the present invention provides a text messaging system further having a quasi information terminal connected to the communications line.
- the quasi information terminal has receive means, information acquisition means, send means, and information setting means.
- the receive means receives from a server a text message sent from a mobile terminal.
- the information acquisition means obtains the operational status of other information terminals according to received text messages.
- the send means sends the obtained operational status to the mobile terminal as a text message.
- the information setting means sets the operational status of other information terminals according to the received text message and notifies the server of it.
- user A sends a message that he/she would like to know the status of user B to a quasi information terminal from a mobile terminal.
- the quasi information terminal obtains the status of user B from the server.
- the obtained information is sent from the quasi information terminal to the mobile terminal of user A as a text message.
- User A sends the phone number of the whereabouts from the mobile terminal to the quasi information terminal as a text message.
- the quasi information terminal sends a text message that changes the present phone number of user A for contact.
- a twelfth aspect of the present invention provides a text messaging system comprising one or more mobile terminals and information terminals respectively having communication means, a primary server connected to the above-mentioned information terminal via a communication line according to the above-mentioned communication means, and a secondary server connected to the above-mentioned mobile terminal and information terminal via a communication line according to the above-mentioned communication means.
- the information terminal has send means, receive means, and status detection means.
- the send means sends to the secondary server a text message addressed to another mobile terminal or information terminal.
- the receive means receives from the secondary server a text message sent from another mobile terminal or information terminal.
- the status detection means detects at least the status of connection to a computer network and notifies the primary server of it.
- the primary server has a status administration means that collects the operational status of an information terminal from the information terminal and retains it for each user.
- the secondary server has receive means, send means, and decision means.
- the receive means receives a text message from a mobile terminal or an information terminal.
- the send means sends a text message received from a mobile terminal or information terminal to another mobile terminal or information terminal.
- the decision means obtains the operational status of an information terminal from the primary server and determines the send mode of a text message according to the obtained operational status.
- a thirteenth aspect of the present invention provides a text messaging system wherein an information terminal can further notify the secondary server that a text message was read and the secondary server further has a reporting administration means that forwards a text message to a mobile terminal if it is not notified that the text message was read.
- the fourteenth aspect of the present invention provides a text message communication device having send means, receive means, and status detection means which is an information terminal that has communication means and sends and receives text messages among mobile terminals or other information terminals via a communication line and a server according to the above-mentioned communication means.
- the send means sends to the server a text message addressed to another mobile terminal or information terminal.
- the receive means receives from the server a text message sent from another mobile terminal or information terminal.
- the status detection means detects an operational status including the status of connection to a communication network and notifies the server of it.
- a fifteenth aspect of the present invention provides a server for text message communication which is a server connected to one or more mobile terminals or information terminals having communication means via a communication network according to the above-mentioned communication means and has receive means, send means, status administration means, and decision means.
- the receive means receives a text message from a mobile terminal or information terminal.
- the send means sends a text message received from a mobile terminal or information terminal to another mobile terminal or information terminal.
- the status administration means receives an operational status from an information terminal and retains it for each user.
- the decision means determines a send mode of text message according to operational status of the information terminal.
- a sixteenth aspect of the present invention provides a computer-readable recording medium which stores a text message communication program used for information terminals having communication means that sends and receives text messages among mobile terminals or other information terminals via a communication line or a server according to the above-mentioned communication means and stores a program for executing steps A to C below:
- a seventeenth aspect of the present invention provides a computer-readable recording medium which stores a text message communication management program used for a server connected to one or more mobile terminals or information terminals respectively having communication means via a communication line according to the above-mentioned communication means and stores a text message management program for executing steps A to D below:
- An eighteenth aspect of the present invention provides a text message communication method which uses one or more mobile terminals or information terminals respectively having communication means and a server connected to the above-mentioned mobile terminals and information terminals via a communication line according to the above-mentioned communication means, comprising:
- a nineteenth aspect of the present invention provides a text message send/receive method which is used for information terminals that have communication means and send and receive text messages among mobile terminals or other information terminals via a communication line and a server according to the above-mentioned communication means, comprising:
- a twentieth aspect of the present invention provides a text message communication management method of a server connected to one or more mobile terminals or information terminals respectively having communication means via a communication line according to the above-mentioned communication means, comprising:
- FIG. 1 is a functional block diagram of a text messaging system according to the first embodiment of the present invention
- FIG. 2 is a conceptual explanatory diagram of data stored in a status-storing module
- FIG. 3 is a conceptual explanatory diagram of a message table in a reporting administration module
- FIG. 4 is a display example of a window for setting status
- FIG. 5 is a display example of a text message send window
- FIG. 6 is a display example of a text message receive window
- FIG. 7 is a display example of an e-mail text message receive window
- FIG. 8 is a display example of an IRC text message receive window
- FIG. 9 is a flowchart showing flow of an operational status notification process
- FIG. 10 is a flowchart showing flow of a connection status notification process
- FIG. 11 is a flowchart showing flow of a send process
- FIG. 12 is a flowchart showing flow of a receive process
- FIG. 13 is a flowchart showing process flow in a decision part
- FIG. 14 is a flowchart showing flow of a status administration process
- FIG. 15 is a flowchart showing flow of a reporting administration process
- FIG. 16 is a flowchart showing flow of a timeout process
- FIG. 17 is a flowchart showing flow of an operational status process
- FIG. 18 is a flowchart showing flow of another process
- FIG. 19 is a configuration of a text messaging system according to a second embodiment
- FIG. 20 is a configuration of a text messaging system according to a third embodiment.
- FIG. 21 is a conceptual configuration diagram of a conventional text messaging system using mobile terminals.
- FIG. 1 shows a functional block diagram of a text messaging system according to the first embodiment.
- the text messaging system according to the first embodiment consists of server 1 connected to Internet 2 and mobile communication network 4 , multiple PC clients 3 , and multiple mobile phones 5 A, 5 B, . . . on the mobile communication network 4 .
- server 1 is notified of a detected self status of each mobile phone such as “busy” or “out of radio area.”
- the server 1 has text message send part 6 , text message receive part 7 , status administration part 8 , status storage part 9 , decision part 10 , notification management part 11 , message storage part 12 , receive part 13 , send part 14 , and radio status detection part 15 .
- the text message send part 6 and text message receive part 7 send and receive a text message with the PC client 3 connected to the Internet 2 , and send and receive send result notification of a text message or already-read notification of a text message with the PC client 3 .
- the status administration part 8 receives operational status of the PC client from the PC client 3 and stores it in the status storage part 9 for each user.
- the operational status of the PC client is, for example, activation and completion of Internet applications, connection and disconnection of the Internet 2 , activation status of a screen saver, or PC in operation.
- the status administration part 8 receives stores prescribed information from the PC client 3 and stores it in the status storage part 9 for each user.
- the prescribed information is, for example, an e-mail address of each user, a nickname in IRC, a server and a channel, the phone number of a mobile phone, or present phone number.
- FIG. 2 shows an example of an operational status and a phone number of each PC client retained for each user by the status storage part 9 .
- the status storage part 9 retains only one active status for each user. For example, even if one user has multiple PC clients, a PC for which an up-to-date status is set according to the user's operation is valid. In FIG. 2 , if data are blank, it is determined that the status is null.
- a status of each PC client in FIG. 2 means the following:
- the decision part 10 When the server 1 receives a text message addressed to any of the users, the decision part 10 operates as follows. The decision part 10 refers to the operational status of a PC client of the relevant user and determines a send mode which can receive the text message in real time. At this time, if an Internet application is active on the PC client of the relevant user, the decision part 10 determines that the text message is sent with the Internet application. If a PC client of the relevant user does not exist, is not connected to the Internet, or is not used, the mobile phone of the relevant user is determined as the destination of the text message. If necessary, the text message is converted after the determination of a send mode, and the send request of the text message is done to the message send part 6 or send part 14 . The decision part 10 notifies the text message to be sent to the notification management part 11 to monitor the send result of the text message.
- the notification management part 11 retains the text message sent in response to the notification from the decision part 10 in a message table.
- the notification management part 11 also sends send notification to the sender if the status of the text message corresponds to a prescribed case.
- the prescribed case is such that the other party did not read the text message within a prescribed time, the text message was not read while the network application is active, the text message is not read while the PC is connected to the Internet 2 .
- FIG. 3 shows a conceptual diagram of the message table. In the message table shown in the figure, the name of a sender, the name of a receiver, the type of receiver, the timer ID, and the contents of the text message are retained.
- the message storage part 12 temporally stores the text message if the text message is not immediately sent to the mobile terminal 5 A, 5 B, etc.
- the receive part 13 and send part 14 are for sending and receiving the text message among mobile phones 5 A and 5 B.
- Radio status detection part 15 detects notification from the mobile phone 5 A or 5 B and stores the status of the mobile phone such as within radio area or busy.
- the PC client 3 has text message send/receive 21 , network service detection part 22 , PC operation detection part 23 , and status setting part 24 .
- the text message send/receive part 21 sends and receives the text message with the server 1 , notifies the user of the send result of the text message sent from the server 1 , and further notifies the server 1 that the received text message was read according to the input of the user.
- the text message send/receive part 21 may be an independent application or another Internet application for sending and receiving text messages can be substituted.
- An e-mail application or an IRC application is cited as an example of an application for sending and receiving text messages.
- the network service detection part 22 detects the activation and completion of a network application. Specifically, it detects the connection and disconnection of an webpage or the activation and completion of an e-mail or IRC application, and notifies the status setting part 24 of it each time the status changes. At the same time, it detects an e-mail address, a nickname used for IRC, a server, and a channel and notifies of them.
- the PC operation detection part 23 monitors a user status and notifies the status setting part 24 of it each time the status changes. Specifically, it monitors whether or not there is input by keyboard or mouse, the PC client 3 connects to or disconnects from a network by LAN or dial up, the screensaver is active, input by keyboard or mouse is done on the top window in multiwindow.
- the PC operation detection part 23 also sends “connection message” to the status administration part 8 of the server 1 at every definite period of time. If “connection message” does not come within a period of time, the status administration part 8 determines that the PC client 3 is disconnected from the Internet 2 .
- the status setting part 24 notifies the status administration part 8 of the server of the status of the PC client detected by the above-mentioned service detection part 22 and the PC operation detection part 23 .
- the status setting part 24 receives the mobile phone number of the user and the present phone number and notifies the status administration part 8 of the server 1 of them. Furthermore, the status setting part 24 obtains the operational status of the PC client of another user, destination, contact address, etc. from the server 1 and outputs them.
- FIG. 4 shows an example of a window for setting whereabouts of the user.
- the right side of the screen shown in the figure is a presence status setting window.
- This window is for writing presence status of the user (present, absent, away from seat, in council, in laboratory, etc.), his/her destination, phone number, brief schedule, etc.
- Input in the window by the user notifies the status administration part of the server 1 of a presence status.
- the presence status of another user obtained from the server 1 by the status setting part is displayed on a window on the left side in the figure.
- FIG. 5 shows an example of a message send window in the PC client 3 . Selecting the receiver of a text message on the above-mentioned left window in the figure opens the text message send window. With this, a brief message such as “hey, come on” or “call me” can be notified substantially in real time if the other party connects to the Internet 2 with a PC client. Furthermore, by checking the send result notification box, the result notification of a sent message can be asked for.
- FIG. 6 shows the receive window of text messages.
- the receive window is displayed in the corner of the screen without being displayed in front of the window being used.
- On the right side of the window there is a button for replying by call or text message. This button is for immediately replying to a received text message.
- the button on the right edge is for abandoning the text message without replying to it.
- the already-read message showing the text message was read is sent to the server 1 from the PC client 3 .
- the text message receive part 6 of the server 1 that received notification notifies the notification management part 11 of an already-read notification.
- FIG. 7 is a screen example when a text message is received while an e-mail application is being used.
- a message from user B indicated as to-be-read in FIG. 7 is a message send by the present invention.
- FIG. 8 is a screen example when a text message is received while the IRC application is being used. If these Internet application are being used, the mail becoming already-read or reply input to a chat is detected with the service detection part 22 of the PC client 3 and is notified the server 1 .
- step S 1 the above-mentioned network service detection part 22 and the PC operation detection part 23 monitor the operational status of the PC client 3 .
- step S 2 the service detection part 22 and the PC operation detection part 23 determine whether or not there is a change in the operational status. If there is a change, a new status is notified the status setting part 24 and step S 3 ensues. If there is no changes in the operational status, the process returns to step S 1 .
- step S 3 the status setting part 24 received the notification notifies the server 1 of a new operational status.
- information for identifying the user such as a user name or an IP address is added and notified, and the process returns to step S 1 to monitor occurrence of a new status change.
- steps S 1 to S 3 a process that the change of the operational status of the PC client is notified the server 1 is performed.
- the PC operation detection part 23 performs the connection status notification process shown in FIG. 10 in addition to the monitor and detection of the PC operation in the above-mentioned steps S 1 and S 2 and notifies the server 1 of the connection status.
- step S 21 the PC operation detection part 23 determines whether or not the PC client 3 is connected to the Internet 2 . If the result is “Yes”, step S 22 ensues. If the result is “No”, the process returns to step S 21 again and repeat the above-mentioned determination.
- step S 22 the PC operation detection part 23 sends the connection notification to the server 1 via the status setting part 24 .
- step S 23 the PC operation detection part 23 waits for the elapse of predetermined time T and if the time elapsed, the process returns to step S 21 and repeats the above-mentioned determination and connection notification.
- steps S 21 to S 23 while the PC client 3 is connecting to the Internet 2 , a process that the connection notification to the server 1 is performed every time the predetermined time T elapses.
- step S 31 the text message send/receive part 21 determines whether or not the other party a text message is sent to was selected. If the result is “Yes”, step S 32 ensues. Otherwise the process repeats the step and waits for the other party to be selected.
- step 32 the text message send/receive part 21 opens the text message send window in FIG. 5 and accepts the input of a text message to be sent.
- step S 33 the text message send/receive part 21 waits for the “Send” button to be pressed.
- the button is pressed, the input message is sent to the serve with the sender's name and the process returns to step S 31 .
- step S 41 the text message send/receive part 21 waits for a reception from the server 1 and if there is a reception, step S 42 ensues.
- step S 42 the text message send/receive part 21 determines whether or not the reception is a text message from another user. If the result is “Yes”, step S 43 ensues. Otherwise step S 50 , which will be descried below, ensues.
- step S 43 the text message send/receive part 21 opens the receive window exemplified in FIG. 6 , 7 , or 8 , notifies the user of the received text message part, and obtains a sender number included in the sent text message such as an IP address.
- step S 44 the text message send/receive part 21 determines whether or not the reply button was pressed. If the above-mentioned read-and-abandon button was pressed or the window was closed, step S 45 ensues. If the reply button was pressed, step S 46 ensues.
- step S 45 the text message send/receive part 21 sends a already-read notification that notifies the server that the text message was read.
- step S 46 the text message send/receive part 21 determines whether the pressed reply button is the button for call. If the button for call was pressed, the step S 47 ensues. If the reply button by text message was pressed, step S 48 ensues.
- step S 47 the text message send/receive part 21 dials the mobile-phone number of the other party or the phone number of current whereabouts that is notified with the text message.
- the receive wait state in step S 41 returns.
- step S 48 the text message send/receive part 21 opens the text message send window as shown in the above-mentioned FIG. 5 and accepts the input of a text message.
- the text message By the text message being input and the “Send” button being pressed in step S 49 , the inputted text message is sent.
- the destination of the text message to be sent is set to the sender of the text message that is previously obtained.
- step S 50 the text message send/receive part 21 determines whether or not the send result of the text message is received. If the reception is the send result, then step S 51 ensues, the send result notified from the server 1 is notified the user, and the receive wait state in step S 41 returns. For example, a send result “The message addressed to 020-222-222 was not read and forwarded to the mobile phone.” is displayed on the screen. If the reception is not the send result, step S 52 ensues.
- step S 52 the text message send/receive part 21 determines whether or not the reception is an already-read notification. If the reception is the already-read notification, step S 53 ensues and it is notified the user that the sent text message is read by the other party. For example, as the result display of the mail in FIG. 7 , the text message is displayed in catalogue and the relevant message part is displayed with half-tone dot meshing or a color. After that the receive wait state of step S 41 returns.
- the flow of the process performed by the server 1 is explained with a flowchart.
- the operational status of each PC client is shown in the above-mentioned FIG. 2 .
- the server 1 can support an e-mail or IRC application used by the PC client.
- a case that a text message is sent from the mobile phone 5 A of user A to the mobile phone of another user C is described as a example.
- step S 61 by the decision part 10 receiving from the receive part 13 of the server 1 a text message sent from the mobile phone 5 A of user A, the process is commenced.
- the text message includes the mobile phone number, contents of the text message, sender information, and the presence of the notification of the send result.
- the mobile phone number of user C is “020-444-4444”
- contents of the text message is “Returns to the office at 3 p.m.”
- the sender information is the mobile phone number of user A i.e. “020-444-4444.”
- the message receive part 7 of the server 1 receives the text message and notifies the decision part 10 of it.
- information for identifying the sender and receiver is a user's name or an IP address. If the text message is sent by e-mail, the information is an e-mail address; if the text message is sent by IRC, the information is a nickname.
- step S 62 the decision part 10 searches in the status storage part 9 with the received mobile phone number “020-444-4444” as a search key and obtains the status of user C. Similarly, the decision part 10 also obtains the status of the sender.
- step S 64 the decision part 10 determines whether or not the PC client of user B is connected to the Internet 2 .
- the IP address of user C is not empty, it is determined that the PC client is connected and step S 65 ensues. If it is not connected, the text message is sent to the send part 14 and step S 74 , which is described below, ensues.
- step S 65 it is determined whether or not the PC client 3 of user C is in operation. Namely, if a screensaver is active on the PC client of user C, it is assumed that user C is not in front of the PC and a mobile phone is selected as a destination. The received text message is stored in the message storage part 12 . Conversely, a screensaver is not active on the user C's PC in this example. Therefore the other party is assumed to be in front of the PC, the PC client of user C is selected as a destination, and step S 66 ensues.
- step S 66 the decision part 10 determines whether or not an Internet application of the PC client is active on the PC client 3 of user C. Specifically, by referring to FIG. 2 , it is understand that the e-mail address of user C is written and the e-mail is being used. In this case, step S 67 ensues. Conversely, if the Internet application is not active, step S 68 , which is described later, ensues.
- step S 67 the decision part 10 obtains a necessary parameter for sending the text message with an e-mail application such as an e-mail address from the status storage part 9 . At this moment the decision part 10 also obtains the name of user A.
- step S 68 the decision part 10 obtains a necessary parameter for directly sending the text message such as an IP address from the status storage part 9 . At this moment the decision part 10 also obtains the name of user A.
- step S 69 the decision part 10 notifies the text message send part 6 of the text message and the information obtained in step S 67 or S 68 and requests send.
- the text message is configured to an e-mail message by text message send part 6 and sent to the e-mail address of user C.
- the text message is displayed on an window shown in FIG. 7 .
- the e-mail message sent from the server is usually sent to a client via an e-mail server.
- step S 63 if it is determined that the PC client of user C is not active, step S 70 ensues.
- step S 70 the decision part 10 obtains a parameter which is necessary to send the text message to the mobile phone of user C such as a mobile phone number from the status storage part 9 .
- the decision part 10 also obtains the name of user A, which is a sender, the mobile phone number of user A, and the number of whereabouts. If it is determined there is no statuses and step S 70 ensues, the parameter of user C is not obtained. Consequently, the other party's phone number that were sent when the previous message was received “020-444-4444” is set to the other party's phone number and next step S 71 proceeds.
- step S 71 the decision part 10 passes the information obtained in the above-mentioned step S 70 to the send part 14 and requests radio transmission.
- step S 72 the decision part 10 determines whether or not the mobile phone of user C can notify the server 1 that the text message was read and the sender requests notification. If both is possible, step S 73 ensues. If the notification from the mobile phone is impossible, the process returns to step S 61 and waits for the reception of the text message.
- step S 73 the decision part 10 sends the sent text message, the sender's name, and send notification including a send terminal and a receive terminal to the notification management part 11 .
- step S 61 returns.
- the notification part 11 writes contents of the received send notification in the message table.
- step S 47 if it is determined that the PC client of user C is not connected to the Internet or the PC is not currently used, step S 47 ensues.
- step S 74 the decision part 10 determines whether or not sender A requests notification of a send result. If sender A requests the notification, then the above-mentioned step S 70 ensues and the notification to the mobile phone is sent.
- step S 75 the decision part 10 creates result notification addressed to the sender indicating that the text message is temporally stored in the message storage part 12 .
- step S 76 the decision part 10 determines send mode according to the status of sender A sends the result notification created in step S 74 . Namely, the decision part 10 sends the text message to the mobile phone because the PC client of receiver C is not connected to the Internet and notifies user A that a text message indicating it. The message is sent to the decision part 10 and transmitted to sender A in an appropriate way.
- FIG. 14 Flow of status administration process managing the operational status of the PC client in the server 1 is described next with a flowchart shown in FIG. 14 .
- step S 82 the status administration part 8 updates the contents of the status storage part 9 for each user based on the received contents.
- step S 83 the status administration part 8 further notifies the notification management part 11 of the change of the operational status.
- Reporting administration process performing notification to the sender from the server 1 is described below with a flowchart shown in FIG. 15 .
- the following four processes are performed: (i) main process, (ii) timeout process of stored text message, (iii) process of stored text message according to a receiver status, and (iv) process other than above.
- step S 91 in FIG. 15 receiving events such as message, timeout process, and status notification of user's activities commences the following process.
- step S 92 the notification management part 11 determines whether or not the received event is a text message. If the event is a text message, step S 93 ensues. Otherwise step S 100 , which will be described later, ensues.
- step S 93 the notification management part 11 determines whether or not the received text message is send notification notified from the decision part 10 in step S 37 in FIG. 13 . If the received text message is the send notification, step S 94 ensues. If the received text message is not the send notification, no process is performed and step S 91 returns.
- step S 94 the notification management part 11 activates a timer counting a prescribed time and manages the message table with timer ID.
- step S 95 the notification management part 11 writes timer ID in addition to contents of the text message included in the send notification, sender and receiver, and send/receive type. Then step S 95 ensues.
- step S 92 If it is determined in step S 92 that the text message is not send notification or is not an usual text message, then step S 100 ensues.
- step S 100 the notification management part 11 determines whether or not the received event is timeout notification. If the event is timeout notification, message timeout handling routine in step S 300 ensues. In the timeout handling routine, stored text messages that timed out are deleted. Timeout process is described later. If the received event is not timeout notification, step S 200 ensues.
- step S 200 the notification management part 11 determines whether or not the received event is notification of the operational status of a PC client. If the event is the notification of the operational status, step S 500 ensues and another handling routine is performed.
- the operational status handling routine in step S 400 and another operational routine in step S 500 are described later.
- step S 100 If it is determined in step S 100 that the event is timeout notification, the timeout handling routine in step S 300 ensues.
- FIG. 16 is a flowchart showing flow of the timeout handling routine.
- step S 301 the notification management part 11 determines whether or not the timed-out text message is left in the message table. If the text message is left, it is assumed that already-read notification from the receiver in a predetermined time and step S 302 ensues. If the text message is not left, the main routine in above-mentioned FIG. 15 returns.
- step S 302 the notification management part 11 determines whether or not the type of the receiver of the timed-out text message is a mobile phone. If the type is a mobile phone, step S 303 ensues; if the type is a PC client, step S 307 ensues.
- step S 303 the notification management part 11 determines whether or not the sender hopes for notification of send result of the text message. If the sender hopes for the notification, step S 304 ensues. If the sender does not hope for the notification, step S 306 ensues.
- step S 304 the notification management part 11 creates to-be-read result notification that indicates the sent text message was not read and step S 305 ensues.
- step S 305 the notification management part 11 notifies the decision part 10 of created to-be-read result notification.
- the decision part 10 selects appropriate send means and send method from the sender status and sends the to-be-read result notification to the sender.
- step S 306 the notification management part 11 deletes an entry of relevant text messages from the message table and the main routine in above-mentioned FIG. 15 returns.
- step S 303 to S 305 result notification indicating “the text message is sent to the mobile phone, but it was not read.” is sent to the sender.
- step S 302 if the receiver is determined as a PC client, step S 307 ensues.
- step S 307 the status administration part 11 determines whether or not the sender hopes for notification of send result. If the sender hopes for the notification, step S 308 ensues. If the sender does not hope for the notification, step S 315 ensues.
- step S 308 the notification management part 11 creates radio send result notification indicating the text message is sent to the mobile phone.
- step S 309 the notification management part 11 notifies the decision part 10 of the created radio send result notification.
- the decision part 10 that received the notification notifies the sender of the above-mentioned result notification in a send mode according to the operational status of the sender's PC client.
- step S 310 the notification management part 11 passes the text message to the send part 14 and deletes the entry of the relevant text message from the message table.
- step S 311 the notification management part 11 obtains necessary information such as the receiver's mobile phone number to send the text message to the mobile phone from the status storage part 9 .
- step S 312 the notification management part 11 notifies the send part 14 of send information and requests the transmission of text message.
- step S 313 the notification management part 11 determines whether or not it can be notified that the receiver's mobile phone read the text message. If it can be notified, the step S 314 ensues. Otherwise the main routine in above-mentioned FIG. 15 returns.
- step S 314 the notification management part 11 issues send notification including sender/receiver, send/receive type, etc. This send notification is written in the message table in the above-described step S 94 .
- step S 200 if the received event is determined as the change notification of the operational status of the PC client, step S 400 operational status handling routine shown in FIG. 17 ensues.
- FIG. 17 is a flowchart showing flow of the operational status handling routine.
- step S 401 the notification management part 11 determines whether or not the text message addressed to the PC client with the operational status changed is in the message table. If it is in the message table, step S 402 ensues. If not, the main routine returns.
- step S 402 the notification management part 11 determines whether or not the change of the status corresponds to “disconnection from the Internet” or “Screensaver active.” If it corresponds to either of the above two statuses, step S 403 ensues. If it is not corresponds to any of the above two statuses, step S 410 ensues.
- step S 403 the notification management part 11 determines whether or not the sender hopes for the send notification sent to the sender, and if the sender for it step S 404 ensues. If the sender does not hope for it step S 416 ensues.
- step S 404 the notification management part 11 creates radio send result notification and notifies the decision part of it, assuming that the a text message that was previously sent to the PC client. For example, Radio send result notification with a message “The message addressed to 020-222-222 was not read in the PC and was sent to the mobile phone.” is created.
- the decision part determines a send mode according to the status of the sender and requests it to be sent from the text message send part 6 or the send part 14 .
- step S 405 the notification management part 11 passes the text message to the send part 14 and deletes the entry of the relevant text message from the message table.
- step S 406 the notification management part 11 obtains necessary information such as a mobile phone number to send it to the mobile phone from the status storage part 9 .
- step S 407 the notification management part 11 sends the obtained send information to the send part 14 and requests sending.
- step S 408 the notification management part 11 determines whether or not that the receiver's mobile phone read can be notified. If it is possible, step S 409 ensues. Otherwise the main routine in FIG. 10 returns.
- step S 409 the notification management part 11 creates send notification including the sent text message, sender/receiver, and send/receive type, etc. This send notification is written in the message table in step S 94 of the above-mentioned main routine.
- step S 410 ensues.
- step S 410 the notification management part 11 determines whether or not the notified status change is completion notification of an Internet application that is already sent. If it is completion notification, step S 411 ensues; otherwise the main routine in FIG. 15 ensues.
- step S 411 the notification management part 11 obtains send information necessary to send to PC client such as an IP address by referring to the status storage part 9 .
- step S 412 the notification management part 11 passes the send part 14 an obtained send message or text message and requests sending.
- step S 413 the notification management part 11 deletes the relevant text message from the message table.
- step S 414 the notification management part 11 determines whether or not the sender hopes for the notification of the send result. If the user hopes for the notification, step S 415 ensues. If not, the main routine indicated in FIG. 15 ensues.
- step S 415 the notification management part 11 creates a PC send result notification and notifies the decision part 10 of it, assuming that a text message previously sent to an Internet application of the PC client was not read. For example, a PC send result notification with a content “a text message addressed to channel #CA was not read and was sent to PC” is created.
- the decision part 10 selects a send means and send method according to the sender's status and requests sending from the text message send part 6 .
- step S 416 the notification management part 11 obtains information necessary to send to the mobile phone such as the mobile phone number from the status storage part 9 .
- step S 417 the notification management part 11 passes the obtained information to the send part 14 and requests sending.
- step S 200 if it is determined that the received event is not a change notification of the operational status, another handling routine in step S 500 ensues.
- FIG. 18 is a flowchart showing flow of another handling routine.
- the notification management part 11 determines whether or not the received event is text message acquisition notification from the receiver. For example, if acquisition notification from a PC client or mobile terminal that received a text message is received by the text message receive part 7 or the receive part 13 , the acquisition notification is sent to the notification management part 11 . There may also be the case in which reply to an e-mail message or a confirmation command sent in the same channel of IRC may be detected by the text message receive part 7 and the acquisition notification 11 is sent to the notification management part 11 . If the received event is acquisition notification, step S 502 ensues; otherwise a below-described step S 503 ensues.
- step S 502 the notification management part 11 deletes the entry of the relevant text message from the message table and the main routine in FIG. 15 returns.
- step S 503 the notification management part 11 determines whether or not the received event is notification indicating a text message to the mobile phone is stored. If it is the notification, step S 504 ensues. Otherwise the main routine in FIG. 15 returns. That is to say, if a text message is stored in the message storage part 12 , storage notification is sent to the notification management part 11 from the send part 14 .
- step S 504 the notification management part 11 determines whether or not the sender hopes for the notification of a send result. If the sender hopes for the notification, step S 505 ensues. If not, the main routine in FIG. 15 ensues.
- step S 505 the notification management part 11 creates storage result notification indicating a text message is stored.
- the decision part 10 determines a send mode according to a sender's status and requests sending of storage result notification from the send part 6 or the send part 14 .
- time to be timed out or notification setting when a text message is not read immediately may be set for the server from a mobile phone or a PC client via the Internet.
- the setting can also be performed with a text message in a prescribed format.
- a mobile terminal can obtain arbitrary information by sending a text message in a prescribed format from the mobile terminal with the text messaging system shown in the above-mentioned first embodiment.
- FIG. 19 shows a configuration diagram of a text messaging system that changes or refers to the operational status of a PC client managed by the server 1 .
- information server 30 is used as a PC client.
- the mobile terminal 5 sends a text message in a format for sending the text message to the PC client.
- the information server 30 pretends to be the PC client and sets an operational status form the server 1 .
- a destination or schedule information is sent from a mobile terminal 5 to a phone number of the information server 30 as a text message in a prescribed format.
- the server 1 sends the text message to the information server 30 .
- the information setting part 26 of the information server 30 that received the text message analyzes the received text message, and notifies the status administration part 8 of information that changes the operational status of the sender.
- the information setting part 26 sends a text message indicating that the destination of another user needs to be known with a phone number of the other user. Then the server 1 sends the text message to the information server 30 .
- the information acquisition part 25 of the information server 30 analyzes the received text message and obtains the operational status of the other PC client with the phone number as a search key.
- the obtained information is sent as a text message from the information server to the number of the sender mobile terminal. Accordingly, for example, current whereabouts of another user can be identified and a call can be made to him/her.
- the radio server 1 b may be made to have the message storage part 12 and radio status detection part 15 by installing a radio sever 1 b independent of a text message server 1 a .
- the receive part 13 a and 13 b and the send part 14 a and 14 b are respectively installed in the text message server 1 a and the radio server 1 b .
- the status administration server 1 c may also be made to have the status administration part 8 and decision part 9 by further installing an independent status administration server 1 .
- a where-to-call number may be sent with a text message so that the other party can immediately call back when the text message is sent from a PC client or a mobile phone.
- a receiver can call the number and talk to the other party as soon as he receives the text message.
- the decision part 10 refers to the sender's status as well as the receiver's status. If the number of current whereabouts is set in the status storage part 12 , the decision part 10 sends the phone number as a callback number with the text message. If the number of current whereabouts is not set, the mobile phone number may be sent with the text message as a callback number.
- a single mobile communication network and a single Internet are respectively shown. However, they may be multiple. Since the status administration part of the server 1 holds only one active status per user, if the number of networks increases, it can be supported.
- Use of this invention allows a text message to be sent in a send mode according to the other party's status and to be sent and received substantially in real time.
- the text message can be notified in another send mode.
- the sender can know which send mode is used in which the text message was sent and thus communications with texts can be smoothly performed in real time.
Abstract
A text messaging device including a transmitter having different transmission modes for transmitting text messages, which are addressed to mobile terminals or to other information, to a server. The text messaging device includes a receiver for receiving from the server text messages from the mobile terminals or from the other information terminals. The text messaging device also includes a detector for detecting and reporting to the server an operational status of the transmitter including a change of status of a connection with communication lines.
Description
- This is a continuation of Ser. No. 09/772,000 filed Jan. 30, 2001 now pending, which is a continuation of International Application PCT/JP99/02353 filed Apr. 30, 1999 now pending, the disclosures of which are incorporated herein by reference. This application also claims the benefit of Japanese application No. 10-222655, filed Jun. 8, 1998, whose priority is claimed under 35 U.S.C. §119, the disclosure of which is incorporated herein by reference.
- 1. Field
- The present invention relates to a text messaging system for sending and receiving text messages among mobile terminals and information terminals connected via a network. More particularly, the present invention relates to a text messaging system for sending and receiving according to sender and receiver status text messages whose immediacy is strong, among multiple mobile terminals and information terminals connected to a computer network such as mobile a communication network or packet exchange network.
- In the present invention, “packet exchange networks” mean networks for connecting personal computers (PC), workstations (WS), and PDAs (personal digital assistants); and the Internet, local area networks (LAN) and intranets can be cited as examples of packet exchange networks.
- Mobile terminals are not particularly limited as long as they can send and receive text information via a mobile communication network, and mobile phones, personal handyphone systems (PHS), car phones, and pocket beepers can be cited as examples of mobile terminals. Information terminals are not particularly limited as long as they can send and receive text information via a network, and PCs, WSs, and PDAs can be cited as examples of information terminals.
-
FIG. 21 shows a conceptual structure of a conventional text messaging system using mobile phones, PHSs, and a center for relaying them. - A mobile terminal A sends wirelessly to a text message center text messages addressed to a mobile terminal B (1). The center comprehends condition of each mobile terminal with a detection part of radio condition. If the mobile terminal B is receivable, the text message center transmits the text message to the mobile terminal B. If the mobile terminal B is unreceivable because it is out of the radio area, for example, the text message center stores the text message in the storage area (2). At the moment that the mobile terminal B becomes receivable the text message center transmits the text message (3, 4, 5, 6, 7). A part of the mobile terminals B may connect to the center and obtain the text message stored in the center. Furthermore, text messages may be transmitted from mobile terminal A to mobile terminal B directly, not via the center. In this case, if the destination terminal is out of the radio area or on the phone, text messages are not received.
- In the above-mentioned system in
FIG. 21 , a setting that e-mail is forwarded to a designated address is previously made. By storing in the center e-mail reached the designated address as a text message to a mobile terminal, e-mail is liaised with mobile terminals (9). There is also a system in which sender, title, and importance level of e-mail are previously set. When e-mail corresponding to forwarding conditions reaches the center, the e-mail is forwarded to a mobile terminal. Conversely, there is a system that when an e-mail address is inputted on the destination in a mobile terminal, the center transmits text messages as e-mail (8). - There already exists a system other than those above that an e-mail server detects e-mail arrival and notifies a predetermined mobile terminal of incoming of mail with information such as a sender of the e-mail, the title, and the time.
- Meanwhile, as a means to detect other parties' statuses on a network, a monitor service of link state to the network, a busy condition management service of a service such as chat or electronic conference, an inventory management service, and a service computerized destination board are provided.
- However, in a conventional text messaging system, text messages from mobile terminals are forwarded to e-mail only if such a setting is made. Receive messages cannot be received on a mobile terminal unless the setting once made is canceled. Furthermore, these setting and canceling are very troublesome. Receivers selectively use a send method of text messages such as e-mail and transfer to a mobile terminal regardless of the other party's status. On this account, selecting or switching a send mode according to the other party's status, which dynamically changes, is not performed.
- For example, assume that a partner receiving text messages is connected to a network with a PC. In this case, receiving character messages on the PC instead of a mobile terminal is convenient for replying, enabling text messages to be immediately transmitted. Text messages of a mobile terminal are stored if the other party cannot receive them, but the sender cannot know that the messages are not immediately received. Under such circumstances, the sender cannot know if he/she needs to take another means or measure because the other party does not look at the sent text messages.
- Since liaison of text message communication between mobile terminals and PCs are limited, it is difficult to freely transmit text messages to an information terminal currently used by the other party with a network application currently used by the other party. On this account, a user cannot communicate according to the other party's status and it is inconvenient for the user even if he/she know that the other party is connected to a network or network service in a place away from home.
- Furthermore, an e-mail system can notify the sender a status that a sent e-mail did not reach the other party, for example. However, this system does not manage such dynamically-changing send result as the other party not having check the e-mail for certain time or the other party not having read it while he was using a network service.
- Additional aspects and/or advantages will be set forth in part in the description which follows and, in part, will be apparent from the description, or may be learned by practice of the invention.
- The present invention aims at providing technologies for sending and receiving text messages with mobile terminals such as mobile phones and PCs in real time according to the utilization status of dynamically-changing information terminals.
- A first aspect of the present invention provides a text messaging system comprising multiple information terminals having communication means, and a server connected to the above-mentioned information terminals via a communication line suitable to the above-mentioned communication means. The above-mentioned information terminals have send means, receive means, and status detection means. The send means sends to a server a text message addressed to another information terminal. The receive means receives from another information terminal the text message from another information terminal. The status detection means detects operational status including at least link state to the communication line and notifies the server of it.
- The server has receive means, send means, status administration means, and decision means. The receive means receives text messages from information terminals. The send means sends text messages received from information terminals to other information terminals. The status administration means retains operational statuses of information terminals notified from the status detection means for every users. The decision means determines send modes of text messages according to operational statuses of information terminals.
- Mobile communication networks, call switching networks such as PSTN (public switched telephone network), and packet switched networks can be cited as communication lines. A server comprehends operational statuses of information terminals because each information terminal reports operational status such as condition of connection to a communication line to the server. For example, assume that user A sends a text message from a PC on a communication line to another user B via a server. The server determines whether or not the PC of user B is connected to the communication line, and if it is connected, the server sends the text message to the PC of user B. If it is not connected to the communication line, the server transmits the text message to the mobile phone of user B.
- A second aspect of the present invention provides a text messaging system comprising one or more mobile terminals and information terminals respectively having communication means and a server connected to the above-mentioned mobile terminals and mobile information terminals via a communication line according to communication means.
- The information terminals have send means, receive means, and status detection means. The send means sends to the server text messages addressed to other mobile terminals or information terminals. The receive means receives from the server text messages sent from other mobile terminals or information terminals. The status detection means detects operational status including at least link state to the communication line and notifies the server of it.
- The server has receive means, send means, status administration means, and decision means. The receive means receives text messages from information terminals. The send means sends text messages received from mobile terminals or information terminals to other mobile terminals or information terminals. The status administration means retains operational statuses of information terminals notified from the status detection means for every users. The decision means determines send modes of text messages according to operational statuses of information terminals. PCs and WSs notify the server of at least the status of a link to a communication line and the server retains the notified status of the information terminal. When user A sends a text message to other user B via the server, information that user B is identified by is included in the text message to be sent. Specifically, a text message from a mobile terminal includes a telephone number of user B, ID, etc. The status administration means of the server obtains operational status of the user B's PC based on the information included in the text message. The decision means determines a send mode according to the present status of the PC if text messages can be sent to the user B's PC. Otherwise the decision means forwards the text message to the mobile terminal of user B.
- A third aspect of the present invention provides a text messaging system wherein the status detection means detects whether or not an information terminal is being used and notifies the server of it and the decision means determines the information terminal as a receiver of the text message if the information terminal is being used.
- In other words, the status detection means determines whether or not the information terminal is being used. The determination is performed by detecting operation of a mouse or a keyboard of the information terminal such as a PC or operational status of a screen saver. In this case, the decision means of the server sends a text message to the PC if the destination PC is being used. Otherwise a destination can be determined so that the text message is sent to a mobile terminal.
- A fourth aspect of the present invention provides a text messaging system wherein an information terminal further has service detection means which detects the operational status of a network application in the information terminal and notifies a server of it. In this system, the status administration means of the server retains the operational statuses of a notified network application, and if the network application can operate on the server, the decision means determines the sending of a text message with the network application when the network application is operating on the information terminal.
- The service detection means detects that a predetermined network application for utilizing WWW (World Wide Web), IRC (Internet Relay Chat), E-mail, etc. is started and notifies the server of it. On the server side, the decision means determines the sending of a text message with a network application operating in a destination information terminal. For example, a text message is sent by e-mail if a destination PC is using an e-mail application or the text message is sent by chat if the destination PC is using a chat application.
- A fifth aspect of the present invention provides a text messaging system wherein the send means of an information terminal can notify a server that a text message was read, and the server further has reporting administration means which saves the text message sent to the information terminal and forwards the text message to the information terminal if that the text message was read is not notified.
- For example, the receive means of a PC displays a received text message on the corner of the screen. When the displayed message is deleted, the receive means determines that the text message is read and notifies the send means of it. The send means sends “already-read notification” to the receive means of the server. Meanwhile, the sent text message, the sender, the name of the destination, etc. are notified reporting administration means from the decision means and the reporting administration means saves them. The saved text message is deleted when “already-read notification” is received from the information terminal. However, as for a text message for which “already-read notification” is not notified, the saved text message is forwarded to a mobile terminal.
- A sixth aspect of the present invention provides a text messaging system wherein a reporting administration means forwards a text message sent to an information terminal according to the variation of the operational status of the information terminal.
- The status change of an information terminal is notified the reporting administration means from the status administration means. For example, if the notification of disconnection from a communication line is sent prior to “already-read notification”, the sent text message is forwarded to the mobile terminal.
- A seventh aspect of the present invention provides a text messaging system wherein if a text message sent to the information terminal is not read within a prescribed time period, the reporting administration means forwards the text message to the mobile terminal.
- The reporting administration means activates a timer when the sent text message is notified the reporting administration means from the decision means. The reporting administration means determines that the sent text message is not read in the information terminal if the text message is left after a prescribed time, and then sends the text message to the information terminal on the communication line.
- An eighth aspect of the present invention provides a text messaging system wherein the reporting administration means of the server notifies a text message sender that the text message is sent to a mobile terminal in a prescribed case.
- The reporting administration means notifies a text message sender that the text message is sent to a mobile terminal in a prescribed case. The prescribed case means a case that, for example, a text message was unable to be sent to an information terminal or a text message is not read in the information terminal. The prescribed case may include a case that, for example, a prescribed identifier is inserted into a text message. If a user needs the notification of a send result, he/she can hope for the notification by inserting an prescribed identifier into a text message to be sent.
- A ninth aspect of the present invention provides a text messaging system wherein the reporting administration means stores a text message and notifies the text message sender that the text message is stored if it cannot send the text message to a mobile terminal.
- There may be a case that a text message sent to a mobile terminal is stored in a server because the destination mobile terminal is out of the radio area or busy. If this is the case, the reporting administration means notifies the sending information terminal of it. A sending user can know if the text message is immediately transmitted. If the sending user requests the notification of a send result, he/she may add an identifier to a text message to be sent as described above.
- A tenth aspect of the present invention provides a text messaging system wherein the status detection means of an information terminal notifies a server of a phone number for contact, the status administration means of the server retains the notified phone number, and when a text message is sent from the information terminal to a mobile terminal, the decision means adds the phone number to a text message and sends it if the phone number of the sender for contact is set.
- The status detection means of the information terminal notifies the server of the phone number of the present whereabouts of a user. The status administration means of the server retains the notified phone number. The decision means refers to the status of a sending user when the destination of the text message from a PC such as a mobile terminal is selected. If the present phone number is set, the decision means adds the phone number to the text message as a callback phone number and sends it. If there is no present phone number, the decision means adds a default phone number of each user. This is convenient when a message receiver would like to inquire by phone instead of a character message.
- An eleventh aspect of the present invention provides a text messaging system further having a quasi information terminal connected to the communications line. The quasi information terminal has receive means, information acquisition means, send means, and information setting means.
- The receive means receives from a server a text message sent from a mobile terminal. The information acquisition means obtains the operational status of other information terminals according to received text messages. The send means sends the obtained operational status to the mobile terminal as a text message. The information setting means sets the operational status of other information terminals according to the received text message and notifies the server of it.
- For example, user A sends a message that he/she would like to know the status of user B to a quasi information terminal from a mobile terminal. The quasi information terminal obtains the status of user B from the server. The obtained information is sent from the quasi information terminal to the mobile terminal of user A as a text message. User A sends the phone number of the whereabouts from the mobile terminal to the quasi information terminal as a text message. The quasi information terminal sends a text message that changes the present phone number of user A for contact.
- A twelfth aspect of the present invention provides a text messaging system comprising one or more mobile terminals and information terminals respectively having communication means, a primary server connected to the above-mentioned information terminal via a communication line according to the above-mentioned communication means, and a secondary server connected to the above-mentioned mobile terminal and information terminal via a communication line according to the above-mentioned communication means.
- The information terminal has send means, receive means, and status detection means. The send means sends to the secondary server a text message addressed to another mobile terminal or information terminal. The receive means receives from the secondary server a text message sent from another mobile terminal or information terminal. The status detection means detects at least the status of connection to a computer network and notifies the primary server of it.
- The primary server has a status administration means that collects the operational status of an information terminal from the information terminal and retains it for each user.
- The secondary server has receive means, send means, and decision means.
- The receive means receives a text message from a mobile terminal or an information terminal. The send means sends a text message received from a mobile terminal or information terminal to another mobile terminal or information terminal. The decision means obtains the operational status of an information terminal from the primary server and determines the send mode of a text message according to the obtained operational status.
- This is a system configuration that the primary server and secondary server shares the function of the server according to the second aspect of the present invention.
- A thirteenth aspect of the present invention provides a text messaging system wherein an information terminal can further notify the secondary server that a text message was read and the secondary server further has a reporting administration means that forwards a text message to a mobile terminal if it is not notified that the text message was read.
- This is a system configuration that the primary server and secondary server shares the function of the server according to the fifth aspect of the present invention.
- The fourteenth aspect of the present invention provides a text message communication device having send means, receive means, and status detection means which is an information terminal that has communication means and sends and receives text messages among mobile terminals or other information terminals via a communication line and a server according to the above-mentioned communication means.
- The send means sends to the server a text message addressed to another mobile terminal or information terminal. The receive means receives from the server a text message sent from another mobile terminal or information terminal. The status detection means detects an operational status including the status of connection to a communication network and notifies the server of it.
- A fifteenth aspect of the present invention provides a server for text message communication which is a server connected to one or more mobile terminals or information terminals having communication means via a communication network according to the above-mentioned communication means and has receive means, send means, status administration means, and decision means.
- The receive means receives a text message from a mobile terminal or information terminal. The send means sends a text message received from a mobile terminal or information terminal to another mobile terminal or information terminal. The status administration means receives an operational status from an information terminal and retains it for each user. The decision means determines a send mode of text message according to operational status of the information terminal.
- A sixteenth aspect of the present invention provides a computer-readable recording medium which stores a text message communication program used for information terminals having communication means that sends and receives text messages among mobile terminals or other information terminals via a communication line or a server according to the above-mentioned communication means and stores a program for executing steps A to C below:
-
- A: a send step that a text message addressed to another mobile terminal or information terminal is sent to the server;
- B: a receive step that the text message sent from another mobile terminal or information terminal is received from the server; and
- C: a status detection step that an operational status including at least a status of connection to the communication line is detected and notified the server.
- A seventeenth aspect of the present invention provides a computer-readable recording medium which stores a text message communication management program used for a server connected to one or more mobile terminals or information terminals respectively having communication means via a communication line according to the above-mentioned communication means and stores a text message management program for executing steps A to D below:
-
- A: a receive step that a text message is received from a mobile terminal or information terminal;
- B: a send step that the received text message is sent to another mobile terminal or information terminal;
- C: a status administration step that the operational status of the information terminal is obtained and is retained for each user; and
- D: a determination step that the send mode of the text message is determined according to the operational status of the information terminal.
- An eighteenth aspect of the present invention provides a text message communication method which uses one or more mobile terminals or information terminals respectively having communication means and a server connected to the above-mentioned mobile terminals and information terminals via a communication line according to the above-mentioned communication means, comprising:
-
- A: sending and receiving a text message between a mobile terminal or information terminal and another mobile terminal or information terminal via the server;
- B: detecting the operational status of the information terminal including at least status of connection to the communication line and notifying the server of it;
- C: retaining the operational status of the information terminal for each user in the server; and
- D: determining the send mode of the text message according to the operational status of the information terminal by the server.
- A nineteenth aspect of the present invention provides a text message send/receive method which is used for information terminals that have communication means and send and receive text messages among mobile terminals or other information terminals via a communication line and a server according to the above-mentioned communication means, comprising:
-
- A: sending to the server a text message addressed to the above-mentioned mobile terminal or information terminal;
- B: receiving from the server a text message sent from another mobile terminal or information terminal; and
- C: detecting the operational status including at least the status of connection to the communication line and notifying the server of it.
- A twentieth aspect of the present invention provides a text message communication management method of a server connected to one or more mobile terminals or information terminals respectively having communication means via a communication line according to the above-mentioned communication means, comprising:
-
- A: receiving from a mobile terminal or information terminal a text message addressed to another information terminal;
- B: sending the received text message to another mobile terminal or information terminal;
- C: collecting the operational status of the information terminal including at least the status of the connection to the communication line and retaining it for each user; and
- D: determining the send mode of the text message according to the operational status of the information terminal.
- From the following detailed description in conjunction with the accompanying drawings, the foregoing and other objects, features, aspects and advantages of the present invention will become readily apparent to those skilled in the art.
-
FIG. 1 is a functional block diagram of a text messaging system according to the first embodiment of the present invention; -
FIG. 2 is a conceptual explanatory diagram of data stored in a status-storing module; -
FIG. 3 is a conceptual explanatory diagram of a message table in a reporting administration module; -
FIG. 4 is a display example of a window for setting status; -
FIG. 5 is a display example of a text message send window; -
FIG. 6 is a display example of a text message receive window; -
FIG. 7 is a display example of an e-mail text message receive window; -
FIG. 8 is a display example of an IRC text message receive window; -
FIG. 9 is a flowchart showing flow of an operational status notification process; -
FIG. 10 is a flowchart showing flow of a connection status notification process; -
FIG. 11 is a flowchart showing flow of a send process; -
FIG. 12 is a flowchart showing flow of a receive process; -
FIG. 13 is a flowchart showing process flow in a decision part; -
FIG. 14 is a flowchart showing flow of a status administration process; -
FIG. 15 is a flowchart showing flow of a reporting administration process; -
FIG. 16 is a flowchart showing flow of a timeout process; -
FIG. 17 is a flowchart showing flow of an operational status process; -
FIG. 18 is a flowchart showing flow of another process; -
FIG. 19 is a configuration of a text messaging system according to a second embodiment; -
FIG. 20 is a configuration of a text messaging system according to a third embodiment; and -
FIG. 21 is a conceptual configuration diagram of a conventional text messaging system using mobile terminals. - Reference will now be made in detail to the embodiments, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to the like elements throughout. The embodiments are described below to explain the present invention by referring to the figures.
-
FIG. 1 shows a functional block diagram of a text messaging system according to the first embodiment. The text messaging system according to the first embodiment consists ofserver 1 connected toInternet 2 andmobile communication network 4,multiple PC clients 3, and multiplemobile phones mobile communication network 4. Incidentally, to simplify the drawing, only onePC client 3 is shown. The mobile phone can send and receive a text message. Theserver 1 is notified of a detected self status of each mobile phone such as “busy” or “out of radio area.” - Server
- The
server 1 has text message sendpart 6, text message receivepart 7,status administration part 8,status storage part 9,decision part 10,notification management part 11,message storage part 12, receivepart 13, sendpart 14, and radiostatus detection part 15. - The text message send
part 6 and text message receivepart 7 send and receive a text message with thePC client 3 connected to theInternet 2, and send and receive send result notification of a text message or already-read notification of a text message with thePC client 3. - The
status administration part 8 receives operational status of the PC client from thePC client 3 and stores it in thestatus storage part 9 for each user. The operational status of the PC client is, for example, activation and completion of Internet applications, connection and disconnection of theInternet 2, activation status of a screen saver, or PC in operation. Thestatus administration part 8 receives stores prescribed information from thePC client 3 and stores it in thestatus storage part 9 for each user. The prescribed information is, for example, an e-mail address of each user, a nickname in IRC, a server and a channel, the phone number of a mobile phone, or present phone number. -
FIG. 2 shows an example of an operational status and a phone number of each PC client retained for each user by thestatus storage part 9. As shown inFIG. 2 , thestatus storage part 9 retains only one active status for each user. For example, even if one user has multiple PC clients, a PC for which an up-to-date status is set according to the user's operation is valid. InFIG. 2 , if data are blank, it is determined that the status is null. - For example, a status of each PC client in
FIG. 2 means the following: -
- User A: PC does not operate because there is not an IP address.
- User B: PC is in operation and is connected to a network.
- User C: PC is in operation and is connected to a network. E-mail is currently in use.
- User D: PC is in operation. Chatting by IRC. PC is in operation. There is a phone number of a destination.
- User E: PC is in operation. A screensaver is active. There is a phone number of a destination.
- When the
server 1 receives a text message addressed to any of the users, thedecision part 10 operates as follows. Thedecision part 10 refers to the operational status of a PC client of the relevant user and determines a send mode which can receive the text message in real time. At this time, if an Internet application is active on the PC client of the relevant user, thedecision part 10 determines that the text message is sent with the Internet application. If a PC client of the relevant user does not exist, is not connected to the Internet, or is not used, the mobile phone of the relevant user is determined as the destination of the text message. If necessary, the text message is converted after the determination of a send mode, and the send request of the text message is done to the message sendpart 6 or sendpart 14. Thedecision part 10 notifies the text message to be sent to thenotification management part 11 to monitor the send result of the text message. - The
notification management part 11 retains the text message sent in response to the notification from thedecision part 10 in a message table. Thenotification management part 11 also sends send notification to the sender if the status of the text message corresponds to a prescribed case. The prescribed case is such that the other party did not read the text message within a prescribed time, the text message was not read while the network application is active, the text message is not read while the PC is connected to theInternet 2.FIG. 3 shows a conceptual diagram of the message table. In the message table shown in the figure, the name of a sender, the name of a receiver, the type of receiver, the timer ID, and the contents of the text message are retained. - The
message storage part 12 temporally stores the text message if the text message is not immediately sent to themobile terminal - The receive
part 13 and sendpart 14 are for sending and receiving the text message amongmobile phones - Radio
status detection part 15 detects notification from themobile phone - PC Client
- The
PC client 3 has text message send/receive 21, networkservice detection part 22, PCoperation detection part 23, andstatus setting part 24. - The text message send/receive
part 21 sends and receives the text message with theserver 1, notifies the user of the send result of the text message sent from theserver 1, and further notifies theserver 1 that the received text message was read according to the input of the user. Incidentally, the text message send/receivepart 21 may be an independent application or another Internet application for sending and receiving text messages can be substituted. An e-mail application or an IRC application is cited as an example of an application for sending and receiving text messages. - The network
service detection part 22 detects the activation and completion of a network application. Specifically, it detects the connection and disconnection of an webpage or the activation and completion of an e-mail or IRC application, and notifies thestatus setting part 24 of it each time the status changes. At the same time, it detects an e-mail address, a nickname used for IRC, a server, and a channel and notifies of them. - The PC
operation detection part 23 monitors a user status and notifies thestatus setting part 24 of it each time the status changes. Specifically, it monitors whether or not there is input by keyboard or mouse, thePC client 3 connects to or disconnects from a network by LAN or dial up, the screensaver is active, input by keyboard or mouse is done on the top window in multiwindow. The PCoperation detection part 23 also sends “connection message” to thestatus administration part 8 of theserver 1 at every definite period of time. If “connection message” does not come within a period of time, thestatus administration part 8 determines that thePC client 3 is disconnected from theInternet 2. - The
status setting part 24 notifies thestatus administration part 8 of the server of the status of the PC client detected by the above-mentionedservice detection part 22 and the PCoperation detection part 23. Thestatus setting part 24 receives the mobile phone number of the user and the present phone number and notifies thestatus administration part 8 of theserver 1 of them. Furthermore, thestatus setting part 24 obtains the operational status of the PC client of another user, destination, contact address, etc. from theserver 1 and outputs them. - Next gives a specific explanation of the process done by the PC client according to the embodiment (process done by the application) showing screen examples and flowcharts.
- (1) Screen Example
- “In” Status Setting Window
-
FIG. 4 shows an example of a window for setting whereabouts of the user. The right side of the screen shown in the figure is a presence status setting window. This window is for writing presence status of the user (present, absent, away from seat, in council, in laboratory, etc.), his/her destination, phone number, brief schedule, etc. Input in the window by the user notifies the status administration part of theserver 1 of a presence status. The presence status of another user obtained from theserver 1 by the status setting part is displayed on a window on the left side in the figure. - Text Message Send Window
-
FIG. 5 shows an example of a message send window in thePC client 3. Selecting the receiver of a text message on the above-mentioned left window in the figure opens the text message send window. With this, a brief message such as “hey, come on” or “call me” can be notified substantially in real time if the other party connects to theInternet 2 with a PC client. Furthermore, by checking the send result notification box, the result notification of a sent message can be asked for. - Text Message Receive Window
-
FIG. 6 shows the receive window of text messages. The receive window is displayed in the corner of the screen without being displayed in front of the window being used. On the right side of the window, there is a button for replying by call or text message. This button is for immediately replying to a received text message. The button on the right edge is for abandoning the text message without replying to it. By pressing any of the buttons or closing the window, the already-read message showing the text message was read is sent to theserver 1 from thePC client 3. The text message receivepart 6 of theserver 1 that received notification notifies thenotification management part 11 of an already-read notification. - If the
PC client 3 where an Internet application is in operation received a text message, the receive window is displayed with the application window.FIG. 7 is a screen example when a text message is received while an e-mail application is being used. A message from user B indicated as to-be-read inFIG. 7 is a message send by the present invention.FIG. 8 is a screen example when a text message is received while the IRC application is being used. If these Internet application are being used, the mail becoming already-read or reply input to a chat is detected with theservice detection part 22 of thePC client 3 and is notified theserver 1. - (2) Operational Status Notification Process
- Once a PC is powered and connected to the server via the Internet, the operative status notification process shown in
FIG. 9 and the connection status notification process shown inFIG. 10 are commenced. - At first in step S1, the above-mentioned network
service detection part 22 and the PCoperation detection part 23 monitor the operational status of thePC client 3. - In step S2, the
service detection part 22 and the PCoperation detection part 23 determine whether or not there is a change in the operational status. If there is a change, a new status is notified thestatus setting part 24 and step S3 ensues. If there is no changes in the operational status, the process returns to step S1. - In step S3, the
status setting part 24 received the notification notifies theserver 1 of a new operational status. At the moment, information for identifying the user such as a user name or an IP address is added and notified, and the process returns to step S1 to monitor occurrence of a new status change. - In other words, in steps S1 to S3, a process that the change of the operational status of the PC client is notified the
server 1 is performed. - Meanwhile, the PC
operation detection part 23 performs the connection status notification process shown inFIG. 10 in addition to the monitor and detection of the PC operation in the above-mentioned steps S1 and S2 and notifies theserver 1 of the connection status. - At first, in step S21, the PC
operation detection part 23 determines whether or not thePC client 3 is connected to theInternet 2. If the result is “Yes”, step S22 ensues. If the result is “No”, the process returns to step S21 again and repeat the above-mentioned determination. - In step S22, the PC
operation detection part 23 sends the connection notification to theserver 1 via thestatus setting part 24. - In step S23, the PC
operation detection part 23 waits for the elapse of predetermined time T and if the time elapsed, the process returns to step S21 and repeats the above-mentioned determination and connection notification. - Namely, in steps S21 to S23, while the
PC client 3 is connecting to theInternet 2, a process that the connection notification to theserver 1 is performed every time the predetermined time T elapses. - (3) Send Process
- When the PC is powered and connected to the server via the Internet, the send process as shown in
FIG. 11 are commenced along with the above-mentioned operation status notification process and the connection status notification process. - In step S31, the text message send/receive
part 21 determines whether or not the other party a text message is sent to was selected. If the result is “Yes”, step S32 ensues. Otherwise the process repeats the step and waits for the other party to be selected. - In
step 32, the text message send/receivepart 21 opens the text message send window inFIG. 5 and accepts the input of a text message to be sent. - In step S33, the text message send/receive
part 21 waits for the “Send” button to be pressed. When the button is pressed, the input message is sent to the serve with the sender's name and the process returns to step S31. - (4) Receive Process
- When the PC is powered, a receive process as shown in
FIG. 12 is commenced in parallel with the above-mentioned process. - At first, in step S41, the text message send/receive
part 21 waits for a reception from theserver 1 and if there is a reception, step S42 ensues. - In step S42, the text message send/receive
part 21 determines whether or not the reception is a text message from another user. If the result is “Yes”, step S43 ensues. Otherwise step S50, which will be descried below, ensues. - In step S43, the text message send/receive
part 21 opens the receive window exemplified inFIG. 6 , 7, or 8, notifies the user of the received text message part, and obtains a sender number included in the sent text message such as an IP address. - In step S44, the text message send/receive
part 21 determines whether or not the reply button was pressed. If the above-mentioned read-and-abandon button was pressed or the window was closed, step S45 ensues. If the reply button was pressed, step S46 ensues. - In step S45, the text message send/receive
part 21 sends a already-read notification that notifies the server that the text message was read. - In step S46, the text message send/receive
part 21 determines whether the pressed reply button is the button for call. If the button for call was pressed, the step S47 ensues. If the reply button by text message was pressed, step S48 ensues. - In step S47, the text message send/receive
part 21 dials the mobile-phone number of the other party or the phone number of current whereabouts that is notified with the text message. The receive wait state in step S41 returns. - In step S48, the text message send/receive
part 21 opens the text message send window as shown in the above-mentionedFIG. 5 and accepts the input of a text message. By the text message being input and the “Send” button being pressed in step S49, the inputted text message is sent. The destination of the text message to be sent is set to the sender of the text message that is previously obtained. - If it is determined that the reception is not a text message in step S42, step S50 ensues. In step S50, the text message send/receive
part 21 determines whether or not the send result of the text message is received. If the reception is the send result, then step S51 ensues, the send result notified from theserver 1 is notified the user, and the receive wait state in step S41 returns. For example, a send result “The message addressed to 020-222-222 was not read and forwarded to the mobile phone.” is displayed on the screen. If the reception is not the send result, step S52 ensues. - In step S52, the text message send/receive
part 21 determines whether or not the reception is an already-read notification. If the reception is the already-read notification, step S53 ensues and it is notified the user that the sent text message is read by the other party. For example, as the result display of the mail inFIG. 7 , the text message is displayed in catalogue and the relevant message part is displayed with half-tone dot meshing or a color. After that the receive wait state of step S41 returns. - The flow of the process performed by the
server 1 is explained with a flowchart. In the following description, the operational status of each PC client is shown in the above-mentionedFIG. 2 . Theserver 1 can support an e-mail or IRC application used by the PC client. To simplify the description, a case that a text message is sent from themobile phone 5A of user A to the mobile phone of another user C is described as a example. - (1) Decision Process
- At first, flow of the process performed by the
decision part 10 based onFIG. 13 is explained. - In step S61, by the
decision part 10 receiving from the receivepart 13 of theserver 1 a text message sent from themobile phone 5A of user A, the process is commenced. The text message includes the mobile phone number, contents of the text message, sender information, and the presence of the notification of the send result. Now assume that the mobile phone number of user C is “020-444-4444”, contents of the text message is “Returns to the office at 3 p.m.”, and the sender information is the mobile phone number of user A i.e. “020-444-4444.” - Incidentally, when a text message is sent with each application from the
PC client 3, the message receivepart 7 of theserver 1 receives the text message and notifies thedecision part 10 of it. In this case, information for identifying the sender and receiver is a user's name or an IP address. If the text message is sent by e-mail, the information is an e-mail address; if the text message is sent by IRC, the information is a nickname. - In step S62, the
decision part 10 searches in thestatus storage part 9 with the received mobile phone number “020-444-4444” as a search key and obtains the status of user C. Similarly, thedecision part 10 also obtains the status of the sender. - In step S64, the
decision part 10 determines whether or not the PC client of user B is connected to theInternet 2. In this example, since the IP address of user C is not empty, it is determined that the PC client is connected and step S65 ensues. If it is not connected, the text message is sent to the sendpart 14 and step S74, which is described below, ensues. - In step S65, it is determined whether or not the
PC client 3 of user C is in operation. Namely, if a screensaver is active on the PC client of user C, it is assumed that user C is not in front of the PC and a mobile phone is selected as a destination. The received text message is stored in themessage storage part 12. Conversely, a screensaver is not active on the user C's PC in this example. Therefore the other party is assumed to be in front of the PC, the PC client of user C is selected as a destination, and step S66 ensues. - In step S66, the
decision part 10 determines whether or not an Internet application of the PC client is active on thePC client 3 of user C. Specifically, by referring toFIG. 2 , it is understand that the e-mail address of user C is written and the e-mail is being used. In this case, step S67 ensues. Conversely, if the Internet application is not active, step S68, which is described later, ensues. - In step S67, the
decision part 10 obtains a necessary parameter for sending the text message with an e-mail application such as an e-mail address from thestatus storage part 9. At this moment thedecision part 10 also obtains the name of user A. - In step S68, the
decision part 10 obtains a necessary parameter for directly sending the text message such as an IP address from thestatus storage part 9. At this moment thedecision part 10 also obtains the name of user A. - In step S69, the
decision part 10 notifies the text message sendpart 6 of the text message and the information obtained in step S67 or S68 and requests send. In this example, the text message is configured to an e-mail message by text message sendpart 6 and sent to the e-mail address of user C. In thePC client 3 of user C which received the e-mail message, the text message is displayed on an window shown inFIG. 7 . The e-mail message sent from the server is usually sent to a client via an e-mail server. - In above-mentioned step S63, if it is determined that the PC client of user C is not active, step S70 ensues.
- In step S70, the
decision part 10 obtains a parameter which is necessary to send the text message to the mobile phone of user C such as a mobile phone number from thestatus storage part 9. At the same time, thedecision part 10 also obtains the name of user A, which is a sender, the mobile phone number of user A, and the number of whereabouts. If it is determined there is no statuses and step S70 ensues, the parameter of user C is not obtained. Consequently, the other party's phone number that were sent when the previous message was received “020-444-4444” is set to the other party's phone number and next step S71 proceeds. - In step S71, the
decision part 10 passes the information obtained in the above-mentioned step S70 to the sendpart 14 and requests radio transmission. - In step S72, the
decision part 10 determines whether or not the mobile phone of user C can notify theserver 1 that the text message was read and the sender requests notification. If both is possible, step S73 ensues. If the notification from the mobile phone is impossible, the process returns to step S61 and waits for the reception of the text message. - In step S73, the
decision part 10 sends the sent text message, the sender's name, and send notification including a send terminal and a receive terminal to thenotification management part 11. And step S61 returns. As described later, thenotification part 11 writes contents of the received send notification in the message table. - In the above-mentioned step S64 or S65, if it is determined that the PC client of user C is not connected to the Internet or the PC is not currently used, step S47 ensues.
- In step S74, the
decision part 10 determines whether or not sender A requests notification of a send result. If sender A requests the notification, then the above-mentioned step S70 ensues and the notification to the mobile phone is sent. - In step S75, the
decision part 10 creates result notification addressed to the sender indicating that the text message is temporally stored in themessage storage part 12. - In step S76, the
decision part 10 determines send mode according to the status of sender A sends the result notification created in step S74. Namely, thedecision part 10 sends the text message to the mobile phone because the PC client of receiver C is not connected to the Internet and notifies user A that a text message indicating it. The message is sent to thedecision part 10 and transmitted to sender A in an appropriate way. - (2) Status Administration Process
- Flow of status administration process managing the operational status of the PC client in the
server 1 is described next with a flowchart shown inFIG. 14 . - At first, it is notified the
status administration part 8 of theserver 1 from thestatus setting part 24 that the operational status in thePC client 3 of the user changed in step S81 and the process is commenced. - In step S82, the
status administration part 8 updates the contents of thestatus storage part 9 for each user based on the received contents. - In step S83, the
status administration part 8 further notifies thenotification management part 11 of the change of the operational status. - (3) Reporting Administration Process
- Reporting administration process performing notification to the sender from the
server 1 is described below with a flowchart shown inFIG. 15 . In this embodiment, the following four processes are performed: (i) main process, (ii) timeout process of stored text message, (iii) process of stored text message according to a receiver status, and (iv) process other than above. - (i) Main Process
- At first, in step S91 in
FIG. 15 , receiving events such as message, timeout process, and status notification of user's activities commences the following process. - In step S92, the
notification management part 11 determines whether or not the received event is a text message. If the event is a text message, step S93 ensues. Otherwise step S100, which will be described later, ensues. - In step S93, the
notification management part 11 determines whether or not the received text message is send notification notified from thedecision part 10 in step S37 inFIG. 13 . If the received text message is the send notification, step S94 ensues. If the received text message is not the send notification, no process is performed and step S91 returns. - In step S94, the
notification management part 11 activates a timer counting a prescribed time and manages the message table with timer ID. - In step S95, the
notification management part 11 writes timer ID in addition to contents of the text message included in the send notification, sender and receiver, and send/receive type. Then step S95 ensues. - If it is determined in step S92 that the text message is not send notification or is not an usual text message, then step S100 ensues.
- In step S100, the
notification management part 11 determines whether or not the received event is timeout notification. If the event is timeout notification, message timeout handling routine in step S300 ensues. In the timeout handling routine, stored text messages that timed out are deleted. Timeout process is described later. If the received event is not timeout notification, step S200 ensues. - In step S200, the
notification management part 11 determines whether or not the received event is notification of the operational status of a PC client. If the event is the notification of the operational status, step S500 ensues and another handling routine is performed. The operational status handling routine in step S400 and another operational routine in step S500 are described later. - (ii) Timeout Process
- If it is determined in step S100 that the event is timeout notification, the timeout handling routine in step S300 ensues.
FIG. 16 is a flowchart showing flow of the timeout handling routine. - At first in step S301, the
notification management part 11 determines whether or not the timed-out text message is left in the message table. If the text message is left, it is assumed that already-read notification from the receiver in a predetermined time and step S302 ensues. If the text message is not left, the main routine in above-mentionedFIG. 15 returns. - In step S302, the
notification management part 11 determines whether or not the type of the receiver of the timed-out text message is a mobile phone. If the type is a mobile phone, step S303 ensues; if the type is a PC client, step S307 ensues. - In step S303, the
notification management part 11 determines whether or not the sender hopes for notification of send result of the text message. If the sender hopes for the notification, step S304 ensues. If the sender does not hope for the notification, step S306 ensues. - In step S304, the
notification management part 11 creates to-be-read result notification that indicates the sent text message was not read and step S305 ensues. - In step S305, the
notification management part 11 notifies thedecision part 10 of created to-be-read result notification. Thedecision part 10 selects appropriate send means and send method from the sender status and sends the to-be-read result notification to the sender. - In step S306, the
notification management part 11 deletes an entry of relevant text messages from the message table and the main routine in above-mentionedFIG. 15 returns. - That is to say, in steps S303 to S305, result notification indicating “the text message is sent to the mobile phone, but it was not read.” is sent to the sender.
- In step S302, if the receiver is determined as a PC client, step S307 ensues.
- In step S307, as is the case with the above-mentioned S303, the
status administration part 11 determines whether or not the sender hopes for notification of send result. If the sender hopes for the notification, step S308 ensues. If the sender does not hope for the notification, step S315 ensues. - In step S308, the
notification management part 11 creates radio send result notification indicating the text message is sent to the mobile phone. - In step S309, the
notification management part 11 notifies thedecision part 10 of the created radio send result notification. Thedecision part 10 that received the notification notifies the sender of the above-mentioned result notification in a send mode according to the operational status of the sender's PC client. - In step S310, the
notification management part 11 passes the text message to the sendpart 14 and deletes the entry of the relevant text message from the message table. - In step S311, the
notification management part 11 obtains necessary information such as the receiver's mobile phone number to send the text message to the mobile phone from thestatus storage part 9. - In step S312, the
notification management part 11 notifies thesend part 14 of send information and requests the transmission of text message. - In step S313, the
notification management part 11 determines whether or not it can be notified that the receiver's mobile phone read the text message. If it can be notified, the step S314 ensues. Otherwise the main routine in above-mentionedFIG. 15 returns. - In step S314, the
notification management part 11 issues send notification including sender/receiver, send/receive type, etc. This send notification is written in the message table in the above-described step S94. - (iii) Operational Status Process
- In step S200, if the received event is determined as the change notification of the operational status of the PC client, step S400 operational status handling routine shown in
FIG. 17 ensues.FIG. 17 is a flowchart showing flow of the operational status handling routine. - At first in step S401, the
notification management part 11 determines whether or not the text message addressed to the PC client with the operational status changed is in the message table. If it is in the message table, step S402 ensues. If not, the main routine returns. - In step S402, the
notification management part 11 determines whether or not the change of the status corresponds to “disconnection from the Internet” or “Screensaver active.” If it corresponds to either of the above two statuses, step S403 ensues. If it is not corresponds to any of the above two statuses, step S410 ensues. - In step S403, the
notification management part 11 determines whether or not the sender hopes for the send notification sent to the sender, and if the sender for it step S404 ensues. If the sender does not hope for it step S416 ensues. - In step S404, the
notification management part 11 creates radio send result notification and notifies the decision part of it, assuming that the a text message that was previously sent to the PC client. For example, Radio send result notification with a message “The message addressed to 020-222-222 was not read in the PC and was sent to the mobile phone.” is created. The decision part determines a send mode according to the status of the sender and requests it to be sent from the text message sendpart 6 or thesend part 14. - In step S405, the
notification management part 11 passes the text message to the sendpart 14 and deletes the entry of the relevant text message from the message table. - In step S406, the
notification management part 11 obtains necessary information such as a mobile phone number to send it to the mobile phone from thestatus storage part 9. - In step S407, the
notification management part 11 sends the obtained send information to the sendpart 14 and requests sending. - In step S408, the
notification management part 11 determines whether or not that the receiver's mobile phone read can be notified. If it is possible, step S409 ensues. Otherwise the main routine inFIG. 10 returns. - In step S409, the
notification management part 11 creates send notification including the sent text message, sender/receiver, and send/receive type, etc. This send notification is written in the message table in step S94 of the above-mentioned main routine. - If it is determined that the status change notified in above-mentioned S402 is not disconnection or activation, step S410 ensues.
- In step S410, the
notification management part 11 determines whether or not the notified status change is completion notification of an Internet application that is already sent. If it is completion notification, step S411 ensues; otherwise the main routine inFIG. 15 ensues. - In step S411, the
notification management part 11 obtains send information necessary to send to PC client such as an IP address by referring to thestatus storage part 9. - In step S412, the
notification management part 11 passes thesend part 14 an obtained send message or text message and requests sending. - In step S413, the
notification management part 11 deletes the relevant text message from the message table. - In step S414, the
notification management part 11 determines whether or not the sender hopes for the notification of the send result. If the user hopes for the notification, step S415 ensues. If not, the main routine indicated inFIG. 15 ensues. - In step S415, the
notification management part 11 creates a PC send result notification and notifies thedecision part 10 of it, assuming that a text message previously sent to an Internet application of the PC client was not read. For example, a PC send result notification with a content “a text message addressed to channel #CA was not read and was sent to PC” is created. Thedecision part 10 selects a send means and send method according to the sender's status and requests sending from the text message sendpart 6. - In step S416, the
notification management part 11 obtains information necessary to send to the mobile phone such as the mobile phone number from thestatus storage part 9. - In step S417, the
notification management part 11 passes the obtained information to the sendpart 14 and requests sending. - (iv) Other Process
- In step S200, if it is determined that the received event is not a change notification of the operational status, another handling routine in step S500 ensues.
FIG. 18 is a flowchart showing flow of another handling routine. - At first in step S501, the
notification management part 11 determines whether or not the received event is text message acquisition notification from the receiver. For example, if acquisition notification from a PC client or mobile terminal that received a text message is received by the text message receivepart 7 or the receivepart 13, the acquisition notification is sent to thenotification management part 11. There may also be the case in which reply to an e-mail message or a confirmation command sent in the same channel of IRC may be detected by the text message receivepart 7 and theacquisition notification 11 is sent to thenotification management part 11. If the received event is acquisition notification, step S502 ensues; otherwise a below-described step S503 ensues. - In step S502, the
notification management part 11 deletes the entry of the relevant text message from the message table and the main routine inFIG. 15 returns. - In step S503, the
notification management part 11 determines whether or not the received event is notification indicating a text message to the mobile phone is stored. If it is the notification, step S504 ensues. Otherwise the main routine inFIG. 15 returns. That is to say, if a text message is stored in themessage storage part 12, storage notification is sent to thenotification management part 11 from thesend part 14. - In step S504, the
notification management part 11 determines whether or not the sender hopes for the notification of a send result. If the sender hopes for the notification, step S505 ensues. If not, the main routine inFIG. 15 ensues. - In step S505, the
notification management part 11 creates storage result notification indicating a text message is stored. Thedecision part 10 determines a send mode according to a sender's status and requests sending of storage result notification from thesend part 6 or thesend part 14. - In the above process, time to be timed out or notification setting when a text message is not read immediately may be set for the server from a mobile phone or a PC client via the Internet. The setting can also be performed with a text message in a prescribed format.
- A mobile terminal can obtain arbitrary information by sending a text message in a prescribed format from the mobile terminal with the text messaging system shown in the above-mentioned first embodiment.
- For example,
FIG. 19 shows a configuration diagram of a text messaging system that changes or refers to the operational status of a PC client managed by theserver 1. InFIG. 19 ,information server 30 is used as a PC client. Themobile terminal 5 sends a text message in a format for sending the text message to the PC client. Theinformation server 30 pretends to be the PC client and sets an operational status form theserver 1. - For example, a destination or schedule information is sent from a
mobile terminal 5 to a phone number of theinformation server 30 as a text message in a prescribed format. As described, theserver 1 sends the text message to theinformation server 30. Theinformation setting part 26 of theinformation server 30 that received the text message analyzes the received text message, and notifies thestatus administration part 8 of information that changes the operational status of the sender. - The
information setting part 26 sends a text message indicating that the destination of another user needs to be known with a phone number of the other user. Then theserver 1 sends the text message to theinformation server 30. - The information acquisition part 25 of the
information server 30 analyzes the received text message and obtains the operational status of the other PC client with the phone number as a search key. The obtained information is sent as a text message from the information server to the number of the sender mobile terminal. Accordingly, for example, current whereabouts of another user can be identified and a call can be made to him/her. - As shown in
FIG. 20 , theradio server 1 b may be made to have themessage storage part 12 and radiostatus detection part 15 by installing a radio sever 1 b independent of atext message server 1 a. In this case, the receivepart send part 14 a and 14 b are respectively installed in thetext message server 1 a and theradio server 1 b. The status administration server 1 c may also be made to have thestatus administration part 8 anddecision part 9 by further installing an independentstatus administration server 1. - A where-to-call number may be sent with a text message so that the other party can immediately call back when the text message is sent from a PC client or a mobile phone. A receiver can call the number and talk to the other party as soon as he receives the text message. For example, the
decision part 10 refers to the sender's status as well as the receiver's status. If the number of current whereabouts is set in thestatus storage part 12, thedecision part 10 sends the phone number as a callback number with the text message. If the number of current whereabouts is not set, the mobile phone number may be sent with the text message as a callback number. - In addition to the above-mentioned embodiment, it is conceivable that a schedule in a particular condition is obtained or a function such as acquisition of e-mail is added to the
server 1. Services can easily be added without changing server configuration. - In the above-mentioned embodiment, a single mobile communication network and a single Internet are respectively shown. However, they may be multiple. Since the status administration part of the
server 1 holds only one active status per user, if the number of networks increases, it can be supported. - Use of this invention allows a text message to be sent in a send mode according to the other party's status and to be sent and received substantially in real time. By notifying the sender of send result such as the text message not being checked by the other party, the text message can be notified in another send mode. Furthermore, the sender can know which send mode is used in which the text message was sent and thus communications with texts can be smoothly performed in real time.
- While only selected embodiments have been chosen to illustrate the present invention, to those skilled in the art it will be apparent from this disclosure that various changes and modifications can be made herein without departing from the scope of the invention as defined in the appended claims. Furthermore, the foregoing description of the embodiments according to the present invention is provided for illustration only, and not for the purpose of limiting the invention as defined by the appended claims and their equivalents.
Claims (14)
1. In an information terminal provided with communication means for transmitting and receiving text messages among mobile terminals or other information terminals via communication lines and servers responsive to said communication means, a text messaging device comprising:
a plurality of transmission means having different transmission modes for transmitting to the servers text messages addressed to the mobile terminals or to the other information terminals;
reception means for receiving from the servers text messages from the mobile terminals or from the other information terminals; and
status detection means for detecting and reporting to the servers an operational status of the each transmission means of the information terminals including at least a change of status of a connection with the communications lines,
wherein the detecting the change of status further comprises:
detecting a disconnection of one of the each transmission means, and
detecting whether a user is using one of the information terminals.
2. The text messaging device according to claim 1 , wherein the detecting a disconnection of one of the each transmission means further comprises detecting a disconnection of the one of the each transmission means from the Internet.
3. A text-messaging server connected to a mobile terminal and an information terminal respectively provided with communication means, via communications line responsive to the communications means, the server comprising:
reception means for receiving text messages from the mobile terminal or the information terminal;
transmission means for transmitting text messages received from the mobile terminal or the information terminal to another mobile terminal or to another information terminal using a dynamically selected transmission means and a dynamically selected transmission mode, wherein the server is connected to a plurality of either;
status administration means for receiving and storing, per user of the information terminal, an operational status, including a change of status, of the each transmission means of the information terminal; and
selecting means for referring to the operational status, including the change of status, stored by the status administration means of an information terminal that is a destination of the text message received from the information terminal, and for dynamically selecting a message destination and a transmission means and transmission mode for the text messages according to the stored operational status and change of status.
4. A computer-readable recording medium on which is recorded a text messaging program utilized in an information terminal provided with communication means for transmitting and receiving text messages among mobile terminals or other information terminals via communication lines and servers responsive to said communication means, the computer-readable recording medium on which is recorded the text messaging program for executing:
transmitting to the servers text messages addressed to the mobile terminals or to the other information terminals with one of a plurality of transmission means with different transmission modes;
receiving from the servers text messages from the mobile terminals or from the other information terminals; and
detecting and reporting to the servers an operational status of each information terminal including at least a change of status of a connection with the communications lines,
wherein the detecting the change of status further comprises:
detecting a disconnection of one of the each transmission means, and
detecting whether a user is using one of the information terminals.
5. The computer-readable recording medium according to claim 4 , wherein the detecting whether a user is using one of the information terminals further comprises detecting an activation of a screen saver.
6. A computer-readable recording medium on which is stored a text messaging administration program utilized in a server connected to mobile terminal and information terminal respectively provided with communication means, via communications line responsive to the communications means, the computer-readable recording medium on which is recorded the text messaging administration program for executing:
receiving text messages from the mobile terminal or the information terminal;
obtaining and storing, per user of the information terminal, an operational status, including a change of status, of each transmission means of each the information terminal;
selecting each text message transmission mode according to the operational status, including the change of status, of the information terminal; and
transmitting text messages from the information terminals to a destination information terminal according to the selected text transmission mode,
wherein the change of status further comprises:
a disconnection of one of the each transmission means and
a use of an information terminal by a user.
7. A text messaging method utilized in a server connected to a mobile terminal and an information terminal respectively provided with communication means, via communications line responsive to the communications means, the text messaging method:
detecting and reporting to the server an operational status of each transmission means of the information terminal including at least a change of status of connection with the communications line;
storing, per user of the information terminal, in the server the operational status, including the change of status; and
selecting a transmission mode for the received text messages according to the stored operational status and change of status of the information terminal; and
transmitting and receiving text messages by way of the server between the mobile terminal and the destination information terminal, or between the mobile terminal and another mobile terminal, wherein the system includes a plurality thereof, or between the information terminal and the destination information terminal, wherein the system includes a plurality thereof,
according to the dynamically selected transmission mode.
8. A text message transmission and reception method utilized in an information terminal provided with communication means for transmitting and receiving text messages among mobile terminals or other information terminals via communication lines and servers responsive to said communication means, the text message transmission and reception method:
transmitting to the servers text messages addressed to the mobile terminals or to the other information terminals with one of a plurality of transmission means with different transmission modes;
receiving from the servers text messages from the mobile terminals or from the other information terminals; and
detecting and reporting to the servers an operational status of the each transmission means including at least a change of status of a connection with the communications lines.
9. The computer-readable recording medium according to claim 8 , wherein the change of status further comprises an activation or completion of a network application.
10. A text-messaging administration method for a server connected to a mobile terminal and an information terminal respectively provided with communication means, via a communications line responsive to the communications means, the text-messaging administration method comprising:
receiving from the mobile terminal or the information terminal text messages addressed to another mobile terminal or another information terminal, or addressed to another mobile terminal or to another information terminal, wherein the system includes a plurality of either;
gathering and storing per a user of the information terminal, an operational status of each transmission means of each information terminal including at least a change of status of connection with the communications line; and
selecting a transmission means and a transmission mode for the received text messages according to the operational status, including the change of status, of the information terminal that is a destination of the text message received from the information terminal; and
transmitting the received text messages to another mobile terminal or a destination information terminal according to the dynamically selected transmission mode using the dynamically selected transmission means.
11. A text messaging system including a plurality of information terminals, and servers connected to the information terminals via communication lines, comprising:
status detection means provided in the information terminals for detecting and reporting to the servers an operational status of the each transmission means including at least a change of status of the connection with the communication lines;
status administration means provided in the servers for storing, per user of any one of the information terminals, the operational status, including the change of status, of the each transmission means of each information terminal reported from said status detection means;
selecting means provided in the server for referring to the operational status, including the change of status, stored by the status administration means of an information terminal that is a destination of the text message received from the information terminal, and for dynamically selecting a message destination and a transmission mode and a transmission means for the received text messages according to the stored operational status and change of status.
12. A text messaging system according to claim 11 , further comprising a proxy information terminal, connectable to the communications line, wherein said proxy information terminal is provided with:
information acquisition means for obtaining in accordance with the received text messages an operational status of another information terminal;
transmission means for transmitting the obtained operational status as a text message to the mobile terminal according to the dynamically selected transmission mode using the dynamically selected transmission means; and
information setting means for setting and reporting to the server an operational status of the other information terminal in accordance with the received text messages.
13. A text messaging system including a plurality of information terminals and servers connected to the information terminals via communication lines, comprising:
a detector detecting and reporting to the servers an operational status of the each transmission means including at least a change of status of the connection with the communication lines;
a receiver receiving text messages from any one of the information terminals;
a controller storing, per user of any one of the information terminals, the change of operational status of the each transmission means of each information terminal reported from said status detection means; and
a processor referring to the changed operational status stored by the controller and dynamically selecting a message destination and a transmission means and transmission mode for the received text messages according to the stored operational status and change of status.
14. The text messaging system according to claim 13 , further comprising a proxy information terminal comprising:
a receiver receiving from the server text messages from the mobile terminal and obtaining in accordance with the received text messages operational status of each transmission means of another information terminal;
a transmitter transmitting the obtained operational status as a text message to the mobile terminal; and
a processor setting and reporting to the server the operational status in accordance with the received text messages.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/149,951 US20090082044A1 (en) | 1998-08-06 | 2008-05-09 | Text messaging system and method |
Applications Claiming Priority (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP22265598A JP3865946B2 (en) | 1998-08-06 | 1998-08-06 | 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 |
JP10-222655 | 1998-08-06 | ||
PCT/JP1999/002353 WO2000008813A1 (en) | 1998-08-06 | 1999-04-30 | Character message communication system and method |
US09/772,000 US7437413B2 (en) | 1998-08-06 | 2001-01-30 | Text messaging system and method |
US12/149,951 US20090082044A1 (en) | 1998-08-06 | 2008-05-09 | Text messaging system and method |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/772,000 Continuation US7437413B2 (en) | 1998-08-06 | 2001-01-30 | Text messaging system and method |
Publications (1)
Publication Number | Publication Date |
---|---|
US20090082044A1 true US20090082044A1 (en) | 2009-03-26 |
Family
ID=16785864
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/772,000 Expired - Fee Related US7437413B2 (en) | 1998-08-06 | 2001-01-30 | Text messaging system and method |
US12/149,951 Abandoned US20090082044A1 (en) | 1998-08-06 | 2008-05-09 | Text messaging system and method |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/772,000 Expired - Fee Related US7437413B2 (en) | 1998-08-06 | 2001-01-30 | Text messaging system and method |
Country Status (4)
Country | Link |
---|---|
US (2) | US7437413B2 (en) |
EP (1) | EP1102443B1 (en) |
JP (1) | JP3865946B2 (en) |
WO (1) | WO2000008813A1 (en) |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080095337A1 (en) * | 2006-10-24 | 2008-04-24 | Yigang Cai | Storage of data messages for later retrieval by the recipient |
US8239457B1 (en) * | 1999-12-17 | 2012-08-07 | Ipcom Gmbh & Co. Kg | Method for transmission of an electronic post message |
US8526922B1 (en) * | 2012-05-01 | 2013-09-03 | Noble Systems Corporation | Integrating two-dimensional barcodes and embedded links with call center operation |
US8532283B1 (en) | 2012-05-14 | 2013-09-10 | Noble Systems Corporation | Integrating embedded links with call center operation |
US8548133B1 (en) | 2012-05-01 | 2013-10-01 | Noble Systems Corporation | Managing electronic consent for calling campaigns |
US20140156760A1 (en) * | 2008-10-07 | 2014-06-05 | Mingoe Inc. | Method and system for maintaining contact information |
CN103944979A (en) * | 2014-04-09 | 2014-07-23 | Tcl集团股份有限公司 | Method, device and system for message pushing |
CN104333852A (en) * | 2014-01-23 | 2015-02-04 | 广州三星通信技术研究有限公司 | Processing method and system of status of message |
US9848082B1 (en) | 2016-03-28 | 2017-12-19 | Noble Systems Corporation | Agent assisting system for processing customer enquiries in a contact center |
US9936066B1 (en) | 2016-03-16 | 2018-04-03 | Noble Systems Corporation | Reviewing portions of telephone call recordings in a contact center using topic meta-data records |
Families Citing this family (227)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6430604B1 (en) * | 1999-08-03 | 2002-08-06 | International Business Machines Corporation | Technique for enabling messaging systems to use alternative message delivery mechanisms |
US6832245B1 (en) | 1999-12-01 | 2004-12-14 | At&T Corp. | System and method for analyzing communications of user messages to rank users and contacts based on message content |
US6999565B1 (en) | 2000-02-01 | 2006-02-14 | Envoyworldwide, Inc. | Multi-mode message routing and management |
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 |
US6842772B1 (en) | 2000-03-14 | 2005-01-11 | Envoy World Wide, Inc | Application program interface for message routing and management system |
US8645137B2 (en) | 2000-03-16 | 2014-02-04 | Apple Inc. | Fast, language-independent method for user authentication by voice |
DE60132433T2 (en) | 2000-03-17 | 2008-12-24 | America Online, Inc. | IMMEDIATE MESSAGE TRANSMISSION WITH ADDITIONAL LANGUAGE COMMUNICATION |
US9246975B2 (en) | 2000-03-17 | 2016-01-26 | Facebook, Inc. | State change alerts mechanism |
US7624172B1 (en) | 2000-03-17 | 2009-11-24 | Aol Llc | State change alerts mechanism |
US7979802B1 (en) | 2000-05-04 | 2011-07-12 | Aol Inc. | Providing supplemental contact information corresponding to a referenced individual |
US9100221B2 (en) | 2000-05-04 | 2015-08-04 | Facebook, Inc. | Systems for messaging senders and recipients of an electronic message |
US6912564B1 (en) | 2000-05-04 | 2005-06-28 | America Online, Inc. | System for instant messaging the sender and recipients of an e-mail message |
US8122363B1 (en) | 2000-05-04 | 2012-02-21 | Aol Inc. | Presence status indicator |
US20130073648A1 (en) | 2000-05-04 | 2013-03-21 | Facebook, Inc. | Presenting a recipient of an e-mail with an option to instant message a sender or another recipient based on the sender's or the other recipient's address and online status |
US20130067340A1 (en) * | 2000-05-04 | 2013-03-14 | Facebook, Inc. | Intelligently enabled menu choices based on online presence state in address book |
US8132110B1 (en) | 2000-05-04 | 2012-03-06 | Aol Inc. | Intelligently enabled menu choices based on online presence state in address book |
US8001190B2 (en) | 2001-06-25 | 2011-08-16 | Aol Inc. | Email integrated instant messaging |
WO2002009437A2 (en) | 2000-07-25 | 2002-01-31 | America Online, Inc. | Video messaging |
US8516047B2 (en) | 2000-11-06 | 2013-08-20 | Rick Castanho | System and method for service specific notification |
WO2002037393A2 (en) * | 2000-11-06 | 2002-05-10 | Envoy Worlwide, Inc. | System and method for service specific notification |
JP3866506B2 (en) * | 2000-12-04 | 2007-01-10 | 株式会社エヌ・ティ・ティ・ドコモ | E-mail delivery control method and mail server |
JP3825265B2 (en) * | 2001-02-07 | 2006-09-27 | 日本電信電話株式会社 | Kanmon connection device |
US20020129103A1 (en) * | 2001-03-12 | 2002-09-12 | Birkler J?Ouml;Rgen | Instant messaging presence service protocol |
WO2002087095A1 (en) | 2001-04-25 | 2002-10-31 | Envoy Worldwide, Inc. | Wireless messaging system to multiple |
US7409423B2 (en) * | 2001-06-28 | 2008-08-05 | Horvitz Eric J | Methods for and applications of learning and inferring the periods of time until people are available or unavailable for different forms of communication, collaboration, and information access |
JP2003044418A (en) * | 2001-07-27 | 2003-02-14 | Sharp Corp | Instant message transmission and reception system |
US7512652B1 (en) | 2001-09-28 | 2009-03-31 | Aol Llc, A Delaware Limited Liability Company | Passive personalization of buddy lists |
US7774711B2 (en) | 2001-09-28 | 2010-08-10 | Aol Inc. | Automatic categorization of entries in a contact list |
GB0125201D0 (en) * | 2001-10-19 | 2001-12-12 | Nokia Corp | A messaging system |
US7549096B2 (en) * | 2001-11-16 | 2009-06-16 | At&T Mobility Ii Llc | Methods and systems for tracking and playing back errors in a communications network |
US7487262B2 (en) * | 2001-11-16 | 2009-02-03 | At & T Mobility Ii, Llc | Methods and systems for routing messages through a communications network based on message content |
US7657253B2 (en) * | 2001-11-16 | 2010-02-02 | At&T Mobility Ii Llc | System and method for providing message notification |
US8660537B2 (en) | 2001-11-16 | 2014-02-25 | At&T Mobility Ii Llc | System for the storage and retrieval of messages |
US7454195B2 (en) | 2001-11-16 | 2008-11-18 | At&T Mobility Ii, Llc | System for the centralized storage of wireless customer information |
US7793334B2 (en) | 2001-11-16 | 2010-09-07 | At&T Mobility Ii Llc | System and method for password protecting a distribution list |
WO2003049384A1 (en) | 2001-12-07 | 2003-06-12 | Research In Motion Limited | System and method of managing information distribution to mobile stations |
GB0202370D0 (en) * | 2002-02-01 | 2002-03-20 | Symbian Ltd | Pinging |
EP1333689A1 (en) * | 2002-02-04 | 2003-08-06 | Siemens Aktiengesellschaft | Routing method and system with conditional logging |
JP2003271531A (en) * | 2002-03-18 | 2003-09-26 | Nec Corp | Message server, message system, presence information management method and program |
US7421580B2 (en) * | 2002-08-12 | 2008-09-02 | Aol Llc A Delaware Limited Liability Company | Method and apparatus for synchronizing e-mail addresses |
US7177414B1 (en) * | 2002-09-17 | 2007-02-13 | Bellsouth Intellectual Property Corporation | Call forwarding based on determination of status of destination |
JP3943467B2 (en) * | 2002-09-18 | 2007-07-11 | 株式会社エヌ・ティ・ティ・ドコモ | Relay device, information transmission device, and information transmission method |
US7590696B1 (en) | 2002-11-18 | 2009-09-15 | Aol Llc | Enhanced buddy list using mobile device identifiers |
US8005919B2 (en) | 2002-11-18 | 2011-08-23 | Aol Inc. | Host-based intelligent results related to a character stream |
US7428580B2 (en) | 2003-11-26 | 2008-09-23 | Aol Llc | Electronic message forwarding |
US8965964B1 (en) | 2002-11-18 | 2015-02-24 | Facebook, Inc. | Managing forwarded electronic messages |
US7640306B2 (en) | 2002-11-18 | 2009-12-29 | Aol Llc | Reconfiguring an electronic message to effect an enhanced notification |
US7899862B2 (en) | 2002-11-18 | 2011-03-01 | Aol Inc. | Dynamic identification of other users to an online user |
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 |
WO2004046867A2 (en) | 2002-11-18 | 2004-06-03 | America Online, Inc. | People lists |
US9742615B1 (en) | 2002-12-31 | 2017-08-22 | Aol Inc. | Popularity index |
US7945674B2 (en) | 2003-04-02 | 2011-05-17 | Aol Inc. | Degrees of separation for handling communications |
US7263614B2 (en) | 2002-12-31 | 2007-08-28 | Aol Llc | Implicit access for communications pathway |
JP3891939B2 (en) * | 2003-01-20 | 2007-03-14 | ソニー・エリクソン・モバイルコミュニケーションズ株式会社 | Message data processing method for portable communication terminal, portable communication terminal, message data processing program for portable communication terminal |
US7698367B2 (en) | 2003-03-06 | 2010-04-13 | Siemens Communications, Inc. | System and method for presence enabled e-mail delivery |
US7761516B2 (en) | 2003-03-06 | 2010-07-20 | Siemens Enterprise Communications, Inc. | System and method for e-mail presence confirmation |
US7603417B2 (en) | 2003-03-26 | 2009-10-13 | Aol Llc | Identifying and using identities deemed to be known to a user |
US7669134B1 (en) | 2003-05-02 | 2010-02-23 | Apple Inc. | Method and apparatus for displaying information during an instant messaging session |
US20050021645A1 (en) * | 2003-05-27 | 2005-01-27 | Kiran Kulkarni | Universal presence indicator and instant messaging system |
EP1494488A1 (en) * | 2003-07-01 | 2005-01-05 | Precisa Instruments AG | Mobile phone comprising position computation means |
US7653693B2 (en) | 2003-09-05 | 2010-01-26 | Aol Llc | Method and system for capturing instant messages |
JP2005050113A (en) * | 2003-07-28 | 2005-02-24 | Sony Corp | Instant message utilizing system, sending client, relay server, receiving client, method for using instant message, and its program |
US7613472B2 (en) * | 2003-09-17 | 2009-11-03 | Sony Ericsson Mobile Communications Ab | System and method of sharing a contact list among mobile phones |
US7088993B2 (en) * | 2003-09-24 | 2006-08-08 | Telefonaktiebolaget Lm Ericsson(Publ) | Optimized message notification |
US20050078668A1 (en) * | 2003-10-08 | 2005-04-14 | Wittenberg Joel L. | Network element having a redirect server |
KR100529931B1 (en) * | 2003-12-09 | 2005-11-22 | 엘지전자 주식회사 | Server system communicating through the wireless network |
US7559030B2 (en) * | 2003-12-09 | 2009-07-07 | Skyums Co. Ltd | Method of providing notification service of electronic mail transfer |
NO321223B1 (en) * | 2004-01-26 | 2006-04-10 | Telenor Asa | Procedure and facility for conditional forwarding of an IM message |
US8635273B2 (en) | 2004-03-05 | 2014-01-21 | Aol Inc. | Announcing new users of an electronic communications system to existing users |
US8595146B1 (en) | 2004-03-15 | 2013-11-26 | Aol Inc. | Social networking permissions |
US8635283B2 (en) * | 2004-04-05 | 2014-01-21 | International Business Machines Corporation | Tagging the seen/not-seen status of a real time message |
JP2006101205A (en) * | 2004-09-29 | 2006-04-13 | Sharp Corp | Facsimile machine |
US20060173966A1 (en) * | 2005-02-01 | 2006-08-03 | Jennings Raymond B Iii | Method and apparatus for inferring read status of instant messages |
US7353034B2 (en) | 2005-04-04 | 2008-04-01 | X One, Inc. | Location sharing and tracking using mobile phones or other wireless devices |
US20060274701A1 (en) * | 2005-06-03 | 2006-12-07 | Telefonaktiebolaget Lm Ericsson (Publ) | Means and method for notification |
KR100713537B1 (en) | 2005-08-08 | 2007-04-30 | 삼성전자주식회사 | Method for transmission and reception a message in mobile communication terminal |
US8677377B2 (en) | 2005-09-08 | 2014-03-18 | Apple Inc. | Method and apparatus for building an intelligent automated assistant |
GB2430582B (en) | 2005-09-26 | 2008-04-09 | Nec Technologies | Method of managing connectivity status for a mobile radio communications device, and such a device |
US20080052389A1 (en) * | 2006-08-24 | 2008-02-28 | George David A | Method and apparatus for inferring the busy state of an instant messaging user |
US9304675B2 (en) | 2006-09-06 | 2016-04-05 | Apple Inc. | Portable electronic device for instant messaging |
US8564544B2 (en) | 2006-09-06 | 2013-10-22 | Apple Inc. | Touch screen device, method, and graphical user interface for customizing display of content category icons |
US9318108B2 (en) | 2010-01-18 | 2016-04-19 | Apple Inc. | Intelligent automated assistant |
KR100797563B1 (en) * | 2006-09-26 | 2008-01-24 | 삼성전자주식회사 | Apparatus and method for transmission of message |
US8041024B2 (en) * | 2006-10-17 | 2011-10-18 | International Business Machines Corporation | Method and system for telephone number change notification and tracking |
US8000458B2 (en) * | 2006-11-10 | 2011-08-16 | International Business Machines Corporation | Method and system for verifying incoming telephone numbers |
US8977255B2 (en) | 2007-04-03 | 2015-03-10 | Apple Inc. | Method and system for operating a multi-function portable electronic device using voice-activation |
US8014512B2 (en) * | 2007-04-18 | 2011-09-06 | International Business Machines Corporation | Method and system for user interaction within a queue |
KR101303380B1 (en) * | 2007-05-16 | 2013-10-16 | 주식회사 케이티 | System and method for providing chatting service in public switched telephone network |
US9954996B2 (en) | 2007-06-28 | 2018-04-24 | Apple Inc. | Portable electronic device with conversation management for incoming instant messages |
US8136125B2 (en) * | 2007-10-02 | 2012-03-13 | International Business Machines Corporation | Prioritization for online contact status updates |
US9451038B2 (en) * | 2007-10-02 | 2016-09-20 | International Business Machines Corporation | Managing contact status updates in a presence management system |
US7885937B2 (en) * | 2007-10-02 | 2011-02-08 | International Business Machines Corporation | Mapping online contact information into a contacts list |
US9330720B2 (en) | 2008-01-03 | 2016-05-03 | Apple Inc. | Methods and apparatus for altering audio output signals |
US8327272B2 (en) | 2008-01-06 | 2012-12-04 | Apple Inc. | Portable multifunction device, method, and graphical user interface for viewing and managing electronic calendars |
US8595302B2 (en) | 2008-02-22 | 2013-11-26 | Qualcomm Incorporated | Method and apparatus for monitoring message status in an asynchronous mediated communication system |
US8149850B2 (en) | 2008-02-22 | 2012-04-03 | Qualcomm Incorporated | Method and apparatus for asynchronous mediated communicaton |
US8996376B2 (en) | 2008-04-05 | 2015-03-31 | Apple Inc. | Intelligent text-to-speech conversion |
US10496753B2 (en) | 2010-01-18 | 2019-12-03 | Apple Inc. | Automatically adapting user interfaces for hands-free interaction |
US8190990B2 (en) * | 2008-06-27 | 2012-05-29 | Google Inc. | Annotating webpage content |
WO2010009055A1 (en) * | 2008-07-14 | 2010-01-21 | Wuiper, Inc. | System and method for real world interface to online social networks |
US20100030549A1 (en) | 2008-07-31 | 2010-02-04 | Lee Michael M | Mobile device having human language translation capability with positional feedback |
US9356907B2 (en) * | 2008-08-05 | 2016-05-31 | HeyWire, Inc. | Messaging system having multiple number, dual mode phone support |
US20120221962A1 (en) | 2008-08-05 | 2012-08-30 | Eugene Lee Lew | Social messaging hub system |
US11172067B1 (en) | 2008-08-05 | 2021-11-09 | HeyWire, Inc. | Call center mobile messaging |
JP4864950B2 (en) * | 2008-09-16 | 2012-02-01 | パイオニア株式会社 | In-vehicle device, information communication system, in-vehicle device control method and program |
US9959870B2 (en) | 2008-12-11 | 2018-05-01 | Apple Inc. | Speech recognition involving a mobile device |
US8429236B2 (en) * | 2009-04-08 | 2013-04-23 | Research In Motion Limited | Transmission of status updates responsive to status of recipient application |
US20100281123A1 (en) * | 2009-05-04 | 2010-11-04 | Charles Greenberg | System and method for targeted communication |
US20100285822A1 (en) * | 2009-05-05 | 2010-11-11 | Carney Ii Conrad R | Next generation of marketing and method |
US10241644B2 (en) | 2011-06-03 | 2019-03-26 | Apple Inc. | Actionable reminder entries |
US10255566B2 (en) | 2011-06-03 | 2019-04-09 | Apple Inc. | Generating and processing task items that represent tasks to perform |
US10241752B2 (en) | 2011-09-30 | 2019-03-26 | Apple Inc. | Interface for a virtual digital assistant |
US9858925B2 (en) | 2009-06-05 | 2018-01-02 | Apple Inc. | Using context information to facilitate processing of commands in a virtual assistant |
US9431006B2 (en) | 2009-07-02 | 2016-08-30 | Apple Inc. | Methods and apparatuses for automatic speech recognition |
US10276170B2 (en) | 2010-01-18 | 2019-04-30 | Apple Inc. | Intelligent automated assistant |
US10679605B2 (en) | 2010-01-18 | 2020-06-09 | Apple Inc. | Hands-free list-reading by intelligent automated assistant |
US10705794B2 (en) | 2010-01-18 | 2020-07-07 | Apple Inc. | Automatically adapting user interfaces for hands-free interaction |
US10553209B2 (en) | 2010-01-18 | 2020-02-04 | Apple Inc. | Systems and methods for hands-free notification summaries |
US8977584B2 (en) | 2010-01-25 | 2015-03-10 | Newvaluexchange Global Ai Llp | Apparatuses, methods and systems for a digital conversation management platform |
US8682667B2 (en) | 2010-02-25 | 2014-03-25 | Apple Inc. | User profiling for selecting user specific voice input processing information |
US10762293B2 (en) | 2010-12-22 | 2020-09-01 | Apple Inc. | Using parts-of-speech tagging and named entity recognition for spelling correction |
EP2475138B1 (en) | 2011-01-06 | 2019-03-13 | BlackBerry Limited | Delivery and management of status notifications for group messaging |
US10110548B2 (en) | 2011-01-06 | 2018-10-23 | Blackberry Limited | Delivery and management of status notifications for multiple message formats |
US8819156B2 (en) | 2011-03-11 | 2014-08-26 | James Robert Miner | Systems and methods for message collection |
US9419928B2 (en) | 2011-03-11 | 2016-08-16 | James Robert Miner | Systems and methods for message collection |
US9262612B2 (en) | 2011-03-21 | 2016-02-16 | Apple Inc. | Device access using voice authentication |
US10057736B2 (en) | 2011-06-03 | 2018-08-21 | Apple Inc. | Active transport based notifications |
US8994660B2 (en) | 2011-08-29 | 2015-03-31 | Apple Inc. | Text correction processing |
US10134385B2 (en) | 2012-03-02 | 2018-11-20 | Apple Inc. | Systems and methods for name pronunciation |
US9483461B2 (en) | 2012-03-06 | 2016-11-01 | Apple Inc. | Handling speech synthesis of content for multiple languages |
US9280610B2 (en) | 2012-05-14 | 2016-03-08 | Apple Inc. | Crowd sourcing information to fulfill user requests |
US9721563B2 (en) | 2012-06-08 | 2017-08-01 | Apple Inc. | Name recognition system |
US9495129B2 (en) | 2012-06-29 | 2016-11-15 | Apple Inc. | Device, method, and user interface for voice-activated navigation and browsing of a document |
US9576574B2 (en) | 2012-09-10 | 2017-02-21 | Apple Inc. | Context-sensitive handling of interruptions by intelligent digital assistant |
US9547647B2 (en) | 2012-09-19 | 2017-01-17 | Apple Inc. | Voice-based media searching |
EP2954514B1 (en) | 2013-02-07 | 2021-03-31 | Apple Inc. | Voice trigger for a digital assistant |
KR102074940B1 (en) * | 2013-03-07 | 2020-03-02 | 삼성전자주식회사 | Method for transmitting and receiving message and apparatus for the same |
US9368114B2 (en) | 2013-03-14 | 2016-06-14 | Apple Inc. | Context-sensitive handling of interruptions |
WO2014144579A1 (en) | 2013-03-15 | 2014-09-18 | Apple Inc. | System and method for updating an adaptive speech recognition model |
AU2014233517B2 (en) | 2013-03-15 | 2017-05-25 | Apple Inc. | Training an at least partial voice command system |
CN103547342B (en) * | 2013-05-14 | 2018-02-06 | 华为技术有限公司 | Message method, message read notification method, message receival method and device |
WO2014197336A1 (en) | 2013-06-07 | 2014-12-11 | Apple Inc. | System and method for detecting errors in interactions with a voice-based digital assistant |
US9582608B2 (en) | 2013-06-07 | 2017-02-28 | Apple Inc. | Unified ranking with entropy-weighted information for phrase-based semantic auto-completion |
WO2014197334A2 (en) | 2013-06-07 | 2014-12-11 | Apple Inc. | System and method for user-specified pronunciation of words for speech synthesis and recognition |
WO2014197335A1 (en) | 2013-06-08 | 2014-12-11 | Apple Inc. | Interpreting and acting upon commands that involve sharing information with remote devices |
US10176167B2 (en) | 2013-06-09 | 2019-01-08 | Apple Inc. | System and method for inferring user intent from speech inputs |
WO2014200728A1 (en) | 2013-06-09 | 2014-12-18 | Apple Inc. | Device, method, and graphical user interface for enabling conversation persistence across two or more instances of a digital assistant |
AU2014278595B2 (en) | 2013-06-13 | 2017-04-06 | Apple Inc. | System and method for emergency calls initiated by voice command |
KR101749009B1 (en) | 2013-08-06 | 2017-06-19 | 애플 인크. | Auto-activating smart responses based on activities from remote devices |
CN103746906A (en) * | 2014-01-22 | 2014-04-23 | 北京奇虎科技有限公司 | Method, device and system for pushing mobile terminal to control PC (personal computer) operation-related message |
US9620105B2 (en) | 2014-05-15 | 2017-04-11 | Apple Inc. | Analyzing audio input for efficient speech and music recognition |
US10592095B2 (en) | 2014-05-23 | 2020-03-17 | Apple Inc. | Instantaneous speaking of content on touch devices |
US9502031B2 (en) | 2014-05-27 | 2016-11-22 | Apple Inc. | Method for supporting dynamic grammars in WFST-based ASR |
US10170123B2 (en) | 2014-05-30 | 2019-01-01 | Apple Inc. | Intelligent assistant for home automation |
US9734193B2 (en) | 2014-05-30 | 2017-08-15 | Apple Inc. | Determining domain salience ranking from ambiguous words in natural speech |
US9430463B2 (en) | 2014-05-30 | 2016-08-30 | Apple Inc. | Exemplar-based natural language processing |
US9760559B2 (en) | 2014-05-30 | 2017-09-12 | Apple Inc. | Predictive text input |
US10078631B2 (en) | 2014-05-30 | 2018-09-18 | Apple Inc. | Entropy-guided text prediction using combined word and character n-gram language models |
US10289433B2 (en) | 2014-05-30 | 2019-05-14 | Apple Inc. | Domain specific language for encoding assistant dialog |
US9633004B2 (en) | 2014-05-30 | 2017-04-25 | Apple Inc. | Better resolution when referencing to concepts |
US9842101B2 (en) | 2014-05-30 | 2017-12-12 | Apple Inc. | Predictive conversion of language input |
US9785630B2 (en) | 2014-05-30 | 2017-10-10 | Apple Inc. | Text prediction using combined word N-gram and unigram language models |
US9715875B2 (en) | 2014-05-30 | 2017-07-25 | Apple Inc. | Reducing the need for manual start/end-pointing and trigger phrases |
US9966065B2 (en) | 2014-05-30 | 2018-05-08 | Apple Inc. | Multi-command single utterance input method |
US9338493B2 (en) | 2014-06-30 | 2016-05-10 | Apple Inc. | Intelligent automated assistant for TV user interactions |
US10659851B2 (en) | 2014-06-30 | 2020-05-19 | Apple Inc. | Real-time digital assistant knowledge updates |
US10446141B2 (en) | 2014-08-28 | 2019-10-15 | Apple Inc. | Automatic speech recognition based on user feedback |
US9818400B2 (en) | 2014-09-11 | 2017-11-14 | Apple Inc. | Method and apparatus for discovering trending terms in speech requests |
US10789041B2 (en) | 2014-09-12 | 2020-09-29 | Apple Inc. | Dynamic thresholds for always listening speech trigger |
US9886432B2 (en) | 2014-09-30 | 2018-02-06 | Apple Inc. | Parsimonious handling of word inflection via categorical stem + suffix N-gram language models |
US10127911B2 (en) | 2014-09-30 | 2018-11-13 | Apple Inc. | Speaker identification and unsupervised speaker adaptation techniques |
US9668121B2 (en) | 2014-09-30 | 2017-05-30 | Apple Inc. | Social reminders |
US9646609B2 (en) | 2014-09-30 | 2017-05-09 | Apple Inc. | Caching apparatus for serving phonetic pronunciations |
US10074360B2 (en) | 2014-09-30 | 2018-09-11 | Apple Inc. | Providing an indication of the suitability of speech recognition |
US10552013B2 (en) | 2014-12-02 | 2020-02-04 | Apple Inc. | Data detection |
US9711141B2 (en) | 2014-12-09 | 2017-07-18 | Apple Inc. | Disambiguating heteronyms in speech synthesis |
JP6464802B2 (en) * | 2015-02-19 | 2019-02-06 | 株式会社ナカヨ | Presence information management apparatus, program, and presence information management method |
US9865280B2 (en) | 2015-03-06 | 2018-01-09 | Apple Inc. | Structured dictation using intelligent automated assistants |
US9886953B2 (en) | 2015-03-08 | 2018-02-06 | Apple Inc. | Virtual assistant activation |
US9721566B2 (en) | 2015-03-08 | 2017-08-01 | Apple Inc. | Competing devices responding to voice triggers |
US10567477B2 (en) | 2015-03-08 | 2020-02-18 | Apple Inc. | Virtual assistant continuity |
US9899019B2 (en) | 2015-03-18 | 2018-02-20 | Apple Inc. | Systems and methods for structured stem and suffix language models |
US9842105B2 (en) | 2015-04-16 | 2017-12-12 | Apple Inc. | Parsimonious continuous-space phrase representations for natural language processing |
US10083688B2 (en) | 2015-05-27 | 2018-09-25 | Apple Inc. | Device voice control for selecting a displayed affordance |
US10127220B2 (en) | 2015-06-04 | 2018-11-13 | Apple Inc. | Language identification from short strings |
US9578173B2 (en) | 2015-06-05 | 2017-02-21 | Apple Inc. | Virtual assistant aided communication with 3rd party service in a communication session |
US10101822B2 (en) | 2015-06-05 | 2018-10-16 | Apple Inc. | Language input correction |
US10186254B2 (en) | 2015-06-07 | 2019-01-22 | Apple Inc. | Context-based endpoint detection |
US10255907B2 (en) | 2015-06-07 | 2019-04-09 | Apple Inc. | Automatic accent detection using acoustic models |
US11025565B2 (en) | 2015-06-07 | 2021-06-01 | Apple Inc. | Personalized prediction of responses for instant messaging |
US10671428B2 (en) | 2015-09-08 | 2020-06-02 | Apple Inc. | Distributed personal assistant |
US10747498B2 (en) | 2015-09-08 | 2020-08-18 | Apple Inc. | Zero latency digital assistant |
US9697820B2 (en) | 2015-09-24 | 2017-07-04 | Apple Inc. | Unit-selection text-to-speech synthesis using concatenation-sensitive neural networks |
US11010550B2 (en) | 2015-09-29 | 2021-05-18 | Apple Inc. | Unified language modeling framework for word prediction, auto-completion and auto-correction |
US10366158B2 (en) | 2015-09-29 | 2019-07-30 | Apple Inc. | Efficient word encoding for recurrent neural network language models |
US11587559B2 (en) | 2015-09-30 | 2023-02-21 | Apple Inc. | Intelligent device identification |
US10691473B2 (en) | 2015-11-06 | 2020-06-23 | Apple Inc. | Intelligent automated assistant in a messaging environment |
US10049668B2 (en) | 2015-12-02 | 2018-08-14 | Apple Inc. | Applying neural network language models to weighted finite state transducers for automatic speech recognition |
JP6215292B2 (en) | 2015-12-22 | 2017-10-18 | Line株式会社 | Communication control method, information processing apparatus, and program |
US10223066B2 (en) | 2015-12-23 | 2019-03-05 | Apple Inc. | Proactive assistance based on dialog communication between devices |
US10263930B2 (en) * | 2016-03-03 | 2019-04-16 | Genband Us Llc | System and method for blocking notification messages during screen sharing |
US10446143B2 (en) | 2016-03-14 | 2019-10-15 | Apple Inc. | Identification of voice inputs providing credentials |
JP2017167366A (en) * | 2016-03-16 | 2017-09-21 | Kddi株式会社 | Communication terminal, communication method, and program |
US9934775B2 (en) | 2016-05-26 | 2018-04-03 | Apple Inc. | Unit-selection text-to-speech synthesis based on predicted concatenation parameters |
US9972304B2 (en) | 2016-06-03 | 2018-05-15 | Apple Inc. | Privacy preserving distributed evaluation framework for embedded personalized systems |
US10249300B2 (en) | 2016-06-06 | 2019-04-02 | Apple Inc. | Intelligent list reading |
US10049663B2 (en) | 2016-06-08 | 2018-08-14 | Apple, Inc. | Intelligent automated assistant for media exploration |
DK179309B1 (en) | 2016-06-09 | 2018-04-23 | Apple Inc | Intelligent automated assistant in a home environment |
US10509862B2 (en) | 2016-06-10 | 2019-12-17 | Apple Inc. | Dynamic phrase expansion of language input |
US10067938B2 (en) | 2016-06-10 | 2018-09-04 | Apple Inc. | Multilingual word prediction |
US10490187B2 (en) | 2016-06-10 | 2019-11-26 | Apple Inc. | Digital assistant providing automated status report |
US10586535B2 (en) | 2016-06-10 | 2020-03-10 | Apple Inc. | Intelligent digital assistant in a multi-tasking environment |
US10192552B2 (en) | 2016-06-10 | 2019-01-29 | Apple Inc. | Digital assistant providing whispered speech |
DK201670540A1 (en) | 2016-06-11 | 2018-01-08 | Apple Inc | Application integration with a digital assistant |
DK179343B1 (en) | 2016-06-11 | 2018-05-14 | Apple Inc | Intelligent task discovery |
DK179049B1 (en) | 2016-06-11 | 2017-09-18 | Apple Inc | Data driven natural language event detection and classification |
DK179415B1 (en) | 2016-06-11 | 2018-06-14 | Apple Inc | Intelligent device arbitration and control |
US10043516B2 (en) | 2016-09-23 | 2018-08-07 | Apple Inc. | Intelligent automated assistant |
US10593346B2 (en) | 2016-12-22 | 2020-03-17 | Apple Inc. | Rank-reduced token representation for automatic speech recognition |
DK201770439A1 (en) | 2017-05-11 | 2018-12-13 | Apple Inc. | Offline personal assistant |
DK179745B1 (en) | 2017-05-12 | 2019-05-01 | Apple Inc. | SYNCHRONIZATION AND TASK DELEGATION OF A DIGITAL ASSISTANT |
DK179496B1 (en) | 2017-05-12 | 2019-01-15 | Apple Inc. | USER-SPECIFIC Acoustic Models |
DK201770431A1 (en) | 2017-05-15 | 2018-12-20 | Apple Inc. | Optimizing dialogue policy decisions for digital assistants using implicit feedback |
DK201770432A1 (en) | 2017-05-15 | 2018-12-21 | Apple Inc. | Hierarchical belief states for digital assistants |
DK179560B1 (en) | 2017-05-16 | 2019-02-18 | Apple Inc. | Far-field extension for digital assistant services |
Citations (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5701343A (en) * | 1994-12-01 | 1997-12-23 | Nippon Telegraph & Telephone Corporation | Method and system for digital information protection |
US5706211A (en) * | 1995-03-02 | 1998-01-06 | Motorola, Inc. | Message communications system |
US5757901A (en) * | 1995-03-16 | 1998-05-26 | Fujitsu Limited | Call transfer system and electronic mail transfer system |
US5844969A (en) * | 1997-01-23 | 1998-12-01 | At&T Corp. | Communication system, method and device for remotely re-transmitting received electronic mail directed to a destination terminal to a new destination terminal |
US5872926A (en) * | 1996-05-31 | 1999-02-16 | Adaptive Micro Systems, Inc. | Integrated message system |
US5903557A (en) * | 1996-09-30 | 1999-05-11 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for determining activation status of a receiving station of a radio communication system |
US6032051A (en) * | 1997-12-01 | 2000-02-29 | Telefonaktiebolaget L/M Ericsson | Wireless mobile comunication devices for group use |
US6035198A (en) * | 1996-09-02 | 2000-03-07 | Siemens Aktiengesellschaft | Method and system for determining the location of a mobile radiocommunication subscriber registered in a cellular mobile radiotelephone network |
US6093146A (en) * | 1998-06-05 | 2000-07-25 | Matsushita Electric Works, Ltd. | Physiological monitoring |
US6108688A (en) * | 1996-06-12 | 2000-08-22 | Sun Microsystems, Inc. | System for reminding a sender of an email if recipient of the email does not respond by a selected time set by the sender |
US6128512A (en) * | 1995-09-06 | 2000-10-03 | Cisco Systems, Inc. | Cellular communication system with dedicated repeater channels |
US6157941A (en) * | 1998-03-18 | 2000-12-05 | Oracle Corporation | Architecture for client-server communication over a communication link |
US6178331B1 (en) * | 1997-06-17 | 2001-01-23 | Bulletin.Net, Inc. | System and process for allowing wireless messaging |
US6182144B1 (en) * | 1997-12-12 | 2001-01-30 | Intel Corporation | Means and method for switching between a narrow band communication and a wide band communication to establish a continuous connection with mobile computers |
US6219694B1 (en) * | 1998-05-29 | 2001-04-17 | Research In Motion Limited | System and method for pushing information from a host system to a mobile data communication device having a shared electronic address |
US6237027B1 (en) * | 1996-06-20 | 2001-05-22 | Sony Corporation | Electronic mail system, computer device, and remote notification method |
US20010011303A1 (en) * | 1997-05-09 | 2001-08-02 | Jack H. Chang | System and method for managing multimedia messaging platforms |
US6334140B1 (en) * | 1997-09-25 | 2001-12-25 | Nec Corporation | Electronic mail server in which electronic mail is processed |
US6512930B2 (en) * | 1997-12-30 | 2003-01-28 | Telefonaktiebolaget Lm Ericsson (Publ) | On-line notification in a mobile communications system |
US6519471B1 (en) * | 1997-12-27 | 2003-02-11 | Casio Computer Co., Ltd. | Portable electronic mail apparatus and storage medium storing electronic mail program |
Family Cites Families (34)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPS57147748A (en) | 1981-03-09 | 1982-09-11 | Canon Inc | Character processor |
JPS58132849A (en) | 1983-01-17 | 1983-08-08 | Sharp Corp | Electronic device |
JPS6125331A (en) | 1984-07-13 | 1986-02-04 | Matsushita Electric Ind Co Ltd | Communication equipment |
JPS61100860A (en) | 1984-10-22 | 1986-05-19 | Nec Corp | Selective inputting system |
JP3038684B2 (en) | 1985-12-23 | 2000-05-08 | 松下電工株式会社 | Image transmission method |
JPS62160557A (en) | 1986-01-10 | 1987-07-16 | Canon Inc | Personal computer |
JPH01297956A (en) | 1988-05-25 | 1989-12-01 | Nec Corp | Message transmission system |
JPH0258464A (en) | 1988-08-24 | 1990-02-27 | Toshiba Corp | Character message display system for private branch exchange system |
JPH0773377B2 (en) | 1989-07-31 | 1995-08-02 | 日本電気株式会社 | Wireless selective call receiver |
JPH03113953A (en) | 1989-09-27 | 1991-05-15 | Nec Corp | Electronic pushbutton telephone set |
JPH0834493B2 (en) | 1990-01-26 | 1996-03-29 | 富士通株式会社 | Transmission message processing method in communication system |
JP2858991B2 (en) | 1991-04-15 | 1999-02-17 | 日本電気株式会社 | Radio selective call receiver |
JPH04337794A (en) | 1991-05-15 | 1992-11-25 | Sofuteikusu:Kk | Data input device and data display device |
JPH04344787A (en) | 1991-05-21 | 1992-12-01 | Canon Inc | Visual telephone |
JP3108465B2 (en) | 1991-07-10 | 2000-11-13 | 株式会社東芝 | Personal communication system |
JPH05167610A (en) * | 1991-12-11 | 1993-07-02 | Mitsubishi Electric Corp | Electronic mail system |
JPH05199158A (en) | 1992-09-17 | 1993-08-06 | Casio Comput Co Ltd | Paging receiver provided with message information reception function |
JPH0772923A (en) | 1993-09-02 | 1995-03-17 | Mitsubishi Electric Corp | Remote supervisory equipment |
JPH0779485A (en) | 1993-09-06 | 1995-03-20 | Canon Inc | Simple portable telephone system and distributed video conference system |
JPH08237370A (en) | 1995-02-27 | 1996-09-13 | Nec Eng Ltd | Reporting system for storing message |
JPH0918509A (en) * | 1995-06-28 | 1997-01-17 | Matsushita Electric Ind Co Ltd | Electronic mail device |
JP3660942B2 (en) | 1995-07-25 | 2005-06-15 | 雅信 鯨田 | What to do when there is an external call to a mobile phone and a mobile phone carried by an individual during a meeting or business talk |
EP0777394A1 (en) * | 1995-12-01 | 1997-06-04 | ALCATEL BELL Naamloze Vennootschap | Method and apparatus for electronic mail transmission as short messages towards a mobile radio terminal |
JPH09160855A (en) * | 1995-12-11 | 1997-06-20 | Atsushi Matsushita | Data communication system by computer device |
JPH09191309A (en) | 1996-01-09 | 1997-07-22 | Fujitsu Ltd | Multi-cast communication system |
JPH1013461A (en) | 1996-06-25 | 1998-01-16 | Canon Inc | Message delivery supporting system and method |
JP3581218B2 (en) * | 1996-07-03 | 2004-10-27 | 株式会社東芝 | Mobile communication terminal device and its mobile phone and data terminal device |
JPH1066134A (en) | 1996-08-19 | 1998-03-06 | Nec Corp | Inter-exchange handover method |
JP3629107B2 (en) * | 1996-09-27 | 2005-03-16 | 三菱電機株式会社 | E-mail system using mobile phone with incoming call notification |
JPH10107914A (en) | 1996-10-01 | 1998-04-24 | Canon Inc | Information processing unit and its method |
IL119364A (en) * | 1996-10-06 | 2000-11-21 | Icq Inc | Communications system |
JP3038684U (en) * | 1996-12-12 | 1997-06-24 | アイコム株式会社 | Call control device |
JP3500261B2 (en) | 1996-12-20 | 2004-02-23 | セイコーエプソン株式会社 | Processing terminal device, information providing system, information obtaining method, and information providing method |
JP3350412B2 (en) | 1997-09-24 | 2002-11-25 | 富士通株式会社 | Private branch exchange system |
-
1998
- 1998-08-06 JP JP22265598A patent/JP3865946B2/en not_active Expired - Fee Related
-
1999
- 1999-04-30 EP EP19990918310 patent/EP1102443B1/en not_active Expired - Lifetime
- 1999-04-30 WO PCT/JP1999/002353 patent/WO2000008813A1/en active Application Filing
-
2001
- 2001-01-30 US US09/772,000 patent/US7437413B2/en not_active Expired - Fee Related
-
2008
- 2008-05-09 US US12/149,951 patent/US20090082044A1/en not_active Abandoned
Patent Citations (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5701343A (en) * | 1994-12-01 | 1997-12-23 | Nippon Telegraph & Telephone Corporation | Method and system for digital information protection |
US5706211A (en) * | 1995-03-02 | 1998-01-06 | Motorola, Inc. | Message communications system |
US5757901A (en) * | 1995-03-16 | 1998-05-26 | Fujitsu Limited | Call transfer system and electronic mail transfer system |
US6128512A (en) * | 1995-09-06 | 2000-10-03 | Cisco Systems, Inc. | Cellular communication system with dedicated repeater channels |
US5872926A (en) * | 1996-05-31 | 1999-02-16 | Adaptive Micro Systems, Inc. | Integrated message system |
US6108688A (en) * | 1996-06-12 | 2000-08-22 | Sun Microsystems, Inc. | System for reminding a sender of an email if recipient of the email does not respond by a selected time set by the sender |
US6237027B1 (en) * | 1996-06-20 | 2001-05-22 | Sony Corporation | Electronic mail system, computer device, and remote notification method |
US6035198A (en) * | 1996-09-02 | 2000-03-07 | Siemens Aktiengesellschaft | Method and system for determining the location of a mobile radiocommunication subscriber registered in a cellular mobile radiotelephone network |
US5903557A (en) * | 1996-09-30 | 1999-05-11 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for determining activation status of a receiving station of a radio communication system |
US5844969A (en) * | 1997-01-23 | 1998-12-01 | At&T Corp. | Communication system, method and device for remotely re-transmitting received electronic mail directed to a destination terminal to a new destination terminal |
US20010011303A1 (en) * | 1997-05-09 | 2001-08-02 | Jack H. Chang | System and method for managing multimedia messaging platforms |
US6178331B1 (en) * | 1997-06-17 | 2001-01-23 | Bulletin.Net, Inc. | System and process for allowing wireless messaging |
US6334140B1 (en) * | 1997-09-25 | 2001-12-25 | Nec Corporation | Electronic mail server in which electronic mail is processed |
US6032051A (en) * | 1997-12-01 | 2000-02-29 | Telefonaktiebolaget L/M Ericsson | Wireless mobile comunication devices for group use |
US6182144B1 (en) * | 1997-12-12 | 2001-01-30 | Intel Corporation | Means and method for switching between a narrow band communication and a wide band communication to establish a continuous connection with mobile computers |
US6519471B1 (en) * | 1997-12-27 | 2003-02-11 | Casio Computer Co., Ltd. | Portable electronic mail apparatus and storage medium storing electronic mail program |
US6512930B2 (en) * | 1997-12-30 | 2003-01-28 | Telefonaktiebolaget Lm Ericsson (Publ) | On-line notification in a mobile communications system |
US6157941A (en) * | 1998-03-18 | 2000-12-05 | Oracle Corporation | Architecture for client-server communication over a communication link |
US6219694B1 (en) * | 1998-05-29 | 2001-04-17 | Research In Motion Limited | System and method for pushing information from a host system to a mobile data communication device having a shared electronic address |
US6701378B1 (en) * | 1998-05-29 | 2004-03-02 | Research In Motion Limited | System and method for pushing information from a host system to a mobile data communication device |
US6093146A (en) * | 1998-06-05 | 2000-07-25 | Matsushita Electric Works, Ltd. | Physiological monitoring |
Cited By (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8239457B1 (en) * | 1999-12-17 | 2012-08-07 | Ipcom Gmbh & Co. Kg | Method for transmission of an electronic post message |
US8675831B2 (en) * | 2006-10-24 | 2014-03-18 | Alcatel Lucent | Storage of data messages for later retrieval by the recipient |
US20080095337A1 (en) * | 2006-10-24 | 2008-04-24 | Yigang Cai | Storage of data messages for later retrieval by the recipient |
US8972505B2 (en) * | 2008-10-07 | 2015-03-03 | Sun Management, Llc | Method and system for maintaining contact information |
US20140156760A1 (en) * | 2008-10-07 | 2014-06-05 | Mingoe Inc. | Method and system for maintaining contact information |
US9374459B1 (en) | 2012-05-01 | 2016-06-21 | Noble Systems Corporation | Integrating two-dimensional bar codes and embedded links with call center operation |
US9712677B1 (en) | 2012-05-01 | 2017-07-18 | Noble Systems Corporation | Integrating two-dimensional barcodes and embedded links with call center operation |
US8548133B1 (en) | 2012-05-01 | 2013-10-01 | Noble Systems Corporation | Managing electronic consent for calling campaigns |
US8781107B1 (en) | 2012-05-01 | 2014-07-15 | Noble Systems Corporation | Managing electronic consent for calling campaigns |
US8787953B1 (en) | 2012-05-01 | 2014-07-22 | Noble Systems Corporation | Integrating two-dimensional barcodes and embedded links with call center operation |
US9602663B1 (en) | 2012-05-01 | 2017-03-21 | Noble Systems Corporation | Managing electronic consent for calling campaigns |
US9384379B1 (en) | 2012-05-01 | 2016-07-05 | Noble Systems Corporation | Using quick response code to generate an electronic consent database |
US8526922B1 (en) * | 2012-05-01 | 2013-09-03 | Noble Systems Corporation | Integrating two-dimensional barcodes and embedded links with call center operation |
US9172783B1 (en) | 2012-05-01 | 2015-10-27 | Noble Systems Corporation | Integrating two-dimensional barcodes and embedded links with call center operation |
US9256774B1 (en) | 2012-05-01 | 2016-02-09 | Noble Systems Corporation | Using quick response codes to generate an electronic consent database |
US8532283B1 (en) | 2012-05-14 | 2013-09-10 | Noble Systems Corporation | Integrating embedded links with call center operation |
US8774391B1 (en) | 2012-05-14 | 2014-07-08 | Noble Systems Corporation | Integrating embedded links with call center operation |
CN104333852A (en) * | 2014-01-23 | 2015-02-04 | 广州三星通信技术研究有限公司 | Processing method and system of status of message |
CN103944979A (en) * | 2014-04-09 | 2014-07-23 | Tcl集团股份有限公司 | Method, device and system for message pushing |
US9936066B1 (en) | 2016-03-16 | 2018-04-03 | Noble Systems Corporation | Reviewing portions of telephone call recordings in a contact center using topic meta-data records |
US10306055B1 (en) | 2016-03-16 | 2019-05-28 | Noble Systems Corporation | Reviewing portions of telephone call recordings in a contact center using topic meta-data records |
US9848082B1 (en) | 2016-03-28 | 2017-12-19 | Noble Systems Corporation | Agent assisting system for processing customer enquiries in a contact center |
Also Published As
Publication number | Publication date |
---|---|
US7437413B2 (en) | 2008-10-14 |
EP1102443A1 (en) | 2001-05-23 |
EP1102443B1 (en) | 2009-07-01 |
EP1102443A4 (en) | 2005-03-16 |
US20010005859A1 (en) | 2001-06-28 |
JP3865946B2 (en) | 2007-01-10 |
JP2000059422A (en) | 2000-02-25 |
WO2000008813A1 (en) | 2000-02-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7437413B2 (en) | Text messaging system and method | |
US6463142B1 (en) | Messaging system with automatic proxy service | |
US8315651B2 (en) | Instant messaging to a mobile device | |
US7103333B2 (en) | System and method of exchanging identification information for mobile stations | |
US7023964B2 (en) | Communication system | |
US7983657B2 (en) | Presence and session handling information | |
US20050037741A1 (en) | System and method for telephonic presence via e-mail and short message service | |
US20030023691A1 (en) | Routing messages using presence information | |
US20020129109A1 (en) | Electronic mail processing system and mail server | |
GB2374255A (en) | Delivering multimedia messages in a format that is capable of being received by the recipient | |
CA2399144C (en) | An email system, a server, and an email transmitting and receiving apparatus | |
US6865385B1 (en) | Status notification method and status notification system | |
KR100779012B1 (en) | System and method for communicating between different messengers | |
US6944271B2 (en) | Information delivery management apparatus, system, and method | |
US7415516B1 (en) | Net lurkers | |
KR100385146B1 (en) | A web messenger service system and a service method on the network | |
JP4550025B2 (en) | 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 Text message communication management method | |
JP2006352903A5 (en) | ||
JP2003283567A (en) | Data communication system and method, server device, client device, repeater, and program | |
JP2000307724A (en) | Key telephone system, electronic mail system using it, mail arrival notice and transfer method | |
JP3909003B2 (en) | Message delivery system and method, program, and recording medium | |
JP2001308903A (en) | Information communication method, information communication system and recording medium | |
KR100479157B1 (en) | Dual web mail service system using pc mail server and host mail server | |
KR100458512B1 (en) | E-Mail Confirmation System And Method Using Keyphone System | |
JP5127478B2 (en) | Communication device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |