WO2024096170A1 - Procédé de fourniture d'informations de dysfonctionnement et dispositif électronique associé - Google Patents

Procédé de fourniture d'informations de dysfonctionnement et dispositif électronique associé Download PDF

Info

Publication number
WO2024096170A1
WO2024096170A1 PCT/KR2022/017418 KR2022017418W WO2024096170A1 WO 2024096170 A1 WO2024096170 A1 WO 2024096170A1 KR 2022017418 W KR2022017418 W KR 2022017418W WO 2024096170 A1 WO2024096170 A1 WO 2024096170A1
Authority
WO
WIPO (PCT)
Prior art keywords
malfunction
information
page
user terminal
message
Prior art date
Application number
PCT/KR2022/017418
Other languages
English (en)
Korean (ko)
Inventor
쟝카이
Original Assignee
쿠팡 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 쿠팡 주식회사 filed Critical 쿠팡 주식회사
Publication of WO2024096170A1 publication Critical patent/WO2024096170A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/32—Monitoring with visual or acoustical indication of the functioning of the machine
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/32—Monitoring with visual or acoustical indication of the functioning of the machine
    • G06F11/321—Display for diagnostics, e.g. diagnostic result display, self-test user interface
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/32—Monitoring with visual or acoustical indication of the functioning of the machine
    • G06F11/324—Display of status information
    • G06F11/327—Alarm or error message display
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3409—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3452—Performance evaluation by statistical analysis
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06N—COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
    • G06N20/00—Machine learning
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06V—IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
    • G06V10/00—Arrangements for image or video recognition or understanding
    • G06V10/70—Arrangements for image or video recognition or understanding using pattern recognition or machine learning
    • G06V10/74—Image or video pattern matching; Proximity measures in feature spaces
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06V—IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
    • G06V10/00—Arrangements for image or video recognition or understanding
    • G06V10/70—Arrangements for image or video recognition or understanding using pattern recognition or machine learning
    • G06V10/74—Image or video pattern matching; Proximity measures in feature spaces
    • G06V10/761—Proximity, similarity or dissimilarity measures

