WO2024112179A1 - Personalized notification message management system and system operation method - Google Patents

Abstract

An embodiment of the present invention relates to a personalized notification management system and a system operation method, and relates to a personalized notification management system and a system operation method, which can increase a personalized notification processing speed for a large number of users by complexly operating an inbox formed using SQL and an outbox formed using NoSQL.

Description

Personalized notification message management system and system operation method

Embodiments of the present invention relate to a personalized notification message management system and system operation method. More specifically, to a personalized notification message management system and system operation method that provide personalized notification messages for each user to a large number of users.

Due to the recent growth of the entertainment industry and the development of IT technology, social network services and fan platforms for communication between celebrities, artists, and fans are increasing. These social network services can be run by fan communities. For example, it can comprehensively provide communication functions with celebrities and artists, live broadcasting, and fan community functions.

In addition, these fan platforms are expanding beyond the functions of existing communities to a wide range of functions, such as selling goods, purchasing, concert and event reservations, providing their own content, and applying non-fungible tokens (NFTs).

As the functionality of the fan platform expands, a variety of notifications and notification messages can be provided to users. For example, if an artist is provided with the ability to directly write posts, postings, messages, videos, etc. and post them to the community, users will immediately receive a push notification when the artist writes a post, comment, etc., or receive membership subscribers. You can receive various benefit notifications for: Additionally, notifications and notification messages with different contents may be provided according to various functions.

In this way, not only are the functions of the fan platform expanding, but as the entertainment market becomes global, the number of artists, communities, and users of the fan platform are also rapidly increasing. In addition, as the range of notifications allowed for each user and settings related to notifications are personalized, there is a problem in that it is difficult to process notification data immediately and quickly as the time spent processing notification messages increases.

The personalized notification management system and system operation method according to an embodiment of the present invention are intended to provide personalized notifications and notification messages for each user in a large-scale service.

Additionally, the personalized notification management system and system operation method according to an embodiment of the present invention are intended to increase the processing speed of personalized notifications.

However, the technical challenge that this embodiment aims to achieve is not limited to the technical challenges described above, and other technical challenges may exist.

As a technical means for achieving the above-described technical problem, the personalized notification message management system according to an embodiment of the present invention includes an InBox unit configured using SQL (Structured query language) and NoSQL (Not Only SQL). An OutBox unit configured using an OutBox unit, and a control unit that requests the creation and storage of notification messages in the Inbox unit and the Outbox unit, and controls the output of notification messages and notification lists from the Inbox unit and the Outbox unit. and wherein, when one or more notification creation request information is input, the control unit requests the inbox unit and the outbox unit to simultaneously generate a notification message corresponding to the notification creation request information, and the inbox unit and the outbox unit simultaneously request creation of a notification message corresponding to the notification creation request information. While switching the output of the outbox unit, a notification list is output.

In addition, the control unit according to an embodiment of the present invention outputs a notification list for each user using the outbox unit while performing an operation of storing the notification list for each user in the inbox unit, and outputs a notification list for each user in the inbox unit. When the operation of saving the notification list for each user is completed, the notification list for each user is output using the inbox unit.

In addition, the notification message according to an embodiment of the present invention includes a personal notification message sent to each user and a community notification message sent to users belonging to a preset community, and the inbox unit is configured to provide the personal notification message. It includes a notification message storage module for generating messages and community notification messages, and a first notification generating module for generating a notification list, and the outbox unit includes a second notification generating module for generating a notification list.

In addition, the inbox unit according to an embodiment of the present invention creates and stores the notification list after configuring a table for each user and applying the user's filtering information, and the outbox unit configures a table for each community information to list the notification list. Create and save.

In addition, the control unit according to an embodiment of the present invention uses the notification list information for each community and the user's filtering information stored in the outbox unit to derive a user to receive a community notification message, and to the user to receive the community notification list. Provides a list of notification messages and notifications.

In addition, the control unit according to an embodiment of the present invention merges the personal notification list generated in the first notification generation module and the community notification list generated in the second notification generation module or removes duplicate notifications to send a notification message to the user. and provides a notification list.

In addition, a method of operating a personalized notification message management system according to an embodiment of the present invention includes an InBox unit configured using SQL (Structured query language), and an OutBox configured using NoSQL (Not Only SQL). ) In the operating method of a personalized notification message management system including a unit and a control unit, when one or more notification creation request information is input, the control unit corresponds to the notification creation request information in the inbox unit and the outbox unit. It includes a step of requesting the creation of a notification message, and a step of the control unit switching output of the inbox unit and the outbox unit, and outputting a notification message and a notification list for each user.

