Data playback method, device, storage medium, and electronic device

Abstract

The embodiments of the present disclosure relate to the field of computer information technology, and more specifically, the embodiments of the present disclosure relate to a data playback method, device, storage medium, and electronic device. The method includes: obtaining business data from a source business terminal, associating the business data with a scene code; determining the scene to which the business data belongs according to the scene code; determining the recording plan to which the business data belongs according to the recording conditions; storing the business data associated with the recording plan in a database; in response to a business data interruption from the source business terminal to the target business terminal, generating playback conditions according to the business data interruption information; determining the scene code and its recording plan required for playback according to the playback conditions; obtaining business data from the database according to the determined scene code and its recording plan; and sending the obtained business data to the target business terminal for data playback. The technical solution of the present disclosure automatically realizes the storage and playback of business data, while improving the efficiency of data playback.

Description

Technical Field

[0001] The embodiments of the present disclosure relate to the field of computer information technology, and more specifically, relate to a data playback method, device, storage medium, and electronic device. Background Art

[0002] This section is intended to provide a background or context to the embodiments of the disclosure that are recited in the claims, and no description herein is admitted to be prior art by inclusion in this section.

[0003] When business data is abnormal due to configuration errors, network jitters, or logical vulnerabilities, the target business end that relies on the business data for business analysis will not work properly. In order to make the target business end of the business data work properly, the business data needs to be repaired when the business data is abnormal. Summary of the invention

[0004] In some technologies, historical data is generally retrieved from the original flow table, log file or offline storage medium, and then a specific repair script is written based on the retrieved historical data. After the repair script is tested in the test environment, it is released to the production environment. Then, the interface call or scheduled task is executed once to trigger the temporarily written script to achieve the purpose of data repair. However, this data playback method has low data playback efficiency and relies on manual completion, which is prone to errors.

[0005] Therefore, there is a great need for an improved data playback method and device, storage medium and electronic device to realize automatic recording and playback of business data and improve data playback efficiency and accuracy.

[0006] In this context, embodiments of the present invention are intended to provide a data playback method and apparatus, a storage medium, and an electronic device.

[0007] According to one aspect of the present disclosure, there is provided a data playback method, comprising:

[0008] Acquire business data from a source business terminal, the business data is associated with a scenario code, the business data is automatically sent to a target business terminal associated with the scenario code for business data analysis, and the data analysis result is used to feed back to the source business terminal;

[0009] Determine the scene to which the service data belongs according to the scene code, where the scene includes one or more recording plans, each of which has a preset recording condition;

[0010] Determining the recording plan to which the business data belongs according to the recording condition;

[0011] The business data is associated with the recording plan and stored in a database,

[0012] In response to a service data interruption from the source service end to the target service end, generating a playback condition according to service data interruption information;

[0013] Determine the scene code and recording plan required for playback according to the playback condition;

[0014] Acquiring service data from the database according to the determined scene code and its recording plan;

[0015] The acquired business data is sent to the target business end for data playback.

[0016] According to one aspect of the present disclosure, there is provided a data playback device, comprising:

[0017] A business data acquisition module is used to acquire business data from a source business terminal, the business data is associated with a scenario code, the business data is automatically sent to a target business terminal associated with the scenario code for business data analysis, and the data analysis result is used to feed back to the source business terminal;

[0018] A scene determination module, used to determine the scene to which the service data belongs according to the scene code, wherein the scene includes one or more recording plans, each of which has a preset recording condition;

[0019] A recording plan determination module, used to determine the recording plan to which the business data belongs according to the recording condition;

[0020] A recording storage module is used to store the business data in association with the recording plan in a database,

[0021] A playback condition generating module, configured to generate a playback condition according to the service data interruption information in response to the service data interruption from the source service end to the target service end;

[0022] A playback object determination module, used to determine the scene code required for playback and its recording plan according to the playback conditions;

[0023] A playback data acquisition module, used to acquire business data from the database according to the determined scene code and its recording plan;

[0024] The data playback module is used to send the acquired business data to the target business end for data playback.

[0025] According to one aspect of the present disclosure, a storage medium is provided, on which a computer program is stored, and the computer program performs the above-mentioned data playback method when executed by a processor.

[0026] According to one aspect of the present disclosure, there is provided an electronic device, including:

[0027] Processor; and

[0028] A memory, configured to store executable instructions of the processor;

[0029] The processor is configured to execute any one of the above-mentioned data playback methods by executing the executable instructions.

[0030] According to the data playback method of the embodiment of the present disclosure, the business data obtained from the source business terminal is stored through the set scene and recording plan. When the business data is disconnected, the playback condition can be generated according to the disconnection situation, and the business data for playback can be obtained from the stored business data according to the playback condition to perform data playback. Therefore, on the one hand, the storage and playback of business data are automatically realized without manual participation; on the other hand, the business data is stored according to the set scene and recording plan to improve the efficiency of data playback. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] The above and other objects, features and advantages of the exemplary embodiments of the present disclosure will become readily understood by reading the detailed description below with reference to the accompanying drawings. In the accompanying drawings, several embodiments of the present disclosure are shown in an exemplary and non-limiting manner, in which:

[0032] Figure 1 The flowchart of the data playback method according to the embodiment of the present disclosure is schematically shown;

[0033] Figure 2 A system diagram of a data playback method according to an embodiment of the present disclosure is schematically shown;

[0034] Figure 3 The flowchart of configuring a dynamic message consumption engine in a configuration center according to an embodiment of the present disclosure is schematically shown;

[0035] Figure 4 The flowchart of obtaining and storing service data from a source service end according to an embodiment of the present disclosure is schematically shown;

[0036] Figure 5 The flowchart of obtaining business data for playback according to an embodiment of the present disclosure is schematically shown;

[0037] Figure 6 A block diagram schematically shows a data playback device according to an embodiment of the present disclosure;

[0038] Figure 7 A schematic diagram showing a storage medium according to an embodiment of the present disclosure; and

