ETC lane transaction log management system based on end cloud architecture

Abstract

The invention provides an ETC lane transaction log management system based on an end cloud architecture, and relates to the field of ETC charging, and the system comprises a station-level log edge server which is disposed at each toll station through employing a distributed architecture, and is used for generating an aggregation lane log in a preset format from a log generated by a toll station-level transaction system, and carrying out the storage and analysis processing; and the provincial cloud log management and analysis platform is used for uniformly organizing and managing the aggregated lane logs according to log storage paths preset by the station-level log edge servers and displaying log analysis results. According to the method, the structured aggregated lane log is established and is more normative and standard than a common lane log, so that the disordered log has higher data analysis value, the utilization range of log data is widened, the problem of specific software and hardware can be positioned more accurately and quickly, data analysis application in more scenes can be performed, and the data analysis efficiency is improved. And the service scene problem is solved.

Description

Technical Field

[0001] The present invention relates to the field of ETC charging, and in particular to an ETC lane transaction log management system based on a terminal-cloud architecture. Background Art

[0002] At present, with the rapid development of intelligent transportation systems, the province's highway network has been fully covered by ETC (electronic toll collection) lanes. This innovative measure has greatly improved vehicle traffic efficiency and reduced traffic congestion. With its highly automated and intelligent characteristics, ETC lanes can quickly identify and release vehicles with ETC tags, allowing toll stations to gradually transform into unmanned or undermanned operation modes. However, behind this efficient operation, the log acquisition and application links of ETC lanes face two significant problems: (I) Difficulty in obtaining lane logs: In the daily operation and troubleshooting of ETC lanes, log files are an important basis for diagnosing problems and optimizing system performance, but the acquisition process is particularly complex and time-consuming. Since lane systems are often composed of multiple modules, when maintenance or operating personnel need to retrieve logs for a specific time period to analyze problems, they have to rely on lane maintenance personnel to manually collect these scattered log files from the local system one by one. This process is not only cumbersome, but also greatly increases the time cost and affects the efficiency of problem solving.

[0003] (ii) Log analysis challenges: Even if the log files are successfully obtained, the complexity and professionalism of their content pose huge challenges to the analysis work. The log files of the ETC lanes contain rich operating data and transaction information, but these data often exist in an unstructured form, requiring R&D personnel with deep professional knowledge and rich experience to unravel them and extract key information. This process requires not only analysts to have a deep understanding of system architecture and business processes, but also to master efficient log analysis tools and techniques. Therefore, for most non-professionals, reading and effectively using these log information is undoubtedly a daunting task. Summary of the invention

[0004] In response to the problems existing in the prior art, an ETC lane transaction log management system based on end-cloud architecture is provided, which can quickly obtain lane system logs and support users to obtain log files on demand. At the same time, by regenerating structured aggregated lane log files, it improves analysis efficiency, analyzes and locates abnormal situations, and thus improves the efficiency of operation and maintenance troubleshooting.

[0005] The technical solution adopted by the present invention is as follows: an ETC lane transaction log management system based on a terminal-cloud architecture, comprising: The station-level log edge server is deployed at each toll station using a distributed architecture. It is used to generate aggregated lane logs in a preset format from the logs generated by the station-level transaction system of the toll station, and store and analyze them. The provincial cloud-based log management and analysis platform is used to uniformly organize and manage aggregated lane logs according to the log storage paths preset by each station-level log edge server, and to display log analysis results.

[0006] As a preferred solution, in the station-level log edge server, generating an aggregated lane log in a preset format from the log generated by the station-level transaction system of the toll station specifically includes: Through the business definition of a unified text framework, each business service of the toll station-level transaction system prints logs according to the format requirements, structured logs of key text information, and logs of multiple business services are combined according to generation time and rules to generate aggregate lane logs; among them, business services include transaction services, billing services, parameter services and external equipment control services.

[0007] As a preferred solution, the logs of the multiple business services are combined according to the generation time and rules to generate an aggregate lane log, specifically including: reassembling the original logs generated by each business service of the station-level transaction system through splitting, reorganization, aggregation and other actions, and marking the assembled logs to form an aggregate lane log.

[0008] As a preferred solution, in the station-level log edge server, the aggregated lane log is divided into log segments according to the vehicle dimension, and is generated and stored in the order of the time when the vehicles pass. Each segment will have a unique ID to support retrieval and combination by the upper-level system.

