Method and device for reporting buried point logs and method and device for monitoring buried point quality

Abstract

The present application relates to a method and device for reporting a buried point log and a method and device for monitoring buried point quality. The buried point log reporting method includes: in response to session generation, configuring a corresponding global counter for the session, the global counter is used to count the number of buried point events generated in the session; assigning corresponding event numbers to the generated buried point events according to the order in which the buried point events are generated in the session; controlling the event number of the current buried point event to be consistent with the current count value of the global counter; in response to a trigger reporting instruction, generating a buried point log according to the event number of the buried point event within a specified time period and the current count value, and reporting the buried point log to the server. This method can be used to achieve quality monitoring of buried point data.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a method and device for reporting tracking point logs and a method and device for monitoring tracking point quality. Background Art

[0002] With the development of data processing technology, user behavior data collection technology has emerged. User behavior data can also be called embedded data. By analyzing the collected embedded data, it is possible to analyze user characteristics and behaviors and provide personalized solutions for different users.

[0003] However, the quality of the tracking data will affect the accuracy of user personalized analysis, thus affecting business decisions. In traditional technologies, there is no solution to monitor the quality of tracking data. If the tracking data is not reported to the server in time, or the tracking data of the terminal is abnormal and cannot be reported to the server, it is likely to affect the results of business decisions. For example, in a test of AB plan, the effect of plan A is actually better, but because the tracking data corresponding to plan A is of poor quality and has serious leakage, the effect of plan A is weakened when the actual decision is made, thus affecting the accuracy of the decision. Summary of the invention

[0004] Based on this, it is necessary to provide a tracking point log reporting method, device, computer equipment and storage medium that can improve the efficiency of tracking point data quality monitoring in response to the above-mentioned technical problems, and also provide a tracking point quality monitoring method, device, computer equipment and storage medium that can improve the accuracy of user behavior analysis and business decision-making.

[0005] A method for reporting a tracking log, the method comprising:

[0006] In response to session generation, a corresponding global counter is configured for the session, and the global counter is used to count the number of tracking events generated in the session;

[0007] According to the order in which the tracking events are generated in the session, corresponding event numbers are assigned to the generated tracking events;

[0008] The event sequence number of the current tracking event is controlled to be consistent with the current count value of the global counter;

[0009] In response to the trigger reporting instruction, a tracking log is generated according to the event sequence number of the tracking event within the specified time period and the current count value, and the tracking log is reported to the server.

[0010] In one of the embodiments, the tracking log also includes at least one of the following information: the tracking event source, the session identifier, the terminal reporting time, and the tracking event generation time.

[0011] In one of the embodiments, the method further includes: in response to successful reporting to the server, deleting the data of the reported burying event cached by the terminal.

[0012] In one of the embodiments, the method further includes: in response to a failure in reporting to the server, re-reporting according to a preset retry rule.

[0013] A method for monitoring the quality of buried points, the method comprising:

[0014] Receive the tracking log reported by the terminal. The tracking log is generated according to the event sequence number of the tracking event within the specified time period and the current count value of the global counter. The global counter is assigned to the session when the session is generated. The global counter is used to count the number of tracking events generated in the session. The event sequence number of the tracking event is assigned to the generated tracking event according to the order in which the tracking events are generated in the session. The current count value is consistent with the event sequence number of the current tracking event.

[0015] Count the actual number of tracking events reported to the server within a specified time period;

[0016] Calculate the number of tracking events that should be reported to the server within a specified time period based on the current count value and the event sequence number of the tracking event;

[0017] Generate quality monitoring indicators based on the actual reported quantity and the quantity that should be reported, and monitor the data quality of the tracking events within the specified time period based on the quality monitoring indicators.

[0018] In one embodiment, a specified time period includes multiple sessions, and the step of calculating the number of tracking events that should be reported to the server within the specified time period according to the current count value and the event sequence number of the tracking event includes:

[0019] Group the event sequence numbers of tracking events according to the session ID of each session;

[0020] Determine the minimum event sequence number from the event sequence numbers of the tracking events corresponding to each session;

[0021] The number of sessions to be reported for each session is obtained according to the current count value corresponding to each session and the minimum event sequence number corresponding to each session;

[0022] The reportable quantity of each session is summed up to obtain the reportable quantity.

[0023] In one embodiment, the step of generating a quality monitoring indicator according to the actual reported quantity and the quantity to be reported includes:

[0024] The difference between the actual reported quantity and the required reported quantity is used to obtain the leakage quantity of buried point events within the specified time period, and the leakage quantity is used as a quality monitoring indicator.

[0025] In one embodiment, the tracking log also includes the terminal reporting time and the tracking event generation time, and the method further includes:

[0026] The delay time of the corresponding tracking event is calculated according to the terminal reporting time and the time when the tracking event is generated. The delay number of the delayed reporting tracking events within the specified time period is determined according to the delay time, and the delay number is used as a quality monitoring indicator.

[0027] In one embodiment, the method further comprises:

[0028] Visualize and display quality monitoring indicators.

[0029] In one embodiment, the method further comprises:

[0030] In response to the quality monitoring indicator exceeding a preset alarm threshold, an alarm message is generated.

[0031] A device for reporting buried point logs, the device comprising:

[0032] A counter configuration module, configured to configure a corresponding global counter for a session in response to session generation, where the global counter is used to count the number of tracking events generated in the session;

[0033] An event sequence number allocation module is used to allocate unique event sequence numbers to the generated tracking events according to the order in which the tracking events are generated in the session;

[0034] The sequence number and count unification module is used to control the event sequence number of the current tracking event to be consistent with the current count value of the global counter;

[0035] The tracking point log reporting module is used to respond to the trigger reporting instruction, generate the tracking point log according to the event sequence number of the tracking point event within the specified time period and the current count value, and report the tracking point log to the server.