[0039] Figure 8 A block diagram of an electronic device according to a disclosed embodiment is schematically shown.

[0040] In the drawings, the same or corresponding reference numerals represent the same or corresponding parts. DETAILED DESCRIPTION

[0041] The principles and spirit of the present invention will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are provided only to enable those skilled in the art to better understand and implement the present invention, and are not intended to limit the scope of the present invention in any way. On the contrary, these embodiments are provided to make the present disclosure more thorough and complete, and to fully convey the scope of the present disclosure to those skilled in the art.

[0042] Those skilled in the art will appreciate that the embodiments of the present disclosure may be implemented as a system, device, apparatus, method or computer program product. Therefore, the present disclosure may be specifically implemented in the following forms, namely: complete hardware, complete software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.

[0043] According to an embodiment of the present disclosure, a data playback method, a data playback device, a storage medium and an electronic device are provided.

[0044] In this document, any number of elements in the drawings is used for illustration rather than limitation, and any naming is used only for distinction and does not have any limiting meaning.

[0045] The principle and spirit of the present disclosure are explained in detail below with reference to several representative embodiments of the present disclosure. SUMMARY OF THE INVENTION

[0047] The inventor has found that, currently, when business data is abnormal due to configuration errors, network jitters, or logical vulnerabilities, historical data is retrieved from the original flow table, log file, or offline storage medium, and then a specific repair script is written based on the retrieved historical data. After the repair script is tested in the test environment, it is released to the production environment. Then, an interface call or a scheduled task is executed to trigger the temporarily written script once to achieve the purpose of data repair.

[0048] The above scheme has the following problems: there may be data missing in the original flow table, log file or offline storage, which makes it impossible to recover the data after it is lost, and thus it is impossible to replay the data; the replay method of the original flow table can only retrieve data from the data source, and a large number of calculation processes in the intermediate process need to be repeated when the data is repaired, which leads to low efficiency of data replay; in the data replay method of log retrieval, it is necessary to rely on log burial points and log collection platforms. If there is a lack of relevant log burial points or the infrastructure for log collection is not equipped, it is impossible to complete the retrieval of historical data, and thus it is impossible to replay the data; in the data replay method of log retrieval, due to the diversity of log formats, log cleaning is required after the logs are collected, which increases the complexity of data replay; offline storage media generally store business data in batches at regular intervals according to settings, which leads to a large delay in the stored data and cannot achieve timely data replay; the entire data replay process relies on manual completion, which is prone to errors and inefficient.

[0049] In view of the above, the basic idea of ​​the present invention is to store the business data obtained from the source business end through the set scene and recording plan. When the business data is disconnected, the playback conditions can be generated according to the disconnection situation, and the business data for playback can be obtained from the stored business data according to the playback conditions to perform data playback. Thus, on the one hand, the storage and playback of business data are automatically realized without manual participation; on the other hand, the business data is stored according to the set scene and recording plan, so as to improve the speed of obtaining business data and the playback efficiency when the data is played back.

[0050] After introducing the basic principles of the present invention, various non-limiting embodiments of the present invention are described in detail below.

[0051] Exemplary Methods

[0052] Combine the following Figure 1 A data playback method according to an exemplary embodiment of the present disclosure will be described.

[0053] refer to Figure 1 As shown, the data playback method may include the following steps:

[0054] Step S110: acquiring business data from a source business terminal, the business data being associated with a scenario code, the business data being automatically sent to a target business terminal associated with the scenario code for business data analysis, and the data analysis result being used to feed back to the source business terminal;

[0055] Step S120: determining the scene to which the service data belongs according to the scene code, wherein the scene includes one or more recording plans, and each recording plan is preset with recording conditions;

[0056] Step S130, determining the recording plan to which the service data belongs according to the recording condition;

[0057] Step S140, storing the service data in association with the recording plan in a database;

[0058] Step S150, in response to the interruption of the flow of service data from the source service end to the target service end, generating a playback condition according to the information of the interruption of the flow of service data;

[0059] Step S160, determining the scene code and recording plan required for playback according to the playback condition;

[0060] Step S170, acquiring service data from the database according to the determined scene code and its recording plan;

[0061] Step S180: sending the acquired business data to the target business end for data playback.

[0062] In the data playback method of the embodiment of the present disclosure, the business data obtained from the source business terminal is stored through the set scene and recording plan. When the business data is disconnected, the playback condition can be generated according to the disconnection situation, and the business data for playback can be obtained from the stored business data according to the playback condition to perform data playback. Thus, on the one hand, the storage and playback of business data are automatically realized without manual participation; on the other hand, the business data is stored according to the set scene and recording plan, so as to improve the speed of obtaining business data and the playback efficiency when the data is played back.

[0063] The source business end is the business end that produces business data. The target business end is the business end that uses and analyzes business data. The business end is a client deployed on the device in the form of applications, applets, web pages, etc. to provide corresponding business services. In the normal business data flow process, the source business end produces business data, and the target business end processes and analyzes the business data of the source business end to generate data analysis results and feed them back to the source business end.

[0064] For example, the source business end is a dating application, and the target business end is a message push engine. When users use dating applications, user behavior logs are generated. The source business end sends these user behavior logs to the message push engine. The message push engine performs user behavior analysis based on the received user behavior logs to determine which type of messages to deliver to users through dating applications. When the user behavior logs sent by dating applications to the message push engine are interrupted, the message push engine will find it difficult to analyze the user behavior logs, resulting in the delivered messages not meeting user expectations, reducing user experience. The method disclosed in the present invention is particularly suitable for use when the user behavior logs sent by dating applications to the message push engine are interrupted, and can provide data playback to the message push engine, thereby ensuring that the message push engine can obtain user behavior logs for data analysis and processing such as user portrait analysis.