In addition, the step of outputting the notification message and notification list for each user according to an embodiment of the present invention includes the notification list for each user using the out-box unit while performing the operation of storing the notification list for each user in the inbox unit. A step of outputting, and when the operation of storing the notification list for each user in the inbox unit is completed, the step of outputting the notification list for each user using the inbox unit.

In addition, the notification message according to an embodiment of the present invention includes a personal notification message sent to each user and a community notification message sent to users belonging to a preset community, and a step of requesting the creation of the notification message. Generating the notification message and notification list using a first notification generating module included in the inbox unit, and generating the community notification message and notification using a second notification generating module included in the outbox unit. Includes the step of creating a list.

In addition, the step of requesting the creation of a notification message according to an embodiment of the present invention includes the steps of the inbox unit configuring a table for each user, applying the user's filtering information, and then generating and storing the notification message, and the outbox unit. Additional steps include configuring a table for each community to generate and store the notification message.

In addition, the step of outputting a notification message and a notification list for each user according to an embodiment of the present invention involves the control unit receiving a community notification message using the notification list information for each community and the user's filtering information stored in the outbox unit. It further includes deriving target users, and providing a notification message and a notification list for users who are eligible to receive the community notification message.

In addition, the step of outputting a notification message and a notification list for each user according to an embodiment of the present invention includes the control unit providing a personal notification list generated in the first notification generating module and a community notification list generated in the second notification generating module. It further includes providing a notification message and a notification list to the user by merging or removing duplicate notifications.

The personalized notification management system and system operation method according to an embodiment of the present invention can provide personalized notifications and notification messages for each user in a large-scale service.

Additionally, the personalized notification management system and system operation method according to an embodiment of the present invention can increase the processing speed of personalized notifications.

Figure 1 is an exemplary diagram showing a communication connection between a personalized notification management system and a terminal according to an embodiment of the present invention.

Figure 2 is a configuration diagram of a personalized notification management system according to an embodiment of the present invention.

Figure 3 is a configuration diagram of a personalized notification management system according to an embodiment of the present invention.

Figure 4 is a configuration diagram of a terminal according to an embodiment of the present invention.

Figure 5 is a flowchart of a personalized notification management system method according to an embodiment of the present invention.

Figure 6 is a flowchart of a personalized notification management system method according to an embodiment of the present invention.

Figure 7 is a flowchart of a method for generating a notification message according to an embodiment of the present invention.

Figure 8 is a flowchart of a method for outputting a notification message according to an embodiment of the present invention.

Below, with reference to the attached drawings, embodiments of the present invention will be described in detail so that those skilled in the art can easily implement the present invention. However, the present invention may be implemented in many different forms and is not limited to the embodiments described herein. In order to clearly explain the present invention in the drawings, parts unrelated to the description are omitted, and similar parts are given similar reference numerals throughout the specification.

Throughout the specification, when a part is said to be "connected" to another part, this includes not only the case where it is "directly connected," but also the case where it is "electrically connected" with another element in between. . Additionally, when a part "includes" a certain component, this means that it may further include other components rather than excluding other components, unless specifically stated to the contrary.

In addition, the attached drawings are only for easy understanding of the embodiments disclosed in this specification, and the technical idea disclosed in this specification is not limited by the attached drawings, and all changes included in the spirit and technical scope of the present invention are not limited. , should be understood to include equivalents or substitutes.

Terms containing ordinal numbers, such as first, second, etc., may be used to describe various components, but the components are not limited by the terms. The above terms are used only for the purpose of distinguishing one component from another.

When a component is said to be "connected" or "connected" to another component, it is understood that it may be directly connected to or connected to the other component, but that other components may exist in between. It should be. On the other hand, when it is mentioned that a component is “directly connected” or “directly connected” to another component, it should be understood that there are no other components in between.

Singular expressions include plural expressions unless the context clearly dictates otherwise.

In this application, terms such as “comprise” or “have” are intended to designate the presence of features, numbers, steps, operations, components, parts, or combinations thereof described in the specification, but are not intended to indicate the presence of one or more other features. It should be understood that it does not exclude in advance the possibility of the existence or addition of elements, numbers, steps, operations, components, parts, or combinations thereof.