[0036] A buried point quality monitoring device, the device comprising:

[0037] The tracking log receiving module is used to receive the tracking log reported by the terminal. The tracking log is generated according to the event sequence number of the tracking event within the specified time period and the current count value of the global counter. The global counter is assigned to the session when the session is generated. The global counter is used to count the number of tracking events generated in the session. The event sequence number of the tracking event is assigned to the generated tracking event according to the order in which the tracking event is generated in the session. The current count value is consistent with the event sequence number of the current tracking event.

[0038] The actual reporting quantity statistics module is used to count the actual reporting quantity of tracking point events reported to the server within a specified time period;

[0039] The module for calculating the number of events to be reported is used to calculate the number of events to be reported to the server within a specified time period based on the current count value and the event sequence number of the event.

[0040] The tracking point quality monitoring module is used to generate quality monitoring indicators based on the actual reported quantity and the number that should be reported, and monitor the quality of the tracking point event data within a specified time period based on the quality monitoring indicators.

[0041] A computer device comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the steps of the method for reporting a tracking point log described in any one of 1 to 3 or the steps of the method for monitoring the tracking point quality described in any one of 4 to 8 are implemented.

[0042] A computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the steps of the method for reporting a tracking point log described in any one of 1 to 3, or the steps of the method for monitoring the tracking point quality described in any one of 4 to 8 are implemented.

[0043] The above-mentioned method, device, computer equipment and storage medium for reporting the buried point log configure a corresponding global counter for the session, count the number of buried point events generated in the session in real time, and assign event numbers to the buried point events in the session in the order of generation, and generate a buried point log according to the event number and the current count value of the global counter. Even if there are delays, interruptions or omissions in the reporting process, the buried point log containing the event number and the current count value can clearly present the relationship between the number of buried point events generated in the session and the number of reported buried point events. Therefore, the server can further monitor the buried point events and their corresponding data efficiently according to the content in the buried point log. On the other hand, the above-mentioned method, device, computer equipment and storage medium for monitoring the quality of buried point can obtain quality monitoring indicators by calculating the actual reported number and the number to be reported based on the received buried point log, and conduct user behavior analysis and business decision-making based on the quality monitoring indicators, which can improve the reliability and accuracy of the analysis results. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 This is an application environment diagram of a method for reporting point logs in an embodiment;

[0045] Figure 2 A flowchart of a method for reporting a tracking point log in an embodiment;

[0046] Figure 3This is a schematic diagram of the method for reporting point-of-sale events in traditional technologies;

[0047] Figure 4 A schematic diagram of a method for reporting tracking logs in the present application in one embodiment;

[0048] Figure 5 It is a flowchart of a method for monitoring the quality of buried points in one embodiment;

[0049] Figure 6 A schematic diagram of the application environment of a method for monitoring the quality of a buried point in an application example;

[0050] Figure 7 It is a structural block diagram of a device for reporting embedded point logs in an embodiment;

[0051] Figure 8 is a structural block diagram of a buried point quality monitoring device in an embodiment;

[0052] Fig. 9 is an internal structure diagram of a computer device in one embodiment;

[0053] Fig.10 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0054] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0055] The tracking log reporting method and tracking quality monitoring method provided in this application can be applied to Figure 1 In the application environment shown, the terminal 102 communicates with the server 104 through a network. The terminal 102 may be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, and portable wearable devices, and the server 104 may be implemented as an independent server or a server cluster consisting of multiple servers.

[0056] In one of the embodiments, the terminal 102 can configure a corresponding global counter for the session in response to session generation, and the global counter is used to count the number of embedding events generated in the session; assign unique corresponding event numbers to the generated embedding events according to the order in which the embedding events are generated in the session; control the event number of the current embedding event to be consistent with the current count value of the global counter; and generate a embedding log according to the event sequence number of the embedding event within the specified time period and the current count value in response to a trigger reporting instruction, and report the embedding log to the server 104.

[0057] In one of the embodiments, the server 104 receives the tracking log reported by the terminal 102. The tracking log is generated according to the event sequence number of the tracking event within a specified time period and the current count value of the global counter. The global counter is assigned to the session when the session is generated. The global counter is used to count the number of tracking events generated in the session. The event sequence number of the tracking event is assigned to the generated tracking event according to the order in which the tracking events are generated in the session, and the current count value is consistent with the event sequence number of the current tracking event. The server 104 counts the actual reported number of tracking events reported to the server 104 within the specified time period; calculates the number of tracking events that should be reported to the server 104 within the specified time period based on the current count value and the event sequence number of the tracking event; the server 104 generates a quality monitoring indicator based on the actual reported number and the number that should be reported, and monitors the data quality of the tracking events within the specified time period based on the quality monitoring indicator.

[0058] In one embodiment, if Figure 2 As shown, a method for reporting buried point logs is provided, which is applied to Figure 1 The terminal in is used as an example to illustrate, including the following steps:

[0059] Step S202: In response to session generation, a corresponding global counter is configured for the session, and the global counter is used to count the number of embedding events generated in the session.

[0060] Among them, a session is an uninterrupted sequence of requests and responses between a client and a server. A session can be generated each time a client loaded on a terminal is started. Each session uniquely corresponds to a session ID (Identity document). The global counter is configured to uniquely correspond to the generated session and coexist with the session during the life cycle of the session. It is used to count the number of buried events generated during the life cycle of the session. For each buried event generated during the life cycle of the session, the count value of the global counter is increased by one and accumulated in sequence. A buried event is an event generated when a user behavior operation triggers a buried event. The corresponding data obtained when a buried event is generated can be called buried data.