[0065] For another example, the source business end is a live broadcast application, and the target business end is a server that provides and updates a gift list. The server obtains the virtual gifts sent by each user in each live broadcast room through the live broadcast application in real time, updates the gift list based on the information, and displays it on the live broadcast room interface. When the business data of the live broadcast application for sending virtual gifts is disconnected and cannot be sent to the server, the data for updating the gift list by the server is missing, so that the updated gift list data is bound to be wrong, which will reduce the user experience of sending virtual gifts. The method disclosed in the present invention is particularly suitable for use in live broadcast applications. When the business data of sending virtual gifts is disconnected and cannot be sent to the server, it can provide data playback to the server, thereby ensuring that the server can obtain the completed virtual gift data to accurately update the gift list.

[0066] In an exemplary embodiment of the present disclosure, obtaining service data from a source service terminal may include directly or indirectly obtaining service data from the source service terminal. The service data obtained from the source service terminal may be processed or unprocessed service data.

[0067] The acquired business data is associated with a scene code. The scene code is used to distinguish different scenes. The scenes may include: message push of the message push engine of the dating application, update of the gift list of the server of the live broadcast application, update of the list of personnel in the live broadcast room of the live broadcast application, etc. The scene and the scene code can be set as needed. One or more recording plans can be set in each scene. The recording plan is used to record the business data of different recording conditions in the scene. The recording condition can be time. For example, for the same scene, the business data from Monday to Friday is set as one recording plan, and the business data from Saturday to Sunday is set as another recording plan; the business data from 8 am to 6 pm is set as one recording plan; the business data from 6 pm to 8 am is set as another recording plan. The recording conditions can be set according to the attributes of the scene. For example, in the scene of updating the live broadcast gift list, the business data with a gift value greater than a set threshold can be set as a recording plan, and the business data with a gift value not greater than the set threshold can be set as another recording plan. The recording plan can be set as needed, and the present disclosure is not limited to this.

[0068] In an exemplary embodiment of the present disclosure, step S110 may include synchronously acquiring business data from the source business end through a first remote business call interface. Specifically, the first remote business call interface may be implemented based on a cross-process method call technology used in a distributed environment. For example, the data transmission of the business data of the source business end may be encapsulated as a remote business call interface, and the data playback platform may call the remote business call interface to synchronously acquire the business data.

[0069] In an exemplary embodiment of the present disclosure, step S110 may include asynchronously acquiring business data from the source business end through a first message queue. In an embodiment of acquiring business data through a first message queue, the source business end may push business messages to the first message queue on its own for consumption by the data playback platform; the data playback platform may also monitor the business data of the source business end for consumption through the first message queue.

[0070] In an exemplary embodiment of the present disclosure, the business data in the first message queue is sent by a software package configured on the source business end. The software package may be, for example, a software development kit. The software development kit may be based on the SpringBoot starter mechanism, so that it can be quickly integrated into the SpringBoot (a framework that integrates many pluggable components (frameworks) and has built-in usage tools to facilitate developers to quickly build and develop) application. Remote data copying can be achieved at the source business end by calling an interface. When the interface is called, the software package is sent to the data recording platform through the first message queue.

[0071] In the embodiment of sending business data through a software package, since the software package can be developed by itself, the software package can be configured at any location of the source business terminal, so as to obtain any required business data without relying on the business data generated by the source business terminal itself. For example, when a user operates the source business terminal to send a virtual gift, the source business terminal only generates business data of the user's successful / failed sending of the virtual gift, and through the configuration of the software package, it can also send the required business data such as the time when the user browses the virtual gift, the virtual gift selected but not sent, the number of times the virtual gift failed to send, etc. to the data playback platform through the first message queue.

[0072] In the embodiment of sending business data through a software package, since the acquired business data is defined and determined by the software package, it is not necessary to divide the subject of the first message queue according to the scenario of the acquired business data. The subject in the message queue is used to associate the producer of the message and the consumer of the message. Further, the subject of the first message queue in which the software package sends business data can be divided by the data transmission mode to transmit business data of different subjects according to different data transmission modes. In this embodiment, the first message queue is associated with a first type of subject, and the first type of subject includes a first subject and a second subject. The first subject and the second subject are configured with different data transmission modes. The packet loss rate of the data transmission mode configured by the first subject is less than the packet loss rate of the data transmission mode configured by the second subject. For example, the first subject can be configured with a TCP (Transmission Control Protocol) transmission protocol; the second subject can be configured with a UDP (User Datagram Protocol) transmission protocol, and the present disclosure is not limited to this. In other words, the first subject is a high-security data transmission subject, which is used to transmit business data that requires a smaller data packet loss rate; the second subject is a low-security data transmission subject, which is used to transmit business data that requires a higher data transmission speed. Furthermore, considering that in a business scenario, business data with a larger data volume requires a smaller data packet loss rate, so a higher packet loss rate can be allowed, while business data with a smaller data volume requires a larger data packet loss rate, so packet loss is not allowed or the allowed packet loss rate is smaller, thus, the business data can be judged to belong to the first topic or the second topic by the data volume per unit time. For example, the data volume per unit time of the business data of the first topic sent to the first message queue is less than the data volume per unit time of the business data of the second topic sent to the first message queue.

[0073] In an embodiment of sending business data via a software package, in response to the scene going offline or the recording window of the recording plan ending, a data push closing message can be sent to the software package of the source business end. The recording plan can be provided with a recording window. The recording window is used to limit the production / acquisition time of the business data to be stored. The time limit information of the recording window can be used as part of the recording conditions. Thus, when recording is not required, the system load of the source business end can be reduced by closing the push, and the redundancy of the stored business data can be avoided, thereby improving the utilization rate of the business data storage in the database.

