TWI877747B - Method and electronic device for managing data related to service and non-transitory computer-readable recording medium - Google Patents

Abstract

The present invention discloses a method for managing service-related data by an electronic device. Specifically, the method for managing service-related data may include the following steps: identifying the first event data corresponding to the event occurring on the service within the first period unit; based on the first event data, storing the first type of data in the first table; generating the second type of data based on the first data corresponding to the second period unit in the first type of data stored in the first table; and storing the second type of data in the second table.

Description

Methods and electronic devices for managing service-related data and non-transitory computer-readable recording media

The embodiments of this specification are related to a method and an electronic device for managing data related to a service. More specifically, the embodiments of this specification are related to a method and an electronic device for merging and managing event data occurring on a service within a period unit.

Various real-time data is generated in response to the user's actions on the service. Especially with the popularization of Internet use, various real-time data generated based on the user's actions on various services on the Internet are increasing rapidly.

The present invention is proposed to solve the above-mentioned problems and aims to provide a method and an electronic device for managing service-related data. More specifically, the present invention aims to provide a method and an electronic device for managing service-related data by merging and storing in layers the event data that occurred on the service within a plurality of time units. The technical issues to be solved by this embodiment are not limited to the above-mentioned technical issues, and other technical issues can be inferred from the following embodiments.

As a technical method for realizing the above-mentioned subject, the method for managing service-related data of the first aspect of the present invention is performed by an electronic device, which may include the following steps: identifying the first event data corresponding to the event occurring on the service within the first period unit; based on the first event data, storing the first type of data in the first table; generating the second type of data based on the first data corresponding to the second period unit among the first type of data stored in the first table; and storing the second type of data in the second table.

According to one embodiment, the first event data may include information of at least one metric included in the set metric set, and the set metric set may include a first sub-metric set and a second sub-metric set.

According to one embodiment, when the first sub-event data included in the first event data corresponds to the first metric included in the first sub-metric set, the value of the first type of data is determined to be the first value obtained by accumulating the values of each of the first sub-event data, and when the second sub-data included in the first data corresponds to the first metric, the value of the second type of data is determined to be the second value obtained by accumulating the values of each of the second sub-data.

According to an embodiment, when the first sub-event data included in the first event data corresponds to the second metric included in the second sub-metric set, the first type of data can be determined based on the value of each of the first sub-event data and the event occurrence time of each of the first sub-event data, and when the second sub-data included in the first data corresponds to the second metric, the second type of data can be determined based on the value of each of the second sub-data and the event occurrence time of each of the second sub-data.

According to one embodiment, the data of the second type may include data of a plurality of levels corresponding to a plurality of period units, and the plurality of period units may be determined based on the metrics corresponding to each of the data of the second type.

According to one embodiment, the plurality of period units include the third period unit and the fourth period unit, and the method for managing service-related data further includes the following steps: when the third period unit is a period unit shorter than the fourth period unit and is a period unit adjacent to the fourth period unit among the plurality of period units, identifying the first-level data corresponding to the third period unit in the second type of data stored in the second table; and generating the second-level data corresponding to the fourth period unit based on the first-level data.

According to one embodiment, the method for managing service-related data may further include the following steps: obtaining a query from a terminal; identifying the second data corresponding to the query in the data of the second type stored in the second table; identifying the third data corresponding to the query in the data of the first type stored in the first table; generating response data corresponding to the query based on the second data and the third data; and transmitting information of the response data to the terminal.

According to one embodiment, the step of generating response data may include the following steps: comparing the event occurrence time corresponding to the second data with the event occurrence time corresponding to the third data, identifying the fourth data that is repeated with the second data in the third data; filtering the fourth data in the third data to identify the fifth data; and generating response data based on the second data and the fifth data.

According to one embodiment, when the data of the second type includes data of multiple levels corresponding to multiple period units, the step of identifying the second data may include the following steps: identifying at least one period unit corresponding to the query among the multiple period units; and identifying the second data based on the data of at least one period unit in the data of the second type stored in the second table.

According to one embodiment, the step of generating data of the second type may include the following steps: when the sixth data as data of the first type is newly stored in the first table, the seventh data as data of the second type is generated based on the first data and the sixth data.

According to one embodiment, when a set period of time has passed since the 7th data was stored in the 2nd table, or when the validity of the 6th data is false (False), the 6th data can be deleted from the 1st table.

According to one embodiment, when a set period of time has passed since the data of the second level was stored in the second table, the data of the first level can be deleted from the second table.

According to one embodiment, the first event data may include at least one of the user identification information of the service or the item identification information of the service.

According to one embodiment, each data stored in the second table may include identification information for identifying a corresponding event, and a method for managing data related to a service may include the following steps: identifying second event data corresponding to a second event occurring on a service, and second identification information corresponding to the second event; based on the second identification information, identifying eighth data in the data stored in the second table, the eighth data being the identification information corresponding to the second identification information; modifying the eighth data based on the second event data; and storing the modified eighth data in the second table.

According to one embodiment, the set period may correspond to the cancelable period of the third event corresponding to the sixth data.

The electronic device for managing service-related data of the second aspect of the present invention may include a transceiver; one or more processors; and a memory storing one or more commands executed by one or more processors. The one or more processors may identify the first event data corresponding to the event occurring on the service within the first period unit by executing one or more commands, store the first type of data in the first table based on the first event data, generate the second type of data based on the first data corresponding to the second period unit among the first type of data stored in the first table, and store the second type of data in the second table.

The recording medium of the third aspect of the present invention may be a non-temporary computer-readable recording medium that records a program for executing a method for electronic device management and service-related data in a computer.

According to the embodiments of this specification, the electronic device can effectively manage service-related data by combining event data that occurs on the service within multiple time units and storing them in layers.

The effects of the invention are not limited to the effects mentioned above. People with common sense in the technical field to which the invention belongs can clearly understand other effects not mentioned based on the description of the scope of the patent application.

10: System

100: Electronic devices

101: Transceiver

102: Storage

103: Processor

120:Terminal

301: Data of the first event

310:Source

311: Data workflow

320: Table 1

330: Table 2

401: Event data 1

410: Table 1

421: 1st subtable

422: Second subtable

600: Table 1

610: Table 2

800: Page

810: Area 1

820: Area 2

830: Area 5

841: Area 3

842: Area 4

900: Page

910: Area

S210: Step

S220: Step

S230: Step

S240: Step

S510: Step

S520: Step

S530: Step

S540: Steps

S550: Steps

S710: Step

S720: Step

S730: Step

S740: Steps

FIG. 1 is a diagram of a system for illustrating various embodiments of a method for implementing electronic device management and service-related data.