[0061] Specifically, in response to the generation of a session, the terminal configures a unique global counter for the generated session. The global counter coexists with the session during the life cycle of the session and is used to count the number of embedding events generated during the life cycle of the session. The statistics are terminated when the life cycle of the session ends.

[0062] Step S204: assign corresponding event serial numbers to the generated embedding events according to the order in which the embedding events are generated in the session.

[0063] In a session, an event sequence number corresponds to a tracking event one by one. The event sequence number is used to number the tracking events generated in the session in the order in which they were generated.

[0064] Specifically, in response to a buried event generated in the current session, the terminal can assign a corresponding event sequence number to the generated buried event. In response to another buried event generated in the current session, the terminal can assign a corresponding event sequence number to the another buried event. The event sequence number assigned to the later buried event is greater than the event sequence number assigned to the earlier buried event.

[0065] Step S204: Control the event sequence number of the current buried event to be consistent with the current count value of the global counter.

[0066] The current buried event refers to the buried event generated at the current time, that is, the latest buried event. The current count value of the global counter refers to the value accumulated by the global counter at the current time, that is, the total statistical value including the latest buried event.

[0067] Specifically, each time in response to the generation of a buried event within the session, the terminal assigns an event number to the current buried event. At the same time, the terminal controls the count value of the global counter corresponding to the session to increase by one. After the count value is increased by one, the current count value of the global counter remains consistent with the event number assigned to the current buried event.

[0068] Exemplarily, in response to the generation of the current embedding event, the current embedding event is the fifth embedding event generated in the session, and the event sequence number assigned by the terminal to the current embedding event (for example, represented by "eventNo") is 5. At the same time, the count value of the global counter is increased by one, and the current count value (for example, represented by "globalEventNo") is also 5.

[0069] Step S204: In response to the triggering reporting instruction, a tracking log is generated according to the event sequence number of the tracking event within the specified time period and the current count value, and the tracking log is reported to the server.

[0070] Among them, the tracking log refers to the log used to record the tracking events and the data (tracking data) corresponding to the tracking events. The specified time period refers to the time period that is expected to be reported according to the preset reporting rules and the reporting instructions currently triggered. The reporting rules can be customized according to business needs. For example, it can be set to trigger a report every 3 seconds, etc.

[0071] Specifically, when the reporting instruction is triggered, the terminal can obtain the event sequence number of each tracking event in the session within the specified time period, and obtain the current count value of the global counter of the session, and use the event sequence number and current count value of each tracking event as log fields, generate a tracking log, and report the generated tracking log to the server.

[0072] The above-mentioned tracking point log reporting method configures a corresponding global counter for the session, counts the number of tracking point events generated in the session in real time, and assigns event numbers to the tracking point events in the session in the order of generation, and generates a tracking point log based on the event number and the current count value of the global counter. Even if there are delays, interruptions or omissions in the reporting process, the tracking point log containing the event number and the current count value can clearly present the relationship between the number of tracking point events generated in the session and the number of reported tracking point events. Therefore, the server can further efficiently monitor or manage the tracking point events and their corresponding data based on the content in the tracking point log.

[0073] In one of the embodiments, the tracking log also includes at least one of the following information: the tracking event source, the session identifier, the terminal reporting time, and the tracking event generation time.

[0074] Among them, the session identifier refers to the identity identifier of the session, that is, the session ID. Since multiple different sessions may exist simultaneously in a specified time period, multiple sessions can come from the same service of the same terminal, or from different services of the same terminal, or from the same service of different terminals, or from different services of different terminals, etc. The source of the buried event is used to identify the source of each buried event, such as an application, mini-program, or web page. The terminal reporting time refers to the time of the terminal when the reporting instruction is triggered. The buried event generation time refers to the time of the terminal when each buried event is triggered.

[0075] Exemplarily, the tracking log generated by the method of the present application may include the following fields:

[0076] 1. uploadTimestamp (terminal reporting time)

[0077] 2. eventNo (the event number of the buried event)

[0078] 3. globalEventNo (current count value of the global counter)

[0079] 4. correlationId (session ID)

[0080] 5. eventSource (source of buried events)

[0081] In one of the embodiments, the method further includes: in response to a successful report to the server, deleting the data of the reported buried event cached by the terminal; and / or, in response to a failure to report to the server, re-reporting according to a preset retry rule.

[0082] In this embodiment, if the report to the server is successful, the relevant data of the reported tracking event can be deleted from the terminal cache in a timely manner. Since the tracking log already contains relevant data that can reflect the quality of its report, even if it is deleted, it will not affect the subsequent analysis, and the cache can be released in time. If the report to the server fails, it can be re-reported according to the retry rules. For example, the retry rule can be: if it still fails after 3 retries, the report is abandoned.

[0083] Next, the method for reporting tracking logs involved in this application is further described in detail with reference to an application example. Figure 3 and Figure 4 As shown, Figure 3 A schematic diagram showing a method for reporting buried point events in traditional technology is shown. Figure 4 A schematic diagram of a method for reporting tracking logs in the present application in an embodiment is shown.

[0084] like Figure 3 As shown, the user interacts with the terminal 302 and generates user behavior by operating the APP (Application), thereby triggering the tracking point of the terminal 302 and generating a new tracking point event. The newly generated tracking point event is added to the tracking point event queue in the cache of the terminal 302. According to the rules pre-configured for the timer 306, for example, a report is triggered every 3 seconds, the tracking point events in the tracking point event queue are batch packaged to generate a tracking point package, and then the tracking point package is uploaded to the server 304.

