WO2011077501A1 - Communication system - Google Patents
Communication system Download PDFInfo
- Publication number
- WO2011077501A1 WO2011077501A1 PCT/JP2009/007322 JP2009007322W WO2011077501A1 WO 2011077501 A1 WO2011077501 A1 WO 2011077501A1 JP 2009007322 W JP2009007322 W JP 2009007322W WO 2011077501 A1 WO2011077501 A1 WO 2011077501A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- chat
- server
- information
- conversation
- communication
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/953—Querying, e.g. by the use of web search engines
- G06F16/9535—Search customisation based on user profiles and personalisation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
- G06F16/972—Access to data in other repository systems, e.g. legacy data or dynamic Web page generation
Definitions
- the present invention relates to, for example, a communication system, and in particular, uses a communication terminal capable of network communication including a mobile phone and a personal computer to perform a conversation in social and real time using text information including chat and / or mail, and the contents of the conversation It is related with the communication system which makes it possible to search the content of the conversation also by the third party who did not actually participate in the conversation.
- a communication system using text information including chat and / or e-mail which exchanges opinions with a distant person using a communication terminal capable of network communication, mainly exchanges information using text instead of voice like a telephone. Basic. For this reason, the other party's remarks will be expressed by the characters sent by the other party, and there is no trouble that the voice is unclear and inaudible. It is possible to chat casually because it is a text exchange without using it.
- the server transmits a chat request to the mobile phone of the other party accordingly.
- the other party who receives the chat request responds according to circumstances. If there is a request permission from the other party, the request permission is transmitted from the server to the request side, a participant list is transmitted to all the participants, and the chat mode is established.
- the server receives a message from a participant, the server transmits the message to all the participants, and displays the message content on the display unit of each participant's mobile phone.
- the other party can join the chat from the middle.
- chats may be performed with friends who have exchanges in real life, or may be conducted with people who have exchanges mainly on the chat system although they have never met in real life.
- chats with people who interact with each other on the chat system, chats are often developed by topics that are common to each other, and those who are not participating in the chat but are also interested in the topic
- the chat content is also interesting and valuable to the third party.
- a log file can be accessed only from a limitedly authorized terminal, the value of this chat cannot be fully enjoyed.
- Communication terminals that can be viewed via an Internet browser are now widely used in personal life, not limited to companies and similar organizations / organizations, and their needs are increasing. Furthermore, communication terminals have come to play a role of not only receiving public information but also transmitting information at an individual level.
- chat that exchanges information by text does not use voice, but it has real-time characteristics like a telephone and is information exchange by text. It is an effective system for exchanging more accurate information. Furthermore, since voice exchange is performed without transmitting one's own voice, a person who has never met in real life can easily communicate on the communication network. Therefore, the subject of chatting differs depending on the topic you are interested in, and chat was often developed meaningfully by asking questions and discussing with each other in real time based on each topic. .
- the chat can be saved or viewed as a log only for the parties participating in the chat and the authorized third parties.
- each person has various interests, and each person has various “specialties”. Therefore, the chat log developed for a topic is itself a treasure trove of valuable information, and is particularly valuable information for third parties who are equally interested in the topic.
- An object of the present invention is social and real-time characteristics that can be enjoyed by an unspecified number of third parties when a chat is performed in real time or after the chat, and / or valuable information as text information including mail is included. It is to provide a certain communication system.
- a further object of the present application is to provide a communication system that records and stores the chat log and / or text information including mail, and further makes the log public and viewable. Furthermore, it is possible to search the published log by entering a keyword, and it is possible to retrieve and view the chat developed about the content you want to know on the spot even if it is not the party who participated in the chat It is also an object of the present application to provide a communication system.
- social is not a group gathered due to the existence of a certain topic or a certain purpose, but individual individuals who have their own world respect each other and share or overlap each other. It is a fluid and highly flexible relationship that is partially connected.
- the communication system according to the present invention provides a multi-faceted information exchange place where each piece of information is not closed but is open and has the possibility of spreading indefinitely, and enables the construction of that place. .
- this chat application provides a communication system that can be activated and used by any device that can be connected to the network via a browser, including a mobile phone, PHS, PDA, smartphone, or computer. That is also the purpose of this application.
- information can be easily exchanged not only in Japan but also overseas by means of a communication network, and the contents of the log can be translated and displayed on the application server side in parallel with the chat so that people with different languages can use it in real time. It is also an object of the present application to provide a communication system that enables chat.
- the communication system receives a plurality of communication terminals capable of exchanging information via the Internet and information exchanged between the plurality of communication terminals.
- a real-time chat system comprising: an application server that performs: a database server that accumulates character information related to chat received by the application server; and a www server that displays at least part of the information stored in the database server.
- the www server includes a public permission acceptance routine for receiving an instruction that allows the plurality of communication terminals that have exchanged the character information related to the chat to disclose the recording of the character information related to the chat,
- the application server receives at least a part of the character information related to the chat stored in the database server when receiving an instruction permitting the disclosure from all the plurality of communication terminals related to the character information related to the chat.
- the system includes a search key reception routine for receiving desired search key data, a search routine for searching for character information related to chats that can be displayed on the www server using the received search key data as a search key, And a transfer routine for transferring the search result to a destination where the search key data is received.
- the communication system in the present invention refers to a system that communicates mainly by text information, including chat and / or mail, and is preferably transmitted by the other party who performs the chat without requiring the user to press the update button.
- Displays input information including text information, image data, voice information or voice information converted into text using, for example, voice recognition software, etc.
- the communication system according to the present invention has a function of identifying and displaying a user who is connected to a chat application and a user who is not connected, and the information is displayed at any time (automatically or predeterminedly). It is preferable to have a function of updating (every time interval). Further, when the users are chatting with each other, a function is provided for displaying on the receiving screen that the information transmitted by the other party is being input.
- the character information in the present invention is information exchanged mainly by characters on the display screen of the communication terminal, including character information related to chat and character information related to mail. Furthermore, the character information is not limited to input by characters, and includes input by speech converted to character information by a conversion function including speech recognition software. Thus, even if characters cannot be input using hands or feet, the communication system according to the present invention can be applied as long as it is possible to display with character information on the screen of the receiving communication terminal. .
- the chat partner can log in to the chat application or can chat even if he / she is not logged in.
- the character information to be transmitted / received can be switched to either according to the mail and the situation on the receiving side or the situation on the sending side, and can be substituted.
- the communication terminal in the present invention is a mobile phone of each carrier including a computer, NTT Docomo (registered trademark), au (registered trademark), Softbank (registered trademark), etc. that can be browsed via an Internet browser, Willcom (registered trademark), E -Communicable terminals including mobile phones, PHS, PDAs, and computers, including mobile terminals including Mobile®, iPhone®, Android®, BlackBerry®, and the like.
- the application server may further include an application that exchanges conversation information with at least one of the plurality of communication terminals and requests the database server to store information.
- the “communication terminal” in the present invention is assumed to be plural, but may be singular.
- character information is exchanged with the server, and for example, the character information can be transmitted and received in a timely manner to a specific destination (including the own device) by shifting the time and date.
- data such as wills, ToDo lists, and “messages for me after a year” are temporarily stored in the database server in advance, and can be transmitted and received at an arbitrary time and date.
- the chat according to the present invention can be used as a conference in which many communication terminals are connected to the same chat group at the same time and many people participate. Further, there is no upper limit to the number of communication terminals belonging to the same chat group described above.
- the database server can store member information and / or conversation information.
- any device that can be connected to the network via a browser such as a mobile phone, PHS, PDA, smart phone, or mobile terminal of each carrier, can start an application for chatting on any communication terminal and can chat. It becomes.
- a mobile phone, PHS, PDA, smart phone, or mobile terminal of each carrier can start an application for chatting on any communication terminal and can chat. It becomes.
- the communication system includes a plurality of communication terminals capable of exchanging information including characters including chat and mail via an Internet browser, and the plurality of communication
- An application server that receives character information related to chat and / or mail exchanged between terminals, a database server that stores the character information received by the application server, and at least one of character information stored in the database server
- a real-time chat system comprising a www server for displaying a part
- the www server includes a public permission receiving routine for receiving a command for allowing the plurality of communication terminals that exchange the character information to disclose the recording of the character information
- the application server displays at least a part of the character information stored in the database server on the www server when receiving an instruction to permit the disclosure from all the plurality of communication terminals related to the character information.
- the system includes a search key reception routine for receiving desired search key data, a search routine for searching for character information that can be displayed on the www server using the received search key data as a search key, And a transfer routine for transferring the result to a destination where the search key data is received.
- the target of the communication system according to the present invention is not only chat but also text information including chat and mail. Thereby, the choice of the means used for communication spreads and becomes a user's convenience more.
- the communication system includes a plurality of communication terminals capable of exchanging information via an Internet browser and a chat exchanged between the plurality of communication terminals.
- a real-time chat system comprising: an application server that receives character information related to the database; a database server that stores character information related to the chat received by the application server; and a www server that displays information stored in the database server
- the real-time chat system includes a search key reception routine for receiving desired search key data, a search routine for searching for character information related to chat stored in the database server using the received search key data as a search key, And a transfer routine for transferring a search result to a destination where the search key data is received.
- the information that is chatted is not limited to the publicly disclosed information, but even if it is not publicly disclosed, for example, the information that is transmitted by the user's own chat can be searched. This makes it possible to utilize previously created documents and the like for new applications, and promotes efficient use of information.
- a communication system includes a plurality of communication terminals capable of exchanging information via an Internet browser and a chat exchanged between the plurality of communication terminals.
- an application server that receives character information related to mail, a database server that stores the character information received by the application server, and a real-time server that includes a www server that displays character information stored in the database server
- the real-time chat system includes a search key reception routine for receiving desired search key data, a search routine for searching for character information stored in the database server using the received search key data as a search key, and a result of the search And a transfer routine for transferring the search key data to a destination where the search key data is received.
- chat and mail content not only those that have been made public but also information that has been made public (chat and mail content) is subject to search. be able to. This makes it possible to utilize previously created documents and the like for new applications, and promotes efficient use of information.
- the said real-time chat system is A location information system (GPS); A routine for extracting all communication terminals in a specific area using the previous period location information system and displaying a list of users related to all the terminals; It is also possible to further comprise a routine for selectively executing broadcast to all the corresponding terminals or transmission to a specific terminal among them. Thereby, it is possible to chat with a nearby person in conjunction with the position information (individually or with everyone).
- GPS location information system
- it may be configured to further include a function of displaying a message related to the chat in a telop on the screens of the corresponding terminals.
- the application server and the www server may be configured so that one server serves as both.
- a plurality of room functions capable of displaying a plurality of screens related to a room where the chat is performed, and a screen related to the first room are displayed. It can also be set as the structure which comprises the switching function which switches to the screen which concerns on 2 rooms. As a result, conversations can be performed simultaneously in parallel in a plurality of groups without an upper limit, that is, windows can be switched.
- the communication terminal can be a communicable terminal including a mobile phone, a PHS, a PDA, a smartphone, and a computer.
- the application server further includes an application that exchanges conversation information with at least one of the plurality of communication terminals and requests the database server to accumulate information. It can also be set as the structure provided.
- the application server may further include a translation processing unit that translates the chat content into a desired language in real time. This enables automatic translation into the main language simultaneously with the input.
- the chat content can be displayed on the communication terminal together with the pre-translation information and the post-translation information. Thereby, it becomes possible to display the sentence before translation in parallel.
- the database server stores member information and / or conversation information, and the stored information is excluded when receiving a deletion instruction from a user. It is also possible to adopt a configuration that can be stored and used for searching without being deleted. Thereby, the character information of chat and mail can be stored indefinitely.
- the www server manages and / or displays the member information, manages and / or displays character information stored in the database server, and manages user information. It is also possible to provide a routine that allows the computer to perform the functions of display, image file management and / or display, and search for published conversations.
- the mobile phone can start a mobile phone chat application corresponding to each carrier or perform chat via a browser.
- PHS in this communication terminal, PDA, a smart phone, or a computer performs the program of the chat application arrange
- the communication terminal sends, to the application server, elapse of a given time, transmission of character information related to chat from the communication terminal, outgoing / incoming call, and It is also possible to send an http request when a predetermined event including the end of conversation occurs.
- the communication terminal may transmit the http request to the application server again when there is no response to the http request for a certain time.
- the communication terminal terminates the conversation when there is still no response even after retransmitting a response to the http request to the application server a predetermined number of times.
- the communication terminal normally chats when a response is returned from the application server after retransmitting an http request a predetermined number of times.
- the conversation information stored in the database server including the room number at the time and the chat start time can be recovered to continue the conversation.
- the communication terminal may be configured to transmit an http request to the application server by a GET method.
- the mobile phone is activated by a predetermined event including a change in a radio wave state or an incoming call of another phone and reception of an email when the mobile phone application is activated.
- a predetermined event including a change in a radio wave state or an incoming call of another phone and reception of an email when the mobile phone application is activated.
- the application can be configured so that the state before the interruption can be recovered by restarting the application within a predetermined time.
- the communication terminal transmits an http request to the application server, but a response to the http request may be in an XML format.
- the communication terminal receives a reply to the http request from the application server in an XML format, but analyzes the XML sentence from the XML layout and based on the content. It can also be set as the structure which performs a screen display.
- the said database server when starting the said chat application and inputting chat content, the said database server via the said application server that the input of chat content is started when inputting the chat content.
- the information in the database server can be transmitted to the communication terminal of the conversation partner when the conversation partner confirms the message.
- the user can determine that writing is in progress.
- a current state grasping unit for grasping a current operation state relating to an application of an arbitrary communication terminal, and a display corresponding to the present state grasped by the present state grasping unit It is also possible to further comprise a current status display means for performing the above.
- the real-time chat system ends the conversation or exchanges a message for a certain period of time after the receiver first accepts the incoming call. It can also be set as the structure further provided with the conversation time measurement function which measures at least until the time of not being confirmed as conversation time. Thereby, chat time can be grasped
- a billing function for charging according to the time measured by the conversation time measuring function may be further provided. In addition to this, it becomes possible to charge partly for a charge depending on the chat call time.
- a communication system as set forth in claim 31 is exchanged between a plurality of communication terminals capable of exchanging information via an Internet browser and the plurality of communication terminals.
- a first server that receives chat data
- a second server that accumulates character information related to the chat and / or mail received by the first server, and information stored in the second server is displayed.
- a communication system comprising a third server server The first server receives a command for permitting disclosure of the recording of the character information to the plurality of communication terminals that have exchanged the character information, and a command for permitting the disclosure to the character information.
- the system includes a search key reception routine for receiving desired search key data, a search routine for searching for character information that can be displayed on the third server using the received search key data as a search key, And a transfer routine for transferring a search result to a destination where the search key data is received.
- the database stored in the database server includes a room number table and a room number detail table, and a conversation date and / or a user who has a conversation from the room number table and the room number detail table. It is also possible to have a function of collating the conversation information by data matching based on such data and displaying the matching data as a result of the collation.
- the room in the present invention means one conversation unit, but a plurality of rooms can be set up (provided) at the same time.
- a function that enables the screens related to multiple rooms to be displayed in a superimposed manner as a window a function that assigns room numbers, and a switching function that switches screens when a change in room number is received. It depends.
- the switching function refers to a function capable of instantaneously and easily switching the screen display from room to room of different chats performed concurrently in parallel by pressing the Tab key, for example.
- the database stored in the database server includes a room number table and a room number detail table, and a conversation date and time and / or a user who has a conversation from the room number table and the room number detail table. It is also possible to provide a function of collating the conversation information by data matching based on the data relating to the data and displaying the matching data as a result of the collation.
- a chat log is stored and made public and searchable so that anyone who receives the service can share conversation information.
- any device that can be connected to a network via a browser such as a mobile phone, PHS, PDA, or mobile terminal of each carrier, can start an application for chatting on any communication terminal and perform chatting. .
- the other party when the other party is not connected to the chat application, it is possible to send a request to participate in the chat to the other party as in the case of a telephone call or to receive a request to participate in chat from another person. Therefore, even if the application is not always connected, a chat can be performed if the convenience of the member suits. For this reason, it also has immediacy that can resolve the desire to know now and exchange information, develop more meaningful chats, enhance the accumulated and disclosed conversation information, and improve information value Leads to.
- the real-time translation function of the present invention enables chatting with people using other languages in real time. This makes it possible to transcend language barriers, discuss matters of interest, and exchange information.
- chat that can be connected to people in other languages while maintaining an appropriate distance relationship by letters instead of voice is a matter of age and gender. It is a system that can easily receive and transmit information, and by searching and browsing other people's conversation information, each curiosity is satisfied and still stimulated.
- FIG. 5 is a timing flowchart illustrating a process of outgoing and incoming calls between a communication server and a user in a real-time chat system according to an embodiment of the present invention. It is a flowchart which shows the transmission procedure of the message which concerns on one Embodiment of this invention. It is a flowchart which shows the transmission procedure of the message which concerns on one Embodiment of this invention. It is a flowchart which shows the confirmation procedure of the message which concerns on one Embodiment of this invention. It is a flowchart which shows the confirmation procedure of the message which concerns on one Embodiment of this invention. It is the schematic showing the status in conversation which concerns on one Embodiment of this invention.
- the real-time chat system concerning another embodiment of the present invention, it is a key map showing a screen image of a user terminal at the time of using a conversation function of four people simultaneously.
- it is a key map showing a screen image of a user terminal at the time of using a pay talk function.
- FIG. 1 is a conceptual diagram showing the overall configuration of a real-time chat system according to an embodiment of the present invention.
- FIG. 2 is a functional block diagram showing the overall configuration of the communication network and the respective roles according to one embodiment of the present invention
- FIG. 2A is a conceptual diagram showing the configuration of the database server in the communication network
- FIG. 2C is a functional block diagram showing a configuration of a mobile phone terminal in the communication network.
- the real-time chat system is transmitted from a communication terminal including a portable terminal (2-A, 2-B, 2-C), a PHS or PDA or a smartphone 3, and a computer 4.
- the chat data is received by the application server 1, and the conversation data is stored and stored in the database server 5.
- “Real-time chat” here refers to the transmission of the other party without having to press the update button to update the conversation information (log) at each communication terminal used by the user when carrying out a conversation (chat) with characters. Words are displayed on the display screen. In addition, the words you speak are displayed immediately on the other party's screen. Furthermore, a user who has logged in to a chat application and a user who has not logged in can be identified on the screen of the communication terminal. In addition, it can be recognized on the screen that the other party who is chatting is inputting a speech (not shown).
- Communication terminals here include mobile phones of carriers including NTT Docomo, au, Softbank, etc., PHS and PDAs and smartphones such as Willcom, E-mobile, iPhone, Android mobile and BlackBerry mobile phones, and computers, etc.
- a communication terminal that can be viewed via an Internet browser.
- the communication network can be mainly divided into servers and communication terminals.
- the application server 1 has a function of exchanging conversation information with communication terminals (2, 3 and 4) for chatting, a reception processing unit 1-A, a transmission processing unit 1-B, a registration request unit 1-C, A translation processing unit 1-D and an image transmission unit 1-D are provided.
- An application that requests the database server 5 to store information is stored.
- the database server 5 includes a conversation log storage unit 5-A-1 for storing a conversation log, a conversation information storage unit 5-A-2 for storing conversation information, and a profile storage unit 5-A-3 for storing user information.
- a storage unit 5-A is provided to store conversation information and user information.
- the conversation information storage unit further includes a conversation data table 5-A-21, a room number table 5-A-221 representing a group or virtual place or opportunity for chatting, and a room number detail table 5-A-222. .
- the www server 6 is an HTML storage unit 6-A that stores member information management screens, management of conversations conducted in the past, inquiry of user information, management of image files, search of published conversations, etc. -1 and an image file 6-A-2 for storing images, and a search unit 6-B.
- Communication terminals connected to these servers via the network are PHS and PDAs including mobile phones 2 of various carriers including NTT Docomo, au, Softbank, Willcom, E-mobile, iPhone, Android mobile and BlackBerry mobile And the communication terminal which can be browsed via an internet browser, such as the smart phone 3 and the computer 4.
- PHS and PDAs including mobile phones 2 of various carriers including NTT Docomo, au, Softbank, Willcom, E-mobile, iPhone, Android mobile and BlackBerry mobile
- the communication terminal which can be browsed via an internet browser, such as the smart phone 3 and the computer 4.
- the mobile phone 2 includes a mobile application unit 2-D and a browser display unit 2-E.
- the mobile application unit 2-D includes a chat function 2-D-1, a room function 2-D-2, and a my page unit.
- 2-D-3 and the open talk search function 2-D-4 (or “subroutines for causing a function to be executed by a device, a processor, or a computer terminal”). Same.)
- the browser display unit 2-E has a my page function 2-E-1 and an open talk search function 2-E-2.
- the PHS and PDA 3 and the computer 4 each include a browser display unit having a chat function, a room function, a my page function, and an open talk search function.
- FIG. 5 is an image diagram showing a chat displayed on the screen of each communication terminal used by the user in the real-time chat system according to the embodiment of the present invention.
- FIG. 6 is a diagram illustrating the application server 1 and the user in the real-time chat system. It is a timing flowchart which shows the process of the transmission and reception of a call.
- FIG. 7 is a flowchart showing a message transmission procedure according to an embodiment of the present invention.
- FIG. 22 is a schematic diagram showing a message transmission request according to an embodiment of the present invention
- FIG. 23 is a schematic diagram showing a message reception request according to an embodiment of the present invention.
- functions according to the respective configurations will be described as operations from the viewpoint of a user (user) using the functions.
- This system has a function that brings the following operations or actions to the user.
- the user A When transmitting a conversation (chat), the user A inputs a message on the message input screen of the communication terminal.
- the message input screen When the message input screen is displayed, the communication terminal used by the user A is notified to the application server 1 that the message is being written. Then, the data related to the situation of the user A in the database server 5 is updated to “being written”, and when the message confirmation is performed from the communication terminal of the user B to the application server 1, the user A is writing. Is notified to the communication terminal of user B that the data is being written.
- information is transmitted to the application server 1 side using the GET method of the http protocol, and is stored in the conversation log storage unit 5-A-1 of the database server 5.
- Information is stored in a conversation log table 5-A-11 and a conversation data table 5-A-21 in the conversation information storage unit 5-A-2.
- a room number is assigned by executing a registration process in the room number table 5-A-221 in the room number information storage unit 5-A-22 of the database server 5 as well.
- the room number and the calling user number are registered in the room number detailed table 5-A-222 of the room number information storage unit 5-A-22.
- a conversation information request is transmitted from the application server 1 to the database server 5 (S721).
- a series of conversation information is transmitted from the database server 5 to the application server 1 (S723).
- the application server 1 acquires the conversation data of the corresponding room number from the conversation data table 5-A-21 of the database server 5 in the order of old conversation data to new conversation data, and the combination of the conversation user and the conversation message. Write to data for transmission.
- the situation (information) of the conversation partner is acquired.
- the user information having the same room number is grasped from the room number detail table 5-A-222 of the database server 5, and the login of the user is obtained from the user information table 5-A-32 in the profile storage unit 5-A-3. Get status and write status.
- the acquired user number, user name, and connection status are further written in the transmission data.
- incoming and conversation information from users other than the user who is talking. From the room number table 5-A-221 of the database server 5, a room number other than the room number currently being talked to and the latest conversation are acquired (S729). If there is a conversation, the room number and the latest message are added to the transmission data. If there is incoming information, the incoming user is added to the transmission data. Further, when a conversation or an incoming call is created after the previous exchange with the application server 1, the fact that it is a new message is written in the transmission data. After the transmission data creation is completed, the data is transmitted to the communication terminal used by the user in the XML format (S733).
- the layout of the http request in one embodiment of the present invention is as follows. 1. Developer ID Send mobile carrier and device type. ⁇ Items for handling terminal-specific processing. 2. Version ⁇ Items to guarantee the operation of the old version program when a new version is released User ID (userid) An item to identify the user. In docomo, au, SoftBank, it is the terminal unique number of each terminal. (Only users who are allowed to send terminal individual numbers) 4). Operation The following five states are shown. sync ⁇ Heartbeat send ⁇ Send message req ⁇ Call ans ⁇ Incoming calls stp ⁇ End of conversation Conversation time (time) 5. Send conversation time in seconds Message (msg) 6. Conversation content Room number 8). Destination user ID (s_userid) Sending user ID.
- the output example of the message reception request in one Embodiment of this invention is as follows.
- ⁇ / message> ⁇ status> 1 ⁇ / status> ⁇ / result>
- ⁇ owner> ⁇ user> ⁇ id> 111 ⁇ / id> ⁇ name>
- Goro Nakamura ⁇ / name> ⁇ / user> ⁇ message> There was a message from Mr. Tanaka.
- the icon display screen (501) showing each user in FIG. 5 is provided with a camera corresponding to a moving image in the communication terminal used by the user, so that the moving image captured by the camera when the user chats is an icon. It may be displayed on the display screen.
- the icon part may be displayed larger, and if necessary, the chat log input to the icon display part may be displayed. This makes it possible for family members and friends who live far away to chat with each other while confirming the situation of the other party in the video.
- biometric authentication using a fingerprint or cornea connected to the communication terminal may be performed in parallel.
- chat use due to impersonation of other people can be prevented, leading to the construction of a more reliable chat system.
- chat performed based on character data can be performed in the environment even in a place where the surroundings are quiet and difficult to talk, or in a place where there is a lot of noise that the voice cannot be heard correctly. Enables necessary information exchange without being affected. Further, since room number information is stored in a room number table and data is linked, it becomes possible to proceed with chatting in a plurality of rooms (groups) in parallel while effectively utilizing a limited time.
- a room means one conversation unit, and a plurality of rooms can be set up (provided) at the same time.
- FIG. 11 is a schematic diagram showing a room number table according to the database according to the embodiment of the present invention
- FIG. 12 is a schematic diagram showing the room number detail table
- FIG. 13 is an image diagram showing the setting of a published conversation according to an embodiment of the present invention
- FIG. 14 is an image diagram showing a detailed screen of the published conversation according to an embodiment of the present invention.
- FIG. 29 is a timing flowchart showing a procedure for publicizing a conversation according to an embodiment of the present invention.
- the disclosure category is updated to “provisional disclosure”
- the users who participated in the conversation are searched from the room number detail table 5-A-222 of the database server 5 (S2907), and a disclosure confirmation email is sent from the www server 6 to all users. It is transmitted (S2910).
- the publication confirmation mail includes a URL for inquiring about contents to be published, a URL for executing a program permitting the publication, and a URL for executing a program for refusal.
- the chat content is not limited to the occasion, but the chat can be promoted as a common understanding that the user can save and publish, so that more detailed information exchange is possible.
- chat information can be disclosed if an agreement is obtained between users, it can also be used as it is for a homepage or a blog, which is a place for information transmission of individuals and companies.
- the possibility that the contents of the chat can be shared and enjoyed by all users as well as the possibility that the contents of the chat can be made public is also a mental deterrent to the act of slander and slander against individuals who tend to be problematic on chat. It can be a driving force for the development of an open dialogue and storyteller.
- chat information published by the system of the present invention (accumulated in the database as much as possible) are stored on a text basis, search is possible and easy. Therefore, when there are important suggestions, information, ideas, etc. in casual conversations, even those that have been extinguished as far as information so far are stored and stored, and the necessary human beings can be used as needed (described later). Can be searched). In other words, so-called cloud computing can affect the level of conversations exchanged by chat, and it is possible to improve the industry and general human life through the distribution, use, and reuse of convenient information. This is possible for the first time.
- FIG. 15 is an image diagram showing a search screen for published conversations according to an embodiment of the present invention
- FIG. 16 is an image diagram showing a detailed search screen for such published conversations.
- the search process searches for conversations that are set to be public in the room number table 5-A-221 in the database server 5 and include the keyword in the message of the conversation log table 5-A-11, and displays the search results as a list. To do.
- the public conversation search system according to the present invention can also be used by users who are not registered as members.
- conversation log data stored in the database server has a function that is automatically searched and extracted by a predetermined keyword at a fixed number of times in a fixed time, regardless of whether it is open or closed. May be. This makes it possible to prevent crimes and harassment of specific individuals and groups, and to disseminate chats that are likely to be closed in a more open and safe system. It becomes.
- chat application system in the mobile phone of each carrier including NTT Docomo, au, and SoftBank in an embodiment according to the present invention will be described.
- FIG. 28 is a timing flowchart showing a mobile phone chat application system according to an embodiment of the present invention.
- the real-time chat system in the present invention is realized by arranging an application on the mobile phone side.
- the mobile phone application can be executed by downloading the program in the www server 6 to the mobile phone.
- the target is users who subscribe to “Packet flat-rate service” of mobile phone companies, and users who do not use “Packet flat-rate service” at the time of downloading and launching the application will display a separate message stating that communication costs will be incurred .
- the program has a function to search for published conversations, incoming / outgoing calls to users, conversations using chat, participation in rooms, My Page function that allows registration information to be added / modified / deleted / referenced.
- a terminal unique number is registered in the mobile phone, and in a terminal that allows the number to be transmitted to the outside, register the terminal unique number in the user information table of the database server and log in. It becomes possible to distinguish the user without any.
- a login screen is displayed when the application is started for the first time, and input of a user name and a password is required.
- An example of an application source code corresponding to NTT docomo is as follows. [Main program (LapeaceMobileChat.java)] import java.io. *; import java.lang. *; import java.util. *; import javax.microedition.io.Connector; import com.nttdocomo.io. *; import com.nttdocomo.ui. *; import com.nttdocomo.util. *; import com.nttdocomo.net.
- oldMessage.user.id.equals newMessage.user.id
- newMessage.comment newMessage.comment
- return true ⁇ if (! oldMessage.comment.equals (newMessage.comment)) ⁇ return true
- a message confirmation timer is set (S2802).
- an http request is generated (S2804). This http request is transmitted when an event occurs on the mobile phone terminal side, including the passage of a specific time, transmission of a chat message from the terminal, outgoing / incoming call, or conversation end.
- a reception information registration request is transmitted from the application server 1 to the database server 6 (S2807), and the reception information is registered in the database server 6 based on the request. (S2808).
- a transmission information search request is transmitted to the database server 6 by the application server 1 (S2809), the transmission information is searched (S2810).
- the search result is transmitted from the database server 6 to the application server 1 and converted into XML (S2811), and the XML data is transmitted to the mobile phone (S2813).
- the XML data received by the mobile phone is analyzed (S2813) and displayed on the screen of the mobile phone based on the content (S2815).
- the conversation time is calculated from the timer time.
- the calculated conversation time is displayed on the screen of the mobile phone terminal.
- FIG. 23 is a schematic diagram illustrating an XML layout of a message reception request according to an embodiment of the present invention.
- the XML layout in one embodiment of the present invention is as follows. XML layout (corresponding to Fig. 23) 1.
- Friend information (friend ⁇ user) (A) User ID (id) User ID of your friend (I) User name Friends username (U) Connection status (status) Friends connection status 1: Connected 2: Conversation (same conversation) 3: Writing (in the same conversation) 4: Conversing (to another conversation) 9: Stopped Conversation information (communication ⁇ room) (A) Room ID (id) Room ID during conversation If the room ID is blank, there is no conversation (periodic inquiry to the server) Or make and receive calls (I) Room name In the case of community conversation, the name is displayed.
- the chat API can be disclosed to the outside.
- the above system of the present invention enables a chat application to be operated in each mobile phone carrier. Chats using computers at home and work, and chats using mobile phones on the go are possible, so you can exchange the information you need at any time, regardless of location.
- a user ID is obtained from the login screen on the communication terminal side.
- a message confirmation timer is embedded in the HTML sentence on the www server side.
- an http request is transmitted from the www server 6 to the application server 1.
- the process is executed on the application server 1 and an XML response is returned to the www server 6.
- the www server 6 analyzes the XML data received from the application server 1, and the result is received by the browser on the communication terminal side to generate a screen (HTML) and display the screen.
- a login screen is displayed.
- the user name and password are entered and the login button is clicked, the user information of the database server 5 is checked via the www server 6, and if authenticated, a chat screen is displayed. If authentication is not successful, an error message is displayed.
- Periodic exchange of messages with the application server 1 is realized by using the refresh function in the html meta tag. In browsers that cannot use the refresh function, this is realized using JavaScript.
- the response to the http request is not returned to the application server 1 within a certain time, it is retransmitted. If no response is returned after a certain number of retransmissions, the conversation is terminated. If a response is returned during a certain number of re-transmissions, the memory stores the room number and the elapsed time from the start of the chat when the chat was successful. Continue the conversation.
- http is used as a transmission means from the mobile phone terminal of each carrier including NTT Docomo, au, and SoftBank to the server.
- HTTP request GET method which is a general-purpose transmission means, it is possible to chat from various mobile phones of each carrier.
- adoption of the versatile GET system makes it possible to cope with version upgrades performed at any time by the mobile phone manufacturer of each carrier.
- the application is interrupted due to radio wave conditions, phone calls, mails, etc. while chatting on a mobile phone, if the application is restarted within a certain time, the state before the interruption Can be recovered.
- the present invention it is possible to set the language of the user when performing membership registration.
- this data is accumulated in the user data table of the user information storage unit of the database server 5.
- the translation program of the application server 1 is executed.
- Translation is translated from the sender's language to the preset sender's language.
- the target languages are Arabic, Bulgarian, Italian, Indonesian, Ukrainian, Estonian, Dutch, Catalan, Galician, Greek, Chinan, Swedish, Spanish, Slovak, Slovenian, Serbian, Vietnamese, Tagalog, Czech, Danish, German, Vietnamese, Hungarian, Hindi, Finnish, French, Bulgarian, Vietnamese, Hebrew, Polish, Portuguese, National languages including Maltese, Lithuanian, Lithuanian, Romanian, Russian, English, Korean and Chinese.
- the translated result is stored in the conversation information storage unit 5-A-2 of the database server 5, and when the message is confirmed from the communication terminal used by the recipient, the application server 1 is translated from the database server 5. Information is received and displayed on the communication terminal used by the recipient.
- chatting on a global scale can be easily performed overseas while staying in the country, by operation that is not different from chatting in the native language.
- Information in various fields is not limited to the country, but is widely demanded from all over the world.
- the present invention satisfies that need sufficiently and easily regardless of age or sex.
- the conversation information before translation input by the conversation partner using the native language may be stored and browsed.
- users who want to learn a foreign language can confirm the content of the conversation in the language they actually use and the content of the foreign language that they want to learn while comparing them over time after chatting. It becomes possible.
- an outgoing / incoming system in chat refers to an outgoing call function for calling a chat partner and an incoming call system for a chat partner to respond to the call.
- a new contact 507 is selected from the menu screen 506 of the communication terminal used by the user A, and the user search screen is displayed.
- user B is searched and the incoming call button is pressed, incoming call information is transmitted to application server 1.
- the transmission information is registered in the conversation log table 5-A-11 and the conversation data table 5-A-21 of the database server 5 (see FIG. 6).
- the conversation data information stored in the database server 5 is read and the incoming call information is transmitted.
- the incoming user A recognizes the incoming information and clicks the message area 504 in which the incoming information is displayed, the incoming information is transmitted to the application server 1.
- incoming information is registered in the conversation log table 5-A-11 and the conversation data table 5-A-21 of the database server 5. After the incoming call information is displayed on the caller communication terminal, the chat is started.
- an answering machine message input screen is displayed.
- the message is transmitted to the application server 1.
- the application server 1 registers the message in the conversation log table 5-A-11 and the conversation data table 5-A-21 of the database server 5.
- the answering machine message in the conversation data table 5-A-21 is searched and the message is transmitted to the communication terminal.
- an incoming message is displayed in the message area 504 of the called user and the message is clicked, an answering message can be inquired.
- This system does not end the chat in an ad hoc relationship, but can be used as a communication tool that allows continuous exchange and information exchange.
- End conversation from the menu screen.
- the end of the conversation can be executed by both users on the outgoing and incoming sides.
- a conversation end message is transmitted to the application server 1.
- information is transmitted to the conversation log table 5-A-11 and the conversation data table 5-A-21.
- the other party makes an inquiry to the application server 1 and receives information on the end of the conversation, it is transmitted to the communication terminal.
- the fact that the other party has finished the conversation is displayed.
- Talk end also applies when there is no communication for a certain period of time.
- the message is confirmed from the communication terminal to the application server 1, it is calculated how much time has passed since the previous message transmission / reception, and the conversation ends when there is no message transmission / reception at a time exceeding a certain time.
- the conversation end information is registered in the conversation log table 5-A-11 and the conversation data table 5-A-11 and notified to the terminal.
- This system makes it possible to request the participation of the chat after grasping the situation of the other party who wants to chat even if the chat application is not activated. What an individual wants to know and wants to share a topic with a person often changes from day to day, and can be more accurately adapted to their needs.
- the above-mentioned outgoing / incoming system not only solves the desire to talk with individual chats, but also makes it possible to achieve more detailed discussions by sharing with others while the topic is in season. Furthermore, if this log is made public, the value as information will increase, and it will be possible to provide useful content for more people.
- the conversation time measurement is started from the time when the conversation is completed and the caller first receives the conversation from the callee.
- the measurement of the conversation time ends.
- This time is defined as call time and can be used when charging for a conversation with a specific user. If there is a telephone call or electronic mail during the conversation, the measurement is continued, but if there is no response for a certain period of time, the conversation is terminated and the time until the conversation is terminated is defined as the conversation time.
- the charge for the call charge is collected from the user on the calling side, and is paid to the user who has received the incoming call at a certain rate.
- the position information is transmitted to the application server 1, and the latitude / longitude is registered in the member information of the database server 5. This makes it possible to inform the chat partner of the current location, measure the distance to the partner, and search for and talk to nearby friends.
- the above-described system of the present invention is a chat system that is generally confined to a closed world of one person, and the relationship with people tends to be sparse, but it becomes obvious at a glance who is nearby, Connections between people can be created in the region and each area, and it can be a chance to develop as a more liberal community.
- the position information grasping system may have a public conference function that allows participants to speak by participating in the same chat if they are in a certain area. As a result, it is possible to discuss and give opinions on a single agenda and use it as a place for meaningful and constructive discussions.
- This is a function that uses a location information system (GPS) to extract all users in a specific area and display a list of applicable users, and to broadcast to all the applicable persons or to specify a part of them. It is possible to use the chat by this system by providing a function to transmit to a human being. This is useful, for example, when securing a criminal when a criminal has occurred and the criminal has escaped to a certain area, or when it is desired to communicate with neighbors.
- GPS location information system
- a message (calling request to participate in chat, request for participation or content spoken in chat) is transmitted with position information
- the message may be further transmitted on a single screen as a telop.
- people who are interested in the telop participate in chats with users in the same area, so that open chats and bright chats are realized, which is expected to activate local communication.
- the present invention is not limited to the above-described embodiment, and various modifications can be made without departing from the spirit of the present invention.
- the screen image of the user terminal when using the one-to-one conversation function can be configured as shown in FIG.
- the screen image of the user terminal when using the talk log display function can be configured as shown in FIG. 31, for example. There is a possibility that convenience for the user is increased.
- the screen image of the user terminal when using the open talk conversation function can be configured as shown in FIG. 32, for example.
- the screen image of the user terminal when using the search function for the public chat data can be configured as shown in FIG. 33, for example. .
- the screen image of the user terminal when using the simultaneous conversation function of four people can be configured as shown in FIG.
- the screen image of the user terminal when using the pay talk function can be configured as shown in FIG. 35, for example.
- a mobile phone and a PC are mainly described as embodiments.
- the idea according to the present application is that provided with any plural or combination processor or storage device, computer system, and palm-type computer.
- a communication terminal capable of browsing via a mobile phone of each carrier, a PHS, a PDA, or an Internet browser including a computer, by chatting with character data instead of voice.
- a chat service that can be enjoyed by many users can be realized without limiting the medium.
- the chat system according to the present invention can be a communication terminal that can be browsed via an Internet browser as described above, it can be used by anyone without limiting the medium.
- the chat system of the present invention can be used as a place for all kinds of communication, including business-related information exchange, status reports between family members and friends, or consulting for consultation.
- the contents of the chats held in each group are not only for exchanging information on an ad hoc basis, but are also made public and searchable by keyword is also possible, so that those who are interested in the topic can also talk You can browse and share information.
- cases that have been solved by using the chat system of the present invention from business consultations to the troubles of the heart are also released, so that people with similar questions and problems can be freed from suffering. Connected.
- the conversation time measurement system of the present invention can be used as a billing system based on call time, a person who has specialized knowledge on a certain theme can use this system as a place for consulting, Rather than actually meeting and talking to people who need information, it is easy to use by chat, and the consulting side can also provide services without investing in setting up an office, etc. It is possible to meet the needs of more and more details, and it is realistically expected to generate very large marketing.
- the present invention has applicability in all industries where communication between people is performed, including the information industry.
Abstract
Description
前記wwwサーバは前記チャットに係る文字情報をやりとりした前記複数の通信端末に対して該チャットに係る文字情報の記録の公開を許容する指令を受ける公開許可受付ルーチンを備え、
前記アプリケーションサーバは、前記公開を許容する指令を前記チャットに係る文字情報に関わる全ての前記複数の通信端末から受けた場合に前記データベースサーバに蓄積された前記チャットに係る文字情報の少なくとも一部を前記wwwサーバにて表示可能にする表示可能化ルーチンを備え、
前記システムは、所望の検索キーデータを受け付ける検索キー受付ルーチンと、前記受けつけられた検索キーデータを検索キーとして前記wwwサーバにて表示可能とされたチャットに係る文字情報について検索する検索ルーチンと、前記検索の結果を前記検索キーデータを受け付けた先に転送する転送ルーチンとを備えることを特徴とする。 In order to solve this problem, the communication system according to the first aspect of the present invention receives a plurality of communication terminals capable of exchanging information via the Internet and information exchanged between the plurality of communication terminals. In a real-time chat system comprising: an application server that performs: a database server that accumulates character information related to chat received by the application server; and a www server that displays at least part of the information stored in the database server.
The www server includes a public permission acceptance routine for receiving an instruction that allows the plurality of communication terminals that have exchanged the character information related to the chat to disclose the recording of the character information related to the chat,
The application server receives at least a part of the character information related to the chat stored in the database server when receiving an instruction permitting the disclosure from all the plurality of communication terminals related to the character information related to the chat. A display enabling routine for enabling display on the www server;
The system includes a search key reception routine for receiving desired search key data, a search routine for searching for character information related to chats that can be displayed on the www server using the received search key data as a search key, And a transfer routine for transferring the search result to a destination where the search key data is received.
前記wwwサーバは前記文字情報をやりとりした前記複数の通信端末に対して該文字情報の記録の公開を許容する指令を受ける公開許可受付ルーチンを備え、
前記アプリケーションサーバは、前記公開を許容する指令を前記文字情報に関わる全ての前記複数の通信端末から受けた場合に前記データベースサーバに蓄積された前記文字情報の少なくとも一部を前記wwwサーバにて表示可能にする表示可能化ルーチンを備え、
前記システムは、所望の検索キーデータを受け付ける検索キー受付ルーチンと、前記受けつけられた検索キーデータを検索キーとして前記wwwサーバにて表示可能とされた文字情報について検索する検索ルーチンと、前記検索の結果を前記検索キーデータを受け付けた先に転送する転送ルーチンとを備えて構成される。 In order to solve the problem, the communication system according to the second aspect of the present invention includes a plurality of communication terminals capable of exchanging information including characters including chat and mail via an Internet browser, and the plurality of communication An application server that receives character information related to chat and / or mail exchanged between terminals, a database server that stores the character information received by the application server, and at least one of character information stored in the database server In a real-time chat system comprising a www server for displaying a part,
The www server includes a public permission receiving routine for receiving a command for allowing the plurality of communication terminals that exchange the character information to disclose the recording of the character information,
The application server displays at least a part of the character information stored in the database server on the www server when receiving an instruction to permit the disclosure from all the plurality of communication terminals related to the character information. With a display enablement routine that enables
The system includes a search key reception routine for receiving desired search key data, a search routine for searching for character information that can be displayed on the www server using the received search key data as a search key, And a transfer routine for transferring the result to a destination where the search key data is received.
前記リアルタイムチャットシステムは、所望の検索キーデータを受け付ける検索キー受付ルーチンと、前記受けつけられた検索キーデータを検索キーとして前記データベースサーバに格納されたチャットに係る文字情報について検索する検索ルーチンと、前記検索の結果を前記検索キーデータを受け付けた先に転送する転送ルーチンとを備えて構成される。 In order to solve the problem, the communication system according to the third aspect of the present invention includes a plurality of communication terminals capable of exchanging information via an Internet browser and a chat exchanged between the plurality of communication terminals. A real-time chat system comprising: an application server that receives character information related to the database; a database server that stores character information related to the chat received by the application server; and a www server that displays information stored in the database server In
The real-time chat system includes a search key reception routine for receiving desired search key data, a search routine for searching for character information related to chat stored in the database server using the received search key data as a search key, And a transfer routine for transferring a search result to a destination where the search key data is received.
前記リアルタイムチャットシステムは、所望の検索キーデータを受け付ける検索キー受付ルーチンと、前記受けつけられた検索キーデータを検索キーとして前記データベースサーバに格納された文字情報について検索する検索ルーチンと、前記検索の結果を前記検索キーデータを受け付けた先に転送する転送ルーチンとを備えて構成される。 In order to solve the problem, a communication system according to the present invention according to
The real-time chat system includes a search key reception routine for receiving desired search key data, a search routine for searching for character information stored in the database server using the received search key data as a search key, and a result of the search And a transfer routine for transferring the search key data to a destination where the search key data is received.
位置情報システム(GPS)と、
前期位置情報システムを用いて特定の地域にいる全通信端末を抽出して該当全端末に係る利用者一覧を表示するルーチンと、
前記該当全端末に対しての同報もしくはそのうちの特定の端末に対しての発信を選択的に実行するルーチンと
をさらに備える構成とすることもできる。これにより、(個別でも全員とでも)位置情報と連動させて、近くにいる人とチャットできる。
Moreover, in the said structure, as in
A location information system (GPS);
A routine for extracting all communication terminals in a specific area using the previous period location information system and displaying a list of users related to all the terminals;
It is also possible to further comprise a routine for selectively executing broadcast to all the corresponding terminals or transmission to a specific terminal among them. Thereby, it is possible to chat with a nearby person in conjunction with the position information (individually or with everyone).
前記第1のサーバは前記文字情報をやりとりした前記複数の通信端末に対して該文字情報の記録の公開を許容する指令を受ける公開許可受付ルーチンと、前記公開を許容する指令を前記文字情報に関わる全ての前記複数の通信端末から受けた場合に前記第2のサーバに蓄積された前記文字情報を前記第3のサーバにて表示可能にする表示可能化ルーチンを備え、
前記システムは、所望の検索キーデータを受け付ける検索キー受付ルーチンと、前記受けつけられた検索キーデータを検索キーとして前記第3のサーバにて表示可能とされた文字情報について検索する検索ルーチンと、前記検索の結果を前記検索キーデータを受け付けた先に転送する転送ルーチンとを備えて構成される。 In order to solve the above problem, a communication system according to the present invention as set forth in
The first server receives a command for permitting disclosure of the recording of the character information to the plurality of communication terminals that have exchanged the character information, and a command for permitting the disclosure to the character information. A display enabling routine for allowing the third server to display the character information stored in the second server when received from all the plurality of communication terminals involved;
The system includes a search key reception routine for receiving desired search key data, a search routine for searching for character information that can be displayed on the third server using the received search key data as a search key, And a transfer routine for transferring a search result to a destination where the search key data is received.
1.
デベロッパID(developerid)
携帯キャリアや端末の種類を送信する。
⇒端末独自の処理に対応する為の項目。
2.バージョン(version)
⇒新バージョンがリリースされた時に旧バージョンのプログラムの動作を保証する為の項目
3.
ユーザID(userid)
ユーザを特定する為の項目。
docomo,au,SoftBankでは各端末の端末固有番号になる。
(端末個別番号の送信を許しているユーザのみ)
4.
オペレーション(operation)
以下5つの状態を示す。
sync
⇒ ハートビート
send
⇒ メッセージ送信
req
⇒ 発信
ans
⇒ 着信
stp
⇒ 会話終了
5.
会話時間(time)
会話時間を秒単位で送信
6.
メッセージ(msg)
会話内容
7.
ルーム番号(roomid)
8.
送信先ユーザID(s_userid)
送信相手のユーザID。複数のユーザの場合はカンマ区切り
9.
接続終了(close)
アプリケーション終了ボタンが押された場合1を送信する。
10.
再接続(reconnect)
長時間の電話やメールでアプリケーションが終了し、再接続する場合に1を送信する。
(送信例)
http://(domain)/(program).php?developerid=docomo&version=20091116&userid=111&operation=sync&time=10&roomid=2222&s_userid=222,333,444 The layout of the http request in one embodiment of the present invention is as follows.
1.
Developer ID
Send mobile carrier and device type.
⇒Items for handling terminal-specific processing.
2. Version
⇒Items to guarantee the operation of the old version program when a new version is released
User ID (userid)
An item to identify the user.
In docomo, au, SoftBank, it is the terminal unique number of each terminal.
(Only users who are allowed to send terminal individual numbers)
4).
Operation
The following five states are shown.
sync
⇒ Heartbeat
send
⇒ Send message
req
⇒ Call
ans
⇒ Incoming calls
stp
⇒ End of conversation
Conversation time (time)
5. Send conversation time in seconds
Message (msg)
6. Conversation content
Room number
8).
Destination user ID (s_userid)
Sending user ID. 8. Separate multiple users with commas.
Close connection (close)
1 is sent when the application end button is pressed.
10.
Reconnect
Send 1 when the application is terminated by a long phone call or email and reconnects.
(Sending example)
http: // (domain) / (program) .php? developerid = docomo & version = 20091116 & userid = 111 & operation = sync & time = 10 & roomid = 2222 & s_userid = 222,333,444
(出力例1)
<?xml
version="1.0" encoding="Shift-JIS" ?>
<resultset>
<result>
<message>メッセージがあります。</message>
<status>1</status>
</result>
<owner>
<user>
<id>111</id>
<name>中村 五郎</name>
</user>
<message>田中さんからメッセージがありました。</message>
</owner>
<friend>
<user>
<id>222</id>
<name>田中 一郎</name>
<status>1</status>
</user>
<user>
<id>444</id>
<name>山本 三郎</name>
<status>2</status>
</user>
</friend>
<communication>
<room>
<id>xxx</id>
<name>xxx</name>
</room>
<user>
<id>333</id>
<name>鈴木 二郎</name>
<status>1</status>
</user>
<user>
<id>444</id>
<name>山本 三郎</name>
<status>2</status>
</user>
<user>
<id>555</id>
<name>田村 四郎</name>
<status>9</status>
</user>
</communication>
<messages>
<message>
<user>
<id>333</id>
<name>鈴木 二郎</name>
</user>
<comment>元気ですか?</comment>
</message>
<message>
<user>
<message>
<user>
<id>444</id>
<name>山本 三郎</name>
</user>
<comment>自宅</comment>
</message>
</messages>
<interrupts>
<interrupt>
<room>
<id>xxx</id>
<name>xxx</name>
</room>
<user>
<id>333</id>
<name>鈴木 二郎</name>
<status>1</status>
</user>
</interrupt>
<interrupt>
<room>
<id>xxx</id>
<name>xxx</name>
</room>
<user>
<id>444</id>
<name>山本 三郎</name>
<status>2</status>
</user>
</interrupt>
</interrupts>
</resultset>
(出力例2)
<id>444</id>
<name>山本 三郎</name>
</user>
<comment>元気です!</comment>
</message>
<message>
<user>
<id>111</id>
<name>津田 隆</name>
</user>
<comment>いまどこにいますか?</comment>
</message>
<message>
<user>
<id>333</id>
<name>鈴木 二郎</name>
</user>
<comment>電車の中</comment>
</message>
<message>
<user>
<id>444</id>
<name>山本 三郎</name>
</user>
<comment>自宅</comment>
</message>
</messages>
<interrupts>
<interrupt>
<room>
<id>xxx</id>
<name>xxx</name>
</room>
<user>
<id>333</id>
<name>鈴木 二郎</name>
<status>1</status>
</user>
</interrupt>
<interrupt>
<room>
<id>xxx</id>
<name>xxx</name>
</room>
<user>
<id>444</id>
<name>山本 三郎</name>
<status>2</status>
</user>
</interrupt>
</interrupts>
</resultset>
Moreover, the output example of the message reception request in one Embodiment of this invention is as follows.
(Output example 1)
<? xml
version = "1.0" encoding = "Shift-JIS"?>
<resultset>
<result>
There is a <message> message. </ message>
<status> 1 </ status>
</ result>
<owner>
<user>
<id> 111 </ id>
<name> Goro Nakamura </ name>
</ user>
<message> There was a message from Mr. Tanaka. </ message>
</ owner>
<friend>
<user>
<id> 222 </ id>
<name> Ichiro Tanaka </ name>
<status> 1 </ status>
</ user>
<user>
<id> 444 </ id>
<name> Saburo Yamamoto </ name>
<status> 2 </ status>
</ user>
</ friend>
<communication>
<room>
<id> xxx </ id>
<name> xxx </ name>
</ room>
<user>
<id> 333 </ id>
<name> Jiro Suzuki </ name>
<status> 1 </ status>
</ user>
<user>
<id> 444 </ id>
<name> Saburo Yamamoto </ name>
<status> 2 </ status>
</ user>
<user>
<id> 555 </ id>
<name> Shiro Tamura </ name>
<status> 9 </ status>
</ user>
</ communication>
<messages>
<message>
<user>
<id> 333 </ id>
<name> Jiro Suzuki </ name>
</ user>
<comment> How are you? </ comment>
</ message>
<message>
<user>
<message>
<user>
<id> 444 </ id>
<name> Saburo Yamamoto </ name>
</ user>
<comment> Home </ comment>
</ message>
</ messages>
<interrupts>
<interrupt>
<room>
<id> xxx </ id>
<name> xxx </ name>
</ room>
<user>
<id> 333 </ id>
<name> Jiro Suzuki </ name>
<status> 1 </ status>
</ user>
</ interrupt>
<interrupt>
<room>
<id> xxx </ id>
<name> xxx </ name>
</ room>
<user>
<id> 444 </ id>
<name> Saburo Yamamoto </ name>
<status> 2 </ status>
</ user>
</ interrupt>
</ interrupts>
</ resultset>
(Output example 2)
<id> 444 </ id>
<name> Saburo Yamamoto </ name>
</ user>
<comment>I'm fine! </ comment>
</ message>
<message>
<user>
<id> 111 </ id>
<name> Takashi Tsuda </ name>
</ user>
<comment> Where are you now? </ comment>
</ message>
<message>
<user>
<id> 333 </ id>
<name> Jiro Suzuki </ name>
</ user>
<comment> In the train </ comment>
</ message>
<message>
<user>
<id> 444 </ id>
<name> Saburo Yamamoto </ name>
</ user>
<comment> Home </ comment>
</ message>
</ messages>
<interrupts>
<interrupt>
<room>
<id> xxx </ id>
<name> xxx </ name>
</ room>
<user>
<id> 333 </ id>
<name> Jiro Suzuki </ name>
<status> 1 </ status>
</ user>
</ interrupt>
<interrupt>
<room>
<id> xxx </ id>
<name> xxx </ name>
</ room>
<user>
<id> 444 </ id>
<name> Saburo Yamamoto </ name>
<status> 2 </ status>
</ user>
</ interrupt>
</ interrupts>
</ resultset>
次に、本発明に係るチャットでの会話を公開する会話公開システムの動作について説明する。 (Conversation open system)
Next, the operation of the conversation publishing system for publishing chat conversations according to the present invention will be described.
[メインプログラム(LapeaceMobileChat.java)]
import java.io.*;
import java.lang.*;
import java.util.*;
import javax.microedition.io.Connector;
import com.nttdocomo.io.*;
import com.nttdocomo.ui.*;
import com.nttdocomo.util.*;
import com.nttdocomo.net.*;
import org.xmlpull.v1.XmlPullParserException;
public class LapeaceMobileChat extends IApplication
implements SoftKeyListener,
ComponentListener, TimerListener {
public static final boolean TEST_MODE_FLAG
= true;
public static final String
TEST_MODE_UID = "10001";
public static final int WAIT_TYPE_TALK
= 1;
public static final int
WAIT_TYPE_INTERRUPT = 2;
String myUserId = "";
ChatItem item = new ChatItem();
ChatItemParser parser = new ChatItemParser();
Panel mainPanel;
HTMLLayout layoutMgr;
Label titleLabel;
ListBox userList;
TextBox chatArea;
TextBox talkText;
Button talkButton;
ListBox interruptList;
Button interruptButton;
Timer heartbeatTimer;
Timer timeTimer;
Timer waitTimer;
int heatbeatTime = 3000;
int timerTime = 0;
int addedDispTime = 0;
boolean timerFlag = false;
Hashtable timerTimes = new Hashtable();
Vector userIdArray = new Vector();
int interruptSelectedRoomId = 0;
int lock = 0;
int waitType = 0;
void error(String msg) {
System.out.println(msg);
}
void message(String msg) {
Dialog message
= new Dialog(Dialog.DIALOG_INFO, "メッセージ");
message.setText(msg);
message.show();
}
boolean confirmInterrupt() {
Dialog confirm
= new Dialog(Dialog.DIALOG_YESNO, "割り込み確認");
confirm.setText("割り込みの場合「はい」、呼び込みの場合「いいえ」を選択してください。");
int ret =
confirm.show();
return
ret == Dialog.BUTTON_YES ? true : false;
}
void sendTerminateMessage() {
try
{
String
url = getSourceURL() +
"?developerid=docomo&version=20091116&userid=" + myUserId +
"&operation=sync&time=" + timerTime +
"&close=1";
HttpConnection
conn = (HttpConnection) Connector.open(url, Connector.READ, true);
conn.setRequestMethod(HttpConnection.GET);
conn.connect();
InputStream
is = conn.openInputStream();
parser.setItem(item);
parser.parse(is);
is.close();
conn.close();
}
catch (Exception e) {
error("エラー("
+ e + ")");
}
}
int getRoomId() {
if(item.communications
!= null && item.communications.room != null &&
item.communications.room.id > 0) {
return
item.communications.room.id;
}
else {
return
0;
}
}
String makeParamByCommunications() {
String
param = "";
if(item.communications
!= null) {
int
roomId = getRoomId();
if(roomId
> 0) {
param
+= "&roomid=" + roomId;
}
if(item.communications.users
!= null && item.communications.users.size() > 0) {
String
to = "";
for(int
i = 0; i < item.communications.users.size(); i++) {
User
user = (User)item.communications.users.elementAt(i);
if(!user.id.equals(myUserId))
{
if(to.length()
> 0) {
to
+= ",";
}
to
+= user.id;
}
}
if(to.length()
> 0) {
param
+= "&s_userid=" + URLEncoder.encode(to);
}
}
}
return
param;
}
boolean inCommunications(String userId)
{
if(item.communications.users
!= null && item.communications.users.size() > 0) {
for(int
i = 0; i < item.communications.users.size(); i++) {
User
user = (User)item.communications.users.elementAt(i);
if(user.id.equals(userId))
{
return
true;
}
}
}
return
false;
}
void sendMessage(String talk) {
lock
= 1;
InputStream
is = null;
HttpConnection
conn = null;
try
{
if(item.friends
!= null && item.friends.size() > 0) {
userIdArray.removeAllElements();
int
i = userList.getSelectedIndex();
if(i
>= 0 && item.friends.size() >= i) {
User
user = (User)item.friends.elementAt(i);
userIdArray.addElement(user.id);
}
}
if(item.interrupts
!= null && item.interrupts.size() > 0) {
int
i = interruptList.getSelectedIndex();
if(i
>= 0 && item.interrupts.size() >= i) {
Interrupt
interrupt = (Interrupt)item.interrupts.elementAt(i);
interruptSelectedRoomId
= interrupt.room.id;
}
}
String
userIds = "";
if(item.friends
!= null && item.friends.size() > 0) {
for(int
i = 0; i < userList.getItemCount(); i++) {
if(userList.isIndexSelected(i))
{
if(userIds.length()
> 0) {
userIds
+= ",";
}
User
user = (User)item.friends.elementAt(i);
if(!user.id.equals(myUserId))
{
userIds
+= user.id;
}
}
}
}
String
operation = "sync";
String
param = "";
if(talk
!= null && talk.length() > 0 && (userIds.length() > 0 ||
getRoomId() > 0)) {
operation
= "send";
param
= "&msg=" + URLEncoder.encode(talk);
if(userIds.length()
> 0) {
if(getRoomId()
> 0) {
if(confirmInterrupt())
{
param
+= "&s_userid=" + URLEncoder.encode(userIds);
}
else {
param
+= makeParamByCommunications();
for(int
i = 0; i < userList.getItemCount(); i++) {
if(userList.isIndexSelected(i))
{
User
user = (User)item.friends.elementAt(i);
if(!user.id.equals(myUserId)
&& !inCommunications(user.id)) {
param
+= URLEncoder.encode(",") + user.id;
}
}
}
}
}
else
{
param
+= "&s_userid=" + URLEncoder.encode(userIds);
}
userIdArray.removeAllElements();
interruptSelectedRoomId
= 0;
}
else
if(item.communications != null) {
param
+= makeParamByCommunications();
}
}
else
{
String
nowTalk = talkText.getText();
if(nowTalk.length()
> 0) {
param
+= "&msg=" + URLEncoder.encode(nowTalk);
}
param
+= makeParamByCommunications();
}
String
url = getSourceURL() +
"?developerid=docomo&version=20091116&userid=" + myUserId +
"&operation=" + operation + "&time=" + timerTime +
param;
conn
= (HttpConnection) Connector.open(url, Connector.READ, true);
conn.setRequestMethod(HttpConnection.GET);
conn.connect();
is
= conn.openInputStream();
ChatItem
newItem = new ChatItem();
parser.setItem(newItem);
parser.parse(is);
is.close();
conn.close();
initPanel(newItem);
} catch
(XmlPullParserException pe) {
error("パースエラー(" + pe + ")");
} catch
(IOException ie) {
error("I/O エラー(" + ie + ")");
}
catch (Exception e) {
error("XML読み込みエラー("
+ e + ")");
} finally {
try
{
if(is
!= null) {
is.close();
}
if(conn
!= null) {
conn.close();
}
}
catch (IOException ioe) {}
}
lock
= 0;
}
boolean checkUserList(ChatItem oldItem,
ChatItem newItem) {
if(oldItem.friends
== null) {
return
true;
}
if(oldItem.friends.size()
!= newItem.friends.size()) {
return
true;
}
for(int
i = 0; i < oldItem.friends.size(); i++) {
User
oldUser = (User)oldItem.friends.elementAt(i);
User
newUser = (User)newItem.friends.elementAt(i);
if(!oldUser.id.equals(newUser.id))
{
return
true;
}
if(!oldUser.name.equals(newUser.name))
{
return
true;
}
if(oldUser.status
!= newUser.status) {
return
true;
}
}
return
false;
}
boolean checkChatText(ChatItem oldItem,
ChatItem newItem) {
if(oldItem.messages
== null) {
return
true;
}
if(oldItem.messages.size()
!= newItem.messages.size()) {
return
true;
}
for(int
i = 0; i < oldItem.messages.size(); i++) {
Message
oldMessage = (Message)oldItem.messages.elementAt(i);
Message
newMessage = (Message)newItem.messages.elementAt(i);
if(!oldMessage.user.id.equals(newMessage.user.id))
{
return
true;
}
if(!oldMessage.comment.equals(newMessage.comment))
{
return
true;
}
}
return
false;
}
boolean checkInterruptList(ChatItem
oldItem, ChatItem newItem) {
if(oldItem.interrupts
== null) {
return
true;
}
if(oldItem.interrupts.size()
!= newItem.interrupts.size()) {
return
true;
}
for(int
i = 0; i < oldItem.interrupts.size(); i++) {
Interrupt
oldInterrupt = (Interrupt)oldItem.interrupts.elementAt(i);
Interrupt
newInterrupt = (Interrupt)newItem.interrupts.elementAt(i);
if(oldInterrupt.room.id
!= newInterrupt.room.id) {
return
true;
}
if(!oldInterrupt.user.id.equals(newInterrupt.user.id))
{
return
true;
}
}
return
false;
}
void initPanel(ChatItem newItem) {
if(checkUserList(item,
newItem)) {
userList.removeAll();
for(int
i = 0; i < newItem.friends.size(); i++) {
User
user = (User)newItem.friends.elementAt(i);
String
mark = "○ ";
if(user.status
== 2) {
mark
= "● ";
}
else if(user.status == 3) {
mark
= "◎ ";
}
else if(user.status == 4) {
mark
= "▲ ";
}
else if(user.status == 9) {
mark
= "× ";
}
userList.append(mark
+ user.name);
if(userIdArray
!= null && userIdArray.size() > 0) {
for(int
j = 0; j < userIdArray.size(); j++) {
String
userId = (String)userIdArray.elementAt(j);
if(userId.equals(user.id))
{
userList.select(i);
break;
}
}
}
}
}
if(checkChatText(item,
newItem)) {
String
str = "";
for(int
i = 0; i < newItem.messages.size(); i++) {
Message
message = (Message)newItem.messages.elementAt(i);
String
name = message.user.name;
String
comment = message.comment;
str
+= "[" + name + "]:" + comment + "\n";
}
chatArea.setText(str);
}
if(checkInterruptList(item,
newItem)) {
interruptList.removeAll();
for(int
i = 0; i < newItem.interrupts.size(); i++) {
Interrupt
interrupt = (Interrupt)newItem.interrupts.elementAt(i);
interruptList.append(interrupt.user.name
+ "(" + interrupt.room.id + ")");
if(interruptSelectedRoomId
== interrupt.room.id) {
interruptList.select(i);
}
}
}
item
= newItem;
}
void uncheckUserList() {
for(int
i = 0; i < userList.getItemCount(); i++) {
if(userList.isIndexSelected(i))
{
userList.deselect(i);
}
}
}
void uncheckInterruptList() {
for(int
i = 0; i < interruptList.getItemCount(); i++) {
if(interruptList.isIndexSelected(i))
{
interruptList.deselect(i);
}
}
}
public void start() {
myUserId
= Phone.getProperty(Phone.TERMINAL_ID);
if(TEST_MODE_FLAG)
myUserId = TEST_MODE_UID;
mainPanel
= new Panel();
layoutMgr
= new HTMLLayout();
mainPanel.setLayoutManager(layoutMgr);
mainPanel.setTitle("Lapeace携帯チャット");
mainPanel.setSoftKeyListener(this);
mainPanel.setComponentListener(this);
mainPanel.setSoftLabel(Frame.SOFT_KEY_1,
"終了");
titleLabel
= new Label("接続時間 00:00");
userList
= new ListBox(ListBox.CHECK_BOX, 3);
chatArea
= new TextBox("", 40, 5, TextBox.DISPLAY_ANY);
chatArea.setEditable(false);
talkText
= new TextBox("", 20, 1, TextBox.DISPLAY_ANY);
talkButton
= new Button("会話");
interruptList
= new ListBox(ListBox.SINGLE_SELECT, 2);
interruptButton
= new Button("切替");
sendMessage("");
layoutMgr.begin(HTMLLayout.RIGHT);
mainPanel.add(titleLabel);
layoutMgr.begin(HTMLLayout.LEFT);
mainPanel.add(userList);
mainPanel.add(chatArea);
mainPanel.add(talkText);
mainPanel.add(talkButton);
layoutMgr.br();
mainPanel.add(interruptList);
mainPanel.add(interruptButton);
layoutMgr.end();
makeTimeTimer();
makeHeatbeatTimer();
Display.setCurrent((Frame)mainPanel);
}
public void resume() {
lock
= 0;
makeTimeTimer();
makeHeatbeatTimer();
}
public void softKeyPressed(int key) {
Frame
f = Display.getCurrent();
if
(f == mainPanel) {
if (key == Frame.SOFT_KEY_1) {
sendTerminateMessage();
terminate();
}
}
}
public void softKeyReleased(int key) {}
public void componentAction(Component
source, int type, int param) {
if(source
== talkButton && type == ComponentListener.BUTTON_PRESSED) {
String
talk = talkText.getText();
if(lock
== 1) {
makeWaitTimer(WAIT_TYPE_TALK);
}
else {
int
nowRoomId = getRoomId();
sendMessage(talk);
uncheckUserList();
talkText.setText("");
if(talk!=null
&& talk.length()>0) {
resetTime(nowRoomId,
getRoomId());
}
}
}
else
if(source == interruptButton && type ==
ComponentListener.BUTTON_PRESSED) {
if(item.interrupts
!= null && item.interrupts.size() > 0) {
int
i = interruptList.getSelectedIndex();
if(i
>= 0 && item.interrupts.size() >= i) {
Interrupt
interrupt = (Interrupt)item.interrupts.elementAt(i);
int
nowRoomId = getRoomId();
item.communications.room.id
= interrupt.room.id;
if(lock
== 1) {
makeWaitTimer(WAIT_TYPE_INTERRUPT);
}
else {
uncheckUserList();
sendMessage("");
talkText.setText("");
uncheckInterruptList();
resetTime(nowRoomId,
interrupt.room.id);
}
}
}
}
else
if(source == interruptList && type == ComponentListener.SELECTION_CHANGED)
{
int
i = interruptList.getSelectedIndex();
if(i
>= 0 && item.interrupts.size() >= i) {
Interrupt
interrupt = (Interrupt)item.interrupts.elementAt(i);
interruptSelectedRoomId
= interrupt.room.id;
}
}
}
public void timerExpired(Timer source)
{
if(source
== timeTimer) {
String
min = "--";
String
sec = "--";
if(timerFlag)
{
timerTime
+= 1;
min
= "" + (addedDispTime + timerTime) / 60;
sec
= "" + (addedDispTime + timerTime) % 60;
if(min.length()
== 1) {
min
= "0" + min;
}
if(sec.length()
== 1) {
sec
= "0" + sec;
}
}
String
labelText = "接続時間 " + min + ":" + sec;
titleLabel.setText(labelText);
}
else if(source == heartbeatTimer) {
if(lock
== 0) {
sendMessage("");
}
makeHeatbeatTimer();
}
else if(source == waitTimer) {
if(lock
== 0) {
if(waitType
== WAIT_TYPE_TALK) {
componentAction(talkButton,
ComponentListener.BUTTON_PRESSED, 0);
}
else if(waitType == WAIT_TYPE_INTERRUPT) {
componentAction(interruptButton,
ComponentListener.BUTTON_PRESSED, 0);
}
}
else {
makeWaitTimer(waitType);
}
}
}
private void makeTimeTimer() {
timeTimer
= new Timer();
timeTimer.setTime(1000);
timeTimer.setRepeat(true);
timeTimer.setListener(this);
timeTimer.start();
}
private void makeHeatbeatTimer() {
heartbeatTimer
= new Timer();
heartbeatTimer.setTime(heatbeatTime);
heartbeatTimer.setRepeat(false);
heartbeatTimer.setListener(this);
heartbeatTimer.start();
}
private void makeWaitTimer(int type) {
waitType
= type;
waitTimer
= new Timer();
waitTimer.setTime(100);
waitTimer.setRepeat(false);
waitTimer.setListener(this);
waitTimer.start();
}
private void resetTime(int nowRoomId,
int reqRoomId) {
timerFlag
= true;
if(nowRoomId
!= reqRoomId) {
Integer
nowKey = new Integer(nowRoomId);
Integer
reqKey = new Integer(reqRoomId);
Integer
savedTime = new Integer(addedDispTime + timerTime);
timerTimes.put(nowKey,
savedTime);
addedDispTime
= (timerTimes.get(reqKey)!=null) ? ((Integer)timerTimes.get(reqKey)).intValue()
: 0;
timerTime
= 0;
}
}
}
Since the application has different operating environment specifications for docomo, au, and SoftBank, an application corresponding to each carrier is required. An example of an application source code corresponding to NTT docomo according to an embodiment of the present invention is as follows.
[Main program (LapeaceMobileChat.java)]
import java.io. *;
import java.lang. *;
import java.util. *;
import javax.microedition.io.Connector;
import com.nttdocomo.io. *;
import com.nttdocomo.ui. *;
import com.nttdocomo.util. *;
import com.nttdocomo.net. *;
import org.xmlpull.v1.XmlPullParserException;
public class LapeaceMobileChat extends IApplication
implements SoftKeyListener,
ComponentListener, TimerListener {
public static final boolean TEST_MODE_FLAG
= true;
public static final String
TEST_MODE_UID = "10001";
public static final int WAIT_TYPE_TALK
= 1;
public static final int
WAIT_TYPE_INTERRUPT = 2;
String myUserId = "";
ChatItem item = new ChatItem ();
ChatItemParser parser = new ChatItemParser ();
Panel mainPanel;
HTMLLayout layoutMgr;
Label titleLabel;
ListBox userList;
TextBox chatArea;
TextBox talkText;
Button talkButton;
ListBox interruptList;
Button interruptButton;
Timer heartbeatTimer;
Timer timeTimer;
Timer waitTimer;
int heatbeatTime = 3000;
int timerTime = 0;
int addedDispTime = 0;
boolean timerFlag = false;
Hashtable timerTimes = new Hashtable ();
Vector userIdArray = new Vector ();
int interruptSelectedRoomId = 0;
int lock = 0;
int waitType = 0;
void error (String msg) {
System.out.println (msg);
}
void message (String msg) {
Dialog message
= new Dialog (Dialog.DIALOG_INFO, "message");
message.setText (msg);
message.show ();
}
boolean confirmInterrupt () {
Dialog confirm
= new Dialog (Dialog.DIALOG_YESNO, "Confirm interrupt");
confirm.setText ("Select" Yes "for interrupt, select" No "for call.");
int ret =
confirm.show ();
return
ret == Dialog.BUTTON_YES? true: false;
}
void sendTerminateMessage () {
try
{
String
url = getSourceURL () +
"? developerid = docomo & version = 20091116 & userid =" + myUserId +
"& operation = sync & time =" + timerTime +
"& close = 1";
HttpConnection
conn = (HttpConnection) Connector.open (url, Connector.READ, true);
conn.setRequestMethod (HttpConnection.GET);
conn.connect ();
InputStream
is = conn.openInputStream ();
parser.setItem (item);
parser.parse (is);
is.close ();
conn.close ();
}
catch (Exception e) {
error ("Error ("
+ e + ")");
}
}
int getRoomId () {
if (item.communications
! = null && item.communications.room! = null &&
item.communications.room.id> 0) {
return
item.communications.room.id;
}
else {
return
0;
}
}
String makeParamByCommunications () {
String
param = "";
if (item.communications
! = null) {
int
roomId = getRoomId ();
if (roomId
> 0) {
param
+ = "& roomid =" + roomId;
}
if (item.communications.users
! = null && item.communications.users.size ()> 0) {
String
to = "";
for (int
i = 0; i <item.communications.users.size (); i ++) {
User
user = (User) item.communications.users.elementAt (i);
if (! user.id.equals (myUserId))
{
if (to.length ()
> 0) {
to
+ = ",";
}
to
+ = user.id;
}
}
if (to.length ()
> 0) {
param
+ = "& s_userid =" + URLEncoder.encode (to);
}
}
}
return
param;
}
boolean inCommunications (String userId)
{
if (item.communications.users
! = null && item.communications.users.size ()> 0) {
for (int
i = 0; i <item.communications.users.size (); i ++) {
User
user = (User) item.communications.users.elementAt (i);
if (user.id.equals (userId))
{
return
true;
}
}
}
return
false;
}
void sendMessage (String talk) {
lock
= 1;
InputStream
is = null;
HttpConnection
conn = null;
try
{
if (item.friends
! = null && item.friends.size ()> 0) {
userIdArray.removeAllElements ();
int
i = userList.getSelectedIndex ();
if (i
> = 0 && item.friends.size ()> = i) {
User
user = (User) item.friends.elementAt (i);
userIdArray.addElement (user.id);
}
}
if (item.interrupts
! = null && item.interrupts.size ()> 0) {
int
i = interruptList.getSelectedIndex ();
if (i
> = 0 && item.interrupts.size ()> = i) {
Interrupt
interrupt = (Interrupt) item.interrupts.elementAt (i);
interruptSelectedRoomId
= interrupt.room.id;
}
}
String
userIds = "";
if (item.friends
! = null && item.friends.size ()> 0) {
for (int
i = 0; i <userList.getItemCount (); i ++) {
if (userList.isIndexSelected (i))
{
if (userIds.length ()
> 0) {
userIds
+ = ",";
}
User
user = (User) item.friends.elementAt (i);
if (! user.id.equals (myUserId))
{
userIds
+ = user.id;
}
}
}
}
String
operation = "sync";
String
param = "";
if (talk
! = null && talk.length ()> 0 && (userIds.length ()> 0 ||
getRoomId ()> 0)) {
operation
= "send";
param
= "& msg =" + URLEncoder.encode (talk);
if (userIds.length ()
> 0) {
if (getRoomId ()
> 0) {
if (confirmInterrupt ())
{
param
+ = "& s_userid =" + URLEncoder.encode (userIds);
}
else {
param
+ = makeParamByCommunications ();
for (int
i = 0; i <userList.getItemCount (); i ++) {
if (userList.isIndexSelected (i))
{
User
user = (User) item.friends.elementAt (i);
if (! user.id.equals (myUserId)
&&! inCommunications (user.id)) {
param
+ = URLEncoder.encode (",") + user.id;
}
}
}
}
}
else
{
param
+ = "& s_userid =" + URLEncoder.encode (userIds);
}
userIdArray.removeAllElements ();
interruptSelectedRoomId
= 0;
}
else
if (item.communications! = null) {
param
+ = makeParamByCommunications ();
}
}
else
{
String
nowTalk = talkText.getText ();
if (nowTalk.length ()
> 0) {
param
+ = "& msg =" + URLEncoder.encode (nowTalk);
}
param
+ = makeParamByCommunications ();
}
String
url = getSourceURL () +
"? developerid = docomo & version = 20091116 & userid =" + myUserId +
"& operation =" + operation + "& time =" + timerTime +
param;
conn
= (HttpConnection) Connector.open (url, Connector.READ, true);
conn.setRequestMethod (HttpConnection.GET);
conn.connect ();
is
= conn.openInputStream ();
ChatItem
newItem = new ChatItem ();
parser.setItem (newItem);
parser.parse (is);
is.close ();
conn.close ();
initPanel (newItem);
} catch
(XmlPullParserException pe) {
error ("parse error (" + pe + ")");
} catch
(IOException ie) {
error ("I / O error (" + ie + ")");
}
catch (Exception e) {
error ("XML reading error ("
+ e + ")");
} finally {
try
{
if (is
! = null) {
is.close ();
}
if (conn
! = null) {
conn.close ();
}
}
catch (IOException ioe) {}
}
lock
= 0;
}
boolean checkUserList (ChatItem oldItem,
ChatItem newItem) {
if (oldItem.friends
== null) {
return
true;
}
if (oldItem.friends.size ()
! = newItem.friends.size ()) {
return
true;
}
for (int
i = 0; i <oldItem.friends.size (); i ++) {
User
oldUser = (User) oldItem.friends.elementAt (i);
User
newUser = (User) newItem.friends.elementAt (i);
if (! oldUser.id.equals (newUser.id))
{
return
true;
}
if (! oldUser.name.equals (newUser.name))
{
return
true;
}
if (oldUser.status
! = newUser.status) {
return
true;
}
}
return
false;
}
boolean checkChatText (ChatItem oldItem,
ChatItem newItem) {
if (oldItem.messages
== null) {
return
true;
}
if (oldItem.messages.size ()
! = newItem.messages.size ()) {
return
true;
}
for (int
i = 0; i <oldItem.messages.size (); i ++) {
Message
oldMessage = (Message) oldItem.messages.elementAt (i);
Message
newMessage = (Message) newItem.messages.elementAt (i);
if (! oldMessage.user.id.equals (newMessage.user.id))
{
return
true;
}
if (! oldMessage.comment.equals (newMessage.comment))
{
return
true;
}
}
return
false;
}
boolean checkInterruptList (ChatItem
oldItem, ChatItem newItem) {
if (oldItem.interrupts
== null) {
return
true;
}
if (oldItem.interrupts.size ()
! = newItem.interrupts.size ()) {
return
true;
}
for (int
i = 0; i <oldItem.interrupts.size (); i ++) {
Interrupt
oldInterrupt = (Interrupt) oldItem.interrupts.elementAt (i);
Interrupt
newInterrupt = (Interrupt) newItem.interrupts.elementAt (i);
if (oldInterrupt.room.id
! = newInterrupt.room.id) {
return
true;
}
if (! oldInterrupt.user.id.equals (newInterrupt.user.id))
{
return
true;
}
}
return
false;
}
void initPanel (ChatItem newItem) {
if (checkUserList (item,
newItem)) {
userList.removeAll ();
for (int
i = 0; i <newItem.friends.size (); i ++) {
User
user = (User) newItem.friends.elementAt (i);
String
mark = "○";
if (user.status
== 2) {
mark
= "●";
}
else if (user.status == 3) {
mark
= "◎";
}
else if (user.status == 4) {
mark
= "▲";
}
else if (user.status == 9) {
mark
= "×";
}
userList.append (mark
+ user.name);
if (userIdArray
! = null && userIdArray.size ()> 0) {
for (int
j = 0; j <userIdArray.size (); j ++) {
String
userId = (String) userIdArray.elementAt (j);
if (userId.equals (user.id))
{
userList.select (i);
break;
}
}
}
}
}
if (checkChatText (item,
newItem)) {
String
str = "";
for (int
i = 0; i <newItem.messages.size (); i ++) {
Message
message = (Message) newItem.messages.elementAt (i);
String
name = message.user.name;
String
comment = message.comment;
str
+ = "[" + name + "]:" + comment + "\ n";
}
chatArea.setText (str);
}
if (checkInterruptList (item,
newItem)) {
interruptList.removeAll ();
for (int
i = 0; i <newItem.interrupts.size (); i ++) {
Interrupt
interrupt = (Interrupt) newItem.interrupts.elementAt (i);
interruptList.append (interrupt.user.name
+ "(" + interrupt.room.id + ")");
if (interruptSelectedRoomId
== interrupt.room.id) {
interruptList.select (i);
}
}
}
item
= newItem;
}
void uncheckUserList () {
for (int
i = 0; i <userList.getItemCount (); i ++) {
if (userList.isIndexSelected (i))
{
userList.deselect (i);
}
}
}
void uncheckInterruptList () {
for (int
i = 0; i <interruptList.getItemCount (); i ++) {
if (interruptList.isIndexSelected (i))
{
interruptList.deselect (i);
}
}
}
public void start () {
myUserId
= Phone.getProperty (Phone.TERMINAL_ID);
if (TEST_MODE_FLAG)
myUserId = TEST_MODE_UID;
mainPanel
= new Panel ();
layoutMgr
= new HTMLLayout ();
mainPanel.setLayoutManager (layoutMgr);
mainPanel.setTitle ("Lapeace mobile chat");
mainPanel.setSoftKeyListener (this);
mainPanel.setComponentListener (this);
mainPanel.setSoftLabel (Frame.SOFT_KEY_1,
"Exit");
titleLabel
= new Label ("Connection time 00:00");
userList
= new ListBox (ListBox.CHECK_BOX, 3);
chatArea
= new TextBox ("", 40, 5, TextBox.DISPLAY_ANY);
chatArea.setEditable (false);
talkText
= new TextBox ("", 20, 1, TextBox.DISPLAY_ANY);
talkButton
= new Button ("conversation");
interruptList
= new ListBox (ListBox.SINGLE_SELECT, 2);
interruptButton
= new Button ("Switch");
sendMessage ("");
layoutMgr.begin (HTMLLayout.RIGHT);
mainPanel.add (titleLabel);
layoutMgr.begin (HTMLLayout.LEFT);
mainPanel.add (userList);
mainPanel.add (chatArea);
mainPanel.add (talkText);
mainPanel.add (talkButton);
layoutMgr.br ();
mainPanel.add (interruptList);
mainPanel.add (interruptButton);
layoutMgr.end ();
makeTimeTimer ();
makeHeatbeatTimer ();
Display.setCurrent ((Frame) mainPanel);
}
public void resume () {
lock
= 0;
makeTimeTimer ();
makeHeatbeatTimer ();
}
public void softKeyPressed (int key) {
Frame
f = Display.getCurrent ();
if
(f == mainPanel) {
if (key == Frame.SOFT_KEY_1) {
sendTerminateMessage ();
terminate ();
}
}
}
public void softKeyReleased (int key) {}
public void componentAction (Component
source, int type, int param) {
if (source
== talkButton && type == ComponentListener.BUTTON_PRESSED) {
String
talk = talkText.getText ();
if (lock
== 1) {
makeWaitTimer (WAIT_TYPE_TALK);
}
else {
int
nowRoomId = getRoomId ();
sendMessage (talk);
uncheckUserList ();
talkText.setText ("");
if (talk! = null
&& talk.length ()> 0) {
resetTime (nowRoomId,
getRoomId ());
}
}
}
else
if (source == interruptButton && type ==
ComponentListener.BUTTON_PRESSED) {
if (item.interrupts
! = null && item.interrupts.size ()> 0) {
int
i = interruptList.getSelectedIndex ();
if (i
> = 0 && item.interrupts.size ()> = i) {
Interrupt
interrupt = (Interrupt) item.interrupts.elementAt (i);
int
nowRoomId = getRoomId ();
item.communications.room.id
= interrupt.room.id;
if (lock
== 1) {
makeWaitTimer (WAIT_TYPE_INTERRUPT);
}
else {
uncheckUserList ();
sendMessage ("");
talkText.setText ("");
uncheckInterruptList ();
resetTime (nowRoomId,
interrupt.room.id);
}
}
}
}
else
if (source == interruptList && type == ComponentListener.SELECTION_CHANGED)
{
int
i = interruptList.getSelectedIndex ();
if (i
> = 0 && item.interrupts.size ()> = i) {
Interrupt
interrupt = (Interrupt) item.interrupts.elementAt (i);
interruptSelectedRoomId
= interrupt.room.id;
}
}
}
public void timerExpired (Timer source)
{
if (source
== timeTimer) {
String
min = "-";
String
sec = "-";
if (timerFlag)
{
timerTime
+ = 1;
min
= "" + (addedDispTime + timerTime) / 60;
sec
= "" + (addedDispTime + timerTime)% 60;
if (min.length ()
== 1) {
min
= "0" + min;
}
if (sec.length ()
== 1) {
sec
= "0" + sec;
}
}
String
labelText = "Connection time" + min + ":" + sec;
titleLabel.setText (labelText);
}
else if (source == heartbeatTimer) {
if (lock
== 0) {
sendMessage ("");
}
makeHeatbeatTimer ();
}
else if (source == waitTimer) {
if (lock
== 0) {
if (waitType
== WAIT_TYPE_TALK) {
componentAction (talkButton,
ComponentListener.BUTTON_PRESSED, 0);
}
else if (waitType == WAIT_TYPE_INTERRUPT) {
componentAction (interruptButton,
ComponentListener.BUTTON_PRESSED, 0);
}
}
else {
makeWaitTimer (waitType);
}
}
}
private void makeTimeTimer () {
timeTimer
= new Timer ();
timeTimer.setTime (1000);
timeTimer.setRepeat (true);
timeTimer.setListener (this);
timeTimer.start ();
}
private void makeHeatbeatTimer () {
heartbeatTimer
= new Timer ();
heartbeatTimer.setTime (heatbeatTime);
heartbeatTimer.setRepeat (false);
heartbeatTimer.setListener (this);
heartbeatTimer.start ();
}
private void makeWaitTimer (int type) {
waitType
= type;
waitTimer
= new Timer ();
waitTimer.setTime (100);
waitTimer.setRepeat (false);
waitTimer.setListener (this);
waitTimer.start ();
}
private void resetTime (int nowRoomId,
int reqRoomId) {
timerFlag
= true;
if (nowRoomId
! = reqRoomId) {
Integer
nowKey = new Integer (nowRoomId);
Integer
reqKey = new Integer (reqRoomId);
Integer
savedTime = new Integer (addedDispTime + timerTime);
timerTimes.put (nowKey,
savedTime);
addedDispTime
= (timerTimes.get (reqKey)! = null)? ((Integer) timerTimes.get (reqKey)). intValue ()
: 0;
timerTime
= 0;
}
}
}
XMLレイアウト(図23対応)
1.
共通パラメータ(result)
(ア)
出力結果(status)
httpリクエストに対するサーバの処理結果が表示される
Success(成功)
/ NotFount(URL,オペレーションエラー) /
ServerError(サーバ側エラー:versionエラー、データベース登録失敗等)
/
ClientError(クライアント側エラー:機器エラー等)
(イ)
出力結果メッセージ(message)
エラーメッセージが表示。
2.
オーナー情報(owner → user)
(ア)
ユーザID(id)
端末利用者のユーザID
(イ)
ユーザ名(name)
端末利用者のユーザ名
(ウ)
ユーザ向けメッセージ(message)
ユーザに対するメッセージを表示。
アプリのバージョンアップ情報やシステム運営側からのメッセージを表示する。
3.
お友達情報(friend → user)
(ア)
ユーザID(id)
お友達のユーザID
(イ)
ユーザ名(name)
お友達のユーザ名
(ウ)
接続状況(status)
お友達の接続状態
1:接続中
2:会話中(同一会話に)
3:書き込み中(同一会話に)
4:会話中(別の会話に)
9:停止中
4.
会話相手情報(communication → room)
(ア)
ルームID(id)
会話中のルームID
ルームIDが空白の場合、会話無し(サーバへの定期問い合わせ)
または、発着信
(イ)
ルーム名(name)
コミュニティの会話の場合、名称が表示される。
(ウ)
ユーザ情報(user)
(1)ユーザID(id)
会話相手のユーザID
(2)ユーザ名(name)
会話相手のユーザ名
(3)接続状況(status)
会話相手の接続状態
1:接続中
2:会話中(同一会話に)
3:書き込み中(同一会話に)
4:会話中(別の会話に)
9:停止中
5.
メッセージ(messages → message)
(ア)
ユーザID(id)
メッセージ送信者のユーザID
(イ)
ユーザ名(name)
メッセージ送信者のユーザ名
(ウ)
メッセージ(comment)
メッセージ送信者が発信したメッセージ
6.
メッセージ(interrupts → interrupt)
(ア)
ルームID(id)
割込みルームID
(イ)
ルーム名(name)
コミュニティの会話の場合、名称が表示される。
(ウ)
ユーザ情報(user)
(1)ユーザID(id)
割込み会話に参加しているユーザID
(2)ユーザ名(name)
割込み会話に参加しているユーザ名
(3)接続状況(status)
割込み会話に参加しているユーザの接続状態
1:接続中
2:会話中(同一会話に)
3:書き込み中(同一会話に)
4:会話中(別の会話に)
9:停止中
In the present invention, as described above, the response to the http request is returned in the XML format. On the communication terminal side, XML is analyzed from the XML layout, and a screen is displayed based on the analyzed contents. FIG. 23 is a schematic diagram illustrating an XML layout of a message reception request according to an embodiment of the present invention. The XML layout in one embodiment of the present invention is as follows.
XML layout (corresponding to Fig. 23)
1.
Common parameter (result)
(A)
Output result (status)
Displays server processing results for http requests
Success
/ NotFount (URL, operation error) /
ServerError (Server side error: version error, database registration failure, etc.)
/
ClientError (client side error: device error, etc.)
(I)
Output result message (message)
An error message is displayed.
2.
Owner information (owner → user)
(A)
User ID (id)
User ID of terminal user
(I)
User name
User name of terminal user
(U)
Message for users (message)
Displays a message to the user.
App upgrade information and messages from the system management side are displayed.
3.
Friend information (friend → user)
(A)
User ID (id)
User ID of your friend
(I)
User name
Friends username
(U)
Connection status (status)
Friends connection status
1: Connected
2: Conversation (same conversation)
3: Writing (in the same conversation)
4: Conversing (to another conversation)
9: Stopped
Conversation information (communication → room)
(A)
Room ID (id)
Room ID during conversation
If the room ID is blank, there is no conversation (periodic inquiry to the server)
Or make and receive calls
(I)
Room name
In the case of community conversation, the name is displayed.
(U)
User information (user)
(1) User ID (id)
User ID of conversation partner
(2) User name (name)
User name of conversation partner
(3) Connection status (status)
Connection status of conversation partner
1: Connected
2: Conversation (same conversation)
3: Writing (in the same conversation)
4: Conversing (to another conversation)
9: Stopping
Messages (messages → message)
(A)
User ID (id)
User ID of the message sender
(I)
User name
User name of the message sender
(U)
Message
5. Message sent by message sender
Message (interrupts → interrupt)
(A)
Room ID (id)
Interrupt room ID
(I)
Room name
In the case of community conversation, the name is displayed.
(U)
User information (user)
(1) User ID (id)
User ID participating in interrupt conversation
(2) User name (name)
User name participating in interrupt conversation
(3) Connection status (status)
Connection status of users participating in interrupted conversation
1: Connected
2: Conversation (same conversation)
3: Writing (in the same conversation)
4: Conversing (to another conversation)
9: Stopped
Claims (31)
- インターネットを経由して情報交換が可能な複数の通信端末と、前記複数の通信端末間でやりとりされた情報を受信するアプリケーションサーバと、前記アプリケーションサーバで受信したチャットに係る文字情報を蓄積するデータベースサーバと、前記データベースサーバに記憶された情報の少なくとも一部を表示するwwwサーバとを具備するリアルタイムチャットシステムにおいて、
前記wwwサーバは前記チャットに係る文字情報をやりとりした前記複数の通信端末に対して該チャットに係る文字情報の記録の公開を許容する指令を受ける公開許可受付ルーチンを備え、
前記アプリケーションサーバは、前記公開を許容する指令を前記チャットに係る文字情報に関わる全ての前記複数の通信端末から受けた場合に前記データベースサーバに蓄積された前記チャットに係る文字情報の少なくとも一部を前記wwwサーバにて表示可能にする表示可能化ルーチンを備え、
前記システムは、所望の検索キーデータを受け付ける検索キー受付ルーチンと、前記受けつけられた検索キーデータを検索キーとして前記wwwサーバにて表示可能とされたチャットに係る文字情報について検索する検索ルーチンと、前記検索の結果を前記検索キーデータを受け付けた先に転送する転送ルーチンとを備えることを特徴とするコミュニケーションシステム。 A plurality of communication terminals capable of exchanging information via the Internet, an application server for receiving information exchanged between the plurality of communication terminals, and a database server for storing character information relating to chat received by the application server And a real-time chat system comprising a www server that displays at least a part of the information stored in the database server,
The www server includes a public permission acceptance routine for receiving an instruction that allows the plurality of communication terminals that have exchanged the character information related to the chat to disclose the recording of the character information related to the chat,
The application server receives at least a part of the character information related to the chat stored in the database server when receiving an instruction permitting the disclosure from all the plurality of communication terminals related to the character information related to the chat. A display enabling routine for enabling display on the www server;
The system includes a search key reception routine for receiving desired search key data, a search routine for searching for character information related to chats that can be displayed on the www server using the received search key data as a search key, And a transfer routine for transferring a result of the search to a destination where the search key data is received. - インターネットブラウザを経由してチャット及びメールを含む文字による情報交換が可能な複数の通信端末と、前記複数の通信端末間でやりとりされたチャット及び/もしくはメールに係る文字情報を受信するアプリケーションサーバと、前記アプリケーションサーバで受信した前記文字情報を蓄積するデータベースサーバと、前記データベースサーバに記憶された文字情報の少なくとも一部を表示するwwwサーバとを具備するリアルタイムチャットシステムにおいて、
前記wwwサーバは前記文字情報をやりとりした前記複数の通信端末に対して該文字情報の記録の公開を許容する指令を受ける公開許可受付ルーチンを備え、
前記アプリケーションサーバは、前記公開を許容する指令を前記文字情報に関わる全ての前記複数の通信端末から受けた場合に前記データベースサーバに蓄積された前記文字情報の少なくとも一部を前記wwwサーバにて表示可能にする表示可能化ルーチンを備え、
前記システムは、所望の検索キーデータを受け付ける検索キー受付ルーチンと、前記受けつけられた検索キーデータを検索キーとして前記wwwサーバにて表示可能とされた文字情報について検索する検索ルーチンと、前記検索の結果を前記検索キーデータを受け付けた先に転送する転送ルーチンとを備えることを特徴とするコミュニケーションシステム。 A plurality of communication terminals capable of exchanging information using characters including chat and mail via an Internet browser; an application server for receiving character information related to chat and / or mail exchanged between the plurality of communication terminals; In a real-time chat system comprising a database server that accumulates the character information received by the application server, and a www server that displays at least part of the character information stored in the database server,
The www server includes a public permission receiving routine for receiving a command for allowing the plurality of communication terminals that exchange the character information to disclose the recording of the character information,
The application server displays at least a part of the character information stored in the database server on the www server when receiving an instruction to permit the disclosure from all the plurality of communication terminals related to the character information. With a display enablement routine that enables
The system includes a search key reception routine for receiving desired search key data, a search routine for searching for character information that can be displayed on the www server using the received search key data as a search key, And a transfer routine for transferring the result to a destination where the search key data is received. - インターネットブラウザを経由して情報交換が可能な複数の通信端末と、前記複数の通信端末間でやりとりされたチャットに係る文字情報を受信するアプリケーションサーバと、前記アプリケーションサーバで受信した前記チャットに係る文字情報を蓄積するデータベースサーバと、前記データベースサーバに記憶された情報を表示するwwwサーバとを具備するリアルタイムチャットシステムにおいて、
前記リアルタイムチャットシステムは、所望の検索キーデータを受け付ける検索キー受付ルーチンと、前記受けつけられた検索キーデータを検索キーとして前記データベースサーバに格納されたチャットに係る文字情報について検索する検索ルーチンと、前記検索の結果を前記検索キーデータを受け付けた先に転送する転送ルーチンとを備えることを特徴とするコミュニケーションシステム。 A plurality of communication terminals capable of exchanging information via an Internet browser, an application server that receives character information related to chat exchanged between the plurality of communication terminals, and a character related to the chat received by the application server In a real-time chat system comprising a database server for accumulating information and a www server for displaying information stored in the database server,
The real-time chat system includes a search key reception routine for receiving desired search key data, a search routine for searching for character information related to chat stored in the database server using the received search key data as a search key, And a transfer routine for transferring a search result to a destination where the search key data is received. - インターネットブラウザを経由して情報交換が可能な複数の通信端末と、前記複数の通信端末間でやりとりされたチャット及び/もしくはメールに係る文字情報を受信するアプリケーションサーバと、前記アプリケーションサーバで受信した前記文字情報を蓄積するデータベースサーバと、前記データベースサーバに記憶された文字情報を表示するwwwサーバとを具備するリアルタイムチャットシステムにおいて、
前記リアルタイムチャットシステムは、所望の検索キーデータを受け付ける検索キー受付ルーチンと、前記受けつけられた検索キーデータを検索キーとして前記データベースサーバに格納された文字情報について検索する検索ルーチンと、前記検索の結果を前記検索キーデータを受け付けた先に転送する転送ルーチンとを備えることを特徴とするコミュニケーションシステム。 A plurality of communication terminals capable of exchanging information via an Internet browser, an application server that receives text information related to chat and / or mail exchanged between the plurality of communication terminals, and the application server that receives the character information In a real-time chat system comprising a database server that accumulates character information and a www server that displays character information stored in the database server,
The real-time chat system includes a search key reception routine for receiving desired search key data, a search routine for searching for character information stored in the database server using the received search key data as a search key, and a result of the search And a transfer routine for transferring the search key data to a destination where the search key data is received. - 定期的に前記データベースサーバにメッセージの受信の有無を問い合わせる問合せ手段と、前記問合せにより受け取った結果を画面に表示する表示手段とをさらに具備することを特徴とする請求項1乃至4記載のうち1項記載のコミュニケーションシステム。 5. The apparatus according to claim 1, further comprising inquiry means for periodically inquiring the database server whether or not a message has been received, and display means for displaying a result received by the inquiry on a screen. The communication system described in the section.
- 前記リアルタイムチャットシステムは、
位置情報システム(GPS)と、
前期位置情報システムを用いて特定の地域にいる全通信端末を抽出して該当全端末に係る利用者一覧を表示するルーチンと、
前記該当全端末に対しての同報もしくはそのうちの特定の端末に対しての発信を選択的に実行するルーチンと
をさらに備えることを特徴とする請求項1乃至4記載のうち1項記載のコミュニケーションシステム。 The real-time chat system
A location information system (GPS);
A routine for extracting all communication terminals in a specific area using the previous period location information system and displaying a list of users related to all the terminals;
5. The communication according to claim 1, further comprising: a routine that selectively executes broadcast to all the corresponding terminals or transmission to a specific terminal among them. system. - 前記チャットに関わるメッセージが前記該当全端末の画面にテロップで表示させる機能をさらに備えることを特徴とする請求項6記載のコミュニケーションシステム。 The communication system according to claim 6, further comprising a function for displaying messages related to the chat in a telop on the screens of all the terminals.
- 前記アプリケーションサーバと前記wwwサーバは1台のサーバが兼務することを特徴とする請求項1乃至4記載のうち1項記載のコミュニケーションシステム。 5. The communication system according to claim 1, wherein one server serves as both the application server and the www server.
- 前記チャットが行われる場を意味するルームに係る複数の画面を重畳的に表示できる複数ルーム機能と、第1のルームに係る画面から第2のルームに係る画面に切り替える切替機能とをさらに具備することを特徴とする請求項1もしくは3記載のコミュニケーションシステム。 A plurality of room functions capable of displaying a plurality of screens related to the room where the chat is performed in a superimposed manner, and a switching function for switching from the screen related to the first room to the screen related to the second room are further provided. The communication system according to claim 1 or 3, wherein
- 前記通信端末は、携帯電話、PHS、PDA、スマートフォンおよびコンピュータを含む通信可能な端末であることを特徴とする請求項1乃至4記載のうち1項記載のコミュニケーションシステム。 5. The communication system according to claim 1, wherein the communication terminal is a communicable terminal including a mobile phone, a PHS, a PDA, a smartphone, and a computer.
- 前記アプリケーションサーバは、前記複数の通信端末の少なくとも一つと会話情報の交換を行い、かつ前記データベースサーバに情報の蓄積を依頼するアプリケーションをさらに備えることを特徴とする請求項1乃至4記載のうち1項記載のコミュニケーションシステム。 5. The application server according to claim 1, further comprising an application for exchanging conversation information with at least one of the plurality of communication terminals and requesting the database server to store information. The communication system described in the section.
- 前記アプリケーションサーバは、前記チャット内容をリアルタイムで所望の言語に翻訳する翻訳処理部をさらに備えることを特徴とする請求項1乃至4記載のうち1項記載のコミュニケーションシステム。 5. The communication system according to claim 1, wherein the application server further includes a translation processing unit that translates the chat content into a desired language in real time.
- 前記チャット内容は、前記翻訳前の情報及び該翻訳後の情報が併記して前記通信端末に表示可能であることを特徴とする請求項12記載のコミュニケーションシステム。 13. The communication system according to claim 12, wherein the chat content can be displayed on the communication terminal together with the information before translation and the information after translation.
- 前記データベースサーバは、会員情報、および/または会話情報の記憶を行い、該記憶された情報は利用者からの削除指示を受ける場合を除いて削除されず、蓄積され検索に供され得ることを特徴とする請求項1乃至4記載のうち1項記載のコミュニケーションシステム。 The database server stores member information and / or conversation information, and the stored information is not deleted except when receiving a deletion instruction from a user, and can be accumulated and used for a search. The communication system according to claim 1, wherein:
- 前記wwwサーバは、前記会員情報の管理及び/もしくは表示、前記データベースサーバに格納された文字情報の管理及び/もしくは表示、ユーザ情報の管理及び/もしくは表示、画像ファイルの管理及び/もしくは表示、公開された会話の検索の各機能をコンピュータに果たさせるルーチンを備えることを特徴とする請求項1乃至4記載のうち1項記載のコミュニケーションシステム。 The www server manages and / or displays the member information, manages and / or displays character information stored in the database server, manages and / or displays user information, manages and / or displays image files, and publishes. 5. The communication system according to claim 1, further comprising a routine for causing a computer to perform each function of searching for a conversation made.
- 前記携帯電話は、各キャリアに対応する携帯電話用チャットアプリケーションを起動させ、或いはブラウザ経由でチャットを行うことを特徴とする請求項1乃至4記載のうち1項記載のコミュニケーションシステム。 5. The communication system according to claim 1, wherein the mobile phone activates a mobile phone chat application corresponding to each carrier or performs chat via a browser. 6.
- 前記通信端末におけるPHS、PDA、スマートフォンまたはコンピュータは、前記wwwサーバに配置されたチャットアプリケーションのプログラムを実行し、その結果をPHS、PDA、スマートフォンまたはコンピュータのブラウザもしくはプログラムが受信して画面表示することを特徴とする請求項1乃至4記載のうち1項記載のコミュニケーションシステム。 The PHS, PDA, smartphone or computer in the communication terminal executes a chat application program arranged on the www server, and the result is received by the PHS, PDA, smartphone or computer browser or program and displayed on the screen. The communication system according to claim 1, wherein the communication system is characterized in that:
- 前記通信端末は、前記アプリケーションサーバに対し、所与の時間の経過、前記通信端末からのチャットに係る文字情報の送信、発着信、および/または会話終了を含む所定のイベントが発生した際、httpリクエストを送信することを特徴とする請求項1もしくは3記載のコミュニケーションシステム。 When the communication terminal generates a predetermined event including the passage of a given time, transmission of character information related to chat from the communication terminal, outgoing / incoming call, and / or conversation end to the application server, The communication system according to claim 1, wherein the request is transmitted.
- 前記通信端末は、httpリクエストに対する返答が一定時間ない場合、再度前記アプリケーションサーバへhttpリクエストを送信することを特徴とする請求項1もしくは3記載のコミュニケーションシステム。 4. The communication system according to claim 1, wherein the communication terminal transmits an http request to the application server again when there is no response to the http request for a predetermined time.
- 前記通信端末は、前記アプリケーションサーバに対してhttpリクエストに対する返答を一定回数再送信してもなお返答がない場合、会話を終了することを特徴とする請求項1もしくは3記載のコミュニケーションシステム。 4. The communication system according to claim 1 or 3, wherein the communication terminal terminates the conversation if there is still no response even after retransmitting a response to the http request to the application server a predetermined number of times.
- 前記通信端末は、httpリクエストを一定回数再送信したのち、前記アプリケーションサーバから応答が返ってきた場合には、正常にチャットを行っていた時点のルーム番号、チャット開始時刻を含む前記データベースサーバに格納された会話情報を復旧させ、会話の継続を行うことを特徴とする請求項1もしくは3記載のコミュニケーションシステム。 If the response is returned from the application server after retransmitting an http request for a certain number of times, the communication terminal stores the room number and chat start time at the time of normal chatting in the database server. 4. The communication system according to claim 1, wherein the conversation information is restored and the conversation is continued.
- 前記通信端末は、前記アプリケーションサーバに対するhttpリクエストの送信をGET方式で行うことを特徴とする請求項1乃至4記載のうち1項記載のコミュニケーションシステム。 5. The communication system according to claim 1, wherein the communication terminal transmits an http request to the application server by a GET method. 6.
- 前記携帯電話は、前記携帯電話用アプリケーションの起動において、電波状態の変動、または他の電話の着信およびメールの受信を含む所定のイベントによってアプリケーションが中断した場合、一定時間内でのアプリケーションの再起動により、中断前の状態に復旧できることを特徴とする請求項1もしくは3記載のコミュニケーションシステム。 When the application for a mobile phone is interrupted due to a change in a radio wave state or a predetermined event including reception of another telephone and reception of an email when the application for the mobile phone is started, the application is restarted within a predetermined time. The communication system according to claim 1, wherein the communication system can be restored to the state before the interruption.
- 前記通信端末は、前記アプリケーションサーバにhttpリクエストを送信するが、httpリクエストに対する返答はXML形式であることを特徴とする請求項1もしくは3記載のコミュニケーションシステム。 4. The communication system according to claim 1, wherein the communication terminal transmits an http request to the application server, and a response to the http request is in an XML format.
- 前記通信端末は、前記アプリケーションサーバからhttpリクエストに対する返信をXML形式で受信するが、XMLレイアウトからXML文を解析し、その内容に基づいて画面表示を行うことを特徴とする請求項1もしくは3記載のコミュニケーションシステム。 4. The communication terminal receives a reply to an http request from the application server in an XML format, analyzes an XML sentence from an XML layout, and displays a screen based on the content. Communication system.
- 会話相手を呼び出す発信機能、および/または会話相手が呼出に応答する着信機能をさらに備えることを特徴とする請求項1もしくは3記載のコミュニケーションシステム。 4. The communication system according to claim 1 or 3, further comprising an outgoing call function for calling a conversation partner and / or an incoming call function for responding to a call by the conversation partner.
- 前記チャットアプリケーションを起動しチャット内容を入力する際、チャット内容の入力が開始されかつ入力中であることを前記アプリケーションサーバ経由で前記データベースサーバに送信して情報を格納し、会話相手がメッセージの確認を行った際に前記データベースサーバ内の前記情報を会話相手の通信端末に送信することを特徴とする請求項16もしくは17記載のコミュニケーションシステム。 When the chat application is activated and chat content is entered, the chat content input is started and is being entered, the information is stored by transmitting to the database server via the application server, and the conversation partner confirms the message. 18. The communication system according to claim 16, wherein the information in the database server is transmitted to a communication terminal of a conversation partner when the communication is performed.
- 任意の通信端末のアプリケーションに係る現在の稼働状況を把握するための現状把握手段と、前記現状把握手段によって把握された現状に応じた表示を行う現状表示手段とをさらに具備することを特徴とする請求項1乃至4記載のうち1項記載のコミュニケーションシステム。 The present invention further comprises a current state grasping means for grasping a current operation state relating to an application of an arbitrary communication terminal, and a current state display means for performing display according to the current state grasped by the current state grasping means. The communication system according to claim 1, wherein the communication system is one of claims 1 to 4.
- 前記リアルタイムチャットシステムは、発信者からの会話を受信者が最初に着信を了解した時点から、会話終了、または一定時間メッセージのやりとりが行われなかった時点までを少なくとも会話時間として計測する会話時間計測機能をさらに備えることを特徴とする請求項1もしくは3記載のコミュニケーションシステム。 The real-time chat system measures a conversation time at least as a conversation time from the time when a receiver first receives a conversation from a sender to the time when the conversation ends or a message is not exchanged for a certain period of time. The communication system according to claim 1, further comprising a function.
- 前記会話時間計測機能により計測された時間に応じて課金する課金機能をさらに具備することを特徴とする請求項29記載のコミュニケーションシステム。 30. The communication system according to claim 29, further comprising a charging function for charging according to the time measured by the conversation time measuring function.
- インターネットブラウザを経由して情報交換が可能な複数の通信端末と、前記複数の通信端末間でやりとりされたチャットデータを受信する第1のサーバと、前記第1のサーバで受信した前記チャット及び/もしくはメールに係る文字情報を蓄積する第2のサーバと、前記第2のサーバに記憶された情報を表示する第3のサーバサーバとを具備するコミュニケーションシステムにおいて、
前記第1のサーバは前記文字情報をやりとりした前記複数の通信端末に対して該文字情報の記録の公開を許容する指令を受ける公開許可受付ルーチンと、前記公開を許容する指令を前記文字情報に関わる全ての前記複数の通信端末から受けた場合に前記第2のサーバに蓄積された前記文字情報を前記第3のサーバにて表示可能にする表示可能化ルーチンを備え、
前記システムは、所望の検索キーデータを受け付ける検索キー受付ルーチンと、前記受けつけられた検索キーデータを検索キーとして前記第3のサーバにて表示可能とされた文字情報について検索する検索ルーチンと、前記検索の結果を前記検索キーデータを受け付けた先に転送する転送ルーチンとを備えることを特徴とするコミュニケーションシステム。 A plurality of communication terminals capable of exchanging information via an Internet browser; a first server for receiving chat data exchanged between the plurality of communication terminals; and the chat and / or received by the first server Alternatively, in a communication system comprising a second server that accumulates character information relating to mail and a third server server that displays information stored in the second server,
The first server receives a command for permitting disclosure of the recording of the character information to the plurality of communication terminals that have exchanged the character information, and a command for permitting the disclosure to the character information. A display enabling routine for allowing the third server to display the character information stored in the second server when received from all the plurality of communication terminals involved;
The system includes a search key reception routine for receiving desired search key data, a search routine for searching for character information that can be displayed on the third server using the received search key data as a search key, And a transfer routine for transferring a search result to a destination where the search key data is received.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2011547088A JPWO2011077501A1 (en) | 2009-12-26 | 2009-12-26 | Communication system |
PCT/JP2009/007322 WO2011077501A1 (en) | 2009-12-26 | 2009-12-26 | Communication system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2009/007322 WO2011077501A1 (en) | 2009-12-26 | 2009-12-26 | Communication system |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2011077501A1 true WO2011077501A1 (en) | 2011-06-30 |
Family
ID=44195065
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2009/007322 WO2011077501A1 (en) | 2009-12-26 | 2009-12-26 | Communication system |
Country Status (2)
Country | Link |
---|---|
JP (1) | JPWO2011077501A1 (en) |
WO (1) | WO2011077501A1 (en) |
Cited By (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2014071616A (en) * | 2012-09-28 | 2014-04-21 | Konami Digital Entertainment Co Ltd | Message display system, control method, and program |
JP2014096096A (en) * | 2012-11-12 | 2014-05-22 | Konami Digital Entertainment Co Ltd | Display device, control method, and program |
JP2014096097A (en) * | 2012-11-12 | 2014-05-22 | Konami Digital Entertainment Co Ltd | Display device, control method, and program |
JP2014106592A (en) * | 2012-11-26 | 2014-06-09 | Konami Digital Entertainment Co Ltd | Display device, control method, and program |
CN104734940A (en) * | 2013-12-23 | 2015-06-24 | 华为技术有限公司 | Message display method for instant messaging tool and user terminals |
JP2015127947A (en) * | 2013-11-27 | 2015-07-09 | 株式会社リコー | Information process system and method |
JP2015154196A (en) * | 2014-02-13 | 2015-08-24 | 株式会社リコー | Transmission system, transmission management device and program |
WO2015194339A1 (en) * | 2014-06-17 | 2015-12-23 | 株式会社ディー・エヌ・エー | Audio chat management device and method |
CN105656706A (en) * | 2014-11-14 | 2016-06-08 | 北京通达无限科技有限公司 | Business data processing method and device |
WO2016163951A1 (en) * | 2015-04-07 | 2016-10-13 | Combuilder Fmit Pte Ltd | Method and user interface for project management |
JPWO2015186534A1 (en) * | 2014-06-06 | 2017-04-20 | ソニー株式会社 | Information processing apparatus and method, and program |
JP2017107255A (en) * | 2015-11-26 | 2017-06-15 | Line株式会社 | Control method for information processing apparatus, information processing apparatus and control program, and terminal control method and terminal control program |
JP2018507480A (en) * | 2015-02-04 | 2018-03-15 | アリババ・グループ・ホールディング・リミテッドAlibaba Group Holding Limited | Method and apparatus for storing instant messaging chat records |
JP6375039B1 (en) * | 2017-07-21 | 2018-08-15 | テイク エイト インコーポレイテッド | Program, photographing method and terminal |
US10205754B2 (en) | 2014-02-13 | 2019-02-12 | Ricoh Company, Ltd. | Transmission system, transmission management apparatus and non-transitory computer-readable information recording medium |
JP2019161260A (en) * | 2018-03-07 | 2019-09-19 | 株式会社Nttドコモ | Communication control system |
WO2019244703A1 (en) * | 2018-06-20 | 2019-12-26 | Kotozna株式会社 | Message transmission/reception system |
JPWO2019003395A1 (en) * | 2017-06-29 | 2020-06-11 | 株式会社オプティム | Call center conversation content display system, method and program |
Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2000181847A (en) * | 1998-12-18 | 2000-06-30 | Fujitsu Ltd | Method and system for supporting communication |
JP2001344184A (en) * | 2000-03-31 | 2001-12-14 | Fujitsu Ltd | Chat system, object server, chat object content recording medium, and chat object control program |
JP2002259315A (en) * | 2001-02-27 | 2002-09-13 | Fujitsu Ltd | Conference server program |
JP2003058482A (en) * | 2001-08-14 | 2003-02-28 | Fujitsu Ltd | Method for providing area chat room, method for processing terminal side area chat, recording medium recording area chat room providing/processing program and area chat room providing device |
JP2003058481A (en) * | 2001-08-10 | 2003-02-28 | Logo Vista Corp | Multilanguage chat system |
JP2003085114A (en) * | 2001-09-11 | 2003-03-20 | Bagujii Data:Kk | Chat system for cellular phone terminal |
JP2003296257A (en) * | 2002-04-01 | 2003-10-17 | Nec Infrontia Corp | Network conference system |
JP2003316740A (en) * | 2002-04-25 | 2003-11-07 | Nippon Telegr & Teleph Corp <Ntt> | Communication restart service system, communication restart service method, program, and storage medium |
JP2005235118A (en) * | 2004-02-23 | 2005-09-02 | Nippon Telegr & Teleph Corp <Ntt> | Information extracting method and device |
JP2008250889A (en) * | 2007-03-30 | 2008-10-16 | Nifty Corp | Community management system |
JP2009169914A (en) * | 2007-12-21 | 2009-07-30 | Taito Corp | Service providing system, service providing method and computer program |
-
2009
- 2009-12-26 JP JP2011547088A patent/JPWO2011077501A1/en active Pending
- 2009-12-26 WO PCT/JP2009/007322 patent/WO2011077501A1/en active Application Filing
Patent Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2000181847A (en) * | 1998-12-18 | 2000-06-30 | Fujitsu Ltd | Method and system for supporting communication |
JP2001344184A (en) * | 2000-03-31 | 2001-12-14 | Fujitsu Ltd | Chat system, object server, chat object content recording medium, and chat object control program |
JP2002259315A (en) * | 2001-02-27 | 2002-09-13 | Fujitsu Ltd | Conference server program |
JP2003058481A (en) * | 2001-08-10 | 2003-02-28 | Logo Vista Corp | Multilanguage chat system |
JP2003058482A (en) * | 2001-08-14 | 2003-02-28 | Fujitsu Ltd | Method for providing area chat room, method for processing terminal side area chat, recording medium recording area chat room providing/processing program and area chat room providing device |
JP2003085114A (en) * | 2001-09-11 | 2003-03-20 | Bagujii Data:Kk | Chat system for cellular phone terminal |
JP2003296257A (en) * | 2002-04-01 | 2003-10-17 | Nec Infrontia Corp | Network conference system |
JP2003316740A (en) * | 2002-04-25 | 2003-11-07 | Nippon Telegr & Teleph Corp <Ntt> | Communication restart service system, communication restart service method, program, and storage medium |
JP2005235118A (en) * | 2004-02-23 | 2005-09-02 | Nippon Telegr & Teleph Corp <Ntt> | Information extracting method and device |
JP2008250889A (en) * | 2007-03-30 | 2008-10-16 | Nifty Corp | Community management system |
JP2009169914A (en) * | 2007-12-21 | 2009-07-30 | Taito Corp | Service providing system, service providing method and computer program |
Cited By (26)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2014071616A (en) * | 2012-09-28 | 2014-04-21 | Konami Digital Entertainment Co Ltd | Message display system, control method, and program |
JP2014096096A (en) * | 2012-11-12 | 2014-05-22 | Konami Digital Entertainment Co Ltd | Display device, control method, and program |
JP2014096097A (en) * | 2012-11-12 | 2014-05-22 | Konami Digital Entertainment Co Ltd | Display device, control method, and program |
JP2014106592A (en) * | 2012-11-26 | 2014-06-09 | Konami Digital Entertainment Co Ltd | Display device, control method, and program |
JP2015127947A (en) * | 2013-11-27 | 2015-07-09 | 株式会社リコー | Information process system and method |
US10237210B2 (en) | 2013-11-27 | 2019-03-19 | Ricoh Company, Ltd. | Information processing system and method of processing information |
CN104734940A (en) * | 2013-12-23 | 2015-06-24 | 华为技术有限公司 | Message display method for instant messaging tool and user terminals |
JP2016515251A (en) * | 2013-12-23 | 2016-05-26 | ▲ホア▼▲ウェイ▼技術有限公司Huawei Technologies Co.,Ltd. | Information display method and user terminal for instant messaging tool |
JP2015154196A (en) * | 2014-02-13 | 2015-08-24 | 株式会社リコー | Transmission system, transmission management device and program |
US10205754B2 (en) | 2014-02-13 | 2019-02-12 | Ricoh Company, Ltd. | Transmission system, transmission management apparatus and non-transitory computer-readable information recording medium |
JPWO2015186534A1 (en) * | 2014-06-06 | 2017-04-20 | ソニー株式会社 | Information processing apparatus and method, and program |
US9942393B2 (en) | 2014-06-17 | 2018-04-10 | DeNA Co., Ltd. | Audio chat management device and method |
CN106576126B (en) * | 2014-06-17 | 2019-06-11 | 株式会社得那 | Audio chat management equipment and method |
WO2015194339A1 (en) * | 2014-06-17 | 2015-12-23 | 株式会社ディー・エヌ・エー | Audio chat management device and method |
CN106576126A (en) * | 2014-06-17 | 2017-04-19 | 株式会社得那 | Audio chat management device and method |
CN105656706A (en) * | 2014-11-14 | 2016-06-08 | 北京通达无限科技有限公司 | Business data processing method and device |
JP2018507480A (en) * | 2015-02-04 | 2018-03-15 | アリババ・グループ・ホールディング・リミテッドAlibaba Group Holding Limited | Method and apparatus for storing instant messaging chat records |
US10659412B2 (en) | 2015-02-04 | 2020-05-19 | Alibaba Group Holding Limited | Method and device for saving chat record of instant messaging |
WO2016163951A1 (en) * | 2015-04-07 | 2016-10-13 | Combuilder Fmit Pte Ltd | Method and user interface for project management |
JP2017107255A (en) * | 2015-11-26 | 2017-06-15 | Line株式会社 | Control method for information processing apparatus, information processing apparatus and control program, and terminal control method and terminal control program |
JPWO2019003395A1 (en) * | 2017-06-29 | 2020-06-11 | 株式会社オプティム | Call center conversation content display system, method and program |
JP6375039B1 (en) * | 2017-07-21 | 2018-08-15 | テイク エイト インコーポレイテッド | Program, photographing method and terminal |
JP2019023846A (en) * | 2017-07-21 | 2019-02-14 | テイク エイト インコーポレイテッド | Program, photographing method, and terminal |
JP2019161260A (en) * | 2018-03-07 | 2019-09-19 | 株式会社Nttドコモ | Communication control system |
WO2019244703A1 (en) * | 2018-06-20 | 2019-12-26 | Kotozna株式会社 | Message transmission/reception system |
JP2019219891A (en) * | 2018-06-20 | 2019-12-26 | Kotozna株式会社 | Message transmitting and receiving system |
Also Published As
Publication number | Publication date |
---|---|
JPWO2011077501A1 (en) | 2013-05-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2011077501A1 (en) | Communication system | |
AU2020203752B2 (en) | Authentication of service requests initiated from a social networking site | |
Donner et al. | Exploring mobile-only Internet use: Results of a training study in urban South Africa | |
Puri | The web of insights: The art and practice of webnography | |
US7822821B2 (en) | Access point object depositable on a web page and useful for initiating communication between depositing user and buddy | |
TWI420409B (en) | Device, media and method for mobile contextual sms advertising | |
US20110113086A1 (en) | System and method for monitoring activity on internet-based social networks | |
CN102474507A (en) | Telephony discovery mashup and presence | |
CN101198948A (en) | Instant messaging with search characteristics | |
KR20040081058A (en) | System and method for social interaction | |
KR20160108421A (en) | Dynamic invites with automatically adjusting displays | |
WO2006020758A2 (en) | Resource based virtual communities | |
CN101611398A (en) | The context-sensitive searches and the function that are used for instant messaging applications | |
CN102158614A (en) | Context sensitive, cloud-based telephony | |
CN101341482A (en) | Voice initiated network operations | |
JP5732530B2 (en) | Intercommunication method, apparatus and system for intercommunication information on the Internet | |
CN112437004A (en) | Information processing method, information processing device, electronic equipment and storage medium | |
Kobayashi et al. | Social media agency robot for elderly people | |
WO2007058282A1 (en) | Chat processing device, method, and computer program | |
Beal | Twitter dictionary: A guide to understanding twitter lingo | |
JP2007535880A (en) | A method of searching for a specific computer IP address on the World Wide Web by adding an identification number to a numerical array formed by sequentially combining several specific telephone numbers | |
Francke et al. | South African youth and mobile technology impact: The MXit phenomenon | |
WO2018140413A1 (en) | Collective address book system | |
Khattab | Infobotting COVID-19: A case study of Ask Nameesa in Egypt | |
KR20050059380A (en) | Community connecting system through network and method thereof |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 09852518 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2011547088 Country of ref document: JP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 11/10/2012) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 09852518 Country of ref document: EP Kind code of ref document: A1 |