[0009] As a preferred solution, in the station-level log edge server, the aggregated lane logs are stored in an orderly manner in a directory divided in the form of folders, and the preset log storage path is provided to the provincial cloud log management and analysis platform.

[0010] As a preferred solution, the analysis and processing of the station-level log edge server includes: According to the analysis rules, the required key information and data fragments in the aggregated lane logs are quickly located and extracted, and the key information is structured to support further data statistics and indicator calculations.

[0011] As a preferred solution, after obtaining the logs generated by each business service of the station-level transaction system, the station-level log edge server verifies, filters and converts the data through preset filtering rules, and outputs data that can be used to generate aggregated lane logs.

[0012] As a preferred solution, the station-level log edge server is controlled by the analysis rules and analysis instructions issued by the provincial cloud log management and analysis platform, analyzes and counts the data, and returns the results to the provincial cloud log management and analysis platform.

[0013] As a preferred solution, the provincial cloud log management and analysis platform is configured with the name of each station-level log edge server, the toll station to which it belongs, the IP and port information, and information interaction is achieved by calling the server IP and port information.

[0014] As a preferred solution, after receiving the analysis results, the provincial cloud-based log management and analysis platform provides corresponding data visualization services, and supports log text retrieval analysis and data sharing through the preset log storage path of the station-level log edge server.

[0015] Compared with the prior art, the beneficial effects of adopting the above technical solution are: 1. The station-level servers deployed at toll stations and the provincial log management system can not only manage the ETC lane transaction system logs, but also expand their business to manage other business system logs such as the overload lane system and the mixed lane log system, with the advantages of high scalability and flexibility.

[0016] 2. Log data often contains more business details and has great value for mining, but log printing is generally irregular and unregulated, and business problems cannot be accurately located. The present invention builds a structured aggregated lane log, which is more standardized than ordinary lane logs, making disorganized logs have higher data analysis value, broadening the scope of log data utilization, and being able to more accurately and quickly locate specific software and hardware problems. It can perform data analysis applications in more scenarios and assist in solving business scenario problems. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 Schematic diagram of the ETC lane transaction log management system based on the end-cloud architecture proposed in the present invention.

[0018] Figure 2 This is a data architecture diagram of an ETC lane transaction log management system based on an end-cloud architecture in one embodiment of the present invention.

[0019] Figure 3 This is an implementation architecture diagram of an ETC lane transaction log management system based on an end-cloud architecture in one embodiment of the present invention. DETAILED DESCRIPTION

[0020] Embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar modules or modules with the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application, and cannot be construed as limitations on the present application. On the contrary, the embodiments of the present application include all changes, modifications and equivalents that fall within the spirit and connotation of the appended claims.

[0021] To obtain and analyze lane logs, please refer to Figure 1 , an embodiment of the present invention proposes an ETC lane transaction log management system based on end-cloud architecture, which mainly includes a station-level log edge server and a provincial cloud-based log management and analysis platform.

[0022] In this embodiment, the station-level log edge server is deployed in each toll station using a distributed architecture, and is used to obtain the logs generated by each business service (transaction service, billing service, parameter service and external device control service) of the station-level transaction system, and generate aggregate lane logs in a preset format according to preset rules; and store and analyze the generated aggregate lane logs.

[0023] The provincial cloud-based log management and analysis platform is deployed in the cloud server. It interacts with data from each station-level log edge server, can uniformly organize and manage aggregated lane logs through preset log storage paths, and can also display the analysis results of aggregated lane logs.

[0024] The following is further explanation of the station-level log edge server and the provincial cloud log management and analysis platform.

[0025] The station-level log edge server serves as the initial node for log data aggregation, realizing the real-time collection and preliminary processing of logs of various business services in the station-level transaction system of the toll station. In this embodiment, in addition to aggregating the log file collection of each business service for analysis at the station-level log edge server, the data is verified, filtered and converted through preset filtering rules, and data compression and encryption are performed to ensure data security and transmission efficiency. The deployment of log edge servers at each toll station and the use of a distributed architecture can ensure that each toll station can independently and efficiently process and store the log files uploaded by its station-level transaction system.

