WO2023169251A1 - 一种指标确定方法、装置、服务器和介质 - Google Patents

一种指标确定方法、装置、服务器和介质 Download PDF

Info

Publication number
WO2023169251A1
WO2023169251A1 PCT/CN2023/078651 CN2023078651W WO2023169251A1 WO 2023169251 A1 WO2023169251 A1 WO 2023169251A1 CN 2023078651 W CN2023078651 W CN 2023078651W WO 2023169251 A1 WO2023169251 A1 WO 2023169251A1
Authority
WO
WIPO (PCT)
Prior art keywords
event information
indicator
determined
result
information
Prior art date
Application number
PCT/CN2023/078651
Other languages
English (en)
French (fr)
Inventor
王超
杨智超
Original Assignee
北京字节跳动网络技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京字节跳动网络技术有限公司 filed Critical 北京字节跳动网络技术有限公司
Publication of WO2023169251A1 publication Critical patent/WO2023169251A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3452—Performance evaluation by statistical analysis
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3438—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment monitoring of user actions

Definitions

  • Embodiments of the present disclosure relate to computer technology, for example, to an index determination method, device, server, and medium.
  • user behavior information can be collected by burying points, and based on the user behavior information, some indicators used to reflect the running performance of the application during running are determined, such as room entry success rate indicators, etc., and then based on the user behavior information, These metrics allow further optimization of application performance.
  • Embodiments of the present disclosure provide an index determination method, device, server, and medium to improve the accuracy, stability, and reliability of index determination in the presence of log loss or event reporting delays.
  • embodiments of the present disclosure provide an indicator determination method, including:
  • Receive event information reported by the client at a preset hidden location where the preset buried location includes: a start event generation location corresponding to the indicator to be determined, a result event generation location, and a location that matches the indicator to be determined. At least one subsequent event generation location after the target result event generation location;
  • the index result corresponding to the index to be determined is determined.
  • embodiments of the present disclosure also provide an indicator determination device, including:
  • the event information receiving module is configured to receive event information reported by the client at a preset buried point location, where the preset buried point location includes: the start event generation location and the result event corresponding to the indicator to be determined.
  • the file generation location and at least one subsequent event generation location located after the target result event generation location that matches the indicator to be determined;
  • the number determination module is configured to perform deduplication processing on each event information based on the client identification information in each received event information, and determine the number of target result executions and the total number of executions corresponding to the indicator to be determined;
  • the indicator result determination module is configured to determine the indicator result corresponding to the indicator to be determined based on the number of executions of the target result and the total number of executions.
  • embodiments of the present disclosure also provide a server, where the server includes:
  • processors one or more processors
  • memory configured to store one or more programs
  • the one or more processors are caused to implement the indicator determination method provided by any embodiment of the present disclosure.
  • embodiments of the present disclosure also provide a computer-readable storage medium on which a computer program is stored.
  • the program is executed by a processor, the indicator determination method as provided in any embodiment of the present disclosure is implemented.
  • Figure 1 is a flow chart of an index determination method provided by an embodiment of the present disclosure
  • Figure 2 is an example of an event reporting process involved in an embodiment of the present disclosure
  • Figure 3 is a flow chart of an index determination method provided by another embodiment of the present disclosure.
  • Figure 4 is a schematic structural diagram of an index determination device provided by an embodiment of the present disclosure.
  • Figure 5 is a schematic structural diagram of a server provided by an embodiment of the present disclosure.
  • the term “include” and its variations are open-ended, ie, “including but not limited to.”
  • the term “based on” means “based at least in part on.”
  • the term “one embodiment” means “at least one embodiment”; the term “another embodiment” means “at least one additional embodiment”; and the term “some embodiments” means “at least some embodiments”. Relevant definitions of other terms will be given in the description below.
  • Figure 1 is a flow chart of an indicator determination method provided by an embodiment of the present disclosure. This embodiment can be applied to the situation of determining user behavior indicators during the running of an application.
  • the method can be executed by an indicator determination device, which can be implemented in software and/or hardware and integrated in the server. As shown in Figure 1, the method includes the following steps:
  • S110 Receive event information reported by the client at a preset buried point location, where the preset buried point location includes: a start event generation location corresponding to the indicator to be determined, a result event generation location, and a target that matches the indicator to be determined. At least one subsequent event generation location after the resulting event generation location.
  • the indicators to be determined may include: success rate indicators or failure rate indicators corresponding to the preset behavior.
  • the success rate indicator may refer to the probability of successful execution of the preset behavior.
  • the failure rate metric can refer to the probability of failure to execute a preset behavior.
  • a preset behavior can refer to a user behavior that has a process of starting events and result events.
  • the preset behavior may refer to the room entry behavior of the user entering the live broadcast room.
  • the start event corresponding to the room entry behavior may refer to the room entry request event generated based on the user's trigger operation.
  • the result event corresponding to the room entry behavior may be success.
  • the start event generation location may refer to the location of the start event generated when the preset behavior starts.
  • the result event generation location may refer to the location of the result event generated when the preset behavior ends.
  • the result event generation location in the embodiment of the present disclosure may include: a result success event generation location and/or a result failure event generation location. If the indicator to be determined is a success rate indicator, the target result event generation location that matches the indicator to be determined may refer to the result success event generation location. If the indicator to be determined is a failure rate indicator, the target result event generation location that matches the indicator to be determined may refer to the result failure event generation location.
  • the subsequent event generation location may refer to the location of one or more subsequent events generated after the target result event, so that by reporting the subsequent events, it can be indirectly determined whether the execution result of the preset behavior is the target result.
  • embodiments of the present disclosure can be based on a preset burying method, such as a manual burying method or an automatic burying method, and the start event generation position, the result event generation position and the target event corresponding to the indicator to be determined in each client.
  • a preset burying method such as a manual burying method or an automatic burying method
  • At least one subsequent event generation position after the result event generation position is buried, so that each client reports the generated start event information when the preset behavior starts, and reports the generated result event information when the preset behavior ends.
  • each subsequent event information generated when performing subsequent operations after the target result event so that the server can receive Receive multiple event information reported by each client.
  • Figure 2 shows an example of an event reporting process.
  • the indicator to be determined is the success rate indicator corresponding to the preset behavior
  • it can be performed at the starting event generation position corresponding to the preset behavior, the result success event generation position, and at least one subsequent event generation position after success.
  • the buried point allows the client to report the generated start event information A when the preset behavior starts, to report the generated result success event information B1 when the preset behavior is successful, and to report subsequent events when subsequent operations are performed successfully.
  • Information Cn is reported; alternatively, the location of the start event generation, success event generation location, failure event generation location, and at least one subsequent event generation location after success corresponding to the preset behavior can be buried so that the client can Start event information A, result success event information B1, result failure event information B2, and subsequent event information Cn after success are reported.
  • the indicator to be determined is the failure rate indicator corresponding to the preset behavior
  • the starting event generation position corresponding to the preset behavior, the result failure event generation position, and at least one subsequent event generation position after the failure can be buried.
  • the client reports the generated start event information A when the preset behavior starts, reports the generated failure event information B2 when the preset behavior fails, and reports the subsequent event information Dn when performing subsequent operations after the failure. (not shown in Figure 2) to report; or, you can also bury the point at the start event generation location, the success event generation location, the failure event generation location, and at least one subsequent event generation location after the failure corresponding to the preset behavior.
  • the client can report the start event information A, the result success event information B1, the result failure event information B2, and the subsequent event information Dn after the failure.
  • the client identification information can be used to uniquely identify the client that reports each event information, so as to distinguish different clients, that is, distinguish different users. Different event information sent by the same client corresponds to the same client identification information.
  • Client identification information may include but is not limited to: session identification session_id.
  • the session identifier may refer to the identifier corresponding to the session created when the client interacts with the server, so that different event information reported by the same client or the same event information can be determined based on the session identifier in the event information.
  • the number of executions of the target result may refer to the number of times the execution result of the preset behavior is the target result, that is, the number of clients whose execution result of the preset behavior is the target result, such as the number of successful room entries or the number of failed room entries.
  • the total number of executions may refer to the number of executions of the preset behavior, that is, the number of clients that execute the preset behavior, such as the total number of room entries, which is the sum of the number of successful room entries and the number of failed room entries.
  • the server can receive the event information reported by the client at each preset buried location, that is, it can receive the event information reported by the client. Start event information, result event information, and subsequent event information after the target result, and the client may report the same event information multiple times, so it needs to be sent to the same client based on the client identification information in each event information.
  • the same event information or different event information are deduplicated to determine the number of target result execution times and the total number of execution times corresponding to the indicators to be determined. If the client fails to receive the target result event information due to log loss, or the target result event information is delayed, the client can also determine that the execution result is after receiving the subsequent event information after the target result.
  • the target result can be accurately determined during the real-time determination process of the target result, thereby avoiding the situation where the actual result is successful and mistakenly considered as failure, thereby avoiding the situation where the determined number of executions of the target result is too small and reducing the indicator.
  • the range of fluctuations in results can be accurately determined during the real-time determination process of the target result, thereby avoiding the situation where the actual result is successful and mistakenly considered as failure, thereby avoiding the situation where the determined number of executions of the target result is too small and reducing the indicator.
  • the server detects whether there is at least one event information in the target result event information corresponding to the same client identification information and at least one subsequent event information. If there is the same At least one of the target result event information and subsequent event information corresponding to the client identification information indicates that the result of the client executing the preset behavior is the target result. At this time, the number of executions of the target result can be increased by 1, so that The final target result execution times can be determined more timely and accurately.
  • At least one event information in the subsequent event information indicates that the client has executed the preset behavior. At this time, the total number of executions can be added by 1, so that the final total number of executions can be determined more accurately.
  • the ratio of the number of executions of the target result to the total number of executions can be used as the indicator result corresponding to the indicator to be determined, so that accurate, stable, and timely indicators can be determined in the presence of log loss or event reporting delays, improving efficiency. Accuracy, stability and reliability of indicator determination.
  • the technical solution of the embodiment of the present disclosure is to bury points in advance at the start event generation position corresponding to the indicator to be determined, the result event generation location, and at least one subsequent event generation location located after the target result event generation location matching the indicator to be determined. , so that each client can report the event information generated at each preset buried location, that is, the start event information, the result event information, and at least one subsequent event information after the target result event, thereby reporting the subsequent events through the client
  • the event information method can avoid large fluctuations and inaccurate indicator results due to the loss of result events, and also avoid the situation where the actual success is mistaken for failure due to delayed reporting of result events, so that it can be used when there is log loss or In the case of delayed event reporting, accurate, stable, and timely indicators are determined, which improves the accuracy, stability, and reliability of indicator determination.
  • Figure 3 is a flow chart of an index determination method provided by another embodiment of the present disclosure.
  • the process of determining the number of execution times of the target result and the total number of executions is described in detail. The explanations of terms that are the same as or corresponding to the above-mentioned embodiments will not be repeated here.
  • the indicator determination method provided in this embodiment includes the following steps:
  • S310 Receive event information reported by the client at a preset buried point location, where the preset buried point location includes: a start event generation location corresponding to the indicator to be determined, a result event generation location, and a target that matches the indicator to be determined. At least one subsequent event generation location after the resulting event generation location.
  • S320 Based on the client identification information in each received event information, perform deduplication processing on the same event information reported by the same client.
  • the server can deduplicate the same event information reported by the same client based on the client identification information in each event information received, delete the same event information repeatedly reported by the same client, and retain only the same event information reported by the same client. Different event information to ensure the accuracy of subsequent statistics.
  • the target result event information and subsequent event information in the deduplicated event information For example, for each client, it can be detected whether there is at least one of the target result event information and subsequent event information in the deduplicated event information. If it exists, it indicates that the client performs the preset behavior. The result is the target result. At this time, the number of executions of the target result can be added by 1, so that in the process of real-time determination of the indicator, the final number of executions of the target result can be determined promptly and accurately, avoiding the problem of not receiving the target result event information. Or the indicator may fluctuate greatly and be determined inaccurately due to delayed reporting of target result event information.
  • S330 may include: deduplicating the target result event information and subsequent event information corresponding to the same client identification information again, determining the number of event information after deduplication again, and using the number of event information as the indicator to be determined. The number of times the target result is executed.
  • the server receives the target result event information and at least one subsequent event information reported by the same client, it can delete the target result event information or at least one subsequent event information with the same client identification information, and only retain the corresponding client identification information. an event information. If the server only receives one target result event information or one subsequent event information reported by the client, there is no need to deduplicate it again. After deduplicating the target result event information and subsequent event information again, determine the number of event information corresponding to the target result event information and subsequent event information obtained after deduplication again, and use the number of event information as the corresponding indicator to be determined The number of times the target result is executed.
  • the determined number of executions of the target result (ie, the number of successful results) can be expressed as: count(distinct([B1
  • S340 may include: determining the total number of executions corresponding to the indicator to be determined based on the start event information, result event information and subsequent event information corresponding to each client identification information after deduplication.
  • each client it can be detected whether there is at least one event information among start event information, result event information and subsequent event information in the event information after deduplication. If it exists, it indicates that the client executed Preset behavior, at this time, the total number of executions can be added by 1, so that in the process of real-time determination of indicators, the final number of execution results can be more accurately determined, avoiding indicator determination caused by log loss or event reporting delays. Inaccuracies further ensure the accuracy of indicator determination.
  • determining the total number of executions corresponding to the indicator to be determined may include: The start event information, result event information and subsequent event information are deduplicated again, the number of event information after deduplication is determined again, and the number of event information is used to determine the total number of executions corresponding to the indicator to be determined.
  • the start event information, result event information, and subsequent event information corresponding to each deduplicated client identification information may be deduplicated again, and only one event information corresponding to the client identification information may be retained.
  • the number of event information obtained after deduplication is determined again, and the number of event information is used as the total number of executions corresponding to the indicator to be determined.
  • the indicator to be determined is the success rate indicator of a preset behavior
  • the total number of executions determined can be expressed as: count(distinct([A
  • the indicator result can be expressed as: count(distinct([B1
  • the technical solution of this embodiment is to perform deduplication processing on the same event information reported by the same client based on the client identification information in each received event information, and based on the deduplication of each client identification information, the corresponding The target result event information and subsequent event information are used to determine the number of executions of the target result corresponding to the indicator to be determined, and based on the start event information corresponding to each client identification information after deduplication, the total number of executions corresponding to the indicator to be determined can be determined. It avoids large fluctuations and inaccurate indicator results due to the loss of result events, and also avoids the situation where actual success is mistaken for failure due to delay in reporting of result events, so that it can be used in situations where there is log loss or event reporting delays. Under this method, accurate, stable and timely indicators are determined, which improves the accuracy, stability and reliability of indicator determination. Reliability.
  • S330 may include: obtaining the time field information in the target result event information corresponding to each client identification information after deduplication; based on the time field information, filtering out the time-consuming results from the target result event information.
  • the target information whose time is less than or equal to the preset time consumption; based on the amount of target information, determine the number of target result execution times corresponding to the indicators to be determined under the preset time consumption.
  • the target result event information may include a time field information, that is, elapse field information, which is used to represent the elapsed time from the start to the end of the preset behavior.
  • the preset time consumption can be the maximum time consumption specified based on business requirements, so as to determine the indicator results under the specified time consumption, thereby obtaining the N-second success rate indicator or N-second failure rate indicator.
  • the server can obtain the elapsed time when the preset behavior is executed based on the time field information in each target result event information obtained after deduplication, and detect whether the elapsed time is less than or equal to the preset elapsed time. If the elapsed time is less than or equal to the preset elapsed time, the target result event information is used as the target information.
  • the following is an example of an indicator determination device provided by an embodiment of the present disclosure.
  • This device belongs to the same concept as the indicator determination method in the above embodiment.
  • FIG. 4 is a schematic structural diagram of an indicator determination device provided by an embodiment of the present disclosure. This embodiment can be applied to determining user behavior indicators during the running of an application. As shown in Figure 4, the device includes: an event information receiving module 410, a times determining module 420 and an indicator result determining module 430.
  • the event information receiving module 410 is configured to receive event information reported by the client at a preset embedding location, where the preset embedding location includes: the start event generation location corresponding to the indicator to be determined, the result event generation location and the At least one subsequent event generation location after the target result event generation location that matches the indicator to be determined; the number of times determination module 420 is configured to remove each event information based on the client identification information in each event information received. Re-process to determine the number of target result executions and the total number of executions corresponding to the indicator to be determined; the indicator result determination module 430 is configured to determine the indicator result corresponding to the indicator to be determined based on the number of executions of the target result and the total number of executions.
  • the technical solution of the embodiment of the present disclosure is to bury points in advance at the start event generation position corresponding to the indicator to be determined, the result event generation location, and at least one subsequent event generation location located after the target result event generation location matching the indicator to be determined. , so that each client can convert each preset The event information generated at the buried point location, that is, the start event information, the result event information, and at least one subsequent event information after the target result event are reported, so that the client reports the subsequent event information to avoid the loss of result events.
  • Stable and timely indicators improve the accuracy, stability and reliability of indicator determination.
  • the indicators to be determined include: the success rate indicator or the failure rate indicator corresponding to the preset behavior; the client identification information includes: the session identification.
  • the times determination module 420 includes:
  • the deduplication processing unit is configured to deduplicate the same event information reported by the same client based on the client identification information in each received event information;
  • the target result execution times determination unit is configured to determine the target result execution times corresponding to the indicators to be determined based on the target result event information and subsequent event information corresponding to each client identification information after deduplication;
  • the total number of execution times determination unit is configured to determine the total number of execution times corresponding to the indicator to be determined based on the start event information corresponding to each client identification information after deduplication.
  • the target result execution number determination unit is set as:
  • the total number of execution times determination unit is also set to:
  • result event information and subsequent event information corresponding to each client identification information after deduplication determine the total number of executions corresponding to the indicator to be determined.
  • the total number of execution times determination unit is also set to:
  • the target result execution number determination unit is also set to:
  • the index determination device provided by the embodiments of the present disclosure can execute the index determination method provided by any embodiment of the present disclosure, and has corresponding functional modules and beneficial effects for executing the index determination method.
  • the multiple units and modules included are only divided according to functional logic, but are not limited to the above-mentioned divisions, as long as the corresponding functions can be achieved; in addition, the specific names of multiple functional units are only for the convenience of mutual distinction and are not used to limit the protection of the present disclosure. scope.
  • FIG. 5 a schematic structural diagram of a server 900 suitable for implementing embodiments of the present disclosure is shown.
  • the server shown in Figure 5 is only an example and should not bring any limitations to the functions and scope of use of the embodiments of the present disclosure.
  • the server 900 may include a processing device (eg, central processing unit, graphics processor, etc.) 901 that may be loaded into a random access memory according to a program stored in a read-only memory (ROM) 902 or from a storage device 908 (RAM) 903 to perform various appropriate actions and processes.
  • ROM read-only memory
  • RAM storage device 908
  • various programs and data required for the operation of the server 900 are also stored.
  • the processing device 901, ROM 902 and RAM 903 are connected to each other via a bus 904.
  • An input/output (I/O) interface 905 is also connected to bus 904.
  • the following devices may be connected to the I/O interface 905: input devices 906 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; including, for example, a liquid crystal display (LCD), speakers, vibration An output device 907 such as a computer; a storage device 908 including a magnetic tape, a hard disk, etc.; and a communication device 909.
  • the communication device 909 may allow the server 900 to communicate wirelessly or wiredly with other devices to exchange data.
  • FIG. 5 illustrates server 900 with various devices, it should be understood that implementation or availability of all illustrated devices is not required. More or fewer means may alternatively be implemented or provided.
  • embodiments of the present disclosure include a computer program product including a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the method illustrated in the flowchart.
  • the computer program may be downloaded and installed from the network via communication device 909, or from storage device 908, or from ROM 902.
  • the processing device 901 When the computer program is executed by the processing device 901, the above-mentioned functions defined in the method of the embodiment of the present disclosure are performed.
  • the server provided by the embodiment of the present disclosure and the indicator determination method provided by the above embodiment belong to the same concept.
  • Technical details that are not described in detail in the embodiment of the present disclosure can be referred to the above embodiment, and the embodiment of the present disclosure has the same features as the above embodiment. beneficial effects.
  • Embodiments of the present disclosure provide a computer storage medium on which a computer program is stored.
  • the program is executed by a processor, the indicator determination method provided in the above embodiments is implemented.
  • the computer-readable medium mentioned above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the above two.
  • the computer-readable storage medium may be, for example, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or any combination thereof. More specific examples of computer-readable storage media may include Includes, but is not limited to: electrical connections with one or more wires, portable computer disks, hard drives, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), fiber optics , portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above.
  • a computer-readable storage medium may be any tangible medium that contains or stores a program for use by or in connection with an instruction execution system, apparatus, or device.
  • a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code therein. Such propagated data signals may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above.
  • a computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device .
  • Program code embodied on a computer-readable medium may be transmitted using any suitable medium, including but not limited to: wire, optical cable, RF (radio frequency), etc., or any suitable combination of the above.
  • the client and server can communicate using any currently known or future developed network protocol such as HTTP (HyperText Transfer Protocol), and can communicate with digital data in any form or medium.
  • Communications e.g., communications network
  • communications networks include local area networks (“LAN”), wide area networks (“WAN”), the Internet (e.g., the Internet), and end-to-end networks (e.g., ad hoc end-to-end networks), as well as any currently known or developed in the future network of.
  • the above-mentioned computer-readable medium may be included in the above-mentioned server; it may also exist separately without being assembled into the server.
  • the computer-readable medium carries one or more programs.
  • the server receives event information reported by the client at each preset buried point location, wherein the preset The buried point locations include: the start event generation location corresponding to the indicator to be determined, the result event generation location, and at least one subsequent event generation location after the target result event generation location that matches the indicator to be determined; based on each event received Based on the client identification information in the information, each event information is deduplicated to determine the number of executions of the target result and the total number of executions corresponding to the indicator to be determined; based on the number of executions of the target result and the total number of executions, determine the indicator corresponding to the indicator to be determined. result.
  • Computer program code for performing the operations of the present disclosure may be written in one or more programming languages, including but not limited to object-oriented programming languages—such as Java, Smalltalk, C++, and Includes conventional procedural programming languages—such as "C” or similar programming languages.
  • the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
  • remote computing In the case of a computer, the remote computer can be connected to the user's computer through any kind of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (such as through an Internet service provider). .
  • LAN local area network
  • WAN wide area network
  • each block in the flowchart or block diagram may represent a module, segment, or portion of code that contains one or more logic functions that implement the specified executable instructions.
  • the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown one after another may actually execute substantially in parallel, or they may sometimes execute in the reverse order, depending on the functionality involved.
  • each block of the block diagram and/or flowchart illustration, and combinations of blocks in the block diagram and/or flowchart illustration can be implemented by special purpose hardware-based systems that perform the specified functions or operations. , or can be implemented using a combination of specialized hardware and computer instructions.
  • the units involved in the embodiments of the present disclosure can be implemented in software or hardware.
  • the name of a unit does not constitute a limitation on the unit itself under certain circumstances.
  • an editable content display unit may also be described as an "editing unit”.
  • FPGAs Field Programmable Gate Arrays
  • ASICs Application Specific Integrated Circuits
  • ASSPs Application Specific Standard Products
  • SOCs Systems on Chips
  • CPLD Complex Programmable Logical device
  • a machine-readable medium may be a tangible medium that may contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • the machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium.
  • Machine-readable media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or devices, or any suitable combination of the foregoing.
  • machine-readable storage media would include one or more wire-based electrical connections, laptop disks, hard drives, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above.
  • RAM random access memory
  • ROM read only memory
  • EPROM or flash memory erasable programmable read only memory
  • CD-ROM portable compact disk read-only memory
  • magnetic storage device or any suitable combination of the above.
  • Example 1 provides an indicator determination method, including:
  • Receive event information reported by the client at a preset hidden location where the preset buried location includes: a start event generation location corresponding to the indicator to be determined, a result event generation location, and a location that matches the indicator to be determined. at least one subsequent event generation position after the target result event generation position set;
  • the index result corresponding to the index to be determined is determined.
  • Example 2 provides a method for determining indicators, wherein the indicators to be determined include: a success rate indicator or a failure rate indicator corresponding to a preset behavior; the client identifier Information includes: Session ID.
  • Example 3 provides an indicator determination method, wherein each event information is deduplicated based on the client identification information in each event information received. Processing, determining the number of executions of the target result corresponding to the indicator to be determined and the total number of executions, including:
  • the same event information reported by the same client is deduplicated
  • the total number of executions corresponding to the indicator to be determined is determined.
  • Example 4 provides an indicator determination method, wherein the target result event information and subsequent event information corresponding to each client identification information after deduplication are determined.
  • the number of target result execution times corresponding to the indicators to be determined includes:
  • Example 5 provides an indicator determination method, wherein the indicator to be determined is determined based on the start event information corresponding to each client identification information after deduplication.
  • the corresponding total number of executions includes:
  • the total number of executions corresponding to the indicator to be determined is determined.
  • Example 6 provides an indicator determination method, wherein the start event information, result event information and subsequent events corresponding to each client identification information after deduplication are Information to determine the total number of executions corresponding to the indicator to be determined, including:
  • Example 7 provides an indicator determination method, wherein the target result event information and subsequent event information corresponding to each client identification information after deduplication are determined.
  • the number of execution times of the target results corresponding to the indicators to be determined include:
  • the number of execution times of the target result corresponding to the indicator to be determined is determined under the preset time consumption.
  • Example 8 provides an indicator determination device, including:
  • the event information receiving module is configured to receive event information reported by the client at a preset buried point location, where the preset buried point location includes: a start event generation location corresponding to the indicator to be determined, a result event generation location, and a location located between At least one subsequent event generation location after the target result event generation location that the indicator to be determined matches;
  • the number determination module is configured to perform deduplication processing on each event information based on the client identification information in each received event information, and determine the number of target result executions and the total number of executions corresponding to the indicator to be determined;
  • the indicator result determination module is configured to determine the indicator result corresponding to the indicator to be determined based on the number of executions of the target result and the total number of executions.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Bioinformatics & Cheminformatics (AREA)
  • Bioinformatics & Computational Biology (AREA)
  • Evolutionary Biology (AREA)
  • Probability & Statistics with Applications (AREA)
  • Debugging And Monitoring (AREA)

Abstract

本公开实施例公开了一种指标确定方法、装置、服务器和介质。该方法包括：接收客户端在预设埋点位置处上报的事件信息，其中，预设埋点位置包括：待确定指标对应的开始事件生成位置、结果事件生成位置以及位于与待确定指标相匹配的目标结果事件生成位置之后的至少一个后续事件生成位置(S110)；基于接收到的每个事件信息中的客户端标识信息，对每个事件信息进行去重处理，确定待确定指标对应的目标结果执行次数和执行总次数(S120)；根据目标结果执行次数和执行总次数，确定待确定指标对应的指标结果(S130)。

Description

一种指标确定方法、装置、服务器和介质
本申请要求在2022年3月9日提交中国专利局、申请号为202210225178.0的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本公开实施例涉及计算机技术，例如涉及一种指标确定方法、装置、服务器和介质。
背景技术
随着计算机技术的快速发展，可以通过埋点方式收集用户行为信息，并基于用户行为信息确定出应用程序运行过程中的用于反映运行性能的一些指标，比如进房成功率指标等，进而基于这些指标可以对应用程序的性能进行进一步优化。
目前，通常是在指标对应的开始事件和结果事件的生成位置处进行埋点，以便基于客户端上报的开始事件和结果事件确定出指标结果。然而，在客户端存在日志丢失导致结果事件丢失或者结果事件上报延时的情况时，会导致确定出的指标波动较为严重，并且也降低了指标确定的准确性。
发明内容
本公开实施例提供了一种指标确定方法、装置、服务器和介质，以在存在日志丢失或者事件上报延时的情况下，提高指标确定的准确性、稳定性和可靠性。
第一方面，本公开实施例提供了一种指标确定方法，包括：
接收客户端在预设埋点位置处上报的事件信息，其中，所述预设埋点位置包括：待确定指标对应的开始事件生成位置、结果事件生成位置以及位于与所述待确定指标相匹配的目标结果事件生成位置之后的至少一个后续事件生成位置；
基于接收到的每个事件信息中的客户端标识信息，对每个事件信息进行去重处理，确定所述待确定指标对应的目标结果执行次数和执行总次数；
根据所述目标结果执行次数和所述执行总次数，确定所述待确定指标对应的指标结果。
第二方面，本公开实施例还提供了一种指标确定装置，包括：
事件信息接收模块，设置为接收客户端在预设埋点位置处上报的事件信息，其中，所述预设埋点位置包括：待确定指标对应的开始事件生成位置、结果事 件生成位置以及位于与所述待确定指标相匹配的目标结果事件生成位置之后的至少一个后续事件生成位置；
次数确定模块，设置为基于接收到的每个事件信息中的客户端标识信息，对每个事件信息进行去重处理，确定所述待确定指标对应的目标结果执行次数和执行总次数；
指标结果确定模块，设置为根据所述目标结果执行次数和所述执行总次数，确定所述待确定指标对应的指标结果。
第三方面，本公开实施例还提供了一种服务器，所述服务器包括：
一个或多个处理器；
存储器，设置为存储一个或多个程序；
当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如本公开任意实施例提供的指标确定方法。
第四方面，本公开实施例还提供了一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现如本公开任意实施例提供的指标确定方法。
附图说明
贯穿附图中，相同或相似的附图标记表示相同或相似的元素。应当理解附图是示意性的，原件和元素不一定按照比例绘制。
图1是本公开一实施例提供的一种指标确定方法的流程图；
图2是本公开一实施例所涉及的一种事件上报过程的示例；
图3是本公开另一实施例提供的一种指标确定方法的流程图；
图4是本公开一实施例提供的一种指标确定装置的结构示意图；
图5是本公开一实施例提供的一种服务器的结构示意图。
具体实施方式
应当理解，本公开的方法实施方式中记载的多个步骤可以按照不同的顺序执行，和/或并行执行。此外，方法实施方式可以包括附加的步骤和/或省略执行示出的步骤。本公开的范围在此方面不受限制。
本文使用的术语“包括”及其变形是开放性包括，即“包括但不限于”。术语“基于”是“至少部分地基于”。术语“一个实施例”表示“至少一个实施例”；术语“另一实施例”表示“至少一个另外的实施例”；术语“一些实施例”表示“至少一些实施例”。其他术语的相关定义将在下文描述中给出。
需要注意，本公开中提及的“第一”、“第二”等概念仅用于对不同的装置、模块或单元进行区分，并非用于限定这些装置、模块或单元所执行的功能的顺序 或者相互依存关系。
需要注意，本公开中提及的“一个”、“多个”的修饰是示意性而非限制性的，本领域技术人员应当理解，除非在上下文另有明确指出，否则应该理解为“一个或多个”。
本公开实施方式中的多个装置之间所交互的消息或者信息的名称仅用于说明性的目的，而并不是用于对这些消息或信息的范围进行限制。
图1为本公开一实施例提供的一种指标确定方法的流程图，本实施例可适用于对应用程序运行过程中的用户行为指标进行确定的情况。该方法可以由指标确定装置来执行，该装置可以由软件和/或硬件的方式来实现，集成于服务器中。如图1所示，该方法包括以下步骤：
S110、接收客户端在预设埋点位置处上报的事件信息，其中，预设埋点位置包括：待确定指标对应的开始事件生成位置、结果事件生成位置以及位于与待确定指标相匹配的目标结果事件生成位置之后的至少一个后续事件生成位置。
其中，待确定指标可以包括：预设行为对应的成功率指标或者失败率指标。成功率指标可以是指预设行为执行成功的概率。失败率指标可以是指预设行为执行失败的概率。预设行为可以是指具有开始事件和结果事件这一过程的用户行为。例如，预设行为可以是指用户进入直播间的进房行为，该进房行为对应的开始事件可以是指基于用户触发操作生成的进房请求事件，该进房行为对应的结果事件可以是成功进入直播间时生成的结果成功事件，或者未能进入直播间时生成的结果失败事件。
其中，开始事件生成位置可以是指预设行为开始时生成的开始事件的位置。结果事件生成位置可以是指预设行为结束时生成的结果事件的位置。本公开实施例中的结果事件生成位置可以包括：结果成功事件生成位置和/或结果失败事件生成位置。若待确定指标为成功率指标，则与待确定指标相匹配的目标结果事件生成位置可以是指结果成功事件生成位置。若待确定指标为失败率指标，则与待确定指标相匹配的目标结果事件生成位置可以是指结果失败事件生成位置。后续事件生成位置可以是指在目标结果事件之后所生成的一个或多个后续事件的位置，以便通过上报后续事件可以间接确定出预设行为的执行结果是否为目标结果。
例如，本公开实施例可以预先基于预设埋点方式，比如手动埋点方式或者自动埋点方式，在每个客户端中的待确定指标对应的开始事件生成位置、结果事件生成位置以及位于目标结果事件生成位置之后的至少一个后续事件生成位置进行埋点，使得每个客户端在预设行为开始时将生成的开始事件信息进行上报，在预设行为结束时将生成的结果事件信息进行上报、以及在目标结果事件之后执行后续操作时将生成的每个后续事件信息进行上报，从而服务器可以接 收到每个客户端上报的多个事件信息。
需要说明的是，本实施例可以基于业务需求、待确定指标以及指标的具体确定方式确定出多个具体的埋点位置。例如，图2给出了一种事件上报过程的示例。如图2所示，在待确定指标为预设行为对应的成功率指标时，可以在该预设行为对应的开始事件生成位置、结果成功事件生成位置以及成功之后的至少一个后续事件生成位置进行埋点，使得客户端在预设行为开始时将生成的开始事件信息A进行上报、在预设行为成功时将生成的结果成功事件信息B1进行上报、以及在成功之后执行后续操作时将后续事件信息Cn进行上报；或者，也可以在预设行为对应的开始事件生成位置、结果成功事件生成位置、结果失败事件生成位置以及成功之后的至少一个后续事件生成位置进行埋点，使得客户端可以将开始事件信息A、结果成功事件信息B1、结果失败事件信息B2、以及成功之后的后续事件信息Cn进行上报。
又如，在待确定指标为预设行为对应的失败率指标时，可以将在该预设行为对应的开始事件生成位置、结果失败事件生成位置以及失败之后的至少一个后续事件生成位置进行埋点，使得客户端在预设行为开始时将生成的开始事件信息A进行上报、在预设行为失败时将生成的结果失败事件信息B2进行上报、以及在失败之后执行后续操作时将后续事件信息Dn(图2中未示出)进行上报；或者，也可以在预设行为对应的开始事件生成位置、结果成功事件生成位置、结果失败事件生成位置以及失败之后的至少一个后续事件生成位置进行埋点，使得客户端可以将开始事件信息A、结果成功事件信息B1、结果失败事件信息B2、以及失败之后的后续事件信息Dn进行上报。
S120、基于接收到的每个事件信息中的客户端标识信息，对每个事件信息进行去重处理，确定待确定指标对应的目标结果执行次数和执行总次数。
其中，客户端标识信息可以用于对上报每个事件信息的客户端进行唯一标识，以便区分不同的客户端，即区分不同的用户。同一客户端发送的不同事件信息对应同一客户端标识信息。客户端标识信息可以包括但不限于：会话标识session_id。会话标识可以是指客户端与服务器进行信息交互时创建出的会话所对应的标识，从而基于事件信息中的该会话标识可以确定出同一客户端上报的不同事件信息或者同一事件信息。目标结果执行次数可以是指预设行为的执行结果为目标结果的次数，也就是预先行为的执行结果为目标结果的客户端数量，比如进房成功次数或者进房失败次数。执行总次数可以是指预设行为的执行次数，即执行预设行为的客户端数量，比如进房总次数，即进房成功次数和进房失败次数之和。
例如，客户端若不存在日志丢失或者事件上报延时的情况，则服务器可以接收到客户端在每个预设埋点位置处上报的事件信息，即接收到客户端上报的 开始事件信息、结果事件信息、以及目标结果之后的后续事件信息，并且客户端可能存在同一事件信息上报多次的情况，从而需要基于每个事件信息中的客户端标识信息，对同一客户端发送的同一事件信息或者不同事件信息进行去重处理，确定出待确定指标对应的目标结果执行次数和执行总次数。客户端若存在日志丢失导致未接收到目标结果事件信息，或者目标结果事件信息上报延时的情况，则客户端还可以在接收到目标结果之后的后续事件信息时，确定出该次执行结果为目标结果，从而在指标实时确定过程中，可以准确地确定出目标结果执行次数，避免实际结果成功而被误认为失败的情况，进而避免确定出的目标结果执行次数偏小的情况，降低了指标结果的波动幅度。
示例性地，服务器基于接收到的每个事件信息中的客户端标识信息，检测是否存在同一客户端标识信息对应的目标结果事件信息和至少一个后续事件信息中的至少一个事件信息，若存在同一客户端标识信息对应的目标结果事件信息和后续事件信息中的至少一个事件信息，则表明该客户端执行预设行为的结果为目标结果，此时可以对目标结果执行次数进行加1处理，从而可以更加及时准确地确定出最终的目标结果执行次数。通过检测是否存在同一客户端标识信息对应的开始事件信息、结果事件信息和至少一个后续事件信息中的至少一个事件信息，若存在同一客户端标识信息对应的开始事件信息、结果事件信息和至少一个后续事件信息中的至少一个事件信息，则表明该客户端执行了预设行为，此时可以对执行总次数进行加1处理，，从而可以更加准确地确定出最终的执行总次数。
S130、根据目标结果执行次数和执行总次数，确定待确定指标对应的指标结果。
例如，可以将目标结果执行次数与执行总次数的比值作为待确定指标对应的指标结果，从而可以在存在日志丢失或者事件上报延时的情况下，确定出准确、稳定、及时的指标，提高了指标确定的准确性、稳定性和可靠性。
本公开实施例的技术方案，通过预先在待确定指标对应的开始事件生成位置、结果事件生成位置以及位于与待确定指标相匹配的目标结果事件生成位置之后的至少一个后续事件生成位置进行埋点，使得每个客户端可以将每个预设埋点位置处生成的事件信息，即开始事件信息、结果事件信息以及在目标结果事件之后的至少一个后续事件信息进行上报，从而通过客户端上报后续事件信息的方式，可以避免因结果事件丢失而导致指标结果波动大且不准确的情况，同时也避免因结果事件上报延迟而导致实际成功而被误认为失败的情况，从而可以在存在日志丢失或者事件上报延时的情况下，确定出准确、稳定、及时的指标，提高了指标确定的准确性、稳定性和可靠性。
图3为本公开另一实施例提供的一种指标确定方法的流程图，本实施例在 上述实施例的基础上，对目标结果执行次数和执行总次数的确定过程进行了详细描述。其中与上述多个实施例相同或相应的术语的解释在此不再赘述。
参见图3，本实施例提供的指标确定方法包括以下步骤：
S310、接收客户端在预设埋点位置处上报的事件信息，其中，预设埋点位置包括：待确定指标对应的开始事件生成位置、结果事件生成位置以及位于与待确定指标相匹配的目标结果事件生成位置之后的至少一个后续事件生成位置。
S320、基于接收到的每个事件信息中的客户端标识信息，对同一客户端上报的同一事件信息进行去重处理。
例如，服务器可以基于接收到的每个事件信息中的客户端标识信息，对同一客户端上报的同一事件信息进行去重处理，删除同一客户端重复上报的相同事件信息，仅保留同一客户端上报的不同事件信息，以保证后续次数统计的准确性。
S330、基于去重后的每个客户端标识信息对应的目标结果事件信息和后续事件信息，确定待确定指标对应的目标结果执行次数。
例如，针对每个客户端而言，可以检测在去重后的事件信息中是否存在目标结果事件信息和后续事件信息中的至少一个事件信息，若存在，则表明该客户端执行预设行为的结果为目标结果，此时可以对目标结果执行次数进行加1处理，从而在指标实时确定过程中，可以及时准确地确定出最终的目标结果执行次数，避免了在未接收到目标结果事件信息，或者目标结果事件信息上报延时导致的指标波动较大且确定不准确的情况。
示例性地，S330可以包括：对同一客户端标识信息对应的目标结果事件信息和后续事件信息进行再次去重，确定再次去重后的事件信息数量，并将该事件信息数量作为待确定指标对应的目标结果执行次数。
例如，若服务器接收到同一客户端上报的目标结果事件信息和至少一个后续事件信息，则可以删除客户端标识信息相同的目标结果事件信息或者至少一个后续事件信息，仅保留该客户端标识信息对应的一个事件信息。若服务器仅接收到客户端上报的一个目标结果事件信息或者一个后续事件信息，则无需进行再次去重。在对目标结果事件信息和后续事件信息进行再次去重后，确定出再次去重后获得的目标结果事件信息和后续事件信息所对应的事件信息数量，并将该事件信息数量作为待确定指标对应的目标结果执行次数。例如，在待确定指标为预设行为的成功率指标时，确定的目标结果执行次数(即结果成功次数)可以表示为：count(distinct([B1||Cn].session_id)。
S340、基于去重后的每个客户端标识信息对应的开始事件信息，确定待确定指标对应的执行总次数。
例如，可以对去重后的每个客户端标识信息对应的开始事件信息进行数量 统计，并将统计出的事件信息数量作为待确定指标对应的执行总次数。例如，在待确定指标为预设行为的成功率指标时，确定的执行总次数可以表示为：count(distinct([A].session_id)。
示例性地，S340可以包括：基于去重后的每个客户端标识信息对应的开始事件信息、结果事件信息和后续事件信息，确定待确定指标对应的执行总次数。
例如，针对每个客户端而言，可以检测在去重后的事件信息中是否存在开始事件信息、结果事件信息和后续事件信息中的至少一个事件信息，若存在，则表明该客户端执行了预设行为，此时可以对执行总次数进行加1处理，从而在指标实时确定过程中，可以更加准确地确定出最终的执行结果次数，避免了因日志丢失或者事件上报延时导致的指标确定不准确的情况，进一步保住了指标确定的准确性。
示例性地，基于去重后的每个客户端标识信息对应的开始事件信息、结果事件信息和后续事件信息，确定待确定指标对应的执行总次数，可以包括：对同一客户端标识信息对应的开始事件信息、结果事件信息和后续事件信息进行再次去重，确定再次去重后的事件信息数量，并将该事件信息数量作为确定待确定指标对应的执行总次数。
例如，可以对去重后的每个客户端标识信息对应的开始事件信息、结果事件信息和后续事件信息进行再次去重，仅保留该客户端标识信息对应的一个事件信息。在对开始事件信息、结果事件信息和后续事件信息进行再次去重后，确定出再次去重后获得的事件信息数量，并将该事件信息数量作为待确定指标对应的执行总次数。例如，在待确定指标为预设行为的成功率指标时，确定的执行总次数可以表示为：count(distinct([A||B1||B2||Cn].session_id)。
S350、根据目标结果执行次数和执行总次数，确定待确定指标对应的指标结果。
例如，在待确定指标为预设行为的成功率指标时，指标结果可以表示为：count(distinct([B1||Cn].session_id)/count(distinct([A].session_id)，还可以表示为：count(distinct([B1||Cn].session_id)/count(distinct([A||B1||B2||Cn].session_id)。
本实施例的技术方案，通过基于接收到的每个事件信息中的客户端标识信息，对同一客户端上报的同一事件信息进行去重处理，并基于去重后的每个客户端标识信息对应的目标结果事件信息和后续事件信息，确定待确定指标对应的目标结果执行次数，以及基于去重后的每个客户端标识信息对应的开始事件信息，确定待确定指标对应的执行总次数，可以避免因结果事件丢失而导致指标结果波动大且不准确的情况，同时也避免因结果事件上报延迟而导致实际成功而被误认为失败的情况，从而可以在存在日志丢失或者事件上报延时的情况下，确定出准确、稳定、及时的指标，提高了指标确定的准确性、稳定性和可 靠性。
在上述技术方案的基础上，S330可以包括：获取去重后的每个客户端标识信息对应的目标结果事件信息中的时间字段信息；基于时间字段信息，从目标结果事件信息中筛选出耗时时间小于或者等于预设耗时的目标信息；基于目标信息的数量，确定在预设耗时下待确定指标对应的目标结果执行次数。
其中，目标结果事件信息中可以包括一个时间字段信息，即elapse字段信息，用于表征预设行为从开始到结束的耗时时间。预设耗时可以是基于业务需求所指定的最大耗时时间，以便确定出该指定耗时下的指标结果，从而获得N秒成功率指标或者N秒失败率指标。
例如，服务器可以基于去重后获得的每个目标结果事件信息中的时间字段信息，获得该次预设行为执行时的耗时时间，并检测该耗时时间是否小于或者等于预设耗时，若该耗时时间小于或者等于预设耗，则将该目标结果事件信息作为目标信息。同理，确定出耗时时间小于或者等于预设耗时的目标信息，并将目标信息的数量作为在预设耗时下待确定指标对应的目标结果执行次数，并将该目标结果执行次数与执行总次数的比值作为待确定指标在预设耗时下的指标结果，从而可以兼容获得N秒成功率指标或者N秒失败率指标，进一步满足个性化需求。
以下是本公开实施例提供的指标确定装置的实施例，该装置与上述实施例的指标确定方法属于同一个构思，在指标确定装置的实施例中未详尽描述的细节内容，可以参考上述实施例的指标确定方法。
图4为本公开实施例提供的一种指标确定装置的结构示意图，本实施例可适用于对应用程序运行过程中的用户行为指标进行确定的情况。如图4所示，该装置包括：事件信息接收模块410、次数确定模块420和指标结果确定模块430。
其中，事件信息接收模块410，设置为接收客户端在预设埋点位置处上报的事件信息，其中，预设埋点位置包括：待确定指标对应的开始事件生成位置、结果事件生成位置以及位于与待确定指标相匹配的目标结果事件生成位置之后的至少一个后续事件生成位置；次数确定模块420，设置为基于接收到的每个事件信息中的客户端标识信息，对每个事件信息进行去重处理，确定待确定指标对应的目标结果执行次数和执行总次数；指标结果确定模块430，设置为根据目标结果执行次数和执行总次数，确定待确定指标对应的指标结果。
本公开实施例的技术方案，通过预先在待确定指标对应的开始事件生成位置、结果事件生成位置以及位于与待确定指标相匹配的目标结果事件生成位置之后的至少一个后续事件生成位置进行埋点，使得每个客户端可以将每个预设 埋点位置处生成的事件信息，即开始事件信息、结果事件信息以及在目标结果事件之后的至少一个后续事件信息进行上报，从而通过客户端上报后续事件信息的方式，可以避免因结果事件丢失而导致指标结果波动大且不准确的情况，同时也避免因结果事件上报延迟而导致实际成功而被误认为失败的情况，从而可以在存在日志丢失或者事件上报延时的情况下，确定出准确、稳定、及时的指标，提高了指标确定的准确性、稳定性和可靠性。
在上述技术方案的基础上，待确定指标包括：预设行为对应的成功率指标或者失败率指标；客户端标识信息包括：会话标识。
在上述多个技术方案的基础上，次数确定模块420，包括：
去重处理单元，设置为基于接收到的每个事件信息中的客户端标识信息，对同一客户端上报的同一事件信息进行去重处理；
目标结果执行次数确定单元，设置为基于去重后的每个客户端标识信息对应的目标结果事件信息和后续事件信息，确定待确定指标对应的目标结果执行次数；
执行总次数确定单元，设置为基于去重后的每个客户端标识信息对应的开始事件信息，确定待确定指标对应的执行总次数。
在上述多个技术方案的基础上，目标结果执行次数确定单元，设置为：
对同一客户端标识信息对应的目标结果事件信息和后续事件信息进行再次去重，确定再次去重后的事件信息数量，并将该事件信息数量作为待确定指标对应的目标结果执行次数。
在上述多个技术方案的基础上，执行总次数确定单元，还设置为：
基于去重后的每个客户端标识信息对应的开始事件信息、结果事件信息和后续事件信息，确定待确定指标对应的执行总次数。
在上述多个技术方案的基础上，执行总次数确定单元，还设置为：
对同一客户端标识信息对应的开始事件信息、结果事件信息和后续事件信息进行再次去重，确定再次去重后的事件信息数量，并将该事件信息数量作为确定待确定指标对应的执行总次数。
在上述多个技术方案的基础上，目标结果执行次数确定单元，还设置为：
获取去重后的每个客户端标识信息对应的目标结果事件信息中的时间字段信息；基于时间字段信息，从目标结果事件信息中筛选出耗时时间小于或者等于预设耗时的目标信息；基于目标信息的数量，确定在预设耗时下待确定指标对应的目标结果执行次数。
本公开实施例所提供的指标确定装置可执行本公开任意实施例所提供的指标确定方法，具备执行指标确定方法相应的功能模块和有益效果。
值得注意的是，上述指标确定装置的实施例中，所包括的多个单元和模块 只是按照功能逻辑进行划分的，但并不局限于上述的划分，只要能够实现相应的功能即可；另外，多个功能单元的具体名称也只是为了便于相互区分，并不用于限制本公开的保护范围。
下面参考图5，其示出了适于用来实现本公开实施例的服务器900的结构示意图。图5示出的服务器仅仅是一个示例，不应对本公开实施例的功能和使用范围带来任何限制。
如图5所示，服务器900可以包括处理装置(例如中央处理器、图形处理器等)901，其可以根据存储在只读存储器(ROM)902中的程序或者从存储装置908加载到随机访问存储器(RAM)903中的程序而执行多种适当的动作和处理。在RAM 903中，还存储有服务器900操作所需的多种程序和数据。处理装置901、ROM 902以及RAM 903通过总线904彼此相连。输入/输出(I/O)接口905也连接至总线904。
通常，以下装置可以连接至I/O接口905：包括例如触摸屏、触摸板、键盘、鼠标、摄像头、麦克风、加速度计、陀螺仪等的输入装置906；包括例如液晶显示器(LCD)、扬声器、振动器等的输出装置907；包括例如磁带、硬盘等的存储装置908；以及通信装置909。通信装置909可以允许服务器900与其他设备进行无线或有线通信以交换数据。虽然图5示出了具有多种装置的服务器900，但是应理解的是，并不要求实施或具备所有示出的装置。可以替代地实施或具备更多或更少的装置。
根据本公开的实施例，上文参考流程图描述的过程可以被实现为计算机软件程序。例如，本公开的实施例包括一种计算机程序产品，其包括承载在非暂态计算机可读介质上的计算机程序，该计算机程序包含用于执行流程图所示的方法的程序代码。在这样的实施例中，该计算机程序可以通过通信装置909从网络上被下载和安装，或者从存储装置908被安装，或者从ROM 902被安装。在该计算机程序被处理装置901执行时，执行本公开实施例的方法中限定的上述功能。
本公开实施例提供的服务器与上述实施例提供的指标确定方法属于同一构思，未在本公开实施例中详尽描述的技术细节可参见上述实施例，并且本公开实施例与上述实施例具有相同的有益效果。
本公开实施例提供了一种计算机存储介质，其上存储有计算机程序，该程序被处理器执行时实现上述实施例所提供的指标确定方法。
需要说明的是，本公开上述的计算机可读介质可以是计算机可读信号介质或者计算机可读存储介质或者是上述两者的任意组合。计算机可读存储介质例如可以是——但不限于——电、磁、光、电磁、红外线、或半导体的系统、装置或器件，或者任意以上的组合。计算机可读存储介质的更具体的例子可以包 括但不限于：具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、随机访问存储器(RAM)、只读存储器(ROM)、可擦式可编程只读存储器(EPROM或闪存)、光纤、便携式紧凑磁盘只读存储器(CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。在本公开中，计算机可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。而在本公开中，计算机可读信号介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了计算机可读的程序代码。这种传播的数据信号可以采用多种形式，包括但不限于电磁信号、光信号或上述的任意合适的组合。计算机可读信号介质还可以是计算机可读存储介质以外的任何计算机可读介质，该计算机可读信号介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。计算机可读介质上包含的程序代码可以用任何适当的介质传输，包括但不限于：电线、光缆、RF(射频)等等，或者上述的任意合适的组合。
在一些实施方式中，客户端、服务器可以利用诸如HTTP(HyperText Transfer Protocol，超文本传输协议)之类的任何当前已知或未来研发的网络协议进行通信，并且可以与任意形式或介质的数字数据通信(例如，通信网络)互连。通信网络的示例包括局域网(“LAN”)，广域网(“WAN”)，网际网(例如，互联网)以及端对端网络(例如，ad hoc端对端网络)，以及任何当前已知或未来研发的网络。
上述计算机可读介质可以是上述服务器中所包含的；也可以是单独存在，而未装配入该服务器中。
上述计算机可读介质承载有一个或者多个程序，当上述一个或者多个程序被该服务器执行时，使得该服务器：接收客户端在每个预设埋点位置处上报的事件信息，其中，预设埋点位置包括：待确定指标对应的开始事件生成位置、结果事件生成位置以及位于与待确定指标相匹配的目标结果事件生成位置之后的至少一个后续事件生成位置；基于接收到的每个事件信息中的客户端标识信息，对每个事件信息进行去重处理，确定待确定指标对应的目标结果执行次数和执行总次数；根据目标结果执行次数和执行总次数，确定待确定指标对应的指标结果。
可以以一种或多种程序设计语言或其组合来编写用于执行本公开的操作的计算机程序代码，上述程序设计语言包括但不限于面向对象的程序设计语言—诸如Java、Smalltalk、C++，还包括常规的过程式程序设计语言—诸如“C”语言或类似的程序设计语言。程序代码可以完全地在用户计算机上执行、部分地在用户计算机上执行、作为一个独立的软件包执行、部分在用户计算机上部分在远程计算机上执行、或者完全在远程计算机或服务器上执行。在涉及远程计算 机的情形中，远程计算机可以通过任意种类的网络——包括局域网(LAN)或广域网(WAN)—连接到用户计算机，或者，可以连接到外部计算机(例如利用因特网服务提供商来通过因特网连接)。
附图中的流程图和框图，图示了按照本公开多种实施例的系统、方法和计算机程序产品的可能实现的体系架构、功能和操作。在这点上，流程图或框图中的每个方框可以代表一个模块、程序段、或代码的一部分，该模块、程序段、或代码的一部分包含一个或多个用于实现规定的逻辑功能的可执行指令。也应当注意，在有些作为替换的实现中，方框中所标注的功能也可以以不同于附图中所标注的顺序发生。例如，两个接连地表示的方框实际上可以基本并行地执行，它们有时也可以按相反的顺序执行，这依所涉及的功能而定。也要注意的是，框图和/或流程图中的每个方框、以及框图和/或流程图中的方框的组合，可以用执行规定的功能或操作的专用的基于硬件的系统来实现，或者可以用专用硬件与计算机指令的组合来实现。
描述于本公开实施例中所涉及到的单元可以通过软件的方式实现，也可以通过硬件的方式来实现。其中，单元的名称在某种情况下并不构成对该单元本身的限定，例如，可编辑内容显示单元还可以被描述为“编辑单元”。
本文中以上描述的功能可以至少部分地由一个或多个硬件逻辑部件来执行。例如，非限制性地，可以使用的示范类型的硬件逻辑部件包括：现场可编程门阵列(FPGA)、专用集成电路(ASIC)、专用标准产品(ASSP)、片上系统(SOC)、复杂可编程逻辑设备(CPLD)等等。
在本公开的上下文中，机器可读介质可以是有形的介质，其可以包含或存储以供指令执行系统、装置或设备使用或与指令执行系统、装置或设备结合地使用的程序。机器可读介质可以是机器可读信号介质或机器可读储存介质。机器可读介质可以包括但不限于电子的、磁性的、光学的、电磁的、红外的、或半导体系统、装置或设备，或者上述内容的任何合适组合。机器可读存储介质的更具体示例会包括基于一个或多个线的电气连接、便携式计算机盘、硬盘、随机存取存储器(RAM)、只读存储器(ROM)、可擦除可编程只读存储器(EPROM或快闪存储器)、光纤、便捷式紧凑盘只读存储器(CD-ROM)、光学储存设备、磁储存设备、或上述内容的任何合适组合。
根据本公开的一个或多个实施例，【示例一】提供了一种指标确定方法，包括：
接收客户端在预设埋点位置处上报的事件信息，其中，所述预设埋点位置包括：待确定指标对应的开始事件生成位置、结果事件生成位置以及位于与所述待确定指标相匹配的目标结果事件生成位置之后的至少一个后续事件生成位 置；
基于接收到的每个事件信息中的客户端标识信息，对每个事件信息进行去重处理，确定所述待确定指标对应的目标结果执行次数和执行总次数；
根据所述目标结果执行次数和所述执行总次数，确定所述待确定指标对应的指标结果。
根据本公开的一个或多个实施例，【示例二】提供了一种指标确定方法，其中，所述待确定指标包括：预设行为对应的成功率指标或者失败率指标；所述客户端标识信息包括：会话标识。
根据本公开的一个或多个实施例，【示例三】提供了一种指标确定方法，其中，所述基于接收到的每个事件信息中的客户端标识信息，对每个事件信息进行去重处理，确定所述待确定指标对应的目标结果执行次数和执行总次数，包括：
基于接收到的每个事件信息中的客户端标识信息，对同一客户端上报的同一事件信息进行去重处理；
基于去重后的每个客户端标识信息对应的目标结果事件信息和后续事件信息，确定所述待确定指标对应的目标结果执行次数；
基于去重后的每个客户端标识信息对应的开始事件信息，确定所述待确定指标对应的执行总次数。
根据本公开的一个或多个实施例，【示例四】提供了一种指标确定方法，其中，所述基于去重后的每个客户端标识信息对应的目标结果事件信息和后续事件信息，确定所述待确定指标对应的目标结果执行次数，包括：
对同一客户端标识信息对应的目标结果事件信息和后续事件信息进行再次去重，确定再次去重后的事件信息数量，并将再次去重后的事件信息数量作为所述待确定指标对应的目标结果执行次数。
根据本公开的一个或多个实施例，【示例五】提供了一种指标确定方法，其中，所述基于去重后的每个客户端标识信息对应的开始事件信息，确定所述待确定指标对应的执行总次数，包括：
基于去重后的每个客户端标识信息对应的开始事件信息、结果事件信息和后续事件信息，确定所述待确定指标对应的执行总次数。
根据本公开的一个或多个实施例，【示例六】提供了一种指标确定方法，其中，所述基于去重后的每个客户端标识信息对应的开始事件信息、结果事件信息和后续事件信息，确定所述待确定指标对应的执行总次数，包括：
对同一客户端标识信息对应的开始事件信息、结果事件信息和后续事件信息进行再次去重，确定再次去重后的事件信息数量，并将再次去重后的事件信息数量作为确定所述待确定指标对应的执行总次数。
根据本公开的一个或多个实施例，【示例七】提供了一种指标确定方法，其中，所述基于去重后的每个客户端标识信息对应的目标结果事件信息和后续事件信息，确定所述待确定指标对应的目标结果执行次数，包括：
获取去重后的每个客户端标识信息对应的目标结果事件信息中的时间字段信息；
基于所述时间字段信息，从所述目标结果事件信息中筛选出耗时时间小于或者等于预设耗时的目标信息；
基于所述目标信息的数量，确定在所述预设耗时下所述待确定指标对应的目标结果执行次数。
根据本公开的一个或多个实施例，【示例八】提供了一种指标确定装置，包括：
事件信息接收模块，设置为接收客户端在预设埋点位置处上报的事件信息，其中，所述预设埋点位置包括：待确定指标对应的开始事件生成位置、结果事件生成位置以及位于与所述待确定指标相匹配的目标结果事件生成位置之后的至少一个后续事件生成位置；
次数确定模块，设置为基于接收到的每个事件信息中的客户端标识信息，对每个事件信息进行去重处理，确定所述待确定指标对应的目标结果执行次数和执行总次数；
指标结果确定模块，设置为根据所述目标结果执行次数和所述执行总次数，确定所述待确定指标对应的指标结果。
此外，虽然采用特定次序描绘了多种操作，但是这不应当理解为要求这些操作以所示出的特定次序或以顺序次序执行来执行。在一定环境下，多任务和并行处理可能是有利的。同样地，虽然在上面论述中包含了若干具体实现细节，但是这些不应当被解释为对本公开的范围的限制。在单独的实施例的上下文中描述的某些特征还可以组合地实现在单个实施例中。相反地，在单个实施例的上下文中描述的多种特征也可以单独地或以任何合适的子组合的方式实现在多个实施例中。

Claims (10)

  1. 一种指标确定方法，包括：
    接收客户端在预设埋点位置处上报的事件信息，其中，所述预设埋点位置包括：待确定指标对应的开始事件生成位置、结果事件生成位置以及位于与所述待确定指标相匹配的目标结果事件生成位置之后的至少一个后续事件生成位置；
    基于接收到的每个事件信息中的客户端标识信息，对所述每个事件信息进行去重处理，确定所述待确定指标对应的目标结果执行次数和执行总次数；
    根据所述目标结果执行次数和所述执行总次数，确定所述待确定指标对应的指标结果。
  2. 根据权利要求1所述的方法，其中，所述待确定指标包括：预设行为对应的成功率指标或者失败率指标；所述客户端标识信息包括：会话标识。
  3. 根据权利要求1所述的方法，其中，所述基于接收到的每个事件信息中的客户端标识信息，对所述每个事件信息进行去重处理，确定所述待确定指标对应的目标结果执行次数和执行总次数，包括：
    基于接收到的每个事件信息中的客户端标识信息，对同一客户端上报的同一事件信息进行去重处理；
    基于去重后的每个客户端标识信息对应的目标结果事件信息和后续事件信息，确定所述待确定指标对应的目标结果执行次数；
    基于去重后的每个客户端标识信息对应的开始事件信息，确定所述待确定指标对应的执行总次数。
  4. 根据权利要求3所述的方法，其中，所述基于去重后的每个客户端标识信息对应的目标结果事件信息和后续事件信息，确定所述待确定指标对应的目标结果执行次数，包括：
    对同一客户端标识信息对应的目标结果事件信息和后续事件信息进行再次去重，确定再次去重后的事件信息数量，并将再次去重后的事件信息数量作为所述待确定指标对应的目标结果执行次数。
  5. 根据权利要求3所述的方法，其中，所述基于去重后的每个客户端标识信息对应的开始事件信息，确定所述待确定指标对应的执行总次数，包括：
    基于去重后的每个客户端标识信息对应的开始事件信息、结果事件信息和后续事件信息，确定所述待确定指标对应的执行总次数。
  6. 根据权利要求5所述的方法，其中，所述基于去重后的每个客户端标识信息对应的开始事件信息、结果事件信息和后续事件信息，确定所述待确定指标对应的执行总次数，包括：
    对同一客户端标识信息对应的开始事件信息、结果事件信息和后续事件信息进行再次去重，确定再次去重后的事件信息数量，并将再次去重后的事件信 息数量作为确定所述待确定指标对应的执行总次数。
  7. 根据权利要求3所述的方法，其中，所述基于去重后的每个客户端标识信息对应的目标结果事件信息和后续事件信息，确定所述待确定指标对应的目标结果执行次数，包括：
    获取去重后的每个客户端标识信息对应的目标结果事件信息中的时间字段信息；
    基于所述时间字段信息，从所述目标结果事件信息中筛选出耗时时间小于或者等于预设耗时的目标信息；
    基于所述目标信息的数量，确定在所述预设耗时下所述待确定指标对应的目标结果执行次数。
  8. 一种指标确定装置，包括：
    事件信息接收模块，设置为接收客户端在预设埋点位置处上报的事件信息，其中，所述预设埋点位置包括：待确定指标对应的开始事件生成位置、结果事件生成位置以及位于与所述待确定指标相匹配的目标结果事件生成位置之后的至少一个后续事件生成位置；
    次数确定模块，设置为基于接收到的每个事件信息中的客户端标识信息，对所述每个事件信息进行去重处理，确定所述待确定指标对应的目标结果执行次数和执行总次数；
    指标结果确定模块，设置为根据所述目标结果执行次数和所述执行总次数，确定所述待确定指标对应的指标结果。
  9. 一种服务器，包括：
    一个或多个处理器；
    存储器，设置为存储一个或多个程序；
    当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如权利要求1-7中任一所述的指标确定方法。
  10. 一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1-7中任一所述的指标确定方法。
PCT/CN2023/078651 2022-03-09 2023-02-28 一种指标确定方法、装置、服务器和介质 WO2023169251A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210225178.0A CN114579416B (zh) 2022-03-09 2022-03-09 一种指标确定方法、装置、服务器和介质
CN202210225178.0 2022-03-09

Publications (1)

Publication Number Publication Date
WO2023169251A1 true WO2023169251A1 (zh) 2023-09-14

Family

ID=81773446

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/078651 WO2023169251A1 (zh) 2022-03-09 2023-02-28 一种指标确定方法、装置、服务器和介质

Country Status (2)

Country Link
CN (1) CN114579416B (zh)
WO (1) WO2023169251A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114579416B (zh) * 2022-03-09 2024-05-03 北京字节跳动网络技术有限公司 一种指标确定方法、装置、服务器和介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111444072A (zh) * 2020-03-26 2020-07-24 世纪龙信息网络有限责任公司 客户端的异常识别方法、装置、计算机设备和存储介质
CN112527414A (zh) * 2020-12-23 2021-03-19 平安普惠企业管理有限公司 一种基于前端的数据处理方法、装置、设备及存储介质
WO2021082858A1 (zh) * 2019-10-28 2021-05-06 深圳前海微众银行股份有限公司 一种数据采集方法及装置
CN113901153A (zh) * 2021-10-15 2022-01-07 马上消费金融股份有限公司 数据处理方法及相关设备
CN114579416A (zh) * 2022-03-09 2022-06-03 北京字节跳动网络技术有限公司 一种指标确定方法、装置、服务器和介质

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011023424A1 (en) * 2009-08-27 2011-03-03 International Business Machines Corporation A method and system for testing a computer program
US8719568B1 (en) * 2011-06-30 2014-05-06 Cellco Partnership Secure delivery of sensitive information from a non-communicative actor
US20150161678A1 (en) * 2013-12-05 2015-06-11 Turn Inc. Dynamic ordering of online advertisement software steps
US10380098B1 (en) * 2015-09-30 2019-08-13 EMC IP Holding Company LLC Fine-grained shared multi-tenant de-duplication system
US10394677B2 (en) * 2016-10-28 2019-08-27 International Business Machines Corporation Method to efficiently and reliably process ordered user account events in a cluster
CN108156006B (zh) * 2016-12-05 2021-10-12 阿里巴巴集团控股有限公司 一种埋点数据上报方法、装置及电子设备
CN108363657B (zh) * 2018-01-25 2021-07-06 上海连尚网络科技有限公司 监控app客户端埋点数据采集完整性的方法、设备以及介质
CN110633390A (zh) * 2018-05-31 2019-12-31 北京嘀嘀无限科技发展有限公司 获取用户行为路径的方法和装置
CN110362480A (zh) * 2019-06-19 2019-10-22 平安普惠企业管理有限公司 客户端埋点测试方法、装置、设备及存储介质
US11516238B2 (en) * 2019-08-15 2022-11-29 Bank Of Montreal Systems and methods for monitoring user activities
CN110781061B (zh) * 2019-09-20 2022-11-25 平安科技（深圳）有限公司 一种记录用户行为链路的方法及装置
CN112015788A (zh) * 2020-08-28 2020-12-01 支付宝(杭州)信息技术有限公司 向目标用户展示目标对象序列的方法和装置
CN112416728A (zh) * 2020-11-23 2021-02-26 平安普惠企业管理有限公司 埋点数据获取方法、装置、客户端设备及可读存储介质
CN112799925A (zh) * 2021-01-25 2021-05-14 北京嘀嘀无限科技发展有限公司 数据采集方法、装置、电子设备和可读存储介质
CN113472858B (zh) * 2021-06-10 2023-09-29 北京达佳互联信息技术有限公司 埋点数据处理方法、装置及电子设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021082858A1 (zh) * 2019-10-28 2021-05-06 深圳前海微众银行股份有限公司 一种数据采集方法及装置
CN111444072A (zh) * 2020-03-26 2020-07-24 世纪龙信息网络有限责任公司 客户端的异常识别方法、装置、计算机设备和存储介质
CN112527414A (zh) * 2020-12-23 2021-03-19 平安普惠企业管理有限公司 一种基于前端的数据处理方法、装置、设备及存储介质
CN113901153A (zh) * 2021-10-15 2022-01-07 马上消费金融股份有限公司 数据处理方法及相关设备
CN114579416A (zh) * 2022-03-09 2022-06-03 北京字节跳动网络技术有限公司 一种指标确定方法、装置、服务器和介质

Also Published As

Publication number Publication date
CN114579416A (zh) 2022-06-03
CN114579416B (zh) 2024-05-03

Similar Documents

Publication Publication Date Title
US10484326B2 (en) Distributed message queue stream verification
CN109508326B (zh) 用于处理数据的方法、装置和系统
US20130226985A1 (en) Monitoring a path of a transaction across a composite application
WO2023273544A1 (zh) 日志文件的存储方法、装置、设备和存储介质
WO2023169251A1 (zh) 一种指标确定方法、装置、服务器和介质
CN107943618B (zh) 仿真系统的数据快速恢复方法及存储介质
CN111930385A (zh) 数据采集方法、装置、设备及存储介质
WO2023273539A1 (zh) 航班查询系统业务监控方法、装置、设备及存储介质
EP4280565A1 (en) Sample message processing method and apparatus
WO2022068348A1 (zh) 关系图谱构建方法、装置、电子设备及存储介质
WO2021073413A1 (zh) 系统性能参数的发送方法、装置、管理设备和存储介质
CN114020496A (zh) 一种数据核对方法、装置、电子设备和存储介质
CN110955709B (zh) 一种数据的处理方法、装置及电子设备
CN112948410A (zh) 数据处理方法、装置、设备及介质
CN113760988A (zh) 一种无界流数据关联处理方法、装置、设备及存储介质
CN112667119A (zh) 测点批量关联方法、装置、电子设备和计算机可读介质
CN112749204A (zh) 一种读取数据的方法和装置
CN112015746A (zh) 数据实时处理方法、装置、介质和电子设备
CN116431523B (zh) 一种测试数据管理方法、装置、设备及存储介质
CN113225228B (zh) 数据处理方法及装置
CN113760982B (zh) 一种数据处理方法和装置
CN113779139A (zh) 信息同步方法、装置、电子设备和计算机可读介质
EP4191983A1 (en) Driving data processing method, apparatus, device, automatic driving vehicle, medium and product
CN117908783A (zh) 一种操作日志上传方法、装置、电子设备和可读介质
CN113760903A (zh) 一种无界流数据关联处理方法、装置、设备及存储介质

Legal Events

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

Ref document number: 23765829

Country of ref document: EP

Kind code of ref document: A1