System for asynchronously and incrementally playing back station yard state based on cloud service

Abstract

The invention provides a system for asynchronous incremental playback of a station yard state based on cloud service, and the system comprises a cloud server which is used for obtaining the operation state data of all devices in a station yard, generating a first data packet according to the operation state data of all devices in the station yard, and transmitting the first data packet to a server; a first frame of the first data packet comprises the operation states of all devices in the station yard, and other frames comprise the operation states of the devices of which the states are changed in the station yard; and the client is used for receiving the first data packet and replaying the operation states of all equipment in the station according to the first data packet. According to the system, the operation state data of all devices in the station are packaged into the first data packet, and during packaging, except the first frame is full data, the other frames are incremental data, so that the volume of the data packet can be greatly reduced; and during playback, data transmission is performed by taking the first data packet as a basic unit, so that normal playback can be ensured, and the transmission of the first data packet is reduced as much as possible.

Description

Technical Field

[0001] The present invention relates to the technical field of intelligent operation and maintenance of railway signal interlocking, and in particular to a system for asynchronous incremental playback of station status based on cloud services. Background Art

[0002] In railway yards, the operating status data of sections, tracks, switches and other equipment will be recorded by the interlocking system. The intelligent operation and maintenance system needs to obtain these operating status data and play them in real time to display the operating status of the equipment in the entire yard, so that users can fully understand the status of the entire yard. For historical operating status data, the intelligent operation and maintenance system also needs to support playback at a specified time and speed, so that managers or operators can play back to find and confirm yard operations, equipment status and fault conditions within a specific time.

[0003] However, under the daily working conditions of the station, the status of each device in the station does not change very frequently. The data packets of the station status obtained by the intelligent operation and maintenance system, the data in the previous and next packets, are almost the same because there is no change in the status of the equipment. Even if the status of the equipment changes, the data in the data packet is the same except for the data of the changed equipment.

[0004] A large amount of unchanged data in the data packet will occupy the bandwidth of the data channel, affecting the upper limit of the number of stations that the system can process simultaneously; at the same time, when playing back the station data, the selection of a large playback time interval and a fast playback rate will be greatly affected. Summary of the invention

[0005] In view of the above defects of the prior art, the present invention provides a system for asynchronous incremental playback of station status based on cloud services to solve the technical problem of large amount of data occupying data channel bandwidth when playing back station data.

[0006] To achieve the above-mentioned purpose and other related purposes, the present invention provides a system for asynchronous incremental playback of station status based on cloud services, including: a cloud server, used to obtain the operating status data of all equipment in the station, and generate a first data packet based on the operating status data of all equipment in the station, the first frame of the first data packet contains the operating status of all equipment in the station, and other frames contain the operating status of equipment whose status has changed in the station; and a client, used to receive the first data packet and play back the operating status of all equipment in the station according to the first data packet.

[0007] In an embodiment of the present invention, the start and end time span of the first data packet is 1 to 10 minutes.

[0008] In one embodiment of the present invention, the client is also used to obtain the start and end time of the first data packet, write the first data packet into a data content file, and write the mapping relationship between the storage location of the first data packet and the start and end time of the first data packet into a primary key mapping file.

[0009] In one embodiment of the present invention, the client is also used to receive a user's playback request; and according to the playback period in the playback request and the primary key mapping file, obtain a target data packet corresponding to the playback period from the data content file and / or the cloud server, and replay the operating status of all equipment in the station according to the target data packet.

[0010] In one embodiment of the present invention, according to the playback time period in the playback request and the primary key mapping file, a target data packet corresponding to the playback time period is obtained from the data content file and / or the cloud server, including: obtaining the playback time period according to the user's playback request; obtaining the start and end time of all first data packets saved in the data content file according to the primary key mapping file; and obtaining the target data packet corresponding to the playback time period from the data content file and / or the cloud server according to the start and end time of all first data packets saved in the data content file.