Hereinafter, a personalized notification management system according to an embodiment of the present invention will be described with reference to FIG. 1.

Figure 1 is an exemplary diagram showing a communication connection between a personalized notification management system 100 and a terminal 200 according to an embodiment of the present invention.

Referring to Figure 1, the personalized notification management system 100 is connected to the terminal 200 using a communication network. At this time, the personalized notification management system 100 refers to a system for providing notifications to users who use a fan platform, social network service, etc., and may correspond to a fan platform server, social network service server, etc. The terminal 200 refers to a user's terminal and may refer to a device that displays notifications received from the personalized notification management system 100 to the user.

The personalized notification management system 100 can generate notification messages and notification lists from fan platforms, social network services, etc. and provide them to users. At this time, rather than simply providing a notification to the user, a personalized notification message and notification list can be provided to the user according to filtering information for each user. The specific configuration of the personalized notification management system 100 will be described in detail with reference to FIGS. 2 and 3 described later.

The terminal 200 is a laptop equipped with a web browser, a desktop, a laptop, a wireless communication device that guarantees portability and mobility, or any type of handheld device such as a smartphone, tablet PC, etc. ) may refer to a wireless communication device based on

In addition, the communication network shown in FIG. 1 is a wired network or mobile radio communication network such as a local area network (LAN), a wide area network (WAN), or a value added network (VAN). ) or can be implemented as any type of wireless network, such as a satellite communication network.

Hereinafter, the structure of a personalized notification management system according to an embodiment of the present invention will be described with reference to FIGS. 2 and 3.

Figures 2 and 3 are structural diagrams showing the structure of the personalized notification management system 100 according to an embodiment of the present invention.

Referring to FIG. 2, the personalized notification management system 100 includes a control unit 110, an InBox unit 120, and an OutBox unit 130.

Here, the notification includes a personal notification message sent to each user and a community notification message sent to users belonging to a preset community.

After receiving notification creation request information and a notification message queue (MQ), the control unit 110 controls the inbox unit 120 to create a notification message and write the user's personalized data. Additionally, the control unit 110 controls the creation of notification lists in the inbox unit 120 and the outbox unit 130. The control unit 110 switches the notification list output of the inbox unit 120 and the outbox unit 130, and merges the notification lists generated in the inbox unit 120 and the outbox unit 130 or duplicates the notification list. It performs the function of removing notifications and providing a personalized notification list and notification message (M) to the user.

The inbox unit 120 is built using SQL (Structured query language). The inbox unit 120 creates a DB (DataBase) table for each user, and when notification message creation information is received from the control unit 110, the DB table filter for each user can be applied to store the notification list and notification message for each user. there is.

The outbox unit 130 is built using NoSQL (Not Only SQL). The outbox unit 130 may group users by subscription information and community information and store notification lists and notification messages for each community.

Since the inbox unit 120 is formed using SQL, it can store data using a relational database. On the other hand, since the outbox unit 130 is built using NoSQL, it does not use a relational database and can store unstructured data in a non-relational data store. Accordingly, the outbox unit 130 can store notification lists and notification messages for each community.

Accordingly, the inbox unit 120 has a slower writing speed and a faster reading speed than the outbox unit 130. On the other hand, the out-box unit 130 has a faster writing speed and a slower reading speed than the in-box unit 120. The control unit 110 selectively operates the inbox unit 120 and the outbox unit 130 to perform control so that the inbox unit 120 and the outbox unit 130 perform complementary operations.

While performing a notification storage operation in the inbox unit 120, the control unit 110 outputs a personalized notification message and notification list for each user using the outbox unit 130. Additionally, when the notification message storage operation is completed in the inbox unit 120, the control unit 110 may output a personalized notification message and notification list for each user using the inbox unit 120.

Specifically, when a request for creating (sending) a community notification is input, the control unit 110 not only requests writing a community notification list to the outbox unit 130, but also requests users included in the community to the inbox unit 120. Requests to write a corresponding personal notification list. As described above, the writing speed of the inbox unit 120 is slower than that of the outbox unit 130. Accordingly, when the user requests a notification list while a notification list writing operation is being performed in the inbox unit 120, the notification list is output using the outbox unit 130.

Additionally, because the reading speed of the inbox unit 120 is faster than that of the outbox unit 130, when the notification list writing operation is completed in the inbox unit 120, the outbox unit 130 outputs only an empty notification list and , the inbox unit 120 can output a notification list for each user. Accordingly, the inbox unit 120 and the outbox unit 130 can perform mutual operations to increase the speed of processing personalized notifications.

