Method and apparatus for providing summary of fan messages received during absence

Abstract

An embodiment of the present invention relates to a method and apparatus for providing a summary of fan messages received during absence, which can enhance an artist's convenience in checking fan messages by providing a summary of a plurality of fan messages received during the artist's absence in a message transmission and reception service between the artist and a plurality of fans.

Description

Method and device for providing a summary of missed fan messages

[0001] The present invention relates to a method and apparatus for providing a summary of absent fan messages, and more specifically, to a method and apparatus for providing a summary of absent fan messages to enhance the convenience of sending and receiving messages between an artist and a number of fans following the artist.

[0002] Due to the recent growth of the entertainment industry and the advancement of IT technology, social network services and fan platforms for communication between celebrities, artists, and fans are on the rise. These social network services can serve as fan community hubs. For example, they can comprehensively provide features such as communication with celebrities and artists, live broadcasting, and fan community functions.

[0003] In addition, these fan platforms are expanding their functions beyond the functions of existing communities to a wide range of areas, such as selling and purchasing merchandise, booking tickets for concerts and events, providing their own content, and applying non-fungible tokens (NFTs).

[0004] As the functionality of fan platforms expands, the notifications and messages provided to users can also be diverse. For example, if a feature is provided that allows artists to directly write and post articles, messages, or videos to the community, users can receive immediate push notifications when artists write posts or comments, or receive notifications regarding various benefits for membership subscribers. Furthermore, notifications and messages with different content can be provided depending on the various features.

[0005] Furthermore, with the recent development of various online-based messaging services, there has been a surge in demand from artists, such as celebrities and creators, for more direct and intimate communication with their fans. Consequently, services providing personalized one-on-one message exchanges between artists and fans have emerged. Notably, services that allow artists and fans to exchange messages individually can provide fans with a special sense of intimacy and belonging, thereby having the effect of revitalizing fandom culture.

[0006] However, conventional artist-fan messaging services had a problem in that it was difficult to efficiently manage or track the large number of messages sent by fans when the artist was unable to access the service for an extended period due to personal schedules or activities.

[0007] When a large volume of messages accumulates while an artist is away, the artist faces the burden of having to check every single message received during their absence, and there is a possibility that important or meaningful messages may be missed in this process. Additionally, fans also face the disadvantage of finding it difficult to clearly determine whether their messages were properly delivered to the artist, and they experience anxiety that their messages might get buried among many others and go unread.

[0008] The method and device for providing a summary of absent fan messages according to an embodiment of the present invention are intended to increase the convenience of an artist who exchanges messages with multiple fans.

[0009] In addition, the method and device for providing a summary of absent fan messages according to an embodiment of the present invention are intended to increase the convenience of checking a number of fan messages received while the artist is not online.

[0010] However, the technical problem that this embodiment aims to solve is not limited to the technical problem described above, and other technical problems may exist.

[0011] As a technical means for achieving the aforementioned technical problem, a method for providing a message transmission and reception service according to an embodiment of the present invention is a method for providing a message transmission and reception service between an artist terminal and a fan terminal using a message transmission and reception server, comprising the steps of: receiving a plurality of fan messages transmitted from a fan terminal to an artist; identifying an absent message received among the plurality of fan messages during a period when the artist terminal is not connected; generating one or more representative messages for the absent messages; and providing the representative message to the artist terminal.

[0012] In addition, the step of generating a representative message according to an embodiment of the present invention includes the step of deriving a semantic value for each absent message, the step of classifying the absent messages into one or more message groups according to the semantic value, and the step of generating a representative message for each message group.

[0013] In addition, the step of providing a representative message to an artist terminal according to an embodiment of the present invention includes the step of setting a priority for each representative message and the step of providing the representative message to the artist terminal according to the priority within a preset maximum number of displays.

[0014] In addition, the step of providing a representative message to an artist terminal according to an embodiment of the present invention further includes the step of displaying original fan messages of a message group included in the selected representative message when the representative message is selected.

[0015] In addition, the step of providing a representative message according to an embodiment of the present invention to an artist terminal further includes a filtering step in which, when the artist terminal selects a representative message to be filtered, subsequent messages having a semantic value similar to that of the representative message to be filtered are excluded from the display target.

[0016] In addition, the step of deriving a semantic value according to an embodiment of the present invention includes the step of deriving a semantic value for each fan message by inputting a plurality of fan messages into an embedding model, and further includes the step of using at least one model among the Clova Embedding V2 model and the Finetuned-BGE-M3 model as the embedding model.

[0017] In addition, the step of classifying a plurality of fan messages to generate one or more message groups according to an embodiment of the present invention includes the step of generating message groups by inputting a plurality of fan messages, for which semantic values ​​have already been matched, into a clustering model, and further includes the step of using an HDBSCAN model for the clustering model.

[0018] In addition, the step of determining a representative message based on a message group according to an embodiment of the present invention includes the step of inputting the message group into a summary model to derive a representative message for each message group, and the summary model further includes the step of using at least one model among the HyperClova LLM model or the Finetuned-Llama 3.2 model.

[0019] Additionally, the step of providing a representative message to an artist terminal according to an embodiment of the present invention further includes the steps of providing a representative message display interface to the artist terminal, displaying a representative message on the representative message display interface, and providing a plurality of fan messages corresponding to a representative message selected by the artist on the representative message display interface.

[0020] In addition, a message transmission and reception service providing device according to an embodiment of the present invention is a device that provides a message transmission and reception service between an artist terminal and a fan terminal using a message transmission and reception server, and comprises at least one memory and at least one processor that performs a message transmission and reception service by executing at least one application stored in the memory, and the instructions of the processor include the steps of receiving a plurality of fan messages transmitted from a fan terminal to an artist, identifying an absent message received among the plurality of fan messages during a period when the artist terminal is in an unconnected state, generating one or more representative messages for the absent messages, and providing the representative message to the artist terminal.

[0021] In addition, the instructions of a processor according to an embodiment of the present invention further include the steps of deriving a semantic value for each absent message, classifying the absent messages into one or more message groups according to the semantic value, and generating a representative message for each message group.

[0022] In addition, the instructions of the processor according to an embodiment of the present invention further include the steps of setting a priority for each representative message and providing representative messages to an artist terminal according to the priority within a preset maximum number of displays.

[0023] In addition, the instruction of the processor according to an embodiment of the present invention further includes the step of displaying the original fan message of a message group included in the selected representative message when a representative message is selected.

[0024] In addition, the instruction of the processor according to an embodiment of the present invention further includes a filtering step in which, when the artist terminal selects a representative message to be filtered, subsequent messages having a semantic value similar to the representative message to be filtered are excluded from the display target.

[0025] In addition, the instruction of the processor according to an embodiment of the present invention includes the step of inputting a plurality of fan messages into an embedding model to derive a semantic value for each fan message, and further includes the step of using at least one model among the Clova Embedding V2 model and the Finetuned-BGE-M3 model as the embedding model.

[0026] In addition, the instruction of the processor according to an embodiment of the present invention includes the step of generating a message group by inputting a plurality of fan messages, in which semantic values ​​are already matched, into a clustering model, and the clustering model further includes the step of using an HDBSCAN model.

[0027] In addition, the instruction of the processor according to an embodiment of the present invention includes the step of inputting a message group into a summary model to derive a representative message for each message group, and the summary model further includes the step of using at least one of the HyperClova LLM model or the Finetuned-Llama 3.2 model.

[0028] The method and device for providing a summary of absent fan messages according to an embodiment of the present invention can increase the convenience of an artist exchanging messages with multiple fans.

[0029] In addition, the method and device for providing a summary of absent fan messages according to an embodiment of the present invention can increase the convenience of checking a number of fan messages received while the artist is not connected.

[0030] FIG. 1 is an exemplary diagram showing a communication connection of a message transmission and reception service providing device according to an embodiment of the present invention.

[0031] FIG. 2 is a configuration diagram of a message transmission and reception service relay server according to an embodiment of the present invention.

[0032] FIG. 3 is a configuration diagram of a terminal according to an embodiment of the present invention.

[0033] FIG. 4 is a conceptual diagram illustrating the functions of a processor according to an embodiment of the present invention.

[0034] FIG. 5 is a data flow diagram for summarizing absent fan messages according to an embodiment of the present invention.

[0035] FIG. 6 is a data flow diagram for generating a final representative message according to an embodiment of the present invention.

[0036] FIG. 7 is a flowchart of a method for summarizing absent fan messages according to an embodiment of the present invention.

[0037] FIG. 8 is a flowchart of a representative message selection method according to an embodiment of the present invention.

[0038] FIG. 9 is a flowchart of a representative message generation method according to an embodiment of the present invention.

[0039] FIG. 10 is a flowchart of a method for determining a final representative message according to an embodiment of the present invention.

[0040] FIG. 11 is a flowchart of a representative message filtering method according to an embodiment of the present invention.

[0041] FIG. 12 is an example diagram of an absent message summary display interface according to an embodiment of the present invention.

[0042] FIG. 13 is an example diagram of an absent message summary display interface according to an embodiment of the present invention.

[0043] FIG. 14 is an example diagram of a text fan message display interface according to an embodiment of the present invention.

[0044] FIG. 15 is a conceptual diagram illustrating the functions of a database according to an embodiment of the present invention.

[0045] FIG. 16 is a conceptual diagram of data processing for storing fan messages according to an embodiment of the present invention.

[0046] FIG. 17 is a data flow diagram for storing artist messages according to an embodiment of the present invention.

[0047] FIG. 18 is a data flow diagram for private chat inquiry of a fan terminal according to an embodiment of the present invention.

[0048] FIG. 19 is a data flow diagram for private chat inquiry of a fan terminal according to an embodiment of the present invention.

[0049] FIG. 20 is a data flow diagram for private chat inquiry of an artist terminal according to an embodiment of the present invention.

[0050] FIG. 21 is a flowchart of a fan message storage method according to an embodiment of the present invention.