[0011] In one embodiment of the present invention, according to the start and end times of all the first data packets saved in the data content file, the target data packet corresponding to the playback time period is obtained from the data content file and / or the cloud server, including: according to the start and end times of all the first data packets saved in the data content file, determining whether the data content file stores all the first data packets corresponding to the playback time period; if so, obtaining all the first data packets corresponding to the playback time period from the data content file as the target data packet; if not, obtaining all the first data packets corresponding to the playback time period from the cloud server as the target data packet.

[0012] In one embodiment of the present invention, all the first data packets corresponding to the playback period are obtained from the cloud server as the target data packets, including: determining whether the data content file stores part of the first data packets corresponding to the playback period: if not, obtaining all the first data packets corresponding to the playback period from the cloud server as the target data packets; if yes, obtaining all the first data packets corresponding to the playback period from the data content file and the cloud server as the target data packets.

[0013] In one embodiment of the present invention, all the first data packets corresponding to the playback period are obtained from the data content file and the cloud server as the target data packet, including: dividing the playback period into a first period and a second period according to the start and end times of all the first data packets saved in the data content file, the first period being included in the start and end times of all the first data packets saved in the data content file, and the second period being not included in the start and end times of all the first data packets saved in the data content file; obtaining the first data packet corresponding to the first period from the data content file; obtaining the first data packet corresponding to the second period from the cloud server; and using the first data packet corresponding to the first period and the first data packet corresponding to the second period as the target data packet.

[0014] In one embodiment of the present invention, the cloud server sends the first data packet to the client according to the following steps: obtain a request period according to the request sent by the client; obtain the first first data packet according to the start time of the request period; obtain the last first data packet according to the end time of the request period; and send the first first data packet, the last first data packet, and all other first data packets in between to the client together.

[0015] In one embodiment of the present invention, according to the request sent by the client, the request time period is obtained, including: according to the request sent by the client, determining whether the requesting user needs to be limited: if yes, not sending the first data packet and returning a failure message; if no, obtaining the request time period.

[0016] Beneficial effects of the present invention: The present invention proposes a system for asynchronous incremental playback of station status based on cloud services. The system packages the operating status data of all equipment in the station into a first data packet, and when packaging, except for the first frame which is full data, the remaining frames are incremental data, which can greatly reduce the size of the data packet; during playback, data is transmitted with the first data packet as the basic unit, ensuring normal playback while minimizing the transmission of the first data packet. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0018] Figure 1 A schematic diagram of a structure provided for an embodiment of the present invention;

[0019] Figure 2 A processing flow after a client receives a first data packet is provided in an embodiment of the present invention.

[0020] Description of reference numerals: 100, cloud server; 200, client. DETAILED DESCRIPTION

[0021] The following describes the embodiments of the present invention through specific specific embodiments, and those skilled in the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. It should be noted that the following embodiments and the features in the embodiments can be combined with each other without conflict. In addition to the specific methods, equipment, and materials used in the embodiments, according to the technical personnel in this technical field's grasp of the prior art and the records of the present invention, any methods, equipment, and materials of the prior art that are similar or equivalent to the methods, equipment, and materials described in the embodiments of the present invention can also be used to implement the present invention.

[0022] It should be understood that the terms used in the embodiments of the present invention are for describing specific embodiments rather than for limiting the scope of protection of the present invention. Unless otherwise defined, all technical and scientific terms used in the present invention have the same meaning as those generally understood by those skilled in the art.

[0023] In the following description, numerous details are discussed to provide a more thorough explanation of the embodiments of the present invention. However, it is obvious to those skilled in the art that the embodiments of the present invention can be implemented without these specific details. In some of the embodiments, well-known structures and devices are shown in the form of block diagrams rather than in detail to avoid making the embodiments of the present invention difficult to understand.

