KR20120129564A - Method, client device, chatting server and recording medium for providing client-based chatting service - Google Patents

Abstract

PURPOSE: A client apparatus, chatting server, system, and recording medium are provided to promote user convenience by promoting chatting service quality according to a mobile environment. CONSTITUTION: A message reception unit(210) receives package data from a first client apparatus. The package data is created by packaging a message inputted from a message header and the first client apparatus. The message header includes transmitter information, a receiver list, and message type information. A message storage unit(220) stores the package data. A message transmission unit(230) transmits the stored package data to one or more second client apparatuses by referring to the receiver list. [Reference numerals] (100a) First client unit; (100b) Second client unit; (210) Message reception unit; (220) Message storage unit; (230) Message transmission unit

Description

How to provide client-based chat services, client devices, chat servers, systems and recording media {METHOD, CLIENT DEVICE, CHATTING SERVER AND RECORDING MEDIUM FOR PROVIDING CLIENT-BASED CHATTING SERVICE}

The present invention relates to chat service technology, and more particularly, to a chat service technology suitable for a mobile environment.

In a conventional chat service, 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. In this sense, the conventional chat service is a server-based chat service.

In addition, the conventional chat service is performed in a better network situation and in a general web environment than in a mobile environment.

In addition, since 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.

Therefore, in the mobile environment, which is relatively poor in all aspects compared to the web environment and the network environment where the server-based chat service is performed, if the conventional chat service is applied as it is, the chat service quality and user convenience are greatly degraded. There is a problem.

In this context, an object of the present invention is to provide a client-based chat service suitable for a mobile environment.

In order to achieve the above object, in one aspect, the present invention, 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; And a message transmitting unit which transmits the stored package data to the at least one second client device by referring to the recipient list.

In another aspect, 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. Receiving, from the first client device, a message header including a recipient list and message type information, and package data in which a message input from the first client device is packaged; Storing the package data; And transmitting the stored package data to the one or more client devices with reference to the recipient list.

According to another aspect of the present invention, when the first message is input, 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; And a chat screen controller configured to output the inputted first message and the second message to a chat screen.

In another aspect, 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.

In another aspect, 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. Provides a system for providing chat services.

In another aspect, 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. Receiving from the chat server a function of transmitting data to the chat server, 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.

As described above, according to the present invention, there is an effect of providing a client-based chat service suitable for a mobile environment.

1 is a diagram schematically illustrating a system for providing a client-based chat service according to an embodiment of the present invention.
2 is a block diagram of a chat server providing a client-based chat service according to an embodiment of the present invention.
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.
4 is a block diagram of a client device for providing a client-based chat service according to an embodiment of the present invention.
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.
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.
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.
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.

Hereinafter, some embodiments of the present invention will be described in detail with reference to exemplary drawings. In adding reference numerals to the components of each drawing, it should be noted that the same reference numerals are assigned to the same components as much as possible even though they are shown in different drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear.

In addition, in describing the component of this invention, terms, such as 1st, 2nd, A, B, (a), (b), can be used. These terms are intended to distinguish the constituent elements from other constituent elements, and the terms do not limit the nature, order or order of the constituent elements. When a component is described as being "connected", "coupled", or "connected" to another component, the component may be directly connected to or connected to the other component, It should be understood that an element may be "connected," "coupled," or "connected."

1 is a diagram schematically illustrating a system for providing a client-based chat service according to an embodiment of the present invention.

Referring to FIG. 1, a system for providing a client-based chat service according to an embodiment of the present invention 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.

Here, the term "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.

In a conventional chat service, 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. In this sense, the conventional chat service is a server-based chat service.

In addition, the conventional chat service is performed in a better network situation than in a mobile environment and in a general web environment.

In addition, since 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.

Therefore, in the mobile environment, which is relatively poor in all aspects compared to the web environment and the network environment where the server-based chat service is performed, if the conventional chat service is applied as it is, the chat service quality and user convenience are greatly degraded. There is a problem.

Accordingly, in the client-based chat service according to the embodiment of the present invention, 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. Among 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 according to an embodiment of the present invention communicate with each other through a network 120 to provide a chat service.

Here, 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.

