TWI862111B - Operating method for electronic apparatus for providing information and electronic apparatus supporting thereof - Google Patents

Abstract

According to the present invention, a method for an electronic device to provide information may include the following steps: obtaining data source management information, the data source management information is for managing a data source, the data source is used to store event data corresponding to an event on a service related to the above-mentioned electronic device in a database; obtaining data storage management information, the data storage management information is for setting up a database used to store the above-mentioned event data in the above-mentioned database; management; storing the processed data in the above-mentioned database, the processed data being the result of processing the above-mentioned event data according to a data management format set based on the above-mentioned data source management information and the above-mentioned data storage management information; and providing information related to a data set in response to a data query request for searching data in the above-mentioned database, the data set including one or more processed data confirmed from the above-mentioned database.

Description

Operation method of electronic device for providing information and electronic device supporting the same

The present invention relates to a method and device for providing information, and more specifically, to a method and an electronic device for providing information related to data corresponding to a data query request based on a database constructed in a manner of storing data according to a fixed format.

With the development of electronic technology, e-commerce has become a field of shopping. Customers can buy items online even if they do not go directly to the mall or market, and the items purchased online will be delivered to the delivery location requested by the customer.

In the case of e-commerce, the processing of detailed and accurate information about products has a significant impact on service satisfaction, so various solutions are being discussed to process information in a more detailed and accurate manner.

In this regard, please refer to previous literature such as KR101756594B1 or KR101500849B1.

[The problem the invention is trying to solve]

According to the method of the present invention, the electronic device can provide information related to data corresponding to the data query request based on a database constructed in a manner of storing data according to a fixed format.

The technical problems to be solved by this embodiment are not limited to the technical problems mentioned above. Those with common sense in the technical field to which the present invention belongs can clearly understand other technical problems not mentioned based on the following description. [Technical means for solving the problem]

Various embodiments may provide an operation method of an electronic device for providing information and an electronic device supporting the same.

The method of providing information by an electronic device in various embodiments may include the following steps: obtaining data source management information, wherein the data source management information manages a data source (source), wherein the data source is used to obtain event data (business information) corresponding to an event on a service related to the electronic device; data) in a database; obtaining data storage management information, the data storage management information managing the database setting for storing the event data in the database; setting in a manner to store processed data in the database, the processed data being processed according to a data management format set based on the data source management information and the data storage management information; and providing information related to a data set in response to a data query request for searching data in the database, the data set including one or more processed data confirmed from the database.

In an exemplary embodiment, the event data may be queued based on a message queue, which includes more than one message queue.

In an exemplary embodiment, the data source management information includes information of more than one data source, and the first data source included in the more than one data source may correspond to the first topic, which is selected for the first data source from one or more topics corresponding to the more than one message queues.

In an exemplary embodiment, the information of the first data source included in the data source management information may include information of a data subject corresponding to the first topic.

In an exemplary embodiment, the data storage management information may include identification information for identifying a data subject corresponding to the first topic.

In an exemplary embodiment, the identification information may be generated based on one of the customer ID (Identifier) of the user on the service, the email ID of the user, the IP (Internet Protocol) address of the user, and the terminal ID of the user.

In an exemplary embodiment, the data management format can manage data by classifying it in a row form, and the row form is set according to the unit of the identification information.

In an exemplary embodiment, the data storage management information may include information of one or more data items corresponding to the first question.

In an exemplary embodiment, when a plurality of data related to a data subject corresponding to the first topic is confirmed in a first data item included in the one or more data items, the data storage management information may include information for setting the plurality of data into a column form of the first data item corresponding to the data subject.

In an exemplary embodiment, for identifying the identification information of the data subject corresponding to the above-mentioned first question, the above-mentioned data management format can classify and manage each data item included in one or more data items corresponding to the above-mentioned first question and one or more data confirmed for the above-mentioned data subject in each of the above-mentioned data items in a row format corresponding to the above-mentioned identification information.

In an exemplary embodiment, the data storage management information may include information on the validity period of the data stored in the database.

In an exemplary embodiment, the processing data may include identification information for identifying a data subject corresponding to a topic included in the data source management information, data items set in the data storage management information corresponding to the topic, data values confirmed in the event data based on the data subject and the data items, and the time point when the event data is obtained on the service.

In an exemplary embodiment, the data query request may include input information required for querying the data, and the input information required for querying the data is set based on the data management format.

In an exemplary embodiment, the data query request may include information about the subject for querying data and information about the data operator for the subject.

In an exemplary embodiment, the information associated with the data set may include information about a result obtained by operating the data operator on the one or more processed data.

In an exemplary embodiment, the data query request may include information of a query period for querying data.

In an exemplary embodiment, each processing data included in the above-mentioned one or more processing data can be confirmed based on the time point at which each event data corresponding to the above-mentioned each processing data is obtained on the above-mentioned service is included in the point during the above-mentioned query period.

In an exemplary embodiment, the data query request may include information about the data subject and data items used to query the data.

The electronic device for providing information in various embodiments may include: a processor; and one or more memories storing one or more instructions; and when executing the one or more instructions, controlling the processor to perform the following steps: obtaining data source management information, the data source management information is for managing a data source, the data source is used to store event data corresponding to events on services related to the electronic device in a database; obtaining data storage The data storage management information manages the database setting for storing the event data in the database; the processing data is stored in the database, and the processing data is processed according to the data management format set based on the data source management information and the data storage management information; and in response to a data query request for searching data in the database, information related to a data set is provided, and the data set includes one or more processed data confirmed from the database.