[0024] The flowchart and block diagram in the accompanying drawings illustrate the system architecture, functions and operations that may be implemented according to the methods and computer program products of various embodiments disclosed in the present invention. In this regard, each box in the flowchart or block diagram can represent a module, a program segment, or a part of a code, and the module, the program segment, or a part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or the flowchart, and the combination of the boxes in the block diagram and / or the flowchart can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0025] See also Figure 1 and Figure 2 , Figure 1 and Figure 2 A system for asynchronous incremental playback of station status based on cloud services provided in one embodiment of the present invention includes a cloud server 100 and a client 200, wherein the cloud server 100 is used to obtain the operating status data of all equipment in the station, and generate a first data packet according to the operating status data of all equipment in the station, wherein the first frame of the first data packet contains the operating status of all equipment in the station, and the other frames contain the operating status of equipment whose status has changed in the station; the client 200 is used to receive the first data packet, and play back the operating status of all equipment in the station according to the first data packet.

[0026] The system packages the operating status data of all equipment in the station into the first data packet. When packaging, except for the first frame which is full data, the remaining frames are all incremental data. The frame containing the full data can be called the full frame, and the frame containing the incremental data can be called the incremental frame. This can greatly reduce the size of the data packet. By adopting the cloud playback decoding method, the encoding compression ratio can be as high as 1:100. The larger the station, the higher the compression ratio, up to 1:200. During playback, the first data packet is used as the basic unit for data transmission to ensure normal playback while minimizing the transmission of the first data packet. The meaning of this sentence can also be understood as: when the data packet is packaged, if each frame contains the operating status data of all equipment, then during playback, the frame corresponding to the playback period can be directly played, but this will make the amount of data transmitted extremely large; if only the incremental frame is transmitted, it is difficult to obtain the full data corresponding to the start time of the playback period during playback, so normal playback cannot be performed.

[0027] In a specific embodiment of the present invention, when the cloud server 100 packages the operating status data of all equipment in the station, each first data packet should contain a start time and an end time, which can be collectively referred to as the start and end time. For incremental frames, if the status of each device in a certain incremental frame has not changed compared to the previous frame, only the frame time needs to be filled in to indicate no state update. When packaging, the time span of each first data packet can be customized, for example, it can be set to 1 to 10 minutes. The specific time selection can be determined according to the status changes of all equipment in the station. In this embodiment, for example, 5 minutes can be selected. When the cloud server 100 is packaging, each frame in the first data packet is sequential and continuous, and the time interval between two adjacent frames can also be customized.

[0028] In a specific embodiment of the present invention, the client 200 is also used to obtain the start and end time of the first data packet, write the first data packet into a data content file, and write the mapping relationship between the storage location of the first data packet and the start and end time of the first data packet into a master key mapping file. When the client 200 plays back and displays the received first data packet, it may be limited by the network and may cause a freeze, which affects the playback effect. Therefore, in this embodiment, a data content file and a master key mapping file are set in the client 200 to save some recently transmitted data packets, for example, the first data packets of the last three days can be saved. In this way, when there is a need for playback, the client 200 can directly read the first data packet corresponding to the playback period based on these two files. Since it is read locally, there will be no freeze during playback.

[0029] Before writing the data content file and the primary key mapping file, the two files need to be created first. For example, a data content file and a primary key mapping file may be created for each station every day, and then the first received data packet is written into the two files.

[0030] In a specific embodiment of the present invention, the client 200 is also used to receive a playback request from a user, and the playback request includes at least a playback period, and in addition, other data such as a playback rate. The client 200 also obtains a target data packet corresponding to the playback period from the data content file and / or the cloud server according to the playback period in the playback request and the primary key mapping file, and replays the operating status of all devices in the station according to the target data packet. Since the cloud server 100 stores all first data packets, and the data content file only stores the most recent first data packet, during playback, it is necessary to determine where to obtain the corresponding first data packet based on the specific playback period.

[0031] In a specific embodiment of the present invention, according to the playback period in the playback request and the primary key mapping file, the target data packet corresponding to the playback period is obtained from the data content file and / or the cloud server, including: obtaining the playback period according to the user's playback request; obtaining the start and end time of all the first data packets saved in the data content file according to the primary key mapping file; obtaining the target data packet corresponding to the playback period from the data content file and / or the cloud server according to the start and end time of all the first data packets saved in the data content file. The start and end time of all the first data packets saved in the data content file corresponds to the span time of all the first data packets saved locally by the client 200. By comparing this time with the playback period, it can be determined whether the target data packet during playback is read locally from the client 200 or obtained from the cloud server 100.

