Malfunction information providing method, electronic device for the same, and non-transitory computer-readable recording medium comprising a computer program for performing the method

Abstract

According to the present invention, a method and electronic device for providing malfunction information are disclosed, comprising the following steps: obtaining malfunction information of a page provided to a user terminal; and providing malfunction information of the page to an administrator terminal based on the malfunction information; wherein the malfunction information includes identification information of the page, information of the program associated with the malfunction, and information of the cause of the malfunction.

Description

Technical Field

[0001] This invention relates to a method and electronic device for providing malfunction information to an administrator terminal by monitoring malfunctions on a page provided to a user terminal. Prior Technology

[0002] With the widespread use of the Internet, Internet-based services are being provided in various fields. In particular, e-commerce, in which buyers and sellers can conduct real-time transactions by connecting to online shopping malls via terminals, is developing rapidly.

[0003] In operating Internet-based services for e-commerce, it is necessary to monitor malfunctions in applications provided to user terminals, identify the causes of malfunctions when they occur, and resolve them quickly. Therefore, methods for monitoring malfunctions in applications provided to user terminals and methods for reporting information related to malfunctions are being discussed.

[0004] For related information, see previous references such as KR 10-1655800B1 and KR 10-1202941 B1. Summary of the Invention

[0005] [The problem the invention aims to solve] The purpose of this invention is to provide a method and electronic device for providing malfunction information by monitoring malfunctions on a page provided to a user terminal and providing malfunction information to an administrator terminal.

[0006] The technical problem to be achieved by the present invention is not limited to the technical problem described above, and other technical problems can be derived from the following examples. [Technical means to solve the problem]

[0007] One embodiment of the disclosed method for providing malfunction information may include the following steps: obtaining malfunction information of a page provided to a user terminal; and providing malfunction information of the page to an administrator terminal based on the malfunction information; wherein the malfunction information includes identification information of the page, information of the program associated with the malfunction, and information of the cause of the malfunction.

[0008] The aforementioned malfunction message can be obtained from at least one of the aforementioned user terminal, the first server that provides the aforementioned page to the aforementioned user terminal, and the second server that processes the user's input information for the aforementioned page.

[0009] When the aforementioned erroneous operation message is obtained from the aforementioned user terminal, the steps of obtaining the aforementioned erroneous operation message may include the following steps: obtaining the aforementioned erroneous operation message from the log transmitter of the aforementioned user terminal, wherein the log transmitter is configured to store and transmit logs associated with the aforementioned page.

[0010] Information associated with the aforementioned malfunction may include information associated with at least one of the following steps: a first step in which the user terminal prepares first data to request the aforementioned page; a second step in which the user terminal transmits the first data to a first server that provides the aforementioned page to the user terminal; a third step in which the first server processes the first data to generate second data associated with the aforementioned page; a fourth step in which the user terminal receives the second data from the first server; and a fifth step in which the user terminal processes the second data.

[0011] The steps to obtain the above-mentioned malfunction information may include the following steps: obtaining information associated with at least one UI included in the above-mentioned page; and sensing whether there is a malfunction based on the information associated with the above-mentioned at least one UI.

[0012] The steps to obtain information associated with at least one UI may include the following steps: obtaining statistical information on multiple user inputs to at least one UI obtained in a time series.

[0013] The steps for sensing whether there is any malfunction may include the following: confirming whether there is any malfunction based on whether the statistical information is within the set benchmark range.

[0014] The above-mentioned baseline range may vary depending on the type of malfunction.

[0015] The steps to obtain information associated with at least one of the above-mentioned UIs may include the following steps: obtaining a captured image of the above-mentioned page that includes at least one of the above-mentioned UIs.

[0016] The steps for sensing whether there is the above-mentioned malfunction may include the following steps: confirming whether there is a malfunction based on the reference image during normal operation and the above-mentioned captured image.

[0017] The aforementioned malfunction messages may further include domain information corresponding to the aforementioned administrator terminal.

[0018] An electronic device for providing malfunction information according to one embodiment may include: a memory storing at least one command; and a processor that, based on the at least one command, obtains malfunction information of a page provided to a user terminal, and provides malfunction information of the page to a management terminal based on the malfunction information; wherein the malfunction information includes identification information of the page, information of the program associated with the malfunction, and information of the cause of the malfunction.

[0019] Specific details of other embodiments are included in the detailed description and drawings. [Effects of the Invention]

[0020] According to the present invention, malfunctions can be detected by optimizing the causes of malfunctions, and the information on the malfunctions can be efficiently transmitted to the management terminal.

[0021] The effects of the invention are not limited to those mentioned above. Those with common knowledge in the relevant technical field can clearly understand other effects not mentioned based on the description in the scope of the patent application. Simple Explanation of the Diagram

