Event data determination method and device, storage medium and electronic equipment

By collecting and saving public information on the front-end page and obtaining the required event data according to the event type, the problem of low event processing efficiency caused by repeated acquisition of public information is solved, and the system's processing efficiency and performance are improved.

CN118939454APending Publication Date: 2024-11-12QINGDAO HAIER TECH +2
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411073497.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-06
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

In the prior art, public information needs to be obtained repeatedly, resulting in low event processing efficiency.

Method used

When receiving pending events on the front-end page, public information is collected and saved in the event collector, and the required event data is obtained according to the event type (single event or combined event), avoiding repeated acquisition of public information and improving event processing efficiency.

Benefits of technology

By reducing the duplicate acquisition of public information, the event processing efficiency is significantly improved, and the system performance and response speed are improved.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118939454A_ABST
    Figure CN118939454A_ABST
Patent Text Reader

Abstract

The invention discloses an event data determination method and device, a storage medium and electronic equipment, and relates to the technical field of smart homes. The event data determination method comprises the steps of receiving a to-be-processed event corresponding to a front-end page under the condition that the front-end page receives a loading operation of a target object, collecting public information of the to-be-processed event, and storing the collected public information in an event collector; and determining that the event type of the to-be-processed event is a single event, acquiring the public information from the event collector, and determining event data required for executing the to-be-processed event according to the public information. By adopting the technical scheme, the problem that the event processing efficiency is not high due to the fact that public information needs to be repeatedly acquired in the related technology is solved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of smart home technology, and more specifically, to a method and device for determining event data, a storage medium, and an electronic device. Background Art

[0002] In the related art, when the target object performs front-end page operations, public information is re-acquired each time the page is loaded, resulting in a long time to call the required public information during the processing of a single event, thereby affecting the event processing efficiency.

[0003] In view of the problem in related technologies that event processing efficiency is low due to the need to repeatedly obtain public information, no effective solution has been proposed yet. Summary of the invention

[0004] The embodiments of the present application provide a method and device for determining event data, a storage medium, and an electronic device, so as to at least solve the problem in the related art that event processing efficiency is low due to the need to repeatedly obtain public information.

[0005] According to an embodiment of the present application, a method for determining event data includes: when a front-end page receives a loading operation of a target object, receiving a pending event corresponding to the front-end page, collecting public information of the pending event, and saving the collected public information in an event collector; determining that the event type of the pending event is a single event, obtaining the public information from the event collector, and determining the event data required to execute the pending event based on the public information.

[0006] In an optional embodiment, determining the event data required to execute the event to be processed based on the public information includes: when the public information is the same content included in different events to be processed, obtaining difference data corresponding to the event to be processed; determining the event data required to execute the event to be processed based on the public information and the difference data.

[0007] In an optional embodiment, after determining the event data required to execute the event to be processed based on the common information and the difference data, the method further includes: executing the event to be processed based on the event data to obtain an execution result of the event to be processed; adding the execution result to the event sequence set for the event processor, so that when the execution result is needed again, the execution result can be called from the event processor.

[0008] In an optional embodiment, after receiving the pending event corresponding to the front-end page, the method further includes: when it is determined that the event type of the pending event is a combined event, and the common information is the same content included in different pending events, obtaining the common information of the combined event and the difference data of the combined event from the event collector through the event processor, and obtaining the execution result of the first event pre-saved in the event sequence set for the event processor, wherein the combined event includes a first event and a second event, and the execution of the second event depends on the execution result of the first event; executing the second event according to the common information of the combined event, the difference data of the combined event and the execution result of the first event.

[0009] In an optional embodiment, after receiving the pending events corresponding to the front-end page, the method also includes: obtaining the event number of the pending events; when the event number is one, determining that the event type of the pending event is a single event; when the event number is at least two, determining whether there is a dependency relationship between the at least two pending events, and if there is a dependency relationship, determining that the at least two pending events are combined events.