[0085] like Figure 4 As shown, the user interacts with the terminal 402. Each time a session is started (not shown in the figure), a global counter 406 is configured for the started session. The user operates the APP (Application) to generate user behavior, triggering the terminal 402's embedding point, generating a new embedding point event, configuring the corresponding event sequence number for the newly generated embedding point event, and controlling the current count value of the global counter 406 to be consistent with the event sequence number corresponding to the newly generated embedding point event according to the event sequence number corresponding to the newly generated embedding point event. Then, the newly generated embedding point event is added to the embedding point event queue in the cache of the terminal 402. According to the rules pre-configured for the timer 408, for example, a report is triggered every 3 seconds, and the embedding point events in the embedding point event queue are batch packaged to generate a embedding point package. When generating the embedding point package, the current count value of the global counter and the event sequence number of the embedding point event to be packaged are obtained to generate a embedding point log, and the embedding point package containing the embedding point log is reported to the server 404.

[0086] In another aspect of the present application, a method for monitoring the quality of a buried point is also provided. Figure 5 As shown, this method is applied to Figure 1 The server in the example is used to illustrate the following steps:

[0087] Step S502: Receive the tracking log reported by the terminal. The tracking log is generated based on the event sequence number of the tracking event within the specified time period and the current count value of the global counter. The global counter is assigned to the session when the session is generated. The global counter is used to count the number of tracking events generated in the session. The event sequence number of the tracking event is assigned to the generated tracking event according to the order in which the tracking events are generated in the session. The current count value is consistent with the event sequence number of the current tracking event.

[0088] Specifically, the server receives the tracking log reported by the terminal, and the tracking log can be generated according to the event sequence number of the tracking event within the specified time period and the current count value of the global counter. Exemplarily, the tracking log generation process may include the following steps: configuring a corresponding global counter for the generated session, and the global counter is used to count the number of tracking events generated in the session; assigning a unique corresponding event sequence number to the generated tracking event according to the order in which the tracking events are generated in the session, controlling the event sequence number of the current tracking event to be consistent with the current count value of the global counter, and generating the tracking log according to the event sequence number of the tracking event within the specified time period and the current count value. More specifically, reference may be made to the description of how to generate the tracking log in the above embodiment, which will not be repeated here.

[0089] Step S504: Count the actual number of reported tracking events reported to the server within a specified time period.

[0090] The actual number of reports refers to the number of tracking events received by the server obtained by counting the tracking events reported to the server within a specified time period.

[0091] Step S506: Calculate the number of buried events that should be reported to the server within a specified time period based on the current count value and the event sequence number of the buried event.

[0092] The number to be reported refers to the number of tracking events that should be reported to the server if there are no delays, omissions, failed uploads, or cleanups.

[0093] Specifically, since the current count value can represent the total number of embedded events that have occurred in the current session,

[0094] Event Source Session ID Event number Current count value app A 2 5 app A 3 5

[0095] The event sequence number can be used to analyze the number of tracking events that have been reported within the specified event segment. Therefore, the number of tracking events that should be reported to the server can be calculated based on the two.

[0096] For example, if there is only one session in a specified time period, the minimum event number can be determined from the event numbers of multiple tracking events corresponding to the session, and then the number to be reported is calculated based on the current count value of the global counter corresponding to the session and the minimum event number. For example, to calculate the data within the statistical window (within the specified time period), you can refer to the following formula:

[0097] Number to be reported = GlobalEventNo-minEventNo+1

[0098] Among them, GlobalEventNo represents the current count value, and minEventNo represents the minimum event number among the event numbers of the embedded events.

[0099] For example, refer to the following flow table information:

[0100] The event numbers of the tracking events uploaded within the specified time period are 2 and 3 respectively, and the current count value of the global counter with session ID A is 5. The minimum event number determined from the event numbers is 2. Therefore, according to the above formula, the number of events to be reported within the specified time period is calculated to be 5-2+1=3. However, only the two tracking events with event numbers 2 and 3 and their corresponding data are actually reported. Therefore, it can be further determined that the number of missed tracking events reported within the specified time period is 1.

[0101] In one of the embodiments, a specified time period includes multiple sessions, and the steps of calculating the number of buried point events to be reported to the server within the specified time period according to the current count value and the event sequence number of the buried point events include: grouping the event sequence numbers of the buried point events according to the session identifier of each session; determining the minimum event sequence number from the event sequence numbers of the buried point events corresponding to each session; obtaining the number of sessions to be reported for each session according to the current count value corresponding to each session and the minimum event sequence number corresponding to each session; and summing the number of sessions to be reported to obtain the number to be reported.

[0102] In this embodiment, multiple terminals may generate multiple sessions within the same time period. Therefore, the buried events of each session can be grouped according to the session identification information (session ID), and the number of events to be reported for each session can be calculated separately, that is, the number of events to be reported for each session. The summation is then performed to obtain the number of events to be reported within the specified time period.

[0103] For example, refer to the following flow table information:

[0104] Event Source Session ID Event number Current count value app A 2 5 app A 3 5 app B 101 102

[0105] In this specified time period, tracking events from two different sessions were uploaded. First, we can group them according to the session ID. We can see that the first two tracking events in the table are from the same session (session with ID A) and are grouped together. The third is also in a group. The calculation is done in sessions:

[0106] The number of events that session A should report = current count value - minimum event sequence number + 1 = 5 - 2 + 1 = 3;

[0107] The number of events that session B should report = current count value - minimum event sequence number + 1 = 102 - 101 + 1 = 2;

[0108] The number of reports to be submitted within the specified time period = the number of reports to be submitted for session A + the number of reports to be submitted for session B = 3 + 2 = 5.

[0109] Step S508: Generate a quality monitoring indicator based on the actual reported quantity and the required reported quantity, and monitor the data quality of the buried event within the specified time period based on the quality monitoring indicator.