In addition, 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.

As described above, in order to provide a client-based chat service according to an exemplary embodiment of the present invention, 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.

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.

However, hereinafter, 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. Works. That is, 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.

Referring to FIG. 2, the chat server 110 that provides a client-based chat service according to an embodiment of the present invention 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.

In the present invention, in order for a message (a message input by a user) received from the first client device 100a to be correctly delivered to the corresponding second client device 100b, a message input by the user is packaged by attaching a message header. And delivered in the form of package data. Here, 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.

However, below, 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".

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. In addition, the message M that the client device A sends to the chat server 110 is the first message, and 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.

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. In this case, 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.

In case of transmitting in a pull mode, when the message request data is received from the second client device 100b, 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.

If the message is transmitted using the push method, 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. In this case, 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.

Based on the foregoing description, again describing a system for providing a client-based chat service according to an embodiment of the present invention , 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.

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.

Referring to FIG. 3, the method for providing a client-based chat service by the chat server 110 according to an exemplary embodiment of the present invention 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. Receiving the first package data from the first client device 100a (S300), storing the received first package data (S302), and referring to the first recipient list in the stored first package data. And transmitting the stored first package data to the one or more second client devices 100b (S304).

Hereinafter, 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.

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.

Referring to FIG. 4, when a first message is input by a user, the client device 100 providing a client-based chat service according to an embodiment of the present invention may include first sender information, a first receiver list, and a first receiver. First package data for generating first package data by packaging a first message header including message type information and a first message input by a user, and transmitting the generated first package data to the chat server 110. A second message header including a transmitter 410, 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 the second message is packaged, from the chat server 110; 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.

Here, 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. In addition, 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.

Meanwhile, the client device 100 that provides a client-based chat service according to an embodiment of the present invention may perform a function of managing a list of all users (participants) who are chatting. To this end, as shown in FIG. 4, 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.

In other words, in order for another user who is chatting with the user of the client device 100 to invite someone, 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, and 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.

In other words, when another user (user who has stopped chatting) chatting with the user of the client device 100 has pressed the exit button or the like to stop chatting, in the client device of the user who has stopped chatting, Set the sender information (second sender information from the point of view of the client device 100) as identification information corresponding to the sender information and the message type information (second message type information from the point of view of the client device 100) as the exit message type information. When setting and sending the package data (second package data from the client device 100's point of view) to the chat server 110, all the client devices that have received the package data are identified corresponding to the client device of the user who has stopped chatting. Delete information from the participant list that was 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.

In order to receive the second package data from the chat server 110, 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. In this case, 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 according to an embodiment of the present invention 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. However, in order to efficiently provide a group chat service, group information for identifying a chat group may be further included in a message header packaged in package data. Here, 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.

For example, if the group information is included in the 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. In addition, if the group information is included in the message header, while several chats are being performed in the client device 100, 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.

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.

Referring to FIG. 5, the method for providing a client-based chat service by the client device 100 according to an exemplary embodiment of the present disclosure 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.

In the above-described 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.

Here, 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. In addition, 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.

If the second message type information included in the second message header packaged in the received second package data after the above-described step S306, that is, after receiving the second package data, is received. 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. .

If the second message type information included in the second message header packaged in the received second package data after the above-described step S306, that is, after receiving the second package data, is received, 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 according to an embodiment of the present invention 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. However, in order to efficiently provide a group chat service, when generating the first package data in step 302, the group information may be further included in the first message header. Group information may be further included in the second message header.

For example, if the group information is included in the 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. In addition, if the group information is included in the message header, while several chats are being performed in the client device 100, 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.

In step S306 described above, 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). In this case, the second receiver list in the second package data includes identification information corresponding to the client device 100.

In addition, in step S306 described above, the message request data may be received in the standby state without transmitting the message request data to the chat server 110.

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.

Even if 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.

Accordingly, the method for providing a client-based chat service according to the embodiment of the present invention described above 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 according to an embodiment of the present invention 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. A function of packaging a first message header including a recipient list and first message type information and an inputted first message to generate first package data, and transmitting the generated first package data to the chat server 110. And a second message header including a second sender information, a second receiver list, and a second message type information, and a second package data in which the second message is packaged, from the chat server 110, and a second message. Execute a function such as output to the chat screen.