[0010] In an optional embodiment, after determining the event data required to execute the event to be processed based on the public information, the method also includes: detecting the current state of the event to be processed; when it is detected that the event to be processed has been completed, determining the state of the event to be processed as the end state; and passing the state of the event to be processed to the execution layer through an external communicator.

[0011] In an optional embodiment, collecting the public information of the event to be processed includes: determining the content included in the public information of the event to be processed and the collection method for the public information; collecting the content according to the collection method to obtain the public information of the event to be processed.

[0012] According to another aspect of the present invention, a device for determining event data is also provided, including: a receiving module, which is used to receive the pending event corresponding to the front-end page when the front-end page receives the loading operation of the target object, collect the public information of the pending event, and save the collected public information in an event collector; an execution module, which is used to determine that the event type of the pending event is a single event, obtain the public information from the event collector, and determine the event data required to execute the pending event based on the public information.

[0013] According to another aspect of the embodiments of the present application, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program is configured to execute the above-mentioned method for determining event data when running.

[0014] According to another aspect of an embodiment of the present application, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the method for determining event data through the computer program.

[0015] According to another aspect of the embodiments of the present application, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the method for determining the event data described above is implemented.

[0016] In an embodiment of the present application, when the front-end page receives a load operation of a target object, the to-be-processed event corresponding to the front-end page is received, the public information of the to-be-processed event is collected, and the collected public information is saved in an event collector; the event type of the to-be-processed event is determined to be a single event, the public information is obtained from the event collector, and the event data required to execute the to-be-processed event is determined based on the public information. The above technical solution solves the problem in the related art that event processing efficiency is low due to the need to repeatedly obtain public information. There is no need to repeatedly obtain public information, thereby improving event processing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0018] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0019] Figure 1 It is a hardware environment diagram of a method for determining event data in an embodiment of the present application;

[0020] Figure 2 is a flowchart of a method for determining event data according to an embodiment of the present application;

[0021] Figure 3 A system flow chart of a method for determining event data according to an optional embodiment of the present application;

[0022] Figure 4is a detailed flow chart of a method for determining event data according to an optional embodiment of the present application;

[0023] Figure 5 It is a structural block diagram of a device for determining event data according to an embodiment of the present application. DETAILED DESCRIPTION

[0024] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0025] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0026] According to one aspect of an embodiment of the present application, a method for determining event data is provided. The method for determining event data is widely used in smart home (Smart Home), smart home, smart home device ecology, smart residential (Intelligence House) ecology and other whole-house intelligent digital control application scenarios. Optionally, in this embodiment, the above-mentioned method for determining event data can be applied to Figure 1 The hardware environment is composed of the operating system 102 and the execution layer 104 shown in FIG. Figure 1 As shown, the event processing center 102 is connected to the home appliance 104 via a network, and can be used to provide services (such as application services, etc.) for the event processing center 102 or a client installed on the event processing center 102. A database can be set on the event processing center 102 or independently of the event processing center 102 to provide data storage services for the event processing center 102 and the home appliance 104. Cloud computing and / or edge computing services can be configured on the event processing center 102 or independently of the event processing center 102 to provide data computing services for the event processing center 102 and the home appliance 104.

[0027] The above network may include but is not limited to at least one of the following: wired network, wireless network. The above wired network may include but is not limited to at least one of the following: wide area network, metropolitan area network, local area network, and the above wireless network may include but is not limited to at least one of the following: WIFI (Wireless Fidelity), Bluetooth. The event processing center 102 and the home appliance 104 may not be limited to PC, mobile phone, tablet computer, smart air conditioner, smart range hood, smart refrigerator, smart oven, smart stove, smart washing machine, smart water heater, smart washing equipment, smart dishwasher, smart projection equipment, smart TV, smart clothes drying rack, smart curtain, smart audio and video, smart socket, smart audio, smart speaker, smart fresh air equipment, smart kitchen and bathroom equipment, smart bathroom equipment, smart sweeping robot, smart window cleaning robot, smart mopping robot, smart air purification equipment, smart steamer, smart microwave oven, smart kitchen treasure, smart purifier, smart water dispenser, system platform, etc.