[0074] Combine the following Figure 2 , an example of an embodiment of sending service data through a software package is given. For the sake of clarity, Figure 2 In the data playback platform 1, the source service end 10A, the source service end 10B, the source service end 10C, and the software development kit 11 are all equipment / functional modules at the source service; the first configuration center 20, the second configuration center 25, the first message queue 21A and its message distribution component 22, the second message queue 21B and its message distribution component 23, the first message queue 21C and its message distribution component 24 are used to transmit messages between the source service end and the data playback platform 1. The data playback platform 1 includes a message dynamic consumption engine 30, a scene determination unit 31 for scene determination, a recording plan determination unit 32 for determining a recording plan, a business data storage unit 33 for storing business data, a business data acquisition unit 34 for acquiring business data according to playback conditions, and a data playback unit 35 for data playback. The message dynamic consumption engine 30 will be described in detail below. The scene determination unit 31, the recording plan determination unit 32, the business data storage unit 33, the business data acquisition unit 34, and the data playback unit 35 can be implemented by one or more of hardware, software, and firmware. The second message queue 40 and its message distribution component 41 and the second remote service calling interface 42 are used to transmit messages between the data playback platform 1 and the target service end. The target service end 51A, the target service end 51B and the target service end 51C are all equipment / functional modules at the target service. Figure 2 This is merely illustrative and the present application is not limited thereto.

[0075] like Figure 2 As shown, the source business terminal 10A is provided with a software development kit 11. The software development kit 11 is configured via the first configuration center 20 to send the corresponding business data to the first message queue 21A, and the message distribution component 22 transmits the data playback platform 1 in different data transmission modes according to the subject corresponding to the business data, so as to perform the determination of the scene through the scene determination unit 31.

[0076] In an exemplary embodiment of the present disclosure, the business data in the first message queue is obtained by monitoring the data playback platform that executes the data playback method. Figure 1 Before step S110 in the above, it may also include: sending the second category of topics to be monitored by the data playback platform to the configuration center, for the configuration center to send to the message dynamic consumption engine of the data playback platform, the second category of topics includes multiple topics associated with different events, so that the message dynamic consumption engine is automatically registered as a consumer of the second category of topics, so that the message dynamic consumption engine can consume the business data of the second category of topics from the first message queue in real time. The message dynamic consumption engine is a server, multiple servers or a server cluster. Furthermore, when the message dynamic consumption engine has registered a second category of topics, the message dynamic consumption engine can automatically update the registered original second category of topics to the second category of topics. Therefore, through the real-time configuration of the configuration center, there is no need to frequently restart the system when changing the data source, so that the data source can be changed in real time, which greatly improves the efficiency of the system.

[0077] In the embodiment in which the data playback platform monitors and obtains business data, there is no need to perform any change operation on the source business end. At the same time, since the business data monitored by the data playback platform is the event data built into the source business end. In other words, when an event occurs at the source business end, relevant event data will be automatically generated. The data playback platform uses the event data of the existing event by monitoring it as business data. Therefore, the subject of the first message queue can be set according to the existing event at the source business end, so that the data playback platform can monitor it.

[0078] In the embodiment of the data playback platform monitoring and obtaining business data, in response to the scene going offline or the recording window of the recording plan ending, a data monitoring closing message is sent to the message dynamic consumption engine. Thus, when there is no need to record, the system load of the data playback platform can be reduced through the monitoring of the data playback platform, the redundant business data stored can be avoided, and the utilization rate of the business data storage in the database can be improved.

[0079] like Figure 2 and Figure 3 The data playback platform first executes step S111, and sends the second type of topic to be monitored by the data playback platform to the second configuration center 25 according to step 31 determined by the scenario.

[0080] The second configuration center 25 executes step S112 to send the second type of topic to be monitored to the message dynamic consumption engine 30 of the data playback platform.

[0081] The message dynamic consumption engine 30 executes step S113 and automatically registers as a consumer of the second type of topic.

[0082] The message dynamic consumption engine 30 monitors the business data generated by the event triggering of the source business end 10B and the source business end 10C through the first message queue 21B and the first message queue 21C respectively, and the message distribution component 23 of the first message queue 21B and the message distribution component 24 of the first message queue 21C send them to the message dynamic consumption engine 30 according to the corresponding topics and registered consumers, so as to implement step S114 and consume the business data in the second category of topics in the first message queue. Among them, in the message queue, the party that sends messages to the message queue can be called a producer, and the party that obtains messages from the message queue can be called a consumer, so the act of obtaining messages from the message queue can be called consumption.

[0083] Combination Figure 4 In an exemplary embodiment of the present disclosure, the automatic selection of two acquisition methods, software development kit push and platform monitoring, can be achieved through a judgment step.

[0084] Step S201: Determine the topic type.

[0085] Specifically, the configuration center can identify the first category of topics or the second category of topics associated with the business data obtained from the source business end, the first category of topics includes multiple topics associated with different data transmission methods, and the second category of topics includes multiple topics associated with different events. In an optional embodiment, the first configuration center and the second configuration center can be integrated together and used as the same configuration center.

[0086] In response to the business data obtained from the source business end being associated with the first type of topic, it is determined that the business data in the first message queue is sent by a software package configured on the source business end (step S202).

[0087] Step S203: The first configuration center determines whether the scene code associated with the current business data needs to be recorded.

[0088] Step S204, determining whether the acquired business data is the first subject.

[0089] If the judgment in step S204 is yes, step S205 is executed to push the business data to the first topic of the first message queue.

[0090] If the judgment in step S204 is no, step S206 is executed to push the business data to the second topic of the first message queue.

[0091] After step S205 and step S206, step S207 to step S210 are executed.

[0092] In response to the business data obtained from the source business end being associated with the second type of topic, it is determined that the business data in the first message queue is obtained by monitoring by the data playback platform that executes the data playback method (step S203).

[0093] Step S212: The second configuration center determines whether to monitor the topic.

[0094] If the judgment in step S212 is yes, then step S207 is executed to determine the recording plan. The step of determining the recording plan can be performed by Figure 2 The recording plan is determined by the unit 32 in the recording plan determination unit.

[0095] Step S207 may filter the acquired service data according to the recording conditions of the determined recording plan.

[0096] Step S208: label the business data.

[0097] For example, the environment identifier, the corresponding recording plan, the scene code, etc. may be associated with the filtered business data to identify the environment identifier. The environment identifier may include, but is not limited to, one or more of the environment identifiers of the test environment, the production environment, and multiple environments coexisting.