The above-mentioned various embodiments of the present invention are only a part of the preferred embodiments of the present invention. Those with common sense in the technical field can derive and understand multiple embodiments reflecting the technical features of the various embodiments of the present invention based on the following detailed description. [Effects of the invention]

The present invention proposes a method for an electronic device to provide information related to data corresponding to a data query request based on a database constructed in a manner of storing data according to a fixed format, thereby having a technical effect in terms of effectively seeking convenience in the storage, management and provision of data obtained in a service.

The effects that can be obtained in the present invention are not limited to the effects mentioned above. Those with common sense in the technical field to which the present invention belongs can clearly understand other effects not mentioned according to the following description.

The following embodiments are those that combine the constituent elements and features of various embodiments in a specific form. If not explicitly mentioned otherwise, each constituent element or feature can be considered optional. Each constituent element or feature can be implemented in a form that is not combined with other constituent elements or features. In addition, some constituent elements and features can be combined to form various embodiments. The order of the actions described in various embodiments can be changed. Some constituent elements or features of a certain embodiment can be included in other embodiments, or can be exchanged with corresponding constituent elements or features of other embodiments.

In the description of the drawings, processes or steps that may confuse the subject matter of various embodiments are not described, nor are processes or steps that are understandable to a person having ordinary knowledge in the technical field.

Throughout the specification, when a certain part is described as "comprising or including" a certain constituent element, unless otherwise specifically stated, it means that other constituent elements may be further included, and other constituent elements are not excluded. In addition, the terms "...part", "...device", "module" and the like stated in the specification refer to a unit that processes at least one function or action, which may be implemented by hardware, software, or a combination of hardware and software. In addition, in the text describing various embodiments (especially, in the scope of the invention application below), unless otherwise indicated in the present invention or not explicitly contradicted in the text, "a (or an)", "one (one)", "the (the)" and similar related words can be used in a meaning including both the singular and the plural.

Hereinafter, with reference to the attached drawings, the preferred implementation modes of various embodiments are described in detail. The detailed description disclosed below together with the attached drawings is for illustrating exemplary implementation modes of various embodiments, and is not intended to represent the only implementation mode.

Furthermore, specific terms used in various embodiments are provided to help understand the various embodiments, and the use of such specific terms may be changed into other forms without departing from the technical ideas of the various embodiments.

FIG. 1 is a diagram of an information providing system for illustrating an operation method of an electronic device for providing information that can implement various embodiments.

Referring to FIG. 1 , the information providing system of various embodiments can be implemented in various types of electronic devices. For example, the information providing system can be implemented in a server device 100 and a user device 200. In other words, the server device 100 and the user device 200 can implement the actions of various embodiments of the present invention based on the information providing system implemented in each device. On the other hand, the information providing system of various embodiments can also be implemented in more electronic devices and servers, and is not limited to the above-mentioned FIG. 1 .

The server device 100 of various embodiments may be a device that performs wired and wireless communication with a plurality of user devices 200 and includes a storage device having a large unit of storage capacity. For example, the server device 100 may be a cloud device that is connected to a plurality of user devices 200.

The user device 200 of various embodiments can be a device that can be used by a personal user, such as a desktop computer, a tablet computer, a mobile terminal, etc. In addition, other electronic devices that perform similar functions can also be used as the user device 200.

The information providing system of various embodiments may include various modules for performing actions. The modules included in the information providing system may be computer codes and one or more instructions implemented in the following manner: the physical device (e.g., the server device 100 and the user device 200) that implements the information providing system (or included in the physical device) may perform a specified action. In other words, the physical device that implements the information providing system may store a plurality of modules in the form of computer codes in a memory, and when executing the plurality of modules stored in the memory, the plurality of modules cause the physical device to perform the specified actions corresponding to the plurality of modules.

FIG. 2 is a diagram showing the configuration of a server device 100 and a client device 200 according to various embodiments.

2 , the server device 100 and the client device 200 may include an input/output unit 210 , a transceiver (or a communication unit) 220 , a memory 230 , and a processor 240 .

The input/output unit 210 may be various interfaces or ports for receiving user input or outputting information to the user. The input/output unit 210 may include an input module and an output module, and the input module receives user input from the user. User input can be implemented in various forms including key input, touch input, and audio input. As examples of input modules that can receive such user input, in addition to traditional keypads or keyboards, and mice, of course, they also include touch sensors that sense user touch, microphones that receive audio signals, cameras that recognize gestures by image recognition, proximity sensors that include at least one of an illumination sensor or an infrared sensor that senses the approach of a user, motion sensors that recognize user movements by means of an accelerometer or a gyroscope sensor, and various types of input mechanisms that sense or receive various forms of user input. The input module of the embodiments of the present invention may include at least one of the devices listed above. Here, the touch sensor can be implemented as a piezoelectric or electrostatic touch sensor that senses touch by attaching a touch panel or touch film on a display panel, an optical touch sensor that senses touch by optical means, etc. In addition, the input module can also be implemented in the form of an input interface (USB (Universal Serial Bus) port, PS/2 (Personal System 2) port, etc.) that connects to an external input device that receives user input instead of a device that senses user input itself. In addition, the output module can output various information. The output module may include at least one of a display that outputs images, a speaker that outputs sounds, a tactile device that generates vibrations, and various other forms of output mechanisms. In addition, the output module can also be implemented in the form of an output interface of a port type connected to the above-mentioned single output mechanism.