[0110] In this step, the server can further calculate the leakage quantity based on the difference between the actual reported quantity and the quantity that should be reported. The leakage quantity refers to the number of missed reports. The server can use the leakage quantity as a quality monitoring indicator, or further calculate the leakage rate based on the leakage quantity, and use the leakage rate as a quality monitoring indicator, etc., or analyze and process the actual reported quantity and the quantity that should be reported to generate other indicators that can characterize the reported leakage situation, and use it as a quality monitoring indicator, etc. The quality monitoring indicator can reflect the leakage of the buried point events reported to the server within a specified time period. Therefore, the quality of the buried point events and their corresponding data (buried point data) can be evaluated according to the quality monitoring indicator. Therefore, when conducting user behavior analysis and business decision-making, while considering the amount of buried point data, quality issues such as leakage are also taken as one of the assessment dimensions. Adding the buried point quality monitoring indicator to the analysis can improve the accuracy and reliability of user behavior analysis and business decision-making, and ensure the fairness and accuracy of the analysis results.

[0111] In one of the embodiments, the step of generating a quality monitoring indicator based on the actual reported quantity and the number to be reported includes: obtaining the leakage number of buried point events within a specified time period based on the difference between the actual reported quantity and the number to be reported, and using the leakage number as the quality monitoring indicator.

[0112] In this embodiment, the number of leakages reported by the buried events within a specified time period can be calculated by the actual number of reports and the number of reports that should be reported, and the number of leakages is used as one of the quality monitoring indicators. The calculation formula for the number of leakages is:

[0113] Leakage quantity = quantity to be reported - actual reported quantity.

[0114] Furthermore, the leakage rate can be calculated based on the actual reported quantity and the quantity that should be reported, and the leakage quantity can also be used as one of the quality monitoring indicators. The calculation formula for the leakage rate is:

[0115] Leakage rate = 1-(actual reported quantity / should be reported quantity)

[0116] By calculating the leakage quantity or leakage rate within a specified time period in real time, the leakage situation of the buried event can be monitored in real time, and then the monitoring and analysis of the buried data can be improved, ensuring the reliability of real-time business decisions.

[0117] In one of the embodiments, the tracking log also includes the terminal reporting time and the tracking event generation time. The method also includes: calculating the delay time of the corresponding tracking event based on the terminal reporting time and the tracking event generation time, determining the delay number of the delayed reporting tracking events within the specified time period based on the delay time, and using the delay number as a quality monitoring indicator.

[0118] In this embodiment, the terminal reporting time and the time when the buried event occurred can be further recorded in the buried event log. The time when the buried event occurred refers to the actual time when the buried event occurred, that is, the time of the terminal when the buried event occurred. The terminal reporting time refers to the time of the terminal when the buried event was reported. The delay time refers to the difference between the actual generation time of the buried event and the actual reporting time reported to the server. This embodiment uses the terminal reporting time as the actual reporting time of the buried event to calculate the delay time. Since the buried event generation time (event Timestamp) comes from the terminal, the terminal reporting time (upload Timestamp) also comes from the terminal. Therefore, using information recorded from the same end to calculate the delay time can improve the accuracy of the calculation.

[0119] Exemplarily, the step of calculating the delayed number of delayed reported buried event events within a specified time period based on the reporting delay time includes: judging in turn whether each reported buried event is a delayed reporting event. The judgment logic may be: if the delay time is greater than a preset threshold, the buried event is judged to be a delayed reporting event; if the delay time is less than the preset threshold, it is judged not to be a delayed reporting event, and the number of delayed reporting events is counted as the delay number.

[0120] Furthermore, the delay rate can be calculated based on the delay quantity and the actual reported quantity, and the delay rate can also be used as one of the quality monitoring indicators. The calculation logic of the delay rate can be: delay quantity / actual reported quantity.

[0121] If the delay time of the tracking event and its related data is too large, the server will not be able to capture the user behavior of the terminal in time, which will affect the decision-making accuracy of real-time business strategies. Therefore, by using the delay number as one of the quality monitoring indicators, the decision-making accuracy of real-time business strategies can be further improved, thereby improving the accuracy of personalized service recommendations.

[0122] In one embodiment, the method further includes: visualizing and displaying the quality monitoring indicators. In this embodiment, the quality monitoring indicators can be further processed, for example, a leakage rate report and / or a delay rate report can be generated, and displayed through a visualization platform, which can more intuitively display the quality of the buried point data and provide visualization support for quality monitoring.

[0123] In one embodiment, the method further includes: generating an alarm message in response to the quality monitoring indicator exceeding a preset alarm threshold. In this embodiment, the alarm threshold can be pre-set on the alarm platform, and when the quality monitoring indicator exceeds the preset alarm threshold, an alarm message can be generated, and the alarm message can be further sent to a configured associated person, thereby improving the monitoring efficiency, increasing the detection rate of abnormal points, and reducing the occurrence of decision-making errors.

[0124] Next, the method for monitoring the quality of the buried points involved in this application is further described in detail with reference to an application example. Figure 6 As shown, Figure 6 A schematic diagram of the application environment of a method for monitoring the quality of buried points in an application example is shown.

[0125] like Figure 6 As shown in the figure, the terminal reports the tracking log to the stats application (status monitoring application), the stats application distributes the tracking log to the tracking log message queue, the server in the Flink computing cluster obtains the tracking log from the tracking log message queue, and performs statistical calculations to obtain the actual reported number, the number to be reported, the number of leakages and the number of delays of the tracking events in each minute time period, and distributes the quality monitoring index results obtained by statistical calculation to the index result message queue, the usertracking application (user tracking application) obtains the index results from the index result message queue, and stores the index result data in DB (Data Base), for example, the business database MySQL, and then, it can be transferred to ADB (Analytical Database) through DTS (Data Transformation Services). After secondary calculation, the data can be visualized on the Guanyuan platform, or sent to the alarm platform for alarm processing, etc.