[0028] In this embodiment, a method for determining event data is provided, which is applied to the above event processing center. Figure 2 : is a flowchart of a method for determining event data according to an embodiment of the present application, the process includes the following steps:

[0029] Step S202, when the front-end page receives a load operation of the target object, receiving a to-be-processed event corresponding to the front-end page, collecting public information of the to-be-processed event, and storing the collected public information in an event collector;

[0030] Step S204, determining that the event type of the event to be processed is a single event, obtaining the public information from the event collector, and determining event data required to execute the event to be processed according to the public information;

[0031] In an embodiment of the present application, when the front-end page receives a load operation of a target object, the to-be-processed event corresponding to the front-end page is received, the public information of the to-be-processed event is collected, and the collected public information is saved in an event collector; the event type of the to-be-processed event is determined to be a single event, the public information is obtained from the event collector, and the event data required to execute the to-be-processed event is determined based on the public information. The above technical solution solves the problem in the related art that event processing efficiency is low due to the need to repeatedly obtain public information. There is no need to repeatedly obtain public information, thereby improving event processing efficiency.

[0032] In an optional embodiment, determining the event data required to execute the event to be processed based on the public information can be achieved through the following technical solution: when the public information is the same content included in different events to be processed, obtaining the difference data corresponding to the event to be processed; determining the event data required to execute the event to be processed based on the public information and the difference data.

[0033] When the target object is loaded on the front-end page, the event collector will receive multiple pending events. The information contained in the above multiple pending events is the common information. Since each pending event is different, each corresponding individual pending event has its own required data, which is the difference data of each individual pending event. The event data required for the pending event can be determined based on the common information and difference data.

[0034] For example, when the target object submits a fault repair ticket on the front-end page, the event collector will receive the fault repair event and collect the common information of the fault repair event, such as the target object's name, contact information, and home address. The difference data includes the model of the repaired device, fault description, and urgency. Through these common information and difference data, the event data required for the fault repair event can be determined.

[0035] In an optional embodiment, after determining the event data required to execute the event to be processed based on the common information and the difference data, the method further includes: executing the event to be processed based on the event data to obtain an execution result of the event to be processed; adding the execution result to the event sequence set for the event processor, so that when the execution result is needed again, the execution result can be directly called from the event processor.

[0036] For example, suppose the target object Zhang reported a malfunction in his home air conditioning equipment on the front-end page. Public information includes Zhang's name as Zhang San, contact number as mobile phone number 123456789, and home address as No. XX, XX Street. Difference data includes the model of the equipment reported as XX air conditioner, the fault description as the air conditioner cannot cool, and the urgency level as high. Based on the above event data, the event processor arranges for a technician to go to Zhang's home to check the air conditioning fault. The execution result of the event includes but is not limited to: the fault repair measures that can be taken for this type of air conditioning fault, and the execution result is saved in the event sequence so that when Zhang later inquires about the fault repair situation on the front-end page, the event processor can directly retrieve the execution result.

[0037] In an optional embodiment, after receiving the pending event corresponding to the front-end page, the method further includes: when it is determined that the event type of the pending event is a combined event, and the common information is the same content included in different pending events, obtaining the common information of the combined event and the difference data of the combined event from the event collector through the event processor, and obtaining the execution result of the first event pre-saved in the event sequence set for the event processor, wherein the combined event includes a first event and a second event, and the execution of the second event depends on the execution result of the first event; executing the second event according to the common information of the combined event, the difference data of the combined event and the execution result of the first event.

[0038] Alternatively, suppose Zhang places an order to buy a product on a shopping website. This order purchase event is a combined event, in which the first event is to check whether the product inventory is sufficient, and the second event is to place an order to purchase. Only when the execution result of the first event is "sufficient" can the second event continue to execute. In this combined event, the public information includes Zhang's name as Zhang San, the contact information is the mobile phone number 123456789, and the home address is No. XX, XX Street; the difference data includes the product name, payment amount and payment method.