Definitions

  • the present disclosure relates to a method for providing malfunction information that monitors malfunctions that occur in pages provided on a user terminal and provides malfunction information to an administrator terminal, and an electronic device therefor.
  • the purpose of the present disclosure is to provide a malfunction information providing method and an electronic device for the same, which monitor malfunctions that occur in pages provided on a user terminal and provide malfunction information to an administrator terminal.
  • a method of providing malfunction information includes obtaining a malfunction message for a page provided to a user terminal and providing malfunction information for the page to an administrator terminal based on the malfunction message,
  • the malfunction message may include identification information about the page, information about the process involved in the malfunction, and information about the reason for the malfunction.
  • the malfunction message may be 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 information about the user's input to the page.
  • obtaining the malfunction message may include obtaining the malfunction message from a log sender of the user terminal configured to store and transmit logs related to the page. there is.
  • Information about the process related to the malfunction includes: a first step in which the user terminal prepares first data for a request of the page; the user terminal sends the first step to a first server that provides the page to the user terminal A second step of transmitting data, a third step of the first server processing the first data to generate second data related to the page, and the user terminal receiving the second data from the first server. It may include information related to at least one of the fourth step and the fifth step in which the user terminal processes the second data.
  • Obtaining the malfunction message may include obtaining information related to at least one UI included in the page and detecting whether there is a malfunction based on the information related to the at least one UI.
  • Obtaining information related to the at least one UI may include obtaining statistical information about a plurality of inputs of a plurality of users for the at least one UI obtained in a time-serial manner.
  • the step of detecting whether there is a malfunction may include checking whether there is a malfunction based on whether the statistical information is within a set reference range.
  • the set reference range may vary depending on the type of malfunction.
  • Obtaining information related to the at least one UI may include obtaining a captured image for the page including the at least one UI.
  • the step of detecting whether there is a malfunction may include checking whether there is a malfunction based on a reference image during normal operation and the captured image.
  • the malfunction message may further include domain information corresponding to the manager terminal.
  • An electronic device that provides malfunction information includes a memory storing at least one command, and based on the at least one command, obtains a malfunction message for a page provided to a user terminal, and sends the malfunction message. and a processor that provides malfunction information about the page to an administrator terminal based on the malfunction message.
  • the malfunction message may include identification information about the page, information about a process related to the malfunction, and information about the reason for the malfunction.
  • a malfunction can be detected in a method optimized for the cause of the malfunction and information about the malfunction can be efficiently transmitted to the administrator terminal.
  • FIG. 1 is a conceptual diagram illustrating an electronic device in which a method for providing malfunction information according to embodiments of the present disclosure is implemented.
  • Figure 2 is a schematic block diagram for explaining servers and terminals according to embodiments of the present disclosure.
  • FIG. 3 is a flowchart illustrating a method of providing malfunction information according to embodiments of the present disclosure.
  • Figure 4 is a conceptual diagram for explaining processes related to malfunction.
  • Figure 5 is a page for explaining the step of obtaining a malfunction message in the method for providing malfunction information according to embodiments of the present disclosure.
  • 6 to 9 are conceptual diagrams for explaining a method of providing malfunction information according to embodiments of the present disclosure.
  • the “terminal” mentioned below may be implemented as a computer or portable terminal that can connect to a server or other terminal through a network.
  • the computer includes, for example, a laptop, desktop, laptop, etc. equipped with a web browser
  • the portable terminal is, for example, a wireless communication device that guarantees portability and mobility.
  • all types of communication-based terminals such as IMT (International Mobile Telecommunication), CDMA (Code Division Multiple Access), W-CDMA (W-Code Division Multiple Access), and LTE (Long Term Evolution), smartphones, tablet PCs, etc. It may include a handheld-based wireless communication device.
  • each block of the processing flow diagrams and combinations of the flow diagram diagrams can be performed by computer program instructions.
  • These computer program instructions can be mounted on a processor of a general-purpose computer, special-purpose computer, or other programmable data processing equipment, so that the instructions performed through the processor of the computer or other programmable data processing equipment are described in the flowchart block(s). It creates the means to perform functions.
  • These computer program instructions may also be stored in computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement a function in a particular manner, so that the computer-usable or computer-readable memory It is also possible to produce manufactured items containing instruction means to perform the functions described in the flowchart block(s).
  • Computer program instructions can also be mounted on a computer or other programmable data processing equipment, so that a series of operational steps are performed on the computer or other programmable data processing equipment to create a process that is executed by the computer and generates a computer or other programmable data processing equipment. Instructions for performing processing equipment may also provide steps for executing the functions described in the flowchart block(s).
  • each block may represent a module, segment, or portion of code containing one or more executable instructions for executing specified logical function(s).
  • each block may represent a module, segment, or portion of code containing one or more executable instructions for executing specified logical function(s).
  • FIG. 1 is a conceptual diagram illustrating an electronic device in which a method for providing malfunction information according to embodiments of the present disclosure is implemented.
  • the method for providing malfunction information according to embodiments of the present disclosure may be implemented in various types of devices.
  • the method for providing malfunction information according to embodiments of the present disclosure may be implemented in the electronic device 110.
  • the electronic device 110 may perform operations according to embodiments of the present disclosure based on the implemented method for providing malfunction information.
  • the method for providing malfunction information according to embodiments of the present disclosure is not limited to that shown in FIG. 1 and may be implemented in various electronic devices, terminals, and servers.
  • the electronic device 110 may be a monitoring server.
  • the electronic device 110 may be a device that performs wired or wireless communication with at least one device that interacts with the electronic device 110 and includes a memory with a large storage capacity.
  • the electronic device 110 may be a cloud device connected to at least one device.
  • the electronic device 110 is linked with each of the user terminal 120, the first server 130, the second server 140, and the administrator terminal 150 and may perform wired or wireless communication.
  • Each of the user terminal 120 and the administrator terminal 150 that interact with the electronic device 110 may be at least one of a desktop PC, a tablet PC, and a mobile terminal.
  • other electronic devices that perform similar functions may be used as the user terminal 120 and the administrator terminal 150 that are linked to the electronic device 110.
  • Each of the first server 130 and the second server 140 linked with the electronic device 110 and the user terminal 120 may be at least one of a desktop PC, a tablet PC, and a mobile terminal. there is.
  • other electronic devices that perform similar functions may be used as the first server 130 and the second server 140 that are linked with the electronic device 110 and the user terminal 120.
  • the user terminal 120, the first server 130, and the second server 140 are not shown to be linked to the manager terminal 150, but are shown to be linked to the electronic device 110, that is, the monitoring server.
  • This disclosure is only illustrative and is not limited thereto.
  • at least one of the user terminal 120, the first server 130, and the second server 140 is directly linked to the administrator terminal 150 and may perform wired or wireless communication.
  • the first server 130 and the second server 140 are not directly linked to each other, but are shown to be linked to the electronic device 110 and the user terminal 120, but this is only an example and does not apply to the present disclosure. is not limited to this.
  • the first server 130 and the second server 140 are directly linked to each other and may perform wired or wireless communication.
  • the modules may be computer code or one or more instructions implemented to enable a physical device (e.g., electronic device 110) on which a method for providing malfunction information is implemented (or included in the physical device) to perform a specified operation.
  • the physical device in which the method for providing malfunction information is implemented stores a plurality of modules in the memory in the form of computer code, and when the plurality of modules stored in the memory are executed, the plurality of modules are generated by the physical device corresponding to the plurality of modules. You can have it perform specified actions.
  • Figure 2 is a schematic block diagram for explaining an electronic device and an operator terminal according to embodiments of the present disclosure.
  • the electronic device 110 and the user terminal 120, first server 130, second server 140, and administrator terminal 150 linked to the electronic device 110 each have a communication unit 210. ), memory 220, and processor 230.
  • the electronic device 110 and the user terminal 120, the first server 130, the second server 140, and the administrator terminal 150 linked to the electronic device 110 each have an input unit and an output unit. It may include more. Each of the input unit and output unit may be various interfaces or connection ports that receive user input or output information to the user.
  • the input unit may include an input module, and the input module receives a user input from a user.
  • User input can take various forms, including key input, touch input, and voice input.
  • Examples of input modules that can receive such user input include traditional keypads, keyboards, and mice, as well as touch sensors that detect the user's touch, microphones that receive voice signals, cameras that recognize gestures through image recognition, etc.
  • a proximity sensor including at least one of an illumination sensor or an infrared sensor that detects user approach, a motion sensor that recognizes user movement through an acceleration sensor or gyro sensor, and various other types of sensors that detect or receive user input.
  • the input module may include at least one of the devices listed above.
  • the touch sensor may be implemented as a piezoelectric or capacitive touch sensor that detects touch through a touch panel or touch film attached to the display panel, or an optical touch sensor that detects touch by an optical method.
  • the input module may be implemented in the form of an input interface (USB port, PS/2 port, etc.) that connects an external input device that receives user input instead of a device that detects user input itself.
  • the output unit may include an output module, and the output module may output various types of information.
  • the output module may include at least one of a display that outputs an image, a speaker that outputs sound, a haptic device that generates vibration, and other various types of output means.
  • the output module may be implemented in the form of a port-type output interface that connects the individual output means described above.
  • a display-type output module can display text, still images, and moving images. Displays include liquid crystal display (LCD), light emitting diode (LED) display, organic light emitting diode (OLED) display, flat panel display (FPD), and transparent display.
  • This display may be in the form of a touch display integrated with the touch sensor of the input module.
  • the communication unit 210 can communicate with other devices. Accordingly, the electronic device 110 and the user terminal 120, first server 130, second server 140, and administrator terminal 150 linked to the electronic device 110 each communicate with the other device through the communication unit 210. You can send and receive information to and from devices. For example, the electronic device 110 and the user terminal 120, first server 130, second server 140, and administrator terminal 150 linked to the electronic device 110 each have a communication unit 210. You can use it to communicate with each other or with other devices.
  • the communication unit 210 includes a wired communication module that connects to the Internet, etc. through a LAN (Local Area Network), a mobile communication module that connects to a mobile communication network through a mobile communication base station and transmits and receives data, and a WLAN such as Wi-Fi.
  • a short-range communication module that uses a Wireless Local Area Network (Wireless Local Area Network) series communication method or a WPAN (Wireless Personal Area Network) series communication method such as Bluetooth or Zigbee, and a GNSS (Global Positioning System) such as GPS (Global Positioning System). It may be composed of a satellite communication module using a Navigation Satellite System or a combination thereof.
  • the memory 220 can store various types of information.
  • the memory 220 can store data temporarily or semi-permanently.
  • the memory 220 of the electronic device 110 contains an operating program (OS; Operating System) for driving the electronic device 110, a program for generating data or Braille for hosting a website, or an application (e.g. For example, data related to a web application, etc. may be stored.
  • OS Operating Program
  • an application e.g. For example, data related to a web application, etc. may be stored.
  • the memory 220 may store modules in the form of computer code as described above.
  • Examples of the memory 220 include hard disk drive (HDD), solid state drive (SSD), flash memory, read-only memory (ROM), random access memory (RAM), etc. This can be.
  • This memory 220 may be provided as a built-in type or a detachable type.
  • the processor 230 controls the overall operation of the electronic device 110 and the user terminal 120, first server 130, second server 140, and administrator terminal 150 that are linked to the electronic device 110. do. To this end, the processor 230 can perform computation and processing of various information and control the operation of components of the electronic device 110. For example, the processor 230 may execute a program or application to provide page information.
  • the processor 230 may be implemented as a computer or similar device using hardware, software, or a combination thereof. In hardware, the processor 230 may be implemented in the form of an electronic circuit that processes electrical signals to perform a control function, and in software, it may be implemented in the form of a program that drives the hardware processor 230.
  • the electronic device 110 and the user terminal 120, first server 130, second server 140, and administrator terminal 150 linked to the electronic device 110 Each operation can be interpreted as being performed under the control of the processor 230. That is, when modules implemented in the method for providing malfunction information according to embodiments of the present disclosure are executed, the modules are configured such that the processor 230 is connected to the electronic device 110 and the user terminal 120 that works with the electronic device 110. This may be interpreted as controlling each of the first server 130, the second server 140, and the manager terminal 150 to perform the steps of the method for providing malfunction information.
  • various embodiments may be implemented through various means.
  • various embodiments may be implemented by hardware, firmware, software, or a combination thereof.
  • methods include one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), and FPGAs ( It can be implemented by field programmable gate arrays, processors, controllers, microcontrollers, microprocessors, etc.
  • 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.
  • firmware or software methods according to various embodiments may be implemented in the form of modules, procedures, or functions that perform the functions or operations described below.
  • software code can be stored in memory and run by a processor.
  • the memory may be located inside or outside the processor, and may exchange data with the processor through various known means.
  • the electronic device 110 that is, the monitoring server, performs the steps of the method for providing malfunction information.
  • the electronic device 110 performs the steps of the method for providing malfunction information.
  • Information related to the steps may be transmitted and received to any one of the user terminal 120, the first server 130, the second server 140, and the administrator terminal 150 that are linked to the electronic device 110.
  • FIG. 3 is a flowchart illustrating a method of providing malfunction information according to embodiments of the present disclosure.
  • the monitoring server 110 may obtain a malfunction message for a page provided to the user terminal 120.
  • the malfunction message may include identification information about the page where the malfunction occurred, information about the process related to the malfunction, and information about the reason for the malfunction.
  • step S330 may be obtained from at least one of the user terminal 120, the first server 130, and the second server 140.
  • Step S330 may include steps S331, S332 to S333.
  • the monitoring server 110 may obtain the first malfunction message from the user terminal 120.
  • the first malfunction message may include, for example, identification information about the page, information about at least one UI included in the page, information about a process related to the malfunction, and information about the reason for the malfunction.
  • 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 process involved in the malfunction and information about the reason for the malfunction.
  • the monitoring server 110 may obtain a third malfunction message from the second server 140.
  • the third malfunction message may include, for example, information regarding the user's input to the page.
  • the first malfunction message when the first malfunction message is obtained from the user terminal 120, the first malfunction message may be obtained from a log sender of the user terminal 120 configured to store and transmit logs related to the page. You can.
  • the log sender of the user terminal 120 can store malfunction information by dividing it according to the type of malfunction.
  • the log sender of the user terminal 120 may transmit malfunction information in batches to the message broker program.
  • the message broker program can determine the subject to transmit the malfunction information in real time according to the characteristics of the malfunction message.
  • step S330 may include obtaining information related to at least one UI included in the page and detecting a malfunction based on the information related to at least one UI.
  • obtaining information related to at least one UI may include obtaining statistical information about a plurality of inputs from a plurality of users for the at least one UI obtained in a time series manner.
  • the step of detecting whether there is a malfunction may include checking whether there is a malfunction based on whether statistical information is within a set standard range.
  • the established reference range may vary depending on the type of malfunction.
  • acquiring information related to at least one UI may include obtaining a captured image for a page including at least one UI.
  • the step of detecting whether there is a malfunction may include checking whether there is a malfunction based on a reference image and a captured image during normal operation.
  • the monitoring server 110 may provide malfunction information about the page to the administrator terminal 150 based on the malfunction message.
  • a plurality of manager terminals 150 may be provided. Each of the plurality of manager terminals 150 may respond to different types of malfunctions.
  • the malfunction message may include domain information corresponding to the administrator terminal 150, and accordingly, the malfunction message may be automatically transmitted to the corresponding administrator terminal 150.
  • step S310 the user terminal 120 transmits a page provision request to the first server 130, and the first server 130 may provide the page to the user terminal 120.
  • the monitoring server 110 may detect a malfunction that occurs in step S310 and obtain a malfunction message accordingly.
  • Step S310 may include steps S311 to S315. Steps S311 and S315 will be described in detail with reference to FIG. 4.
  • Information about the process related to the malfunction included in the malfunction message may include information related to at least one of steps S311 and S315.
  • the user terminal 120 may transmit information about the user input to the page to the second server 140.
  • Information about user input may include, for example, statistical information about a plurality of inputs from a plurality of users on at least one UI of a page, which is acquired in time series.
  • the second server 140 may be a server that processes statistical information regarding user input.
  • the second server 140 may transmit the statistical information processed in step S333 to the monitoring server 110 in the form of a third malfunction message.
  • Figure 4 is a conceptual diagram for explaining processes related to malfunction.
  • step S311 the user terminal 120 may prepare first data for requesting a page.
  • a malfunction may occur in the process of preparing first data for displaying the 'Add to Cart' icon on the page provided to the user terminal 120.
  • a malfunction that may occur when the 'Add to Cart' icon is displayed on the page provided to the user terminal 120 in relation to step S310 will be described as an example, but the present disclosure is not limited thereto.
  • Information about the malfunction that occurs in step S311 may be transmitted by the user terminal 120 to the monitoring server 110 in the form of a first malfunction message in step S331.
  • the user terminal 120 may transmit first data to the first server 130. For example, due to an error in the connection process between the user terminal 120 and the first server 130 for transmitting the first data, the first data for displaying the 'Add to Cart' icon is checked on the first server 130. A malfunction may occur. Information about the malfunction that occurs in step S312 may be transmitted by the user terminal 120 to the monitoring server 110 in the form of a first malfunction message in step S331.
  • the first server 130 may process the first data to generate second data related to the page.
  • a malfunction may occur while the first server 130 processes first data related to the 'Add to Cart' icon or while the first server 130 generates second data related to the 'Add to Cart' icon.
  • Information about the malfunction that occurs in step S313 may be transmitted by the first server 130 to the monitoring server 110 in the form of a second malfunction message in step S332.
  • the user terminal 120 may receive second data from the first server 130. For example, due to an error in the connection process between the user terminal 120 and the first server 130 for receiving the second data, the user terminal 120 does not check the second data to display the 'Add to Cart' icon. Malfunctions may occur. Specifically, in at least one of the following cases: when the http response includes an error code, when the second data includes information that the product is unsaleable or out of stock, and when a problem occurs during the deserialization process. , the user terminal 120 may recognize that a malfunction has occurred. Information about the malfunction that occurs in step S314 may be transmitted by the user terminal 120 to the monitoring server 110 in the form of a first malfunction message in step S331.
  • step S315 the user terminal 120 may process the second data. For example, a malfunction may occur in the process of processing second data to display the 'Add to Cart' icon. Specifically, a malfunction may occur while the user terminal 120 renders the second data and displays the 'Add to Cart' icon on the page. At this time, the first server 130 may determine that all processes have been successful, but the 'Add to Cart' icon may not be displayed on the page of the user terminal 120. Information about the malfunction that occurs in step S315 may be transmitted by the user terminal 120 to the monitoring server 110 in the form of a first malfunction message in step S331.
  • Malfunctions that occur in steps S312 and S314 include when the network connection between the user terminal 120 and the first server 130 fails (connection failure), when an http status error occurs (http status failure), and when the specification of the internal response This may correspond to at least one of the cases where an error occurs (internal response body spec failure). However, this is only an example and the present disclosure is not limited thereto.
  • the user terminal 120 or the first server 130 may detect a malfunction by, for example, a network interceptor.
  • Some of the malfunctions that occur in steps S311, S313, and S315 are at least one of the following: an error occurs in the process of preparing or processing the first data and an error occurs in the process of generating or processing the second data. It may apply. More specifically, when an error occurs related to at least one of the first data and the second data, it is at least one of the following: data is empty, data is not provided in a valid format, and part of the data is lost. You can. However, this is only an example and the present disclosure is not limited thereto. In the case where there is no data or when the data is not provided in a valid format, the user terminal 120 or the first server 130 checks the fields related to the corresponding data to see if the data exists and is in a valid format. Malfunctions can be detected by regularly checking the etc. Additionally, at least some of various types of malfunctions may be confirmed by the monitoring server 110 linked to the user terminal 120.
  • steps S311, S313, and S315 may be confirmed based on whether statistical information regarding a plurality of inputs from a plurality of users for at least one UI obtained in time series is within a set reference range. You can. A method for detecting malfunction using statistical information will be described in detail with reference to FIG. 5.
  • steps S311, S313, and S315 Another part of the malfunctions that occur in steps S311, S313, and S315 can be confirmed by comparing the captured image for the page including at least one UI with a reference image during normal operation.
  • At least some of the malfunctions that occur in steps S311 to S315 may be confirmed manually or using machine learning by the monitoring server 110.
  • Figure 5 is a page for explaining the step of obtaining a malfunction message in the method for providing malfunction information according to embodiments of the present disclosure.
  • a dashboard page 500 is shown showing statistical information about a plurality of inputs from a plurality of users on a page obtained in time series over 24 hours.
  • the dashboard page 500 includes, for example, a first area 510 containing statistical information about operations performed on a product detailed information page, and a second area 510 containing statistical information about operations related to a shopping cart. It may include an area 520 and a third area 530 containing statistical information on operations related to payment.
  • Each of the first to third areas 510, 520, and 530 may include a graph showing the number of inputs corresponding to each operation from 24 hours ago to the current time and success rate information for each operation at the reference time. there is.
  • the number of inputs corresponding to each of the operations can be confirmed, for example, in units of 1 minute.
  • the success rate information for each operation may be, for example, a ratio of the number of inputs at the current time to the average number of inputs on other dates corresponding to the current time.
  • the first area 510 may include landing success rate information of the product detailed information page, success rate information of input corresponding to the 'Add to Cart' icon, and success rate information of input corresponding to the 'Change Option' icon.
  • the second area 520 may include landing success rate information of the shopping cart page, checkout validation success rate information, etc.
  • the third area 530 may include direct checkout success rate information, normal checkout success rate information, etc.
  • the step of detecting a malfunction based on information related to the page itself or at least one UI included in the page includes success rate information for each of the first to third areas 510, 520, and 530 of the dashboard page 500. It may include a step of checking whether there is a malfunction based on whether (i.e., statistical information) is within a set standard range. For example, in the case of input success rate information corresponding to the 'Add to Cart' icon, the range of success rate that serves as a standard for determining malfunction may be 95% or more. At this time, a malfunction may be detected if the success rate information of the input corresponding to the 'Add to Cart' icon is less than 95% at a specific time. The range of success rate, which is the standard for determining malfunction, may vary depending on the type of icon and the type of operation to be checked.
  • 6 to 9 are conceptual diagrams for explaining a method of providing malfunction information according to embodiments of the present disclosure.
  • the monitoring server 110 may provide malfunction information related to the page of the user terminal 120 to the administrator terminal 150 in various ways.
  • the user terminal 120 may include, for example, a malfunction manager and a log sender.
  • the log sender may receive malfunction information from the malfunction manager and transmit it to the monitoring server 110.
  • a problem occurs during deserialization, if a malfunction is detected by a network interceptor, or if a problem occurs in local logic, information about each case and the corresponding reason for the malfunction (root cause) can be obtained by the malfunction manager. Additionally, for example, if a malfunction related to the page itself or at least one component (i.e., UI) included in the page is detected, the state information of the component obtained through a component hook is sent to the malfunction manager. can be obtained.
  • Monitoring server 110 may include, for example, a message broker program (e.g., KAFKA), a real time consumer, an online storage program (e.g., S3), a visualization program (e.g., Grafana) and AMP (accelerated mobile page).
  • the message broker program can transmit malfunction information received from the log sender to a real-time consumer or online storage program.
  • the real-time consumer can transmit malfunction information in real time to the AMP through a visualization program.
  • AMP can transmit malfunction information to the administrator terminal 150 in the form of a dashboard, report, or alert.
  • FIG. 7 a conceptual diagram of a method for providing malfunction information according to another embodiment of the present disclosure is shown.
  • description of matters that are substantially the same as those described with reference to FIG. 6 will be omitted and differences will be explained.
  • malfunction information related to the page itself may be obtained through a life cycle callback method and transmitted to the log sender, and malfunction information related to at least one component included in the page may be obtained through a component hook. It can be acquired using a (component hook) method and transmitted to the log sender.
  • the log sender may transmit malfunction information received in the above-described manner to the monitoring server 110.
  • Monitoring server 110 may include, for example, a message broker program (e.g., KAFKA), an online storage program (e.g., S3), a distributed data store program (e.g., druid), and a visualization program (e.g., For example, Grafana).
  • the message broker program can transmit malfunction information received from the log sender to an online storage program or distributed data store program. Additionally, the distributed data store program may transmit processed malfunction information to an online storage program.
  • FIG. 8 a conceptual diagram of a method for providing malfunction information according to another embodiment of the present disclosure is shown.
  • descriptions of matters that are substantially the same as those described with reference to FIGS. 6 and 7 will be omitted and differences will be explained.
  • a plurality of user terminals 120 may be provided.
  • a plurality of user terminals 120 may use any one of applications developed in different methods and versions.
  • Monitoring server 110 may include a machine learning model.
  • the machine learning model may use, for example, a YOLO (you only look once) type object detection algorithm.
  • the machine learning model of the monitoring server 110 may detect whether the reference page is malfunctioning based on captured images of the reference page obtained from the plurality of user terminals 120.
  • the monitoring server 110 may transmit information about malfunctions detected by the machine learning model to the manager terminal 150.
  • FIG. 9 a conceptual diagram of a method for providing malfunction information according to another embodiment of the present disclosure is shown.
  • descriptions of items that are substantially the same as those described with reference to FIGS. 6, 7, and 8 will be omitted and differences will be explained.
  • malfunction information for each of the gateway page, search result page, product list page, detailed information page, shopping cart page, and payment page may be transmitted to the log sender.
  • the types of pages displayed on the user terminal 120 are merely examples and the present disclosure is not limited thereto.
  • the AMP of the monitoring server 110 may transmit malfunction information to the administrator terminal 150 in the form of a dashboard, report, or alert, and may transmit malfunction log search results to an online storage program in the form of an http response.
  • the electronic device or terminal includes a processor, memory for storing and executing program data, permanent storage such as a disk drive, a communication port for communicating with a setting information storage server, a touch panel, and a key ( It may include user interface devices such as keys, buttons, etc.
  • Methods implemented as software modules or algorithms may be stored on a computer-readable recording medium as computer-readable codes or program instructions executable on a processor.
  • computer-readable recording media include magnetic storage media (e.g., ROM (read-only memory), RAM (random-access memory), floppy disk, hard disk, etc.) and optical read media (e.g., CD-ROM). ), DVD (Digital Versatile Disc), etc.
  • the computer-readable recording medium is distributed among computer systems connected to a network, so that computer-readable code can be stored and executed in a distributed manner.
  • the media may be readable by a computer, stored in memory, and executed by a processor.
  • This embodiment can be represented by functional block configurations and various processing steps. These functional blocks may be implemented in various numbers of hardware or/and software configurations that execute specific functions. For example, embodiments include integrated circuit configurations such as memory, processing, logic, look-up tables, etc. that can execute various functions under the control of one or more microprocessors or other control devices. can be hired. Similar to how the components can be implemented as software programming or software elements, the present embodiments include various algorithms implemented as combinations of data structures, processes, routines or other programming constructs, such as C, C++, Java ( It can be implemented in a programming or scripting language such as Java, assembler, Python, etc. Functional aspects may be implemented as algorithms running on one or more processors.
  • this embodiment may employ conventional technologies for electronic environment settings, signal processing, and/or data processing.
  • Terms such as “mechanism,” “element,” “means,” and “composition” can be used broadly and are not limited to mechanical and physical components. The above-mentioned term may include the meaning of a series of software routines in connection with a processor, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Computing Systems (AREA)
  • Software Systems (AREA)
  • Computer Vision & Pattern Recognition (AREA)
  • Evolutionary Computation (AREA)
  • Artificial Intelligence (AREA)
  • Medical Informatics (AREA)
  • Computer Hardware Design (AREA)
  • Mathematical Physics (AREA)
  • General Health & Medical Sciences (AREA)
  • Databases & Information Systems (AREA)
  • Multimedia (AREA)
  • Data Mining & Analysis (AREA)
  • Health & Medical Sciences (AREA)
  • Human Computer Interaction (AREA)
  • Bioinformatics & Cheminformatics (AREA)
  • Bioinformatics & Computational Biology (AREA)
  • Evolutionary Biology (AREA)
  • Probability & Statistics with Applications (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

La présente divulgation divulgue un procédé de fourniture d'informations de dysfonctionnement et un dispositif électronique associé, le procédé de fourniture d'informations de dysfonctionnement comprenant les étapes consistant à : acquérir un message de dysfonctionnement pour une page fournie à un terminal utilisateur ; et fournir des informations de dysfonctionnement de la page à un terminal gestionnaire sur la base du message de dysfonctionnement, le message de dysfonctionnement comprenant des informations d'identification de la page, des informations sur un processus associé à un dysfonctionnement, et des informations sur la cause du dysfonctionnement.
PCT/KR2022/017418 2022-10-31 2022-11-08 Procédé de fourniture d'informations de dysfonctionnement et dispositif électronique associé WO2024096170A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR1020220142839A KR102650041B1 (ko) 2022-10-31 2022-10-31 오작동 정보 제공 방법 및 이를 위한 전자 장치
KR10-2022-0142839 2022-10-31

Publications (1)

Publication Number Publication Date
WO2024096170A1 true WO2024096170A1 (fr) 2024-05-10

Family

ID=90480941

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2022/017418 WO2024096170A1 (fr) 2022-10-31 2022-11-08 Procédé de fourniture d'informations de dysfonctionnement et dispositif électronique associé

Country Status (2)

Country Link
KR (2) KR102650041B1 (fr)
WO (1) WO2024096170A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20000054324A (ko) * 2000-02-24 2000-09-05 이장혁 네트워크 사이트 감시 방법 및 장치
JP2002236626A (ja) * 2000-12-06 2002-08-23 Site Rock Corp サイト監視方法、および、サイト監視システム
KR20030084091A (ko) * 2002-04-24 2003-11-01 정보통신연구진흥원 웹사이트 에러처리시스템 및 그 처리방법
JP2004157906A (ja) * 2002-11-08 2004-06-03 Fujitsu Ltd 不具合情報管理サーバ、端末装置、不具合通報方法、およびコンピュータプログラム
KR101443071B1 (ko) * 2013-12-10 2014-09-22 주식회사 브이시스템즈 웹페이지의 에러 체크 시스템

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20000054324A (ko) * 2000-02-24 2000-09-05 이장혁 네트워크 사이트 감시 방법 및 장치
JP2002236626A (ja) * 2000-12-06 2002-08-23 Site Rock Corp サイト監視方法、および、サイト監視システム
KR20030084091A (ko) * 2002-04-24 2003-11-01 정보통신연구진흥원 웹사이트 에러처리시스템 및 그 처리방법
JP2004157906A (ja) * 2002-11-08 2004-06-03 Fujitsu Ltd 不具合情報管理サーバ、端末装置、不具合通報方法、およびコンピュータプログラム
KR101443071B1 (ko) * 2013-12-10 2014-09-22 주식회사 브이시스템즈 웹페이지의 에러 체크 시스템

Also Published As

Publication number Publication date
KR102650041B1 (ko) 2024-03-22
KR20240063058A (ko) 2024-05-09

Similar Documents

Publication Publication Date Title
WO2018143694A1 (fr) Dispositif électronique et procédé de vérification de l'intégrité de données sur la base d'une chaîne de blocs
WO2014157806A1 (fr) Dispositif d'affichage et son procédé de commande
WO2016017855A1 (fr) Dispositif à porter sur soi, et procédé de commande de ce dispositif
WO2018044077A1 (fr) Dispositif électronique et procédé de service de notification de rappel automatique
WO2018155854A1 (fr) Module pogo et dispositif électronique le comprenant
WO2019050072A1 (fr) Système et procédé de demande de service utilisant un bouton virtuel basé sur une application
WO2018124775A1 (fr) Procédé de permettant de relier un dispositif externe et dispositif électronique le prenant en charge
US11457108B2 (en) Cloud integration to desktop-based emergency service applications
WO2015093731A1 (fr) Dispositif électronique et procédé de fonctionnement associé
WO2024096170A1 (fr) Procédé de fourniture d'informations de dysfonctionnement et dispositif électronique associé
WO2016104873A1 (fr) Dispositif numérique et procédé de commande associé
WO2023171908A1 (fr) Système de gestion de données et procédé de gestion de données collectées en provenance d'un appareil de collecte de données d'usine par l'intermédiaire d'une interface de gestion de données sur le web
WO2024117384A1 (fr) Procédé de gestion d'informations de test et dispositif électronique le prenant en charge
WO2016032260A1 (fr) Dispositif électronique et procédé de réglage de bloc
WO2024147402A1 (fr) Procédé de gestion d'informations de fichier et appareil électronique associé
WO2018169364A1 (fr) Dispositif électronique et procédé permettant de fournir un appel d'urgence, et serveur s'y rapportant
WO2024014597A1 (fr) Procédé de fourniture d'informations de liste d'éléments, et dispositif électronique associé
WO2014171720A1 (fr) Dispositif électronique et procédé de prévention d'erreur d'entrée tactile
WO2023229080A1 (fr) Procédé de recherche d'informations d'article et appareil électronique associé
WO2023229086A1 (fr) Procédé de fourniture d'informations de couverture de code et dispositif électronique associé
WO2024005239A1 (fr) Procédé de fourniture d'informations de page et dispositif élecrtronique associé
WO2024048829A1 (fr) Procédé de gestion d'informations de transfert d'inventaire et appareil électronique associé
WO2024147401A1 (fr) Procédé de fourniture d'informations de page et dispositif électronique associé
WO2024172196A1 (fr) Procédé de fourniture d'informations relatives à un article et appareil électronique associé
WO2024135932A1 (fr) Procédé de fonctionnement d'un dispositif électronique de fourniture d'informations et dispositif électronique le prenant en charge

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22964549

Country of ref document: EP

Kind code of ref document: A1