[0098] Step S209, obtaining context information.

[0099] Specifically, step S209 is used to obtain context information of the service data, thereby improving the obtained service data. The context information may be, for example, a message identifier of the service data.

[0100] Step S210, storing the business data in a database. Step S210 can be performed by Figure 2 The business data storage unit 33 is used to execute.

[0101] Specifically, the database may be a relational database such as MySQL, or may be HBase (a distributed, column-oriented open source database), ClickHouse (an open source column-oriented database), or the like.

[0102] Since the present disclosure is mainly for playback of data loss, generally speaking, the timeliness of data is relatively strong, and the time from the discovery of loss to the initiation of repair is relatively short. Therefore, the data implements a data retention policy in the platform. When creating a business scenario, you can specify a fixed retention time, such as 1 day, then the data will be saved in the platform for 1 day and automatically deleted after 1 day. Therefore, a timer can be set in the database for the business data of the corresponding scene / recording plan. When the timer reaches the set time, the corresponding business data is deleted. On the one hand, it can improve the efficiency and stability of the platform. On the other hand, it can avoid unlimited growth of data and reduce storage costs.

[0103] In an exemplary embodiment of the present disclosure, Figure 1 Step S110 in may include: obtaining the business data from the log cleaning results and / or the real-time calculation results of the data stream of the source business end. Specifically, the business data of the source business end can be analyzed through the log cleaning results and / or the real-time calculation results of the data stream to realize big data analysis. Real-time calculation of data stream can be achieved through FLINK (open source stream processing framework). In this embodiment, step S110 can reuse the log cleaning results and / or the real-time calculation results of the data stream of the source business end as the required business data for processing. Thereby, the transformation cost of the data playback platform can be reduced. At the same time, the data obtained through the log cleaning results and / or the real-time calculation results of the data stream is already processed. Therefore, obtaining these data for data playback can also improve the data analysis efficiency of the target business end.

[0104] In an exemplary embodiment of the present disclosure, the target service end calls the second remote service calling interface to obtain the service data. The service data can be obtained by Figure 2 Specifically, the second remote service call interface can be implemented based on the cross-process method call technology used in a distributed environment. For example, the data transmission of the service data obtained from the database can be encapsulated as a second remote service call interface, and the data playback platform can call the remote service call interface to synchronously obtain the service data. Figure 2 In the process, when the target service end 51C has a service data interruption, a playback condition can be generated according to the interruption information, and the second remote service calling interface 42 is called according to the playback scene and playback time to obtain the service data that meets the playback scene and playback time from the database for playback (the playback of service data can be performed by Figure 2 The playback conditions may, for example, limit the playback scene and playback time. The playback of the business data may be performed by the data playback unit 35 shown in the figure) so that the target business terminal 51C performs normal business data analysis and processing based on the played back business data. The playback conditions may, for example, limit the playback scene and playback time. The playback of the business data may be performed by Figure 2 The data playback unit 35 shown is executed.

[0105] In an exemplary embodiment of the present disclosure, the target business end consumes the business data in the second message queue to obtain the business data. The second message queue includes a third topic set by the data playback platform and / or a fourth topic set by the target business end. The third topic set by the data playback platform can be shared by multiple target business ends, without the need for the target business end to set the topic itself. In this embodiment, the scene code can be used as a message tag of the message queue to facilitate filtering of business data by each target business end. The fourth topic set by the target business end is only used by the target business end to meet the playback requirements of the target business end. Thus, the data playback of each target business end can be better isolated through the fourth topic.

[0106] In an exemplary embodiment of the present disclosure, the third theme and / or the fourth theme can be set according to the recording plan. In some embodiments, the third theme and / or the fourth theme are made to completely correspond to the recording plan, so as to facilitate message push from the database. In this embodiment, when the target service end disconnection time is 3 pm, obtain which recording plan the time falls into. When the recording plan includes 8 am to 6 pm and 6 pm to 8 am, the disconnection time falls into the recording plan from 8 am to 6 pm. After obtaining the business data from the theme corresponding to the recording plan (8 am to 6 pm), the playback conditions (after 3 pm) are determined according to the disconnection time, and the obtained business data is filtered according to the playback conditions to obtain the business data to be played back. The present disclosure can implement more variations, which will not be repeated here.

[0107] Combination Figure 2 and Figure 5, when the target business terminal 51A is disconnected, the corresponding topic type is determined according to the configuration of the target business terminal 51A. If the target business terminal 51A corresponds to the third topic, it is determined to consume business data from the third topic (step S302); if the target business terminal 51A corresponds to the fourth topic, it is determined to consume business data from the fourth topic (step S303). Step S304, determine whether to suspend the consumption of business data. If not, execute step S305 to update the consumption progress of the second message queue. Step S306, consume the business data in the second message queue 40 through the message distribution component 41. Step S307, determine whether the playback is completed. In some embodiments, whether the playback is completed can be determined by whether the interruption is restored. For example, when the interruption is restored, the playback is completed; when the interruption is not restored, the playback is not completed. If step S307 is judged as yes, the step is ended. If step S307 is judged as no, return to step S304. In summary, the present invention solves the problems of missing data sources, high complexity of data extraction, poor data timeliness, low repair efficiency, and pure manual repair in traditional data repair solutions by providing a complete set of solutions such as automatic data recording, automatic data expiration management, and automatic data playback. It greatly reduces the cost of data repair and provides strong protection for business data security.

[0108] The above is merely an illustrative example of a specific implementation of the present disclosure, and the present disclosure is not limited thereto.

[0109] Exemplary Devices

[0110] After introducing the data playback method according to the exemplary embodiment of the present disclosure, Figure 6 A data playback device according to an exemplary embodiment of the present disclosure is described.

[0111] refer to Figure 6 As shown, the data playback device 200 of the exemplary embodiment of the present disclosure may include: a business data acquisition module 210, a scene determination module 220, a recording plan determination module 230, a recording storage module 240, a playback condition generation module 250, a playback object determination module 260, a playback data acquisition module 270 and a data playback module 280. Among them,