[0051] FIG. 22 is a flowchart of an artist message storage method according to an embodiment of the present invention.

[0052] FIG. 23 is a flowchart of a private chat update method according to an embodiment of the present invention.

[0053] FIG. 24 is a flowchart of a private chat update method according to an embodiment of the present invention.

[0054] FIG. 25 is a flowchart of a private chat update method according to an embodiment of the present invention.

[0055] Embodiments of the present invention are described below in detail with reference to the attached drawings so that those skilled in the art can easily implement the invention. However, the present invention may be embodied in various different forms and is not limited to the embodiments described herein. Furthermore, in order to clearly explain the present invention in the drawings, parts unrelated to the explanation have been omitted, and similar parts throughout the specification are denoted by similar reference numerals.

[0056] Throughout the specification, when a part is described as being "connected" to another part, this includes not only cases where they are "directly connected," but also cases where they are "electrically connected" with other components interposed between them. Furthermore, when a part is described as "including" a certain component, this means that, unless specifically stated otherwise, it does not exclude other components but may include additional components.

[0057] In addition, the attached drawings are intended only to facilitate understanding of the embodiments disclosed in this specification, and the technical concept disclosed in this specification is not limited by the attached drawings; it should be understood that all modifications, equivalents, and substitutions included within the concept and technical scope of the present invention are included.

[0058] Terms including ordinal numbers, such as first, second, etc., may be used to describe various components, but said components are not limited by said terms. These terms are used solely for the purpose of distinguishing one component from another.

[0059] When it is stated that one component is "connected" or "connected" to another component, it should be understood that while it may be directly connected or connected to that other component, there may also be other components in between. On the other hand, when it is stated that one component is "directly connected" or "directly connected" to another component, it should be understood that there are no other components in between.

[0060] A singular expression includes a plural expression unless the context clearly indicates otherwise.

[0061] In this application, terms such as “comprising” or “having” are intended to specify the existence of the features, numbers, steps, actions, components, parts, or combinations thereof described in the specification, and should be understood as not precluding the existence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof.

[0062] Hereinafter, a message transmission and reception service providing device according to an embodiment of the present invention will be described with reference to FIG. 1.

[0063] FIG. 1 is an exemplary diagram showing a communication connection between a message transmission and reception service relay server (100) and a terminal (200) according to an embodiment of the present invention.

[0064] Referring to FIG. 1, a message transmission and reception service relay server (100) is connected to a terminal (200) via a communication network. At this time, the message transmission and reception service relay server (100) refers to a device for providing message transmission and reception between users using a fan platform, social network service, etc., and may correspond to a fan platform server, social network service server, etc. The terminal (200) includes an artist terminal (200-1) used by celebrities, artists, etc., and a fan terminal (200-2) used by fans following celebrities, artists, etc. The terminal (200) may refer to a device that displays messages and notifications received from the message transmission and reception service relay server (100) to the user.

[0065] The message transmission and reception service relay server (100) can generate and provide messages and notification lists to users on fan platforms, social network services, etc. At this time, rather than simply providing messages and notifications to users, it can provide personalized message and notification lists to users based on filtering information for each user.

[0066] In addition, the message transmission and reception service relay server (100) performs message transmission and reception between multiple fan accounts of the artist account, and by displaying one-on-one messages between the fan and the artist in the fan's message chat room, it provides an experience of one-on-one message transmission and reception between the fan and the artist.

[0067] Additionally, the message transmission and reception service relay server (100) can generate one or more representative messages for fan messages received from multiple fans when the artist is absent (not connected) and provide them to the artist. Accordingly, the contents of multiple fan messages received while the artist is absent can be summarized and provided. The specific configuration of the message transmission and reception service relay server (100) will be explained in detail with reference to FIGS. 2 and FIGS. 4, which will be described later.

[0068] The terminal (200) may refer to any type of handheld-based wireless communication device, such as a laptop, desktop, laptop, a wireless communication device with guaranteed portability and mobility, or a smartphone, tablet PC, etc., equipped with a web browser.

[0069] In addition, the communication network illustrated in FIG. 1 can be implemented as a wired network such as a Local Area Network (LAN), Wide Area Network (WAN), or Value Added Network (VAN), or as any type of wireless network such as a mobile radio communication network or a satellite communication network.

[0070] Hereinafter, the structure of a message transmission and reception service relay server according to an embodiment of the present invention will be described with reference to FIG. 2.

[0071] FIG. 2 is a structural diagram illustrating the structure of a message transmission and reception service relay server (100) according to an embodiment of the present invention.

[0072] Referring to FIG. 2, the message transmission and reception service relay server (100) includes a communication module (110), memory (120), and a processor (140), and may further include a database (130). The communication module (110) performs information transmission and reception with terminals (200, 201). The communication module (110) may include a device including hardware and software necessary to transmit and receive signals, such as control signals or data signals, using a wired or wireless connection with another network device.

[0073] The memory (120) stores a message transmission and reception program. The name of the message transmission and reception program is set for convenience of explanation and does not limit the function of the program by the name itself. The memory (120) can store at least one of the following: information and data input to the communication module (110), information and data required for functions performed by the processor (140), and data generated by the execution of the processor (140).

[0074] The term "memory" (120) should be interpreted as a collective term for a non-volatile storage device that retains stored information even when power is not supplied, and a volatile storage device that requires power to retain stored information. Additionally, the memory (120) can perform the function of temporarily or permanently storing data processed by the processor (140). The memory (120) may include magnetic storage media or flash storage media in addition to a volatile storage device that requires power to retain stored information, but the scope of the present invention is not limited thereto.

[0075] The database (130) can store data related to artist information, user (fan) information, subscription information, artist messages, fan messages, and private messages converted and provided for each fan user. The database (130) may constitute a part of the memory (120), but is not necessarily located inside the message transmission and reception service relay server (100), and may be connected to the outside of the message transmission and reception service relay server (100) to perform data transmission and reception using a communication connection.

[0076] Additionally, the database (130) may be configured to store message data on an artist-by-artist and user (fan)-by-user basis. The detailed configuration of the database (130) will be described in detail with reference to FIG. 15, which will be described later.

[0077] The processor (140) is configured to execute a message transmission and reception program in memory (120). The processor (140) may include various types of devices for controlling and processing data. The processor (140) may refer to a data processing device embedded in hardware having a physically structured circuit to perform a function expressed by code or instructions included in a program. In one example, the processor (140) may be implemented in the form of a microprocessor, a central processing unit (CPU), a processor core, a multiprocessor, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc., but the scope of the invention is not limited thereto.

[0078] The processor (140) is configured to execute a message transmission and reception program to perform the following functions and procedures.

[0079] The processor (140) can receive multiple fan messages transmitted from the fan terminal (200-2) to the artist account. Among the received fan messages, the processor (140) can identify as absent messages messages received during the period when the artist terminal (200-1) is not connected, or fan messages that the artist account has not acknowledged, as absent messages.

[0080] The processor (140) generates one or more representative fan messages for the identified out-of-office message. Then, by providing the representative fan message generated upon accessing the artist account to the artist terminal (200-1), the fan messages can be summarized and provided so that the artist can easily check multiple fan messages received during their absence.

[0081] The processor (140) can derive a semantic value for each identified absence message, and to do so, the processor (140) inputs the absence message into an embedding model to derive the semantic value of the message. The embedding model used at this time may use at least one of, for example, the Clova Embedding V2 model or the Finetuned-BGE-M3 model.

[0082] The processor (140) can classify the absent messages into one or more message groups based on the derived semantic values, and can use a clustering model for this purpose. As a clustering model, an HDBSCAN model can be applied to determine the similarity of the messages and form message groups.

[0083] The processor (140) can generate a representative message for each message group. To generate the representative message, the processor (140) uses a summary model to analyze the messages within the message group and derives a representative message that best represents the group. As the summary model used, at least one of the HyperClova LLM model or the Finetuned-Llama 3.2 model may be used.

[0084] The processor (140) can set a priority for each generated representative message and, according to the set priority, can select representative messages to be provided to the artist terminal (200-1) within a preset maximum number of displays. Additionally, if the artist terminal (200-1) selects a specific representative message, the processor (140) can display original fan messages included in the message group to the artist terminal (200-1).

[0085] When the processor (140) selects a specific representative message as a filtering target in response to a request from the artist terminal (200-1), it can filter subsequent messages having a similar semantic value to the filtering target so that they are not displayed to the artist terminal (200-1).

[0086] Additionally, the processor (140) may provide a representative message display interface to the artist terminal (200-1), thereby enabling the artist terminal (200-1) to intuitively and efficiently view and manage representative messages and original messages. At this time, the representative message display interface may provide multiple fan messages corresponding to the representative message selected by the artist.

[0087] Additionally, the processor (140) can generate a private message by converting the nickname identification code included in the reply message into a nickname set corresponding to the fan terminal. Then, the processor (140) can transmit the private message to the corresponding fan terminal. The method for generating and transmitting the private message will be explained in detail with reference to FIGS. 15 to 25 described later.

[0088] FIG. 3 is a block diagram illustrating the configuration of a terminal (200).

[0089] Referring to FIG. 3, the terminal (200) includes a memory (220), an input / output module (230), and a processor (240), and may further include a communication module (210).

[0090] The communication module (210) can perform information transmission and reception with an external database or an external device. Here, the external device may be the message transmission and reception service relay server (100) described above. The memory (220) stores a message transmission and reception program. The name of the message transmission and reception program is set for convenience of explanation and does not limit the function of the program by the name itself.

[0091] The input / output module (230) can receive information, data, etc. transmitted from the outside to the terminal (200), or output information, data, etc. held by the terminal (200) to the outside. For example, the input / output module (230) may include a display, a touchpad, etc. The processor (240) executes a message transmission / reception program stored in the memory (220). Additional descriptions of the communication module (210), memory (220), and processor (240) will be replaced by the descriptions of the communication module (110 in FIG. 2), memory (120 in FIG. 2), and processor (140 in FIG. 2) described above with reference to FIG. 2.