FIG2 is a flow chart showing a method for managing service-related data of an electronic device.

FIG3 is a diagram for explaining a method of storing data of the first type and data of the second type in the first table and the second table when the first event data corresponds to the first metric included in the first sub-metric set.

FIG. 4 is a diagram for explaining a method of storing data of the first type and data of the second type in the first table and the second table when the first event data corresponds to the second metric included in the second sub-metric set.

FIG5 is a flow chart showing a method for transmitting information of response data corresponding to a query obtained from a terminal.

FIG. 6 is a diagram for explaining a method in which an electronic device provides information of response data corresponding to a query when performing a query operation during a merge operation.

FIG7 is a flow chart showing a method for modifying data stored in a table.

FIG8 is a diagram for illustrating a page for setting event data and metrics to be summarized in one embodiment.

FIG. 9 is a diagram for illustrating a page displaying summary data in an embodiment.

FIG. 10 is a block diagram showing an electronic device for managing service-related data according to an embodiment.

The terms used in the embodiments are currently widely used general terms selected as much as possible while considering the functions of the invention, but they may also be different according to the intentions of technical personnel in this field or precedents, the emergence of new technologies, etc. In addition, in certain cases, there are also terms arbitrarily selected by the applicant. In this case, their meanings will be detailed in the corresponding description section. Therefore, the terms used in the invention should be defined based on the meaning of the terms and the overall content of the invention, rather than simply based on the names of the terms.

When a component is mentioned in the entire manual as "including" another component, it means that other components are not excluded unless otherwise stated, but other components may be further included. In addition, the terms "...part", "...module" and the like stated in the manual indicate a unit that processes at least one function or operation, which can be implemented by hardware or software, or by a combination of hardware and software.

The expression "at least one of a, b and c" recorded in the entire manual may include "a alone", "b alone", "c alone", "a and b", "a and c", "b and c", or "a, b, c".

The "terminal" mentioned below can be implemented by a computer or a portable terminal, and the computer or portable terminal can be connected to a server or other terminals via a network. Here, computers include, for example, notebook computers, desktop computers, laptop computers, etc. equipped with web browsers. Portable terminals are wireless communication devices that ensure portability and mobility, such as IMT (International Mobile Telecommunication), CDMA (Code Division Multiple Access), W-CDMA (W-Code Division Multiple Access), LTE (Long Term Evolution), and all types of handheld wireless communication devices such as smartphones and tablet computers.

The following is a detailed description of the embodiments of the present invention with reference to the attached drawings, so that those with common sense in the technical field to which the present invention belongs can easily implement it. However, the present invention can be implemented in many different forms and is not limited to the embodiments shown in this article.

When describing the embodiments, the description of the technical contents that are well known in the technical field to which the present invention belongs and are not directly related to the present invention will be omitted. The reason is: by omitting redundant descriptions, the main idea of the present invention can be clearly conveyed to avoid confusion of the main idea of the present invention.

For the same reason, some components are exaggerated, omitted or roughly represented in the attached drawings. In addition, the size of each component does not fully reflect the actual size. In each figure, the same or corresponding components are given the same figure mark.

By referring to the embodiments described in detail below in conjunction with the attached drawings, the advantages and features of the present invention and the methods for realizing the same will become clear. However, the present invention is not limited to the embodiments disclosed below and can be implemented in various forms. The embodiments are provided only to make the disclosure of the present invention more complete and to enable technicians in the technical field to which the present invention belongs to fully understand the technical field to which the present invention belongs. The present invention is limited only by the scope of the patent application. Throughout the specification, the same reference symbols refer to the same constituent elements.

At this point, it should be understood that the blocks of the processing flow chart and the combination of the flow chart can be implemented by computer program instructions. Such computer program instructions can be loaded on a processor of a general-purpose computer, a special-purpose computer or other programmable data processing device, so that such instructions executed by the processor of the computer or other programmable data processing device will produce a method for implementing the functions described in the blocks of the flow chart. In order to implement the functions in a specific manner, such computer program instructions can be stored in a computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing device, and the instructions stored in the computer-usable or computer-readable memory can produce a manufactured item containing the following instruction method, which implements the functions described in the blocks of the flow chart. Computer program instructions may also be loaded onto a computer or other programmable data processing device, thereby executing a series of action steps on the computer or other programmable data processing device to generate a process executed by the computer, and the instructions executed by the computer or other programmable data processing device may also provide steps for executing the functions described in the blocks of the flowchart.

Furthermore, each block may represent a module, a fragment, or a portion of code that includes one or more executable instructions for executing a specific logical function. It should also be noted that in some alternative embodiments, the functions mentioned in the blocks may not be generated in sequence. For example, two blocks represented in succession may actually be executed at the same time, or may occasionally be executed in the opposite order according to the corresponding functions.

The following is a detailed description of the embodiments of the present invention with reference to the attached drawings.

FIG. 1 is a diagram of a system for illustrating various embodiments of a method for implementing electronic device management and service-related data.

Referring to FIG. 1 , the system 10 of various embodiments can be implemented by various types of devices. For example, the system 10 may include an electronic device 100 and a terminal 120. The system 10 shown in FIG. 1 only shows the components related to the present embodiment. Therefore, those who have common sense in the relevant technical field of the present embodiment can understand that in addition to the components shown in FIG. 1 , other general components may be further included.

Each of the electronic device 100 and the terminal 120 may include a transceiver, a memory, and a processor. In addition, each of the electronic device 100 and the terminal 120 may refer to a unit that processes at least one function or action, which may be implemented by hardware or software, or a combination of hardware and software. On the other hand, throughout the embodiment, the electronic device 100 and the terminal 120 are each referred to as a separate device or server, but they may be logically separate structures, at least a portion of which may be implemented by functions separated from one device or server.

According to one embodiment, the electronic device 100 and the terminal 120 may include a plurality of computer systems or computer software implemented by a network server. For example, at least a portion of the electronic device 100 and the terminal 120 may refer to a computer system and computer software that is connected to a lower device to receive an operation execution request, execute the operation execution request and provide an execution result. The lower device may communicate with other network servers via a computer network such as an intranet or the Internet. In addition, at least a portion of the electronic device 100 and the terminal 120 may be understood as a broad concept, including a series of applications that can be operated on a network server, and various databases constructed on internal or other connected nodes. For example, at least a portion of the electronic device 100 and the terminal 120 can be implemented using various network server programs provided by operating systems such as DOS, Windows, Linux, UNIX, or Macintosh.

