Live Data Service Exception Handling via Display Rate Adjustment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data live broadcast technologies experience jumps and rollbacks when exceptions occur in live data services, leading to disruptions in real-time data display, as the backup service clears and reprocesses buffered data, causing inconsistencies and affecting user experience.
Innovation Solution
A method and device that monitor the running status of live data services, calculate a predicted recovery duration, and adjust the display rate of live data on terminal devices based on this duration, allowing for controlled display and enabling sufficient time for troubleshooting without clearing buffered data, thus preventing rollbacks and jumps.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the server switches to a backup live data service when an exception occurs, then the service reliability is improved, but data consistency deteriorates causing rollbacks and jumps
Solution Approach 1:
The system pre-calculates and stores historical statistics data in advance. When an exception occurs and the backup service is activated, the terminal device can directly display the pre-calculated historical statistics data without requiring the backup service to reprocess raw data, thereby avoiding data rollbacks and maintaining consistency.
Solution Approach 2:
The terminal device maintains a local copy of historical statistics data. When switching from the original live data service to the backup service, the terminal device continues to display the local copy, avoiding the need to immediately fetch new data from the backup service and preventing data jumps or rollbacks.
2Reliability
If the backup live data service reprocesses buffered data, then the service reliability is improved, but the loss of time increases due to repeated statistics processing
Solution Approach 1:
The system pre-calculates and stores historical statistics data in advance. When the backup service is activated, it can directly provide the pre-calculated historical statistics data without reprocessing the raw buffered data, significantly reducing the time loss associated with repeated statistics processing.
Solution Approach 2:
Instead of discarding and reprocessing the buffered data, the system recovers and reuses the pre-calculated historical statistics data. This approach eliminates the need to reprocess the same data, thereby reducing time loss while maintaining service reliability.
3Reliability
If the live data service clears buffered data after an exception, then the service reliability is improved, but the loss of information increases causing data jumps
Solution Approach 1:
The terminal device maintains a local copy of historical statistics data. When the live data service clears its buffer after an exception, the terminal device continues to display the local copy, preventing data jumps and maintaining information continuity from the user's perspective.
Solution Approach 2:
The system pre-calculates and stores historical statistics data before exceptions occur. This preliminary action ensures that even if the server clears its buffer, the terminal device has access to the pre-calculated data, preventing information loss and data jumps.
Data Source
Figure 1a~1c
Figure 2a~2b
Figure 2c~2d
AI summary
The present application discloses a method and a device for processing data. The method includes the following: monitoring, by a server, a running status of a live data service; determining predicted recovery time when it is detected that an exception occurs in the running status; calculating a first rate based on the predicted recovery time; and sending the calculated first rate to a terminal device, so that the terminal device displays live data based on the first rate. In this method, when an exception occurs in the live data service on the server, the server can decrease a current display rate of the terminal device, and prolong troubleshooting or recovery time of the back end staff, without making an end user significantly aware of a change such as a jump, a rollback, or stagnancy of the live data. Correspondingly, after the live data service is recovered, the display rate of the terminal device can be increased, so that the terminal device can adapt to new live data sent by the server.