Message transmission/receipt system, server device, server processing program, and information providing method
Abstract
[Subject] Even if exchange of an instant message is in a difficult state and a partner's user does not know a partner's e-mail address, a partner enables it to have a dialog using a mobile communications terminal. [Solution means] When a user's present state information in two or more terminal units which have a messenger function, and the above-mentioned terminal unit is managed for every user and a user's change of the present state is detected, It is a message transceiver system consisting of the server device which transmits the state information which shows the state after change of the user concerned to other users' terminal unit, and memorizes an e-mail address for every user so that distinction is possible. As opposed to the user of other above-mentioned terminal units which the above-mentioned terminal unit receives the state information transmitted from the above-mentioned server device, and have been the receptionist targets of the E-mail, if a message is transmitted, a server device will generate an E-mail based on the message transmitted from the terminal unit -- being concerned -- others -- it transmits to addressing to an e-mail address of the user of a terminal unit. [Selection figure] Fig. 10
Term
No projected expiry on record.
- Priority and filed
- Published
- Today
6 claims: 3 independent, 3 dependent
- 1A plurality of terminal devices having a messenger function capable of sending and receiving a message instructed by a user to and from another terminal device via a network, and state information indicating the current state of the user in each of the terminal devices. Is managed for each user, and at least when a change in the current state of the user is detected, the state information transmitting means for transmitting the state information indicating the changed state of the user to the terminal device of the other user is used. A message transmission / reception system including a server device having a storage means for identifiablely storing an e-mail address for each user, wherein the terminal device stores the state information transmitted from the server device. When a message is transmitted to the receiving state information receiving means and another user of the terminal device whose state information indicates a specific state for receiving e-mail, the message is sent to the second server. The server device is provided with a message transmitting means for transmitting to the device. When the message transmitted from the terminal device is received, an e-mail is generated based on the received message, and the e-mail is transmitted to the e-mail address of the user of the other terminal device. A message transmission / reception system characterized by providing means. ネットワークを通じて他の端末装置との間で、ユーザから指示されたメッセージの送受信を行うことが可能なメッセンジャー機能を有する複数の端末装置と、 夫々の前記端末装置におけるユーザの現在の状態を示す状態情報を当該ユーザ毎に管理し、少なくとも、前記ユーザの現在の状態の変更を検知したとき、当該ユーザの変更後の状態を示す状態情報を前記他のユーザの端末装置に送信する状態情報送信手段と、電子メールアドレスを前記ユーザ毎に判別可能に記憶する記憶手段と、を有するサーバ装置と、 を備えるメッセージ送受信システムであって、 前記端末装置は、 前記サーバ装置から送信されてきた前記状態情報を受信する状態情報受信手段と、 前記状態情報が電子メールの受付対象とする特定の状態を示す他の前記端末装置のユーザに対してメッセージを送信する場合には、当該メッセージを前記第2のサーバ装置に送信するメッセージ送信手段と、 を備え、 前記サーバ装置は、 前記端末装置から送信されてきた前記メッセージを受信したとき、当該受信したメッセージに基づき電子メールを生成し、当該電子メールを、当該他の端末装置のユーザの電子メールアドレス宛てに送信する電子メール送信手段を備えることを特徴とするメッセージ送受信システム。
- 2Management of status information indicating the current status of a user in each of a plurality of terminal devices having a messenger function capable of sending and receiving a message instructed by a user to and from another terminal device via a network for each user. At least, in the server device provided with the state information transmitting means for transmitting the state information indicating the changed state of the user to the terminal device of the other user when the change of the current state of the user is detected. When the storage means for identifiablely storing the e-mail address for each user and the message transmitted from the terminal device are received, an e-mail is generated based on the received message, and the e-mail is stored in the e-mail. A server device including an e-mail sending means for sending to the e-mail address of a user of another terminal device. ネットワークを通じて他の端末装置との間で、ユーザから指示されたメッセージの送受信を行うことが可能なメッセンジャー機能を有する複数の端末装置夫々におけるユーザの現在の状態を示す状態情報を当該ユーザ毎に管理し、少なくとも、前記ユーザの現在の状態の変更を検知したとき、当該ユーザの変更後の状態を示す状態情報を前記他のユーザの端末装置に送信する状態情報送信手段を備えたサーバ装置において、 電子メールアドレスを前記ユーザ毎に判別可能に記憶する記憶手段と、 前記端末装置から送信されてきた前記メッセージを受信したとき、当該受信したメッセージに基づき電子メールを生成し、当該電子メールを、当該他の端末装置のユーザの電子メールアドレス宛てに送信する電子メール送信手段と、 を備えることを特徴とするサーバ装置。
- 6Management of status information indicating the current status of a user in each of a plurality of terminal devices having a messenger function capable of sending and receiving a message instructed by a user to and from another terminal device via a network for each user. However, at least, it is an information providing method in the server device that transmits the state information indicating the changed state of the user to the terminal device of the other user when the change of the current state of the user is detected. An e-mail address is identifiable for each user, and when the message sent from the terminal device is received, an e-mail is generated based on the received message, and the e-mail is stored in the other terminal device. An information providing method characterized by sending to the e-mail address of the user. ネットワークを通じて他の端末装置との間で、ユーザから指示されたメッセージの送受信を行うことが可能なメッセンジャー機能を有する複数の端末装置夫々におけるユーザの現在の状態を示す状態情報を当該ユーザ毎に管理し、少なくとも、前記ユーザの現在の状態の変更を検知したとき、当該ユーザの変更後の状態を示す状態情報を前記他のユーザの端末装置に送信するサーバ装置における情報提供方法であって、 電子メールアドレスを前記ユーザ毎に判別可能に記憶し、 前記端末装置から送信されてきた前記メッセージを受信したとき、当該受信したメッセージに基づき電子メールを生成し、当該電子メールを、当該他の端末装置のユーザの電子メールアドレス宛てに送信することを特徴とする情報提供方法。
Independent claims3
187 paragraphs, as filed
The present invention relates to a technical field such as a message transmission / reception system capable of transmitting / receiving a message between terminal devices via a network.
Conventionally, an instant messenger (also called an IM client) that can exchange text messages (generally called instant messages) between terminal devices such as personal computers via networks such as the Internet and intranets, is a communication application installed on the terminal devices. Software) is widespread (see, for example, Patent Document 1).
In such an instant messenger, presence information indicating the current state (for example, online or offline) of a user (a friend record member described later) with whom an instant message is exchanged can be displayed on a terminal device. It has become.<patcit num="1"><text>Japanese Unexamined Patent Publication No. 2003-44418</text></patcit>
<p> By the way, in the conventional instant messenger, the user cannot exchange instant messages when the other user is away from the terminal device (for example, while eating or returning home), for example, when he / she is offline. was there. In such a case, the user may make a call to a mobile communication terminal such as a mobile phone owned by the other user, or send an e-mail to the mobile communication terminal. If you do not know the telephone number or e-mail address of the user's mobile communication terminal, you cannot interact with the other user (for example, by voice or text).</p><p> The present invention has been made in view of such a point, and one example of the problem is that it is difficult for the other user to exchange instant messages, and the e-mail address of the other user is used. It is an object of the present invention to provide a message transmission / reception system, a server device, a server processing program, and an information providing method capable of a dialogue between a partner user using a mobile communication terminal even if he / she does not know it.</p>
<p> In order to solve the above problems, the invention according to claim 1 is a plurality of terminal devices having a messenger function capable of transmitting and receiving a message instructed by a user to and from another terminal device via a network. And, the state information indicating the current state of the user in each of the terminal devices is managed for each user, and at least when a change in the current state of the user is detected, the state indicating the changed state of the user is indicated. A message transmission / reception system including a server device having a state information transmitting means for transmitting information to the terminal device of the other user and a storage means for storing an e-mail address in a distinguishable manner for each user. The terminal device is intended for a state information receiving means for receiving the state information transmitted from the server device and for other users of the terminal device indicating a specific state in which the state information is an e-mail reception target. When the message is transmitted, the server device includes a message transmitting means for transmitting the message to the second server device, and the server device receives the message transmitted from the terminal device. It is characterized by comprising an e-mail transmission means for generating an e-mail based on a received message and transmitting the e-mail to the e-mail address of a user of the other terminal device.</p><p> According to the present invention, the server device stores an e-mail address identifiable for each user, and when receiving a message transmitted from the terminal device, generates an e-mail based on the received message. Since the e-mail is configured to be sent to the e-mail address of the user of the other terminal device, the user of the terminal device is such that the other user (user of the other terminal device) exchanges messages, for example. Even if you do not know the e-mail address of the other user in a difficult situation, you can have a dialogue by exchanging messages using e-mail.</p><p> The invention according to claim 2 describes the current state of the user in each of a plurality of terminal devices having a messenger function capable of sending and receiving a message instructed by the user to and from another terminal device via a network. State information to be shown is managed for each user, and at least when a change in the current state of the user is detected, state information indicating the changed state of the user is transmitted to the terminal device of the other user. In a server device provided with a transmission means, a storage means for identifiablely storing an e-mail address for each user, and when the message transmitted from the terminal device is received, an e-mail is sent based on the received message. It is characterized by comprising an e-mail transmission means for generating and transmitting the e-mail to the e-mail address of a user of the other terminal device.</p><p> The invention according to claim 3 is the server device according to claim 2, wherein the server device is composed of a first server device and a second server device, and the first server device and the second server device. The first server device includes the state information transmitting means, and the second server device includes the storage means and the e-mail transmitting means. It is characterized by that.</p><p> The invention according to claim 4 is the server device according to claim 3, wherein the second server device sends an e-mail replied to the e-mail from a device owned by a user of the other terminal device. When it is received, the e-mail is saved and the e-mail reception information indicating that the e-mail has been received is transmitted to the first server device, and the first server device is the second server device. When the e-mail reception information from the server device is received, the e-mail reception information is transmitted to the terminal device of the message transmission source, and the terminal device receives the electronic mail from the first server device. When the mail reception information is received, the information indicating the message request is transmitted to the second server device, and the second server device sends the information indicating the message request from the terminal device. When received, a message is generated based on the stored e-mail, and the message is transmitted to the terminal device.</p><p> According to the present invention, the terminal device can quickly acquire the message returned by the mobile mail from the second server device.</p><p> The invention according to claim 5 is characterized in that it functions as the server device according to any one of claims 2 to 4.</p><p> The invention according to claim 6 describes the current state of the user in each of a plurality of terminal devices having a messenger function capable of sending and receiving a message instructed by the user to and from another terminal device via a network. A server device that manages the indicated status information for each user, and at least transmits the status information indicating the changed status of the user to the terminal device of the other user when a change in the current status of the user is detected. In the information providing method in the above, an e-mail address is identifiable for each user, and when the message transmitted from the terminal device is received, an e-mail is generated based on the received message, and the e-mail is generated. The e-mail is sent to the e-mail address of the user of the other terminal device.</p>
<p> According to the present invention, the server device stores an e-mail address identifiable for each user, and when receiving a message transmitted from the terminal device, generates an e-mail based on the received message. Since the e-mail is configured to be sent to the e-mail address of the user of the other terminal device, the user of the terminal device is such that the other user (user of the other terminal device) exchanges messages, for example. Even if you do not know the e-mail address of the other user in a difficult situation, you can have a dialogue by exchanging messages using e-mail.</p>
Hereinafter, the best embodiment of the present invention will be described in detail with reference to the drawings. The embodiments described below are embodiments when the present invention is applied to a message transmission / reception system.
[1. Message transmission / reception system configuration and functions] First, the configuration and functions of the message transmission / reception system S according to the present embodiment will be described with reference to FIG.
FIG. 1 is a diagram showing an outline configuration example of the message transmission / reception system S according to the present embodiment.
As shown in Fig. 1, the message transmission / reception system S includes an IM (instant messenger) service providing server SA, a cooperation server RS, a user terminal (an example of a terminal device) UTm (m = 1,2 ... k), and mobile communication. It is configured with a terminal MTm (m = 1,2 ... k), a gateway server GS, a mail server MS, and the like.
The IM service providing server SA and the linked server RS constitute the server device of the present invention.
The IM service providing server SA is a server that supports transmission / reception (exchange) of instant messages (hereinafter, simply referred to as "messages") performed between user terminals UTm through a network NW, and is a network NW (communication) such as the Internet or an intranet. It is connected to a line and a relay device such as a router), and a unique IP (Internet Protocol) address (global IP address) is assigned. The transmission and reception of the above message is based on a known SIP (Session Initiation Protocol) or Jabber protocol.
Further, in the example shown in FIG. 1, one IM service providing server SA is shown, and the IM service providing server SA is a plurality of server groups (for example, an application server, a proxy server, a redirect server, a registrar, and a location). It may be composed of a server, etc.).
Data is sent and received between the IM service providing server SA and the user terminal UTm based on the SIP and Jabber protocols.
The linked server RS is a server that supports the transmission and reception of messages between the user terminal UTm and the mobile communication terminal MTm, is connected to the network NW, and is assigned a unique IP address.
Data is sent and received between the linked server RS (Web server) and the user terminal UTm based on HTTPS (Hypertext Transfer Protocol Security).
The user terminal UTm can connect to the network NW through, for example, the server of the Internet service provider, and when connecting to the network NW, a unique IP (Internet Protocol) address (for example, a global IP address) is assigned. ing. Then, the user terminal UTm can connect to the service providing server SA and the cooperation server RS through the network NW and perform communication.
Further, the user terminal UTm is installed in each user's home or office, for example, and has a messenger function and a browser function (application software related to the messenger function and the browser function is installed in each user terminal UTm).
In this specification, the messenger function can display presence information indicating the current state of the user with whom the message is exchanged, and is described above through the network NW with the user terminal UTm of the user with whom the message is exchanged. A function that can send and receive messages (instant messages).
The mobile communication terminal MTm is, for example, a mobile body (mobile station) such as a mobile phone or PHS (Personal Handyphone System), and is used to provide a base station BTn (n = 1,2 ... j) and a packet communication service. It is possible to make voice calls with other mobile communication terminals MTm and fixed telephones (not shown) through the mobile communication network MW and the like. A large number of base stations BTn are installed in the packet communication service area at predetermined intervals, and perform wireless communication with the mobile communication terminal MTm located in each wireless cell.
Further, the mobile communication terminal MTm has a function of a mail client for sending and receiving e-mail (hereinafter referred to as "mobile mail") with another mobile communication terminal MTm or the like via a mail server MS or the like. Each mobile communication terminal MTm is carried by each user of the user terminal UTm. In addition, each user has an e-mail address (hereinafter, referred to as "mobile e-mail address") related to the mobile communication terminal MTm.
The gateway server GS is a server provided in the mobile packet barrier relay exchange that interconnects the mobile communication network MW and the network NW, and converts the communication protocol between the mobile communication network MW and the network NW. Communication is relayed (in this embodiment, mobile mail is relayed).
The mail server MS is equipped with a storage unit (for example, a hard disk) as a mailbox for storing mobile mail sent to the mobile mail address of the user of the mobile communication terminal MTm, and is a server that relays the sending and receiving of mobile mail. .. More specifically, when the mail server MS receives the mobile mail addressed to the user's mobile mail address, the mail server MS temporarily stores the mobile mail in the memory allocated to the user in the mailbox, and moves the user. In response to an acquisition request from the communication terminal MTm, the mobile communication mail is transmitted to the mobile communication terminal MTm through the mobile communication network MW.
In the message transmission / reception system S configured as described above, the cooperation server RS receives, for example, a message sent from the user terminal UT2 to the user of the user terminal UT1 (a message based on HTTPS (hereinafter referred to as "HTTPS message"). Then, a mobile mail (mobile mail based on SMTP (Simple Mail Transfer Protocol)) is generated based on the message, and the mobile mail is sent to the mobile mail address of the user of the user terminal UT1, that is, the mobile mail is sent. It is designed to be sent to the mail server MS via the network NW and the gateway server GS.
Then, when the gateway server GS receives the mobile mail from the cooperation server RS, it converts the communication protocol of the mobile mail (for example, from SMTP to the communication protocol of the mobile communication network MW (for example, TCP / IP is moved). Convert to a protocol that matches the body communication network MW) and send it to the mail server MS.
In this way, the mobile mail sent to the mail server MS and stored in the mailbox is acquired by the mobile communication terminal MT1 owned by the user of the user terminal UT1, and the user is the mobile communication terminal MT1 for example, a message from the user terminal UT2. You can check the contents by mobile mail.
[1-1. Configuration and functions of IM service providing server SA] Next, the details of the configuration and functions of the IM service providing server SA will be described with reference to FIG.
Figure 2 is a block diagram showing an example of the outline configuration of the IM service providing server SA.
As shown in FIG. 2, the IM service providing server SA includes an operation unit 1, a display unit 2, a communication unit 3, a drive unit 4, a storage unit 5 as a storage means, an input / output interface unit 6, a system control unit 7, and the like. The system control unit 7 and the input / output interface unit 6 are connected to each other via the system bus 8.
The operation unit 1 is composed of, for example, a keyboard, a mouse, or the like, receives an operation instruction from an administrator or the like, and outputs the instruction content as an instruction signal to the system control unit 7.
The display unit 2 is composed of, for example, a CRT (Cathode Ray Tube) display, a liquid crystal display, or the like, and displays information such as characters and images.
The communication unit 3 connects to the network NW and controls the communication status with the user terminal UTm, the gateway server GS, and the like.
The drive unit 4 reads data or the like from a disc DK (recording medium) such as a flexible disc, a CD (Compact Disc), or a DVD (Digital Versatile Disc), and records data or the like on the disc DK.
The input / output interface unit 6 performs interface processing between the operation unit 1 to the storage unit 5 and the system control unit 7.
The storage unit 5 is composed of, for example, a hard disk drive or the like, and stores an operating system (O / S), various programs (including the server processing program of the present invention), data (including data provided to the user terminal UTm), and the like. .. The server processing program or the like of the present invention may be downloaded from another server or the like via the network NW, or may be recorded on a disk DK such as a CD-ROM and recorded via the drive unit 4. It may be read.
Further, in the storage unit 5, a user information database 51 for registering information about the user of the user terminal UTm is constructed.
FIG. 3 is a diagram showing an example of registration information in the user information database 51.
As shown in FIG. 3, the user information database 51 contains address information, a user ID, a mobile phone email address, a password, a nickname (also referred to as a screen name, hereinafter referred to as "NN"), and a member registered as a friend (hereinafter referred to as "NN"). , NN of (called "friend record member"), presence information (status information) showing the current state of the user presented to each friend record member, mobile phone mail reception setting information showing mobile phone reception setting, mobile phone Specific state information indicating a specific state to be received by mail, reception available time information indicating the receptionable time of mobile mail, and the like are registered in association with each other.
Here, each registration information in the user information database 51 will be described.
The user ID, password, mobile email address, and NN are registered, for example, after each user operates the user terminal UTm to connect to the IM service providing server SA and undergoes a procedure for using the system S. Further, the user ID and NN are uniquely given to each user in the system S, and are registered so as not to be duplicated with other users.
Further, the address information includes, for example, the IP address (current IP address) assigned when the user terminal UTm is connected to the network NW. For example, when the authentication process is executed in response to a login (sign-in) request (including user ID and password) from the user terminal UTm activated by the messenger and login is permitted (that is, the user ID and password are user information). If it is registered in the database 51), the address information of the user terminal is registered in the user information database 51.
In addition, the friend record member is a user who has allowed each other as a partner for exchanging messages. For example, the NN of a user who becomes a friend record member in response to a friend registration request from another user terminal UTm (user ID of the user). Is registered in the user information database 51. It is possible to disclose each other's presence information among the users who are permitted as members of the friendship record.
In addition, each presence information is registered for each friend record member (for example, when the user logs in or when the user's status changes). In the example of FIG. 3, NN The states shown in the presence information of a user who is "aaaaa" are all the friend record members of that user (ie, NN "bbbbb", NN "ccccc", NN "ddddd", NN "eeeee", and NN "ggggg". (Each user of "") is "offline" (this means that all members of the friend record will be presented (notified) with the "offline" status).
It is also possible to individually set the presence information so as to be different for each friend record member (for example, a setting that is always "offline" only for a user who is an NN "ggggg"). Further, for example, when a user with NN "aaaaa" logs in, presence information indicating, for example, "online" is registered (change registration) in the user information database 51 as the presence information of the user.
Further, the mobile mail reception setting information is information indicating a setting of whether or not to accept a message from the user terminal UTm of the friend record member by mobile mail. In addition, the specific state for receiving mobile mail corresponds to a state in which it is difficult or impossible for the user to give an instruction to input a message, for example, "offline", "busy", "away". , "Difficult to chat", and "I'm out of my seat" are examples. The user can arbitrarily specify which of the plurality of types of states is to be a specific state.
When the mobile mail reception setting is "ON", when the current state of the user is the state shown in the specific status information (Fig. 3), the message from the user terminal UTm of the friend record member is received by mobile mail. It will be possible. In this case, as described above, the message from the user terminal UTm is converted into a mobile mail, and the mobile mail is sent to the mobile mail address of the user. In addition, the available time information is the time (time) during which the above message can be received by mobile mail when the reception setting of the mobile mail is "ON" and the state of the user is shown in the specific state information. Limitation) is shown.
In the example of FIG. 3, the mobile mail reception setting of the user who is NN "aaaaa" is registered as "ON", and the specific states for receiving mobile mail are "away" and "offline". Furthermore, since the available time for receiving mobile mail is registered as "until 10:00 on February 1, 2007", the user who is the NN "aaaaa" has his / her current state. If you are "away" or "offline", you can receive messages from the user terminal UTm of the friend record member by mobile mail until "10 o'clock on February 1, 2007" (that is, via the mail server MS etc.). It indicates that the mobile communication terminal MT1 can receive the mobile mail), and that the message will not be accepted by the mobile mail after this time has passed.
Further, in the example of FIG. 3, the user whose mobile mail reception setting is registered as "ON" and whose NN "bbbbb" is the mobile mail reception time is "status change (state change to offline)" registered as the mobile mail reception time. ) Within 3 hours "(when you go offline, the date and time when 3 hours have passed since that time is registered) indicates that the above message can be accepted by mobile mail.
Further, in the example of FIG. 3, the mobile mail reception time of the user whose mobile mail reception setting is registered as "ON" and which is NN "ddddd" is registered as "no limit". The user indicates that the above message can be accepted by mobile mail at any time without limitation when his / her status becomes "away".
Furthermore, in the example of FIG. 3, since the reception setting of the user's mobile mail with NN "ccccc" is registered as "OFF", it is shown that the above message cannot be received by mobile mail, but it is specified. Status information and available time information are registered, and after that, if the reception setting of mobile mail is registered as "ON", the user can use it without any restrictions if his / her current status becomes "offline". The above message can be accepted by mobile mail at any time.
In addition, the reception setting of mobile mail, the specific state for receiving mobile mail, and the reception time of mobile mail can be specified by the user on each user terminal UTm, for example, and the specified mobile mail can be specified. The mobile mail reception setting information indicating the reception setting, the specific status information indicating the specific state for which the mobile mail is to be accepted, and the reception available time information indicating the available time of the mobile mail are transmitted from the user terminal UTm and the system. It will be registered (stored) in the user information database 51 by the control unit 7.
Next, the system control unit 7 is equipped with a CPU (Central Processing Unit) 7a, a ROM (Read Only Memory) 7b, a RAM (Random Access Memory) 7c, etc., and controls the entire IM service providing server SA in an integrated manner. There is. Then, the system control unit 7 executes authentication processing and the like in response to a login request from the user terminal UTm by having the CPU 7a read and execute various programs stored in the ROM 7b and the storage unit 5, and also in the present invention. It functions as a state information transmitting means and the like, and performs processing described later.
Further, when the system control unit 7 permits the login in response to the login request related to the messenger function from the user terminal UTm, the system control unit 7 registers the presence information (registered in the user information database 51) of the friend record member of the user of the user terminal UTm. Presence information that is provided, for example, "online" if the member is logged in, "offline" if the member is not logged in) (NN of the friend record member, etc.) (Together), and transmit (PUSH type distribution) to the user terminal UTm via the communication unit 3 and the network NW. At this time, the system control unit 7 registers the presence information (for example, information indicating "online") of the logged-in user in the user information database 51 in association with the NNs of all the friend record members of the user. At the same time, it is sent (notified) to the user terminal UTm of the friend record member who is logged in among the friend record members of the user (the user terminal UTm of the friend record member who is not logged in among the friend record members of the user). The user terminal UTm periodically acquires the presence information of the logged-in user from the IM service providing server SA. May be).
As a result, the presence information of the friend record member is presented to the user on the main screen related to the messenger function described later.
Further, the system control unit 7 manages the presence information of each user by using the user information database 51, and when a change in the current state of any user is detected, the changed state of the user is displayed. The presence information to be shown is changed and registered in the user information database 51, and is transmitted to the user terminal UTm of the logged-in friend record member among the friend record members of the user via the communication unit 3 and the network NW (). PUSH type distribution) (sent to the user terminal UTm of the friend record member who is not logged in among the friend record members of the user when the friend record member logs in).
Here, the change in the current state of the user is detected when a login request, a logout request, or a state change request is made from the user terminal UTm to the IM service providing server SA. For example, if a login request is made, a change in status from "offline" to "online" is detected, and if a logout request is made, the status is changed from "online" (or "away") to "offline". Changes are detected. In addition, when the user does not operate the operation unit of the user terminal UTm for a certain period of time (for example, 3 minutes), or when the user operates the operation unit of the user terminal UTm, his / her presence information is set to "away" or the like. When the setting is changed, a request to change the status to "Away" is sent from the user terminal UTm to the IM service providing server SA, and a change in the status to "Away" or the like is detected.
Further, when the system control unit 7 detects a change in the current state of any user, the reception setting of the mobile mail of the user is "ON", and the changed state corresponds to the user. In the case of a specific state (for example, offline) shown in the specific state information, an email reception indicating that the user can receive a message by mobile mail together with presence information indicating the changed state of the user. Log in to the user's friend record members with possible information (for example, if the user's mobile mail reception time is not "unlimited", the reception time information indicating the reception time is also included). Send (PUSH type distribution) to the user terminal UTm of the friend record member who is logged in via the communication unit 3 and the network NW (the user terminal UTm of the friend record member who is not logged in among the friend record members of the user). Is sent when the member of the friend record logs in.)
If the user's mobile mail reception time is not "no limit" and the reception end time based on the reception time (for example, 10 o'clock) is reached, the system control unit 7 will perform the user's mobile mail. The reception setting of is set to "OFF" and registered in the user information database 51, and the mail reception cancellation information indicating the mail reception cancellation is sent to the user terminal UTm of the logged-in friend record member among the friend record members of the user. Then, it will be transmitted (PUSH type distribution) via the communication unit 3 and the network NW.
[1-2. Configuration and functions of linked server RS] Next, the details of the configuration and functions of the linked server RS will be described.
FIG. 4 is a block diagram showing an example of the outline configuration of the linked server RS.
As shown in FIG. 4, the linked server RS includes an operation unit 21, a display unit 22, a communication unit 23, a drive unit 24, a storage unit 25, an input / output interface unit 26, a system control unit 27, and the like. It has a server (HTTP server) function and a mail server function. The configuration of the operation unit 21, the display unit 22, the communication unit 23, the drive unit 24, the storage unit 25, and the input / output interface unit 26 is the operation unit 1, the display unit 22, and the communication unit in the IM service providing server SA described above. The configuration is the same as that of 23, the drive unit 24, the storage unit 25, and the input / output interface unit 26.
In the storage unit 25, a user information database for registering information about the user of the user terminal UTm is constructed, and in this, at least the above-mentioned address information, user ID, mobile mail address, password, nickname, etc. Are registered in association with each other.
The user information database 51 may be provided in the database server so that it can be shared by the IM service providing server SA and the cooperation server RS. In this case, the linkage server RS acquires the information registered in the user information database 51 via the database server.
Then, the system control unit 27 functions as an e-mail transmission means or the like in the present invention by the CPU 27a reading and executing various programs (including the server processing program of the present invention) stored in the ROM 27c and the storage unit 25. , The process that supports the exchange of messages between the user terminal UTm and the mobile communication terminal MTm is performed. The server processing program or the like of the present invention may be downloaded from another server or the like via the network NW, or may be recorded on a disk DK such as a CD-ROM and recorded via the drive unit 24. It may be read.
Specifically, when the system control unit 27 receives, for example, an HTTPS message sent from the user terminal UT2 to the user of the user terminal UT1, the system control unit 27 generates a mobile mail based on the HTTPS message (for example, the content of the message is set as the body). To generate a mobile email by describing it in the header with the mobile email address of the user of the user terminal UT1 (obtained from the user information database) as the destination (conversion from HTTPS message to mobile email). Then, the system control unit 27 sends the generated mobile mail to the mobile mail address. The mobile mail transmitted in this way is received and saved by the mail server MS via the network NW and the gateway server GS, and is acquired by the mobile communication terminal MT1.
On the other hand, the mobile mail returned from the mobile communication terminal MT1 is sent to the cooperation server RS via the mail server MS and the gateway server GS and stored, and the system control unit 27 is stored, for example, from the user terminal UT2. Generates an HTTPS message based on the saved mobile mail (for example, the message body described in the body of the mobile mail is described in the HTTPS message and generated) in response to the chat window update request described later. The HTTPS message is sent to the user terminal UT2.
Here, when a mobile mail is returned from the mobile communication terminal MT1, the system control unit 27 receives a mobile mail reception notification including information (for example, NN or user ID) for identifying the user to whom the mobile mail is to be returned. Should be sent to the IM service providing server SA. The IM service providing server SA that has received the mobile mail reception notification will perform the mobile mail reception notification to the user terminal UT2. As a result, the user terminal UT2 can acquire the HTTPS message from the cooperation server RS.
[1-3. Configuration and functions of user terminal UTm] Next, the details of the configuration and functions of the user terminal UTm will be described with reference to FIG. 5 and the like.
FIG. 5 is a block diagram showing an example of an outline configuration of the user terminal UTm.
As shown in FIG. 5, the user terminal UTm includes an operation unit 11, a display unit 12, a communication unit 13, a drive unit 14, a storage unit 15, an input / output interface unit 16, a system control unit 17, a headphone with a microphone 18, and the like. The system control unit 17 and the input / output interface unit 16 are connected to each other via the system bus 19. The configuration of the operation unit 11, the display unit 12, the communication unit 13, the drive unit 14, the storage unit 15, and the input / output interface unit 16 is the operation unit 1, the display unit 2, and the communication unit in the IM service providing server SA described above. The configuration is the same as that of 3, the drive unit 4, the storage unit 5, and the input / output interface unit 6.
The system control unit 17 activates the messenger function by the CPU 17a reading and executing various programs (including the terminal processing program of the present invention) stored in the ROM 17c and the storage unit 15, and the state information receiving means in the present invention. And it is designed to function as a state information display means and the like.
FIG. 6 is a diagram showing an example of a display screen on the display unit 12 displayed by the messenger function of the user terminal UT2.
For example, after the messenger is started and logged in on the user terminal UT2 (the same applies to other user terminals UTm), an icon indicating that the messenger is started is displayed (not shown) on the toolbar 101 on the display unit 12. At the same time, the main screen 100 as shown in FIG. 6 (A) is displayed (opened) on the display unit 12, and further, the presence information (or the presence information) of the friend record member sent from the IM service providing server SA is mailed. Acceptable information and available time information) and the NN of the friend record member are received via the communication unit 13.
Then, as shown in FIG. 6 (A), for example, the status display unit 100a on the main screen 100 has presence information indicating the status of each friend record member (in the example of FIG. 6 (A), the mark 100aa and the character 100ab). Is displayed in association with the NN of the friend record member. Furthermore, when the mail receptionable information from the IM service providing server SA is received, the mark indicating the presence information of the corresponding friend record member (in this example, the friend record member who is NN "aaaaa") is replaced with the relevant mark. An email acceptance mark 100p will be displayed to indicate that the friend record member can accept messages by mobile email. As a result, the user of the user terminal UT2 can grasp that it is difficult or impossible for his / her friend record member to give an instruction to input a message on the user terminal UTm, and a message is sent by mobile mail. Can be accepted (that is, messages can be exchanged by the mobile communication terminal MTm).
Furthermore, when the reception available time information is also received from the IM service providing server SA, the reception available time 100o of the mobile mail will be displayed in the vicinity of the mail reception possible mark 100p of the corresponding friend record member.
In this way, the presence information displayed on the status display unit 100a is displayed and changed (rewritten) from the IM service providing server SA to the latest presence information received later. At this time, if the latest presence information as well as the mail reception available information is received, the display is changed to the latest presence information and the corresponding mail reception mark of the friend record member is also displayed (reception time information is also displayed). If it is received, the available time will also be displayed). In the example of Fig. 6 (B), the status of the friend record member is changed from "online" to "away" by receiving the latest presence information and mail reception information of the friend record member who is NN "ddddd". The display has been changed to, and the mail acceptance mark 100q is displayed.
In addition, for example, when the mail acceptable mark 100p is displayed, when the latest presence information of the friend record member is received, if the mail acceptable information is not received together, the mail acceptable mark is displayed. The display of 100p will be deleted (if the mobile mail reception time of 100o is also displayed, the display will be deleted for this as well). In addition, even if the mail reception cancellation information is received from the IM service providing server SA, the display of the corresponding mail reception possible mark 100p of the friend record member is deleted (when the mobile phone mail reception time 100o is also displayed). , The display will be erased for this as well).
In addition, the main screen 100 shown in FIG. 6 (A) has a "setting" button 100c, a "register new member" button 100d, an "x" (close) button 100e for closing the initial screen 100, and a logout. A "logout" button 100f, a "chat start" button 100g, a "call start" button 100h, and a "mobile mail chat ON" button 100k are provided so as to be selectable by the user.
In such a display state, when the user of the user terminal UT2 operates the operation unit 11 and specifies the "setting" button 100c (for example, clicks with the mouse), a list of various setting items (not shown) is pulled down and displayed. When the user selects a desired setting item from among them, for example, with a mouse, a setting screen (not shown) corresponding to the selected setting item is displayed.
For example, as shown in FIG. 6B, the mobile mail reception setting screen 102, which is one of the setting screens, is displayed.
The reception setting screen 102 of the mobile mail is provided with a reception target designation unit 102a, a reception available time designation unit 102b, and a "registration" button 102c.
The reception target designation unit 102a can specify a specific state to be received for mobile mail. In the example of FIG. 6B, the user specifies the specific state (multiple designations can be made) by designating a check box (for example, clicking with the mouse) in the reception target designation unit 102a. In the example of Fig. 6 (B), "busy", "away", and "offline" are displayed as candidates for a specific state, but other "off the seat" entered by the user is displayed. It may be configured so that a state such as "" can be specified.
In addition, the receptionable time designation unit 102b can specify the receptionable time for mobile mail. In the example of FIG. 6B, the user specifies a radio button (for example, clicks with the mouse) in the acceptable time designation unit 102b, and the end time (for example, the change to the above specific state) is started from the state change (for example, the change to the above specific state). , 3 hours) can be entered with the keyboard, or the available end time can be specified with the keyboard. It is also possible to specify a radio button corresponding to "no limit" in the receptionable time designation unit 102b.
In this way, when the user specifies a specific state for receiving mobile mail and the available time for receiving mobile mail, and then operates the operation unit 11 to specify the "register" button 102c (for example, click with the mouse). , The specific state information indicating the specified specific state and the receivable time information indicating the specified receivable time will be transmitted from the user terminal UT2 to the IM service providing server SA. As a result, the "mobile mail chat OFF" button 100k shown in FIG. 6 (B) is switched to "mobile mail chat ON". In addition, when the IM service providing server SA receives the specific status information and the available time information, the reception setting of the user's mobile mail is registered in the user information database 51 as "ON", and the received specific status is registered. Information and available time information will be registered in the user information database 51.
It should be noted that, for example, a designated unit for a receivable day of the week and a time zone may be provided on the mobile mail reception setting screen 102 shown in FIG. 6 (B) so that a periodic receivable time can be set.
In addition, when the user operates the operation unit 11 to specify the "Mobile mail chat ON" button (for example, click with the mouse), the button is switched to "Mobile mail chat OFF" and the mobile mail reception setting OFF registration request is made. The reception setting OFF registration request information indicating is transmitted from the user terminal UT2 to the IM service providing server SA, and the reception setting of the user's mobile mail is registered in the user information database 51 as "OFF". Furthermore, when the user specifies the "Mobile mail chat OFF" button (for example, clicks with the mouse), the button switches to "Mobile mail chat ON" and the reception setting ON registration request indicating the mobile mail reception setting ON registration request. The information is transmitted from the user terminal UT2 to the IM service providing server SA, and the mobile mail reception setting of the user is registered in the user information database 51 as "ON". In this way, the ON / OFF setting of mobile mail can be switched by the user's one-time specification.
In addition, when the user operates the operation unit 11 and specifies the "register new member" button 100d (for example, click with the mouse), a new member registration screen (not shown) for newly registering a friend is displayed. The mouse. On the new member registration screen, the user operates the operation unit 11 to specify the NN or the like of the user who wants to newly register as a friend, and sends a message to the user terminal UTm (to the IP address) or the e-mail address of the user. It is possible to send information to invite the other party (friend) to exchange with, and if this is permitted to the destination user, the NN etc. of the user who permitted the friend registration is saved in the storage unit 15. In addition, a friend registration request including the NN of the user who has permitted the friend registration is sent to the IM service providing server SA, and is associated with the user ID of the user terminal UT2 who made the friend registration request, and is associated with the user information database. It will be registered in 51 (friend registration).
By registering as a friend in this way, a friend record member of the user of the user terminal UT2 is added, and the status of the friend record member is displayed on the status display unit 100a on the initial screen 100 of the user terminal UT2. (Conversely, the user of the user terminal UT2 is also registered as a friend record member on the friend record member side).
Then, when the user wants to exchange a message with his / her own friend record member, he / she operates the operation unit 11 to display the NN of the online friend record member who wants to exchange the message on the status display unit 100a. If you specify and specify the "Chat start" button 100g (for example, click with the mouse or double-click the NN of the friend record member in the status display unit 100a with the mouse), the chat window screen will be displayed on the display unit 12. .. Through such a chat window screen, the user can exchange messages with a user who is a friend record member (for example, peer-to-peer message exchange based on SIP). Since the method of sending and receiving the message in this case is known, further detailed description thereof will be omitted.
When the user wants to make a call with his / her own friend record member, he / she operates the operation unit 11 to specify the NN of the friend record member who is online and wants to make a call on the status display unit 100a, and "starts a call". When the button (Click to call function button) 100h is specified (for example, clicked with the mouse), the user of the user terminal UT2 uses the headphone 18 with a microphone connected to the user terminal UT2 to and the user who is a friend record member. You can make a call (for example, an IP phone based on SIP).
Then, the user specifies, for example, the NN (aaaaa) of the friend record member on which the mail acceptance mark 100p is displayed, and specifies the "chat start" button 100 g (for example, click with the mouse or the friend record member). Double-click the NN with the mouse) to start the browser and send the chat window ID issuance request to the cooperation server RS. In response to this, the chat window (room) ID is issued from the cooperation server RS, notified to the user terminal UT2, and the chat window screen is displayed on the display unit 12 by the browser. The chat window screen allows the user to exchange messages with a friend record member who is an offline NN "aaaaa".
The chat window ID issued from the cooperation server RS is an identifier uniquely assigned to the chat window screen, and the chat window ID is, for example, a user who exchanges messages on the chat window screen. NN ("aaaaa" and "bbbbb", which may be a user ID) is linked in the cooperation server RS. It is also possible for three or more users to exchange messages on the chat window screen, and in this case as well, for example, NN of each user is associated with the chat window ID.
FIG. 7 is a conceptual diagram when a user of the user terminal UT2 exchanges a message with a user of the user terminal UT1.
As shown in FIG. 7, the chat window screen 103 is displayed on the display unit 12 of the user terminal UT2. The chat window screen 103 is a screen for the user of the user terminal UT2 to exchange messages with a user (friend record member) who is NN "aaaaa", and the chat window screen 103 has a transmission message input field. 103a, a "send" button 103b, a message output field 103c, an "x" (close) button 103d for closing the chat window screen 103, and the like are provided.
In such a display state, the user of the user terminal UT2 operates the operation unit 11 to input the desired message content (for example, a relatively short document) in the transmission message input field 103a (for example, input with a keyboard). When the "Send" button 103b is specified (for example, clicked with the mouse), the content of the input message ("Where are you now?" In the example of FIG. 6) is displayed in the message output field 103c, and the corresponding message is displayed. An HTTPS message including the input message content is sent from the user terminal UT2 to the cooperation server RS.
Then, as shown in FIG. 7, the HTTPS message sent to the cooperation server RS is converted into a mobile mail. The content of the HTTPS message is described in the body of the mobile mail, the mobile mail address of the user of the user terminal UT1 is described in the destination (To :) of the header, and the above chat is described in the sender (From :) of the header. A unique mobile email address (for example, data @ domain name in which the chat window ID is encrypted) is described on the window screen. Then, the mobile mail is transmitted to the user's mobile communication terminal MT1 which is the NN "aaaaa" via the gateway server GS, the mail server MS (not shown in FIG. 7), and the like. As a result, the user of the mobile communication terminal MT1 can confirm the content of the above message in the mobile mail received by the mobile communication terminal MT1.
Then, the user who is the NN "aaaaa" operates the operation unit of the mobile communication terminal MT1 to input the content of the reply message (in the example of FIG. 7, "I'm at Shibuya station!") And presses the send button. Then, the mobile mail containing the content (the destination (To :) of the header describes the mobile mail address unique to the above chat window screen, and the sender (From :) of the header is the mobile mail of the user of the mobile communication terminal MT1. The address is described) is sent to the cooperation server RS via the gateway server GS (not shown in FIG. 7) or the like. Then, the returned mobile mail is converted into an HTTPS message by the cooperation server RS in response to a chat window update request from the user terminal UT2, the HTTPS message is sent to the user terminal UT2, and the content is displayed on the chat window screen. It is displayed in the message output field 103c in 103.
In this way, for example, a message exchange (mobile chat) can be performed between the user of the user terminal UT2 and the user of the mobile communication terminal MT1 (which is also the user of the user terminal UT1).
[2. Operation of message sending / receiving system] Next, the operation of the message transmission / reception system S according to the present embodiment will be described.
(Processing in IM service providing server SA) First, the processing in the system control unit 7 of the IM service providing server SA will be described with reference to FIG.
FIG. 8 is a flowchart showing the processing in the system control unit 7 of the IM service providing server SA. The process is always executed (other than maintenance) in the system control unit 7 of the IM service providing server SA. Further, the information registered in the user information database 51 described above is appropriately read by the system control unit 7 (stored in a predetermined area of RAM) and referred to.
In the process shown in FIG. 8, the system control unit 7 of the IM service providing server SA determines whether or not a change in the current state of any user has been detected (step S1), and determines whether or not the change in the current state of any user has been detected (step S1). When a change in state is detected (step S1: YES), the user ID (or NN) of the user is specified, and the presence information indicating the changed state of the user is provided to the user ID (or NN) of the user. ) Is changed and registered (overwritten) in the user information database 51 (step S2), and the process proceeds to step S3.
As described above, the change of the current state of the user includes a login request, a logout request, a state change request, etc. sent from the user terminal UTm (the user ID for identifying the user in these requests). (Or NN) is added) is detected when it is received by the IM service providing server SA. In addition, the changed state of the user will be specified by the type of the above request.
On the other hand, if the change in the current state of any user is not detected (step S1: NO), the process proceeds to step S9.
In step S3, the system control unit 7 determines whether or not the mobile mail reception setting of the user whose user ID (or NN) is specified is "ON", and the mobile mail reception registered in the user information database 51. If it is determined by referring to the setting information and the mobile mail reception setting of the user is not "ON" (step S3: NO), the process proceeds to step S4 and the mobile mail reception setting of the user is "ON". If (step S3: YES), the process proceeds to step S5.
In step S4, the system control unit 7 receives the address information of the friend record member who is logged in (for example, not offline) among the friend record members of the user (that is, the user whose user ID (or NN) is specified). Is specified from the user information database 51, and presence information indicating the changed state of the user (identified above for the user) is given to the user terminal UTm of the friend record member (according to the address information of the friend record member). The user ID (or NN) is added) is transmitted via the communication unit 3 and the network NW, and the process proceeds to step S9.
In step S5, the system control unit 7 determines the specific state information (specific state information registered in the user information database 51) in which the changed state of the user is associated with the user ID (or NN) of the user. ) Is determined, and if it is not in a specific state (step S5: NO), the process proceeds to step S4 and the same processing as above is performed, and if it is in a specific state. (Step S5: YES), proceed to step S6.
In step S6, the system control unit 7 receives the mobile mail indicated in the available time information (receivable time information registered in the user information database 51) associated with the user ID (or NN) of the user. It is determined whether or not there is a limit on the available time, and if there is no limit (step S6: YES), the process proceeds to step S7, and if there is no limit (that is, there is a limit) (step S6: NO). ), Proceed to step S8.
In step S7, the system control unit 7 identifies the address information of the friend record member who is logged in (for example, not offline) from the user information database 51 among the friend record members of the user, and the user terminal of the friend record member. For UTm (according to the address information of the friend record member), presence information indicating the changed state of the user (the above-specified user ID (or NN) of the user is added), and the above mail. The acceptable information is transmitted via the communication unit 3 and the network NW, and the process proceeds to step S9.
In step S8, the system control unit 7 identifies the address information of the friend record member who is logged in (for example, not offline) from the user information database 51 among the friend record members of the user, and the user terminal of the friend record member. For UTm (according to the address information of the friend record member), presence information indicating the changed state of the user (the above-specified user ID (or NN) of the user is added), the above-mentioned mail reception Possible information and available time information (acceptable time information registered in the user information database 51) associated with the user ID of the user are transmitted via the communication unit 3 and the network NW, etc., and step S9. Proceed to.
In step S9, the system control unit 7 registers, for example, in the user information database 51 whether or not there is a user whose current time has reached the reception end time of the mobile phone (determined by the reception available time information described above). If there is a user who has reached the reception end time of mobile mail (it is time to end reception) by referring to the reception available time information (step S9: YES), proceed to step S10 and carry out mobile mail. If no user has reached the available reception time (step S9: NO), the process proceeds to step S12.
In step S10, the system control unit 7 registers the mobile mail reception setting (setting shown in the mobile mail reception setting information) of the user who has reached the mobile mail reception end time in the user information database 51 as "OFF" ("" Change registration from "ON" to "OFF"). Subsequently, the system control unit 7 identifies the address information of the friend record member who is logged in (for example, not offline) among the friend record members of the user who has reached the reception end time of the mobile mail from the user information database 51. , For the user terminal UTm of the friend record member (according to the address information of the friend record member), the above mail reception cancellation information (user ID (or NN) of the user whose reception setting of the mobile mail is "OFF" ) Is added) via the communication unit 3 and the network NW (step S11), and the process proceeds to step S12.
In step S12, the system control unit 7 determines whether or not the specific state information and the available time information have been received from any user terminal UTm. The specific state information and the available time information are specific states indicating a specific state (for example, offline) specified on the user terminal UTm (for example, specified on the mobile mail reception setting screen 102 of FIG. 6 (B)). Information and available time information indicating the designated available time.
Then, when the specific state information or the like (that is, the specific state information and the available time information) is received (step S12: YES), the process proceeds to step S13, and when the specific state information or the like is not received, the process proceeds to step S13. (Step S12: NO), proceed to step S15.
In step S13, the system control unit 7 sets the mobile mail reception setting (setting shown in the mobile mail reception setting information) corresponding to the user ID (or NN) added to the received specific state information to "ON". Register in the user information database 51 (if it is already "ON", leave it as it is). Subsequently, the system control unit 7 changes and registers the received specific state information and the receivable time information in the user information database 51 in association with the user ID (or NN) added to the specific state information and the like. (Overwrite) (step S14), and proceed to step S15.
In step S15, the system control unit 7 determines whether or not the above-mentioned reception setting OFF registration request information has been received from any user terminal UTm, and if the reception setting OFF registration request information is received (step S15). S15: YES), the process proceeds to step S16, and if the reception setting OFF registration request information has not been received (step S15: NO), the process proceeds to step S17.
In step S16, the system control unit 7 sets the mobile mail reception setting corresponding to the user ID (or NN) added to the received reception setting OFF registration request information (setting shown in the mobile mail reception setting information). Is registered in the user information database 51 as "OFF", and the process proceeds to step S17.
In step S17, the system control unit 7 determines whether or not the above-mentioned reception setting ON registration request information has been received from any user terminal UTm, and if the reception setting ON registration request information is received (step S17). S17: YES), the process proceeds to step S18, and if the reception setting ON registration request information has not been received (step S17: NO), the process proceeds to step S19.
In step S18, the system control unit 7 receives the mobile mail reception setting (setting shown in the mobile mail reception setting information) corresponding to the user ID (or NN) added to the received reception setting ON registration request information. Is registered in the user information database 51 as "ON", and the process proceeds to step S19.
In step S19, the system control unit 7 determines whether or not a mobile mail reception notification (for example, HTTPS POST) has been received from the cooperation server RS, and if the mobile mail reception notification is received (step S19: YES). ), Proceed to step S20, and if the mobile mail reception notification has not been received (step S19: NO), the process proceeds to step S21. This mobile mail reception notification is sent when the linked server RS receives the mobile mail returned from the mobile communication terminal MTm, and the mobile mail reception notification is sent to the user of the user terminal UTm of the message transmission source. User ID (or NN) and chat window ID are included.
In step S20, the system control unit 7 identifies the address information corresponding to the user ID (or NN) included in the mobile mail reception notification from the user information database 51, and notifies the user terminal UTm of the mobile mail reception notification (chat). A message including a window ID (for example, a message based on SIP) is transmitted (PUSH type distribution) via the communication unit 3 and the network NW, and the process proceeds to step S21. The processing of the user terminal UTm that has received the mobile mail reception notification will be described later.
In the other processes in step S21, for example, a process corresponding to a login request, a logout request, a state change request, or the like from each user terminal UTm is performed, but detailed description thereof will be omitted.
(Processing in user terminal UTm) Next, the processing in the system control unit 17 of the user terminal UTm will be described with reference to FIG.
FIG. 9 is a flowchart showing processing related to the messenger in the system control unit 17 of the user terminal UTm.
When the messenger is activated in a certain user terminal UTm (for example, user terminal UT2), the process shown in FIG. 9 is started, and first, the system control unit 17 executes a login process automatically or according to the user's instruction (step S31). ). In such a login process, as described above, the user terminal UTm connects to the IM service providing server SA via the network NW (session establishment), and requests a login to the IM service providing server SA (the user when the messenger is started). Performs the user ID and password entered in (including the user ID and password previously entered and stored in the storage unit 15) by the authentication process in the IM service providing server SA (performed in step S21 above). When login is permitted, the address information of the user terminal UTm and the presence information of the user of the user terminal UTm (for example, the presence information indicating "online") are stored in the user ID of the user by the IM service providing server SA. Is associated with and registered in the user information database 51 (registered for each friend record member). In addition, the presence information of the friend record member of the user who is permitted to log in (the user ID (or NN) of the friend record member is added) is transmitted from the IM service providing server SA to the user terminal UTm.
Next, the system control unit 17 displays the main screen 100 as shown in FIG. 6A on the display unit 12 (step S32).
Next, the system control unit 17 determines whether or not the presence information transmitted from the IM service providing server SA (transmitted in step S4, S7, or S8 above) has been received (step S33), and receives the presence information. If so (step S33: YES), the process proceeds to step S34, and if the presence information is not received (step S33: NO), the process proceeds to step S39. The presence information received in step S33 is transmitted when the status of any of the friend record members is changed after the presence information of all the friend record members is displayed in the process of step S32. is there.
In step S34, the system control unit 17 determines whether or not the mail acceptable information is received together with the presence information, and if the mail acceptable information is not received (step S34: NO), step S35. If the mail reception information is received (step S34: YES), the process proceeds to step S36.
In step S35, the system control unit 17 changes the presence information of the friend record member displayed on the main screen 100 to the friend record member corresponding to the user ID (or NN) added to the received presence information. The presence information is displayed and updated (for example, changed from offline to online) in the received presence information, and the process proceeds to step S39.
In step S36, the system control unit 17 determines whether or not the reception available time information has been received together with the presence information and the mail reception available information, and if the reception available time information has not been received (step S36: NO), the process proceeds to step S37, and if the reception available time information is received (step S36: YES), the process proceeds to step S38.
In step S37, the system control unit 17 updates the display of the presence information (similar to step S35), and, as described above, displays the mail acceptance mark of the friend record member instead of the mark indicating the presence information. Proceed to step S39.
On the other hand, in step S38, the system control unit 17 updates the display of the presence information (similar to step S35), and as described above, instead of the mark indicating the presence information, the mail acceptance mark of the friend record member and the mail acceptance mark of the friend record member and Display the available reception time and proceed to step S39.
In step S39, it is determined whether or not the mail reception cancellation information sent from the IM service providing server SA (sent in step S11 above) has been received, and if the mail reception cancellation information is received (step S39: YES). ), Display and delete the mail acceptance mark of the friend record member corresponding to the user ID (or NN) added to the mail reception cancellation information (If the reception available time is also displayed, display and delete this as well) (Step S40) The mark indicating the presence information is displayed, and if the mail reception cancellation information is not received (step S39: NO), the process proceeds to step S41.
In step S41, it is determined whether or not there is a registration instruction related to the mobile mail reception setting. For example, the user displays the mobile mail reception setting screen 102 as shown in FIG. 6 (B). , As described above, after specifying the specific state for receiving mobile mail and the available time for receiving mobile mail, when the operation unit 11 is operated and the "Register" button 102c is specified (for example, clicked with the mouse), The system control unit 17 determines that there has been a registration instruction related to the reception setting of the mobile mail (step S41: YES), and determines the specific state information indicating the specified specific state and the specified reception available time. The indicated available time information (the user ID (or NN) of the user is added) is transmitted to the IM service providing server SA via the communication unit 13 and the network NW (step S42), and the process proceeds to step S43. If there is no registration instruction (step S41: NO), the process proceeds to step S43.
In step S43, the system control unit 17 determines whether or not the mobile mail reception setting OFF instruction has been given. For example, the "Mobile mail chat ON" button is displayed on the menu screen 100 as shown in FIG. 6 (A). When the user operates the operation unit 11 and specifies the "mobile mail chat ON" button (for example, clicks with the mouse), the system control unit 17 determines that the mobile mail reception setting OFF instruction has been given. (Step S43: YES), the reception setting OFF registration request information (the user ID (or NN) of the user is added) is transmitted to the IM service providing server SA via the communication unit 13 and the network NW (step). S44), proceed to step S45. If there is no instruction to turn off the mobile mail reception setting (step S43: NO), the process proceeds to step S45.
In step S45, the system control unit 17 determines whether or not there has been an instruction to turn on the mobile mail reception setting. For example, "Mobile mail chat OFF" is displayed on the menu screen 100 as shown in FIG. 6 (A). When the user operates the operation unit 11 and specifies the "mobile mail chat OFF" button (for example, clicks with the mouse), the system control unit 17 determines that the mobile mail reception setting ON instruction has been given ( Step S45: YES), the reception setting ON registration request information (the user ID (or NN) of the user is added) is transmitted to the IM service providing server SA via the communication unit 13 and the network NW (step S46). ), Proceed to step S47. If there is no instruction to turn on the mobile mail reception setting (step S45: NO), the process proceeds to step S47.
The mobile chat (message exchange between the user terminal UTm and the mobile communication terminal MTm) process in step S47 is a friend record in which the mail acceptance mark 100p is displayed on the menu screen 100 as shown in FIG. 6 (A), for example. It starts when the member's NN is specified.
The details of the mobile chat process will be described later.
In the other processing in step S48, a message exchange process with a user who is a friend record member (for example, a friend record in which the mail acceptance mark 100p is not displayed on the menu screen 100 as shown in FIG. 6 (A)). For example, peer-to-peer message exchange processing based on SIP), various setting processing, status change request processing, etc., which are executed by specifying the member NN, are executed, but detailed description will be omitted.
In step S49, the system control unit 17 determines whether or not a logout instruction has been given. For example, in a state where the menu screen 100 as shown in FIG. 6A is displayed, the user presses the operation unit 11. When the "logout" button 100f is specified (for example, clicked with the mouse) by operation, the system control unit 17 determines that the logout instruction has been given (step S49: YES), and requests a logout (user ID (or NN) of the user). ) Is added) to the IM service providing server SA via the communication unit 13 and the network NW, etc., and the process is terminated (the menu screen 100 is also closed). If there is no logout instruction (step S49: NO), the process returns to step S33 and the process is continued.
(Operation during mobile chat) Next, the operation during mobile chat will be described with reference to FIGS. 10 and 11.
FIG. 10 is a sequence diagram showing processing and information exchange between each terminal and server during mobile chat, and FIG. 11 shows the format and contents of data based on HTTPS transmitted and received between the user terminal UT2 and the linked server RS. It is a conceptual diagram.
For example, in the process of step S47 of the user terminal UT2, when the mobile chat process is started by specifying the NN (for example, aaaaa) of the friend record member displaying the mail acceptance mark 100p, the browser is started. (Step S101), the chat window ID issuance request is sent to the cooperation server RS by specifying the URL of the cooperation server RS set in advance by the browser (step S102).
As shown in FIG. 11 (A), the data related to this chat window ID issuance request includes the NN (user ID of the user terminal UT2 of the user terminal UT2 that started the mobile chat process in this example) of the mobile chat creator. Good), NN (user ID is also acceptable) of mobile chat participant (in this example, user of mobile communication terminal MT1 to exchange messages), local time (time by clock function in user terminal UT2) stamp, processing content ( In this example, the chat window is open) and the information used for encryption / decryption is included.
The NN of the mobile chat creator, the NN of the mobile chat participant, and the local time stamp are encrypted by SSL (Secure Socket Layer) on the user terminal UT2 side and decrypted on the cooperation server RS side. There is.
When the chat window ID issuance request transmitted in this way is received by the cooperation server RS, the cooperation server RS executes a program corresponding to the processing content (in this example, chat window open) included in the chat window ID issuance request. Execute and issue a chat window ID (create an ID that does not overlap with the ID issued in the past) (step S103). The issued chat window ID is associated with the NN of the mobile chat opener, the NN of the mobile chat participant, and the local time stamp, and is stored in the cooperation server RS.
Then, the issued chat window ID notification is transmitted from the cooperation server RS to the user terminal UT2 (step S104).
As shown in Fig. 11 (B), the data related to this chat window ID notification includes the return code (here, normal, there are other errors such as expiration) and the above-issued chat window ID. ing.
When the chat window ID notification transmitted in this way is received by the user terminal UT2, the chat window screen as shown in FIG. 7, for example, is displayed on the display unit 12 by the browser (step S105). The transmitted chat window ID is stored in association with the chat window screen.
Then, the user of the user terminal UT2 operates the operation unit 11 to input the content of the desired message in the transmission message input field 103a on the displayed chat window screen (step S106), and presses the "send" button 103b. If specified, the browser sends a message transmission request to the linkage server RS (step S107).
As shown in FIG. 11C, the data related to this message transmission request (corresponding to the above-mentioned HTTPS message) includes the chat window ID and the message sender (in this example, the user of the user terminal UT2 who input the message). NN, local timestamp, message content, processing content (contribution in this example), and information used for encryption / decryption.
The chat window ID, message sender's NN, local time stamp, and message content are encrypted by SSL on the user terminal UT2 side and decrypted on the cooperation server RS side.
When the message transmission request transmitted in this way is received by the cooperation server RS, the message sender's NN, local time stamp, and message content included in the request are stored and saved in association with the chat window ID. (Step S108).
Then, the cooperation server RS executes a program corresponding to the processing content (contribution in this example) included in the message transmission request and generates a mobile mail (step S109). Specifically, a mobile email address containing encrypted data of the chat window ID included in the message transmission request is described in the source (From :) of the header, and corresponds to the chat window ID included in the message transmission request. The mobile email address (obtained from the user information database) associated with the NN of the mobile chat participant that is attached and stored is described in the destination (To :), and the content of the message included in the message transmission request. Is written on the body and a mobile mail is generated.
Then, the generated mobile mail is sent from the cooperation server RS to the mail server MS via the gateway server GS (not shown in FIG. 10) (step S110), and is stored in the mailbox of the mail server MS (step S110). Step S111).
The mobile mail stored in this way is transmitted to the mobile communication terminal MT1 in response to an acquisition request from the mobile communication terminal MT1 corresponding to the destination mobile mail address (step S112).
Then, when the user of the mobile communication terminal MT1 inputs the content of the reply message to the mobile mail (step S113) and presses the send button, the mobile mail including the content of the reply message (header destination (To :) is described above. The mobile email address including the encrypted data of the chat window ID is described, and the mobile communication terminal MT1 user's mobile email address is described in the source (From :) of the header), and cooperates via the gateway server GS etc. Sent to server RS (step S114). Then, the link server RS extracts the chat window ID from the mobile email address described as the destination of the mobile email (by decrypting the data before @ in the mobile email address) and associates it with the chat window ID. The mobile mail is saved (step S115).
Next, the cooperation server RS has the extracted chat window ID and the NN (user ID may be used) of the mobile chat opener (in this example, the user of the user terminal UT2) stored in association with the extracted chat window ID. A mobile mail reception notification including the above is sent to the IM service providing server SA (step S116).
When the mobile mail reception notification transmitted in this way is received by the IM service providing server SA, the mobile mail reception notification (including the chat window ID) is sent from the IM service providing server SA to the user through the process of step S20 described above. Sent to terminal UT2 (step S117).
When the mobile mail reception notification sent in this way is received by the user terminal UT2, the chat window ID included in the mobile mail reception notification is extracted by the messenger, passed to the browser, and the chat window ID is transmitted by the browser. The including chat window update request is sent to the cooperation server RS (step S118).
As another example in which the chat window update request is sent to the cooperation server RS by the mobile mail reception notification, the chat window update request is linked regularly (for example, every 5 minutes) by the browser even if there is no mobile mail reception notification. It may be configured to be sent to the server RS (messages are reloaded periodically).
As shown in FIG. 11 (D), the data related to this chat window update request includes the chat window ID, the NN of the chat window updater (in this example, the user of the user terminal UT2), the local time stamp, and the processing content ( In this example, the information used for update) and encryption / decryption is included.
When the chat window update request sent in this way is received by the cooperation server RS, the cooperation server RS executes a program corresponding to the processing content (update in this example) included in the message transmission request and sends an HTTPS message. Generate (step S119). Specifically, the mobile mail stored in association with the chat window ID included in the chat window update request is acquired, and an HTTPS message including the content of the message described in the body is generated.
The HTTPS message generated in this way is sent from the cooperation server RS to the user terminal UT2 as a message notification (step S120).
As shown in FIG. 11 (E), the data related to this message notification includes a return code, a chat window ID, a message content, and a lead flag.
When the message notification transmitted in this way is received by the user terminal UT2, the content of the message included in the message notification is displayed by the browser in the message output field 103c on the chat window screen (step S121).
The above processes from step S106 to step S121 can be repeated until the chat window screen is closed (displayed is canceled) on the user terminal UT2. Of course, when the user terminal UT2 continuously transmits a message, the processes from step S106 to step S112 are continuously performed, and the mobile communication terminal MT1 continuously transmits the message. In that case, the processes from step S113 to step S121 are continuously performed. Then, when the chat window screen is closed on the user terminal UT2, a mobile chat end notification including the chat window ID and the like is sent from the user terminal UT2 to the cooperation server RS, and a mail is sent from the cooperation server RS accordingly. A mobile mail indicating the end of mobile chat is sent (to the mobile mail address) to the mobile communication terminal MT1 via the server MS. After that, when there is a reply of mobile mail from the mobile communication terminal MT1, the cooperation server RS does not save the mobile mail and returns a mobile mail indicating the end of mobile chat to the mobile communication terminal MT1 via the mail server MS. To do. Alternatively, the linked server RS may be configured to store the mobile mail and later send it as an HTTPS message to the user terminal UT2.
As described above, according to the above embodiment, when the IM service providing server SA detects a change in the current state of any user, the user's mobile mail reception setting is "ON", and the user concerned. When the changed state is the specific state (for example, offline) shown in the specific state information corresponding to the user, the user is sent by mobile mail together with the presence information indicating the changed state of the user. The user terminal UTm that sends the mail acceptable information indicating that the message can be accepted to the user terminal UTm of the friend record member of the user and receives the presence information and the mail acceptable information is the user terminal UTm of the above user. Since it is configured to display the mail acceptance mark together with the presence information, the user of the user terminal UTm is in a state where it is difficult or impossible for the other user (friend record member) to exchange messages, for example (for example). , Online or absent), the user of the other party can receive messages by mobile mail, and can know in advance whether or not they are in a state where they can interact with each other. Further, according to the configuration in which the reception available time information is transmitted to the user terminal UTm together with the above mail reception possible information, the user of the user terminal UTm can also determine how long the other user can receive the message by mobile mail. It can be grasped in advance.
In addition to the IM service providing server SA, a linked server RS that functions as a Web server and a mail server is installed so that the mobile email address of each user is acquired by the linked server RS, and the linked server RS is HTTPS. When a message is received, it is converted to mobile mail, the mobile mail is sent to the mobile mail address of the user who is the destination of the message, and the mobile mail returned by the user is converted to an HTTPS message. , Since the message is configured to be sent to the user terminal UTm of the user who sent the message, the user of the user terminal UTm is in a state where it is difficult or impossible for the other user to exchange messages, and the message is concerned. Even if you do not know the mobile mail address of the other user, you can interact with the other user by exchanging messages using mobile mail. In addition, each user can keep his / her mobile email address secret without telling the other user. Furthermore, the existing Web server, mail server, and IM service providing server can be efficiently utilized, and the cost can be reduced.
In addition, the linked server RS that received the mobile mail returned from the mobile communication terminal MTm sends a mobile mail reception notification to the IM service providing server SA, and the IM service providing server SA that receives this sends the mobile mail reception notification to the user terminal UTm. Since it is configured to send a mobile mail reception notification (PUSH type delivery), the user terminal UTm can quickly acquire the message returned by the mobile mail from the cooperation server RS. This can reduce unnecessary update requests as compared with the case where the user terminal UTm periodically requests updates to the linked server RS, so that the load on the server can be reduced.
In addition, each user is configured to be able to set a desired specific state for receiving mobile mail and a desired available time for receiving mobile mail on the reception setting screen 102 as shown in FIG. 6 (B). Therefore, it is possible to set a unique reception state and reception time for each user, and it is possible to improve convenience.
In the above embodiment, the user can set a specific state for receiving mobile mail and a available time for receiving mobile mail on the reception setting screen 102 as shown in FIG. 6 (B). As another example, for example, when a user gives a logout instruction (step S49 above), the reception setting screen 102 as shown in FIG. 6 (B) is displayed, and the specific state and the reception available time are displayed by the user. When is specified, the above specific status information and available time information are transmitted to the IM service providing server SA, the reception setting of the user's mobile mail is registered as "ON" in the user information database 51, and the specific is specified. The status information and the available time information may be configured to be registered in the user information database 51. According to this configuration, the user can remember to register the reception setting "ON" of the mobile mail, the specific state information, and the reception available time information.
Further, in the above embodiment, each user inputs the specific state and the receivable time from the mobile communication terminal MTm, and the mobile communication terminal MTm inputs the input specific state information and the receivable time information (user ID). By sending the mobile mail including (additional) to the cooperation server RS, the information is sent to the IM service providing server SA, and the mobile mail reception setting of the user is registered in the user information database 51 as "ON". At the same time, the specific state information and the available time information may be configured to be registered in the user information database 51. According to this configuration, the user can later register the reception setting "ON" of the mobile mail, the specific state information, and the reception available time information by using his / her mobile communication terminal MTm.
Further, in the above embodiment, a field for inputting a mobile phone email address is provided on the reception setting screen 102 as shown in FIG. 6 (B), and after the mobile phone email address is entered, the user specifies the registration button 102c. In this case, the entered mobile email address may be sent to the IM service providing server SA and registered in the user information database 51, and may also be registered in the user information database of the linkage server RS. .. According to this configuration, the user can easily change the mobile email address that accepts the message in the above specific state.
Further, in the above embodiment, a case where two users (a user whose NN is "aaaaa" and a user whose NN is "bbbbb") exchange messages has been described as an example, but three or more users exchange messages. It can also be applied when performing. For example, a case where three users exchange messages will be described below.
For example, after the processing of steps S101 to S105 above, the chat window screen 103 as shown in FIG. 7 is displayed on the user terminal UT2, and then the user of the user terminal UT2 gives an invitation to the room with the NN "ccccc". When a user (user of user terminal UT3 and mobile communication terminal MT3) is invited to the chat room, i) NN (or user ID) of the invited user, ii) the user can accept messages by mobile mail. Mobile mail acceptance / rejection information indicating whether or not the message is accepted, and iii) additional user information I including the chat window ID are transmitted to the cooperation server RS.
Upon receiving this user additional information I, the linkage server RS associates the NN (ccccc) of the invited user and the mobile mail acceptance / rejection information included in the information with the chat window ID already stored. Additional memory.
Next, the cooperation server RS determines whether or not the invited user can accept the message by mobile mail based on the above mobile mail acceptance / rejection information, and if not, i) is invited. User's NN (eg ccccc), ii) Mobile chat founder's NN (eg bbbbb), iii) Mobile chat participant's NN (eg aaaaa), and iV) User additional information II including the chat window ID. Send to IM service providing server SA.
The IM service providing server SA that has received this additional user information II refers to the presence information of the NN (for example, ccccc) of the invited user included in the presence information from the user information database 51, and is in the "online" state, for example. In some cases, the above-mentioned user additional information II is transferred to the user terminal UT3 of the invited user (if it is not "online", for example, it is transferred when it becomes "online").
The user terminal UT3 that has received this user additional information II displays the chat window screen 103 as shown in FIG. 7 by starting the browser, as in step S101 above. Then, for example, the content of the message transmitted from the user terminal UT2 and saved in the cooperation server RS (step S108 above) is a chat window update request from the user terminal UT3 (regularly or IM service from the cooperation server RS). According to the message save notification via the providing server SA), it is included in the message notification and sent from the cooperation server RS to the user terminal UT3 and displayed on the chat window screen (corresponding to this together with NN). Is displayed). In this case, the data related to the message notification includes the NN (for example, bbbbb) of the user who sent the message, in addition to the contents shown in FIG. 11 (E). On the other hand, for example, the content of the message included in the reply mail returned from the mobile communication terminal MT1 is included in the message notification and transmitted from the cooperation server RS to the user terminal UT3 by the same processing as in steps S115 to S120. , Will be displayed on the chat window screen. In addition to the contents shown in FIG. 11 (E), the data related to the message notification in this case also includes the NN (for example, aaaaa) of the user who sent the mobile mail.
On the other hand, when the cooperation server RS receives the user additional information I and the invited user can accept the message by mobile mail, that is, the invited user is in a specific state (for example, "offline". The above user additional information II is not transmitted to the IM service providing server SA. In this case, for example, the content of the message transmitted from the user terminal UT2 and saved in the cooperation server RS (step S108 above) is included in the mobile communication terminal by the same processing as in steps S106 to S112 above. It is transmitted to MT3 (that is, the mobile mail is transmitted to a plurality of mobile communication terminals MT1 and MT3). On the other hand, for example, the reply mail returned from the mobile communication terminal MT1 is forwarded to the mobile communication terminal MT3 (that is, forwarded to the mobile mail address of the invited user) (at this time, steps S115 to S120). Needless to say, the processing of is also performed).
As described above, even when three or more users (even if the number increases to four or five, they are processed in the same way as when there are three) exchange messages, the same effect as in the case of the above two is achieved. In addition, the convenience can be further improved.
Further, in the above embodiment, it is desirable to apply, for example, a mobile phone or PHS as the mobile communication terminal MTm, but in addition, for example, a PDA (Personal Digital Assistant) or a portable personal computer may be applied. Further, when a portable personal computer is applied as a mobile communication terminal MTm, for example, it can be connected to a network NW by a wireless LAN (Local Area Network), and in this case, the gateway server GS becomes unnecessary.
Further, in the above embodiment, the cooperation server RS functions as a Web server and a mail server, receives an HTTPS message from the user terminal UTm, converts it into a mobile mail, and sends it to the mobile mail address. However, as another example, the linked server RS functions only as a mail server, and a message based on, for example, SIP is sent from the user terminal UTm to the IM service providing server SA, and the IM service providing server SA sends to the linked server RS. It may be configured to be forwarded, and the linked server RS may be configured to convert the received message into a mobile mail and send it to the above mobile mail address.
<figref num="1">It is a figure which shows the outline configuration example of the message transmission / reception system S which concerns on this embodiment.</figref><figref num="2">It is a block diagram which shows an example of the outline structure of IM service providing server SA.</figref><figref num="3">It is a figure which shows the example of the registration information in the user information database 51.</figref><figref num="4">It is a block diagram which shows an example of the outline structure of the cooperation server RS.</figref><figref num="5">It is a block diagram which shows an example of the outline structure of a user terminal UTm.</figref><figref num="6">It is a figure which shows the display screen example in the display part 12 displayed by the messenger function of the user terminal UT2.</figref><figref num="7">It is a conceptual diagram when a user of a user terminal UT2 exchanges a message with a user of a user terminal UT1.</figref><figref num="8">It is a flowchart which shows the process in the system control part 7 of the IM service providing server SA.</figref><figref num="9">It is a flowchart which shows the process which concerns on a messenger in the system control part 17 of a user terminal UTm.</figref><figref num="10">It is a sequence diagram which shows the processing and information exchange in each terminal and server at the time of mobile chat.</figref><figref num="11">It is a conceptual diagram which shows the format and contents of the data based on HTTPS sent and received by the user terminal UT2 and the cooperation server RS.</figref>
Code description
1,11,21 Operation unit 2,12,22 Display 3,13,23 Communication Department 4,14,24 Drive section 5,15,25 Memory 6,16,26 Input / output interface 7,17,27 System control unit 7a, 17a, 27a CPU 7b, 17b, 27b ROM 7c, 17c, 27c RAM 8,19,28 System bus 18 Headphones with microphone 51 User information database SA IM service provider server RS cooperation server GS gateway server MS mail server UTm user terminal MTm mobile communication terminal S message sending and receiving system NW network MW mobile communication network
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| JP2012178062A | Cited by | Japan | Examiner |
| JP5175402B1 | Cited by | Japan | Examiner |
| JP2014515132A | Cited by | Japan | Search report |
| JP2014006870A | Cited by | Japan | Examiner |
| US9438552B2 | Cited by | United States of America | Applicant |
| WO2013190972A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| CN102685028A | Cited by | China | Search report |
| JP2003044418A | Cites | Japan | Search report |
| JP2004129084A | Cites | Japan | Examiner |
| JP2004241946A | Cites | Japan | Examiner |
2 priority claims, no other members on record
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 2007118525 | Japan | A | |
| JP20070118525 | – | – | – |
24 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Receipt of annual feesR250 | R250 | |
| Written notification of registration of transferR350 | R350 | |
| Written request for registration of change of nameS533 | S533 | |
| Receipt of annual feesR250 | R250 | |
| Receipt of annual feesR250 | R250 | |
| Receipt of annual feesR250 | R250 | |
| Receipt of annual feesR250 | R250 | |
| Receipt of annual feesR250 | R250 | |
| Receipt of annual feesR250 | R250 | |
| Written notification of registration of transferR350 | R350 | |
| Written request for registration of change of domicileS531 | S531 | |
| Receipt of annual feesR250 | R250 | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Certificate of patent or registration of utility modelR150 | R150 | |
| Certificate of patent or registration of utility modelR150 | R150 | |
| First payment of annual fees (during grant procedure)A61 | A61 | |
| Written decision to grant a patent or to grant a registration (utility model)A01 | A01 | |
| Written decision to grant a patent or to grant a registration (utility model)A01 | A01 | |
| Decision of grant or rejection writtenTRDD | TRDD | |
| Written amendmentA521 | A521 | |
| Notification of reasons for refusalA131 | A131 | |
| Report on retrievalA977 | A977 | |
| Written amendmentA521 | A521 | |
| Written request for application examinationA621 | A621 |
Numbers
- Publication
- 2008276461
- Publication, DOCDB
- 2008276461
- Publication, EPODOC
- JP2008276461
- Application
- 118525
- Application, DOCDB
- 2007118525
- Application, EPODOC
- JP20070118525
Titles3
- Japanese
- メッセージ送受信システム、サーバ装置、サーバ処理プログラム、及び情報提供方法
- English
- Message transmission / reception system, server device, server processing program, and information provision method
- English
- MESSAGE TRANSMISSION/RECEIPT SYSTEM, SERVER DEVICE, SERVER PROCESSING PROGRAM, AND INFORMATION PROVIDING METHOD
Classification
- IPC, 4
- G06F13 00
- H04L12 58
- H04M3 42
- H04M11 00