The electronic device 100 and the terminal 120 can communicate with each other via a network (not shown). The network includes a local area network (LAN), a wide area network (WAN), a value-added network (VAN), a mobile radio communication network, a satellite communication network, and combinations thereof, and the network is a comprehensive data communication network that enables the network components shown in FIG. 1 to communicate with each other smoothly, and may include a wired Internet, a wireless Internet, and a mobile wireless communication network. Wireless communication may include, for example, Wi-Fi, Bluetooth, Bluetooth low energy, Zigbee, WFD (Wi-Fi Direct), UWB (ultra wideband), infrared communication (IrDA), NFC (Near Field Communication), etc., but is not limited thereto.

Various real-time data may be generated in response to the user's actions on the service. For example, when the user purchases an item, real-time data corresponding to the user's item purchase event may be generated. In this article, event data may be data stored in a message queue in response to an event occurring on the service. As an embodiment, event data may be log data corresponding to the user's actions on the service, but is not limited thereto. Event data is data stored in a message queue, which may be distinguished from data stored in the first table or the second table in the memory of the electronic device 100. In this regard, the message queue may store event data generated in response to events occurring on the service in the order in which they are generated.

The electronic device 100 can combine and store the event data occurring on the service in multiple time units in layers. The electronic device 100 can store the data of the first type corresponding to the first time unit in the first table, and store the data of the second type corresponding to the second time unit in the second table.

As an embodiment, the electronic device 100 can identify the first event data corresponding to the event occurring on the service within the first period unit of a relatively short period from among the event data accumulated in the message queue. The electronic device 100 can store the first type of data in the first table based on the first event data. More specifically, the electronic device 100 can generate the first type of data by merging the first event data. Here, the first period unit can be the shortest period unit among the period units set in the electronic device 100. The first period unit can be 10 seconds, but is not limited thereto. The first type of data is data representing the value of the data within the integrated shorter period unit, i.e., the first period unit, and can be referred to as non-aggregation data. Data of the first type may be stored in the first table in the memory of the electronic device 100.

As another embodiment, the electronic device 100 may generate data of the second type based on the first data corresponding to the second period unit in the data of the first type stored in the first table. More specifically, the electronic device 100 may generate data of the second type by merging data corresponding to events occurring on the service within the second period unit in the data of the first type stored in the first table. Here, the second period unit may be a period unit longer than the first period unit. For example, the second period unit may be 1 hour, but is not limited thereto. The data of the second type may be data representing the value of the data of the first type integrated within the second period unit. Here, the data of the second type is data generated by integrating a part of the data of the first type stored in the first table, and can be called integrated data. The electronic device 100 can store the data of the second type in the second table. The second table can be a separate table different from the first table in the memory.

FIG2 is a flow chart showing a method for managing service-related data of an electronic device.

Referring to Figure 2, it can be clearly understood that each action of electronic device management and service-related data can be changed or replaced within the scope of the common sense in the technical field to which the present invention belongs, or some orders between actions can be changed.

In step S210, the electronic device 100 can identify the first event data corresponding to the event occurring on the service within the first period unit.

When an event occurs in real time on a service, the electronic device 100 can determine whether the event data corresponding to the event that occurs includes information about the metrics included in the set metric set. When the event data includes information about the metrics included in the set metric set, the electronic device 100 can perform an action of identifying the first event data. The electronic device 100 can identify the first event data corresponding to the event that occurs on the service within the set first period unit from the data stored in the message queue.

In step S220, the electronic device 100 can store the data of the first type in the first table based on the first event data.

According to one embodiment, the electronic device 100 may integrate the first event data identified in step S210 to generate data of the first type, and store the generated data of the first type in the first table. The first event data may include information of at least one metric included in the set metric set. The set metric set may include a first sub-metric set and a second sub-metric set.

As an example, when the first sub-event data included in the first event data corresponds to the first metric included in the first sub-metric set, the value of the first type of data can be determined as the first value accumulated from the values of each of the first sub-event data. For example, the value of the first type of data corresponding to the number of orders of a user can be determined as the sum of the number of orders of the user that occurred on the service during the first period.

As another embodiment, when the first sub-event data included in the first event data corresponds to the second metric included in the second sub-metric set, the first type of data can be determined based on the value of each of the first sub-event data and the event occurrence time of each of the first sub-event data. For example, the value of the first type of data corresponding to the user's latest order date (order last date) can be the value of the event data corresponding to the date of the order with the latest event occurrence time (i.e., order date) among the user's orders that occurred on the service during the first period. In addition, the event occurrence time of the first type of data corresponding to the user's latest order date (order last date) can be determined as the date of the order with the latest event occurrence time (i.e., order date) among the user's orders that occurred on the service during the first period.

In step S230, the electronic device 100 can generate data of the second type based on the first data corresponding to the second period unit in the data of the first type stored in the first table.

In step S240, the electronic device 100 may store the second type of data in the second table.

Here, the first data may be data corresponding to an event occurring in the second period unit among the data of the first type stored in the first table. According to one embodiment, the electronic device 100 may generate data of the second type by integrating the first data. Furthermore, the generated data of the second type may be stored in a second table different from the first table.

As an example, when the second sub-data included in the first data corresponds to the first metric, the value of the second type of data can be determined as the second value obtained by accumulating the values of each of the second sub-data. For example, the value of the second type of data corresponding to the number of orders of a user can be determined as the sum of the number of orders of each of the first type of data included in the second period unit.

As another embodiment, when the second sub-data included in the first data corresponds to the second metric, the second type of data can be determined based on the value of each of the second sub-data and the time of occurrence of each of the second sub-data. For example, the value of the second type of data corresponding to the user's latest order date (order last date) can be the value of the event data corresponding to the date of the order with the latest event time (i.e., order date) among the user's orders that occurred on the service during the second period. In addition, the time of occurrence of the event of the second type of data corresponding to the user's latest order date (order last date) can be determined as the date of the order with the latest event time (i.e., order date) among the user's orders that occurred on the service during the second period.

That is, the data of the first type generated based on the first event data corresponding to the event occurring in the first period unit can be stored in the first table, and the first period unit is a relatively short period unit. On the contrary, the data of the second type generated based on the first data corresponding to the second period unit can be stored in the second table, and the second period unit is a longer period unit than the first period unit in the data of the first type stored in the first table. That is, the event data stored in the message queue can be stored in at least one of the first table and the second table in a hierarchical manner according to a plurality of period units, rather than being stored separately in the memory of the electronic device 100.