[0112] The business data acquisition module 210 may be used to acquire business data from a source business terminal, the business data being associated with a scenario code, the business data being automatically sent to a target business terminal associated with the scenario code for business data analysis, and the data analysis result being used to feed back to the source business terminal;

[0113] The scene determination module 220 may be used to determine the scene to which the service data belongs according to the scene code, wherein the scene includes one or more recording plans, each of which has a preset recording condition;

[0114] The recording plan determination module 230 may be used to determine the recording plan to which the service data belongs according to the recording condition;

[0115] The recording storage module 240 can be used to store the business data in association with the recording plan in a database.

[0116] The playback condition generating module 250 may be used to generate a playback condition according to the service data interruption information in response to the service data interruption from the source service end to the target service end;

[0117] The playback object determination module 260 may be used to determine the scene code required for playback and its recording plan according to the playback condition;

[0118] The playback data acquisition module 270 may be used to acquire business data from the database according to the determined scene code and its recording plan;

[0119] The data playback module 280 may be used to send the acquired service data to the target service end for data playback.

[0120] According to an exemplary embodiment of the present disclosure, the early warning rules include fixed rules and / or dynamic rules, the rule parameters of the fixed rules are fixed parameters, and the rule parameters of the dynamic rules are dynamically set according to the inventory change data / sales data of the inventory quantity unit associated with the dynamic rule and the unit time of the channel associated with the dynamic rule, and the rule parameters are used for comparison with the changed inventory data.

[0121] According to an exemplary embodiment of the present disclosure, the business data acquisition module includes:

[0122] A first remote call acquisition module is used to synchronously acquire service data from the source service end through a first remote service call interface; or

[0123] The first message queue acquisition module is used to asynchronously acquire service data from the source service end through the first message queue.

[0124] According to an exemplary embodiment of the present disclosure, the first message queue acquisition module includes:

[0125] A configuration center control module, used for identifying, through the configuration center, that the business data obtained from the source business terminal is associated with a first category of topics or a second category of topics, wherein the first category of topics includes a plurality of topics associated with different data transmission modes, and the second category of topics includes a plurality of topics associated with different events;

[0126] A first topic association module, configured to, in response to associating the service data obtained from the source service end with the first type of topic, determine that the service data in the first message queue is sent by a software package configured on the source service end, and store the service data in a first message queue associated with the first type of topic;

[0127] A second topic association module is used to associate the second type of topic in response to the business data obtained from the source business end, determine that the business data in the first message queue is obtained by monitoring the data playback platform that executes the data playback method, and store the business data in the first message queue associated with the second type of topic.

[0128] According to an exemplary embodiment of the present disclosure, the business data in the first message queue is sent by a software package configured on the source business end, the first message queue is associated with a first category of topics, the first category of topics includes a first topic and a second topic, the first topic and the second topic are configured with different data transmission methods, and the packet loss rate of the data transmission method configured for the first topic is less than the packet loss rate of the data transmission method configured for the second topic.

[0129] According to an exemplary embodiment of the present disclosure, the data volume per unit time of the business data sent to the first topic of the first message queue is smaller than the data volume per unit time of the business data sent to the second topic of the first message queue.

[0130] According to an exemplary embodiment of the present disclosure, it further includes:

[0131] The push closing module is used to send a data push closing message to the source service end in response to the scene going offline or the recording window of the recording plan ending.

[0132] According to an exemplary embodiment of the present disclosure, the business data in the first message queue is obtained by monitoring the data playback platform that executes the data playback method, and the data playback device further includes:

[0133] A second topic sending module, used to send the second type of topic to be monitored by the data playback platform to the configuration center, so that the configuration center can send it to the message dynamic consumption engine of the data playback platform, wherein the second type of topic includes multiple topics associated with different events;

[0134] A registration module is used to enable the dynamic message consumption engine to automatically register as a consumer of the second type of topic, so that the dynamic message consumption engine can consume the business data of the second type of topic from the first message queue in real time.

[0135] According to an exemplary embodiment of the present disclosure, the registration module includes:

[0136] The registration update module is used for the message dynamic consumption engine to automatically update the registered original second-category topic to the second-category topic.

[0137] According to an exemplary embodiment of the present disclosure, it further includes:

[0138] The monitoring closing module is used to send a data monitoring closing message to the message dynamic consumption engine in response to the scene going offline or the recording window of the recording plan ending.

[0139] According to an exemplary embodiment of the present disclosure, the business data acquisition module includes:

[0140] A processing business data acquisition module is used to obtain the business data from the log cleaning results and / or data flow real-time calculation results of the source business end.

[0141] According to an exemplary embodiment of the present disclosure, the recording storage module further includes:

[0142] A context acquisition module, which acquires context information of the business data;

[0143] The context storage module stores the context information of the business data in the database.

[0144] According to an exemplary embodiment of the present disclosure, the target service end calls the second remote service calling interface to obtain the service data: or

[0145] The target service end consumes the service data in the second message queue to obtain the service data.

[0146] According to an exemplary embodiment of the present disclosure, the second message queue includes a third topic set by the data playback platform and / or a fourth topic set by the target business end.

[0147] According to an exemplary embodiment of the present disclosure, the third theme and / or the fourth theme are set according to the recording plan.

[0148] Since the functional modules of the data playback device in the disclosed embodiment are the same as those in the disclosed embodiment of the data playback method, they will not be described in detail here.

[0149] Exemplary Storage Media

[0150] After introducing the data playback method, device and system according to the exemplary embodiments of the present disclosure, Figure 7 A storage medium according to an exemplary embodiment of the present disclosure is described.

[0151] refer to Figure 7As shown, a program product 1000 for implementing the above method according to an embodiment of the present disclosure is described, which can adopt a portable compact disk read-only memory (CD-ROM) and include program code, and can be run on a device, such as a personal computer. However, the program product of the present disclosure is not limited thereto. In this document, a readable storage medium can be any tangible medium containing or storing a program, which can be used by or in combination with an instruction execution system, an apparatus or a device.