[0092] Additionally, the processor (240) is configured to execute a message transmission and reception program to perform the following functions and procedures.

[0093] The processor (240) can transmit artist messages or fan messages generated at the terminal (200) to the message transmission and reception service relay server (100). Additionally, the processor (240) can receive and display artist messages, fan messages, private messages, feeds, alarms, interfaces, etc., stored and generated at the message transmission and reception service relay server (100).

[0094] The processor (240) can view and manage representative messages and original fan messages belonging to the corresponding message group through a representative message display interface provided by the message transmission and reception service relay server (100). The processor (240) can also prevent the repetitive display of similar messages by selecting specific representative messages as filtering targets at the request of the artist.

[0095] The processor (240) of the fan terminal (200-2) can efficiently and intuitively display private messages received from the artist to support smooth interaction with the fan.

[0096] Hereinafter, the function and operation of the processor (140) according to an embodiment of the present invention will be described in detail with reference to FIG. 4.

[0097] FIG. 4 is a conceptual diagram illustrating the functions of a message transmission and reception service relay server according to an embodiment of the present invention.

[0098] Referring to FIG. 4, the processor (140) can perform the functions of a preprocessing unit (141), an embedding unit (142), a clustering unit (143), a summary unit (144), a search unit (145), and a representative message management unit (146).

[0099] The preprocessing unit (141) identifies fan messages received while the artist account is away. Then, the preprocessing unit (141) generates bundles of fan messages while the artist is away based on a preset unit time and / or a preset number.

[0100] Bundles of absent fan messages can be selected through a load-controlled sampling procedure that samples at a preset rate based on the system load status, and the sampling criteria can be strengthened if the system processing metric standard is exceeded according to conditions such as exceeding request limits, occurrence of failures, or processing delays.

[0101] Additionally, the preprocessing unit (141) can obtain a list of fan message IDs from the artist receiving database and collect fan message data including the body of the fan message, subscriber ID, etc., corresponding to the ID. Preprocessing operations such as removing special characters, removing stop words, and tokenization are performed on the collected messages.

[0102] The embedding unit (142) extracts semantic values ​​for each fan message, and the clustering unit (143) can classify multiple fan messages according to semantic values ​​to create one or more message groups.

[0103] In this case, the meaning of the message may refer to the intent, content, and / or intention represented by the message.

[0104] Additionally, a semantic value may refer to information used to distinguish or group multiple fan messages. More specifically, a semantic value may further refer to a data value that expresses the meaning of a fan message in vector form, and may be in the form of a high-dimensional real vector.

[0105] The embedding unit (142) converts the preprocessed fan message into a semantic value vector. The semantic value refers to a high-dimensional real number vector that quantifies the meaning, intention, content, etc., represented by the message. It tokenizes words, sentences, creation timestamps, subscriber IDs, photos, or videos included in the fan message, maps them to a vector space, and extracts the semantic value based on this.

[0106] The embedding section can be implemented using a model such as Clova Embedding V2, and a standby model such as Finetuned-BGE-M3 can be used in the event of system load or error. In addition, various embedding models such as Doc2Vec, USE, SBERT, and OpenAI Embedding can be applied as alternatives.

[0107] The clustering unit (143) classifies absent fan messages into one or more message groups based on the embedded fan message semantic values. The classification is based on the similarity of semantic values, and the fan messages can be automatically clustered using a clustering model including an HDBSCAN model after being converted into locations in a vector space. The number of clusters can be adjusted to be below a preset standard, and models such as K-Means, DBSCAN, GMM, and Spectral Clustering can also be utilized.

[0108] The summary unit (144) analyzes the fan messages of each message group to generate a representative message. The representative message can be generated by selecting the fan message with the highest similarity to the average semantic value, or by summarizing the absent fan messages within the message group. When summarizing, weights can be assigned to elements within the fan message and combined to form a single text. The model used is HyperClova LLM, and in exceptional cases, models such as Finetuned-Llama 3.2, BART, PEGASUS, T5, etc., can be used.

[0109] The summary unit (144) can determine the similarity between the fan message and the average of the semantic values ​​by determining the average of the semantic values ​​based on the semantic values ​​of multiple fan messages included in one message group.

[0110] The summary unit (144) can determine the similarity between a fan message and an average semantic value, and select a fan message with the highest semantic value among multiple fan messages included in a message group as a representative message.

[0111] On the other hand, when the summary unit (144) determines a fan message created by summarizing a fan message included in a message group as a representative message, it may create a representative message by combining the elements included in the fan message, giving weights to the elements included in the fan message, and creating a message in the form of text such as a sentence by combining the given elements.

[0112] The search unit (145) determines the similarity between summarized representative messages and searches for similar representative messages. The search is performed through various search layers such as OpenSearch, Elasticsearch, and Pinecone, and if the similarity between representative messages is greater than or equal to a preset standard, it requests the clustering unit (143) to integrate message groups for similar representative messages.

[0113] The summary unit (144) generates a final representative message based on an integrated message group. The summary unit (144) can again derive a final representative message based on a summary or semantic value similarity method.

[0114] If no similar representative message exists, the search unit (145) confirms the existing representative message as the final representative message.

[0115] The representative message management unit (146) performs the function of storing and managing representative messages and final representative messages for absent fan messages.

[0116] The representative message management unit (146) sets the priority of representative messages displayed on the artist terminal (200-1) and selects messages to be provided within the maximum number of displayed messages. The priority of the representative message can be set based on the number of absent fan messages included in the message group corresponding to the representative message.

[0117] In addition, the representative message management unit (146) can also perform a filtering function to exclude subsequent fan messages having a similar semantic value to the representative message from being displayed when the artist designates a specific representative message as a filtering target. Through such a representative message management function, the artist can efficiently check fan messages and minimize the exposure of repetitive and unnecessary messages.

[0118] Hereinafter, the data flow for summarizing absent fan messages will be described in detail with reference to FIG. 5.

[0119] FIG. 5 is a data flow diagram for summarizing absent fan messages according to an embodiment of the present invention.

[0120] Referring to FIG. 5, the message transmission and reception server (100) can acquire fan messages from the fan terminal (200-2) and store them in the database (130).

[0121] The preprocessing unit (141) classifies the fan messages stored in the database (130) as absent messages received during the period when the artist account is not logged in or messages that the artist has not viewed as absent fan messages. The preprocessing unit (141) can sample the absent fan messages by a preset number.

[0122] The embedding unit (142) derives the semantic value of the absent fan message sampled from the preprocessing unit (141).

[0123] The clustering unit (143) can generate message groups by classifying absent fan messages, for which semantic values ​​were obtained from the embedding unit (142), according to semantic values.

[0124] The summary unit (144) can generate a representative message based on the message group generated by the clustering unit (143).

[0125] Representative messages generated in the summary unit (144) are transmitted to the representative message management unit (146), and the representative message management unit (146) performs data processing related to the representative messages, such as merging representative messages or providing them to the artist terminal (200-1).

[0126] Hereinafter, the data flow for generating the final representative message will be described in detail with reference to FIG. 6.

[0127] FIG. 6 is a data flow diagram for generating a final representative message according to an embodiment of the present invention.

[0128] When the search unit (145) receives a request to search for similar representative messages from the representative message management unit (146), it can search whether there are similar representative messages among the generated representative messages.

[0129] The search unit (145) transmits the search result of the absence of a similar representative message to the representative message management unit (146) if there is no similar representative message for the representative message for which a search was requested.

[0130] The representative message management unit (146) sets the representative message requested by the search as the final representative message when it receives a search result in which no similar representative message exists.

[0131] The search unit (145) transmits the search result of the existence of similar representative messages to the clustering unit (143) if there is a similar representative message to the representative message for which a search was requested.

[0132] The clustering unit (143) integrates message groups for similar representative messages and requests the summary unit (144) to generate a final representative message for the integrated message groups.

[0133] The summary unit (144) generates a final representative message based on the integrated message group and transmits the generated final representative message to the representative message management unit (146).

[0134] The representative message management unit (146) provides the final representative message to the artist terminal (200-1) when the final representative message is derived.

[0135] Hereinafter, a method for providing a summary of absent fan messages according to an embodiment of the present invention will be described in detail with reference to FIGS. 7 to 11.

[0136] FIG. 7 is a flowchart of a method for providing a summary of fan messages while absent according to an embodiment of the present invention.

[0137] Referring to FIG. 7, the method for providing a summary of absent fan messages according to an embodiment of the present invention includes an absent fan message classification step (S100), a message group classification step (S200), and a representative message generation step (S300).

[0138] In the absent fan message classification step (S100), the message transmission / reception service relay server (100) receives a plurality of fan messages transmitted from the fan terminal (200-2) to the artist account, and among them, identifies and classifies messages received during the time period when the artist terminal (200-1) is not connected as absent messages.

[0139] Missed message classification is performed based on reception time information, artist terminal connection history information, etc.

[0140] Additionally, in the absent fan message classification step (S100), the message transmission and reception service relay server (100) may perform sampling for system load control in parallel and refine the message so that it can be analyzed through a preprocessing process.

[0141] In the out-of-office fan message classification step (S100), the message transmission / reception service relay server (100) can generate out-of-office fan message bundles based on a preset unit time and / or a preset number.

[0142] Additionally, in the absent fan message classification step (S100), the message transmission and reception service relay server (100) can be selected through a load control sampling procedure that samples at a preset rate according to the system load status, and the sampling criteria can be strengthened if the system processing indicator standard is higher than the requested limit, failure, or processing delay.

[0143] Additionally, in the absent fan message classification step (S100), the message transmission / reception service relay server (100) may obtain a list of fan message IDs from the artist reception database and collect fan message data including the body of the fan message, subscriber ID, etc., corresponding to the ID. Preprocessing operations such as removing special characters, removing stop words, and tokenization may be performed on the collected messages.