Furthermore, data of a plurality of levels corresponding to a plurality of period units other than the second period unit may be stored in the second table. For example, the plurality of period units may include a third period unit and a fourth period unit, and the third period unit may be a period unit shorter than the fourth period unit and adjacent to the fourth period unit in the plurality of period units. At this time, the electronic device 100 may identify data of the first level corresponding to the third period unit from the data of the second type stored in the second table, and generate data of the second level corresponding to the fourth period unit based on the data of the first level. As an embodiment, the plurality of period units may include 1 day, 1 week, 1 month, 1 quarter, and 6 months, and the second period unit may be 1 day. At this time, the upper level data corresponding to a week can be generated based on the lower level data corresponding to the day. In addition, the upper level data corresponding to a month can be generated based on the lower level data corresponding to a week and the lower level data corresponding to the day. The upper level data corresponding to a quarter can be generated based on the lower level data corresponding to a month. The upper level data corresponding to half a year can be generated based on the lower level data corresponding to a quarter.

The first period unit, the second period unit, and a plurality of period units can be determined based on the metrics corresponding to the first event data, the first type of data, and the second type of data. As an example, the number of orders of each user in the metric can be a metric that occurs less frequently in a day. That is, the first period unit, the second period unit, and a plurality of period units corresponding to the number of orders of each user can be set to be relatively long. As another example, the number of logins of each user in the metric can be a metric that occurs more frequently in a day. That is, the first period unit, the second period unit, and a plurality of period units corresponding to the number of logins of each user can be set to be relatively short.

When a query is obtained from the terminal 120, the electronic device 100 may transmit information of response data corresponding to the query to the terminal 120. As an embodiment, the electronic device 100 may identify the second data corresponding to the query in the data of the second type stored in the second table, identify the third data corresponding to the query in the data of the first type stored in the first table, generate response data corresponding to the query based on the second data and the third data, and transmit information of the response data to the terminal 120. The specific embodiment will be described with reference to FIG. 5.

FIG. 3 is a diagram for explaining a method of storing data of the first type and data of the second type in the first table and the second table when the first event data corresponds to the first metric included in the first sub-metric set. The metric of the event data of one embodiment of FIG. 3 is related to "Order-last-date", which can be included in the second sub-metric set.

The data source 310 may correspond to event data corresponding to an event occurring on the service. When the first event occurs on the service, the electronic device 100 may determine whether to include information of the metric included in the metric set set in the first event data 301 corresponding to the first event. When including information of the first metric included in the metric set set in the first event data 301, the electronic device 100 may sequentially store the data of the first type and the data of the second type in the first table and the second table. Specifically, the electronic device 100 may store the event data including the first event data 301 in the storage 102 through the data workflow 311.

As an example, data of the first type may be stored in the first table 320 in the memory 102. When the first period unit is 10 seconds, the first event data with event occurrence times from 13:01:10 on April 3, 2023 to 13:01:20 on April 3, 2023 may be combined to generate data of the first type and may be stored in the first table 320. For example, the first event data 301 corresponding to the first event occurring between 13:01:10 on April 3, 2023 and 13:01:20 on April 3, 2023 may be stored in the first table 320 as data of the first type after being processed at 13:01:11 on April 3, 2023. In addition, the event data that occurred in the past can be combined into the first period unit and stored in the first table 320 in the order of the time when the event occurred.

For example, the value of the data of the first type based on the second event data corresponding to the item order event occurring at 16:31:20 on March 2, 2023 may be "True" and may be stored in the first table 320. Also, the value of the data of the first type based on the fourth event data corresponding to the item order event occurring at 16:31:19 on March 1, 2023 may be "True" and may be stored in the first table 320. However, the item order occurring at 16:31:19 on March 1, 2023 is cancelled, and the item order cancellation event may occur at 16:35:20 on March 1, 2023. The value of the data of the first type based on the third event data corresponding to the item order cancellation event occurring at 16:35:20 on March 1, 2023 may be "False" and may be stored in the first table 320. In connection with identifying mutually related events such as item order events and item order cancellation events, the event data included in the data source 310 and the data stored in the first table 320 or the second table 330 may further include identification information for identifying the corresponding events. Referring to FIG. 3, the identification information corresponding to the item order cancellation event occurring at 16:35:20 on March 1, 2023 may correspond to the identification information corresponding to the item order event occurring at 16:31:19 on March 1, 2023.

As an embodiment, the data of the second type may be stored in the second table 330 in the memory 102. i) Corresponding to the new storage or update of the data of the first type in the first table 320, the data of the second type may also be newly stored or updated in the second table 330. Alternatively, ii) from the time when the data of the first type is newly stored or updated in the first table 320 to the time when a set period (e.g., 1 day) has passed, the data of the second type may be newly stored or updated in the second table 330. As an embodiment, the event occurrence time and the processing time of the data of the second type stored in the second table 330 may differ by a set period, i.e., 1 day. The set period is not limited to 1 day. As another embodiment, the set period may correspond to the period of the cancelable event corresponding to the data of the first type. If the set period is set to the period of the cancelable event corresponding to the data of the first type, the event corresponding to the data of the first type cannot be canceled from the time when the data of the first type is newly stored or updated to the time when the set period has passed. That is, when the set period is set to the period of the cancelable event corresponding to the data of the first type, the modification operation of the data stored in the first table 320 can be minimized.

When the second period unit is one month, the data generated by merging the data of type 1 corresponding to events occurring in April 2023 can be stored as data of type 2. In addition, the data generated by merging the data of type 1 corresponding to events occurring in March 2023 can also be stored as data of type 2. For example, events occurring in March 2023 may include an item order event occurring at 16:31:20 on March 2, 2023, an item order event occurring at 16:31:19 on March 1, 2023, and an item order cancellation event occurring at 16:35:20 on March 1, 2023. The data of the second type corresponding to March 2023 can be determined based on the values of each of the data of the first type corresponding to the events occurring in March 2023 and the time of occurrence of the events. The time of occurrence of the events of the data of the second type can be determined as the latest time of occurrence of the data of the first type corresponding to the events occurring in March 2023, which is 16:31:19 on March 1, 2023. In addition, the value of the data of the second type can be "True". That is, the data of the first type corresponding to the item order event occurring at 16:31:19 on March 1, 2023 and the data of the first type corresponding to the item order cancellation event occurring at 16:35:20 on March 1, 2023 can be combined and managed. Therefore, the efficiency of data management can be improved. Furthermore, in order to improve the efficiency of data management, the set time for merging the data of the first type stored in the first table 320 and storing them in the second table 330 can be determined to correspond to the metric. For example, in order to minimize the modification operation of the data of the second type stored in the second table 330, the set time can be determined based on the difference between the time of occurrence of related events such as item order events and item order cancellations. For example, the set time can be set to be greater than the average interval between the time of occurrence of related events such as item order events and item order cancellations.