Figure 3 is a structural diagram showing the structure and data flow of the control unit 110, inbox unit 120, and outbox unit 130.

Referring to FIG. 3, the control unit includes a notification creation control module 111, user filter modules 112 and 113, and a notification inquiry API (Application Programming Interface, 114). The notification creation control module 110 transmits a notification message and a notification list creation request to the inbox unit 120 and the outbox unit 130.

Notification creation request information and notification message queue (MQ) are input to the notification creation control module 111. When notification creation request information and a notification message queue (MQ) are input, the notification creation control module 111 sends a notification message, notification list creation request information, or notification message to the inbox unit 120 and the outbox unit 130. Sends a notification list creation request signal.

At this time, the notification creation control module 111 simultaneously requests the inbox unit 120 and the outbox unit 130 to create a notification message. That is, when notification creation request information and notification message queue (MQ) are input to the notification creation control module 111, the inbox unit 120 generates a personal notification message and notification list, and the outbox unit 130 generates a notification list. You can create a list.

The user filter module 112 receives filtering information for each user from the filter storage module 134 for each user, and transmits the received filtering information for each user to the inbox unit 120 or generates filtering information for each user in the outbox unit 130. Users who are eligible to receive notifications can be derived. The notification inquiry API 114 merges the notification messages and notification lists generated in the inbox unit 120 and the outbox unit 130, removes duplicate notifications, and transmits them to the terminal.

The inbox unit 120 may include a first notification creation module for creating a personal notification list. That is, the inbox unit 120 includes a creation API 121, a sending API 122, an inquiry API 123, a notification message storage module 124, a sending message module 125, and a notification storage module 126 for each user. It may include a creation API (121), a sending API (122), a notification message storage module (124), a sending message module (125), and a notification storage module for each user (126) that may correspond to the first notification generating module. You can. The inbox unit 120 performs a function of creating and providing personal notifications for each user.

Specifically, the creation API 121 performs an interface between the notification creation control module and the notification message storage module 124. The creation API 121 converts the notification message creation request received from the control unit 110 and transmits it to the notification message storage module 124.

The notification message storage module 124 stores the body of the notification message. At this time, the body of the notification message may be set differently depending on the type of notification and the user.

The sending API 122 performs an interface between the user filter module 112 and the sending message module 125. The sending API 122 receives a table for each user from the user filter module 112, converts the received table information for each user, and transmits it to the sending message module 125.

The sending message module 125 serves as an intermediate storage so that notifications for individual users can be sequentially stored in the notification storage module 126 for each user. The notification storage module for each user stores the notification list for each user. At this time, the notification list may include notification ID and reception information.

The inquiry API 123 performs an interface between the notification storage module 126 for each user and the notification inquiry API 114. Therefore, when a user requests notification inquiry, the inquiry API 123 receives and converts the user's notification list information from the notification storage module 126 for each user and transmits it to the notification inquiry API 114.

The outbox unit 130 may include a second notification generation module for generating a community notification message and a notification list. The outbox unit 130 may include a creation API 131, a filter API 132, a query API 133, a filter storage module 134 for each user, and a notification storage module 135 for each community, and a second The notification creation module may correspond to the creation API 131, the filter API 132, and the notification storage module 135 for each community. The outbox unit 130 performs a function of generating and providing notifications for each community.

Specifically, the creation API 131 may perform an interface between the notification creation control module 111 and the notification storage module 135 for each community. The creation API converts the notification message creation request received from the control unit 110 and transmits it to the notification storage module 135 for each community.

When receiving notification creation request information, the notification storage module 135 for each community can create and store a notification list for each community by configuring a table for each community. At this time, the notification list for each community includes notification ID, reception conditions, and reception information.

The filter API 132 performs an interface between the user-specific filter storage module 134 and the user filter modules 112 and 113. The user-specific filter storage module 134 stores various filter setting information set for each user. Accordingly, the filter API 132 receives user-specific filtering information from the user-specific filter storage module 134, converts the received user-specific table information and user-specific filtering information, and transmits them to the user filter modules 112 and 113. .

The inquiry API 133 performs an interface between the notification storage module 135 for each community and the user filter module 113. When notification inquiry request information is received from a user, the inquiry API 133 receives a community notification list from the notification storage module 135 for each community, converts the received community notification list, and transmits it to the user filter module 113. .