[0144] In the message group classification step (S200), the message transmission and reception service relay server (100) derives a semantic value for each absent fan message identified in the absent fan message classification step (S100), and clusters similar messages together based on the derived semantic value to classify them into one or more message groups.

[0145] The semantic value is a vector value derived through an embedding model and can refer to information used to distinguish or group multiple fan messages. More specifically, the semantic value can refer to a data value that expresses the meaning of a fan message in vector form, and may be in the form of a high-dimensional real vector.

[0146] In the message group classification step (S200), the message transmission / reception service relay server (100) converts the out-of-office fan message into a semantic value vector. The semantic value refers to a high-dimensional real number vector that quantifies the meaning, intention, content, etc., represented by the message. Words, sentences, time of creation, subscriber ID, photos, or videos included in the fan message are tokenized and mapped into a vector space, and the semantic value is extracted based on this.

[0147] In the message group classification step (S200), the message transmission and reception service relay server (100) can derive the semantic value of the absent fan message using a model such as Clova Embedding V2, and a standby model such as Finetuned-BGE-M3 can be used in the event of system load or error. In addition, various embedding models such as Doc2Vec, USE, SBERT, and OpenAI Embedding can be applied as alternatives.

[0148] In the message group classification step (S200), the message transmission / reception service relay server (100) classifies the absent fan messages into one or more message groups based on the embedded fan message semantic values. The classification is based on the similarity of the semantic values, and the fan messages can be automatically clustered using a clustering model including an HDBSCAN model after being converted into locations in a vector space. The number of clusters can be adjusted to be below a preset standard, and models such as K-Means, DBSCAN, GMM, and Spectral Clustering can also be utilized.

[0149] In the representative message generation step (S300), the message transmission and reception service relay server (100) can determine a representative message representing each message group or create a new representative message for each message group.

[0150] The representative message generation step (S300) is explained in detail with reference to FIGS. 8 and FIGS. 9, which will be described later.

[0151] FIG. 8 is a flowchart of a representative message selection method according to an embodiment of the present invention.

[0152] Referring to FIG. 8, the representative message selection method includes a semantic value average determination step (S311), a similarity determination step (S312), and a representative message selection step (S313).

[0153] In the step of determining the average semantic value (S311), the message transmission and reception service relay server (100) derives a semantic value for each of the plurality of fan messages included in the message group using an embedding unit, and calculates the central semantic value of the group by averaging the derived semantic values ​​in a high-dimensional vector space.

[0154] Here, the mean-centered semantic value functions as a reference value that numerically expresses the core meaning or theme represented by the message group, and is subsequently used as a criterion for selecting the representative message.

[0155] In the similarity determination step, the message transmission and reception service relay server (100) calculates the similarity between the central semantic value calculated in the semantic value average determination step and the individual semantic value of each fan message. The similarity is quantified using a vector-to-vector distance-based measurement technique, such as cosine similarity, for example, and can quantitatively determine how similar each fan message is to the central semantic value.

[0156] In the representative message selection step (S313), the message transmission / reception service relay server (100) selects the fan message having the highest similarity value among the similarity values ​​calculated in the similarity determination step and designates it as the representative message of the corresponding message group. Thus, the message closest semantically to the center of the group is selected as the representative message and can be utilized as a message that most effectively summarizes the overall meaning of the group.

[0157] FIG. 9 is a flowchart of a representative message generation method according to an embodiment of the present invention.

[0158] Referring to FIG. 9, the representative message generation method includes a step of assigning weights to elements (S321) and a representative message generation step (S322).

[0159] In the step of assigning weights to elements (S321), the message transmission and reception service relay server (100) analyzes the elements included in each fan message included in the message group and assigns weights to each element according to importance.

[0160] Here, the elements included in the fan message may include text information (words, sentences), time of creation, the fan's subscriber ID, the fan's activity history (e.g., frequency of message creation, history of fan activity participation), multimedia information (whether photos or videos are included), etc. The message transmission and reception service relay server (100) assigns a higher weight to the elements among these elements that have high representativeness and influence as information to be delivered to the artist, thereby ensuring that the representative message to be generated in the future reflects more core content.

[0161] In the representative message generation step (S322), the message transmission and reception service relay server (100) comprehensively analyzes the elements of each fan message to which weights were assigned in the element weighting step (S321) to generate a representative message in the form of natural language.

[0162] At this time, the message transmission and reception service relay server (100) can generate text organized into a core sentence form by utilizing a summary model or combining elements with high weight. For example, a representative message is written in a summarized form so that the artist can easily identify the fan's interests and passion by emphasizing words or topics that appear commonly in multiple fan messages and by referring to time information or fan activity information.

[0163] As described above, the message transmission and reception service relay server (100) can determine a representative message for each message group by determining one of the absent fan messages included in the message group as the representative message for the group, or by using a method of creating a new representative message based on the weight of each element of the message group.

[0164] Hereinafter, a method for determining the final representative message will be explained in detail with reference to FIG. 10.

[0165] FIG. 10 is a flowchart of a method for determining a final representative message according to an embodiment of the present invention.

[0166] Referring to FIG. 10, the final representative message determination method includes a representative message determination step (S310), a similarity comparison step (S320), a message group integration step (S330), a final representative message generation step (S340), and a final representative message determination step (S350).

[0167] In the representative message determination step (S310), the message transmission / reception service relay server (100) obtains a plurality of representative messages determined through the representative message generation step (S300) described above.

[0168] In the similarity comparison step (S320), the message transmission / reception service relay server (100) derives a semantic value for each representative message. The derived semantic value is used as a standard for similarity comparison and integrated processing. This step is a preliminary procedure for deriving the final representative message and is a step for configuring input values ​​for subsequent judgments targeting representative messages for each individual group.

[0169] In the similarity comparison step (S320), the message transmission / reception service relay server (100) compares the semantic values ​​between representative messages and calculates the similarity between the representative messages. The similarity can be calculated using a vector distance measurement technique such as cosine similarity, and if it is greater than or equal to a set similarity threshold, the two representative messages are determined to be semantically similar. This allows for the identification of duplicate or semantically similar representative messages.

[0170] In the similarity comparison step (S320), the message transmission and reception service relay server (100) performs the message group integration step (S330) if there is a representative message with a similarity greater than or equal to a preset standard, and performs the final representative message determination step (S350) if there is no representative message with a similarity greater than or equal to a preset standard.

[0171] In the message group integration step (S330), the message transmission and reception service relay server (100) merges each message group corresponding to a plurality of representative messages determined to be similar in the similarity comparison step (S320) into a single integrated group. At this time, the fan messages included in each group belong to the integrated group, and the integrated message group is again used as a single input to generate a final message with representativeness.

[0172] In the final representative message generation step (S340), the message transmission / reception service relay server (100) generates a final representative message for the message group merged in the message group integration step (S330). The method for generating the final representative message may be performed in at least one of the following: selecting the most similar message based on the average semantic value of the integrated group, similar to the existing representative message generation method, or analyzing the elements included in the integrated message and reflecting weights to create a new summary message in natural language form. This process may also be performed in parallel with a summary model or a search layer.

[0173] In the final representative message determination step (S350), the message transmission and reception service relay server (100) determines the final representative message for each message group and can provide the final representative message to the artist terminal (200-1).

[0174] In the final representative message determination step (S350), the message transmission / reception service relay server (100) reviews the final representative message generated in the final representative message generation step (S340) and determines the message as the final representative message to be provided to the artist terminal (200-1).

[0175] On the other hand, in the final representative message determination step (S350), if no similar representative message exists in the similarity comparison step (S320), the message transmission / reception service relay server (100) may determine the existing representative message as the final representative message. This step is a final procedure for determining the message to be finally displayed to the artist, and contributes to the removal of duplicates and the improvement of message quality.

[0176] Hereinafter, a representative message filtering method will be described in detail with reference to FIG. 11.

[0177] FIG. 11 is a flowchart of a representative message filtering method according to an embodiment of the present invention.

[0178] Referring to FIG. 11, the representative message filtering method includes a filtering representative message setting step (S110), a filtering message semantic value acquisition step (S210), a semantic value similarity comparison step (S220), and a similar representative message filtering step (S230).

[0179] In the filtering representative message setting step (S110), the message transmission / reception service relay server (100) receives a user selection input from the artist terminal (200-1) that designates a representative message or a portion of the final representative message as a 'filtering target'. The artist may designate, for example, repetitive messages, messages on unwanted topics, or representative messages containing spam content as filtering targets.

[0180] The filtering target set in the filtering representative message setting step (S110) may be a message generated in the representative message generation step (S300) or a message derived through the final representative message determination step (S350). This step reflects a user-centric interface function that supports the artist in directly controlling content quality.

[0181] In the filtering message semantic value acquisition step (S210), the message transmission / reception service relay server (100) derives the semantic value of the corresponding message by using the representative message designated as a filtering target in the filtering representative message setting step (S110) or the final representative message as input. The semantic value is high-dimensional vector data calculated through an embedding model (e.g., Clova Embedding V2, Finetuned-BGE-M3, etc.), and is a numerical representation of the message's topic, intent, emotion, etc. In filtering, this semantic value is used as a future comparison standard.

[0182] In the semantic value similarity comparison step (S220), the message transmission / reception service relay server (100) calculates the similarity between the semantic value of the filtering target message derived in the filtering message semantic value acquisition step (S210) and the semantic value of new representative messages or final representative messages that are scheduled to be generated or displayed in the future.

[0183] In this case, similarity is based on vector similarity measurement methods such as cosine similarity, and if it exceeds a set threshold value (e.g., threshold similarity), the message is considered a similar message.

[0184] In the similar representative message filtering step (S230), the message transmission / reception service relay server (100) performs filtering to exclude representative messages or final representative messages that are determined to be similar to the representative message to be filtered through the semantic value similarity comparison step (S220) from the display target.

[0185] Filtered messages are not provided on the artist terminal (200-1), and only other representative messages or final representative messages are provided to the user. This filtering step contributes to increasing the efficiency of the artist's content consumption by reducing exposure to similar or repetitive messages.