Furthermore, storing the data corresponding to the events occurring on the service in the first table 320 and the second table 330 at the same time may be inefficient in terms of the first aspect of data storage space. On the contrary, storing the data corresponding to the events occurring on the service in the first table 320 and the second table 330 at the same time may be efficient in terms of the second aspect of detecting the accuracy of the data. Taking the first aspect and the second aspect into consideration, the electronic device 100 may store the data corresponding to the events occurring on the service in the first table 320 and the second table 330 at the same time during a set period. At the same time, the electronic device 100 may delete the data of the first type stored in the first table 320 corresponding to the event when the set period has passed. Therefore, the first aspect regarding data storage space and the second aspect regarding the accuracy of the test data can be optimized at the same time.

As an example, after integrating the data of type 1 stored in table 320, the data of type 1 may be deleted from table 320 when a set period (e.g., 2 months) has passed since the data was stored as type 2 or the validity of the data of type 1 is false. In this regard, the data of type 1 corresponding to the item order event occurring at 18:31:20 on February 2, 2023 may be deleted at 18:31:20 on April 2, 2023, which is 2 months after the set period has passed since the data was stored as type 2. Therefore, the data of the item order event occurring at 18:31:20 on February 2, 2023 may not be stored in table 320 of FIG. 3.

FIG. 4 is a diagram for explaining a method of storing data of the first type and data of the second type in the first table and the second table when the first event data corresponds to the second metric included in the second sub-metric set.

The metric of event data in one embodiment is "Order-count", which can be included in the first sub-metric set. In the method of storing the data of the first type and the data of the second type in FIG. 4 in the first table and the second table, the detailed description that is partially repeated with that in FIG. 3 is omitted.

As an example, data of the first type may be stored in the first table 410 in the memory 102. When the first period unit is 10 seconds, data of the first type generated by merging the first event data with event occurrence times from 13:01:10 on May 3, 2023 to 13:01:20 on May 3, 2023 may be stored in the first table 410. For example, the first event data 401 corresponding to the first event occurring between 13:01:10 on May 3, 2023 and 13:01:20 on May 3, 2023 may be stored in the first table 410 as data of the first type after being processed at 13:01:11 on May 3, 2023. In addition, event data that occurred in the past may be combined into the first period unit and stored in the first table 410 in the order of the event occurrence. For example, the value of the first type of data based on the third event data corresponding to the item order event that occurred at 16:31:19 on April 1, 2023 may be 3 and may be stored in the first table 410. The item order cancellation event that occurred at 16:35:20 on April 1, 2023 may be an event that cancels part of the items ordered by the item order event that occurred at 16:31:19 on April 1, 2023. Therefore, the value of the data of the first type based on the second event data corresponding to the item order event occurring at 16:35:20 on April 1, 2023 can be -1 and can be stored in the first table 410.

As an embodiment, the second table in the memory 102 may include a plurality of sub-tables. The second type of data may include a plurality of levels of data corresponding to a plurality of period units, and the plurality of period units may be set based on measurement. Referring to FIG. 4 , when the plurality of period units include a month as the second period unit and half a year as the third period unit, the first sub-table 421 may store the second type of data corresponding to the second period unit, and the second sub-table 422 may store the second type of data corresponding to the third period unit. In FIG. 4 , the second type of data corresponding to the second period unit may be referred to as the first level of data, and the third type of data corresponding to the third period unit may be referred to as the second level of data.

The data generated by merging the data of type 1 corresponding to the events occurring in May 2023 can be stored as data of type 2 in the first sub-table 421. More specifically, the events occurring in May 2023 may include the item order event occurring at 13:01:10 on May 3, 2023.

The data generated by merging the data of the first type corresponding to the events occurring in April 2023 can be stored as the data of the second type in the first sub-table 421. More specifically, the events occurring in April 2023 can include the item order event occurring at 16:31:19 on April 1, 2023, and the item order cancellation event occurring at 16:35:20 on April 1, 2023. At this time, the value of the data of the second type corresponding to April 2023 can be determined as the sum of -1 and 3, 2, where -1 and 3 are the values of the item order event occurring at 16:31:19 on April 1, 2023 and the item order cancellation event occurring at 16:35:20 on April 1, 2023, respectively. In addition, the event occurrence time of the data of type 2 corresponding to April 2023 may include 16:31:19 on April 1, 2023. That is, the event occurrence time corresponding to the item order cancellation event is not included in the event occurrence time of the data of type 2, but can be accumulated into the value of the data of type 2.

The data generated by merging the data of the first type corresponding to the events occurring in March 2023 can be stored as the data of the second type in the first sub-table 421. More specifically, the events occurring in March 2023 can include the item order event occurring at 16:31:19 on March 1, 2023, and the item order event occurring at 15:31:19 on March 2, 2023. At this time, the value of the data of the second type corresponding to April 2023 can be determined as the sum of 3 and 6, 9, and 3 and 6 are the values of the item order event occurring at 16:31:19 on March 1, 2023, and the item order event occurring at 15:31:19 on March 2, 2023, respectively. In addition, the event occurrence time of the second type of data corresponding to March 2023 may include 16:31:19 on March 1, 2023 and 15:31:19 on March 2, 2023.

The data generated by merging the data of the first level corresponding to the events occurring in the first half of 2023, i.e., from January to June, can be stored in the second sub-table 422 as the data of the second type. The value of the data of the second level can be determined as the sum of the values of the data of the first level, i.e., 10, 2, 9, and 21. The event occurrence time of the data of the second level can include 13:01:10 on May 3, 2023, 16:31:19 on April 1, 2023, 16:31:19 on March 1, 2023, and 15:31:19 on March 2, 2023. Although not shown in Figure 4, if the upper-level data generated based on the lower-level data stored in Table 2 is stored in Table 2 as the second type of data, the lower-level data and the upper-level data may be partially duplicated. The lower-level data can be deleted at a time point after a set period of time has passed since the upper-level data was stored in Table 2. In terms of data management efficiency, the set period can be set shorter.

As shown in Figures 3 and 4, the electronic device 100 can merge the event data that occurred on the service within multiple time units and store them in layers. In addition, when the data stored repeatedly in the first table and the second table meets the set conditions (for example, the first condition that the set time has passed since the time point stored in the second table and the second condition that the validity of the data is false), the electronic device 100 can delete part of the repeatedly stored data. Therefore, the efficiency of data storage management can be improved.

FIG5 is a flow chart showing a method for transmitting information of response data corresponding to a query obtained from a terminal.

Referring to FIG. 5 , it can be clearly understood that each action of the electronic device 100 transmitting information of the response data corresponding to the query obtained from the terminal 120 can be changed or replaced in part, or some orders between actions can be changed within the scope clearly understood by a person with common sense in the technical field to which the present invention belongs.

In step S510, the electronic device 100 may obtain a query from the terminal.