[0032] In a specific embodiment of the present invention, according to the start and end times of all first data packets stored in the data content file, the target data packet corresponding to the playback period is obtained from the data content file and / or the cloud server, including: according to the start and end times of all first data packets stored in the data content file, judging whether the data content file stores all first data packets corresponding to the playback period; if yes, obtaining all first data packets corresponding to the playback period from the data content file as the target data packet; if not, obtaining all first data packets corresponding to the playback period from the cloud server 100 as the target data packet. In this embodiment, if the data content file of the client 200 contains all first data packets corresponding to the playback period, the corresponding content can be directly read from the data content file for playback; otherwise, it is necessary to obtain the target data packet for playback from the cloud server 100.

[0033] In a specific embodiment of the present invention, all first data packets corresponding to the playback period are obtained from the cloud server 100 as target data packets, including: determining whether the data content file stores part of the first data packets corresponding to the playback period: if not, all first data packets corresponding to the playback period are obtained from the cloud server 100 as target data packets; if yes, all first data packets corresponding to the playback period are obtained from the data content file and the cloud server 100 as target data packets. When it is necessary to obtain the first data packet from the cloud server 100, there are two situations: one is that the playback period is relatively early, and the start and end times of all first data packets stored in the data content file do not intersect with the playback period. At this time, all first data packets corresponding to the playback period need to be obtained from the cloud server 100; the other is that the start and end times intersect with the playback period. At this time, it is necessary to obtain the first data packets in the data content file and the cloud server 100 at the same time as the target data packet.

[0034] In a specific embodiment of the present invention, all first data packets corresponding to the playback period are obtained from the data content file and the cloud server 100 as target data packets, including: dividing the playback period into a first period and a second period according to the start and end times of all first data packets saved in the data content file, the first period being included in the start and end times of all first data packets saved in the data content file, and the second period not being included in the start and end times of all first data packets saved in the data content file; obtaining the first data packet corresponding to the first period from the data content file; obtaining the first data packet corresponding to the second period from the cloud server 100; and using the first data packet corresponding to the first period and the first data packet corresponding to the second period as target data packets. In this embodiment, the playback period is divided into the first period and the second period, so that it can be more accurately determined which first data packets need to be obtained from the data content file and which first data packets need to be obtained from the cloud server 100.

[0035] In a specific embodiment of the present invention, the cloud server 100 sends the first data packet to the client 200 according to the following steps: according to the request sent by the client 200, obtain the request period; according to the start time of the request period, obtain the first first data packet; according to the end time of the request period, obtain the last first data packet; send the first first data packet, the last first data packet, and all other first data packets between the two to the client 200. In the above request period, if the data content file stores part of the first data packets corresponding to the playback period, then the request period is equivalent to the second period; if the data content file does not include any first data packet corresponding to the playback period, then the request period is equivalent to the playback period.

[0036] In a specific embodiment of the present invention, according to the request sent by the client 200, the request period is obtained, including: according to the request sent by the client 200, determining whether the request user needs to limit the flow: if yes, not sending the first data packet and returning a failure message; if no, obtaining the request period. Since the amount of site playback data is very large, considering the performance of the cloud server 100 and network IO and other limiting factors, it is necessary to perform flow limiting processing on the interface to prevent a large number of instantaneous requests from overwhelming the cloud server 100.

[0037] The above embodiments are merely illustrative of the principles and effects of the present invention, and are not intended to limit the present invention. Anyone familiar with the art may modify or alter the above embodiments without departing from the spirit and scope of the present invention. Therefore, all equivalent modifications or alterations made by a person of ordinary skill in the art without departing from the spirit and technical concept disclosed by the present invention shall still be covered by the claims of the present invention.

Claims