Such a program (application) is recorded on a recording medium readable by a computer and executed by a computer so that the above functions can be executed.

As described above, in order to execute a method of providing a client-based chat service according to an embodiment of the present invention in which a computer reads a program recorded on a recording medium and is implemented as a program, the above-described program may be executed by a processor (CPU) of the computer. 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.

The code may include a function code related to a function or the like that defines the functions described above and may include an execution procedure related control code necessary for the processor of the computer to execute the functions described above according to a predetermined procedure.

In addition, 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.

In addition, when the processor of the computer needs to communicate with any other computer or chat server in the remote to execute the method of providing a client-based chat service according to an embodiment of the present invention, 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.

The functional program for implementing the present invention and the related code and code segment may be implemented by programmers of the technical field of the present invention in consideration of the system environment of the computer that reads the recording medium and executes the program, Or may be easily modified or modified by the user.

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.

Also, the computer-readable recording medium on which the above-described program is recorded may be distributed to a computer system connected via a network so that computer-readable codes can be stored and executed in a distributed manner. In this case, one or more of the plurality of distributed computers may execute some of the functions presented above and send the results of the execution to one or more of the other distributed computers, The computer may also perform some of the functions described above and provide the results to other distributed computers as well.

In particular, 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. In addition, 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. In the case of the client device 100 including the mobile terminal, 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.

Hereinafter, a client-based chat service according to an embodiment of the present invention described above will be described as an example.

However, hereinafter, it will be described that 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. In the following description, an application (chat program) installed in the client device 100 is referred to as "client C" for convenience of explanation.

Client-based chat service according to an embodiment of the present invention 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. Before explaining an example of the chat service, the above-described protocol will be described first with reference to FIGS. 6 to 8.

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 according to an embodiment of the present invention 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.

Referring to FIG. 6 (a) illustrating a message transmission procedure, when a message is input by a user, 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). When 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).

Referring to (b) of FIG. 6, which shows a message receiving procedure, according to the above-described message transmission procedure, 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. In order to request and request whether there is data (message), 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.

Referring to FIG. 7A, 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.

Referring to FIG. 7B, 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.

Referring to FIG. 7C, 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.

Referring to FIG. 7D, 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.

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.

Referring to FIG. 8, 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. In addition, message type information about various functions required for chatting, such as accepting an invitation or rejecting an invitation, may be further defined.

Hereinafter, an example of providing a client-based chat service according to an embodiment of the present invention using the aforementioned protocol will be described with reference to FIGS. 9 to 15.

9 is a diagram illustrating an environment for implementing a client-based chat service. Hereinafter, as illustrated in FIG. 9, it is assumed that three users (user 1, user 2, and user 3) who own a smartphone as the client device 100 chat. And user 1 is a user who wants to chat for the first time.

As illustrated in FIG. 9, 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.

As shown in FIG. 9, 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. In addition, 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).

Referring to FIG. 9, when user 1 executes the application to use the chat service, the application C1 displays a chat screen as shown in FIG. 9. In addition, corresponding applications installed in the smart phones of the user 2 and the user 3 may be running in the background.

In addition, the application C1 provides a user invitation UI (User Interface). When 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.

This chat counterpart invitation procedure will be described with reference to FIGS. 10 and 11. However, in the following drawings, 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.

As described above, 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.

Referring to FIG. 10, 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.

Referring to FIG. 10, 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.

As described above, after the package data 1000, which is the message delivery request data, is stored in the message storage space of the chat server S, 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.

Referring 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. FIG. Accordingly, 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.

In the same manner, 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.

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. In this case, C2 and C3 may provide a user interface for invitation acceptance or invitation rejection.

According to this procedure, User 1, User 2 and User 3 are in a chatable state. Subsequently, as the actual chat proceeds, a function of the actual chat contents message (message of general message type) is transferred between C1, C2, and C3 will be described with reference to FIGS. 12 and 13. This message delivery function is also executed according to the message transmission procedure (FIG. 12) and the message reception procedure (FIG. 13) defined in the protocol.