For example, the output module in the form of a display can display text, still images, and videos. The display may include a liquid crystal display (LCD), a light emitting diode (LED) display, an organic light emitting diode (OLED) display, a flat panel display (FPD), a transparent display, a curved display, a flexible display, a three-dimensional display (3D) display, a holographic display, a projector, and at least one of various devices that can implement image output functions. Such a display may be in the form of a touch display that is integrally formed with a touch sensor of the input module.

The transceiver 220 can communicate with other devices. Therefore, the server device 100 and the user device 200 can transmit and receive information with other devices through the transceiver 220. For example, the server device 100 and the user device 200 can communicate with each other or with other devices using the transceiver 220.

Here, communication, i.e., the transmission and reception of data, can be realized by wired or wireless. For this purpose, the transceiver 220 may include a wired communication module connected to the Internet via a LAN (Local Area Network), a mobile communication module connected to a mobile communication network via a mobile communication base station to transmit and receive data, a short-range communication module using a communication method such as a WLAN (Wireless Local Area Network) series of wireless fidelity (Wi-Fi) or a communication method such as a WPAN (Wireless Personal Area Network) series of Bluetooth or Zigbee, a satellite communication module using a GNSS (Global Navigation Satellite System) such as a GPS (Global Positioning System), or a combination thereof.

The memory 230 can store various information. The memory 230 can store data temporarily or semi-permanently. For example, the memory 230 of the server device 100 can store an operating system (OS) for driving the server device 100, data for hosting a website, or a program for generating braille and data related to an application (e.g., a website application). In addition, the memory can store modules in the form of computer code as described above.

Examples of the memory 230 include a hard disk drive (HDD), a solid state drive (SSD), a flash memory, a read-only memory (ROM), a random access memory (RAM), etc. Such a memory 230 can be provided in a built-in type or a removable type.

The processor 240 controls the overall operation of the server device 100 and the user device 200. To this end, the processor 240 can perform various information calculations and processing to control the operation of the components of the server device 100. For example, the processor 240 can execute programs and applications for providing information. The processor 240 can be implemented as a computer or a similar device based on hardware, software, or a combination thereof. In terms of hardware, the processor 240 can be implemented in the form of a circuit that processes electrical signals to perform control functions, and in terms of software, it can be implemented in the form of a program that drives the hardware processor 240. On the other hand, in the case where no particular mention is made in the following description, the actions of the server device 100 and the user device 200 can be interpreted as being performed under the control of the processor 240. That is, in the case of executing the module implemented in the above-mentioned information providing system, the module can be interpreted as the processor 240 controlling the server device 100 and the user device 200 to perform the following actions.

In short, various embodiments can be implemented by various mechanisms. For example, various embodiments can be implemented by hardware, firmware, software or a combination thereof.

When implemented by hardware, the methods of various embodiments can be implemented by one or more ASICs (application specific integrated circuits), DSPs (digital signal processors), DSPDs (digital signal processing devices), PLDs (programmable logic devices), FPGAs (field programmable gate arrays), processors, controllers, microcontrollers, microprocessors, etc.

When implemented by firmware or software, the methods of various embodiments can be implemented in the form of modules, processes or functions that implement the functions or actions described below. For example, the software code can be stored in a memory and driven by a processor. The memory can be located inside or outside the processor and can send and receive data with the processor through various well-known mechanisms.

The following describes various embodiments in more detail based on the above-mentioned technical ideas. For the various embodiments described below, the contents described previously can be applied. For example, actions, functions, terms, etc. that are not defined in the various embodiments described below can be implemented and described based on the contents described previously.

In the following description, various embodiments are described based on the following premise: the server device 100 is configured to store and manage a database for data. If the user device 200 transmits a request for data query to the server device 100, the server device 100 performs an action of providing information related to the data corresponding to the above request.

FIG. 3 is a diagram showing an operation method of the server device 100 for providing information according to various embodiments.

According to FIG. 3 , the server device 100 can provide information related to a data set corresponding to a request for querying data. Specifically, data source management information is obtained, and the data source management information is used to manage a data source (source). The data source is used to store event data corresponding to an event on a service in a database (301). Data storage management information is obtained, and the data storage management information is used to store event data in a database. Management is set (303) to store processed data in a database, the processed data being obtained by processing event data according to a data management format set based on data source management information and data storage management information (305), and corresponding to a data query request for searching data in the database, providing information related to a data set, the data set including one or more processed data confirmed from the database (307).

According to FIG. 3 , the action of the server device 100 providing information related to the data set may be performed for the service provided by the server device 100 or for the service related to the server device 100. The above service may be a service for a plurality of users utilizing the service to order and purchase a plurality of items sold in the service. The plurality of items sold in the service are not limited to the types or categories of items, etc., and may include various types or categories of items registered by the seller for the purpose of selling the items.