1. A system for asynchronous incremental playback of station status based on cloud services, characterized in that: include: The cloud server is used to obtain the operating status data of all the equipment in the station, and generate a first data packet according to the operating status data of all the equipment in the station, wherein the first frame of the first data packet contains the operating status of all the equipment in the station, and the other frames contain the operating status of the equipment whose status has changed in the station; as well as The client is used to receive the first data packet and replay the operating status of all devices in the station according to the first data packet.

2. The system for asynchronous incremental playback of station status based on cloud services according to claim 1, characterized in that: The start and end time span of the first data packet is 1 to 10 minutes.

3. The system for asynchronous incremental playback of station status based on cloud services according to claim 1, characterized in that: The client is also used to obtain the start and end time of the first data packet, write the first data packet into a data content file, and write a mapping relationship between the storage location of the first data packet and the start and end time of the first data packet into a primary key mapping file.

4. The system for asynchronous incremental playback of station status based on cloud services according to claim 3, characterized in that: The client is also used to receive a user's playback request; and according to the playback period in the playback request and the primary key mapping file, obtain a target data packet corresponding to the playback period from the data content file and / or the cloud server, and replay the operating status of all devices in the station according to the target data packet.

5. The system for asynchronous incremental playback of station status based on cloud services according to claim 4, characterized in that: According to the playback period in the playback request and the primary key mapping file, a target data packet corresponding to the playback period is obtained from the data content file and / or the cloud server, and the operating status of all devices in the station is replayed according to the target data packet, including: According to the playback request of the user, obtaining the playback period; According to the primary key mapping file, obtaining the start and end time of all first data packets stored in the data content file; According to the start and end times of all first data packets stored in the data content file, obtaining a target data packet corresponding to the playback period from the data content file and / or the cloud server; The operating status of all devices in the station is replayed according to the target data packet.

6. The system for asynchronous incremental playback of station status based on cloud services according to claim 5, characterized in that: According to the start and end times of all first data packets stored in the data content file, obtaining a target data packet corresponding to the playback period from the data content file and / or the cloud server includes: According to the start and end times of all the first data packets stored in the data content file, determining whether the data content file stores all the first data packets corresponding to the playback period: If yes, obtaining all the first data packets corresponding to the playback period from the data content file as the target data packets; If not, all the first data packets corresponding to the playback period are obtained from the cloud server as the target data packets.

7. The system for asynchronous incremental playback of station status based on cloud services according to claim 6, characterized in that: Acquiring all the first data packets corresponding to the playback period from the cloud server as the target data packets includes: Determine whether the data content file stores part of the first data packet corresponding to the playback period: If not, obtaining all of the first data packets corresponding to the playback period from the cloud server as the target data packets; If yes, all the first data packets corresponding to the playback period are obtained from the data content file and the cloud server as the target data packets.

8. The system for asynchronous incremental playback of station status based on cloud services according to claim 7, characterized in that: Acquiring all the first data packets corresponding to the playback period from the data content file and the cloud server as the target data packets includes: According to the start and end times of all the first data packets saved in the data content file, the playback period is divided into a first period and a second period, the first period is included in the start and end times of all the first data packets saved in the data content file, and the second period is not included in the start and end times of all the first data packets saved in the data content file; Acquire the first data packet corresponding to the first time period from the data content file; Acquire the first data packet corresponding to the second time period from the cloud server; The first data packet corresponding to the first time period and the first data packet corresponding to the second time period are used as the target data packets.

9. The system for asynchronous incremental playback of station status based on cloud services according to any one of claims 5 to 8, characterized in that: The cloud server sends the first data packet to the client according to the following steps: Obtaining a request period according to the request sent by the client; Obtaining the first first data packet according to the start time of the request period; Obtaining the last of the first data packets according to the end time of the request period; The first first data packet, the last first data packet, and all other first data packets therebetween are sent to the client together.

10. The system for asynchronous incremental playback of station status based on cloud services according to claim 9, characterized in that: According to the request sent by the client, a request period is obtained, including: According to the request sent by the client, determine whether the requesting user needs to be limited: If yes, do not send the first data packet and return a failure message; If no, get the requested period.

Images