[0152] The program product may use any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0153] Computer readable signal media may include data signals propagated in baseband or as part of a carrier wave, in which readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Readable signal media may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0154] The program code embodied on the readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.

[0155] Program code for performing the operations of the present disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user computing device, partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., using an Internet service provider to connect through the Internet).

[0156] Exemplary Electronic Devices

[0157] After introducing the storage medium of the exemplary embodiment of the present disclosure, next, reference is made to Figure 8 An electronic device according to an exemplary embodiment of the present disclosure is described.

[0158] Figure 8 The electronic device 800 shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0159] like Figure 8 As shown, the electronic device 800 is in the form of a general computing device. The components of the electronic device 800 may include, but are not limited to: the at least one processing unit 810, the at least one storage unit 820, a bus 830 connecting different system components (including the storage unit 820 and the processing unit 810), and a display unit 840.

[0160] The storage unit stores program codes, which can be executed by the processing unit 810, so that the processing unit 810 performs the steps according to various exemplary embodiments of the present invention described in the above "Exemplary Method" section of this specification. For example, the processing unit 810 can perform the following steps: Figure 1 Follow the steps shown in .

[0161] The storage unit 820 may include a volatile storage unit, such as a random access storage unit (RAM) 8201 and / or a cache storage unit 8202 , and may further include a read-only storage unit (ROM) 8203 .

[0162] The storage unit 820 may also include a program / utility 8204 having a set (at least one) of program modules 8205, such program modules 8205 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0163] The bus 830 may include a data bus, an address bus, and a control bus.

[0164] The electronic device 800 can also communicate with one or more external devices 900 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), and this communication can be performed through an input / output (I / O) interface 850. The electronic device 800 also includes a display unit 840, which is connected to the input / output (I / O) interface 850 for display. In addition, the electronic device 800 can also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs) and / or public networks, such as the Internet) through a network adapter 860. As shown in the figure, the network adapter 860 communicates with other modules of the electronic device 800 through a bus 830. It should be understood that, although not shown in the figure, other hardware and / or software modules can be used in conjunction with the electronic device 800, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, etc.

[0165] It should be noted that, although several modules or submodules of the data playback device and the data playback system are mentioned in the above detailed description, such division is merely exemplary and not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more units / modules described above can be embodied in one unit / module. Conversely, the features and functions of one unit / module described above can be further divided into multiple units / modules for embodiment.

[0166] In addition, although the operations of the disclosed method are described in a specific order in the drawings, this does not require or imply that the operations must be performed in this specific order, or that all the operations shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps.

[0167] Although the spirit and principle of the present invention have been described with reference to several specific embodiments, it should be understood that the present invention is not limited to the disclosed specific embodiments, and the division of various aspects does not mean that the features in these aspects cannot be combined to benefit, and such division is only for the convenience of expression. The present invention is intended to cover various modifications and equivalent arrangements included in the spirit and scope of the attached claims.

Claims

1. A data playback method, characterized in that: include: Acquire business data from a source business terminal, the business data is associated with a scenario code, the business data is automatically sent to a target business terminal associated with the scenario code for business data analysis, and the data analysis result is used to feed back to the source business terminal; Determine the scene to which the service data belongs according to the scene code, where the scene includes one or more recording plans, and each recording plan is preset with recording conditions; Determining the recording plan to which the business data belongs according to the recording condition; storing the business data in association with the recording plan in a database; In response to a service data interruption from the source service end to the target service end, generating a playback condition according to service data interruption information; Determine the scene code and recording plan required for playback according to the playback condition; Acquiring service data from the database according to the determined scene code and its recording plan; The acquired business data is sent to the target business end for data playback.

2. The data playback method according to claim 1, characterized in that: The obtaining of service data from the source service end includes: Synchronously acquiring service data from the source service end through a first remote service calling interface; or The service data is asynchronously obtained from the source service end through the first message queue.

3. The data playback method according to claim 2, characterized in that: The asynchronously acquiring service data from the source service end through the first message queue includes: Identify, by the configuration center, that the business data obtained from the source business terminal is associated with a first category of topics or a second category of topics, wherein the first category of topics includes multiple topics associated with different data transmission modes, and the second category of topics includes multiple topics associated with different events; In response to the business data obtained from the source business terminal being associated with the first category of topics, determining that the business data in the first message queue is sent by a software package configured on the source business terminal, and storing the business data in the first message queue associated with the first category of topics; In response to the business data obtained from the source business end being associated with the second type of topic, it is determined that the business data in the first message queue is obtained by monitoring the data playback platform that executes the data playback method, and the business data is stored in the first message queue associated with the second type of topic.

4. The data playback method according to claim 2, characterized in that: The business data in the first message queue is sent by a software package configured on the source business end. The first message queue is associated with a first category of topics. The first category of topics includes a first topic and a second topic. The first topic and the second topic are configured with different data transmission methods. The packet loss rate of the data transmission method configured for the first topic is less than the packet loss rate of the data transmission method configured for the second topic.

5. The data playback method according to claim 4, characterized in that: The data volume per unit time of the business data sent to the first topic of the first message queue is smaller than the data volume per unit time of the business data sent to the second topic of the first message queue.

6. The data playback method according to claim 4, characterized in that: Also includes: In response to the scene going offline or the recording window of the recording plan ending, a data push closing message is sent to the source service end.

7. The data playback method according to claim 2, characterized in that: The business data in the first message queue is obtained by monitoring the data playback platform executing the data playback method, and the process of obtaining the business data from the source business terminal includes: Sending the second type of topics to be monitored by the data playback platform to the configuration center, so that the configuration center can send them to the message dynamic consumption engine of the data playback platform, wherein the second type of topics includes multiple topics associated with different events; The dynamic message consumption engine is automatically registered as a consumer of the second type of topic, so that the dynamic message consumption engine can consume the business data of the second type of topic from the first message queue in real time.

