WO2012161437A2 - Procédé de fourniture d'un service de chat basé sur le client, un dispositif de client, un serveur de chat, système, et support d'enregistrement - Google Patents

Procédé de fourniture d'un service de chat basé sur le client, un dispositif de client, un serveur de chat, système, et support d'enregistrement Download PDF

Info

Publication number
WO2012161437A2
WO2012161437A2 PCT/KR2012/003655 KR2012003655W WO2012161437A2 WO 2012161437 A2 WO2012161437 A2 WO 2012161437A2 KR 2012003655 W KR2012003655 W KR 2012003655W WO 2012161437 A2 WO2012161437 A2 WO 2012161437A2
Authority
WO
WIPO (PCT)
Prior art keywords
message
chat
client
client device
package data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/KR2012/003655
Other languages
English (en)
Korean (ko)
Other versions
WO2012161437A3 (fr
Inventor
김태우
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Neowiz Internet Corp
Original Assignee
Neowiz Internet Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Neowiz Internet Corp filed Critical Neowiz Internet Corp
Publication of WO2012161437A2 publication Critical patent/WO2012161437A2/fr
Publication of WO2012161437A3 publication Critical patent/WO2012161437A3/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00—Digital computers in general; Data processing equipment in general
    • G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/58—Message adaptation for wireless communication

Definitions

  • the present invention relates to chat service technology, and more particularly, to a chat service technology suitable for a mobile environment.
  • a chat server performs many functions such as user computer connection management, user management, chat room management, message management, various control functions, and the like.
  • the conventional chat service is a server-based chat service.
  • the conventional chat service is performed in a better network situation and in a general web environment than in a mobile environment.
  • the server-based chat service is complex and many functions are provided to the user, the server has to perform many functions as well as the user's computer connected to the server.
  • an object of the present invention is to provide a client-based chat service suitable for a mobile environment.
  • the sender information that is identification information corresponding to the first client device, the recipient list and message type information including identification information respectively corresponding to one or more second client devices
  • a message receiver configured to receive, from the first client device, a message header including a message and package data in which a message input from the first client device is packaged;
  • a message storage unit for storing the package data;
  • a message transmitting unit which transmits the stored package data to the at least one second client device by referring to the recipient list.
  • the present invention provides a client-based chat service in a chat server, comprising: sender information that is identification information corresponding to a first client device and identification information corresponding to one or more second client devices, respectively.
  • sender information that is identification information corresponding to a first client device and identification information corresponding to one or more second client devices, respectively.
  • a first message header including the first sender information, the first receiver list, and the first message type information is packaged with the first message and the first message is packaged.
  • a first package data transmitter for generating package data and transmitting the generated first package data to a chat server;
  • a second package data receiver configured to receive from the chat server a second message header including a second sender information, a second receiver list, and a second message type information, and second package data in which a second message is packaged;
  • a chat screen controller configured to output the inputted first message and the second message to a chat screen.
  • the present invention provides a method for providing a client-based chat service, the client device comprising the steps of: outputting the input first message to the chat screen; When the first message is input, packaging a first message header including first sender information, a first receiver list, and first message type information and the inputted first message to generate first package data; Transmitting the generated first package data to a chat server; Receiving, from the chat server, a second message header including a second sender information, a second receiver list, and a second message type information, and second package data in which a second message is packaged; And outputting the second message to the chat screen.
  • the present invention when the message is input, package the message header including the sender information, recipient list and message type information and the input message to generate and transmit the package data, and sends the input message to the chat screen A first client output to the; A chat server which receives and stores the package data and delivers the package data with reference to the recipient list; And a second client receiving the package data and outputting a message packaged in the package data to a chat screen, wherein the recipient list includes identification information corresponding to the second client.
  • the present invention when the message is input, package the message header including the sender information, recipient list and message type information and the input message to generate and transmit the package data, and sends the input message to the chat screen A first client output to the; A chat server which receives and stores the package data and delivers the package data with reference to the recipient list; And a second client receiving the package data and outputting a message packaged in the package data to a chat screen, wherein the recipient list includes identification information corresponding to the second client.
  • the present invention in the recording medium recording a program for executing a method for providing a client-based chat service, the function of outputting the input first message on the chat screen, the first message is input And a first message header including a first sender information, a first recipient list, and a first message type information and a package of the inputted first message to generate first package data, and the generated first package.
  • a second message header including a second sender information, a second recipient list, and a second message type information, and second package data packed with a second message;
  • a computer-readable recording medium having recorded thereon a program implementing a function and a function of outputting the second message to the chat screen.
  • FIG. 1 is a diagram schematically illustrating a system for providing a client-based chat service according to an embodiment of the present invention.
  • FIG. 2 is a block diagram of a chat server providing a client-based chat service according to an embodiment of the present invention.
  • FIG. 3 is a flowchart illustrating a method in which a chat server provides a client-based chat service according to an exemplary embodiment of the present invention.
  • FIG. 4 is a block diagram of a client device for providing a client-based chat service according to an embodiment of the present invention.
  • FIG. 5 is a flowchart illustrating a method of providing a client-based chat service by a client device according to an exemplary embodiment of the present invention.
  • FIG. 6 is a diagram illustrating a message transmission procedure and a message reception procedure according to a protocol for providing a client-based chat service according to an embodiment of the present invention.
  • FIG. 7 is a diagram illustrating a data format according to a protocol for providing a client-based chat service according to an embodiment of the present invention.
  • FIG. 8 is a diagram exemplarily defining message type information according to a protocol for providing a client-based chat service according to an embodiment of the present invention.
  • 9 to 15 are diagrams for explaining a client-based chat service according to an embodiment of the present invention.
  • FIG. 1 is a diagram schematically illustrating a system for providing a client-based chat service according to an embodiment of the present invention.
  • a system for providing a client-based chat service includes a client device 100 of a user who uses a chat service and a message input by a user in the client device 100. Chat server 110 and the like delivered between the client device (100).
  • the chat service disclosed in the present invention is a "client-based chatting service", which is more suitable for a mobile environment in which a personal identity is relatively clear as compared to a web environment.
  • mobile environment refers to an environment in which a user subscribed to a telecommunication company uses a mobile communication service or a wireless communication service.
  • the personal identity is clear.
  • a chat server performs many functions such as user computer connection management, user management, chat room management, message management, various control functions, and the like.
  • the conventional chat service is a server-based chat service.
  • the conventional chat service is performed in a better network situation than in a mobile environment and in a general web environment.
  • the server-based chat service is complex and many functions are provided to the user, the server has to perform many functions as well as the user's computer connected to the server.
  • the functional elements of the heavy chat service provided in the web environment are simplified to be suitable for the mobile environment described above, and the chat server 110 is simplified.
  • the functional elements only the message transfer function between the client devices 100 is performed, and the client device 100 performs the remaining simplified functional elements. This will be described in more detail with reference to FIGS. 2 to 3.
  • the client device 100 and the chat server 110 included in the system for providing a client-based chat service communicate with each other through a network 120 to provide a chat service.
  • the network 120 is a wired or wireless network, an access network to which the chat server 110 is connected, an access network to which the client device 100 is connected (eg, a mobile communication network, a wireless LAN (WiFi), etc.), It may include a core network (Core Network), etc., which may be in various forms connecting the access networks.
  • the client device 100 described above may be a smartphone, a tablet PC, a mobile communication terminal, or the like, and may be any portable terminal having a communication function.
  • the client device 100 executes an application installed through an application store server to provide a client-based chat service according to an embodiment of the present invention. That is, an application installed in the client device 100 through the application store server may use a client base according to an embodiment of the present invention by using a hardware configuration (eg, a communication module, a memory, a processor, a display, etc.) of the client device 100. Chat service.
  • a hardware configuration eg, a communication module, a memory, a processor, a display, etc.
  • the chat server 110 performs a message transfer function between the client devices 100. It will be described in more detail below with reference to 2-3.
  • FIG 2 is a block diagram of a chat server 110 that provides a client-based chat service according to an embodiment of the present invention.
  • the client device 100 that transmits the message to the chat server 110 in order to deliver the input message to the other client device 100 is also referred to as a "first client device 100a", the chat server ( The client device 110 that receives the message stored in 100 is also referred to as the "second client device 100b.”
  • One client device 100 operates as the first client device 100a when a message is input and transmitted to the chat server 100, and moves to the second client device 100b when receiving a message from the chat server 100.
  • the first client device 100a and the second client device 100b may be different client devices 100, or differently represent the same client device 100 to distinguish roles at any one point in time. have.
  • the chat server 110 may transmit a message input from the first client device 100a to deliver a message.
  • Message receiving unit 210 to receive from the 100a, the message storage unit 220 for storing the message received from the first client device (100a), and the message transmission unit for transmitting the stored message to the second client device (100b) ( 230) and the like.
  • a message input by the user is packaged by attaching a message header. And delivered in the form of package data.
  • the message header includes sender information for sending a message, a recipient list including recipient information for receiving a message, message type information, and the like.
  • package data, a message, and a message header transmitted from the first client device 100a to the chat server 110 are also referred to as “first package data”, “first message”, and “first message header”.
  • package data, messages, and message headers transmitted from the chat server 110 to the second client device 100b are also referred to as “second package data”, “second message”, and “second message header”.
  • the message M When the message M is delivered from the client device A to the client device B through the chat server 110, the message M received by the chat server 110 from the client device A is the first message, and the chat server 110 is connected to the client device.
  • Message M sent to B is the second message.
  • the message M that the client device A sends to the chat server 110 is the first message
  • the message M that the client device B receives from the chat server 110 is the second message. That is, the "first message and the second message" is used to distinguish between the message received by the chat server 110 and the message to be transmitted, or to distinguish between the message sent by the client device 100 and the received message. In fact, it may be the same message.
  • the first package data is transmitted from the first client device 100a to the second client device 100b through the chat server 110.
  • the message receiver 210 When the message is packaged and delivered, the message receiver 210 includes first sender information, which is identification information corresponding to the first client device 100a, and identification information corresponding to one or more second client devices 100b, respectively.
  • the first client device 100a includes the first package data in which the "first message header" including the first recipient list and the first message type information and the "first message” input from the first client device 100a are packaged. From).
  • the message storage unit 220 stores the first package data received from the first client device 100a in the message storage space.
  • the message transmitter 230 transmits the first package data stored in the message storage space to the one or more second client devices 100b by referring to the first recipient list in the first package data.
  • the identification information corresponding to the client policing 100 may be, for example, personally unique information such as a phone number and user information that may correspond to the phone number.
  • the above-described message transmitter 230 may transmit the stored first package data to one or more second client devices 100b in a pull method or a push method.
  • the message transmitter 230 stores the first package in which identification information corresponding to the second client device 100b is stored. It is checked whether it is included in the first recipient list in the data, and if it is found to be included, the first package data stored in the second client device 100b is transmitted. In this case, the message request data is transmitted according to a user's input of the second client device 100b, or an application installed in the second client device 100b is executed and the application automatically sends the message request data when a periodic or event occurs. Send to the chat server 110.
  • the message transmitter 230 checks the first recipient list in the stored first package data when the first package data is stored, and finds the corresponding second client device through this confirmation.
  • the first package data can be transmitted to 100b.
  • the second client device 100b may be in a state capable of receiving the first package data, or may simply have an application installed in the second client device 100b running.
  • the system includes a message header including sender information, a recipient list, and message type information when a message is input.
  • Package the input message to generate and send package data, and receive and store the package data from the first client device 100a for outputting the input message to the chat screen, and the package data from the first client device 100a.
  • the chat server 110 which delivers package data with reference to the recipient list included in the message header packaged in the package, receives the package data from the chat server 110, and outputs a message packaged in the received package data to the chat screen. It includes a second client device (100b).
  • the recipient list included in the message header packaged in the package data includes identification information corresponding to the second client device 100b.
  • the second client device 100b may perform a management function such as adding a new participant or deleting an existing participant by grasping the chat participant list based on the sender information and the recipient list included in the message header packaged in the package data. have.
  • FIG 3 is a flowchart illustrating a method in which the chat server 110 provides a client-based chat service according to an exemplary embodiment of the present invention.
  • the method for providing a client-based chat service by the chat server 110 may include first sender information, one or more identification information corresponding to the first client device 100a, and one or more chatters.
  • the first message list including the first recipient list and the first message type information including identification information corresponding to the second client device 100b and the first message input from the first client device 100a are packaged.
  • a client device 100 that provides a client-based chat service according to an embodiment of the present invention will be described in more detail with reference to FIGS. 4 and 5.
  • FIG. 4 is a block diagram of a client device 100 that provides a client-based chat service according to an embodiment of the present invention.
  • the client device 100 providing a client-based chat service may include first sender information, a first receiver list, and a first receiver.
  • the package data receiver 420 may include a chat screen controller 430 for outputting a first message input by a user and a second message packaged in the second package data to a chat screen.
  • the client device 100 that transmits the first package data by the first package data transmitter 410 operates as the first client device 100a and receives the second package data by the second package data receiver 420.
  • the client device 100 operates as the second client device 100b.
  • the first package data transmitter 410 described above is configured to chat with one or more other client devices (the user of the client device 100) based on a user input or a pre-managed chat participant list to package and transmit the first message.
  • the first recipient list including identification information corresponding to the client device of the user or the client device of the user who is chatting with the user of the client device 100.
  • the method of setting the first recipient list according to the user input may be a method of setting the first recipient list when a user of the client device 100 invites a user to chat.
  • the method of setting the first recipient list based on the previously managed chat participant list may be a method of setting the first recipient list while the chat is already being performed.
  • the client device 100 that provides a client-based chat service may perform a function of managing a list of all users (participants) who are chatting.
  • the client device 100 that provides a client-based chat service according to an embodiment of the present invention may include identification information corresponding to one or more other client devices and the client device 100, respectively.
  • the chat participant list manager 440 may further include a chat participant list manager.
  • the chat participant list manager 440 described above after receiving the second package data of which the second message type information is "invitation message type information" from the chat server 110, the second message packaged in the second package data. On the basis of the second receiver list included in the header, identification information corresponding to the new client device may be added to the chat participant list previously managed, and identification information corresponding to the new client device may be added.
  • identification information corresponding to the client device of the user to be invited is displayed in the recipient list (the second receiver list from the perspective of the client device 100).
  • the message type information is set as the invitation message type information
  • the package data (second package data from the client device 100's point of view) is transmitted through the chat server 110, and all client devices that receive the package data are received. Adds "identification information corresponding to the client device of the user to be invited" which is not included in the existing participant list.
  • the chat participant list manager 440 described above after receiving the second package data whose second message type information is "outgoing message type information" from the chat server 110, the second message packaged in the second package data.
  • the identification information corresponding to the specific other client device, which is the second sender information included in the header, may be deleted from the chat participant list previously managed.
  • the first message type information and the second message type information mentioned above may be one of invitation message type information, general message type information, and exit message type information.
  • the second package data receiving unit 420 described above may check whether there is a second package data to be brought into the message storage space of the chat server 110.
  • the message request data including the identification information corresponding to the apparatus 100 may be transmitted to the chat server 110 to receive the second package data.
  • the second receiver list in the received second package data includes identification information corresponding to the client device 100.
  • the second package data receiver 420 described above may receive the message request data in a standby state without transmitting the message request data to the chat server 110.
  • the client-based chat service may be a 1-1 chat service or a group chat service.
  • the 1-1 chat service and the group chat service differ only in one or more identification information corresponding to the client from the recipient list included in the message header packaged in the package data to be delivered.
  • the operation of 110 and the client device 100 is the same.
  • group information for identifying a chat group may be further included in a message header packaged in package data.
  • a chat group means a group of users (client devices) chatting together, and a chat group may mean a group of users (client devices) in the message delivery range because the message is delivered only within the chat group. There is.
  • Such a chat group may be a chat group for 1-1 chat between two users, or may be a chat group for group chat between three or more users.
  • the chat server 110 may more quickly extract the corresponding package data to be delivered among the package data stored in the message storage space.
  • the client device 100 can more conveniently and quickly manage the package data for each chat. Accordingly, a faster chat service can be provided to the user.
  • Client device 100 according to an embodiment of the present invention shown in Figure 4, a smartphone that provides a client-based chat service by running an application (chat client program) installed through an application store server (Application Store Sever), It may be a mobile terminal such as a tablet PC or a mobile communication terminal.
  • application chat client program
  • Application Store Sever Application Store Sever
  • FIG. 5 is a flowchart illustrating a method in which the client device 100 provides a client-based chat service according to an embodiment of the present invention.
  • the method for providing a client-based chat service by the client device 100 may include: outputting a first message input by a user to a chat screen (S300); When the first message is input, generating a first package data by packaging a first message header including the first sender information, the first receiver list, and the first message type information and the inputted first message (S302); In operation S304, the generated first package data is transmitted to the chat server 110, and a second message header and a second message including second sender information, second recipient list, and second message type information are packaged. Receiving the second package data from the chat server 110 (S306), and outputting the second message on the chat screen (S308) and the like.
  • the above procedure is an example in which the client device 100 first transmits a message (first message) and then receives a message (second message) input from another client device later.
  • the first sender information included in the first message header packaged in the first package data is identification information corresponding to the client device 100, and the first receiver list includes identification information corresponding to one or more other client devices, respectively. .
  • the second sender information included in the second message header packaged in the second package data is identification information corresponding to a specific other client device among one or more other client devices, and the second recipient list is identification corresponding to the client device 100. Information and the like.
  • step S302 when generating the first package data to be sent by packaging the first message, one or more other client devices (users of the client device 100) chat on the basis of a user input or a previously managed chat participant list.
  • a first recipient list including identification information corresponding to a client device of a user or a client device of a user having a user chat of the client device 100.
  • the method of setting the first recipient list according to the user input may be a method of setting the first recipient list when a user of the client device 100 invites a user to chat.
  • the method of setting the first recipient list based on the previously managed chat participant list may be a method of setting the first recipient list while the chat is already being performed.
  • Identification information corresponding to the new client device may be added to the chat participant list managed before the second package data is received based on the second recipient list included in the second message header packaged in the second package data. .
  • the message is received.
  • the identification information corresponding to the specific other client device, which is the second sender information included in the second message header packaged in the second package data, may be deleted from the chat participant list managed before the second package data is received.
  • Each of the first message type information and the second message type information mentioned above may be one of invitation message type information, general message type information, and exit message type information.
  • the client-based chat service may be a 1-1 chat service or a group chat service.
  • the 1-1 chat service and the group chat service differ only in one or more identification information corresponding to the client from the recipient list included in the message header packaged in the package data to be delivered.
  • the operation of 110 and the client device 100 is the same.
  • the group information may be further included in the first message header.
  • Group information may be further included in the second message header.
  • the chat server 110 may more quickly extract the corresponding package data to be delivered among the package data stored in the message storage space.
  • the client device 100 can more conveniently and quickly manage the package data for each chat. Accordingly, a faster chat service can be provided to the user.
  • step S306 in order to check whether there is the second package data to be obtained from the chat server 110, the message request data including the identification information corresponding to the client device 100 is transmitted to the chat server 110.
  • 2 package data may be received from the chat server (110).
  • the second receiver list in the second package data includes identification information corresponding to the client device 100.
  • the message request data may be received in the standby state without transmitting the message request data to the chat server 110.
  • step S300 The above-described procedure is merely an example in which the client device 100 first transmits a message (first message), and then receives a message (second message) input from another client device later, in step S300. And step S302 may be executed after steps S304 and S306.
  • the client device 100 described above is a mobile terminal such as a smartphone, a tablet PC, a mobile communication terminal, etc., which provides a client-based chat service by executing an application (chat client program) installed through an application store server. Can be.
  • the physical device on which the method for providing a client-based chat service according to the above-described embodiment of the present invention is executed is a client device 100, the method for providing a client-based chat service according to the embodiment of the present invention is executed.
  • the actual subject may be an application installed in the client device 100, that is, a chat program.
  • the method for providing a client-based chat service may be implemented in a program (ie, an application) and recorded in a computer-readable recording medium.
  • the program implementing the method for providing a client-based chat service includes a function of outputting an input first message on a chat screen, and, when a first message is input, first sender information and a first message.
  • Execute a function such as output to the chat screen.
  • Such a program is recorded on a recording medium readable by a computer and executed by a computer so that the above functions can be executed.
  • the above-described program may be executed by a computer processor (CPU).
  • Code may be coded in a computer language such as C, C ++, JAVA, or machine language that can be read through a computer device interface.
  • Such code may include a function code associated with a function or the like that defines the above-described functions, and may include execution procedure-related control code necessary for a processor of the computer to execute the above-described functions according to a predetermined procedure.
  • Such code must be referenced from any location (address address) of the computer's internal or external memory for additional information or media necessary for the processor of the computer to execute the method of providing a client-based chat service according to an embodiment of the present invention.
  • Memory reference related code may be further included.
  • the code is The communication module of the computer may further include communication-related code on how to communicate with any other computer or chat server in a remote, and what information or media should be transmitted and received during communication.
  • codes and code segments associated therewith may be used in consideration of a system environment of a computer that reads a recording medium and executes the program. It may be easily inferred or changed by.
  • Examples of recording media that can be read by a computer recording a program as described above include, for example, a ROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, an optical media storage device, and the like.
  • a computer-readable recording medium having recorded a program as described above may be distributed to computer systems connected through a network so that computer-readable codes may be stored and executed in a distributed manner.
  • any one or more of the plurality of distributed computers may execute some of the functions presented above, and transmit the results to one or more of the other distributed computers, and receive the results.
  • the computer may also execute some of the functions presented above, and provide the results to other distributed computers as well.
  • a computer-readable recording medium recording an application which is a program for executing a method of providing a client-based chat service according to an embodiment of the present invention, may be a storage medium (eg, a hard disk, etc.) included in an application store chat server. ) Or the application store chat server itself.
  • a computer capable of reading a recording medium recording an application which is a program for executing a method of providing a client-based chat service according to an embodiment of the present invention is not only a general PC such as a general desktop or a laptop, but also a smartphone and a tablet.
  • the client device 100 may include a mobile terminal such as a personal computer (PDA), a personal digital assistant (PDA), and a mobile communication terminal.
  • PDA personal computer
  • PDA personal digital assistant
  • the present invention should be interpreted as any device capable of computing.
  • a computer capable of reading a recording medium recording an application which is a program for executing a method of providing a client-based chat service according to an embodiment of the present invention may be a smartphone, a tablet PC, a personal digital assistant (PDA), a mobile communication terminal, or the like.
  • the application may be downloaded from the application store server to a general PC and installed on the client device 100 through a synchronization program.
  • an application (chat program) installed in the client device 100 executes the client-based chat service according to the above-described embodiment of the present invention.
  • client C an application (chat program) installed in the client device 100
  • Client-based chat service can be implemented by the protocol specified in the present invention.
  • These protocols define rules for data delivery methods (message delivery methods), data formats, and the like.
  • FIG. 6 is a diagram illustrating a message transmission procedure and a message reception procedure according to a protocol for providing a client-based chat service according to an embodiment of the present invention.
  • the protocol for providing a client-based chat service defines a rule for a data delivery method, wherein the rule for the data delivery method is that the client C sends a message to the chat server S.
  • the rule for the message transmission procedure can be divided into a rule for the message reception procedure that the client (C) receives a message from the chat server (S).
  • Such a message transmission procedure and a message reception procedure may be performed in a request-response manner.
  • FIG. 6 (a) illustrating a message transmission procedure
  • the client C packages the input message with a message header to generate package data, and then generates the package data.
  • the data is transmitted to the chat server S as delivery request data REQUEST (S11).
  • the chat server S receives the package data in which the message is packaged from the client C, the chat server S stores the message data in the message storage space (S12), and transmits the message delivery response data to the corresponding client C (S13).
  • the client C receives a package to which the client C retrieves while the chat server S stores the package data in the message storage space.
  • message request data including receiver information, which is identification information corresponding to the client C, is transmitted to the chat server S (S21).
  • the chat server (S) receives the message request data and checks the receiver information included in the message request data to check whether the package data including the confirmed destination information in the recipient list is stored in the message storage space.
  • the extracted package data is extracted from the message storage space (S22), and the extracted package data is transmitted to the client C as message response data (S23).
  • FIG. 7 illustrates a rule of a data format according to a protocol for providing a client-based chat service according to an exemplary embodiment of the present invention.
  • package data as message delivery request data transmitted from the client C to the chat server S includes a message header including sender information, a recipient list, message type information, and the like. Contains the message actually entered by The message header may optionally include group information.
  • the message delivery response data that the client C receives from the chat server S with respect to the message delivery request data includes a result code, result information, etc. for the message delivery request data reception processing result. It may include.
  • the message request data transmitted from the client C to the chat server S includes recipient information as identification information corresponding to the client C, and the like.
  • the message response data that the client C receives from the chat server S with respect to the message request data is received by the chat server S by receiving package data as the message delivery request data. It is stored without processing, and has the same data format as package data as message transfer request data.
  • FIG. 8 is a diagram exemplarily defining message type information according to a protocol for providing a client-based chat service according to an embodiment of the present invention.
  • the message type information included in the message header is information defining the type of the message.
  • the message type information includes invitation message type information M01, general message type information M02 related to the actual chatting content, and exit message type information. (M03) and the like.
  • message type information about various functions required for chatting, such as accepting an invitation or rejecting an invitation may be further defined.
  • FIG. 9 is a diagram illustrating an environment for implementing a client-based chat service.
  • three users user 1, user 2, and user 3 who own a smartphone as the client device 100 chat.
  • user 1 is a user who wants to chat for the first time.
  • three smartphones may communicate with the chat server S through a network 120 such as a Wi-Fi network, a mobile communication network, or an Internet network.
  • a network 120 such as a Wi-Fi network, a mobile communication network, or an Internet network.
  • each smartphone owned by three users is provided with an application (program) capable of executing a method of providing a client-based chat service according to an embodiment of the present invention.
  • the applications installed in each of the three smartphones are also referred to as C1, C2, and C3 as a client interworking with the chat server (S).
  • the application C1 displays a chat screen as shown in FIG. 9.
  • corresponding applications installed in the smart phones of the user 2 and the user 3 may be running in the background.
  • the application C1 provides a user invitation UI (User Interface).
  • the user 1 presses the find partner button to chat with the user 2 and the user 3, the phone numbers of the user 2 and the user 3 from the contacts stored in the smart phone ( It is an example of the identification information corresponding to the client device), and then press the invite button can invite the user 2 and the user 3.
  • U1, U2, and U3 described in the data field correspond to identification information corresponding to the user's smartphone (client device), the user's smartphone 2 (client device), and the user 3's smartphone (client device), respectively.
  • This may be a phone number or user information (eg, ID, nickname, etc.) corresponding to the phone number.
  • C1 when the user sets a user to invite and presses the invite button, C1 performs an invitation function.
  • This invitation function is executed according to the message transmission procedure (FIG. 10) and the message reception procedure (FIG. 11) defined in the protocol.
  • C1 sets a recipient list including U2 and U3, sets U1 as sender information, sets group information to GO1, sets message type information to M01 (invitation message type information), and Package data 1000 by packaging a message header including the sender information, the recipient list, the group information, and the message type information, and a message M of basic contents such as "invite" or input by the user. Generate and transmit the generated package data 1000 to the chat server S as message delivery request data.
  • the chat server S stores package data 1000 as message delivery request data received from C1 in a message storage space. Thereafter, the chat server S transmits message delivery response data 1010 including a result code (RC) and result information (RI) to C1.
  • message delivery response data 1010 including a result code (RC) and result information (RI) to C1.
  • each of U2 and U3 set in the recipient list in the package data 1000, which is the message delivery request data, is stored.
  • a message receiving procedure for receiving the package data 1000 corresponding to C2 and C3 as message delivery request data will be described with reference to FIG. 11.
  • C2 sets U2, which is identification information corresponding to C2, as receiver information and transmits message request data 1110 including such receiver information to the chat server S.
  • the chat server S checks whether the receiver list included in the message header packaged in the package data 1000 stored in the message storage space includes U2, which is receiver information included in the message request data 1110, If included, the package data 1000 stored in the message storage space is transmitted to the C2 as the message response data. In this manner, C2 may receive the package data 1000 stored in the chat server S as message response data.
  • C3 sets U3, which is identification information corresponding to C3, as recipient information, and transmits the message request data 1120 including the recipient information to the chat server S to store the message stored in the chat server S.
  • Data 1000 may be received as message response data.
  • C2 and C3 After receiving the package data 1000 according to the procedure of FIG. 11, C2 and C3 display the contents (invitation contents) of the message packaged in the package data 1000 by displaying a popup form or a chat screen, and the user displays the invitation fact. can confirm.
  • C2 and C3 may provide a user interface for invitation acceptance or invitation rejection.
  • C2 sets the sender information to U2 and sets a recipient list including U1 and U3.
  • group information is set to G01 and the message type information is set to MO2 (general message type information) to create a message header and package the input message to generate the packaging data 1200.
  • C2 then transmits the generated packaging data 1200 to the chat server S as message delivery request data. Accordingly, the chat server S stores the packaging data 1200 in the message storage space, and transmits the message delivery response data 1210 including the result code RC and the result information RI to C2.
  • Message request data 1310 and 1320 are sent to the chat server S to check if there is package data to import and to import it.
  • C1 transmits the message request data 1310 in which U1, which is identification information corresponding to C1, is set to the receiver information, to the chat server S, and C3 is a message request, in which U3, which is identification information corresponding to C3, is set to the receiver information.
  • the data 1320 is transmitted to the chat server S.
  • the chat server S checks the receiver information included in the message request data 1310 received from C1 as U1, extracts the package data 1200 included in the recipient list from U1, and transmits it to C1.
  • chat server S confirms the receiver information included in the message request data 1320 received from the C3 as U3, and extracts the package data 1200 included in the recipient list from the U3 and transmits it to the C3.
  • C1 and C3 confirm that the message type information included in the message header packaged in the received package data 1200 is general message type information M02, and output a message packaged in the package data 1200 to the chat screen. .
  • a message may be transmitted by transmitting a message between C1, C2, and C3 through a message transmission procedure and a message reception procedure.
  • any user of the participant may stop the chat.
  • the application may provide a user interface such as an exit button for providing an exit function.
  • a message delivery procedure (message transmission and message reception procedure) related to the exit function will be described with reference to FIGS. 14 and 15.
  • C3 sets the sender information to U3 and includes U1 and U2 in the recipient list, and exits the message type information.
  • the message header is configured by setting M03, which is the type information
  • the packaging data 1400 is generated by packaging a message having the configured message header and the contents such as "User 3 leaves the chat room.”
  • C3 transmits the generated packaging data 1400 to the chat server S as message delivery request data. Accordingly, the chat server S stores the package data 1400 in the message storage space.
  • Message request data 1510 and 1520 are sent to the chat server S to check if there is package data to import and to import it.
  • C1 transmits the message request data 1510 in which U1, which is identification information corresponding to C1, is set to the receiver information, to the chat server S, and C2 is a message request, in which U2, which is identification information corresponding to C2, is set to the receiver information.
  • the data 1520 is transmitted to the chat server (S).
  • the chat server S checks the receiver information included in the message request data 1510 received from C1 as U1, extracts the package data 1400 included in the receiver list, and transmits the package data 1400 to C1.
  • chat server S confirms the receiver information included in the message request data 1520 received from the C2 as U2, extracts the package data 1400 included in the recipient list, and transmits the package data 1400 to the C2.
  • C1 and C2 confirm that the message type information included in the message header packaged in the received package data 1400 is the exit message type information M03, and output the message packaged in the package data 1400 to the chat screen. . Accordingly, the user 1 and the user 2 can confirm that the user 3 has left the chat room.
  • a client-based chat service suitable for a mobile environment can be provided.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

La présente invention concerne une technologie de service de chat et, plus particulièrement, un procédé pour fournir un service de chat basé sur le client approprié pour un environnement mobile, un dispositif de client, un serveur de chat, et un support d'enregistrement.
PCT/KR2012/003655 2011-05-20 2012-05-10 Procédé de fourniture d'un service de chat basé sur le client, un dispositif de client, un serveur de chat, système, et support d'enregistrement Ceased WO2012161437A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2011-0047903 2011-05-20
KR1020110047903A KR101292002B1 (ko) 2011-05-20 2011-05-20 클라이언트 기반의 채팅 서비스를 제공하는 방법, 클라이언트 장치, 채팅 서버, 시스템 및 기록매체

Publications (2)

Publication Number Publication Date
WO2012161437A2 true WO2012161437A2 (fr) 2012-11-29
WO2012161437A3 WO2012161437A3 (fr) 2013-01-17

Family

ID=47217844

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2012/003655 Ceased WO2012161437A2 (fr) 2011-05-20 2012-05-10 Procédé de fourniture d'un service de chat basé sur le client, un dispositif de client, un serveur de chat, système, et support d'enregistrement

Country Status (2)

Country Link
KR (1) KR101292002B1 (fr)
WO (1) WO2012161437A2 (fr)

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7650380B2 (en) 2004-02-12 2010-01-19 International Business Machines Corporation System and method for messaging and collaborating in an intranet environment
FI20050092A0 (fi) * 2004-09-08 2005-01-28 Nokia Corp Ryhmäpalveluiden ryhmätiedot
US20090063638A1 (en) * 2007-08-29 2009-03-05 Lei Guo Method and Apparatus for Processing Messages in Messaging System
KR101397633B1 (ko) * 2007-12-05 2014-05-22 주식회사 케이티 아이엠에스 기반 인스턴트 메시지 서비스 제공 시스템 및방법

Also Published As

Publication number Publication date
WO2012161437A3 (fr) 2013-01-17
KR20120129564A (ko) 2012-11-28
KR101292002B1 (ko) 2013-08-01

Similar Documents

Publication Publication Date Title
EP2499848A2 (fr) Procédé et appareil pour obtenir des services d'interfaces utilisateurs distantes
WO2016137092A2 (fr) Procédé pour organiser une icône de groupe dans un service de messagerie, et appareil associé
WO2016047983A1 (fr) Procédé et dispositif pour une communication sans fil entre des terminaux de communication
WO2012026777A2 (fr) Procédé et appareil pour établir une communication
WO2014112754A1 (fr) Procédé de pousser de service web, serveur de pousser de service web et serveur de fourniture de service web l'exécutant
WO2016076472A1 (fr) Procédé et système de commande d'appel
WO2010047470A2 (fr) Système de fourniture de contenu et procédé de fourniture d'un service de données par le biais d'un réseau local, et serveur cpns et terminal de communication mobile correspondant
WO2012099402A2 (fr) Procédé et appareil de communication téléphonique utilisant un réseau domestique
WO2014088146A1 (fr) Système de communication de machine à machine qui utilise un service de réseau social (sns), procédé de communication de machine à machine et serveur de communication de machine à machine pour ces derniers
WO2013023529A1 (fr) Procédé de traitement de données de contact de terminal mobile, et terminal mobile correspondant
WO2014112838A1 (fr) Système de gestion de la transmission d'une carte de visite électronique basée sur un lien avec le numéro de téléphone et procédé y relatif
WO2012148094A2 (fr) Procédé de fourniture de service d'échange de messages à destinataire non identifié
WO2017034097A1 (fr) Procédé et système de service de réseau social
EP2932651A1 (fr) Procédé et appareil de gestion de puissance à base du nuage de dispositifs réseau locaux
WO2012081950A2 (fr) Procédé et appareil permettant de partager automatiquement une application entre une pluralité de clients
WO2024128400A1 (fr) Dispositif électronique et procédé de fourniture de message associé
WO2013022259A2 (fr) Procédé et appareil permettant d'utiliser les informations et l'emplacement d'un appelé avant l'établissement d'un appel
WO2014104579A1 (fr) Procédé de contrôle de nom de fichier et dispositif électronique associé
WO2022186466A1 (fr) Appareil, procédé et programme pour envoyer un message de campagne électorale de sorte que le numéro de connaissance du destinataire soit affiché
WO2012161437A2 (fr) Procédé de fourniture d'un service de chat basé sur le client, un dispositif de client, un serveur de chat, système, et support d'enregistrement
WO2014012522A1 (fr) Procédé et dispositif d'association pour des modes de communication
WO2016060321A1 (fr) Procédé et appareil d'établissement d'appel sécurisé
WO2018216857A1 (fr) Procédé de recherche de conversation, terminal portable à conversations pouvant être recherchées et serveur de gestion de conversations
WO2014204259A1 (fr) Procédé et serveur d'émission d'un message de notification, et procédé de gestion d'un message de conversation en groupe
WO2015174644A1 (fr) Système d'envoi de publicité à un terminal d'utilisateur via un routeur sans fil, et serveur de fourniture de service de publicité

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: 12789181

Country of ref document: EP

Kind code of ref document: A2

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 DATED 10.03.14 (FORM 1205A)

122 Ep: pct application non-entry in european phase

Ref document number: 12789181

Country of ref document: EP

Kind code of ref document: A2