[0126] It should be understood that although Figure 2 and Figure 5 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 2 and Figure 5 At least part of the steps may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least part of the sub-steps or stages of other steps.

[0127] In one embodiment, if Figure 7 As shown, a device for reporting a buried point log is provided, including: a counter configuration module 702, an event sequence number allocation module 704, a sequence number and count unification module 706 and a buried point log reporting module 708, wherein:

[0128] A counter configuration module 702 is used to configure a corresponding global counter for a session in response to the generation of the session, and the global counter is used to count the number of embedding events generated in the session;

[0129] The event sequence number allocation module 704 is used to allocate a unique corresponding event sequence number to the generated embedding event according to the order in which the embedding events are generated in the session;

[0130] The sequence number and count unification module 706 is used to control the event sequence number of the current tracking event to be consistent with the current count value of the global counter;

[0131] The tracking point log reporting module 708 is used to respond to the trigger reporting instruction, generate the tracking point log according to the event sequence number of the tracking point event within the specified time period and the current count value, and report the tracking point log to the server.

[0132] In one of the embodiments, the tracking point log reporting module 708 is further used to delete the data of the reported tracking point events cached by the terminal in response to a successful report to the server.

[0133] In one of the embodiments, the tracking point log reporting module 708 is also used to respond to a failure in reporting to the server and re-report according to a preset retry rule.

[0134] In one embodiment, if Figure 8As shown, a tracking point quality monitoring device is provided, including: a tracking point log receiving module 802, an actual reported quantity counting module 804, a to-be-reported quantity calculating module 806 and a tracking point quality monitoring module 808, wherein:

[0135] The embedding log receiving module 802 is used to receive the embedding log reported by the terminal. The embedding log is generated according to the event sequence number of the embedding event within the specified time period and the current count value of the global counter. The global counter is assigned to the session when the session is generated. The global counter is used to count the number of embedding events generated in the session. The event sequence number of the embedding event is assigned to the generated embedding event according to the order in which the embedding event is generated in the session. The current count value is consistent with the event sequence number of the current embedding event.

[0136] The actual reporting quantity statistics module 804 is used to count the actual reporting quantity of the tracking point events reported to the server within a specified time period;

[0137] The module 806 for calculating the number of events to be reported is used to calculate the number of events to be reported to the server within a specified time period according to the current count value and the event sequence number of the event;

[0138] The tracking point quality monitoring module 808 is used to generate quality monitoring indicators based on the actual reported quantity and the required reported quantity, and monitor the quality of the tracking point event data within a specified time period based on the quality monitoring indicators.

[0139] In one of the embodiments, the module for calculating the number to be reported 806 groups the event numbers of the buried events according to the session identifiers of the sessions; determines the minimum event number from the event numbers of the buried events corresponding to the sessions; obtains the number of sessions to be reported for each session according to the current count value corresponding to each session and the minimum event number corresponding to each session; and sums the number of sessions to be reported to obtain the number to be reported.

[0140] In one of the embodiments, the tracking point quality monitoring module 808 obtains the leakage number of tracking point events within a specified time period based on the difference between the actual reported number and the number that should be reported, and uses the leakage number as a quality monitoring indicator.

[0141] In one of the embodiments, the tracking point quality monitoring module 808 calculates the delay time of the corresponding tracking point event based on the terminal reporting time and the tracking point event generation time, determines the delay number of the delayed reporting tracking point events within the specified time period based on the delay time, and uses the delay number as a quality monitoring indicator.

[0142] In one of the embodiments, the tracking point quality monitoring module 808 is also used to visualize and display the quality monitoring indicators.

[0143] In one of the embodiments, the tracking point quality monitoring module 808 is also used to generate an alarm message in response to the quality monitoring indicator exceeding a preset alarm threshold.

[0144] For the specific limitations on the buried point log reporting device and the buried point quality monitoring device, please refer to the limitations on the buried point log reporting method and the buried point quality monitoring method in the above text, which will not be repeated here. Each module in the above-mentioned buried point log reporting device and buried point quality monitoring device can be implemented in whole or in part through software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0145] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Fig. 9 As shown. The computer device includes a processor, a memory, and a network interface connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a method for monitoring the quality of a buried point is implemented.

[0146] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Fig.10 As shown. The computer device includes a processor, a memory, a network interface, a display screen and an input device connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a method for reporting a buried point log is implemented. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device housing, or an external keyboard, touchpad or mouse, etc.

[0147] Those skilled in the art will understand that Fig. 9 , 10The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0148] In one of the embodiments, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the following steps when executing the computer program: in response to session generation, configuring a corresponding global counter for the session, the global counter being used to count the number of buried point events generated in the session; assigning corresponding event numbers to the generated buried point events according to the order in which the buried point events are generated in the session; controlling the event number of the current buried point event to be consistent with the current count value of the global counter; in response to a trigger reporting instruction, generating a buried point log according to the event sequence number of the buried point event within a specified time period and the current count value, and reporting the buried point log to a server.

[0149] In one of the embodiments, when the processor executes the computer program, the following steps are also implemented: in response to a successful report to the server, the data of the reported burying event cached by the terminal is deleted.

[0150] In one of the embodiments, when the processor executes the computer program, the following steps are further implemented: in response to a failure in reporting to the server, re-reporting according to a preset retry rule.

[0151] In one of the embodiments, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the following steps when executing the computer program: receiving a tracking log reported by a terminal, the tracking log being generated according to an event sequence number of a tracking event within a specified time period and a current count value of a global counter, the global counter being assigned to a session when the session is generated, the global counter being used to count the number of tracking events generated within the session, the event sequence numbers of the tracking events being assigned to the generated tracking events according to the order in which the tracking events are generated within the session, and the current count value being consistent with the event sequence number of the current tracking event; counting the actual number of tracking events reported to a server within a specified time period; calculating the number of tracking events that should be reported to the server within a specified time period according to the current count value and the event sequence number of the tracking events; generating a quality monitoring indicator according to the actual number of reports and the number that should be reported, and monitoring the data quality of the tracking events within the specified time period according to the quality monitoring indicator.