[0022] Figure 1 is a conceptual diagram of an electronic device used to illustrate an embodiment of the present invention for providing malfunction information. Figure 2 is a schematic block diagram illustrating an embodiment of the present invention, showing the server and terminal. Figure 3 is a flowchart illustrating the method for providing malfunction information according to an embodiment of the present invention. Figure 4 is a conceptual diagram used to illustrate the procedures associated with malfunctions. Figure 5 is a page illustrating the steps of obtaining malfunction information in the malfunction information provision method according to an embodiment of the present invention. Figures 6 to 9 are conceptual diagrams illustrating the method for providing malfunction information according to embodiments of the present invention. Implementation

[0023] The terminology used in the embodiments has been selected as widely used and common terms as possible while considering the functions of this invention. However, it may vary depending on the intent of those skilled in the art, precedents, or the emergence of new technologies. Furthermore, in certain situations, terms arbitrarily chosen by the applicant may exist; in such cases, their meanings will be detailed in the corresponding description. Therefore, the terminology used in this invention should be defined based on its meaning and the overall content of the invention, rather than simply on the name of the term.

[0024] When a component is mentioned throughout the specification as "including" another component, it means that, unless otherwise stated, other components are not excluded, but rather may be included. Furthermore, terms such as "...part" and "...module" in the specification 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.

[0025] The expression "at least one of a, b and c" as used throughout the specification may include "a alone", "b alone", "c alone", "a and b", "a and c", "b and c", or "all three of a, b and c".

[0026] The term "terminal" as used below can refer to a computer or portable terminal that can connect to a server or other terminal via a network. Here, a computer includes, for example, a laptop, desktop, or notebook computer equipped with a web browser. A portable terminal is a wireless communication device that ensures portability and mobility, and may include communication terminals such as those using IMT (International Mobile Telecommunication), CDMA (Code Division Multiple Access), W-CDMA (W-Code Division Multiple Access), and LTE (Long Term Evolution), as well as all types of handheld wireless communication devices such as smartphones and tablets.

[0027] The embodiments of the present invention will now be described in detail with reference to the accompanying drawings to enable those skilled in the art to readily implement the invention. However, the present invention can be implemented in various different forms and is not limited to the embodiments shown herein.

[0028] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

[0029] In describing the embodiments, descriptions of technical content well-known in the technical field to which this invention pertains and not directly related to this invention are omitted. This is because omitting redundant descriptions clearly conveys the essence of the invention, thus avoiding confusion regarding its main points.

[0030] For the same reason, some components are exaggerated, omitted, or approximated in the accompanying drawings. Furthermore, the dimensions of each component do not perfectly reflect their actual dimensions. In each drawing, the same or corresponding components are labeled with the same reference symbols.

[0031] The advantages and features of the present invention, as well as the methods for achieving such advantages and features, will become clear from the accompanying drawings and the embodiments described in detail below. However, the present invention is not limited to the embodiments disclosed below and can be implemented in various different forms. These embodiments are provided merely to fully disclose the invention and to enable those skilled in the art to fully understand the scope of the invention. The invention is defined only by the claims of the present invention. Throughout this specification, the same reference numerals denote the same constituent elements.

[0032] At this point, it should be understood that the blocks of the flowchart and the combination of the flowchart can be implemented by computer program commands. These computer program commands can be loaded onto the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment. Therefore, the commands executed by the processor of the computer or other programmable data processing equipment produce methods for implementing the functions described in the blocks of the flowchart. To implement the functions in a specific manner, these computer program commands can be stored in computer-usable or computer-readable memory that is accessible to a computer or other programmable data processing equipment. Therefore, the commands stored in computer-usable or computer-readable memory can also produce manufactured items including command methods that implement the functions described in the blocks of the flowchart. The computer program commands can also be loaded onto a computer or other programmable data processing equipment. Therefore, a series of action steps are performed on the computer or other programmable data processing equipment to produce a flow executed by the computer. Thus, the commands executed by the computer or other programmable data processing equipment can also provide steps for executing the functions described in the blocks of the flowchart.

[0033] Furthermore, each block may represent a portion of a module, fragment, or code that includes one or more executable commands for performing a specific logical function. It should also be noted that in some alternative embodiments, the functions mentioned in the blocks may be generated out of order. For example, two blocks shown consecutively may be executed substantially simultaneously, or occasionally in reverse order depending on their respective functions.

[0034] Figure 1 is a conceptual diagram of an electronic device used to illustrate an embodiment of the present invention for providing malfunction information.