[0026] A key point of the station-level log edge server is the generation of aggregated lane logs. In this embodiment, when processing vehicle communications in the ETC lane of the highway, a text framework uniformly specified in the business is used to integrate log information to form an aggregated lane log. Specifically, the process is based on the log records generated by various business services of the station-level transaction system (mainly including transaction services, billing services, parameter services and external device control services). According to the established text framework, these originally scattered and disordered logs from different software and hardware can be distinguished and integrated to form an information set composed of an orderly combination of various key service modules within the station-level transaction system, namely, the aggregated lane log. In one embodiment, the original logs generated by various business services of the station-level transaction system are reassembled through splitting, reorganization, and aggregation actions, and the assembled logs are identified to form an aggregated lane log. In the aggregated lane log, the log fragments are divided according to the vehicle dimension, and are generated and stored according to the time sequence of the vehicle passing. Each fragment will have a unique ID to support the upper system to retrieve and combine. The aggregated lane log records in detail each step of each vehicle passing through the ETC lane in chronological order, thereby greatly simplifying the subsequent integration and analysis logic of the log. Based on the distributed station-level log edge server, this embodiment supports the overall traffic behavior analysis of a vehicle when passing through a highway, involving the similarities and differences in the logs generated by a vehicle at different times and locations during the same trip, that is, the traffic analysis within the deployment area of ​​the station-level log edge server.

[0027] For the generated aggregated lane log, in this embodiment, the aggregated lane log file is stored in the servers of each toll station in a distributed manner. At the same time, for a station-level log edge server, the aggregated lane log file is stored in a directory divided in the form of a folder in an orderly manner.

[0028] Furthermore, the station-level log edge server also provides an analysis function for the aggregated lane logs, which can be analyzed autonomously or according to instructions issued by the provincial cloud log management and analysis platform. Specifically, on the basis of obtaining the aggregated lane logs, the required key information and data fragments in the aggregated lane logs are quickly located and extracted according to business rules, and these key information are structured for further data statistics and indicator calculations, so that users can clearly view the analysis results. This embodiment provides specific analysis steps, including: Customized business rules, that is, define the business logic of the indicators for data analysis, accurately define the meaning and purpose of each indicator (indicator definition) to form an indicator set, establish the calculation method and steps for each indicator (data collection formula), and unify the statistical scope, frequency and standard (statistical caliber) of the data to ensure the consistency and accuracy of the data analysis results. According to the customized business rules, extract keywords, build data collection logic, ensure effective data acquisition, and finally form specific data indicators. Take the number of ETC tags as an example: Indicator name: Detection of the number of ETC tags; The calculation formula is defined as: Detection tag number = number of successful transactions + number of logical failures + number of physical failures; Keyword collection logic is defined as: Take the trade status (trading status) in the transaction service log text of the station-level trading system, and sum the key fields of TradeStatus (trading status) = 1, 2, 3, 5 (1-trading success, 2-logical failure, 3-physical failure, 5-cross-lane re-take TAC).

[0029] Through the above process, the analysis of the number of ETC tags can be completed.

[0030] The provincial cloud log management and analysis platform is mainly used to realize human-computer interaction for users. The provincial cloud log management and analysis platform is configured with the name of the station-level log edge server, the toll station to which it belongs, IP, port and other information. By calling the server IP and port information, the provincial cloud log management and analysis platform obtains the log storage directory on the station-level log edge server, and can realize the centralized management of log text in the form of folders. Furthermore, the provincial cloud log management and analysis platform can also retrieve the log text on the station-level server as needed according to the log storage directory, and retrieve the required information in the log text.

[0031] The provincial cloud-based log management and analysis platform can also issue analysis rules and analysis instructions to the station-level log edge server to achieve data analysis and statistical control. The log analysis results of each toll station will be summarized and formed into corresponding reports and visual large-screen displays.

[0032] In one embodiment, the ETC lane transaction log management system based on the end-cloud architecture monitors in real time the process of lanes uploading logs to the station-level server and the process of aggregating lane logs and uploading them to the provincial cloud log management and analysis platform, to ensure the integrity of log files on each transmission link.

[0033] It should be noted that, in the present embodiment, the provincial cloud log management and analysis platform can exchange information with the edge system deployed in the station-level log edge server and multiple edge systems. On the one hand, the edge system can send analysis results to the provincial cloud log management and analysis platform. On the other hand, the provincial cloud log management and analysis platform will also issue instructions to the edge system to realize data analysis and statistical control. In addition, different edge systems can also exchange data. For example, if a vehicle enters and exits the highway from multiple stations within a period of time, the edge systems of these stations can aggregate multiple log fragments of the vehicle together for special analysis according to the instructions of the provincial cloud log management and analysis platform.