The query received from the terminal 120 may include information about the measurement and information about the query period.

In step S520, the electronic device 100 can identify and query the corresponding second data in the second type of data stored in the second table.

In step S530, the electronic device 100 can identify and query the corresponding third data in the data of the first type stored in the first table.

According to one embodiment, the electronic device 100 can identify the second data and the third data corresponding to the query from the first type of data and the second type of data stored in the first table and the second table in the memory 102. As an embodiment, the first period unit can be 10 seconds. In addition, the plurality of period units include not only 1 day as the second period unit, but also a month, a quarter, and a half year. The query period corresponding to the query can be from January 1, 2023 to the current time point of May 2, 2023 at 13:01:10. The electronic device 100 can identify at least one period unit corresponding to the query, and identify the second data based on the data of at least one period unit in the data of the second type stored in the second table. The at least one period unit can be 1 day, 1 month, and 1 quarter. The electronic device 100 can identify the second data and the third data according to various methods including 1) and 2).

1) As an embodiment, the electronic device 100 can identify the data corresponding to the first quarter of 2023 (from January 1, 2023 to March 31, 2023), the data corresponding to April and May 2023, and the data corresponding to May 1, 2023 among the data of the second type stored in the second table as the second data.

Furthermore, the electronic device 100 can identify the data of the first type stored in the first table as the third data: i) data from 0:0:00 on May 2, 2023 to 0:0:10 on May 2, 2023, ii) data from 0:0:10 on May 2, 2023 to 0:0:20 on May 2, 2023, ... iii) data from 13:01:00 on May 2, 2023 to 13:01:10 on May 2, 2023. At this time, the second data and the third data can be mutually exclusive.

2) As another example, at a time point when a set period (e.g., one month) has passed since the data corresponding to the data stored in the first table was stored in the second table. That is, based on the current time point of May 2, 2023, 13:01:10, the data of the first type of data stored in the first table from the time of the event to April 1, 2023 can be deleted to improve the efficiency of data management. On the contrary, the data stored in the first table from April 2, 2023 to the current time point can be partially duplicated with the data of the second type stored in the second table. The electronic device 100 can identify the second data and the third data based on this. Specifically, the electronic device 100 can identify the data corresponding to the first quarter of 2023 (from January 1, 2023 to March 31, 2023), the data corresponding to April and May 2023, and the data corresponding to May 1, 2023 among the data of the second type stored in the second table as the second data.

Furthermore, the electronic device 100 can identify i) data from 0:0:00 on April 2, 2023 to 0:0:10 on April 2, 2023, ii) data from 0:0:10 on April 2, 2023 to 0:0:20 on April 2, 2023, ... iii) data from 13:01:00 on May 2, 2023 to 13:01:10 on May 2, 2023 among the data of the first type stored in the first table as the third data. At this time, the second data and the third data may be partially repeated.

In step S540, the electronic device 100 can generate response data corresponding to the query based on the second data and the third data.

As an example, when the second data and the third data are mutually exclusive, the electronic device 100 can integrate the second data and the third data to generate response data corresponding to the query.

However, the update of the data of the first type stored in the first table may not be reflected in the data of the second type stored in the second table. Alternatively, according to the method of identifying the second data and the third data, the second data and the third data may be partially repeated. In this case, the electronic device 100 can verify the accuracy of the data by comparing the data stored in the first table with the data stored in the second table. Specifically, the electronic device 100 can compare the time of occurrence of the event corresponding to the second data with the time of occurrence of the event corresponding to the third data, identify the fourth data that is repeated with the second data in the third data, filter the fourth data in the third data and identify the fifth data, and generate response data based on the second data and the fifth data.

In step S550, the electronic device 100 may transmit the information of the response data to the terminal.

As an embodiment, the electronic device 100 may transmit the information of the response data generated in step S540 to the terminal 120. In this regard, the electronic device 100 merges the event data occurring on the service within a plurality of time units and stores them in layers in the memory 102, and provides the information of the response data from the memory 102, which may be more efficient in data processing efficiency than using the event data stored separately in the message queue to provide the response data corresponding to the query.

FIG. 6 is a diagram for explaining a method in which an electronic device provides information of response data corresponding to a query when performing a query operation during a merge operation.

Here, the merge operation may include: i) a read operation, which identifies the first data corresponding to the second period unit in the data of the first type stored in the first table 600 at time t1, ii) a write operation, which stores the data of the second type generated based on the first data in the second table 610 at time t3, and iii) a delete operation, which deletes the data of the first type stored in the first table 600 that is duplicated with the data stored in the second table 610 at time t4. In addition, the query operation may include providing information of the response data corresponding to the query obtained from the terminal 120 of FIG. 6.

Referring to FIG. 6 , the query operation may be performed at time t3 between time t2 when the lighting operation is performed and time t4 when the deletion operation is performed. At this time, since the deletion operation has not been performed at time t3, the data stored in the first table 600 and the second table 610 may be partially repeated. The electronic device 100 may identify the fourth data in the data stored in the first table 600 that is repeated with the data stored in the second table 610 based on the event occurrence time of the data stored in the first table 600 and the second table 610 and the identification information used to identify the event. The electronic device 100 may identify the fifth data that filters the fourth data in the data stored in the first table 600. The electronic device 100 can generate response data corresponding to the query based on the fifth data and the data stored in the second table 610.

FIG7 is a flow chart showing a method for modifying data stored in a table.

Referring to FIG. 7 , it can be clearly understood that the various actions of the electronic device 100 to modify the data stored in the table can be changed or replaced within the scope of the common sense in the technical field to which the present invention belongs, or some orders between the actions can be changed.

According to one embodiment, when a set period has passed since the time when the data of the first type is newly stored or updated in the first table 320, the data of the second type can be newly stored or updated in the second table 330. In particular, when the set period is set to the period of the cancelable event corresponding to the data of the first type, the modification operation of the data stored in the first table 320 can be minimized. However, if i) the set period is set to be shorter than the period of the cancelable event corresponding to the data of the first type, ii) the data corresponding to the first type is newly stored or updated in the first table 320, and the data of the second type is also newly stored or updated in the second table 330, the data stored in the second table can be modified when a new event occurs.

In step S710, the electronic device 100 can identify the second event data corresponding to the second event occurring on the service and the second identification information corresponding to the second event.

In step S720, the electronic device 100 can identify the eighth data in the data stored in the second table based on the second identification information, and the eighth data is the identification information corresponding to the second identification information.