[0035] Referring to FIG1, the malfunction information provision method of the embodiments of the present invention can be implemented in various types of devices. For example, the malfunction information provision method of the embodiments of the present invention can be implemented in electronic device 110. In other words, electronic device 110 can perform the actions of the embodiments of the present invention based on the implemented malfunction information provision method. On the other hand, the malfunction information provision method of the embodiments of the present invention is not limited to the content shown in FIG1, and can also be implemented in various electronic devices, terminals, and servers. In the present invention, electronic device 110 can be a monitoring server.

[0036] The electronic device 110 of the present invention may be a device that performs wired or wireless communication with at least one device connected to the electronic device 110 and includes a memory with a large storage capacity. For example, the electronic device 110 may be a cloud device connected to at least one device. According to the embodiments, the electronic device 110 may be connected to and perform wired or wireless communication with each of the user terminal 120, the first server 130, the second server 140, and the administrator terminal 150.

[0037] In embodiments of the present invention, the user terminal 120 and the administrator terminal 150 connected to the electronic device 110 can each be at least one of a desktop computer, a tablet computer, and a mobile terminal. In addition, other electronic devices performing similar functions can also be used as the user terminal 120 and the administrator terminal 150 connected to the electronic device 110.

[0038] In embodiments of the present invention, the electronic device 110 and the first server 130 and second server 140 connected to the user terminal 120 can each be at least one of a desktop computer, a tablet computer, and a mobile terminal. Alternatively, other electronic devices performing similar functions can also be used as the electronic device 110, the first server 130, and the second server 140 connected to the user terminal 120.

[0039] Figure 1 shows that user terminal 120, first server 130, and second server 140 are not connected to administrator terminal 150, but are connected to electronic device 110, i.e., the monitoring server. However, this is only an example, and the present invention is not limited thereto. In other words, at least one of user terminal 120, first server 130, and second server 140 can also be directly connected to administrator terminal 150 and perform wired or wireless communication. Also, Figure 1 shows that first server 130 and second server 140 are not directly connected to each other, but are connected to electronic device 110 and user terminal 120. However, this is only an example, and the present invention is not limited thereto. In other words, first server 130 and second server 140 can also be directly connected to each other and perform wired or wireless communication.

[0040] Various modules can be provided for actions used in embodiments of the present invention. A module can be computer code or one or more commands implemented in a manner that enables a physical device (e.g., electronic device 110) implementing a method for providing malfunction information (or included in a physical device) to perform a specified action. In other words, the physical device implementing the method for providing malfunction information stores multiple modules in memory in the form of computer code. When executing the multiple modules stored in memory, the multiple modules can cause the physical device to perform a specified action corresponding to the multiple modules.

[0041] Figure 2 is a schematic block diagram illustrating an electronic device and operator terminal according to an embodiment of the present invention.

[0042] Referring to FIG2, the electronic device 110, the user terminal 120 connected to the electronic device 110, the first server 130, the second server 140 and the administrator terminal 150 may each include a communication unit 210, a memory 220 and a processor 230.

[0043] According to the embodiment, each of the electronic device 110, the user terminal 120 connected to the electronic device 110, the first server 130, the second server 140, and the administrator terminal 150 may further include an input section and an output section. Each of the input section and the output section may be various interfaces or ports for receiving user input or outputting information to the user.

[0044] The input unit may include an input module that receives user input from the user. User input can be implemented in various forms, such as key input, touch input, and voice input. Examples of input modules capable of receiving such user input include: conventional numeric keypads or keyboards, mice, touch sensors that sense user touch, microphones that receive voice signals, cameras that recognize gestures via image recognition, proximity sensors including at least one of an illuminance sensor or an infrared sensor that senses user proximity, motion sensors that recognize user movements via accelerometers or gyroscopes, and various types of input mechanisms that sense or receive user input in various forms. An embodiment of the present invention may include at least one of the devices listed above. Here, the touch sensor may be implemented as a piezoelectric or electrostatic touch sensor that senses touch via a touch panel or touch film attached to the display panel, or an optical touch sensor that senses touch via optical means. In addition, the input module can also be implemented in the form of an input interface (USB (Universal Serial Bus) port, PS / 2 port, etc.) that connects to an external input device that receives user input, rather than a device that senses user input itself.

[0045] On the other hand, the output section may include an output module, which can output various types of information. The output module may include at least one of the following: a display for outputting images, a speaker for outputting sound, a tactile device for generating vibrations, and other types of output devices. Furthermore, the output module may also be implemented as a port-type output interface connecting the aforementioned individual output devices. For example, a display-type output module can display text, still images, and videos. Displays may include at least one of the following: liquid crystal displays (LCDs), light-emitting diode displays (LEDs), organic light-emitting diode displays (OLEDs), flat panel displays (FPDs), transparent displays, curved displays, flexible displays, 3D displays, holographic displays, projectors, and other devices capable of performing image output functions. Such displays may also be in the form of a touch display integrated with the touch sensor of the input module.