[0152] In one of the embodiments, when the processor executes a computer program to calculate the number of buried point events to be reported to the server within a specified time period based on the current count value and the event sequence number of the buried point events, the following steps are specifically implemented: grouping the event sequence numbers of the buried point events according to the session identifier of each session; determining the minimum event sequence number from the event sequence numbers of the buried point events corresponding to each session; obtaining the number of sessions to be reported for each session based on the current count value corresponding to each session and the minimum event sequence number corresponding to each session; and summing the number of sessions to be reported to obtain the number to be reported.

[0153] In one of the embodiments, when the processor executes a computer program to generate a quality monitoring indicator based on the actual reported quantity and the number to be reported, the following steps are specifically implemented: the leakage number of buried point events within a specified time period is obtained based on the difference between the actual reported quantity and the number to be reported, and the leakage number is used as the quality monitoring indicator.

[0154] In one of the embodiments, when the processor executes the computer program, it also implements the following steps: calculating the delay time of the corresponding buried event based on the terminal reporting time and the buried event generation time, determining the delay number of the buried event reported late within the specified time period based on the delay time, and using the delay number as a quality monitoring indicator.

[0155] In one of the embodiments, when the processor executes the computer program, it also implements the following steps: visualizing and displaying the quality monitoring indicators.

[0156] In one of the embodiments, when the processor executes the computer program, the processor further implements the following steps: in response to the quality monitoring indicator exceeding a preset alarm threshold, generating an alarm message.

[0157] In one of the embodiments, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented: in response to session generation, a corresponding global counter is configured for the session, and the global counter is used to count the number of buried point events generated in the session; according to the order in which the buried point events are generated in the session, corresponding event serial numbers are assigned to the generated buried point events; the event serial number of the current buried point event is controlled to be consistent with the current count value of the global counter; in response to a trigger reporting instruction, a buried point log is generated according to the event serial number of the buried point event within a specified time period and the current count value, and the buried point log is reported to the server.

[0158] In one of the embodiments, when the computer program is executed by the processor, the following steps are also implemented: in response to a successful report to the server, the data of the reported burying event cached by the terminal is deleted.

[0159] In one of the embodiments, when the computer program is executed by the processor, the following steps are further implemented: in response to a failure in reporting to the server, re-reporting according to a preset retry rule.

[0160] In one of the embodiments, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented: receiving a tracking log reported by a terminal, the tracking log is generated according to an event sequence number of a tracking event within a specified time period and a current count value of a global counter, the global counter is assigned to a session when the session is generated, the global counter is used to count the number of tracking events generated in the session, the event sequence numbers of the tracking events are assigned to the generated tracking events according to the order in which the tracking events are generated in the session, and the current count value is consistent with the event sequence number of the current tracking event; counting the actual number of tracking events reported to a server within a specified time period; calculating the number of tracking events that should be reported to the server within a specified time period according to the current count value and the event sequence number of the tracking event; generating a quality monitoring indicator according to the actual number of reports and the number that should be reported, and monitoring the data quality of the tracking events within the specified time period according to the quality monitoring indicator.

[0161] In one of the embodiments, when a computer program is executed by a processor to calculate the number of buried events to be reported to a server within a specified time period based on a current count value and an event sequence number of the buried events, the following steps are specifically implemented: grouping the event sequence numbers of the buried events according to the session identifier of each session; determining the minimum event sequence number from the event sequence numbers of the buried events corresponding to each session; obtaining the number of sessions to be reported for each session based on the current count value corresponding to each session and the minimum event sequence number corresponding to each session; and summing the number of sessions to be reported to obtain the number to be reported.

[0162] In one of the embodiments, when a computer program is executed by a processor to generate a quality monitoring indicator based on the actual reported quantity and the number to be reported, the following steps are specifically implemented: the leakage number of buried point events within a specified time period is obtained based on the difference between the actual reported quantity and the number to be reported, and the leakage number is used as a quality monitoring indicator.

[0163] In one of the embodiments, when the computer program is executed by the processor, the following steps are also implemented: calculating the delay time of the corresponding buried event based on the terminal reporting time and the buried event generation time, determining the delay number of the buried event reported late within the specified time period based on the delay time, and using the delay number as a quality monitoring indicator.

[0164] In one of the embodiments, when the computer program is executed by a processor, the following steps are also implemented: visualizing and displaying the quality monitoring indicators.

[0165] In one of the embodiments, when the computer program is executed by the processor, the following steps are also implemented: in response to the quality monitoring indicator exceeding a preset alarm threshold, an alarm message is generated.

[0166] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0167] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0168] In addition, the term "and / or" in this article is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the characters in this article generally indicate that the associated objects before and after are in an "or" relationship.

[0169] The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

Claims

1. A method for reporting a tracking log, the method comprising: In response to session generation, a corresponding global counter is configured for the session, and the global counter is used to count the number of tracking events generated in the session; wherein the global counter is configured to uniquely correspond to the generated session and coexist with the session during the life cycle of the session, and the count value of the global counter is increased by one for each tracking event generated during the life cycle of the session; According to the order in which the tracking events are generated in the session, corresponding event numbers are assigned to the generated tracking events; The event sequence number of the current tracking event is controlled to be consistent with the current count value of the global counter; In response to a triggering reporting instruction, a tracking log is generated according to the event sequence number of the tracking event within a specified time period and the current count value, and the tracking log is reported to the server, so that the server calculates the number of tracking events that should be reported to the server within the specified time period according to the current count value and the minimum event sequence number among the event sequence numbers corresponding to the tracking events, counts the actual reported number of tracking events reported to the server within the specified time period, generates a quality monitoring indicator according to the actual reported number and the number that should be reported, and monitors the data quality of the tracking events within the specified time period according to the quality monitoring indicator.