8. The data playback method according to claim 7, characterized in that: The step of automatically registering the message dynamic consumption engine as a consumer of the second type of topic includes: The message dynamic consumption engine automatically updates the registered original second-category topic to the second-category topic.

9. The data playback method according to claim 7, characterized in that: Also includes: In response to the scene going offline or the recording window of the recording plan ending, a data monitoring closing message is sent to the message dynamic consumption engine.

10. The data playback method according to claim 1, characterized in that: The obtaining of service data from the source service end includes: The business data is obtained from the log cleaning results and / or data flow real-time calculation results of the source business end.

11. The data playback method according to claim 1, characterized in that: The storing the business data in association with the recording plan in a database further includes: Acquiring context information of the business data; The context information of the business data is stored in the database.

12. The data playback method according to claim 1, characterized in that: The target service end calls the second remote service calling interface to obtain the service data: or The target service end consumes the service data in the second message queue to obtain the service data.

13. The data playback method according to claim 12, characterized in that: The second message queue includes a third topic set by the data playback platform and / or a fourth topic set by the target business end.

14. The data playback method according to claim 13, characterized in that: The third theme and / or the fourth theme are set according to the recording plan.

15. A data playback device, characterized in that: include: A business data acquisition module is used to acquire business data from a source business terminal, the business data is associated with a scenario code, the business data is automatically sent to a target business terminal associated with the scenario code for business data analysis, and the data analysis result is used to feed back to the source business terminal; A scene determination module, used to determine the scene to which the service data belongs according to the scene code, wherein the scene includes one or more recording plans, each of which has a preset recording condition; A recording plan determination module, used to determine the recording plan to which the business data belongs according to the recording condition; A recording storage module is used to store the business data in association with the recording plan in a database, A playback condition generating module, configured to generate a playback condition according to the service data interruption information in response to the service data interruption from the source service end to the target service end; A playback object determination module, used to determine the scene code required for playback and its recording plan according to the playback conditions; A playback data acquisition module, used to acquire business data from the database according to the determined scene code and its recording plan; The data playback module is used to send the acquired business data to the target business end for data playback.

16. The data playback device according to claim 15, characterized in that: The business data acquisition module includes: A first remote call acquisition module is used to synchronously acquire service data from the source service end through a first remote service call interface; or The first message queue acquisition module is used to asynchronously acquire service data from the source service end through the first message queue.

17. The data playback device according to claim 16, characterized in that: The first message queue acquisition module includes: A configuration center control module, used for identifying, through the configuration center, that the business data obtained from the source business terminal is associated with a first category of topics or a second category of topics, wherein the first category of topics includes a plurality of topics associated with different data transmission modes, and the second category of topics includes a plurality of topics associated with different events; A first topic association module, configured to, in response to associating the service data obtained from the source service end with the first type of topic, determine that the service data in the first message queue is sent by a software package configured on the source service end, and store the service data in a first message queue associated with the first type of topic; A second topic association module is used to associate the second type of topic in response to the business data obtained from the source business end, determine that the business data in the first message queue is obtained by monitoring the data playback platform that executes the data playback method, and store the business data in the first message queue associated with the second type of topic.

18. The data playback device according to claim 16, characterized in that: The business data in the first message queue is sent by a software package configured on the source business end. The first message queue is associated with a first category of topics. The first category of topics includes a first topic and a second topic. The first topic and the second topic are configured with different data transmission methods. The packet loss rate of the data transmission method configured for the first topic is less than the packet loss rate of the data transmission method configured for the second topic.

19. The data playback device according to claim 18, characterized in that: The data volume per unit time of the business data sent to the first topic of the first message queue is smaller than the data volume per unit time of the business data sent to the second topic of the first message queue.

20. The data playback device according to claim 18, characterized in that: Also includes: The push closing module is used to send a data push closing message to the source service end in response to the scene going offline or the recording window of the recording plan ending.

21. The data playback device according to claim 16, characterized in that: The business data in the first message queue is obtained by monitoring the data playback platform executing the data playback method, and the data playback device further includes: A second topic sending module, used to send the second type of topic to be monitored by the data playback platform to the configuration center, so that the configuration center can send it to the message dynamic consumption engine of the data playback platform, wherein the second type of topic includes multiple topics associated with different events; A registration module is used to enable the dynamic message consumption engine to automatically register as a consumer of the second type of topic, so that the dynamic message consumption engine can consume the business data of the second type of topic from the first message queue in real time.

22. The data playback device according to claim 21, characterized in that: The registration module includes: The registration update module is used for the message dynamic consumption engine to automatically update the registered original second-category topic to the second-category topic.

23. The data playback device according to claim 21, characterized in that: Also includes: The monitoring closing module is used to send a data monitoring closing message to the message dynamic consumption engine in response to the scene going offline or the recording window of the recording plan ending.

24. The data playback device according to claim 15, characterized in that: The business data acquisition module includes: A processing business data acquisition module is used to obtain the business data from the log cleaning results and / or data flow real-time calculation results of the source business end.

25. The data playback device according to claim 15, characterized in that: The recording storage module also includes: A context acquisition module, which acquires context information of the business data; The context storage module stores the context information of the business data in the database.

26. The data playback device according to claim 15, characterized in that: The target service end calls the second remote service calling interface to obtain the service data: or The target service end consumes the service data in the second message queue to obtain the service data.

27. The data playback device according to claim 26, characterized in that: The second message queue includes a third topic set by the data playback platform and / or a fourth topic set by the target business end.

28. The data playback method according to claim 27, characterized in that: The third theme and / or the fourth theme are set according to the recording plan.

29. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, it realizes: The data playback method according to any one of claims 1 to 14.

30. An electronic device, characterized in that: include: processor; as well as A memory, configured to store executable instructions of the processor; The processor is configured to perform, via executing the executable instructions: The data playback method according to any one of claims 1 to 14.

Images