The user filter module 113 uses filtering information for each user and the community notification list to derive information on users belonging to the community who are the recipients of community notifications. Accordingly, the user filter module 113 can derive users who are eligible to receive a community notification list and transmit them to the notification inquiry API 114.

The notification inquiry API 114 uses the personal notification list received from the inbox unit 120 and the community notification list received from the outbox unit 130 to merge notification lists for each user or remove duplicate notifications. do. Additionally, an integrated personalized notification list (M) can be transmitted for each user.

Hereinafter, a terminal according to an embodiment of the present invention will be described with reference to FIG. 4.

Figure 4 is a block diagram showing the configuration of the terminal 200.

Referring to FIG. 4 , the terminal 200 includes a memory 220, an input/output module 230, and a processor 240, and may further include a communication module 210.

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 wired or wireless connections with other network devices.

The communication module 210 may transmit and receive information with an external database or external device. Here, the external device may be the personalized notification management system 100 described above. The memory 220 stores a personalized notification management program. The name of the personalized notification management program is set for convenience of explanation, and may include programs that provide fan platforms or social network services, and the name itself does not limit the function of the program. The input/output module 230 may receive information or data transmitted to the terminal 200 from the outside, or output information or data held by the terminal 200 to the outside. For example, the input/output module 230 may include a display, a touch pad, etc. The processor 240 executes a personalized notification management program stored in the memory 220. The memory 120 stores at least one of information and data input to the communication module 110, information and data required for functions performed by the processor 140, and data generated by execution of the processor 140. You can.

Memory 120 should be interpreted as a general term for non-volatile storage devices that continue to retain stored information even when power is not supplied and volatile storage devices that require power to maintain stored information. Additionally, the memory 120 may perform a 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 volatile storage devices that require power to maintain stored information, but the scope of the present invention is not limited thereto. no.