Furthermore, in FIG. 3 , the user device 200 that inputs a request for querying data is a user device 200 that corresponds to an administrator who manages data on a queryable service. After the user device 200 that corresponds to the administrator obtains a request for querying the data desired by the administrator, the request is confirmed by the server device 100, and the server device 100 can provide information related to a data set including data corresponding to the request from a database.

On the other hand, the actions of the server device 100 in FIG. 3 can be divided into actions 301 to 305 for setting up a database for storing and managing data and actions 307 for providing information related to the data in response to a data query request. Specific implementation examples of each action will be described below.

According to various embodiments, in action 301, the server device 100 may obtain data source management information, where the data source management information manages a data source, where the data source is used to store event data corresponding to an event on a service in a database.

For example, an event on a service may be an event that occurs based on an action taken by a user on the service. For example, after a user takes an action to purchase an item on the service, the action may be confirmed as an event and event data related to the confirmed event may be generated. The data generated as described above may include data of the user who is the subject of the action to purchase the item, data of the item that is the object of the action to purchase the item, and/or data such as the price of the item confirmed based on the action to purchase the item, the order quantity, etc.

For example, event data corresponding to events on a service may be queued based on a message queue, which includes one or more message queues. The message queue may include Kafka, which exposes, subscribes to, stores, and processes real-time streaming data. Kafka, as a large-capacity real-time log processing system, may be a message queue system that processes messages using a publish/subscribe paradigm. Event data corresponding to events on a service may be queued based on Kafka.

For example, the data source management information may include information of one or more data sources for queuing event data on the service through a message queue. That is, the information of the data source may be included in the data source management information, and the data source becomes the basis for queuing the event data to be transmitted to the message queue.

For example, the first data source included in the one or more data sources confirmed in the data source management information may be a data source corresponding to the first topic in one or more Kafka topics corresponding to one or more message queues for queuing event data. That is, each topic included in Kafka sets a single data source corresponding to each message queue and used to queue event data through each message queue, thereby setting each data source for each topic.

For example, the information of the first data source included in the data source management information may include information related to the first topic corresponding to the first data source. As an example, the information related to the above-mentioned first topic included in the data source management information may include information for confirming the subject of data that performs an action on the service to generate event data corresponding to the first topic. For the first topic corresponding to the first data source included in the data source management information, information for confirming the subject of data that generates data belonging to the first topic on the service is set in the data source management information, thereby enabling the first data source to be set in a manner of queuing event data, which is confirmed to be generated on the service by the subject of fixed data for the first topic. If the event data generated by the userId (user identifier) of an ordinary user on the service for the first question is confirmed as a queued object, then the event data generated by the ordinary user on the service performing actions related to the first question on the service using the user identifier can be queued using the message queue corresponding to the first question.

After configuring each data source for each message queue using the data source management information, you can complete the configuration of the data source for the database.

FIG. 4 is a diagram showing an example of a situation in which data source management information is set.

By setting the data source management information as shown in FIG. 4 , a data source can be set for queuing event data corresponding to a specific topic through a message queue. In particular, in FIG. 4 , a data source (401) can be set for queuing event data corresponding to the “Payment” topic in Kafka.

In FIG. 4 , the information user identifier of the subject that confirms the data of the action that generates the event data corresponding to the “Payment” topic on the service can be specified, so that the event data generated by the action related to the “Payment” topic including the specified subject can be queued by the message queue corresponding to the “Payment” topic. At this time, the information of the subject that confirms the data corresponding to the “Payment” topic can be set as the field (403) mapped as the data source as described above.

After setting the information for confirming the subject of the data as 403 by the data source management information of FIG. 4, the data item corresponding to the event data among the multiple data items included in the "Payment" title can be confirmed in the data storage management information for managing the database setting as described below. The event data is generated due to the subject of the data set in the data source management information. In addition, a format for management in the following manner can be set: each data value in the event data corresponding to each data item confirmed based on the data storage management information is stored in correspondence with the subject of the above data and each data item.

According to various embodiments, in action 303, the server device 100 may obtain data storage management information for managing database settings for storing event data in the database.

For example, data storage management information can be set for a specific data source of a database or for a specific topic corresponding to a specific data source. Data storage management information can also be set to process and store event data based on data sources or topics.

For example, the data storage management information may include identification information for identifying the subject of data confirmed for a topic corresponding to a data source. For example, for a first data source included in one or more data sources used in a database, the data storage management information may include identification information of the subject of the data so that the subject of data confirmed for a first topic set to correspond to the first data source can be identified in the data source management information. For example, for the first question corresponding to the first data source, if the event data generated by the user identifier of the user is confirmed as a queued object, it can be managed in the following manner: identification information is generated based on the mail ID, terminal ID, etc. that can identify the user identifier of the user, and the subject of the data is identified in the database based on the identification information.

For example, the identification information on the data storage management information that identifies the subject of the data for the subject corresponding to the data source may specifically be information generated based on one of the customer ID (Identifier) of the user on the service, the email ID of the user on the service, the IP (Internet Protocol) address of the user on the service, and/or the terminal ID of the user on the service. For example, it is generally recognized that the subject of data generated on the service is an ordinary user. Therefore, identification information generated based on various identifiers such as customer ID, email ID, IP (Internet Protocol) address, terminal ID, etc. that can identify ordinary users on the service can be included in the data storage management information. In this way, data can be classified and stored in the database for management according to the identification information.