[0046] The communication unit 210 can communicate with other devices. Therefore, the electronic device 110, the user terminal 120 connected to the electronic device 110, the first server 130, the second server 140, and the administrator terminal 150 can each send and receive information with other devices through the communication unit 210. For example, the electronic device 110, the user terminal 120 connected to the electronic device 110, the first server 130, the second server 140, and the administrator terminal 150 can each use the communication unit 210 to communicate with each other or with other devices.

[0047] Here, communication, i.e., the transmission and reception of data, can be achieved via wired or wireless means. Therefore, the communication unit 210 may include: a wired communication module that connects to the Internet via a LAN (Local Area Network); a mobile communication module that connects to a mobile communication network via a mobile communication base station to transmit and receive data; a short-range communication module that utilizes communication methods such as Wireless Fidelity (Wi-Fi) or WPAN (Wireless Personal Area Network) such as Bluetooth or Zigbee; a satellite communication module that utilizes GNSS (Global Navigation Satellite System) such as GPS (Global Positioning System); or combinations thereof.

[0048] Memory 220 can store various types of information. The memory can store data temporarily or semi-permanently. For example, the memory 220 of electronic device 110 can store the operating system (OS) used to drive electronic device 110, data used to manage web pages, or data used to generate Braille or application programs (e.g., web applications). Additionally, memory 220 can store modules in the form of computer code as described above.

[0049] Examples of memory 220 include: hard disk drive (HDD), solid state drive (SSD), flash memory, read-only memory (ROM), random access memory (RAM), etc. This type of memory 220 can be provided as either internal or removable.

[0050] The processor 230 controls the overall operation of the electronic device 110, the user terminal 120 connected to the electronic device 110, the first server 130, the second server 140, and the administrator terminal 150. To this end, the processor 230 can perform various information calculations and processing, and control the operation of the components of the electronic device 110. For example, the processor 230 can execute programs or applications to provide page information. The processor 230 can be implemented using a computer or similar device, depending on hardware, software, or a combination thereof. In terms of hardware, the processor 230 can be implemented as an electronic circuit that processes electrical signals and performs control functions; in terms of software, it can be implemented as a program that drives the hardware processor 230. On the other hand, unless otherwise specified in the following description, it can be interpreted that the actions of electronic device 110, user terminal 120 connected to electronic device 110, first server 130, second server 140, and administrator terminal 150 are implemented by the control of processor 230. That is, when the module implemented in the malfunction information provision method of the embodiment of the present invention is executed, the module can be interpreted as the processor 230 controlling electronic device 110, user terminal 120 connected to electronic device 110, first server 130, second server 140, and administrator terminal 150 to perform the steps of the malfunction information provision method.

[0051] In summary, various embodiments can be implemented by various means. For example, various embodiments can be implemented by hardware, firmware, software, or a combination thereof.

[0052] In cases where implementation is achieved through 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.

[0053] When implemented using firmware or software, the methods of various embodiments can be implemented by modules, sequences, or functions that perform the functions or actions described below. For example, software code can be stored in memory and driven by a processor. The memory can be located inside or outside the processor and can exchange data with the processor through various known mechanisms.

[0054] The following describes various embodiments in more detail based on the technical concepts described above. The various embodiments described below can be applied to the content described above. For example, actions, functions, terms, etc., not defined in the various embodiments described below can be implemented and described based on the content described above.

[0055] The following describes various embodiments based on the steps of the method for providing malfunction information by the electronic device 110, i.e., the monitoring server. According to the various embodiments, the electronic device 110 can send and receive information related to the steps of the method for providing malfunction information with any of the user terminal 120, the first server 130, the second server 140 and the administrator terminal 150 connected to the electronic device 110.

[0056] Figure 3 is a flowchart illustrating the method for providing malfunction information according to an embodiment of the present invention.

[0057] Referring to Figure 3, in step S330, the monitoring server 110 can obtain malfunction information of the page provided to the user terminal 120. The malfunction information may include identification information of the page where the malfunction occurred, information of the program associated with the malfunction, and information of the cause of the malfunction.

[0058] According to an embodiment, step S330 can be obtained from at least one of the user terminal 120, the first server 130, and the second server 140.

[0059] Step S330 may include steps S331, S332, or S333. In step S331, the monitoring server 110 may obtain a first malfunction message from the user terminal 120. The first malfunction message may include, for example, page identification information, information associated with at least one UI included in the page, information about the program associated with the malfunction, and information about the cause of the malfunction. In step S332, the monitoring server 110 may obtain a second malfunction message from the first server 130. The second malfunction message may include, for example, information about the program associated with the malfunction and information about the cause of the malfunction. In step S333, the monitoring server 110 may obtain a third malfunction message from the second server 140. The third malfunction message may include, for example, information about user input on the page.