The processor 140 is configured to execute a personalized notification management program stored in the memory 120. The processor 140 may include various types of devices that control and process data. The processor 140 may refer to a data processing device built into hardware that has a physically structured circuit to perform functions expressed by codes or instructions included in a program. In one example, the processor 140 may include a microprocessor, a central processing unit (CPU), a processor core, a multiprocessor, an application-specific integrated circuit (ASIC), or an FPGA ( It may be implemented in the form of a field programmable gate array, etc., but the scope of the present invention is not limited thereto. The processor 240 may display the notification list and notification messages received from the personalized notification management system 100 using the input/output module 230.

Hereinafter, the operation method of the personalized notification management system will be described in detail with reference to FIGS. 5 to 8.

Figure 5 is a flow chart sequentially showing the data processing flow of the personalized notification management system.

Referring to Figure 5, a request to send a personal notification (Notification A) includes reception conditions and recipient user ID information. When a request to send a personal notification (Notification A) is input, it is received by the notification creation control module 111 of the control unit 110. The control unit 110 requests the notification message storage module 124 of the inbox unit 120 to create a personal notification (Notification A) message based on the received personal notification sending request. When the notification message creation is completed in the inbox unit 120, a notification message creation completion signal is transmitted to the control unit 110.

Then, the user filter module 112 requests user filter information from the filter storage module 134 for each user based on the receiving user ID included in the personal notification sending request information, and receives the user ID from the filter storage module 134 for each user. Receive user filtering information corresponding to. The user filter module 112 requests the user-specific notification storage module (user-specific inbox, 126) to write (save) a user-specific notification list using the received user filtering information and the user-specific table. At this time, the notification list for each user includes personal notification (Notification A) ID and receiving user ID information. When the user-specific notification list is stored in the user-specific notification storage module 126, a notification is sent to the user's terminal 200.

A request to send a community notification (Notification B) includes reception conditions and community ID information. When a request to send a community notification (Notification B) is input, it is received by the notification creation control module 111 of the control unit 110. The control unit 110 requests the notification message storage module 124 of the inbox unit 120 to create a community notification (notification B) message based on the received community notification sending request. When the notification message creation is completed in the inbox unit 120, a notification message creation completion signal is transmitted to the control unit 110.

Then, the notification creation control module 111 of the control unit requests the community notification list to be stored (written) in the community-specific notification storage module (community-specific inbox, 135) of the outbox unit 130. At this time, the community notification list includes community notification ID (Notification B ID) and reception condition information.

When the community notification list is stored in the notification storage module 135 for each community, the user filter module 113 receives community user filter information from the filter storage module 134 for each user based on the community ID included in the community notification sending request information. Requests and receives community user filtering information from the user-specific filter storage module 134. The user filter module 113 requests the user-specific notification storage module (user-specific inbox, 126) to write (save) a user-specific notification list using the received user filtering information. At this time, the notification list for each user includes community notification (notification B) ID and community user ID information. Then, after requesting the user-specific notification storage module (user-specific inbox, 126) to write (save) the user-specific notification list, a notification is sent to the user's terminal 200.

If a user requests a notification list while a write operation is performed in the user-specific notification storage module (user-specific inbox, 126) of the inbox unit 120, the notification list is provided to the user using the outbox unit 130. can do.

When a user requests a notification list while a write operation is performed in the user-specific notification storage module (user-specific inbox, 126) of the inbox unit 120, the control unit 110 stores the community-specific notification storage module (community-specific inbox, 135) to request a notification list inquiry.

The notification storage module for each community (inbox for each community, 135) outputs a corresponding community notification list using user ID information and community user ID information. Then, when a community notification list corresponding to a user exists, the control unit 110 requests user filter information from the user-specific filter storage module 134 and receives user filtering information from the user-specific filter storage module 134.

The control unit 110 requests the notification message storage module 124 to query the community notification (Notification B) message using the received user filtering information. Then, the control unit 110 receives community notification (notification B) message information from the notification message storage module 124.

Here, if there is no notification list in the outbox unit 130, the steps of transmitting and receiving user filtering information and querying and responding to a community notification (Notification B) message may be omitted.

After the control unit 110 receives the notification list from the outbox unit 130 or receives community notification (notification B) message information, the control unit 120 stores individual notifications in the user-specific notification storage module (user-specific inbox, 126). Request to view notification list information. When the user-specific notification storage module (user-specific inbox, 126) is requested to view the personal notification list, it performs the personal notification (Notification A) message query and response step to retrieve the user's personal notification list or community notification list and notification messages. Transmitted to the control unit 110.

The notification inquiry API 114 of the control unit 110 uses the notification list received from the inbox unit 120 and the notification list received from the outbox unit 130 to merge notification lists for each user or remove duplicate notifications. Perform the action. And the integrated personalized notification list (M) can be transmitted to the terminal 200 for each user.

At this time, when a notification change (B') request is input to the control unit 110, the control unit 110 requests the notification message storage module 124 to change the notification message, and when the notification message change is completed, the notification change is completed. Print out information.

And, after the notification list writing (saving) operation is completed in the user-specific notification storage module (user-specific inbox, 126) of the inbox unit 120, notifications are sent from the inbox unit 120, not the outbox unit 130. Print the list.

Specifically, when the user requests a notification list after the notification list writing (saving) operation is completed in the user-specific notification storage module (user-specific inbox, 126), the outbox unit 130 sends an empty response to the control unit 110. Output as Instead, the inbox unit 120 may output a notification list and a notification message in response to the user ID information and provide them to the user terminal 200.

Hereinafter, with reference to FIG. 6, the method of operating the personalized notification management system will be described according to the operation flow.

Figure 6 is a flowchart of a method of operating a personalized notification management system.

Referring to FIG. 6, the method of operating the personalized notification management system includes a step of receiving notification creation request information (S100), a step of requesting the creation of a notification message (S200), and a step of outputting a notification message and a notification list for each user (S300).

In the notification creation request information receiving step (S100), notification creation request information is input to the notification creation control module 111 of the control unit 110. As described above, the notification creation request may include a personal notification creation (sending) request, a community notification creation (sending) request, and a notification change request.

In the notification message creation request step (S200), the notification creation control module 111 sends the notification message storage module 124 to one of the following: generating a personal notification (Notification A) message, creating a community notification (Notification B) message, or requesting a change to the notification message. Control to perform the above.

In the user-specific notification message and notification list output step (S300), the control unit 110 controls storage of the notification list in the inbox unit 120 and the outbox unit 130, and the inbox unit 120 and the outbox unit 130 While switching the output of the notification list at 130, notification messages and notification lists for each user are provided to the user terminal 200.

Hereinafter, the notification list creation method will be described in detail with reference to FIG. 7.

Figure 7 is a flowchart of a method for generating a notification list according to an embodiment of the present invention.

Referring to Figure 7, the notification list creation method includes a notification message creation step (S210), a user-specific filtering step (S220), a personal notification list creation and storage step (S221), a community-specific notification list creation and storage step (S230), It includes a community user filtering step (S231) and a notification list transmission step (S240).

In the notification message creation step 210, the notification creation control module 111 sends the notification message storage module 124 to one of the following: creating a personal notification (Notification A) message, creating a community notification (Notification B) message, or requesting a change to the notification message. Create and store a notification message in response. The stored notification message may be provided to the user terminal 200 in response to the notification list for each user.

In the user-specific filtering step (S220), which is a preprocessing step for generating a personal notification list, the inbox unit 120 creates and stores a notification list for each personal notification target user.

Specifically, in the user-specific filtering step (S220), the user filter module 112 requests user filter information from the user-specific filter storage module 134 based on the receiving user ID included in the personal notification sending request information, and user User filtering information corresponding to the user ID is received from the star filter storage module 134. Then, the user filter module 112 requests the user-specific notification storage module (user-specific inbox, 126) to write (save) a user-specific notification list using the received user filtering information and the user-specific table.

In the personal notification list creation and storage step (S221), the user-specific filter storage module 134 creates and stores a user-specific notification list. At this time, the notification list for each user includes personal notification (Notification A) ID and receiving user ID information. When the user-specific notification list has been stored in the user-specific notification storage module 126, the notification list can be transmitted to the control unit 110.

In the step of generating and storing notification lists for each community (S230), a community notification list is created and stored using the outbox unit 130.

Specifically, the notification creation control module 111 of the control unit requests to store (write) the community notification list in the notification storage module for each community (inbox for each community, 135) of the outbox unit 130. At this time, the community notification list includes community notification ID (Notification B ID) and reception condition information. Additionally, the notification storage module 135 for each community creates and stores a notification list for each community based on the community notification creation (request) information.

In the community user filtering step (S231), when the community notification list has been stored in the notification storage module 135 for each community, the user filter module 113 stores a filter for each user based on the community ID included in the community notification sending request information. Request community user filter information from module 134. Then, the user filter module 113 receives community user filtering information from the user-specific filter storage module 134. The user filter module 113 may create a community notification list for each user using the received user filtering information.

In the notification list transmission step (S240), the notification inquiry API 114 merges the notification list for each user using the personal notification list received from the inbox unit 120 and the community notification list received from the outbox unit 130. Or perform an action to remove duplicate notifications. Additionally, an integrated personalized notification list (M) can be transmitted for each user.

Hereinafter, a method for outputting notification messages and notification lists for each user will be described in detail with reference to FIG. 8.

Figure 8 is a flowchart showing a method for outputting a notification list according to an embodiment of the present invention.

Referring to FIG. 8, the notification list output method includes a step of outputting a notification list for each user in the outbox unit 130 (S310), a step of determining whether the notification list saving operation of the inbox unit 120 is completed (S320), and an inbox unit 120. In unit 120, a notification list output step for each user is included (S330).

In the step (S310) of outputting a notification list for each user in the outbox unit 130, if the user requests a notification list while a write operation is performed in the notification storage module 126 for each user in the inbox unit 120, A notification list is provided to the user using the box unit 130.

Specifically, when the user requests a notification list while a writing operation is performed in the inbox unit 120, the control unit 110 responds by requesting a notification list inquiry from the notification storage module for each community (inbox for each community, 135). A notification list and notification messages for each user according to the results are provided to the user terminal 200.

In the determination step (S320) of whether the notification list saving operation of the inbox unit 120 has been completed, it is determined whether a saving (writing) operation is being performed in the notification storage module 126 for each user. If the storage (write) operation is not completed in the notification storage module 126 for each user, it is fed back to the notification list output step for each user (S310). When the storage (write) operation is completed in the user-specific notification storage module 126, the inbox unit 120 performs the user-specific notification list output step (S330).

In the step S330 of outputting a notification list for each user in the inbox unit 120, the outbox unit 130 outputs an empty notification list, and the inbox unit 120 outputs a personal notification list and a community notification list.

Specifically, when the user requests a notification list after the notification list writing (saving) operation is completed in the user-specific notification storage module (user-specific inbox, 126), the outbox unit 130 sends an empty response to the control unit 110. Output as Instead, the inbox unit 120 may output a personal notification list, a community notification list, and a notification message in response to the user ID information and provide them to the user terminal 200.

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

The scope of the present invention is indicated by the claims described below rather than the detailed description above, and all changes or modified forms derived from the meaning and scope of the claims and their equivalent concepts should be construed as being included in the scope of the present invention. do.

The form for carrying out the invention is the same as the best form for carrying out the invention described above.

The present invention relates to a personalized notification management system and system operation method, and can be used in the entertainment industry and messenger-related industries, so it has industrial applicability.

Claims (12)

1. In the personalized notification message management system,

   InBox part constructed using SQL (Structured query language),

   An OutBox part constructed using NoSQL (Not Only SQL), and

   A control unit that requests the creation and storage of notification messages in the inbox unit and the outbox unit, and controls output of notification messages and notification lists of the inbox unit and the outbox unit.

   Includes,

   The control unit,

   When one or more notification creation request information is input, requesting the creation of a notification message corresponding to the notification creation request information simultaneously in the inbox unit and the outbox unit,

   A personalized notification message management system that outputs a notification list while switching the output of the inbox unit and the outbox unit.
2. According to paragraph 1,

   The control unit,

   While the inbox unit is performing the operation of storing the notification list for each user, the notification list for each user is output using the outbox unit, and when the operation of storing the notification list for each user is completed in the inbox unit, the inbox unit is used to store the notification list for each user. A personalized notification message management system that outputs a notification list for each user using wealth.
3. According to paragraph 2,

   The notification message is,

   It includes a personal notification message sent to each user and a community notification message sent to users belonging to a preset community,

   The inbox section,

   It includes a notification message storage module for generating the personal notification message and the community notification message, and a first notification generation module for generating the notification list,

   The outer box part,

   A personalized notification message management system, comprising a second notification creation module for generating a notification list.
4. According to paragraph 3,

   The inbox section,

   Create a table for each user, apply the user's filtering information, and then create and save the notification list.

   A personalized notification message management system in which the outbox unit creates and stores the notification list by configuring a table for each community information.
5. According to clause 4,

   The control unit,

   A personalized notification that derives users who are eligible to receive community notification messages using the community-specific notification list information and user filtering information stored in the outbox unit, and provides notification messages and notification lists for users who are eligible to receive the community notification list. Message management system.
6. According to clause 5,

   The control unit,

   A personalized notification message management system that provides notification messages and notification lists to users by merging the personal notification list generated in the first notification creation module and the community notification list generated in the second notification creation module or removing duplicate notifications. .
7. In a method of operating a personalized notification message management system including an InBox unit configured using SQL (Structured query language), an OutBox unit configured using NoSQL (Not Only SQL), and a control unit ,

   When one or more notification creation request information is input, the control unit requests the inbox unit and the outbox unit to generate a notification message corresponding to the notification creation request information, and

   The control unit switching the output of the inbox unit and the outbox unit while outputting a notification message and a notification list for each user.

   A method of operating a personalized notification message management system, including.
8. In clause 7,

   The step of outputting notification messages and notification lists for each user is,

   While performing the operation of storing the notification list for each user in the inbox unit, outputting a notification list for each user using the outbox unit, and

   When the operation of storing the notification list for each user in the inbox unit is completed, outputting the notification list for each user using the inbox unit.

   A method of operating a personalized notification message management system further comprising:
9. According to clause 8,

   The notification message includes a personal notification message sent to each user and a community notification message sent to users belonging to a preset community,

   The step of requesting the creation of the notification message is,

   Generating the notification message and notification list using a first notification creation module included in the inbox unit, and

   Generating the community notification message and notification list using the second notification generation module included in the outbox unit.

   A method of operating a personalized notification message management system, including.
10. According to clause 9,

    The step of requesting the creation of the notification message is,

    The inbox unit configures a table for each user, applies the user's filtering information, and then generates and stores the notification message, and

    Step of the Outbox unit creating and storing the notification message by configuring a table for each community.

    A method of operating a personalized notification message management system further comprising:
11. According to clause 10,

    The step of outputting notification messages and notification lists for each user is,

    The control unit deriving a target user for receiving a community notification message using notification list information for each community and user filtering information stored in the outbox unit, and

    Providing a notification message and notification list for users who are eligible to receive the community notification message.

    A method of operating a personalized notification message management system further comprising:
12. According to clause 11,

    The step of outputting notification messages and notification lists for each user is,

    The control unit merging the personal notification list generated in the first notification generation module and the community notification list generated in the second notification generation module or removing duplicate notifications to provide a notification message and a notification list to the user.

    A method of operating a personalized notification message management system further comprising:

Images