Referring to FIG. 12, when User 1, User 2, and User 3 are chatting, and User 2 inputs a message (general message), C2 sets the sender information to U2 and sets a recipient list including U1 and U3. In addition, the 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.

Referring to FIG. 12, 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.

Referring to FIG. 13, while the package data 1200 is stored in the message storage space of the chat server S, the clients C1 and C3 other than the client C2 who generated the package data 1200 among the chat participants are themselves. 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.

At this time, 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. FIG.

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.

In addition, the 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. .

In this manner, a message may be transmitted by transmitting a message between C1, C2, and C3 through a message transmission procedure and a message reception procedure. During the chat, any user of the participant may stop the chat.

In order to provide such an exit function, the application may provide a user interface such as an exit button for providing an exit function. Hereinafter, 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.

Referring to FIG. 14, when user 3 stops chatting by pressing the exit button to stop chatting, 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, and 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."

Thereafter, 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.

Referring to FIG. 15, while the package data 1400 is stored in the message storage space of the chat server S, the clients C1 and C2 other than C3, which is the client who generated the package data 1400 among the chat participants, are themselves. 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.

At this time, 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.

In addition, the 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.

Before User 3 left, three users had a group chat, and after User 3 left, two users could have a 1-1 chat. There is no difference in the actions that the client C and the chat server S should perform during group chat and 1-1 chat. The only difference is that in 1-1 chat, group information is not set and only one identification information is set in the recipient list.

As described above, according to the present invention, a client-based chat service suitable for a mobile environment can be provided.

While the present invention has been described in connection with what is presently considered to be the most practical and preferred embodiments, it is to be understood that the invention is not limited to the disclosed embodiments. In other words, within the scope of the present invention, all of the components may be selectively operated in combination with one or more. In addition, although all of the components may be implemented as one independent hardware, some or all of the components may be selectively combined to perform a part or all of the functions in one or a plurality of hardware. As shown in FIG. Codes and code segments constituting the computer program may be easily inferred by those skilled in the art. Such a computer program may be stored in a computer readable storage medium and read and executed by a computer, thereby implementing embodiments of the present invention. As a storage medium of the computer program, a magnetic recording medium, an optical recording medium, or the like can be included.

It is also to be understood that the terms such as " comprises, "" comprising," or "having ", as used herein, mean that a component can be implanted unless specifically stated to the contrary. But should be construed as including other elements. All terms, including technical and scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs, unless otherwise defined. Commonly used terms, such as predefined terms, should be interpreted to be consistent with the contextual meanings of the related art, and are not to be construed as ideal or overly formal, unless expressly defined to the contrary.

The foregoing description is merely illustrative of the technical idea of the present invention, and various changes and modifications may be made by those skilled in the art without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are intended to illustrate rather than limit the scope of the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The protection scope of the present invention should be interpreted by the following claims, and all technical ideas within the equivalent scope should be interpreted as being included in the scope of the present invention.

Claims (22)