[0060] According to an embodiment, in step S331, when the first erroneous action message is received from the user terminal 120, the first erroneous action message can be obtained from the log transmitter of the user terminal 120. The log transmitter is configured to store and transmit logs associated with the page. The log transmitter of the user terminal 120 can store erroneous action information categorized according to the type of erroneous action. According to an embodiment, the log transmitter of the user terminal 120 can transmit erroneous action information in batches via a message broker. At this time, the message broker can determine the subject of the erroneous action information to be transmitted based on the characteristics of the real-time erroneous action message.

[0061] On the other hand, step S330 may include the following steps: obtaining information associated with at least one UI included in the page; and sensing whether there is a malfunction based on the information associated with at least one UI.

[0062] According to an embodiment, the step of obtaining information associated with at least one UI may include the following steps: obtaining statistical information on a plurality of user inputs to at least one UI obtained in a time series. At this time, the step of sensing whether there is a malfunction may include the following steps: confirming whether there is a malfunction based on whether the statistical information is within a set benchmark range. The set benchmark range may vary depending on the type of malfunction.

[0063] According to another embodiment, the step of obtaining information associated with at least one UI may include the following steps: obtaining a captured image of a page including at least one UI. In this case, the step of sensing whether there is a malfunction may include the following steps: confirming whether there is a malfunction based on a reference image during normal operation and the captured image.

[0064] In step S340, the monitoring server 110 can provide page malfunction information to the administrator terminal 150 based on the malfunction message. According to an embodiment, a plurality of administrator terminals 150 can be provided. Each of the plurality of administrator terminals 150 can correspond to a different type of malfunction. The malfunction message may include domain information corresponding to the administrator terminal 150, thereby automatically transmitting the malfunction message to the corresponding administrator terminal 150.

[0065] On the other hand, in step S310, user terminal 120 may transmit a page request to first server 130, and first server 130 may provide the page to user terminal 120. Monitoring server 110 may sense the malfunction occurring in step S310, thereby obtaining malfunction information. Step S310 may include step S311 or step S315. Steps S311 and S315 will be described in detail with reference to FIG4. The information of the procedure associated with the malfunction included in the malfunction information may include information associated with at least one of steps S311 and S315.

[0066] In step S320, user terminal 120 may transmit user input information of the page to second server 140. The user input information may include, for example, statistical information of multiple user inputs to at least one UI element of the page obtained in a time series. In other words, second server 140 may be a server that processes the statistical information of user input. Second server 140 may transmit the statistical information processed in step S333 to monitoring server 110 in the form of a third malfunction message.

[0067] Figure 4 is a conceptual diagram used to illustrate the procedures associated with malfunctions.

[0068] Referring to Figures 3 and 4, in step S311, the user terminal 120 can prepare the first data for requesting the page. As an example, a malfunction may occur during the preparation of the first data for displaying the "Add to Cart" icon on the page provided to the user terminal 120. Hereinafter, regarding step S310, illustrative examples of possible malfunctions when displaying the "Add to Cart" icon on the page provided to the user terminal 120 will be described, but the present invention is not limited thereto. Information regarding the malfunction occurring in step S311 can be transmitted to the monitoring server 110 in step S331 via the user terminal 120 in the form of a first malfunction message.

[0069] In step S312, user terminal 120 may transmit first data to first server 130. For example, an error in the connection process between user terminal 120 and first server 130 may cause a malfunction in first server 130 where the first data used to display the "Add to Cart" icon cannot be verified. Information about the malfunction occurring in step S312 can be transmitted to monitoring server 110 via user terminal 120 in step S331 in the form of a first malfunction message.

[0070] In step S313, the first server 130 can generate second data associated with the page by processing the first data. For example, a malfunction may occur during the process of the first server 130 processing the first data associated with the "Add to Cart" icon or during the process of the first server 130 generating the second data associated with the "Add to Cart" icon. Specifically, when the product corresponding to the "Add to Cart" icon is in a non-saleable state (i.e., invalid) or out of stock state (i.e., OOS, out of stock), a malfunction may occur during the process of processing the first data or generating the second data. Information about the malfunction occurring in step S313 can be transmitted to the monitoring server 110 in step S332 via the first server 130 in the form of a second malfunction message.