[0186] Hereinafter, a representative message display interface will be described in detail with reference to FIGS. 12 to 14.

[0187] FIGS. 12 to 14 are exemplary diagrams of a representative message display interface according to an embodiment of the present invention.

[0188] Referring to FIG. 12, the artist terminal (200-1) is provided with an artist chat screen (1000) that displays messages sent by the artist terminal and messages sent by multiple fans.

[0189] The artist chat screen (1000) includes a UI for the artist to send fan messages in real time and a message composition UI, along with a representative message display interface (1100) for checking representative messages for absent fan messages.

[0190] The representative message display interface (1100) is configured to allow the artist to intuitively check the representative message (final representative message) generated by summarizing and classifying messages received from multiple fans while the artist is absent.

[0191] The representative message display interface (1100) can be implemented in the form of a card or block that is visually partitioned to be distinguished from the general message display area, and multiple representative messages are displayed in a list or slide manner.

[0192] Each representative message displayed on the representative message display interface (1100) may consist of a sentence representing a different group of messages, and may be navigated by scrolling or page switching (e.g., left and right swiping) depending on the number of messages. When an artist selects a specific representative message, an additional interface may be provided to view the original fan messages included in that representative message.

[0193] Additionally, the representative message display interface (1100) may include a title such as "Out of Office Message" for visual emphasis, and each message may be arranged in chronological order or by priority.

[0194] When an artist selects a representative message display interface (1100) using an artist terminal (200-1), a representative message detail display interface (1200) may be displayed as shown in FIG. 13.

[0195] The representative message detail display interface (1200) can display representative messages sorted according to preset criteria. The number of representative messages displayed in the representative message detail display interface (1200) is automatically selected so as not to exceed a preset maximum number, and the priority of the displayed messages can be adjusted according to the size of the message group per representative message (number of fan messages included in the message group), the importance of the message, the artist's settings, and the order of the representative message determination time.

[0196] Additionally, in the representative message detail display interface (1200), the artist can select a representative message to be filtered using an artist terminal.

[0197] When a representative message to be filtered is selected, representative messages with similar meanings are filtered and displayed through the representative message filtering step described above.

[0198] Additionally, when an artist selects a representative message from the representative message detail display interface (1200) using the artist terminal (200-1), the original text of the absent fan message for the selected representative message is displayed.

[0199] At this time, the original text of the absent fan message displays the content of the fan message, the author's nickname, and the time of creation, and the artist can select the fan message to be disciplined or filtered among the fan messages using the artist terminal (200-1).

[0200] Hereinafter, the operation of a processor (140) and a database (130) for generating a private message and transmitting and receiving messages according to an embodiment of the present invention will be described in detail with reference to FIGS. 15 to 25.

[0201] FIG. 15 is a conceptual diagram illustrating the functions of a message transmission and reception service relay server according to an embodiment of the present invention.

[0202] Referring to FIG. 15, the processor (140) may be configured to perform the functions of a control unit (1410) and a message queue unit (not shown) described later. Additionally, the database (130) may be composed of a database per DM (Direct Message) (1310), an individual database (1320), and a sub-database (1330).

[0203] The control unit (1410) performs the function of a controller to store artist messages and fan messages generated from the artist terminal (200-1) and fan terminal (200-2) in the database (130), or to read messages from the database (130) for private chat updates. The message queue unit performs the function of publishing messages to publish artist messages or fan messages stored in the database (130) to recipients.

[0204] The DM-specific database (1310) can store messages by private chat unit or by artist unit. In this case, a private chat unit may refer to a unit of a chat room where messages are sent and received between a fan user and an artist. The individual database (1320) can be constructed to store messages by user unit, with a database corresponding to each user. Accordingly, the first individual database (1321) to the Nth individual database (1321) are formed to correspond to the number of users.

[0205] Additionally, the individual database (1320) may be formed to include an artist sending database (1322) for storing the artist's sending messages and an artist receiving database (1323) for storing messages received by the artist.

[0206] The sub-database (133) may be formed to include a subscription information storage unit (1331) that stores information about fan users following the artist, and a message body storage unit (1332) that stores the content of artist messages and fan messages.

[0207] Below, the interaction between the processor (140) and the database (130) that occurs when providing a private chat service between an artist and a fan is described in detail.

[0208] The processor (140) can receive a fan message generated from a first fan terminal among a plurality of fan terminals (200-2). The processor (140) controls the storage of the fan message in a first individual database corresponding to the first fan terminal among a plurality of individual databases (1320). Additionally, when the fan message is stored in the first individual database, the processor (140) can generate a message feed for the fan message and provide it to the artist terminal (200-1).

[0209] Additionally, the processor (140) can receive an artist message from the artist terminal (200-1). When the processor (140) receives an artist message, it can control the storage of the artist message and artist information in the DM-specific database (1310). When the artist message is stored in the DM-specific database (1310), the processor (140) generates a message feed provided to a plurality of fan terminals and transmits the message feed to the first fan terminal.

[0210] When a first fan terminal requests a private chat update, the processor (140) receives a request for a private chat message update from the first fan terminal. Then, the processor (140) generates a private message corresponding to the first fan terminal based on the fan account information and artist message corresponding to the first fan terminal. The processor (140) transmits the fan message stored in the first database and the generated private message to the first fan terminal. At this time, the private message may refer to a message in which a specific word or keyword of the message is converted according to the recipient. Additionally, the message feed may include notifications, posts, etc., to inform the recipient of the receipt of the message.

[0211] Additionally, when the processor (140) receives an artist message, it can store the artist message in the DM-specific database (1310) and at the same time convert the artist message into a private message and store it in the individual database (1320).

[0212] Specifically, the processor (140) generates multiple private messages corresponding to each of the multiple fan terminals based on fan account information and artist messages corresponding to each of the multiple fan terminals. Then, the processor (140) stores the multiple private messages in corresponding individual databases based on the fan account information. When the private messages are stored in the individual databases, the processor (140) controls the deletion of artist messages stored in the DM-specific database (1310). Additionally, after the private messages are stored in the individual databases, the processor receives private messages from the individual database (1320), rather than the DM-specific database (1310), and transmits them to the fan terminals.

[0213] That is, when an artist composes a message, the message transmission and reception service relay server (100) generates a private message corresponding to each subscriber fan and stores the private message in an individual database assigned to each user. Therefore, when a user requests to view or update a message, the message is retrieved from the individual database, thereby enabling the rapid provision of a private chat service to multiple users.

[0214] Additionally, the processor (140) stores artist messages and artist information in a DM-specific database (1310), and when a preset reference time elapses, deletes the artist messages stored in the DM-specific database (1310), receives private messages from the individual database (1320), and transmits the private messages to the fan terminal.

[0215] At this time, the database (1310) for each DM can be formed based on NoSQL (Not Only SQL), and the individual database (1320) can be formed based on SQL (Structured query language).

[0216] Accordingly, the DM-specific database (1310) has a non-relational database structure and can store unstructured data. Additionally, the individual database (1320) has a relational database structure and can store user-specific message data by creating a DB (Database) table for each user and applying a user-specific DB table filter.

[0217] As the individual database (1320) is configured using SQL, the write speed is slower and the read speed is faster compared to the DM-specific database (1310). On the other hand, the DM-specific database (1310) has a faster write speed and a slower read speed compared to the individual database (1320).

[0218] The message transmission and reception service relay server (100) can increase the speed of providing private chat services to multiple users by providing private messages stored using an individual database (1320). Additionally, while private messages are being stored in the individual database (1320), the operation during the time messages are being stored in the individual database can be supplemented by providing private messages using a DM-specific database (1310).

[0219] Hereinafter, the specific data processing process between the processor (140) and the database (130) will be explained in detail with reference to FIGS. 16 to 20 described later.

[0220] FIG. 16 is a data flow diagram for storing fan messages according to an embodiment of the present invention.

[0221] Referring to FIG. 16, when a fan user composes and transmits a fan message to an artist, the fan message data is transmitted from the fan terminal (200-2) to the control unit (1410) of the message transmission and reception service relay server (100). The fan message data may include at least one of the message content, information about the artist to whom the message is received, and the fan's artist subscription information.

[0222] The control unit (1410) transmits the received fan message data to the message body storage unit (1332) and requests that the fan message data be stored in the message body storage unit (1332). The message body storage unit (1332) stores the fan message data, and when the storage of the fan message data is completed, it generates a fan message ID corresponding to the fan message and responds the fan message ID to the control unit (1410).

[0223] The control unit (1410) that receives the fan message ID requests the storage of fan message data in the individual database (1320). At this time, the individual database (1320) refers to a database allocated per user. Accordingly, when a fan message is received at the first fan terminal, the storage of fan message data is requested in the first individual database (1321) allocated to the first fan terminal. Additionally, the fan message data stored in the individual database (1320) may include the fan message ID and subscription information.

[0224] When fan message data is stored in an individual database (1320), the individual database (1320) sends a response to the control unit (1410) indicating that the fan message data storage is complete.

[0225] The control unit (1410), having received a response from the individual database (1320) confirming the completion of saving fan message data, requests the subscription information storage unit (1331) to look up the fan's subscription information. Specifically, a message queue unit (not shown) included in the control unit (1410) requests the subscription information storage unit (1331) to look up the subscription information based on the fan's subscriber ID information.

[0226] The subscription information storage unit (1331) that receives a request to look up subscription information responds to the control unit (1410) with a Direct Message (DM) ID corresponding to the subscriber ID information. At this time, the DM ID may correspond to the ID of a private chat room or artist information.

[0227] The control unit (1410), having received a DM ID from the subscription information storage unit (1331), requests the storage of fan message data in the artist reception database (1323) of the artist receiving the fan message based on the DM ID. At this time, the fan message data stored in the artist reception database (1323) may include fan message ID and DM ID information.

[0228] When the storage of fan message data in the artist receiving database (1323) is complete, the artist receiving database (1323) responds to a request to publish a fan message to the control unit (1410).