For example, event data generated by identifying the subject of data through identification information can also be set in the following manner: the values of each data are distinguished according to the data items on the topic that classifies the object of the data and stored in the database, so that data storage management information can be used.

A Kafka topic corresponding to a data source may include multiple data items, and event data generated by the subject of the above data may correspond to more than one data item in the topic according to the object including the event data. For example, the "Payment" topic may include data items such as "amount", "count", and "ip (Internet Protocol)", and the event data generated by the user's settlement action on the service may include the value of each data corresponding to each data item included in the above data items. At this time, by using data storage management information, it can be set in the following manner: the event data is processed into data including the values of the data items "amount" and "count" in the above data items and stored in the database. In this case, the event data can be processed into processed data and stored in the database. The processed data includes the value of the data corresponding to "amount" and the value of the data corresponding to "count" among the various values of the event data.

For example, if a specific topic corresponding to a specific data source is specified in the data source management information, a plurality of data items included in the specific topic can be confirmed, but in this case, the data storage management information may include the following information: specifying a portion of the data items used to be processed into data in the event data to be stored in the database among the plurality of data items confirmed as described above. In other words, the data storage management information may be information including one or more data items corresponding to the topic specified in the data source management information.

For example, the data storage management information may include information about the validity period of data stored in the database. That is, the data storage management information may be used to set how long the data can be kept in the database. For example, the data storage management information may be set in such a way that a piece of data is stored in the database for one week.

For example, the data storage management information may include information for setting the form of listing and storing data in the database to the column form of the main body of the data.

FIG. 5 is a diagram showing an example of a state of setting data storage management information.

The format of data stored in the database can be determined by setting the data storage management information as shown in FIG. 5 . In particular, in FIG. 5 , “validity period”, “identification information”, “row (column)” and “data item” (501) can be set by the data storage management information.

Specifically, 1) in the case of "validity period", the data is set to be stored in the database for 7 days, and 2) in the case of "identification information (Row Key)", a hash value may be added to one of the user's mail ID, customer ID, IP (Internet Protocol) address, and terminal ID for identifying the user on the service corresponding to the subject of the data, and the identification information generated as described above may be used when storing the data in the database to associate with the user. Furthermore, 3) in the database, data can be managed in the form of columns set as user identification information, and 4) in order to store data in the database, specific data items (amount, ip, count, etc.) to be stored can be set in the subject specified in the data source management information (503).

The format of data stored in the database can be determined by setting the data storage management information as shown in FIG. 5 , and the data can be stored in the database according to the form of FIG. 6 described below based on the determined format.

According to various embodiments, in action 305, the server device 100 can be configured in the following manner: according to a data management format configured based on data source management information and data storage management information, the processed data obtained by processing the event data is stored in a database.

For example, the data management format used to process data and store it in a database may be a format in which data is organized based on identification information that identifies the subject of data corresponding to a topic. As an example, the data management format may be a format in which data is managed by classifying it in a row format set according to the unit of identification information that identifies the subject of data. That is, the data management format may be set in the following manner: the identification information that identifies the subject of data is set as a row, and the object data on various data items related to the subject of the data is set as a row corresponding to the above-mentioned row.

When information of one or more data items included in a specific topic is included in data storage management information for managing database settings, the data management format can be set in the following manner: identification information for identifying the subject of data is set as a row, and the one or more data items are set as rows (columns) corresponding to the above-mentioned rows. For this purpose, for the first data item included in the above-mentioned one or more data items, the data storage management information can include information for management in the following manner: when a plurality of data are confirmed corresponding to the identification information in the first data item, the plurality of data are set in the form of rows (columns) of the above-mentioned first data item corresponding to the above-mentioned identification information.

That is, the data management format may be in the following format: taking identification information for identifying a data subject corresponding to a specific topic as an object, each data item included in one or more data items corresponding to the specific topic and one or more data confirmed in each of the above data items corresponding to the identification information are classified and managed in a row format corresponding to the above identification information.

As a result, the processed data obtained by processing the event data according to the data management format may include identification information for identifying a data subject corresponding to a topic included in the data source management information, each data item included in one or more data items set corresponding to the topic in the data storage management information, data values confirmed in the event data based on the above data subject and the above data items, and the time point when the event data is obtained on the service.

FIG. 6 is a diagram showing an example of storing data in a database according to a data management format.

In FIG. 6 , with the row of identification information (Row Key) generated to identify the user on the service as the center, in each data item ("ip", "amount", "count") storing data in the database corresponding to a fixed topic ("Payment"), multiple data confirmed for the above identification information can be stored in the rows of each data item.

Specifically, for the user (601) having the identification information of "237289098", 1) in the data item "ip" included in the title "Payment", multiple data confirmed for the above user can be listed in row form and stored (603), 2) in the data item "amount" included in the title "Payment", multiple data confirmed for the above user are also listed in row form and stored (606), 3) in the data item "count" included in the title "Payment", multiple data confirmed for the above user are also listed in row form and stored (607).

At this time, each processed data stored in FIG6 includes the time point (timestamp) when the event data corresponding to the processed data is obtained on the service, the specific value of the data, etc. Each processed data of each data item generated according to an event can include the same timestamp value as confirmed in the processed data of multiple data items included in one row.