[0071] In step S314, user terminal 120 may receive second data from first server 130. For example, an error in the connection process between user terminal 120 and first server 130 may cause a malfunction in user terminal 120, preventing the display of the "Add to Cart" icon. Specifically, user terminal 120 may identify a malfunction in at least one of the following situations: the HTTP response includes an error code; the second data item includes information indicating it is unsaleable or out of stock; and a problem occurs during deserialization. Information regarding the malfunction occurring in step S314 may be transmitted to monitoring server 110 via user terminal 120 in step S331 in the form of a first malfunction message.

[0072] In step S315, user terminal 120 can process the second data. For example, a malfunction may occur during the processing of the second data used to display the "Add to Cart" icon. Specifically, user terminal 120 may malfunction during the process of displaying the "Add to Cart" icon on the page by rendering the second data. In this case, the first server 130 can determine that all processes have been successful, but the "Add to Cart" icon may not be displayed on the page of user terminal 120. Information about the malfunction occurring in step S315 can be transmitted to monitoring server 110 in step S331 via user terminal 120 in the form of a first malfunction message.

[0073] The malfunctions occurring in steps S312 and S314 may correspond to at least one of the following situations: a network connection failure between user terminal 120 and the first server 130, an HTTP status error, or an internal response body spec error. However, this is merely an example, and the invention is not limited thereto. In this case, user terminal 120 or the first server 130 may, for example, sense whether there is a malfunction through a network interceptor.

[0074] A portion of the malfunctions occurring in steps S311, S313, and S315 may correspond to at least one of the following situations: an error occurring during the preparation or processing of the first data and an error occurring during the generation or processing of the second data. More specifically, the situation where an error occurs related to at least one of the first and second data may be at least one of the following situations: no data (empty), data not provided in a valid form, and a portion of the data is missing. However, this is merely an example, and the present invention is not limited thereto. In the case of no data (empty) and data not provided in a valid form, malfunctions can be sensed by periodically checking the fields associated with the data corresponding to the user terminal 120 or the first server 130 to confirm whether data exists and whether it has a valid form. Furthermore, at least a portion of the various types of malfunctions can also be confirmed by the monitoring server 110 connected to the user terminal 120.

[0075] Another part of the erroneous actions that occur in steps S311, S313, and S315 can be confirmed based on whether statistical information obtained according to the time series of multiple user inputs to at least one UI falls within a set benchmark range. The method of using statistical information to sense whether there is an erroneous action will be described in detail with reference to FIG5.

[0076] Another part of the erroneous actions that occur in steps S311, S313 and S315 can be identified by comparing a captured image of a page including at least one UI with a reference image during normal operation.

[0077] On the other hand, according to the embodiment, at least a portion of the malfunctions that occur in step S311 or step S315 can be manually confirmed by monitoring server 110 or confirmed by using machine learning.

[0078] Figure 5 is a page illustrating the steps of obtaining malfunction information in the malfunction information provision method according to an embodiment of the present invention.

[0079] Referring to Figure 5, a dashboard page 500 is shown, which displays statistical information on multiple user inputs to the page obtained in a time series over a 24-hour period. Dashboard page 500 may include, for example,: a first area 510, which includes statistical information on actions performed on product detail pages; a second area 520, which includes statistical information on actions associated with the shopping cart; and a third area 530, which includes statistical information on actions associated with checkout. Each of the first to third areas 510, 520, and 530 may include a graph and success rate information for each action at a baseline time. The graph represents the number of inputs corresponding to each action from 24 hours ago to the current time. For example, the number of inputs corresponding to each action can be checked in one-minute increments. The success rate information for each action may be, for example, the ratio of the average number of inputs on other dates corresponding to the current time to the number of inputs at the current time.

[0080] For example, area 1 510 may include login success rate information on the product details page, success rate information for inputs corresponding to the "Add to Cart" icon, and success rate information for inputs corresponding to the "Change Options" icon. For example, area 2 520 may include login success rate information and checkout validation success rate information on the shopping cart page. For example, area 3 530 may include direct checkout success rate information and normal checkout success rate information.

[0081] The steps for sensing whether a malfunction has occurred based on information from the page itself or related to at least one UI element included on the page may include the following: confirming whether a malfunction has occurred based on whether the success rate information (i.e., statistical information) of each of the first to third areas 510, 520, and 530 of the dashboard page 500 falls within a set benchmark range. For example, in the case of success rate information for inputs corresponding to the "Add to Cart" icon, the success rate range used as the benchmark for determining whether a malfunction has occurred may be 95% or higher. In this case, if the success rate information for inputs corresponding to the "Add to Cart" icon is less than 95% at a specific time, a malfunction can be sensed. The success rate range used as the benchmark for determining whether a malfunction has occurred may vary depending on the type of icon and the type of action to be confirmed.