[0229] A control unit (1410) that receives a request to publish a fan message from an artist receiving database (1323) generates a fan feed for an artist to be sent to the artist receiving the fan message, and transmits the fan feed for an artist to the terminal (200) of the artist receiving the fan message.

[0230] Accordingly, when a fan sends a message to an artist, the fan's message is stored in the artist's receiving database. Additionally, if the artist wishes to view fan messages by checking the artist's fan feed, the private chat relay server (100) can read the fan messages based on the fan message data stored in the artist's receiving database and provide them to the artist's terminal.

[0231] Hereinafter, the data processing sequence for storing artist messages will be explained with reference to FIG. 17.

[0232] FIG. 17 is a data flow diagram for storing artist messages according to an embodiment of the present invention.

[0233] Referring to FIG. 17, when an artist user composes and transmits an artist message to be sent to a fan user, artist message data is transmitted from the artist terminal (200-1) to the control unit (1410) of the message transmission and reception service relay server (100). The artist message data may include at least one of message content, message recipient information, and DM ID.

[0234] The control unit (1410) transmits the received artist message data to the message body storage unit (1332) and requests that the fan message data be stored in the message body storage unit (1332). The message body storage unit (1332) stores the artist message data, and when the storage of the artist message data is completed, it generates an artist message ID corresponding to the artist message and responds the artist message ID to the control unit (1410).

[0235] The control unit (1410) that receives the artist message ID requests the storage of artist message data in the artist sending database (1322). At this time, the artist sending database (1322) is an individual database assigned to the artist, and refers to a database where messages written by the artist for sending are stored. Additionally, the artist sending database (1322) may be configured by integrating with the artist receiving database (1323) or configured separately. Furthermore, the artist message data stored in the artist receiving database (1322) may include data regarding one or more of the artist message ID and DM ID.

[0236] When artist message data is stored in the artist receiving database (1322), the artist receiving database (1322) sends a response indicating that the artist message data storage is complete to the control unit (1410).

[0237] The control unit (1410), having received a response from the artist receiving database (1322) indicating completion of saving artist message data, requests the saving of artist message data in the DM-specific database (1310). At this time, the artist message data saved in the DM-specific database (1320) includes data regarding one or more of the artist message ID and DM ID.

[0238] When the artist message data is saved in the DM-specific database (1310), the DM-specific database (1310) sends a response to the control unit (1410) indicating that the artist message data has been saved.

[0239] The control unit (1410), having received a response from the DM-specific database (1310) indicating completion of saving artist message data, requests the subscription information storage unit (1331) to retrieve subscriber list information corresponding to the DM ID. Specifically, a message queue unit (not shown) included in the control unit (1410) requests the subscription information storage unit (1331) for a list of subscriber IDs subscribing to the artist based on the DM ID.

[0240] When the control unit (1410) receives a list of subscriber IDs from the subscription information storage unit (1331), the control unit generates a private message for each subscriber based on the artist message data and the list of subscriber IDs. Additionally, the control unit (1410) requests the storage of the private message corresponding to each subscriber's individual database (1321).

[0241] At this time, requesting storage of a private message in an individual database (1321) may mean that the control unit (1410) stores the content of the private message in the message body storage unit (1332) and requests storage of data for one or more of the private message ID, DM ID, and subscriber ID received in response from the message body storage unit (1332).

[0242] Accordingly, when an artist sends a message to a fan, a private message for each fan is stored in the fan's individual database (1321). Additionally, if a fan wishes to view a message, the private chat relay server (100) can read the private message data stored in the individual database (1321) and provide it to the fan terminal.

[0243] Hereinafter, with reference to FIG. 10, the data processing process for the case where a fan user requests a lookup of a private chat before the private message is stored in an individual database will be described in detail.

[0244] FIG. 18 is a data flow diagram when querying a message of a fan according to an embodiment of the present invention.

[0245] Referring to FIG. 18, when a fan requests to view a private chat or artist message, the control unit (1410) receives a request to view the private chat from the fan terminal (200-2). At this time, the request to view the private chat includes the fan's subscriber ID information.

[0246] When the control unit (1410) receives a private chat lookup request from the fan terminal (200-2), the control unit (1410) requests a message lookup corresponding to the subscriber ID from the individual database (1320) corresponding to the fan terminal (200-2) or the fan account (200-2).

[0247] The individual database (1320) may respond with a list of stored message IDs in response to a message lookup request. At this time, the message that the individual database (1320) responds to the control unit (1410) may include one or more of a fan message ID and a private message ID. However, before the private message is stored in the individual database (1320), the message ID that the individual database (1320) responds to the control unit (1410) includes only a fan message ID.

[0248] Additionally, the control unit (1410) requests the subscription information storage unit (1331) to look up a DM ID corresponding to the fan's subscriber ID. Upon receiving the request to look up a DM ID, the subscription information storage unit (1331) responds to the control unit (1410) with the DM ID stored corresponding to the subscriber ID.

[0249] The control unit (1410) that receives the DM ID requests the DM-specific database (1310) to look up the message corresponding to the DM ID. The DM-specific database (1310) that receives the message lookup request responds to the control unit (1410) with the artist message ID stored corresponding to the DM ID.

[0250] Accordingly, the control unit (1410) receives a fan message ID from an individual database (1320) and receives an artist message ID from a DM-specific database (1310). Then, based on the received fan message ID and artist message ID, the control unit (1410) requests message body information corresponding to the fan message ID and artist message ID from the message body storage unit (1332). Accordingly, the message body storage unit (1332) responds with message information corresponding to the received fan message ID and artist message ID.

[0251] The control unit (1410) can transmit the received fan message and artist message to the fan terminal (200-2). Additionally, the control unit (1410) can convert the artist message into a private message based on the fan's subscription information and transmit it to the fan terminal (200-2).

[0252] Hereinafter, with reference to FIG. 19, the data processing process for the case where a fan user requests to view a private chat after a private message has been stored in an individual database will be described in detail.

[0253] FIG. 19 is a data flow diagram when querying a message of a fan according to an embodiment of the present invention.

[0254] Referring to FIG. 19, when the storage of private messages in individual databases (1320) is completed, the control unit (1410) requests the deletion of completed artist messages in the DM-specific database (1310). A completed artist message refers to an artist message or artist message ID that has been converted into a private message.

[0255] By deleting the artist message ID stored in the DM-specific database (1310), it is possible to prevent duplicate sending of artist messages and private messages to fan terminals.

[0256] After the deletion of the artist message ID from the DM-specific database (1310) is completed, when a fan terminal (200) requests to look up a private chat or artist message, the control unit (1410) receives a request to look up a private chat from the fan terminal (200-2). At this time, the request to look up a private chat includes the fan's subscriber ID information.

[0257] When the control unit (1410) receives a private chat lookup request from the fan terminal (200-2), the control unit (1410) requests a message lookup corresponding to the subscriber ID from the individual database (1320) corresponding to the fan terminal (200-2) or the fan account (200-2).

[0258] The individual database (1320) can respond with a list of stored message IDs in response to a message lookup request. At this time, the message that the individual database (1320) responds to the control unit (1410) may include both fan message IDs and private message IDs.

[0259] Accordingly, the control unit (1410) receives a fan message ID and a private message ID from an individual database (1320). Then, based on the received fan message ID and private message ID, the control unit (1410) requests message body information corresponding to the fan message ID and private message ID from the message body storage unit (1332). Accordingly, the message body storage unit (1332) responds with message information corresponding to the received fan message ID and private message ID.

[0260] The control unit (1410) can transmit the received fan message and private message to the fan terminal (200-2). Therefore, the message transmission and reception service relay server (100) performs only the operation of reading messages from the individual database (1320) corresponding to the fan terminal (200-2), even if multiple fan terminals (200-2) request a lookup of the private chat. Accordingly, a fast processing speed can be maintained even if multiple users request a lookup of messages.

[0261] Hereinafter, with reference to FIG. 20, the data processing process for when an artist requests a lookup of a private chat will be described in detail.

[0262] FIG. 20 is a data flow diagram when an artist views a message according to an embodiment of the present invention.

[0263] Referring to FIG. 20, when an artist requests to view a private chat, the control unit (1410) receives a request to view the private chat from the artist terminal (200-1). At this time, the request to view the private chat includes DM ID information.

[0264] When the control unit (1410) receives a request to look up a private chat from the artist terminal (200-2), the control unit (1410) requests the artist sending database (1322) to look up a message corresponding to the DM ID. Accordingly, the artist sending database (1322) responds with a list of artist message IDs stored corresponding to the artist's DM ID.

[0265] Additionally, the control unit (1410) requests the artist receiving database (1323) to look up messages corresponding to the DM ID. Accordingly, the artist receiving database (1323) responds with a list of stored fan message IDs corresponding to the artist's DM ID.

[0266] Accordingly, the control unit (1410) receives an artist message ID list from the artist sending database (1322) and a fan message ID list from the artist receiving database (1323). Based on the received artist message ID list and fan message ID list, the control unit (1410) requests a message information lookup from the message body storage unit (1332).

[0267] Accordingly, the message body storage unit (1332) responds to the control unit (1410) with message information corresponding to the artist message ID list and the fan message ID list. Upon receiving the artist message and fan message information, the control unit (1410) updates the message content to the artist terminal (200).

[0268] Hereinafter, a method for providing a private chat service will be described in detail with reference to FIGS. 21 to 25.

[0269] FIG. 21 is a flowchart of a fan message storage method according to an embodiment of the present invention.

[0270] Referring to FIG. 21, a method for storing fan messages sent by a fan user to an artist in a private chat service according to an embodiment of the present invention includes a fan message receiving step (S110), a fan message storage step (S120), and a message feed providing step (S130).

[0271] Specifically, in the fan message reception step (S1100), when a fan user composes and transmits a fan message to be sent to an artist, fan message data is transmitted from the fan terminal (200-2) to the control unit (1410) of the message transmission / reception service relay server (100). The fan message data may include at least one of the message content, information about the artist to whom the message is to be received, and the fan's artist subscription information.