By using the data management format as shown in FIG6 , data of users other than the user having the identification information of "237289098" can be appended as a new row and stored in the database. In addition to "ip", "amount", and "count", if the data storage management information is also set in a data storage manner for other data items included in the subject "Payment", then data processed in a manner classified as the other data items can be appended to a new row used for the other data items and stored in the database.

In addition, for new topics other than the topic "Payment", the data management format such as Figure 6 can be re-managed according to the settings of the data source used for the new topic and the settings of the data items included in the new topic.

According to FIG. 4 to FIG. 6 , an example of the situation where event data is converted into processed data and stored in a database can be shown in FIG. 7 .

FIG. 7 is a diagram showing an example of a state in which processed data obtained from event data is stored in a database.

In FIG. 7 , after confirming the event data (business data) obtained from the event occurring on the service, the event data can be queued by the message queue ( 701 ), thereby being obtained and stored in the database as processed data conforming to the data management format set based on the data source management information and the data storage management information.

The data storage management information used to set up the database can be set in a manner that identifies the subject of the data used to indicate the topic in the pre-set data source management information (Row Key) and the data item (qualifier) indicating the stored data on the topic (703). Data can be stored in the following data management format: based on the data storage management information, the user's identification information is set as a row, and each data item included in the topic and the data corresponding to each data item are set as a column (705).

According to various embodiments, in action 307, the server device 100 may provide information related to a data set in response to a data query request for querying data from a database, wherein the data set includes one or more processed data confirmed from the database.

For example, the data query request may be a request for querying data received and confirmed by the server device 100 from the external user device 200, etc. The data query request as described above includes input information required for querying data. In this case, the input information required for querying data may be information set based on a data management format. That is, the data stored in the database is data processed according to a fixed data management format. Therefore, in order to query the processed data, it can be managed by setting input information that conforms to the data management format. When the data query request includes the input information as described above, the server device 100 can confirm the processed data corresponding to the received data query request from the database.

For example, a data query request may include information about a subject for querying data and information about a data operator for the subject. When querying data, the user device 200 that wants to query data may input the subject desired by the user device 200 and the data operator required for the desired subject for the data query request. The server device 100 may confirm the processing data for the subject in accordance with the subject and the data operator included in the data query request and perform operations on the confirmed processing data according to the data operator. In addition, when providing information related to the processing data confirmed in accordance with the data query request, the server device 100 may be set in a manner including the result obtained by performing operations on the processing data according to the data operator. That is, according to action 307, the information related to the data set that can be provided by the server device 100 includes information on the result of operating one or more processed data included in the data set according to the data operator.

For example, the data query request may include information about the query period for querying data. That is, when querying data, the user device 200 that wants to query data may input the desired query period for the data query request, and the server device 100 may confirm the processing data in the database corresponding to the query period included in the data query request, and the processing data is confirmed as the time point when the event data is obtained on the service is included in the above query period.

For example, a data query request may include information about a data subject and a data item for querying data. That is, the user device 200 that wants to query data may input a data subject and a data item for specifying the desired data in order to confirm the value of the desired data.

As described above, after obtaining a data query request including input information such as a subject, a data body, a data item, a data operator, and a query period for querying data, the server device 100 can confirm the processed data filtered by the input information in the database.

FIG. 8 is a diagram showing an example of input information for requesting query data.

The data query request of FIG8 can be set in a manner to obtain input information that is confirmed to be necessary according to the data management format set for the database, and the administrator can input various information used for the data query request through the user device 200 User Interface (UI/UX) in the form of FIG8. Here, setting the input information used for the data query request can also be understood as setting the feature of the information used to obtain the desired processing data from the database.

The data query request of FIG. 8 can be set by inputting matters related to 1) a subject 801 for querying data, 2) a data subject and data item 803 for querying data, 3) a query period 805 for querying data, and 4) a data operator 807 for the subject of the data query. In FIG. 8 , based on the data summation operator (Calc-function: SUM-I), it can be confirmed that input information is set, which is used to calculate the accumulation (FeatureName and DataView) of the data for 3 days (Calc-window: 3d) included in the price data item (Oubject Target: Amount) corresponding to the subject (Subject Target: User Identifier) of the fixed data.

As shown in FIG8 , after obtaining a data query request including various input information, the server device 100 can confirm one or more processed data corresponding to the above data query request in the database, and then provide information including a data set and a calculation result to the user device 200, wherein the data set includes the above one or more processed data, and the calculation result is obtained by calculating the above one or more processed data included in the above data set according to the data query request.

FIG. 9 is a diagram showing an example of a data operator that may be set in a data query request.

The data operators may include various operators that are determined to be supported for data stored in the database, and the data operators that are determined to be supported for the data may be determined based on whether the data type is a number or a string.

In the example of FIG. 9 , as a function for a data operator, it can be confirmed that the following various operators can be set: accumulation of data (Sum-I), number of data (Count-I), maximum value in data (Max-I), minimum value in data (Min-I), average of data (Avg-I), etc.

FIG. 10 is a diagram showing an example of a situation in which information related to a data set including processed data corresponding to a data query request is provided.

FIG. 10 shows the following situation: with identification information of a specific user used for a service as an object, the calculation result of the processed data corresponding to each data item ("ip", "amount") included in a fixed topic ("Payment") is provided.