[0082] Figures 6 to 9 are conceptual diagrams illustrating the method for providing malfunction information according to embodiments of the present invention.

[0083] Referring to Figures 6 to 9, the monitoring server 110 can provide the administrator terminal 150 with malfunction information associated with the page of the user terminal 120 through various methods.

[0084] Referring to Figure 6, a conceptual diagram of a method for providing malfunction information according to one embodiment of the present invention is shown. The user terminal 120 may include, for example, a malfunction manager and a log sender. The log sender can receive malfunction information from the malfunction manager and transmit it to the monitoring server 110.

[0085] For example, when problems occur during deserialization, when erroneous actions are detected by a network interceptor, or when problems occur in local logic, the erroneous action manager can obtain information on the root cause of the erroneous action corresponding to each situation. Furthermore, for example, when a erroneous action is detected that is associated with the page itself or at least one of its components (i.e., the UI), the erroneous action manager can obtain the status information of the component obtained through component hooks.

[0086] Monitoring server 110 may include, for example, a messaging agent (e.g., KAFKA), a real-time consumer device, an online storage application (e.g., S3), a visualization application (e.g., Grafana), and an AMP (accelerated mobile page). The messaging agent can transmit malfunction information received from the log sender to the real-time consumer device or the online storage application. The real-time consumer device can transmit real-time malfunction information to the AMP via a visualization application. The AMP can transmit malfunction information to the administrator terminal 150 in the form of dashboards, reports, or alerts.

[0087] Referring to FIG7, a conceptual diagram of a method for providing malfunction information according to another embodiment of the present invention is shown. For ease of explanation, descriptions that are substantially the same as those described with reference to FIG6 are omitted, and the differences are described in detail.

[0088] In user terminal 120, malfunction information associated with the page itself can be obtained and transmitted to the log sender via lifecycle callback, and malfunction information associated with at least one component included in the page can be obtained and transmitted to the log sender via component hook. The log sender can then transmit the received malfunction information to monitoring server 110 using the above methods.

[0089] The monitoring server 110 may include, for example, a message broker (e.g., KAFKA), an online storage application (e.g., S3), a distributed data storage application (e.g., Druid), and a visualization application (e.g., Grafana). The message broker may transmit malfunction information received from the log sender to the online storage application or the distributed data storage application. Furthermore, the distributed data storage application may transmit processed malfunction information to the online storage application.

[0090] Referring to FIG8, a conceptual diagram of a method for providing malfunction information according to another embodiment of the present invention is shown. For ease of explanation, descriptions that are substantially the same as those described with reference to FIGS. 6 and 7 are omitted, and the differences are described in detail.

[0091] The user terminal 120 may be provided in multiple forms. The multiple user terminals 120 may utilize any of the applications developed in different ways and versions.

[0092] The monitoring server 110 may include a machine learning model. The machine learning model may utilize, for example, an object sensing algorithm based on YOLO (you only look once) principles. The machine learning model of the monitoring server 110 can sense whether there are erroneous actions on a baseline page based on captured images of the baseline page obtained from multiple user terminals 120. The monitoring server 110 can transmit information about erroneous actions sensed by the machine learning model to the administrator terminal 150.

[0093] Referring to FIG9, a conceptual diagram of a method for providing malfunction information according to another embodiment of the present invention is shown. For ease of explanation, descriptions that are substantially the same as those described with reference to FIGS. 6, 7 and 8 are omitted, and the differences are described in detail.

[0094] In user terminal 120, for example, malfunction information of the gateway page, search results page, product list page, details information page, shopping cart page, and checkout page can be transmitted to the log sender. The types of pages displayed by user terminal 120 are merely examples, and the present invention is not limited thereto.

[0095] The AMP of the monitoring server 110 can also transmit malfunction information to the administrator terminal 150 in the form of dashboards, reports or alarm signals, and can also transmit the malfunction log retrieval results to the online storage program in the form of HTTP response.

[0096] On the other hand, this specification and accompanying drawings disclose preferred embodiments of the invention. Although specific terms are used, they are used in a general sense only to illustrate the technical content of the invention and to aid in understanding the invention, and are not intended to limit the scope of the invention. Those skilled in the art will understand that other variations can be implemented based on the technical concept of the invention, in addition to the embodiments disclosed herein.

[0097] The electronic device or terminal described in the above embodiments may include a processor, memory for storing and executing program data, permanent storage such as a disk drive, a communication port for communicating with a configuration information storage server, and a user interface device such as a touch panel, keys, or buttons. The method implemented by software modules or algorithms, as computer-readable code or program commands executable on the processor, can be stored on a computer-readable recording medium. Here, computer-readable recording media include magnetic storage media (e.g., ROM (read-only memory), RAM (random-access memory), floppy disks, hard disks, etc.) and optical reading media (e.g., CD-ROM, DVD, etc.). The computer-readable recording medium is distributed across a networked computer system, thereby enabling distributed storage and execution of computer-readable code. The medium can be read by a computer, stored in memory, and executed in a processor.