[0272] In the fan message storage step (S1200), the control unit (1410) stores the received fan message data in an individual database (1320). Specifically, the control unit (1410) transmits the received fan message data to the message body storage unit (1332) and requests that the fan message data be stored in the message body storage unit (1332). Then, the message body storage unit (1332) stores the fan message data, and when the storage of the fan message data is completed, it generates a fan message ID corresponding to the fan message and responds the fan message ID to the control unit (1410).

[0273] The control unit (1410) that receives the fan message ID requests the storage of fan message data in the individual database (1320). At this time, the individual database (1320) refers to a database allocated per user. Accordingly, when a fan message is received at the first fan terminal, the storage of fan message data is requested in the first individual database (1321) allocated to the first fan terminal. Additionally, the fan message data stored in the individual database (1320) may include the fan message ID and subscription information.

[0274] In the message feed provision step (S1300), the control unit (1410) generates a message feed to be sent to the artist who is the recipient of the fan message and sends it to the artist terminal (200). Specifically, if fan message data is stored in an individual database (1320), the individual database (1320) sends a response to the control unit (1410) indicating that the fan message data storage is complete.

[0275] The control unit (1410), having received a response from the individual database (1320) confirming the completion of saving fan message data, requests the subscription information storage unit (1331) to look up the fan's subscription information. Specifically, a message queue unit (not shown) included in the control unit (1410) requests the subscription information storage unit (1331) to look up the subscription information based on the fan's subscriber ID information.

[0276] The subscription information storage unit (1331) that receives a request to look up subscription information responds to the control unit (1410) with a Direct Message (DM) ID corresponding to the subscriber ID information. At this time, the DM ID may correspond to the ID of a private chat room or artist information.

[0277] The control unit (1410), having received a DM ID from the subscription information storage unit (1331), requests the storage of fan message data in the artist reception database (1323) of the artist receiving the fan message based on the DM ID. At this time, the fan message data stored in the artist reception database (1323) may include fan message ID and DM ID information.

[0278] When the storage of fan message data in the artist receiving database (1323) is complete, the artist receiving database (1323) responds to a request to publish a fan message to the control unit (1410).

[0279] A control unit (1410) that receives a request to publish a fan message from an artist receiving database (1323) generates a fan feed for an artist to be sent to the artist receiving the fan message, and transmits the fan feed for an artist to the terminal (200) of the artist receiving the fan message.

[0280] Accordingly, when a fan sends a message to an artist, the fan's message is stored in the artist's receiving database. Additionally, if the artist wishes to view fan messages by checking the artist's fan feed, the private chat relay server (100) can read the fan messages based on the fan message data stored in the artist's receiving database and provide them to the artist's terminal.

[0281] Hereinafter, a method for storing artist messages will be explained with reference to FIG. 22.

[0282] FIG. 22 is a flowchart of an artist message storage method according to an embodiment of the present invention.

[0283] Referring to FIG. 22, the artist message storage method includes an artist message receiving step (S2100), an artist message storage step in an individual database (S2200), an artist message storage step in a DM-specific database (S2300), a private message creation step (S2400), and a private message storage step (S2500).

[0284] In the artist message reception step (S2100), when an artist user composes and transmits an artist message to a fan user, artist message data is transmitted from the artist terminal (200-1) to the control unit (1410) of the message transmission / reception service relay server (100). The artist message data may include at least one of message content, message recipient information, and DM ID.

[0285] In the step of storing artist messages in individual databases (S2200), the control unit (1410) stores the received artist message data in the artist sending database (1322) among the artist's individual databases (1320).

[0286] Specifically, the control unit (1410) transmits the received artist message data to the message body storage unit (1332) and requests that the fan message data be stored in the message body storage unit (1332). The message body storage unit (1332) stores the artist message data, and when the storage of the artist message data is completed, it generates an artist message ID corresponding to the artist message and responds the artist message ID to the control unit (1410).

[0287] The control unit (1410) that receives the artist message ID requests the storage of artist message data in the artist sending database (1322). At this time, the artist sending database (1322) is an individual database assigned to the artist, and refers to a database where messages written by the artist for sending are stored. Additionally, the artist sending database (1322) may be configured by integrating with the artist receiving database (1323) or configured separately. Furthermore, the artist message data stored in the artist receiving database (1322) may include data regarding one or more of the artist message ID and DM ID.

[0288] When artist message data is stored in the artist receiving database (1322), the artist receiving database (1322) sends a response indicating that the artist message data storage is complete to the control unit (1410).

[0289] In the step of storing artist messages in the DM-specific database (S2300), the control unit (1410) stores the received artist messages in the DM-specific database (1310).

[0290] Specifically, the control unit (1410) requests the storage of artist message data in the DM-specific database (1310). The DM-specific database (1310) stores artist messages or message IDs for each DM ID. At this time, the artist message data stored in the DM-specific database (1320) includes data regarding one or more of the artist message ID and DM ID.

[0291] In the private message generation step (S2400), the control unit (1410) generates a private message to be sent to a fan user who subscribes to the artist based on the received artist message.

[0292] Specifically, the control unit (1410), having received a response from the DM-specific database (1310) indicating completion of saving artist message data, requests the subscription information storage unit (1331) to retrieve subscriber list information corresponding to the DM ID. Specifically, a message queue unit (not shown) included in the control unit (1410) requests the subscription information storage unit (1331) for a list of subscriber IDs subscribing to the artist based on the DM ID.

[0293] When the control unit (1410) receives a list of subscriber IDs from the subscription information storage unit (1331), the control unit generates a private message for each subscriber based on the artist message data and the list of subscriber IDs.

[0294] In the private message storage step (S2500), the control unit (1410) stores the generated private message in the corresponding individual database (1320).

[0295] Specifically, private messages are generated for each fan user who subscribes to the artist. Additionally, an individual database (1321) is assigned to each fan user. Accordingly, the control unit (1410) stores the generated private messages in each fan user's individual database (1321).

[0296] At this time, requesting storage of a private message in an individual database (1321) may mean that the control unit (1410) stores the content of the private message in the message body storage unit (1332) and requests storage of data for one or more of the private message ID, DM ID, and subscriber ID received in response from the message body storage unit (1332).

[0297] Accordingly, when an artist sends a message to a fan, a private message for each fan is stored in the fan's individual database (1321). Additionally, if a fan wishes to view a message, the private chat relay server (100) can read the private message data stored in the individual database (1321) and provide it to the fan terminal.

[0298] Hereinafter, a method for updating private chat for fan users is described with reference to FIGS. 23 and FIGS. 24.

[0299] FIG. 23 is a flowchart of a private chat update method for a fan terminal according to an embodiment of the present invention.

[0300] Referring to FIG. 23, the method for updating a private chat in response to a fan's private chat update and inquiry request includes a step of receiving a private chat update request (S3100), a step of confirming the storage of a private message (S3200), a step of querying an individual database (S3400), a step of querying a database per DM (S3320), and a step of updating the private chat (S3500).

[0301] In the step of receiving a private chat update request (S3100), if a fan requests to view a private chat or artist message, the control unit (1410) receives a private chat view request from the fan terminal (200-2). At this time, the private chat view request includes the fan's subscriber ID information.

[0302] In the private message storage confirmation step (S3200), it is checked whether the private message is being stored in the individual database (1321) or whether storage is complete.

[0303] While private messages are being stored in individual databases (1321), the artist messages are read from the DM-specific database instead of the individual database to update the private chat.

[0304] Specifically, if the private message is not stored in the individual database (1321), the individual database lookup step (S3310), the DM-specific database lookup step (S3320), and the private message creation step (S3330) are performed.

[0305] In the individual database lookup step (S3310), the control unit (1410) requests a message lookup corresponding to the subscriber ID from the individual database (1320) corresponding to the fan terminal (200-2) or fan account (200-2).

[0306] The individual database (1320) may respond with a list of stored message IDs in response to a message lookup request. At this time, the message that the individual database (1320) responds to the control unit (1410) may include one or more of a fan message ID and a private message ID. However, before the private message is stored in the individual database (1320), the message ID that the individual database (1320) responds to the control unit (1410) includes only a fan message ID. Therefore, in the individual database lookup step (S3310), fan message data written by a fan can be received.

[0307] In the DM-specific database lookup step (S3320), the control unit (1410) requests the subscription information storage unit (1331) to look up the DM ID corresponding to the fan's subscriber ID. Upon receiving the DM ID lookup request, the subscription information storage unit (1331) responds to the control unit (1410) with the DM ID stored corresponding to the subscriber ID.

[0308] The control unit (1410) that receives the DM ID requests the DM-specific database (1310) to look up the message corresponding to the DM ID. The DM-specific database (1310) that receives the message lookup request responds to the control unit (1410) with the artist message ID stored corresponding to the DM ID.

[0309] Accordingly, the control unit (1410) receives a fan message ID from an individual database (1320) and receives an artist message ID from a DM-specific database (1310). Then, based on the received fan message ID and artist message ID, the control unit (1410) requests message body information corresponding to the fan message ID and artist message ID from the message body storage unit (1332). Accordingly, the message body storage unit (1332) responds with message information corresponding to the received fan message ID and artist message ID.

[0310] The control unit (1410) can transmit the received fan message and artist message to the fan terminal (200-2).

[0311] Additionally, in the private message generation step (S3330), the control unit (1410) can convert the artist message into a private message based on the fan's subscription information and transmit it to the fan terminal (200-2).

[0312] If the private message is saved in the individual database (1320) in the private message saving confirmation step (S3200), only the individual database lookup step (S3400) is performed to update the fan's private chat.

[0313] In the individual database lookup step (S3400), the control unit (1410) requests the deletion of completed artist messages from the DM-specific database (1310). A completed artist message refers to an artist message converted into a private message or an artist message ID.