2. The method according to claim 1, characterized in that The tracking point log also includes at least one of the following information: tracking point event source, session identifier, terminal reporting time, and tracking point event generation time.

3. The method according to claim 1, characterized in that The method further comprises: In response to a successful report to the server, deleting the data of the reported tracking event cached by the terminal; In response to a failure in reporting to the server, re-report according to a preset retry rule.

4. A method for monitoring the quality of buried points, the method comprising: A tracking log reported by a receiving terminal, wherein the tracking log is generated according to the event sequence number of the tracking event within a specified time period and the current count value of a global counter, wherein the global counter is assigned to the session when the session is generated, and the global counter is used to count the number of tracking events generated in the session, and the event sequence number of the tracking event is assigned to the generated tracking event according to the order in which the tracking event is generated in the session, and the current count value is consistent with the event sequence number of the current tracking event; wherein the global counter is configured to uniquely correspond to the generated session, and coexist with the session during the life cycle of the session, and the count value of the global counter is increased by one for each tracking event generated during the life cycle of the session; Count the actual number of reported tracking events reported to the server within the specified time period; Calculate the number of tracking events that should be reported to the server within the specified time period according to the current count value and the minimum event sequence number among the event sequence numbers corresponding to the tracking events; A quality monitoring indicator is generated according to the actual reported quantity and the quantity that should be reported, and the data quality of the buried event in the specified time period is monitored according to the quality monitoring indicator.

5. The method according to claim 4, characterized in that The specified time period includes multiple sessions, and the calculation of the number of buried events to be reported to the server within the specified time period according to the current count value and the minimum event sequence number of the event sequence numbers corresponding to the buried events includes: Grouping the event sequence numbers of the tracking events according to the session identifiers of the sessions; Determine the minimum event sequence number from the event sequence numbers of the embedding events corresponding to each of the sessions; Obtain the number of sessions to be reported for each session according to the current count value corresponding to each session and the minimum event sequence number corresponding to each session; The number of reports to be submitted for each session is summed to obtain the number of reports to be submitted.

6. The method according to claim 4, characterized in that The step of generating a quality monitoring indicator according to the actually reported quantity and the quantity to be reported includes: The leakage quantity of the buried event in the specified time period is obtained according to the difference between the actually reported quantity and the required reported quantity, and the leakage quantity is used as the quality monitoring indicator.

7. The method according to claim 4, characterized in that The tracking log also includes the terminal reporting time and the tracking event generation time, and the method also includes: The delay time of the corresponding buried event is calculated according to the terminal reporting time and the generation time of the buried event, and the delay number of the delayed reported buried event within the specified time period is determined according to the delay time, and the delay number is used as the quality monitoring indicator.

8. The method according to claim 4, characterized in that The method further comprises: Visualizing and displaying the quality monitoring indicators; and / or In response to the quality monitoring indicator exceeding a preset alarm threshold, an alarm message is generated.

9. A device for reporting buried point logs, characterized in that: The device comprises: A counter configuration module, configured to configure a corresponding global counter for the session in response to session generation, the global counter being used to count the number of tracking events generated in the session; wherein the global counter is configured to uniquely correspond to the generated session and coexist with the session during the life cycle of the session, and the count value of the global counter is increased by one for each tracking event generated during the life cycle of the session; An event sequence number allocation module is used to allocate a unique corresponding event sequence number to the generated embedding event according to the order in which the embedding events are generated in the session; A sequence number and count unification module, used to control the event sequence number of the current buried event to be consistent with the current count value of the global counter; A tracking point log reporting module is used to respond to a trigger reporting instruction, generate a tracking point log according to the event sequence number of the tracking point event within a specified time period and the current count value, and report the tracking point log to the server, so that the server calculates the number of tracking point events that should be reported to the server within the specified time period according to the current count value and the minimum event sequence number of the event corresponding to the tracking point event, counts the actual reported number of tracking point events reported to the server within the specified time period, generates a quality monitoring indicator according to the actual reported number and the number to be reported, and monitors the data quality of the tracking point events within the specified time period according to the quality monitoring indicator.

10. A buried point quality monitoring device, characterized in that: The device comprises: A tracking log receiving module is used to receive tracking logs reported by terminals, wherein the tracking logs are generated according to the event sequence numbers of tracking events within a specified time period and the current count value of a global counter, wherein the global counter is assigned to the session when the session is generated, and the global counter is used to count the number of tracking events generated in the session, wherein the event sequence numbers of tracking events are assigned to the generated tracking events according to the order in which the tracking events are generated in the session, and the current count value is consistent with the event sequence number of the current tracking event; wherein the global counter is configured to uniquely correspond to the generated session, and coexist with the session during the life cycle of the session, and the count value of the global counter is increased by one for each tracking event generated during the life cycle of the session; The actual reporting quantity statistics module is used to count the actual reporting quantity of the tracking point events reported to the server within the specified time period; A module for calculating the number of events to be reported, used to calculate the number of events to be reported to the server within the specified time period according to the current count value and the minimum event sequence number among the event sequence numbers corresponding to the event. The tracking point quality monitoring module is used to generate a quality monitoring indicator based on the actual reported quantity and the number to be reported, and monitor the quality of the tracking point event data within the specified time period based on the quality monitoring indicator.

11. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 3 or 4 to 8 are implemented.

12. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 3 or 4 to 8 are implemented.

Images