[0098] This embodiment can be represented by functional blocks and various processing steps. These functional blocks can be implemented by varying numbers of hardware and / or software components performing specific functions. For example, the embodiment can employ integrated circuits capable of performing various functions via the control of one or more microprocessors or other control devices, such as memory, processing, logic, lookup tables, etc. The constituent elements can be executed by software programs or software components. Similarly, this embodiment includes various algorithms implemented as combinations of data structures, programs, conventions, or other programs, and therefore can be implemented using programming or scripting languages ​​such as C, C++, Java, assemblers, and Python. Functionally, it can be implemented by algorithms executed in one or more processors. Furthermore, this embodiment can employ prior art for electronic environment setup, signal processing, and / or data processing. Terms such as "mechanism," "element," "means," and "construction" are used broadly and are not limited to mechanical and physical structures. The above terms may be associated with processors and include the meaning of a series of software processes.

[0099] The above embodiment is only an example, and other embodiments can be implemented within the scope of the invention application described below.

[0100] 110: Monitoring server (electronic device) 120: User Terminal 130: Server 1 140: Server 2 150: Operator Terminal (Administrator Terminal) 210: Communications Department 220: Memory 230: Processor 500: Page 510: Area 1 520: Area 2 530: Area 3 S310: Steps S311: Steps S312: Steps S313: Steps S314: Steps S315: Steps S320: Steps S330: Steps S331: Steps S332: Steps S333: Steps S340: Steps

Claims

1. A method for providing malfunction information, performed via an electronic device, comprising the following steps: obtaining malfunction information of a page provided to a user terminal; and providing malfunction information of the page to an administrator terminal based on the malfunction information; wherein the malfunction information includes identification information of the page, and wherein obtaining the malfunction information comprises the following steps: obtaining image information of the page including at least one user interface (UI); and sensing whether there is a malfunction based on a reference image of the page during normal operation and the image information.

2. The method for providing malfunction information as described in claim 1, wherein the malfunction information is obtained from at least one of the user terminal, a first server that provides the page to the user terminal, and a second server that processes user input information for the page.

3. The method for providing erroneous information as described in claim 2, wherein when the erroneous information is obtained from the aforementioned user terminal, the step of obtaining the erroneous information includes the following steps: obtaining the erroneous information from the log transmitter of the aforementioned user terminal, wherein the log transmitter is configured to store and transmit logs associated with the aforementioned page.

4. The method for providing malfunction information as described in claim 1, wherein the malfunction information further includes information about a procedure associated with the malfunction, and the information about the procedure associated with the malfunction includes information associated with at least one of the following steps: a first step in which the user terminal prepares first data for requesting the page; a second step in which the user terminal transmits the first data to a first server providing the page to the user terminal; a third step in which the first server processes the first data to generate second data associated with the page; a fourth step in which the user terminal receives the second data from the first server; and a fifth step in which the user terminal processes the second data.

5. The method for providing malfunction information as requested in Item 1, wherein the step of sensing whether there is a malfunction based on the above-mentioned baseline image and the above-mentioned image information when the above-mentioned page is in normal operation includes the following steps: sensing whether there is a malfunction by using a machine learning model based on the above-mentioned image information.

6. The method for providing malfunction information as requested in item 1, wherein the step of obtaining the aforementioned malfunction information includes the following steps: obtaining statistical information of a plurality of inputs from a plurality of users to at least one user interface (UI); and sensing whether there is a malfunction based on whether the aforementioned statistical information is within a reference range.

7. The method for providing malfunction information as requested in item 6, wherein the above-mentioned benchmark range varies depending on the type of malfunction.

8. The method for providing malfunction information as described in Request 6 further includes the step of displaying the aforementioned statistical information on a dashboard.

9. The method for providing malfunction information as requested in item 1, wherein the malfunction information further includes domain information corresponding to the aforementioned administrator terminal.

10. A non-transitory computer-readable recording medium recording a program for performing the method as described in claim 1 on a computer.

11. An electronic device that provides malfunction information, comprising: Memory, which stores at least one command; The processor, based on at least one of the above commands,: obtains malfunction information of a page provided to a user terminal; and provides malfunction information of the page to a management terminal based on the malfunction information, wherein the malfunction information includes identification information of the page, and wherein the malfunction information is obtained by obtaining image information of the page including at least one user interface (UI), and sensing whether there is a malfunction based on a reference image of the page during normal operation and the image information.

Images