First, among the three processed data included in the "ip" data item, 1) may provide information indicating that the calculation result is 2 in response to a data query request for confirming the number of each IP individual included in the processed data having a timestamp value in the past hour (1001). Also, 2) may provide information indicating that the calculation result is 3 in response to a data query request for confirming the total number of IP individuals included in the processed data having a time point value in the past hour (1003), or 3) may provide information indicating each IP address corresponding to the calculation result in response to a data query request for confirming a list of IP individuals included in the processed data having a time point value in the past hour (1005).

Among the three processing data included in the "amount" data item, 4) can provide information (1007) indicating that the calculation result is 96.9 in response to a data query request for confirming the overall cumulative value of the transaction price included in the processing data having a point value within a 1-hour period within the past 1 day.

11 and 12 are diagrams showing the overall state of the present invention in which the server device 100 sets up a database based on a data management format and provides information corresponding to a data query request.

In 1101 of FIG. 11 , the server device 100 sets up a database in the form of FIG. 7 , so that management can be performed in the following manner: event data obtained on the service is converted into processed data that conforms to a fixed data management format for storage. In addition, the server device 100 confirms the data query request or feature related to the data query request obtained from the user device 100 as in 1103 , confirms the processed data that conforms to the data query request or feature, and can provide information including the confirmed processed data and the calculation result of the confirmed processed data.

FIG12 is an example of an information providing system that generalizes the operation of the server device 100 of FIG11. The system of FIG12 may include a structure that manages in the following manner: event data that conforms to a pre-set data source and subject may be processed according to a fixed data management format and the processed data may be stored in a database (1201), or a structure that manages in the following manner: processing data that conforms to the characteristics of a data query request obtained from the outside is confirmed and operated, and information related thereto is provided (1203). In addition, in the information provision system of FIG. 12 , a structure for management can also be constructed in the following manner: learning various characteristics used to query data and providing information corresponding to the various characteristics, thereby comparing and feeding back the information provided in response to actual data query requests, thereby reflecting on the decision-making used for the service (1205).

It should be understood that, according to FIGS. 3 to 12 , the information used in the process of the server device 100 implementing the method for providing information can be combined in various forms.

The embodiments of the present invention disclosed in this specification and the attached drawings are specific examples provided to easily explain the technical content of the present invention and to help understand the present invention, and are not intended to limit the scope of the present invention. That is, those with common sense in the technical field to which the present invention belongs should understand that other variations based on the technical ideas of the present invention can be implemented. In addition, the above-mentioned embodiments can be combined with each other as needed. For example, all embodiments of the present invention can be combined with a part of each other and implemented by a system.

Furthermore, the methods corresponding to the system of the present invention can be implemented in the form of program commands executed by various computer mechanisms and recorded in a computer-readable medium.

As described above, in certain aspects, various embodiments of the present invention may be implemented in a computer readable recording medium by computer readable code. A computer readable recording medium is any data storage device that can store data that can be read by a computer system. Examples of computer readable recording media may include read only memory (ROM), random access memory (RAM), compact disk-read only memory (CD-ROM), magnetic tape, floppy disk, optical data storage device, and carrier wave (data transmission via the Internet, etc.). The computer-readable recording medium can also be distributed through computer systems connected by the Internet, so that the computer-readable code is stored and executed in a distributed manner. In addition, the functional programs, codes and code segments used to implement various embodiments of the present invention can be easily interpreted by a skilled programmer in the field of application of the present invention.

Furthermore, it is understood that the devices and methods of various embodiments of the present invention may be implemented in the form of hardware, software, or a combination of hardware and software. Such software may be stored, for example, in a volatile or non-volatile storage device such as a ROM, or a memory such as a RAM, a memory chip, a device or an integrated circuit, or a storage medium such as a compact disk (CD), a DVD (Digital Versatile Disc), a disk or a tape that can be recorded optically or magnetically and can be read by a machine (e.g., a computer), regardless of whether it is erasable or re-recordable. It can be known that the methods of various embodiments of the present invention can be implemented by a computer including a control unit and a memory or a vehicle including the memory or computer as described above. Such a memory is an example of a storage medium that includes a program that includes commands for implementing the embodiments of the present invention or can be read by a machine suitable for storing programs.

Therefore, the present invention includes a program of code for realizing the device or method described in the scope of the invention application of this specification, and a storage medium readable by a machine (computer, etc.) storing such a program. In addition, such a program can be electronically transferred by any medium such as using a wired or wireless connection to transmit a communication signal, and the present invention appropriately includes its equivalent content.

The above description is made with reference to the embodiments of the present invention, but the embodiments of the present invention disclosed in this specification and drawings are only specific examples provided to easily explain the technical content of the present invention and to help understand the present invention, and are not intended to limit the scope of the present invention. In addition, it can be understood that the embodiments of the present invention described above are only examples, and those with common sense in the field can realize various variations and equivalent embodiments based on them. Therefore, the true technical protection scope of the present invention should be defined according to the following invention patent application scope.

100: Server Devices

200: User Device

210: Input/output unit

220: Transceiver

230: Storage

240:Processor

301: Action

303: Action

305: Action

307: Action

401:Action

403:Action

501:Action

503:Action

601:Action