[0034] The data flow of aggregated lane log generation, log analysis, and log application proposed in the present invention ensures the smooth transmission and processing of log data. From the original log file to the final analysis result, after being processed by the station-level log edge server and the provincial cloud log management and analysis platform, users can intuitively understand the operation status and key indicators of each toll station through reports and large-screen displays. At the same time, the remote log retrieval and sharing function provides a convenient and fast way for users to efficiently retrieve log data, supporting more in-depth data analysis and decision-making.

[0035] Please refer to Figure 2 A specific data architecture diagram of an ETC lane transaction log management system based on an end-cloud architecture is shown, and the solution proposed in the present invention is further explained in conjunction with the diagram.

[0036] From the overall process point of view, log data is generated in each business service of the station-level transaction system and transmitted to the station-level log edge server at a regular interval. The station-level log edge server generates aggregate lane logs while performing data governance, and analyzes and stores the aggregate lane logs. The analysis results are directly uploaded to the provincial cloud log management and analysis platform to realize report display and sharing.

[0037] From the data flow diagram, the log data generated by each business service of the station-level transaction system is regularly transmitted to the station-level log edge server, which collects the data through the log file collection service, verifies, filters and converts the data according to the preset rules, obtains usable structured data, and generates aggregate lane logs based on the structured data. Among them, the aggregate lane logs are stored in the station-level log edge server in the form of folders.

[0038] The station-level log edge server also includes three parts: task scheduling management, data analysis, and log management. Among them, task scheduling management mainly realizes the acquisition of analysis rules issued by the provincial cloud log management and analysis platform, and realizes the scheduling of analysis tasks according to the analysis rules. Data analysis implements specific aggregated lane log analysis according to the analysis task, and uploads the analysis results to the provincial cloud log management and analysis platform through the data transmission service. Log management provides a preset log storage path to the provincial cloud log management and analysis platform for on-demand calling.

[0039] The provincial cloud log management and analysis platform provides a workbench, which is mainly used for issuing instructions. At the same time, it receives the analysis results uploaded by the station-level log edge server, forms an indicator result set and performs ranking summary, and finally displays it through a large screen or report. According to the log management function provided by the station-level log edge server, the provincial cloud log management and analysis platform can call the corresponding aggregate lane log file on demand to realize text retrieval analysis and data sharing.

[0040] Please refer to Figure 3 , shows the implementation architecture diagram of the ETC lane transaction log management system based on the end-cloud architecture. The entire system is in the standard specification system and the safe operation and maintenance guarantee system, including the basic environment layer, data resource layer, application support layer, application layer, and presentation layer from bottom to top. Specifically: The basic environment layer mainly includes the resource system and the network system. The resource system includes computing resources, storage resources, security equipment resources, etc., and the network system includes toll-free networks, security protection network equipment, etc.

[0041] The data resource layer mainly includes lane log files and other system logs generated by various business services of the station-level transaction system, such as transaction information, RSU information, charging information, system information, etc.

[0042] The application support layer includes two parts: station level and provincial level. The station level part is the support for the aforementioned station-level log edge server, which mainly includes data collection and analysis and data storage. Data collection and analysis includes log collection, log conversion storage (including aggregate lane log generation), log analysis, and analysis result indicator transmission; data storage includes the establishment of structured data storage and file system. The provincial part is the support for the aforementioned provincial cloud log management and analysis platform, including data transmission capability, log management capability, analysis capability and storage capability. Among them, data transmission capability mainly provides API access, data sharing and file processing; log management capability mainly realizes remote log retrieval, life cycle management and log directory management of log files stored at the station level; analysis capability is mainly to perform indicator ranking statistics, indicator summary analysis and log retrieval analysis on the analysis result indicators uploaded at the station level; storage capability is used to store indicator data, basic data, business data and log details.

[0043] The application layer, based on the application support layer, provides basic service capabilities and application services. The basic service capabilities include unified user management, unified authentication management, unified authority management, and unified task scheduling; application services include log management, alarm management, report management, and basic data management.

[0044] The presentation layer mainly includes the WEB portal, which provides users with functions such as workbench, large-screen visualization, and message notification.

[0045] In combination with the aforementioned data architecture and system architecture description, this embodiment also provides a workflow of the entire system, including: 1. Each business service of the station-level transaction system generates aggregate lane logs according to the agreed rules; 2. Transmit the data to the station-level edge log server through the interface to complete lane log data management and analysis; 3. Then transmit it to the provincial log management and analysis system, and generate lane operation quality analysis, manufacturer equipment analysis, transaction special situation analysis, and indicator warning based on the analysis results; 4. Operation personnel can log in to the provincial log management and analysis system to check the lane operation quality, or the manufacturer's operation and maintenance personnel can solve the corresponding error code problem based on the equipment analysis results (common error codes, etc.) fed back by the provincial log management and analysis system, or handle the warning information by following up on real-time indicator warnings.