According to one embodiment, when the second event occurs in real time on the service, the electronic device 100 can identify the second event data corresponding to the second event and the second identification information corresponding to the second event. In addition, the electronic device 100 can identify the eighth data in the data stored in the second table based on the second identification information, and the eighth data is the identification information corresponding to the second identification information. As an embodiment, the second event can be a cancellation event of the first event in the event corresponding to the eighth data. However, the second event is not limited to this. For example, the second event can be an event co-related to the first event in the event corresponding to the eighth data. For example, when the first event is an event of an item order, the second event can be an event of a modification of the item order.

In step S730, the electronic device 100 can modify the eighth data based on the second event data.

In step S740, the electronic device 100 can store the modified 8th data into the 2nd table.

According to one embodiment, the 8th data may be modified differently depending on whether the metric corresponding to the 1st event is included in the 1st sub-metric set or the 2nd sub-metric set. i) When the metric corresponding to the 1st event is included in the 1st sub-metric set, the value of the modified 8th data may be determined based on the value of the 8th data before modification and the value corresponding to the 2nd event data. For example, when the metric corresponding to the 1st event is "order count", the value of the modified 8th data may correspond to subtracting the number of order cancellations corresponding to the 2nd event from the value of the 8th data before modification. ii) When the metric corresponding to the 1st event is included in the 2nd sub-metric set, the value of the modified 8th data may be determined based on the value of the 8th data before modification, the time of the event occurrence, the value corresponding to the 2nd event data, and the time of the event occurrence. For example, when the metric corresponding to the first event is "Order-last-date", the value of the revised eighth data can be determined as "True" or "False" according to whether other events other than the first event occurred within the second period unit. In addition, when there are other events other than the first event occurring within the second period unit, the event occurrence time of the revised eighth data can be determined as the latest time among the event occurrence times of other events other than the first event. Therefore, the electronic device 100 can update the second data stored in the second table to the revised second data.

FIG8 is a diagram for illustrating a page for setting event data and metrics to be summarized in one embodiment.

Referring to FIG. 8 , page 800 may be a page for setting event data and metrics to be summarized. Page 800 may include a first area 810 , a second area 820 , a third area 841 , a fourth area 842 , and a fifth area 850 .

The first area 810 may be an area for selecting one of a member or a product as an entity type. Furthermore, the second area 820 may be an area for setting an entity ID, which is used to distinguish the member or product selected in the first area 810 from other members or products. In this regard, the event data may include at least one of the member's identification information and the product's identification information. Referring to FIG. 8 , the entity type may be set to "Member", and the entity ID may be "138339393". Furthermore, according to the embodiments of FIG. 3 and FIG. 4 , the entity type may be "Member", and the entity ID may be "123".

Furthermore, the third area 841 and the fourth area 842 may be areas for setting the second time point from the first time point, which is the time point at which the event data corresponding to the event occurring on the service is extracted. The third area 841 may correspond to the first time point, and the fourth area 842 may correspond to the second time point.

The fifth area 850 may be an area for connecting to a page displaying information of the summary data. In response to the action of the "Search" icon in the third area 830, the electronic device 100 may provide a page displaying the summary data.

The sixth area 860 may be an area for setting information of a metric such as "Member Login Last Date". However, in addition to the metric set set by the sixth area 860, information of a custom metric may also be set. More specifically, the user may set a metric that indicates whether a specific condition is satisfied as "True" or "False" by the sixth area 860. For example, the added specific condition may be related to whether the user has placed an order of a set amount or more within a set period. Therefore, the electronic device 100 may provide a list of users whose value corresponding to the metric of the added specific condition is "True" in the service. That is, by setting the metric of whether a specific condition is satisfied to "True" or "False", the electronic device 100 can provide a list of users whose values corresponding to the metric of the added specific condition are "True" or a list of users whose values corresponding to the metric of the added specific condition are "False".

FIG. 9 is a diagram for illustrating a page displaying summary data in an embodiment.

Referring to FIG. 9 , page 900 may be a page for displaying summary data. Area 910 of page 900 may display the value of each metric included in page 800. For example, the value corresponding to the metric of "Member Login Last Date" may be "2023-05-18 16:44:21 KST".

FIG. 10 is a block diagram showing an electronic device for managing service-related data according to an embodiment.

The electronic device 100 of FIG. 10 may correspond to the electronic device of the present invention. According to one embodiment, the electronic device 100 may include a transceiver 101, a memory 102, and one or more processors 103. The electronic device 100 shown in FIG. 10 only illustrates the components related to the present embodiment. Therefore, those with common sense in the technical field related to the present embodiment can understand that in addition to the components shown in FIG. 10, other general components may be further included.

For example, according to one embodiment, the electronic device 100 may include a transceiver 101. The transceiver 101 may be a device for implementing wired/wireless communication to communicate with an external electronic device. The external electronic device may be a terminal 120. Furthermore, the communication technology used by the transceiver 101 may include GSM (Global System for Mobile communication), CDMA (Code Division Multi Access), LTE (Long Term Evolution), 5G (5th generation mobile network), WLAN (Wireless LAN), Wi- Fi (Wireless-Fidelity), Bluetooth, RFID (Radio Frequency Identification), Infrared Data Association (IrDA), Zigbee, NFC (Near Field Communication), etc.

According to one embodiment, the transceiver 101 can receive query information from the terminal 120 and provide information of response data corresponding to the query to the terminal 120.

The memory 102 can store information for implementing at least one of the above methods by using FIG. 1 to FIG. 10. The memory 102 can store one or more commands implemented by one or more processors 103. The memory 102 can be called a memory, which can be a volatile memory or a non-volatile memory. The memory 102 can include information of a set of measurement sets and information of multiple time units of each measurement.

One or more processors 103 can control the overall operation of the electronic device 100 and process data and signals. One or more processors 103 can implement one of the methods described in Figures 1 to 10. One or more processors 103 can be composed of at least one hardware unit. In addition, one or more processors 103 can operate by executing one or more commands stored in the memory 102 to generate one or more software modules. One or more processors 103 can control the implementation of the electronic device 100 through the interaction of components, which can further include the transceiver 101 and the memory 102, and the electronic device 100.

According to one embodiment, the processor 103 can identify the first event data corresponding to the event occurring on the service in the first period unit by executing one or more commands, store the first type of data in the first table based on the first event data, generate the second type of data based on the first data corresponding to the second period unit among the first type of data stored in the first table, and store the second type of data in the second table.

On the other hand, the preferred embodiments of the present invention are described in this specification and the accompanying drawings. Although specific terms are used, these terms are only used in a general sense to explain the technical content of the present invention and help understand the invention, and are not intended to limit the scope of the present invention. In addition to the embodiments disclosed herein, technical personnel in this field can of course implement other variations based on the technical ideas of the present invention.