[0039] In an optional embodiment, after receiving the pending events corresponding to the front-end page, the method also includes: obtaining the event number of the pending events; when the event number is one, determining that the event type of the pending event is a single event; when the event number is at least two, determining whether there is a dependency relationship between the at least two pending events, and if there is a dependency relationship, determining that the at least two pending events are combined events.

[0040] When the number of events is one, it can be determined that the event type of the event to be processed is a single event. This means that the event collector only receives one event, and the event processor can directly process the event without considering the impact of other events. For example, suppose the target object clicks the "Turn on the air conditioner" button on the front-end page, and the event collector receives an event of the target object clicking. In this case, it can be determined that this event is a single event because it only involves one operation: clicking the button.

[0041] When the number of events is at least two, it is necessary to determine whether there is a dependency between these events. If there is a dependency, these events can be combined into a composite event for processing. For example, suppose that in an e-commerce platform, the event collector receives two events: user order and inventory update. There is a dependency between these two events, that is, user order will cause inventory update. In this case, the two events can be regarded as a composite event.

[0042] In an optional embodiment, after determining the event data required to execute the event to be processed based on the public information, the method also includes: detecting the current state of the event to be processed; when it is detected that the event to be processed has been completed, determining the state of the event to be processed as the end state; and passing the state of the event to be processed to the execution layer through an external communicator.

[0043] Alternatively, suppose the front-end page is an online payment system. When the target object submits a payment request, the event collector receives a pending event and hands it over to the event handler for processing. The event handler detects the status of the event, such as whether the payment is successful or failed. The event handler updates the status of the event to the end state and passes the status to the execution layer of the front-end page through the external communicator (equivalent to Figure 3 component business layer) so that the execution layer can perform subsequent operations such as order processing.

[0044] In an optional embodiment, collecting the public information of the event to be processed includes: determining the content included in the public information of the event to be processed and the collection method for the public information; collecting the content according to the collection method to obtain the public information of the event to be processed.

[0045] When the target object is loaded on the front-end page, the event collector will receive multiple pending events. The information contained in the above pending events is public information. Usually, the content of public information includes: basic information of the target object, such as name, age, contact information, home address, health status; page information, such as the URL and page title of the page where the target object is operating.

[0046] The methods for collecting public information include the following:

[0047] Front-end monitoring: By embedding scripts, such as JavaScript, in H5 pages, it can capture and record the behavior of the target object and related information of page loading.

[0048] Server log: Through the server-side logging function, collect all HTTP request information when the target object requests a page.

[0049] In order to better understand the process of the method for determining the above event data, the process of the method for determining the above event data is described below in combination with an optional embodiment, but it is not used to limit the technical solution of the embodiment of the present application.

[0050] Figure 3 is a system flow chart of a method for determining event data according to an optional embodiment of the present invention, which introduces the event processing flow from the activity initialization process to the final page presentation and the target object operating on the page. Figure 3 As shown, the specific steps include:

[0051] In an optional embodiment of the present invention, when the target object is loaded on the front-end page, the event processing center (equivalent to Figure 3 The event worker (also called event processor) embeds a script in the H5 page (equivalent to the front-end page of the aforementioned embodiment) to capture and record the basic information of the target object, such as name, age, contact information, home address, health status, and relevant information of page loading, such as the URL and page title of the page where the target object is operating. This information is stored as public information so that it does not need to be obtained twice in subsequent event processing.

[0052] After collecting public information, the event processing center will process the execution layer of the front-end page (equivalent to Figure 3 The purpose is to use multi-threaded concurrent processing efficiently when processing events, improving page performance and response speed. For example, if an online shopping website collects information about orders placed by target objects, it is necessary to initialize thread processing for the order processing module in the execution layer so that order information of multiple target objects can be processed simultaneously to ensure timely processing and delivery of orders.

[0053] After the execution layer of the front-end page completes the initialization thread processing in the event processing center, it renders basic data to the front-end page. These data are usually returned by the back-end interface or generated by the front-end logic processing. By rendering these basic data to the page, the target object can see real-time information and load the page. For example, suppose there is a product details page on an e-commerce website, which contains the name, price, description and other information of the product. In this scenario, the execution layer of the front-end page can render basic data to the front-end page, such as the name of the product is "A mobile phone", the price is "XXX yuan", and the description is "new flagship mobile phone, welcome to buy". These data will be dynamically displayed on the page, allowing the target object to intuitively understand the information of the product, and then make purchases or other operations.

[0054] When the target object is loaded on the front-end page, the front-end page transmits events to the execution layer of the front-end page by calling components, and then the execution layer of the front-end page transmits the pending events to the event processing center. Optionally, assuming that the front-end page has a search box component, the target object enters keywords in the search box and clicks the search button. The front-end page will pass the keywords entered by the target object to the execution layer of the front-end page. After receiving the keywords, the execution layer of the front-end page will send a request to the event processing center to obtain search results based on the keywords, and finally return the search results to the front-end page for display.

[0055] When the execution layer of the front-end page adds the pending events to the event processing center, the event processing center will receive the events to be processed, obtain the difference data of different pending events from the data layer, and execute the pending events in combination with the public information stored in the event processing center. After the pending events are completed, the event status is updated to "end", and the event status is passed to the execution layer of the front-end page. When a new event status is received, the execution layer of the front-end page returns the execution result to the front-end page, and the front-end page renders the new event data.

[0056] Figure 4 is a detailed flow chart of a method for determining event data according to an optional embodiment of the present invention, such as Figure 4 As shown, the specific steps include:

[0057] In an optional embodiment of the present invention, when the target object is loaded on the front-end page, a script is embedded in the H5 page (equivalent to the front-end page of the aforementioned embodiment) through the event collector to capture and record the target object's basic information, such as name, age, contact information, home address, health status, and relevant information about page loading, such as the URL and page title of the page where the target object is operating. This information is stored in the event collector as public information so that it does not need to be obtained twice in subsequent event processing.

[0058] According to the loading operation of the target object on the front-end page, the event collector will receive events that need to be processed. At this time, the events are classified according to the number of events to be processed. When the number of events is one, it can be determined that the event type of the event to be processed is a single event. This means that the event collector only receives one event, and the event processor can directly process the event without considering the impact of other events. When the number of events is at least two, it is necessary to determine whether there is a dependency between these events. If there is a dependency, these events can be combined into a combined event for processing.

[0059] When it is determined that the event type of the event to be processed is a single event, the event processor obtains public information from the event collector and determines the event data required for the event to be processed in combination with the difference data obtained from the data layer. The event to be processed is executed according to the event data of the event to be processed to obtain the execution result of the event to be processed; the execution result is added to the event sequence so that it can be directly called from the event processor when the execution result of the event is needed again.

[0060] In the case where it is determined that the event type of the event to be processed is a combined event, the event data of the combined event includes the common information of the combined event stored in the event collector, the difference data of the combined event obtained from the data layer, and the execution result of the first event pre-stored in the event sequence. In this embodiment, the combined event includes the first event and the second event, and the execution of the second event depends on the execution result of the first event. The second event is executed according to the common information and difference data of the combined event and the execution result of the first event.

[0061] After the pending event is completed, the event status is updated to "end", and the updated event status is passed to the execution layer of the front-end page through the external communicator (equivalent to Figure 3 Component business layer).

[0062] The following is a detailed description using examples of single events and combined events.

[0063] When the event received by the event collector is a single event, assuming that the target object clicks the "Turn on the air conditioner" button on the smart home control platform page, the event collector receives the event to be processed, and the event processor determines the air-conditioning device based on the device type in the public information and executes the operation of turning on the air conditioner. When it is detected that the air conditioner is turned on, the event status is modified to "end" and passed to the execution layer through the external communicator so that the execution layer can perform subsequent operations.

[0064] In the case where the event received by the event collector is a combined event, assuming that the target object clicks the "Buy Now" button on the shopping platform, the event collector receives the pending event, and the event processor queries whether the product inventory is sufficient. If the execution result is "sufficient", the purchase operation is performed based on the target object name, contact number, home address in the public information, and the product name, product specifications, payment amount and payment method in the data layer. If the payment is successful, the event status is modified to "end" and the status is passed to the execution layer through the external communicator so that the execution layer can perform subsequent order processing operations.

[0065] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, a computer, an operating terminal, or a network device, etc.) to execute the methods of each embodiment of the present application.

[0066] Figure 5 is a structural block diagram of a device for determining event data according to an embodiment of the present application; Figure 5 As shown, including:

[0067] The receiving module 50 is used to receive the pending event corresponding to the front-end page when the front-end page receives the loading operation of the target object, collect the public information of the pending event, and save the collected public information in the event collector;

[0068] The determination module 52 is used to determine that the event type of the event to be processed is a single event, obtain the public information from the event collector, and determine the event data required to execute the event to be processed according to the public information.

[0069] In an embodiment of the present application, when the front-end page receives a load operation of a target object, the to-be-processed event corresponding to the front-end page is received, the public information of the to-be-processed event is collected, and the collected public information is saved in an event collector; the event type of the to-be-processed event is determined to be a single event, the public information is obtained from the event collector, and the event data required to execute the to-be-processed event is determined based on the public information. The above technical solution solves the problem in the related art that event processing efficiency is low due to the need to repeatedly obtain public information. There is no need to repeatedly obtain public information, thereby improving event processing efficiency.

[0070] In an optional embodiment, the determination module 52 is further used to obtain difference data corresponding to the event to be processed when the public information is the same content included in different events to be processed; and determine the event data required to execute the event to be processed based on the public information and the difference data.

[0071] In an optional embodiment, the determination module 52 is also used to execute the event to be processed according to the event data to obtain the execution result of the event to be processed; and add the execution result to the event sequence set for the event processor so that when the execution result is needed again, the execution result can be called from the event processor.

[0072] In an optional embodiment, the determination module 52 is also used to obtain the common information of the combined event and the difference data of the combined event from the event collector through the event processor when it is determined that the event type of the event to be processed is a combined event and the common information is the same content included in different events to be processed, and to obtain the execution result of the first event pre-saved in the event sequence set for the event processor, wherein the combined event includes a first event and a second event, and the execution of the second event depends on the execution result of the first event; and execute the second event according to the common information of the combined event, the difference data of the combined event and the execution result of the first event.

[0073] In an optional embodiment, the determination module 52 is also used to obtain the event number of the events to be processed; when the event number is one, determine that the event type of the event to be processed is a single event; when the event number is at least two, determine whether there is a dependency relationship between the at least two events to be processed, and if there is a dependency relationship, determine that the at least two events to be processed are combined events.

[0074] In an optional embodiment, the determination module 52 is also used to detect the current state of the pending event; when it is detected that the pending event has been completed, the state of the pending event is determined as the end state; and the state of the pending event is passed to the execution layer through an external communicator.

[0075] In an optional embodiment, the determination module 52 is further used to determine the content included in the public information of the event to be processed and the collection method for the public information; collect the content according to the collection method to obtain the public information of the event to be processed.

[0076] An embodiment of the present application further provides a storage medium, which includes a stored program, wherein the program executes any of the above methods when it is run.

[0077] Optionally, in this embodiment, the storage medium may be configured to store program codes for executing the following steps:

[0078] S1, when a front-end page receives a load operation of a target object, receiving a to-be-processed event corresponding to the front-end page, collecting public information of the to-be-processed event, and saving the collected public information in an event collector;

[0079] S2, determining that the event type of the event to be processed is a single event, obtaining the public information from the event collector, and determining event data required to execute the event to be processed according to the public information.

[0080] An embodiment of the present application further provides an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0081] Optionally, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0082] Optionally, in this embodiment, the processor may be configured to perform the following steps through a computer program:

[0083] S1, when a front-end page receives a load operation of a target object, receiving a to-be-processed event corresponding to the front-end page, collecting public information of the to-be-processed event, and saving the collected public information in an event collector;

[0084] S2, determining that the event type of the event to be processed is a single event, obtaining the public information from the event collector, and determining event data required to execute the event to be processed according to the public information.

[0085] Optionally, in this embodiment, the above-mentioned storage medium may include but is not limited to: a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and other media that can store program codes.

[0086] An embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the steps in any one of the above method embodiments are implemented.

[0087] An embodiment of the present application further provides another computer program product, including a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in any of the above method embodiments are implemented.

[0088] The embodiments of the present application also provide a computer program, which includes computer instructions, which are stored in a computer-readable storage medium; a processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs the steps in any one of the above method embodiments.

[0089] Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation modes, and this embodiment will not be described in detail here.

[0090] Obviously, those skilled in the art should understand that the above modules or steps of the present application can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, and optionally, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order from that herein, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present application is not limited to any specific combination of hardware and software.

[0091] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for determining event data, characterized in that: include: When the front-end page receives a load operation of the target object, receiving a pending event corresponding to the front-end page, collecting public information of the pending event, and storing the collected public information in an event collector; Determine that the event type of the event to be processed is a single event, obtain the public information from the event collector, and determine event data required to execute the event to be processed according to the public information.