A message header including sender information, identification information corresponding to the first client device, a recipient list including identification information corresponding to one or more second client devices, and message type information, and a message input from the first client device A message receiver configured to receive packaged package data from the first client device;
A message storage unit for storing the package data; And
And a message transmitter for transmitting the stored package data to the one or more second client devices by referring to the recipient list. The method of claim 1,
The message transmitter,
When the message request data is received from the second client device, it is checked whether identification information corresponding to the second client device is included in the recipient list, and if it is confirmed that the message is included, the stored information is stored in the second client device. Chat server providing a client-based chat service, characterized in that for transmitting the package data. The method of claim 1,
The message transmitter,
And if the package data is stored, confirming the recipient list, and transmitting the stored package data to the corresponding second client device. In the chat server provides a client-based chat service,
A message header including sender information, identification information corresponding to the first client device, a recipient list including identification information corresponding to one or more second client devices, and message type information, and a message input from the first client device Receiving packaged package data from the first client device;
Storing the package data; And
And transmitting the stored package data to the one or more client devices with reference to the recipient list. When the first message is input, the first message header including the first sender information, the first receiver list, and the first message type information and the inputted first message are packaged to generate first package data. A first package data transmitter for transmitting the first package data to the 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; And
And a chat screen controller configured to output the input first message and the second message to a chat screen. The method of claim 5,
The first package data transmission unit,
Setting the first recipient list including identification information corresponding to one or more other client devices based on a user input or a chat participant list,
And a chat participant list manager configured to manage the chat participant list including identification information corresponding to the one or more other client devices and the client device, respectively. The method according to claim 6,
The chat participant list management unit,
After receiving the second package data in which the second message type information is invitation message type information, identification information corresponding to a new client device based on the second recipient list corresponds to a new client device in the chat participant list. Client device for providing a client-based chat service, characterized in that for adding identification information. The method according to claim 6,
The chat participant list management unit,
After receiving the second package data in which the second message type information is the exit message type information, the identification information corresponding to a specific other client device as the second sender information is deleted from the chat participant list. Client devices that provide client-based chat services. The method of claim 5,
The second package data receiver,
In order to confirm whether there is the second package data to be brought into the message storage space of the chat server, message request data including identification information corresponding to the client device is transmitted to the chat server to receive the second package data. Wherein, the second receiver list in the second package data client device for providing a client-based chat service, characterized in that the identification information corresponding to the client device. The method of claim 5,
The client device,
Client device for providing a client-based chat service, characterized in that the mobile terminal for providing a client-based chat service by running the application installed through the application store server. In the method that the client device provides a client-based chat service,
Outputting an input first message to a 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
And outputting the second message to the chat screen. The method of claim 11,
The first sender information is identification information corresponding to the client device, and the first receiver list includes identification information corresponding to one or more other client devices, respectively.
The second sender information is identification information corresponding to a specific other client device among the one or more other client devices, and the second receiver list includes identification information corresponding to the client device.
And the identification information is a telephone number or user information corresponding to the telephone number. The method of claim 11,
In the generating step,
And setting the first recipient list including identification information corresponding to one or more other client devices based on a user input or a chat participant list. The method of claim 13,
After receiving the second package data, if the second message type information is invitation message type information, a new message is added to the chat participant list that was managed before the second package data was received based on the second recipient list. Method for providing a client-based chat service, characterized in that for adding the identification information corresponding to the client device. The method of claim 13,
After receiving the second package data, if the second message type information is the exit message type information, before the second package data is received, identification information corresponding to a specific other client device that is the second sender information is received. A method for providing a client-based chat service, the method comprising: deleting from a chat participant list managed at. The method of claim 11,
Each of the first message type information and the second message type information,
Method of providing a client-based chat service, characterized in that one of the invitation message type information, general message type information and the exit message type information. The method of claim 11,
Wherein the receiving comprises:
In order to confirm whether there is the second package data to be fetched from the chat server, message request data including identification information corresponding to the client device is transmitted to the chat server to receive the second package data from the chat server. And the identification information corresponding to the client device is included in the second recipient list in the second package data. The method of claim 11,
The client device,
A method of providing a client-based chat service, comprising: a mobile terminal for executing a client-based chat service by executing an application installed through an application store server. The method of claim 11,
Each of the first message header and the second message header,
A method for providing a client-based chat service, characterized by further comprising group information for identifying a chat group, which means a group of users who are chatting with each other or a group of users within a message delivery range. A first client device configured to package a message header including sender information, a recipient list, and message type information and package the input message to generate and transmit package data, and to output the input message to a chat screen;
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 device receiving the package data and outputting a message packaged in the package data to a chat screen;
Including, Wherein the recipient list System for providing a client-based chat service comprising the identification information corresponding to the second client device. 21. The method of claim 20,
The second client device,
System for providing a client-based chat service, characterized in that to identify a chat participant list based on the sender information and the recipient list included in the message header packaged in the package data to add a new participant or delete an existing participant. A recording medium having recorded thereon a program for executing a method of providing a client-based chat service,
A function of outputting the inputted first message on the chat screen;
When the first message is input, a first message header including first sender information, a first receiver list, and first message type information and a package of 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 recipient list, and a second message type information, and second package data in which the second message is packaged;
And a computer-readable recording medium having recorded thereon a program implementing the function of outputting the second message to the chat screen.

Images