The electronic device or terminal of the above embodiment may include: a processor, a memory for storing and executing program data, a permanent storage such as a disk drive, a communication port for communicating with external devices, a touch panel, a key, a button and other user interface devices, etc. The method implemented by the software module or algorithm can be stored in a computer-readable recording medium as a computer-readable code or program command that can be executed on the above processor. Here, as computer-readable recording media, there are magnetic storage media (e.g., ROM (read-only memory), RAM (random-Access memory), floppy disk, hard disk, etc.) and optical readable media (e.g., CD-ROM, DVD, Digital Versatile Disc), etc.). Computer-readable recording media are distributed in computer systems connected to the network, so that computer-readable codes can be stored and executed in a distributed manner. The media can be read by the computer, stored in the memory, and executed in the processor.

The present embodiment may be represented by a functional block structure and various processing steps. Such functional blocks may be implemented by different hardware and/or software structures that perform specific functions. For example, the embodiment may be composed of integrated circuits that can perform various functions such as memory, processing, logic, look-up tables, etc., controlled by one or more microprocessors or other control devices. The components may be executed by software programs or software components. Similarly, the present embodiment includes algorithms implemented by a combination of data structures, programs, routines, or other programs, and can therefore be implemented by programming or scripting languages such as C, C++, Java, assemblers, Python, etc. In terms of functionality, it can be implemented by algorithms executed in one or more processors. In addition, this embodiment can use prior art to perform electronic environment settings, signal processing and/or data processing. Terms such as "mechanism", "component", "mechanism", and "structure" can be used broadly and are not limited to mechanical or physical structures. The above terms can be associated with processors and include the meaning of a series of processes (routines) of software.

The above embodiment is only one example, and other embodiments may be implemented within the scope of the patent application described below.

S210: Step

S220: Step

S230: Step

S240: Step

Claims (15)

A method for managing data related to a service, which is performed by an electronic device, comprises the following steps: identifying first event data corresponding to an event occurring on the service within a first period; based on the first event data, storing data of a first type in a first table; generating data of a second type based on the first data corresponding to a second period in the data of the first type stored in the first table; and storing the data of the second type in a first table. Stored in the second table, the step of generating the data of the second type includes the following steps: when the sixth data as the data of the first type is newly stored in the first table, the seventh data as the data of the second type is generated based on the first data and the sixth data, wherein when the set time has passed since the seventh data was stored in the second table, or the validity of the sixth data is false, the sixth data is deleted from the first table. A method for managing service-related data as in claim 1, wherein the first event data includes information of at least one metric included in a set metric set, and the set metric set includes a first sub-metric set and a second sub-metric set. A method for managing service-related data as in claim 2, wherein when the first sub-event data included in the first event data corresponds to the first metric included in the first sub-metric set, the value of the first type of data is determined to be the first value obtained by accumulating the values of each of the first sub-event data, and when the second sub-data included in the first data corresponds to the first metric, the value of the second type of data is determined to be the second value obtained by accumulating the values of each of the second sub-data. A method for managing service-related data as in claim 2, wherein when the first sub-event data included in the first event data corresponds to the second metric included in the second sub-metric set, the data of the first type is determined based on the value of each of the first sub-event data and the time of occurrence of each of the first sub-event data, and when the second sub-data included in the first data corresponds to the second metric, the data of the second type is determined based on the value of each of the second sub-data and the time of occurrence of each of the second sub-data. A method for managing service-related data as in claim 1, wherein the data of the second type mentioned above includes data of a plurality of levels corresponding to a plurality of time units, and the plurality of time units are determined based on the measurement corresponding to each of the data of the second type mentioned above. A method for managing and service-related data as in claim 5, wherein the plurality of period units include a third period unit and a fourth period unit, and the method further includes the following steps: when the third period unit is a period unit shorter than the fourth period unit and is a period unit adjacent to the fourth period unit among the plurality of period units, identifying the first-level data corresponding to the third period unit in the second-type data stored in the second table; and generating the second-level data corresponding to the fourth period unit based on the first-level data. The method for managing service-related data as in claim 1 further comprises the following steps: obtaining a query from a terminal; identifying the second data corresponding to the query in the data of the second type stored in the second table; identifying the third data corresponding to the query in the data of the first type stored in the first table; generating response data corresponding to the query based on the second data and the third data; and transmitting information of the response data to the terminal. The method for managing service-related data as in claim 7, wherein the step of generating the above-mentioned response data includes the following steps: comparing the time of occurrence of the event corresponding to the above-mentioned second data with the time of occurrence of the event corresponding to the above-mentioned third data, identifying the fourth data that is repeated with the above-mentioned second data in the above-mentioned third data; filtering the above-mentioned fourth data in the above-mentioned third data to identify the fifth data; and generating the above-mentioned response data based on the above-mentioned second data and the above-mentioned fifth data. A method for managing and service-related data as in claim 7, wherein when the data of the second type includes data of multiple levels corresponding to multiple time units, the step of identifying the second data includes the following steps: identifying at least one time unit corresponding to the query among the multiple time units; and identifying the second data based on the data of the at least one time unit in the data of the second type stored in the second table. The method for managing service-related data as in claim 6, wherein the data of the first level mentioned above is deleted from the second table mentioned above when a set period of time has passed since the data of the second level mentioned above was stored in the second table mentioned above. A method for managing data related to a service as in claim 1, wherein the first event data includes at least one of user identification information of the service or item identification information of the service. A method for managing service-related data as in claim 1, wherein each data stored in the second table includes identification information for identifying a corresponding event, and the method further includes the following steps: identifying the second event data corresponding to the second event occurring on the service, and the second identification information corresponding to the second event; based on the second identification information, identifying the eighth data in the data stored in the second table, the eighth data being the identification information corresponding to the second identification information; modifying the eighth data based on the second event data; and storing the modified eighth data in the second table. The method for managing service-related data as in claim 1, wherein the above-mentioned set period corresponds to the cancelable period of the third event corresponding to the above-mentioned sixth data. An electronic device for managing data related to a service, comprising: a transceiver; one or more processors; and a memory storing one or more commands executed by the one or more processors; the one or more processors are configured to identify first event data corresponding to an event occurring on the service within a first period unit by executing the one or more commands, store data of a first type in a first table based on the first event data, and store data of a first type in a second period unit based on the first event data. The first data corresponding to the unit generates data of the second type, and stores the data of the second type in the second table, wherein the one or more processors are further configured to generate the seventh data as the data of the second type based on the first data and the sixth data when the sixth data as the data of the first type is newly stored in the first table, wherein the sixth data is deleted from the first table when a set period of time has passed since the seventh data was stored in the second table or the validity of the sixth data is false. A non-transitory computer-readable recording medium recording a program for executing the method of claim 1 in a computer.