2. The method for determining event data according to claim 1, characterized in that: Determining event data required for executing the event to be processed according to the public information includes: In the case where the public information is the same content included in different events to be processed, obtaining difference data corresponding to the events to be processed; The event data required to execute the event to be processed is determined according to the common information and the difference data.

3. The method for determining event data according to claim 2, characterized in that: After determining the event data required to execute the event to be processed according to the public information and the difference data, the method further includes: Execute the event to be processed according to the event data to obtain the execution result of the event to be processed; add the execution result to the event sequence set for the event processor, so that when the execution result is needed again, the execution result can be called from the event processor.

4. The method for determining event data according to claim 1, characterized in that: After receiving the to-be-processed event corresponding to the front-end page, the method further includes: When it is determined that the event type of the event to be processed is a combined event, and the common information is the same content included in different events to be processed, the event processor obtains the common information of the combined event and the difference data of the combined event from the event collector, and obtains the execution result of the first event pre-stored in the event sequence set for the event processor, wherein the combined event includes the first event and the second event, and the execution of the second event depends on the execution result of the first event; The second event is executed according to the common information of the combined event, the difference data of the combined event, and the execution result of the first event.

5. The method for determining event data according to claim 1, characterized in that: After receiving the to-be-processed event corresponding to the front-end page, the method further includes: Obtain the number of events to be processed; When the number of events is one, determining that the event type of the event to be processed is a single event; When the number of events is at least two, it is determined whether there is a dependency relationship between the at least two events to be processed. If there is a dependency relationship, it is determined that the at least two events to be processed are combined events.

6. The method for determining event data according to claim 1, characterized in that: After determining the event data required to execute the event to be processed according to the public information, the method further includes: Detecting the current state of the pending event; When it is detected that the pending event has been completed, determining the state of the pending event as an end state; The status of the event to be processed is passed to the execution layer through the external communicator.

7. The method for determining event data according to claim 1, characterized in that: Collect public information of the event to be processed, including: Determine the content of the public information of the event to be processed and the method for collecting the public information; The content is collected according to the collection method to obtain the public information of the event to be processed.

8. A device for determining event data, characterized in that: include: A receiving module, used for receiving a pending event corresponding to the front-end page when the front-end page receives a loading operation of the target object, collecting public information of the pending event, and storing the collected public information in an event collector; The determination module is used to determine that the event type of the event to be processed is a single event, obtain the public information from the event collector, and determine the event data required to execute the event to be processed according to the public information.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein the program executes the method described in any one of claims 1 to 7 when executed.

10. An electronic device comprising a memory and a processor, characterized in that: A computer program is stored in the memory, and the processor is configured to execute the method according to any one of claims 1 to 7 through the computer program.