[0314] By deleting the artist message ID stored in the DM-specific database (1310), it is possible to prevent duplicate sending of artist messages and private messages to fan terminals.

[0315] After the deletion of the artist message ID from the DM-specific database (1310) is completed, when a fan terminal (200) requests a lookup of a private chat or artist message, in the individual database lookup step (S3400), the control unit (1410) requests a lookup of the message corresponding to the subscriber ID from the individual database (1320) corresponding to the fan terminal (200-2) or fan account.

[0316] The individual database (1320) can respond with a list of stored message IDs in response to a message lookup request. At this time, the message that the individual database (1320) responds to the control unit (1410) may include both fan message IDs and private message IDs.

[0317] Accordingly, the control unit (1410) receives a fan message ID and a private message ID from an individual database (1320). Then, based on the received fan message ID and private message ID, the control unit (1410) requests message body information corresponding to the fan message ID and private message ID from the message body storage unit (1332). Accordingly, the message body storage unit (1332) responds with message information corresponding to the received fan message ID and private message ID.

[0318] In the private chat update step (S3500), the control unit (1410) transmits the received fan message and private message to the fan terminal (200-2) to update the private chat of the fan terminal (200-2).

[0319] Accordingly, the message transmission and reception service relay server (100) performs only the operation of reading messages from the individual database (1320) corresponding to the fan terminal (200-2), even if multiple fan terminals (200-2) request a lookup of private chats. As a result, a fast processing speed can be maintained even if multiple users request a lookup of messages.

[0320] Additionally, the private chat update method of a fan terminal according to an embodiment of the present invention may be applied by changing the private chat storage confirmation step (S3200) to a reference time elapsed confirmation step (S3210).

[0321] In the step of checking for the elapsed reference time (S3210), the control unit (1410) determines that the private message is being stored in the individual database (1321) before the preset reference time has elapsed. Accordingly, if the control unit (1410) receives an artist message and requests an update of the private chat from the fan terminal (200) before the preset reference time has elapsed, it performs the individual database lookup step (S3310), the DM-specific database lookup step (S3320), and the private message creation step (S3330).

[0322] That is, the control unit (1410) retrieves artist message information stored in the DM-specific database (1310) after receiving an artist message and before a preset reference time has elapsed, and generates a private message based on the artist message and provides it to the fan terminal (200).

[0323] Additionally, in the step of checking for the elapsed reference time (S3210), the control unit (1410) determines that the private message has been saved to the individual database (1321) when the preset reference time has elapsed. Accordingly, the control unit (1410) receives the artist message, and after the preset time has elapsed, if the fan terminal (200) requests an update of the private chat, it performs the message reception step (S3400) in the individual database.

[0324] That is, the control unit (1410) provides fan messages and private messages stored in the individual database (1320) to the fan terminal (200) after a preset reference time has elapsed since receiving the artist message.

[0325] Hereinafter, with reference to FIG. 25, a method for updating a private chat when an artist requests a private chat inquiry will be described in detail.

[0326] FIG. 25 is a flowchart of a private chat update method of an artist terminal according to an embodiment of the present invention.

[0327] Referring to FIG. 25, the private chat update method of the artist terminal (200) includes a private chat update request reception step (S4100), an artist sending database lookup step (S4200), an artist receiving database (S4300), and a private chat update step (S4400).

[0328] In the private chat update request reception step (S4100), when an artist requests to view a private chat, the control unit (1410) receives a private chat view request from the artist terminal (200-1). At this time, the private chat view request includes DM ID information.

[0329] In the artist sending database lookup step (S4200), the control unit (1410) requests the artist sending database (1322) to look up messages corresponding to the DM ID. Accordingly, the artist sending database (1322) responds with a list of artist message IDs stored corresponding to the artist's DM ID.

[0330] In the artist receiving database lookup step (S4300), the control unit (1410) requests the artist receiving database (1323) to look up messages corresponding to the DM ID. Accordingly, the artist receiving database (1323) responds with a list of stored fan message IDs corresponding to the artist's DM ID.

[0331] Accordingly, the control unit (1410) receives an artist message ID list from the artist sending database (1322) and a fan message ID list from the artist receiving database (1323). Based on the received artist message ID list and fan message ID list, the control unit (1410) requests a message information lookup from the message body storage unit (1332).

[0332] Accordingly, the message body storage unit (1332) responds to the control unit (1410) with message information corresponding to the artist message ID list and the fan message ID list. Then, in the private chat update step (S4400), the control unit (1410), having received the artist message and fan message information, updates the message content to the artist terminal (200).

[0333] The foregoing description of the present invention is for illustrative purposes only, and those skilled in the art will understand that other specific forms can be easily modified without altering the technical spirit or essential features of the present invention. Therefore, the embodiments described above should be understood as illustrative in all respects and not restrictive. For example, each component described as a single unit may be implemented in a distributed manner, and components described as distributed may likewise be implemented in a combined form.

[0334] The scope of the present invention is defined by the claims set forth below rather than by the detailed description above, and all modifications or variations derived from the meaning and scope of the claims and equivalent concepts thereof should be interpreted as being included within the scope of the present invention.

[0335] The mode for carrying out the invention is the same as the best mode for carrying out the invention described above.

[0336] The present invention has industrial applicability as it is applicable to the entertainment industry and messenger-related industries.

Claims

1. A method for providing message transmission and reception services between an artist terminal and a fan terminal using a message transmission and reception server, wherein A step of receiving multiple fan messages transmitted from a fan terminal to an artist, A step of identifying a missed message received during the period when the artist terminal is not connected among the plurality of fan messages above, The step of generating one or more representative messages for the above absence message, and Step of providing the above representative message to the artist terminal A method for providing a message transmission and reception service including 2. In Paragraph 1, The step of generating the above representative message is, A step of deriving the semantic value of each of the above-mentioned absence messages, A step of classifying the absence message into one or more message groups according to the above semantic value, and Step of generating representative messages for each of the above message groups A method for providing a message transmission and reception service including 3. In Paragraph 2, The step of providing the above representative message to the artist terminal is: A step of setting priorities for each of the above representative messages, A step of providing the representative message to the artist terminal according to the above priority within a preset maximum number of displays A method for providing a message transmission and reception service including 4. In Paragraph 3, The step of providing the above representative message to the artist terminal is: When the above representative message is selected, the step of displaying the original fan messages of the message group included in the selected representative message. A method for providing message transmission and reception services, further including 5. In Paragraph 4, The step of providing the above representative message to the artist terminal is: When the artist terminal selects a representative message to be filtered, a filtering step that excludes subsequent messages having a semantic value similar to the representative message to be filtered from the display target. A method for providing message transmission and reception services, further including 6. In Paragraph 5, The step of extracting the above semantic value is, The method includes the step of inputting the plurality of fan messages into an embedding model to derive the semantic value for each fan message. The step of using at least one of the Clova Embedding V2 model and the Finetuned-BGE-M3 model as the above embedding model A method for providing message transmission and reception services, further including 7. In Paragraph 6, The step of classifying the above plurality of fan messages to generate one or more message groups is, The method includes the step of generating a message group by inputting a plurality of fan messages, the semantic values ​​of which have already been matched, into a clustering model. The above clustering model utilizes the HDBSCAN model. A method for providing message transmission and reception services, further including 8. In Paragraph 7, The step of determining a representative message based on the above message group is, It includes a step of inputting message groups into a summary model to derive representative messages for each message group, The above summary model utilizes at least one of the HyperClova LLM model or the Finetuned-Llama 3.2 model. A method for providing message transmission and reception services, further including 9. In Paragraph 8, The step of providing the above representative message to the artist terminal is: A step of providing a representative message display interface to the artist terminal, The step of displaying the representative message on the representative message display interface, and A step of providing a plurality of fan messages corresponding to a representative message selected by an artist on the representative message display interface above. A method for providing message transmission and reception services, further including 10. A device that provides message transmission and reception services between an artist terminal and a fan terminal using a message transmission and reception server, At least one memory, and It includes at least one processor that performs a message transmission and reception service by executing at least one application stored in the memory, and The instructions of the above processor are, A step of receiving multiple fan messages transmitted from a fan terminal to an artist, A step of identifying a missed message received during the period when the artist terminal is not connected among the plurality of fan messages above, The step of generating one or more representative messages for the above absence message, and Step of providing the above representative message to the artist terminal A computing device including 11. In Paragraph 10, The instructions of the above processor are, A step of deriving the semantic value of each of the above-mentioned absence messages, A step of classifying the absence message into one or more message groups according to the above semantic value, and Step of generating representative messages for each of the above message groups A computing device that further includes 12. In Paragraph 11, The instructions of the above processor are, A step of setting priorities for each of the above representative messages, A step of providing the representative message to the artist terminal according to the above priority within a preset maximum number of displays A computing device that further includes 13. In Paragraph 12, The instructions of the above processor are, When the above representative message is selected, the step of displaying the original fan messages of the message group included in the selected representative message. A computing device that further includes 14. In Paragraph 13, The instructions of the above processor are, When the artist terminal selects a representative message to be filtered, a filtering step that excludes subsequent messages having a semantic value similar to the representative message to be filtered from the display target. A computing device that further includes 15. In Paragraph 14, The instructions of the above processor are, The method includes the step of inputting the plurality of fan messages into an embedding model to derive the semantic value for each fan message. The step of using at least one of the Clova Embedding V2 model and the Finetuned-BGE-M3 model as the above embedding model A computing device that further includes 16. In Paragraph 15, The instructions of the above processor are, The method includes the step of generating a message group by inputting a plurality of fan messages, the semantic values ​​of which have already been matched, into a clustering model. The above clustering model utilizes the HDBSCAN model. A computing device that further includes 17. In Paragraph 16, The instructions of the above processor are, It includes a step of inputting message groups into a summary model to derive representative messages for each message group, The above summary model utilizes at least one of the HyperClova LLM model or the Finetuned-Llama 3.2 model. A computing device that further includes

Images