[0046] The ETC lane transaction log management system based on the end-cloud architecture proposed in the present invention can not only manage the ETC lane transaction system logs, but also expand its business to manage the square overload control system, the mixed lane log system, the remote duty system and other business system logs, and has the advantages of high scalability and flexibility. By establishing a structured aggregated lane log, which is more standardized than ordinary lane logs, the disorganized logs have higher data analysis value, broaden the scope of log data utilization, and can more accurately and quickly locate specific software and hardware problems. It can perform data analysis applications in more scenarios and assist in solving business scenario problems.

[0047] For those skilled in the art, the specific meanings of the above terms in the present invention can be understood in specific situations; the drawings in the embodiments are used to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Generally, the components of the embodiments of the present invention described and shown in the drawings herein can be arranged and designed in various different configurations.

[0048] Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limitations on the present application. Ordinary technicians in this field can change, modify, replace and modify the above embodiments within the scope of the present application.

Claims

1. An ETC lane transaction log management system based on end-cloud architecture, characterized in that: include: The station-level log edge server is deployed at each toll station using a distributed architecture. It is used to generate aggregated lane logs in a preset format from the logs generated by the station-level transaction system of the toll station, and store and analyze them. The provincial cloud-based log management and analysis platform is used to uniformly organize and manage aggregated lane logs according to the log storage paths preset by each station-level log edge server, and to display log analysis results.

2. The ETC lane transaction log management system based on the end-cloud architecture according to claim 1 is characterized in that: In the station-level log edge server, generating an aggregated lane log in a preset format from the log generated by the station-level transaction system of the toll station specifically includes: Through the unified text framework defined by the business, each business service of the station-level transaction system prints logs according to the format requirements, structured logs contain key text information, and logs of multiple business services are combined according to generation time and rules to generate aggregate lane logs; among them, business services include transaction services, billing services, parameter services, and external device control services.

3. The ETC lane transaction log management system based on the end-cloud architecture according to claim 1 is characterized in that: The logs of the multiple business services are combined according to the generation time and rules to generate an aggregate lane log, specifically including: reassembling the original logs generated by each business service of the station-level transaction system through splitting, reorganization, and aggregation actions, and marking the assembled logs to form an aggregate lane log.

4. The ETC lane transaction log management system based on the end-cloud architecture according to claim 1 is characterized in that: In the station-level log edge server, aggregated lane logs are generated and stored in the order of the time when vehicles pass.

5. The ETC lane transaction log management system based on the end-cloud architecture according to claim 1 is characterized in that: In the station-level log edge server, the aggregated lane logs are stored in an orderly manner in directories divided in the form of folders, and the preset log storage path is provided to the provincial cloud log management and analysis platform.

6. The ETC lane transaction log management system based on the end-cloud architecture according to claim 1 is characterized in that: The analysis and processing of the station-level log edge server includes: According to the analysis rules, the required key information and data fragments in the aggregated lane logs are quickly located and extracted, and the key information is structured to support further data statistics and indicator calculations.

7. The ETC lane transaction log management system based on the end-cloud architecture according to claim 2 is characterized in that: After obtaining the logs generated by each business service of the station-level transaction system, the station-level log edge server verifies, filters and converts the data through preset filtering rules, and outputs data that can be used to generate aggregate lane logs.

8. The ETC lane transaction log management system based on the end-cloud architecture according to claim 1 is characterized in that: The station-level log edge server is controlled by the analysis rules and analysis instructions issued by the provincial cloud log management and analysis platform, analyzes and compiles statistics on the data, and returns the results to the provincial cloud log management and analysis platform.

9. The ETC lane transaction log management system based on the end-cloud architecture according to claim 1 is characterized in that: The provincial cloud-based log management and analysis platform is configured with the name of each station-level log edge server, the toll station to which it belongs, the IP and port information, and information interaction is achieved by calling the server IP and port information.

10. The ETC lane transaction log management system based on the end-cloud architecture according to claim 1 is characterized in that: After receiving the analysis results, the provincial cloud-based log management and analysis platform provides corresponding data visualization services, and supports log text retrieval analysis and data sharing through the preset log storage path of the station-level log edge server.

Images