603:Action

605:Action

607: Action

701:Action

703:Action

705:Action

801: Theme

803: Data Subject and Data Items

805: Query period

807: Data Operator

1001:Action

1003:Action

1005:Action

1007:Action

1101:Action

1103:Action

1201:Action

1203:Action

1205:Action

FIG. 1 is a diagram for explaining an information providing system that can realize the operation method of an electronic device for providing information of various embodiments. FIG. 2 is a diagram showing the configuration of a server device 100 and a user device 200 of various embodiments. FIG. 3 is a diagram showing the operation method of a server device 100 for providing information of various embodiments. FIG. 4 is a diagram showing an example of a state of setting data source management information. FIG. 5 is a diagram showing an example of a state of setting data storage management information. FIG. 6 is a diagram showing an example of a state of storing data in a database according to a data management format. FIG. 7 is a diagram showing an example of a state of storing processed data obtained from event data in a database. FIG. 8 is a diagram showing an example of input information for requesting data query. FIG. 9 is a diagram showing an example of a data operator that can be set in a data query request. FIG. 10 is a diagram showing an example of a state of providing information related to a data set including processed data corresponding to a data query request. FIG. 11 to FIG. 12 are diagrams showing the overall state of the present invention in which the server device 100 sets a database based on a data management format and provides information corresponding to a data query request.

301:Action

303:Action

305:Action

307:Action

Claims (18)

An information providing method, which is for an electronic device to provide information, comprises the following steps: obtaining data source management information, the data source management information is for managing a data source, the data source is used to store event data corresponding to an event on a service related to the electronic device in a database; obtaining data storage management information, the data storage management information is for managing a database setting for storing the event data in the database; setting the processing data in the database in a manner of storing the processing data in the database; Processed data is obtained by processing the above event data according to the data management format set based on the above data source management information and the above data storage management information; and corresponding to the data query request used to query data in the above database, provides information related to the data set, the data set includes one or more processed data confirmed from the above database; wherein the above data query request includes input information required for querying data, and the above input information required for querying data is set based on the above data management format. As in the information providing method of claim 1, the event data is queued based on a message queue, and the message queue includes more than one message queue. The information providing method of claim 2, wherein the data source management information includes information of more than one data source, the first data source included in the more than one data source corresponds to the first topic, and the first topic is selected for the first data source from one or more topics corresponding to the more than one message queue. As in the information providing method of claim 3, the information of the first data source included in the data source management information includes the information of the data subject corresponding to the first topic. As in the information providing method of claim 3, the data storage management information includes identification information for identifying the data subject corresponding to the above-mentioned question 1. The information providing method of claim 5, wherein the identification information is generated based on one of the customer ID of the user on the service, the email ID of the user, the IP address of the user, and the terminal ID of the user. As in the information providing method of claim 5, the data management format is managed by classifying the data in a row format, and the row format is set according to the unit of the identification information. As in the information providing method of claim 3, the data storage management information includes information of one or more data items corresponding to the above-mentioned question 1. In the information providing method of claim 8, when multiple data related to the data subject corresponding to the above-mentioned first topic are confirmed in the first data item included in the above-mentioned one or more data items, the above-mentioned data storage management information includes information for setting the above-mentioned multiple data to the row form of the above-mentioned first data item corresponding to the above-mentioned data subject. As in the information providing method of claim 9, for the identification information for identifying the data subject corresponding to the first question, the data management format manages by classifying each data item included in one or more data items corresponding to the first question and one or more data confirmed for the data subject in each data item in a row format corresponding to the identification information. As in the information providing method of claim 1, the data storage management information includes information on the validity period of the data stored in the database. The information providing method of claim 1, wherein the processed data includes: identification information for identifying a data subject corresponding to a topic included in the data source management information; a data item set in the data storage management information corresponding to the topic; a data value confirmed in the event data based on the data subject and the data item; and a time point when the event data is obtained on the service. As in the information providing method of claim 1, the data query request includes information about the subject for querying the data and information about the data operator for the subject. As in the information providing method of claim 13, the information related to the above-mentioned data set includes information on the result obtained by operating the above-mentioned one or more processed data based on the above-mentioned data operator. As in the information providing method of claim 1, the data query request includes information about the query period used to query the data. As in the information providing method of claim 15, each of the processing data included in the above-mentioned one or more processing data is confirmed based on the point in time when each event data corresponding to the above-mentioned processing data is obtained on the above-mentioned service is included in the point in time during the above-mentioned query period. Such as the information provision method of request item 1, wherein the above data query request includes information on the data subject and data item used to query the data. An electronic device that provides information includes: a processor; and one or more memories that store one or more instructions; and when executing the one or more instructions, the processor is controlled to perform the following steps: obtaining data source management information, the data source management information is used to manage a data source, the data source is used to store event data corresponding to an event on a service related to the electronic device in a database; obtaining data storage management information, the data storage management information is used to manage a database setting used to store the event data in the database; ; set in a manner to store processed data in the above database, the processed data is obtained by processing the above event data according to the data management format set based on the above data source management information and the above data storage management information; and provide information related to a data set corresponding to a data query request for searching data in the above database, the data set includes one or more processed data confirmed from the above database; wherein the above data query request includes input information required for searching data, and the above input information required for searching data is set based on the above data management format.