WO2024053773A1 - Procédé de gestion d'informations de journal et dispositif électronique le prenant en charge - Google Patents

Procédé de gestion d'informations de journal et dispositif électronique le prenant en charge Download PDF

Info

Publication number
WO2024053773A1
WO2024053773A1 PCT/KR2022/015078 KR2022015078W WO2024053773A1 WO 2024053773 A1 WO2024053773 A1 WO 2024053773A1 KR 2022015078 W KR2022015078 W KR 2022015078W WO 2024053773 A1 WO2024053773 A1 WO 2024053773A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
schema
event
log information
log
Prior art date
Application number
PCT/KR2022/015078
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 WO2024053773A1 publication Critical patent/WO2024053773A1/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/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/3438—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 monitoring of user actions
    • 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
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/542—Event management; Broadcasting; Multicasting; Notifications
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]

Definitions

  • the present invention relates to an electronic device and a method for managing log information, and more specifically, to an electronic device and a method for managing logs based on schema information related to an object.
  • an electronic device can acquire log information in response to an event related to a visual object and manage the acquired log information.
  • the electronic device can check whether events related to the object are normally provided to the user based on log information.
  • the electronic device can generate monitoring information based on log information and perform monitoring of events related to the object.
  • Various embodiments may provide a method for managing log information and an electronic device that supports the same.
  • a log information management method performed on an electronic device includes generating schema information about a schema of a first object provided to a user device; Receiving first log information generated based on the schema information from the first server in response to a first event regarding the first object of the first server; And it may include generating monitoring information about the first event based on the first log information.
  • the schema information includes at least identification information for the schema, name information for the schema, name information for the first event, category information for the first event, type information for the first event, and It may include at least part of domain information of the first object, page information including the first object, and version information of the schema.
  • the first log information is generated by a second server based on the schema information, and the second server generates the first log information based on a request for the first event received from the first server.
  • Execution data related to the first object may be provided to the second server.
  • the first server provides an event regarding the first object to the user device based on execution data regarding the first object, and provides the first log information included in the execution data regarding the first object. You can return it as an electronic device.
  • generating the monitoring information may include generating monitoring setting information including identification information about the schema of the first object; Obtaining first log information related to the first object from log information received from the first server based on schema information confirmed based on the monitoring setting information; The method may further include generating monitoring information for the first event based on the collected first log information.
  • the monitoring setting information includes identification information of a schema corresponding to the at least one object, information about at least one parameter related to the first event confirmed based on the schema information, and the monitoring information.
  • the generating step includes classifying the first log information based on the parameters; And it may further include generating the monitoring information based on the classification.
  • the monitoring information includes numerical information about first log information corresponding to the first event
  • the log information management method includes providing information to one or more worker devices corresponding to the electronic device based on the numerical information.
  • the step of providing a notification message may be further included.
  • the log information management method includes providing a notification message to one or more worker devices corresponding to the electronic device based on threshold information confirmed in response to the monitoring information and history information regarding the first log information. It may further include.
  • the log information management method includes receiving information about a user device requesting the first event and second log information generated based on the first event from the first server in response to the first event. step; And it may further include generating monitoring information about the first event based on the first log information and the second log information.
  • the information may include at least part of IP information of the user device, identification information of the user device, platform information of the user device, and identification information about the first event.
  • generating the monitoring information may include checking whether the received first log information is valid based on the schema information; And it may further include generating the monitoring information based on the validity.
  • the schema information further includes information about a valid value of the log
  • the step of checking the validity includes: checking identification information of the schema based on the first log information; The step of comparing the first log information and information on a valid value confirmed corresponding to the identification information of the confirmed schema may be further included.
  • the first object includes a graphical user interface object (GUI)
  • GUI graphical user interface object
  • the first event includes a display event related to the display of the first object or a click event related to the user's input corresponding to the first object. can do.
  • Electronic devices include a transceiver; storage; and a processor, wherein the processor generates schema information about a schema of a first object provided to a user device, and generates the first object in response to a first event about the first object of the first server. It may be configured to receive first log information generated based on the schema information from a server and generate monitoring information about the first event based on the first log information.
  • an electronic device can systematically generate and manage log information about object events by managing schema information including information related to the object.
  • the electronic device 101 can confirm that log information is normally accumulated and monitoring information is generated, and that events for user objects subject to monitoring are normally provided to the user.
  • an electronic device can effectively monitor object-related events provided to a user by generating monitoring information based on log information about object events.
  • the electronic device can efficiently manage object events to be monitored by generating monitoring setting information based on schema information.
  • FIG. 1 is a diagram illustrating a log information management system in which a method of managing log information by an electronic device can be implemented according to various embodiments.
  • FIG. 2 is a diagram illustrating the configuration of an electronic device, a first server, a second server, an operator device, and a user device according to various embodiments.
  • FIG. 3 is a flowchart of an operation in which an electronic device manages log information according to various embodiments.
  • Figure 4 shows a first page for managing schema information by an electronic device according to various embodiments.
  • Figure 5 is a diagram illustrating schema information according to various embodiments.
  • Figure 6 is an additional example of schema information according to various embodiments.
  • FIG. 7 is a diagram for explaining an event related to an object according to various embodiments.
  • FIG 8 is an example diagram of log information according to various embodiments.
  • Figure 9 shows a second page for managing monitoring information according to various embodiments.
  • Figure 10 shows a third page for generating monitoring setting information according to various embodiments.
  • 11 is a diagram for explaining monitoring information according to various embodiments.
  • Figure 12 shows a dashboard page displaying monitoring information according to various embodiments.
  • Figure 13 shows a user interface for operator settings of a dashboard page according to various embodiments.
  • Figure 14 shows a user interface for setting conditions of a dashboard page according to various embodiments.
  • FIG. 15 is a flowchart of an operation in which an electronic device generates monitoring information according to various embodiments.
  • FIG. 16 is a flowchart of an operation in which an electronic device generates monitoring information based on log information according to various embodiments.
  • each component or feature may be considered optional unless explicitly stated otherwise.
  • Each component or feature may be implemented in a form that is not combined with other components or features.
  • various embodiments may be configured by combining some components and features. The order of operations described in various embodiments may change. Some features or features of one embodiment may be included in other embodiments or may be replaced with corresponding features or features of other embodiments.
  • each block of the processing flow diagram 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 flow chart 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 that 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, thereby generating a process that is executed by the computer or other programmable data processing equipment. Instructions that perform processing equipment may also provide steps for executing the functions described in the flow diagram block(s).
  • each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s).
  • each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s).
  • FIG. 1 is a diagram illustrating a log information management system 100 in which a method for managing log information by an electronic device according to various embodiments can be implemented.
  • a log information management system 100 may be implemented in various types of devices.
  • the log information management system 100 may be implemented in an electronic device 101, a first server 102, a second server 103, an operator device 104, and a user device 105.
  • the electronic device 101, the first server 102, the second server 103, the operator device 104, and the user device 105 are based on the log information management system 100 implemented in each device.
  • operations according to various embodiments of the present disclosure can be performed.
  • the log information management system 100 according to various embodiments is not limited to what is shown in FIG. 1, and may be implemented in a wider variety of electronic devices and servers.
  • the electronic device 101 performs wireless and wired communication with the first server 102, the second server 103, and one or more worker devices 104, and provides storage with a large storage capacity. It may be a device including: For example, the electronic device 101 may be a cloud device connected to one or more worker devices 104.
  • the first server 102 performs wireless and wired communication with the electronic device 101, the second server 103, one or more operator devices 104, and one or more user devices 105, It may be a device that includes storage with a large storage capacity.
  • the first server 102 may be a cloud device connected to one or more user devices 105.
  • the first server 102 receives a request related to an event of a user object from the user device 105, transmits it to the second server 103, and receives information provided from the second server 103 based on the request.
  • It may be a front-end server that provides events related to user objects to the user device 105 based on execution data. Events related to user objects may include events related to user interface objects that constitute at least a portion of an application or website (eg, a web application) for a service provided to the user device 105.
  • the second server 103 performs wireless and wired communication with the electronic device 101, the first server 102, and one or more worker devices 104, and provides storage with a large storage capacity. It may be a device including: For example, the second server 103 may be a cloud device connected to one or more worker devices 104. In an embodiment, the second server 103 is a back-end server that provides execution data corresponding to a request related to an event of a user object received from the first server 102 to the first server 102. You can.
  • the worker device 104 may be a device that can be used by an individual user, such as a desktop PC, tablet PC, or mobile terminal.
  • other electronic devices that perform similar functions may be used as the operator device 104.
  • the user device 105 may be a device that can be used by an individual user, such as a desktop PC, tablet PC, or mobile terminal.
  • other electronic devices that perform similar functions may be used as the user device 105.
  • the log information management system 100 may include various modules for operation. Modules included in the log information management system 100 enable a physical device (e.g., electronic device 101) on which the log information management system 100 is implemented (or included in the physical device) to perform a specified operation. It may be implemented computer code or one or more instructions. In other words, the physical device on which the log information management system 100 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 physical device is a plurality of modules. It is possible to perform designated operations corresponding to .
  • a physical device e.g., electronic device 101
  • the physical device on which the log information management system 100 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 physical device is a plurality of modules. It is possible to perform designated operations corresponding to .
  • FIG. 2 is a diagram illustrating the configuration of an electronic device and a user device according to various embodiments.
  • the electronic device 101, the first server 102, the second server 103, the operator device 104, and the user device 105 include an input/output unit 210 and a communication unit 220.
  • the electronic device 101, the first server 102, the second server 103, the operator device 104, and the user device 105 include an input/output unit 210 and a communication unit 220.
  • the input/output unit 210 may be various interfaces or connection ports that receive user input or output information to the user.
  • the input/output unit 210 may include an input module and an output module, and the input module receives user input from the user.
  • User input can 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 module can output various 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 various other 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.
  • LCD liquid crystal display
  • LED light emitting diode
  • OLED organic light emitting diode
  • FPD flat panel display
  • transparent display Among various types of devices that can perform image output functions such as display, curved display, flexible display, 3D display, holographic display, projector, and other It can contain at least one.
  • This display may be in the form of a touch display integrated with the touch sensor of the input module.
  • the communication unit 220 can communicate with other devices. Accordingly, the electronic device 101, the first server 102, the second server 103, the operator device 104, and the user device 105 can transmit and receive information with other devices through the communication unit. For example, the electronic device 101, the first server 102, the second server 103, the operator device 104, and the user device 105 communicate with each other using a communication unit or with other devices. Communication can be performed.
  • the communication department includes a wired communication module that connects to the Internet, etc. through a LAN (Local Area Network), a mobile communication module that transmits and receives data by connecting to a mobile communication network through a mobile communication base station, and a WLAN (Wireless Local Area Network) such as Wi-Fi.
  • a short-distance communication module using an Area Network-type communication method or a WPAN (Wireless Personal Area Network)-type communication method such as Bluetooth or Zigbee, and a GNSS (Global Navigation Satellite System) such as a GPS (Global Positioning System) ) may be composed of a satellite communication module using a satellite communication module or a combination thereof.
  • Storage 230 can store various types of information. Storage can store data temporarily or semi-permanently.
  • the storage of the electronic device 101 includes an operating program (OS: Operating System) for driving the electronic device 101, a program for generating data or Braille for hosting a website, or an application (e.g., Data related to web applications) may be stored.
  • OS Operating System
  • the storage may store modules in the form of computer code as described above.
  • Examples of storage 230 include hard disk drive (HDD), solid state drive (SSD), flash memory, read-only memory (ROM), random access memory (RAM), etc. This can be. This storage can be provided as a built-in or detachable type.
  • HDD hard disk drive
  • SSD solid state drive
  • flash memory read-only memory
  • RAM random access memory
  • the processor 240 controls the overall operation of the electronic device 101, the first server 102, the second server 103, the operator device 104, and the user device 105. To this end, the processor 240 can perform computation and processing of various information and control the operation of components of the electronic device 101. For example, the processor 240 may execute a program or application for managing log information.
  • the processor 240 may be implemented as a computer or similar device using hardware, software, or a combination thereof. In hardware, the processor 240 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 240.
  • the operations of the electronic device 101, the first server 102, the second server 103, the operator device 104, and the user device 105 are performed using the processor 240. It can be interpreted as being carried out under the control of . That is, when the modules implemented in the above-described log information management system 100 are executed, the modules are operated by the processor 240 in the electronic device 101, the first server 102, the second server 103, and the operator device ( 104) and the user device 105 can be interpreted as controlling to perform the following operations.
  • 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), processor, controller, microcontroller, microprocessor, etc.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field programmable gate arrays
  • processor controller, microcontroller, microprocessor, 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 101 performs a log information management operation.
  • the electronic device 101 provides information related to the log information management operation. It can transmit and receive with the first server 102, the second server 103, the operator device 104, and the user device 105.
  • FIG. 3 is a flowchart of an operation in which an electronic device manages log information according to various embodiments.
  • the electronic device 101 may generate schema information (S301).
  • Schema information may include at least information related to user objects provided to the user device 105.
  • the user object may include a graphic user interface (GUI) included in at least part of an accompanying application or website (eg, web application) to provide services to the user.
  • GUI graphic user interface
  • the user object may provide the user with events related to the user object, such as an impression event that displays the user object or a user object that occurs based on user input to the user device 105.
  • Events corresponding to user objects may occur in designated pages provided by applications or websites that provide services.
  • schema information may include one or more information related to an event (eg, first event) corresponding to a designated user object (eg, first object).
  • the electronic device 101 may generate schema information of the first event corresponding to the first object based on the input received through the operator device 104 and store the generated schema information.
  • a schema may include various meta information related to specified objects and events corresponding to the objects. For example, it may include structure information of the object, format information, domain (category) information of the object, and type information of the event corresponding to the object.
  • schema information may include at least identification information about a schema of a designated object (eg, first object) and an event (eg, first event) corresponding to the object.
  • the schema information includes name information for the schema, name information of the first event, category information of the first event, type information of the first event, domain information of the first object, and the first object.
  • schema information about the first object and the first event corresponding to the first object may be updated or changed, and the version information of the schema may be changed in response to the update or change of the schema information.
  • the electronic device 101 may store history information corresponding to each version of the schema.
  • the electronic device 101 may provide schema information to the second server 103 (S302).
  • the second server 103 receives a request related to execution data of an application or website for providing services to the user from the first server 102 and provides execution data corresponding to the request to the first server 102. It may include a backend server.
  • the second server 103 may receive schema information from the electronic device 101 and generate first log information based on the schema information (S310).
  • the first log information may include log information generated based on schema information.
  • the first log information may include data for generating monitoring information corresponding to the first event of the first object.
  • the first log information may be information corresponding to the first object and the first event, which is generated based on schema information.
  • the first log information may include at least part of schema information.
  • the first log information includes identification information for the schema, name information for the schema, name information for the first event, category information for the first event, type information for the first event, and domain of the first object. It may include at least part of information, page information including the first object, and schema version information.
  • the user device 105 may transmit a request regarding the first event to the second server 103.
  • the user device 105 may transmit a request regarding a first event corresponding to a first object to the second server 103.
  • the request regarding the first event may include a request to receive execution data regarding the first event from the second server 103.
  • the user device 105 transmits a first event request to the first server 102 (S311), and the first server 102, which has received the request for the first event, sends the second server ( By transmitting a request for the first event to 103) (S312), the request for the first event can be transmitted from the user device 105 to the second server 103.
  • the user device 105 may directly transmit a request for the first event to the second server 103 using an application related to service provision stored in the user device 105.
  • the second server 103 which has received a request for the first event, may transmit execution data to the first server 102 based on the request for the first event (S313), and the first server 102 A first event may be provided to the user device 105 based on the execution data (S314).
  • the user device 105 when the user device 105 directly transmits a request to the second server 103 using an application related to service provision stored in the user device 105, the user device 105 sends a request to the second server 103.
  • Execution data may be provided directly from 103, and the user device 105 may provide a first event based on the execution data.
  • execution data corresponding to the first event provided by the second server 103 may include first log information.
  • the second server 103 may insert first log information into execution data about the first object corresponding to the first event.
  • Execution data regarding the first object may include first log information at least in part.
  • the electronic device 101 may receive log information from the first server 102 (S303).
  • the electronic device 101 may receive log information including at least first log information included in execution data from the first server 102.
  • the first server 102 may return the first log information included in execution data regarding the first object to the electronic device 101.
  • the log information may include first log information and second log information. The second log information may be generated based on information about the user device 105 and the first event. The second log information may be generated by the first server 102 or the user device 105 based on the first event and transmitted to the electronic device 101.
  • the second log information includes IP address information (internet protocol address information) corresponding to the user device 105, platform information of the user device 105, universally unique identifier (UUID), and personal computer identifier (PCID). ), it may include at least part of time information and application version information.
  • the first server 102 generates the first log information included in the execution data and the first log information included in the execution data in response to receiving the execution data (S313) and/or providing the first event (S314). Log information including second log information may be transmitted to the electronic device 101.
  • the electronic device 101 may generate monitoring information (S304).
  • the electronic device 101 may generate monitoring information corresponding to the first event based on log information.
  • the electronic device 101 may classify log information based on first log information and/or second log information included in each piece of one or more log information.
  • the electronic device 101 processes a plurality of log information based on various data included in the first log information corresponding to the first event, for example, a schema ID, and logs the first log information based on the processed plurality of log information. 1Monitoring information related to events can be created.
  • the electronic device 101 may use a distributed messaging system (e.g., Kafka) to generate monitoring information about the first event by consuming log information distributed for each topic based on the schema ID.
  • the electronic device 101 counts the collected log information to generate numerical information about the first log information corresponding to the first event, and sends a notification about the first event to the operator based on the generated numerical information. It can be provided by device 104.
  • Kafka distributed messaging system
  • Figure 4 shows a first page for managing schema information by an electronic device according to various embodiments.
  • the electronic device 101 may manage schema information through the first page 400.
  • the electronic device 101 may provide the operator device 104 with a first page 400 for managing schema information.
  • the first page 400 may provide a schema creation interface 401 for creating new schema information.
  • Data regarding a new schema can be input through the schema creation interface 401, and schema information created based on the input data can be stored.
  • the first page 400 may provide at least a portion of the schema list 402.
  • the schema list 402 may display one or more schema information.
  • the electronic device 101 may provide a schema information window 403 based on operator input corresponding to at least one schema information included in the schema list 402.
  • the schema information window 403 may display schema information selected from the schema list 402 based on operator input.
  • the schema list 402 may include at least some of identification information (id) for the schema, corresponding application information (tenant), schema name (name), and update information (updated at).
  • the update information may include information about the updated time when the same schema information is updated and changed to a different version. Referring to FIG.
  • the schema information window 403 may be at least a partial area of the first page 400 that specifically displays schema information displayed in the schema list 402.
  • the schema information window 403 includes identification information (id) for the schema, corresponding application information (tenant), schema name (name), update information (updated), description information (description), and creation information (created). ) can be provided.
  • the creation information and update information may include some of the operator information and time information related to the creation or update operation corresponding to the relevant schema information.
  • the first page 400 may include a version creation interface 404 in at least some areas.
  • the electronic device 101 may receive an input regarding a new version for schema information selected from the schema list 402 based on operator input corresponding to the version creation interface 404.
  • inputting a new version may mean that various data included in schema information are changed, deleted, or added.
  • the identification information of the schema can at least be maintained.
  • the first page 400 may provide a version management window 405 in at least some areas and display information about each version corresponding to schema information displayed in the schema information window 403.
  • the version management window 405 may display at least some of version information (version), version status information (state), update time information (updated at), and project information (project).
  • Figure 5 is a diagram illustrating schema information according to various embodiments.
  • Figure 6 is an additional example of schema information according to various embodiments.
  • schema information may include information related to events of user objects.
  • schema information 500 may include at least identification information (schema id) for the schema. Each piece of schema information 500 may be assigned unique schema identification information and may be identified based on the schema identification information.
  • schema information 500 includes state information (state), project information (project), application information corresponding to a user object (tenant), schema name information (schema name), schema description information (schema description), and schema Page information including version information (version), version description information (version description), event category information (log category), event type information (log type), category information (domain), and user objects corresponding to the schema. It may include at least some of (page name), event name information (event name), creation information, and update information.
  • first log information related to an event corresponding to a designated object may be generated based on schema information 500. The first log information may include at least part of the schema information 500.
  • schema information 500 may include additional information 600.
  • Additional information 600 may include different types of data depending on the schema.
  • the additional information 600 may include data items specified for each schema information 500 and related to an object or an event corresponding to the object.
  • the schema information 500 of FIG. 5 may be schema information related to an event corresponding to a widget object, and may include data related to the widget object, such as widget location information (widget position name). ) may be included as additional information 600.
  • the schema information 500 in FIG. 5 may be schema information about a widget that exposes a specific item, and the additional information 600 corresponding to the schema information 500 in FIG. 5 includes item identification information (item id). can do.
  • the first log information may be generated based on the additional information 600 included in the schema information 500.
  • the first log information may include at least part of the additional information 600.
  • FIG. 7 is a diagram for explaining an event related to an object according to various embodiments.
  • the app page 700 is at least a part of a website or application for providing services to users, and is a page provided to the user device 105 from the first server 102 and/or the second server 103 of FIG. 1. It can be.
  • the app page 700 may include at least one object (eg, the first object 701). At least one object may include at least a portion of one or more images, one or more text, and one or more user interfaces.
  • the app page 700 may be a detailed product description page related to a specific item. Referring to the example of FIG.
  • the first object 701 may be a widget that exposes price and discount information for used products or box-damaged products related to the item corresponding to the product detailed description page.
  • the event related to the first object 701 is, for example, an impression event that displays the first object 701 or a first object 701 that occurs based on a user input to the user device 105. ) may include a click event.
  • the electronic device 101 may generate schema information related to an event of the first object 701. Meanwhile, there may be more than one event related to the first object 701. For example, a display event displaying the first object 701, a click event occurring in at least a portion of the first object 701, and a display corresponding to each of one or more user interfaces included in the first object 701. Alternatively, both click events may be events corresponding to the first object 701. As described above, the electronic device 101 may generate schema information corresponding to each of at least some of the one or more events corresponding to an object.
  • the electronic device 101 may receive first log information in response to an event of the first object 701. For example, when an exposure event corresponding to the first object 701 occurs, that is, when the first server 102 receives execution data related to the first object 701 from the second server 103, the first The server 102 may transmit first log information related to the exposure event of the first object 701 included in the execution data to the electronic device 101. The first server 102 may transmit the first log information and the second log information related to the user device 105 to the electronic device 101 by including the second log information in the log information. In response to a first event (e.g., exposure event) about the first object 701, the electronic device 101 sends first log data including information about the first event and the user device 105 that requested the first event. ) can receive second log data containing information about.
  • a first event e.g., exposure event
  • FIG 8 is an example diagram of log information according to various embodiments.
  • log information 800 may include first log information 801 and second log information 802.
  • the first log information 801 may be log information generated based on schema information.
  • the first log information 801 may include various information related to user objects and events corresponding to the user objects.
  • the first log information 801 may include at least schema identification information (schema id).
  • the first log information 801 includes schema version information (schema version), event type information (log type), event reference information (event referrer), category information (domain), event name information (event name), It may include at least part of event category information (log category) and page information (page name) corresponding to the user object.
  • the event reference information may include information corresponding to an event that must precede the occurrence of an event corresponding to the corresponding schema information. For example, a click event on a user object included in a certain widget may be preceded by an exposure event of the widget, and event reference information corresponding to schema information of the click event may be information related to the exposure information of the widget.
  • the second log information 802 may include information about the user device 105.
  • the second log information 802 may be confirmed and/or generated based on the occurrence of an event related to a user object.
  • the second log information 802 includes platform information (platform), universally unique identifier (UUID), personal computer identifier (PCID), language information (lang), and resolution information corresponding to the user device 105. (resolution), time information (event time), application model information (model), and application version information (e.g., application version name information (app version name), application version code information (app version code)) You can.
  • the second server 103 may generate first log information 801 based on schema information, and store the generated first log information 801 in the execution data of the user object corresponding to the schema information. Can be included.
  • the second server 103 may transmit event execution data including first log information 801 to the first server 102 in response to receiving a request for an event related to a user object.
  • the first server 102 sends the first log information 801 included in the execution data and the second log information 802 confirmed and/or generated by the first server 102 to the electronic device 101. ) can be provided.
  • Figure 9 shows a second page for managing monitoring information according to various embodiments.
  • the electronic device 101 may provide the worker device 104 with a second page 900 for managing monitoring information.
  • the second page 900 may provide a monitoring settings list including one or more monitoring settings information 902 corresponding to events related to user objects.
  • the monitoring settings list may include a list of monitoring setting information corresponding to each piece of one or more monitoring information.
  • Monitoring setting information may include basic information for generating monitoring information.
  • the monitoring setting information may include at least schema identification information for one or more schemas that are the target of monitoring in the monitoring information.
  • the second page 900 may provide a monitoring creation interface 901 to create new monitoring setting information.
  • the electronic device 101 may generate monitoring setting information based on input received from the operator device 104 in response to the monitoring creation interface 901.
  • the electronic device 101 may display selected monitoring setting information based on an input for at least a portion of the second page 900 corresponding to the monitoring setting information 902.
  • the second page 900 may display at least part of the task type information (processing time), monitoring type (monitoring type), and name of the monitoring information corresponding to the monitoring setting information.
  • the electronic device 101 may generate monitoring information corresponding to monitoring setting information based on log information and monitoring setting information. For example, referring to the monitoring setting information 902, the task type is near-real-time, which allows monitoring information to be generated by processing log information in close real-time, and the monitoring type is log counting. Since it corresponds to the (raw log count) method, the electronic device 101 can classify log information corresponding to the monitoring setting information 902 and generate monitoring information based on numerical information of the classified log information.
  • Figure 10 shows a third page for generating monitoring setting information according to various embodiments.
  • the third page 1000 may be a page provided based on input to the monitoring creation interface 901 of FIG. 9 .
  • the third page 1000 may provide various interfaces for inputting monitoring setting information.
  • the third page 1000 is based on the name interface 1001 for receiving the name of monitoring information, the schema selection interface 1002 for receiving schema information to be monitored, and the input to the schema selection interface 1002. It may include at least part of schema identification information 1003, schema name information 1004, and schema description information 1005 corresponding to the schema information selected.
  • the electronic device 101 may generate monitoring information based on monitoring setting information.
  • the electronic device 101 may check log information based on one or more schema information confirmed based on monitoring setting information and generate monitoring information corresponding to the monitoring setting information based on the confirmed log information. there is.
  • the third page 1000 may include a filter setting interface 1006.
  • the filter setting interface 1006 can set conditions for filtering log information about selected schema information in response to monitoring setting information. Filtering conditions may be set differently in response to each schema information. Filtering conditions may be set in response to a plurality of items included in log information. For example, a filter regarding platform information may be set among the items included in log information. In this case, only log information about platform information corresponding to the set filter can serve as the basis for monitoring information.
  • the third page 1000 may include a labeling interface 1007. Based on the input to the labeling interface 1007, the electronic device 101 may group one or more schema information selected in response to the monitoring setting information and set a label to distinguish each group.
  • 11 is a diagram for explaining monitoring information according to various embodiments.
  • a monitoring page 1100 displaying monitoring information corresponding to monitoring setting information 902 selected on the second page 900 of FIG. 9 may be shown.
  • the monitoring page 1100 may display monitoring information generated in response to selected monitoring setting information.
  • Monitoring information may include numerical information generated based on log information.
  • the numerical information may include a graph 1102 generated based on log information.
  • the electronic device 101 may check log information based on monitoring setting information and generate monitoring information based on the confirmed log information.
  • the monitoring setting information may include selected schema information corresponding to schema identification information of '10', '116', and '124', respectively.
  • monitoring information (e.g., graph 1102) generated based on monitoring setting information may be generated based on log information corresponding to schema identification information '10', '116', and '124', respectively. That is, the graph 1102 in FIG. 11 is generated based on log information received by the electronic device 101 in response to events of objects corresponding to schema identification information '10', '116', and '124', respectively. It can be understood.
  • monitoring page 1100 may display at least part of the monitoring setting information 1103 corresponding to the monitoring information being monitored.
  • monitoring setting information 1103 includes a task type (processing type), name information of monitoring information (monitoring name), description information of monitoring information (description), creation information of monitoring setting information (created), and monitoring information. It may include at least part of the latest update information (last modified) of the setting information and expiry date of the monitoring setting information.
  • monitoring page 1100 may include a dashboard icon 1101 for displaying a dashboard page displaying one or more monitoring information.
  • the electronic device 101 may provide a dashboard page that displays one or more monitoring information based on input to the dashboard icon 1101.
  • Figure 12 shows a dashboard page displaying monitoring information according to various embodiments.
  • Figure 13 shows a user interface for operator settings of a dashboard page according to various embodiments.
  • the dashboard page 1200 may display one or more monitoring information.
  • the dashboard page 1200 may generate and display one or more monitoring information based on one or more log information confirmed based on monitoring setting information.
  • the dashboard page 1200 may display a monitoring name corresponding to monitoring setting information regarding the monitoring target on the first interface 1201.
  • the dashboard page 1200 may include one or more interfaces for displaying monitoring information in a variety of ways.
  • the dashboard page 1200 can generate various numerical information corresponding to log information based on settings through one or more interfaces.
  • the electronic device 101 may classify one or more log information selected based on monitoring setting information, based on settings through one or more interfaces of the dashboard page 1200, and each classified log information One or more monitoring information can be generated by generating corresponding numerical information.
  • the dashboard page 1200 includes a second interface 1202 for selecting application information (tenant), a third interface for selecting at least some schema information among one or more schema information corresponding to monitoring setting information ( 1203), a fourth interface 1204 for selecting at least one version among one or more versions corresponding to the selected schema information, and a fifth interface for selecting based on the platform among log information confirmed based on monitoring setting information ( 1205) and a sixth interface 1206 for setting a time category.
  • the electronic device 101 may generate one or more monitoring information based on selection items set in each of one or more interfaces of the dashboard page 1200.
  • the dashboard page 1200 displays log information corresponding to the monitoring setting information based on platform information based on the corresponding monitoring setting information and settings of one or more interfaces (e.g., the fifth interface 1205).
  • the first graph 1207 which is sorted monitoring information
  • the dashboard page 1200 stores log information corresponding to the monitoring setting information in a schema based on the corresponding monitoring setting information and the settings of one or more interfaces (e.g., the third interface 1203).
  • a second graph 1208, which is monitoring information sorted based on the information, can be generated.
  • the time category interface 1300 may include a first area 1301 for setting a category based on absolute time and a second area 1302 for setting a category based on relative time.
  • the dashboard page 1200 may generate and display monitoring information corresponding to the set time category based on the setting of the time category interface 1300.
  • Figure 14 shows a query area 1400 for setting conditions of a dashboard page according to various embodiments.
  • the dashboard page 1200 of FIG. 12 may include a query area 1400 for setting notification conditions corresponding to each monitoring information in at least some areas.
  • the electronic device 101 may set notification conditions corresponding to one or more pieces of monitoring information based on one or more interfaces included in the query area 1400.
  • the electronic device 101 may provide a notification regarding corresponding monitoring information to the operator device 104 based on set notification conditions.
  • the query area 1400 may include a rule interface 1410 for setting rules and a condition interface 1420 for setting conditions.
  • the rule interface 1410 may set at least some of the name 1411 corresponding to the notification condition, period information 1412 for checking whether the notification condition is satisfied, and notification time interval information 1413.
  • the condition interface 1420 may receive input of one or more condition directives 1421, 1423, and 1425 and values 1422, 1424, and 1426 corresponding to target values of the condition directives.
  • the electronic device 101 displays the average value (avg()) of 'A' monitoring information from 5 minutes (5 m) ago to now, based on the condition interface 1420. If it exceeds '100', a notification message corresponding to the monitoring information may be provided to the operator device 104.
  • FIG. 15 is a flowchart of an operation in which an electronic device generates monitoring information according to various embodiments.
  • the electronic device 101 may generate schema information.
  • Schema information may include at least information related to user objects provided to the user device 105.
  • the user object may provide events related to the user object to the user, and schema information may include information about events corresponding to the user object.
  • Events may include, for example, exposure events that display user objects or click events on user objects that occur based on user input to user device 105.
  • Events corresponding to user objects may occur in designated pages provided by applications or websites that provide services.
  • schema information may include one or more information related to an event (eg, first event) corresponding to a designated user object (eg, first object).
  • the electronic device 101 may generate schema information of the first event corresponding to the first object based on the input received through the operator device 104 and store the generated schema information.
  • a schema may include various meta information related to specified objects and events corresponding to the objects. For example, it may include structure information of the object, format information, domain (category) information of the object, and type information of the event corresponding to the object.
  • schema information may include at least identification information about a schema of a designated object (eg, first object) and an event (eg, first event) corresponding to the object.
  • the schema information includes name information for the schema, name information of the first event, category information of the first event, type information of the first event, domain information of the first object, and the first object.
  • schema information about the first object and the first event corresponding to the first object may be updated or changed, and the version information of the schema may be changed in response to the update or change of the schema information.
  • the electronic device 101 may store history information corresponding to each version of the schema.
  • the electronic device 101 may receive first log information generated based on schema information.
  • the first log information may include log information generated based on schema information.
  • the first log information may include data for generating monitoring information corresponding to the first event of the first object.
  • the first log information may be information corresponding to the first object and the first event, which is generated based on schema information.
  • the first log information may include at least part of schema information.
  • the first log information includes identification information for the schema, name information for the schema, name information for the first event, category information for the first event, type information for the first event, and domain of the first object. It may include at least part of information, page information including the first object, and schema version information.
  • the electronic device 101 may generate monitoring information based on the first log information.
  • the electronic device 101 may generate monitoring information corresponding to an event based on log information.
  • the electronic device 101 may classify log information based on first log information and/or second log information included in each piece of one or more log information.
  • the electronic device 101 processes a plurality of log information based on various data included in the first log information corresponding to the first event, for example, a schema ID, and logs the first log information based on the processed plurality of log information. 1Monitoring information related to events can be created.
  • the electronic device 101 may use a distributed messaging system (e.g., Kafka) to generate monitoring information about the first event by consuming log information distributed for each topic based on the schema ID.
  • a distributed messaging system e.g., Kafka
  • the electronic device 101 sorts and/or counts the collected log information to generate numerical information about the first log information corresponding to the first event, and generates numerical information about the first log information based on the generated numerical information. Notifications may be provided to the operator device 104.
  • the electronic device 101 may set a threshold value for monitoring information.
  • the threshold value may be a threshold value for providing a notification message by comparing numerical information included in monitoring information.
  • the electronic device 101 may provide a notification message regarding the first event to the worker device 104 based on monitoring information and comparison with the threshold value.
  • monitoring setting information may include information regarding threshold values.
  • the electronic device 101 may set a threshold value in response to history information regarding log information. For example, a threshold value corresponding to monitoring information can be set based on a period-specific trend of numerical information related to log information.
  • FIG. 16 is a flowchart of an operation in which an electronic device generates monitoring information based on log information according to various embodiments.
  • the electronic device 101 may acquire log information.
  • the electronic device 101 may obtain log information about the event from the first server 102 in response to the event provided by the first server 102 to the user device 105.
  • the log information may include first log data included in execution data about an event corresponding to a user object and second log data including information about the user device 105.
  • the electronic device 101 in response to a request for an object-related event, sends the first log information included in the execution data received by the first server 102 from the second server 103 and the first server 102 to the user. Second log information confirmed based on the device 105 may be received from the first server 102.
  • the electronic device 101 may check the validity of the received log information.
  • the electronic device 101 may check whether log information is valid based on schema information. For example, the electronic device 101 may check whether the log information is valid based on the first log information included in the log information and schema information corresponding to the first log information. Since the first log information is generated based on schema information, it is possible to check whether the log information was generated validly by checking the schema information.
  • the electronic device 101 may check corresponding schema identification information based on the first log information.
  • the electronic device 101 can compare the first log information among the schema information confirmed based on the schema identification information and the received log information, and check whether the first log information is valid based on the comparison.
  • schema information may include information about valid values.
  • schema information may include an item regarding a valid value among one or more items included in the schema information.
  • the electronic device 101 may compare the first log information based on information about the valid value confirmed based on the schema information and check whether the log information is valid.
  • the electronic device 101 may generate monitoring information about an event of an object based on log information and monitoring setting information.
  • the electronic device 101 may classify the received log information based on monitoring setting information.
  • Monitoring setting information may include basic information for generating monitoring information.
  • the monitoring setting information may include at least schema identification information for one or more schemas that are the target of monitoring in the monitoring information.
  • the electronic device 101 may generate monitoring setting information based on input received from the operator device 104.
  • the electronic device 101 may generate monitoring information corresponding to monitoring setting information based on log information and monitoring setting information.
  • the electronic device 101 may classify log information corresponding to the monitoring setting information based on the monitoring setting information and generate monitoring information based on numerical information of the classified log information.
  • the electronic device 101 may check log information corresponding to schema information confirmed based on monitoring setting information.
  • the electronic device 101 may classify log information based on schema identification information corresponding to monitoring setting information and generate numerical information based on the classified log information.
  • the generated numerical information may be included in monitoring information corresponding to monitoring setting information.
  • the electronic device 101 may generate monitoring information based on whether log information is valid.
  • the electronic device 101 may use the valid log information confirmed in operation S1602 to generate monitoring information based on the log information in operation S1603.
  • the electronic device 101 may generate monitoring information based on log information that is not valid.
  • the electronic device 101 may check schema identification information based on invalid log information and classify invalid logs according to schema identification information.
  • the electronic device 101 may generate monitoring information based on invalid log information corresponding to each schema identification information, and may provide a notification message based on numerical information included in the generated monitoring information.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Software Systems (AREA)
  • General Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • Development Economics (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Multimedia (AREA)
  • Debugging And Monitoring (AREA)

Abstract

L'invention divulgue un procédé de gestion d'informations de journal mis en œuvre par un dispositif électronique, comprenant les étapes consistant à : générer des informations de schéma concernant un schéma d'un premier objet fourni à un dispositif utilisateur ; recevoir des premières informations de journal générées sur la base des informations de schéma en provenance d'un premier serveur en réponse à un premier événement concernant le premier objet du premier serveur ; et générer des informations de surveillance concernant le premier événement sur la base des premières informations de journal.
PCT/KR2022/015078 2022-09-07 2022-10-07 Procédé de gestion d'informations de journal et dispositif électronique le prenant en charge WO2024053773A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2022-0113459 2022-09-07
KR1020220113459A KR20240034452A (ko) 2022-09-07 2022-09-07 로그 정보를 관리하는 방법 및 이를 지원하는 전자 장치

Publications (1)

Publication Number Publication Date
WO2024053773A1 true WO2024053773A1 (fr) 2024-03-14

Family

ID=90191339

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2022/015078 WO2024053773A1 (fr) 2022-09-07 2022-10-07 Procédé de gestion d'informations de journal et dispositif électronique le prenant en charge

Country Status (3)

Country Link
KR (1) KR20240034452A (fr)
TW (1) TW202429287A (fr)
WO (1) WO2024053773A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20140137653A (ko) * 2013-05-23 2014-12-03 삼성전자주식회사 전자장치의 이벤트 로그 분석 방법 및 장치
US20150227598A1 (en) * 2014-02-13 2015-08-13 Amazon Technologies, Inc. Log data service in a virtual environment
KR101754908B1 (ko) * 2010-12-20 2017-07-07 애플 인크. 이벤트 인식
KR102349495B1 (ko) * 2020-11-18 2022-01-11 쿠팡 주식회사 가상 서버들로부터 대용량 로그 파일들을 프로세싱하는 컴퓨터 시스템 및 방법.
US20220132303A1 (en) * 2020-10-26 2022-04-28 International Business Machines Corporation Internet of things device provisioning

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101754908B1 (ko) * 2010-12-20 2017-07-07 애플 인크. 이벤트 인식
KR20140137653A (ko) * 2013-05-23 2014-12-03 삼성전자주식회사 전자장치의 이벤트 로그 분석 방법 및 장치
US20150227598A1 (en) * 2014-02-13 2015-08-13 Amazon Technologies, Inc. Log data service in a virtual environment
US20220132303A1 (en) * 2020-10-26 2022-04-28 International Business Machines Corporation Internet of things device provisioning
KR102349495B1 (ko) * 2020-11-18 2022-01-11 쿠팡 주식회사 가상 서버들로부터 대용량 로그 파일들을 프로세싱하는 컴퓨터 시스템 및 방법.

Also Published As

Publication number Publication date
TW202429287A (zh) 2024-07-16
KR20240034452A (ko) 2024-03-14

Similar Documents

Publication Publication Date Title
WO2013103243A1 (fr) Procédé et terminal de partage de contenu
WO2011099808A2 (fr) Procédé et appareil permettant de fournir une interface utilisateur
WO2018164532A1 (fr) Système et procédé pour améliorer l'expérience de réalité augmentée (ar) sur un équipement utilisateur (ue) sur la base de contenus dans un dispositif
WO2020256368A1 (fr) Système et procédé de publicité utilisant des produits numériques géolocalisés en réalité augmentée
WO2014119950A1 (fr) Procédé permettant de fournir un service pour trouver un objet perdu à l'aide d'un programme d'application de messagerie
WO2024053773A1 (fr) Procédé de gestion d'informations de journal et dispositif électronique le prenant en charge
WO2013118971A1 (fr) Procédé et système pour compléter des informations horaires, et support d'enregistrement lisible par ordinateur sur lequel est enregistré un programme d'exécution du procédé
WO2023229093A1 (fr) Procédé de gestion d'informations d'inventaire et dispositif électronique le prenant en charge
WO2023033219A1 (fr) Procédé de fonctionnement pour fournir des informations relatives à un service et dispositif électronique le prenant en charge
WO2016208877A1 (fr) Procédé de fourniture de contenu supplémentaire à un terminal, et terminal utilisant ce procédé
WO2024085275A1 (fr) Procédé de détection d'utilisateur anormal et dispositif électronique le prenant en charge
WO2024038950A1 (fr) Procédé de gestion d'information d'articles et dispositif électronique pour le fournir
WO2024150871A1 (fr) Procédé de fourniture d'informations et dispositif électronique le prenant en charge
WO2016080756A1 (fr) Système de gestion d'informations et procédé de gestion d'informations
WO2024014583A1 (fr) Procédé de fourniture d'informations d'article et dispositif électronique le prenant en charge
WO2023229080A1 (fr) Procédé de recherche d'informations d'article et appareil électronique associé
WO2023249150A1 (fr) Procédé permettant de faire fonctionner un dispositif électronique fournissant des informations, et dispositif électronique le prenant en charge
WO2023017877A1 (fr) Procédé de fonctionnement d'un dispositif électronique permettant de fournir des informations de recherche, et dispositif électronique le prenant en charge
WO2024143687A1 (fr) Procédé de fourniture d'informations de service et dispositif électronique le prenant en charge
WO2022265145A1 (fr) Procédé de fonctionnement de dispositif électronique pour fournir un message publicitaire, et dispositif électronique le prenant en charge
WO2024143673A1 (fr) Procédé de commande d'un dispositif électronique fournissant des informations, et dispositif électronique le prenant en charge
WO2024143688A1 (fr) Procédé de gestion d'informations de service et dispositif électronique le prenant en charge
WO2024225516A1 (fr) Procédé de gestion d'informations de promotion et dispositif électronique associé
WO2017065333A1 (fr) Procédé de commande de sortie de tickets photo pour utilisateur en attente de service, et serveur d'exploitation de tickets photo prenant en charge le procédé
WO2024038951A1 (fr) Procédé de fourniture d'informations de code 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: 22958227

Country of ref document: EP

Kind code of ref document: A1