Highway networking toll data safety management method and device

Abstract

The invention provides a highway networking toll data safety management method and device, and the method comprises the steps: determining the classification types of highway networking toll data and the field attributes of the data under each type, respectively determining a sensitive level corresponding to each classification category and a sensitive level corresponding to each field attribute based on the sensitive degree of each classification category and the sensitive degree of each field attribute; a data request is obtained, the data request comprises a request data type, and the data processing level of the to-be-requested highway networking toll collection data is determined based on the request data type, the sensitive level corresponding to each classification category and the sensitive level corresponding to each field attribute; and determining a data processing algorithm based on the data processing level corresponding to the to-be-requested highway networking toll data, and performing data desensitization processing on the to-be-requested highway networking toll data based on the data processing algorithm to obtain a desensitization data request result. According to the invention, the data security of the road networking toll collection data in the business interaction process can be improved.

Description

Technical Field

[0001] The present invention relates to the technical field of highway network toll collection, and in particular, to a method and device for data security management of highway network toll collection. Background Art

[0002] After canceling the provincial boundary toll stations of expressways, the national expressway network has entered a new stage of "operating as a single network and providing integrated services". While each provincial network center and the ministerial network center use virtualization technology, big data analysis, open-source components, and data sharing to support the operation of business such as ETC customer service, new security problems are also brought to the business. However, the road transportation mainly relies on the highway network toll collection system, and the highway network toll collection system involves many different types of data such as passing records, transaction information, ETC user information, industry unit information, infrastructure information, and business information. Therefore, the data classification and grading and security protection of network toll collection business are still in the stage of research and establishment.

[0003] At present, for the highway network toll collection data with large volume, various types, and complex business interactions, there is no effective security management method to improve the data security of highway network toll collection data during business interactions. Therefore, how to improve the data security of highway network toll collection data during business interactions is a technical problem to be solved urgently. Summary of the Invention

[0004] In view of this, embodiments of the present invention provide a method and device for data security management of highway network toll collection to eliminate or improve one or more defects existing in the prior art.

[0005] One aspect of the present invention provides a method for data security management of highway network toll collection, the method comprising:

[0006] Determine the classification categories of highway network toll collection data and the field attributes of the data under each category, and respectively determine the sensitivity levels corresponding to each classification category and the sensitivity levels corresponding to each field attribute based on the sensitivity of each classification category and the sensitivity of each field attribute;

[0007] Obtain a data request, the data request including a requested data type, and determine the data processing level of the highway network toll collection data to be requested based on the requested data type, the sensitivity levels corresponding to each classification category, and the sensitivity levels corresponding to each field attribute;

[0008] Determine a data processing algorithm based on the data processing level corresponding to the highway network toll collection data to be requested, and perform data desensitization processing on the highway network toll collection data to be requested based on the data processing algorithm to obtain a desensitized data request result.

[0009] In some embodiments of the present invention, the request data type is a single-field data request, a single-category data request, or a multi-category data request.

[0010] In some embodiments of the present invention, determining the data processing level of the to-be-requested highway network toll data based on the request data type, the sensitivity levels corresponding to each classification category, and the sensitivity levels corresponding to each field attribute includes:

[0011] Determining a classification strategy based on the request data type, where the classification strategy is a single-field classification strategy, a single-category classification strategy, or a multi-category classification strategy;

[0012] Determining the data processing level of the to-be-requested highway network toll data based on the determined classification strategy, the sensitivity levels corresponding to each classification category, and the sensitivity levels corresponding to each field attribute.

[0013] In some embodiments of the present invention, the single-field classification strategy includes: using the sensitivity level corresponding to the field attribute of the to-be-requested highway network toll data as the data processing level; and / or,

[0014] The single-category classification strategy includes: using the sensitivity level corresponding to the classification category of the to-be-requested highway network toll data as the data processing level; and / or,

[0015] The multi-category classification strategy includes: if the sensitivity levels of multiple classification categories of the to-be-requested highway network toll data are all at the third level, then the data processing level of the to-be-requested highway network toll data is the third level; if the sensitivity level of the classification category of at least one category of data in the to-be-requested highway network toll data is at the first level, then the data processing level of the to-be-requested highway network toll data is the first level; if the sensitivity levels of the classification categories of at least two categories of data in the to-be-requested highway network toll data are at the second level, then the data processing level of the to-be-requested highway network toll data is the first level; if only one category of data in the to-be-requested highway network toll data has a sensitivity level of the second level and at least three categories of data have sensitivity levels of the third level, then the data processing level of the to-be-requested highway network toll data is the first level; if only one category of data in the to-be-requested highway network toll data has a sensitivity level of the second level and less than or equal to two categories of data have sensitivity levels of the third level, then the data processing level of the to-be-requested highway network toll data is the second level.

[0016] In some embodiments of the present invention, performing data desensitization processing on the to-be-requested highway network toll data based on the data processing algorithm includes:

[0017] Determining the data cleaning strategy corresponding to the data request;

[0018] Clean the to-be-requested highway network toll data based on the above data cleaning strategy;

[0019] Perform data desensitization on the to-be-requested highway network toll data after data cleaning based on the above data processing algorithm.

[0020] In some embodiments of the present invention, before the step of cleaning the to-be-requested highway network toll data based on the above data cleaning strategy, it includes:

[0021] Generate a desensitization task based on the to-be-requested highway network toll data, the above data processing level, and the above data cleaning strategy;

[0022] Determine the approval result based on the above desensitization task.

[0023] In some embodiments of the present invention, cleaning the to-be-requested highway network toll data based on the above data cleaning strategy includes:

[0024] Optimize the above data cleaning strategy to obtain an optimized data cleaning strategy;

[0025] Clean the to-be-requested highway network toll data based on the optimized data cleaning strategy.

[0026] In some embodiments of the present invention, the classification categories of the highway network toll data include: entity basic information, contact information, business information, transaction information, geographical information, vehicle information, and certificate information; and / or

[0027] The data processing algorithms corresponding to the first level include masking, encryption, truncation, or offset rounding;

[0028] The data processing algorithms corresponding to the second level include masking, encryption, truncation, offset rounding, synonym replacement, or rearrangement.

[0029] According to another aspect of the present invention, there is also disclosed a highway network toll data security management device, which includes a processor, a memory, and a computer program stored on the memory. The processor is used to execute the computer program, and when the computer program is executed, the device implements the steps of the method described in any of the above embodiments.

[0030] According to still another aspect of the present invention, there is also disclosed a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, it implements the steps of the method described in any of the above embodiments.

[0031] The highway network toll data security management method and device disclosed in the above embodiments of the present invention first determine the sensitivity levels corresponding to each classification category and the sensitivity levels corresponding to each field attribute under each classification category, then determine the data processing level of the to-be-requested highway network toll data according to the obtained request data type and the known sensitivity levels corresponding to each classification category and each field attribute, and finally perform data desensitization processing on the to-be-requested highway network toll data based on the data processing algorithm corresponding to the data processing level, so as to obtain the desensitized data request result. This application can effectively desensitize the requested highway network toll data, improve the data security of highway network toll data during business interaction, and thus achieve the security control of highway network toll data.

[0032] Additional advantages, objects, and features of the present invention will be partially described below, and will become partially apparent to those of ordinary skill in the art after studying the following text, or may be learned from the practice of the present invention. The objects and other advantages of the present invention can be realized and obtained by the structure specifically pointed out in the specification and the drawings.

[0033] Those skilled in the art will understand that the objects and advantages that can be achieved by the present invention are not limited to the above specifically described, and the above and other objects that the present invention can achieve will be more clearly understood according to the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] The drawings described herein are used to provide a further understanding of the present invention, form a part of this application, and do not limit the present invention. The components in the drawings are not drawn to scale, but are only for showing the principles of the present invention. In order to facilitate showing and describing some parts of the present invention, the corresponding parts in the drawings may be enlarged, that is, may become larger relative to other components in the exemplary device actually manufactured according to the present invention. In the drawings:

[0035] Figure 1 is a schematic flowchart of a highway network toll data security management method according to an embodiment of the present application.

[0036] Figure 2 is a schematic flowchart of a highway network toll data security management method according to another embodiment of the present application.

[0037] Figure 3 is a schematic flowchart of a highway network toll data security management method according to yet another embodiment of the present application.

[0038] Figure 4 is a schematic flowchart of an ETC toll suspected overcharge complaint service according to an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0039] To make the objectives, technical solutions and advantages of the present invention more clearly understood, the present invention will be further described in detail below in conjunction with the embodiments and the drawings. Herein, the illustrative embodiments of the present invention and the description thereof are used to explain the present invention, but do not limit the present invention.

[0040] Herein, it should also be noted that in order to avoid obscuring the present invention due to unnecessary details, only the structures and / or processing steps closely related to the solution according to the present invention are shown in the drawings, while other details less related to the present invention are omitted.

[0041] It should be emphasized that the term "including / comprising" when used herein refers to the presence of features, elements, steps or components, but does not exclude the presence or addition of one or more other features, elements, steps or components.

[0042] Herein, it should also be noted that if not otherwise specified, the term "connection" in this document can not only refer to a direct connection, but also represent an indirect connection with an intermediate, and can not only represent a wired connection, but also a wireless connection, and can be specifically changed based on the actual application scenario.

[0043] In the following, embodiments of the present invention will be described with reference to the drawings. In the drawings, the same reference numerals represent the same or similar components, or the same or similar steps.

[0044] Figure 1 It is a schematic flowchart of a method for highway network toll data security management according to an embodiment of the present application. As Figure 1 shown, the method for highway network toll data security management at least includes steps S10 to S30.

[0045] Step S10: Determine the classification categories of highway network toll data and the field attributes of the data under each category, and respectively determine the sensitivity levels corresponding to each classification category and the sensitivity levels corresponding to each field attribute based on the sensitivity of each classification category and the sensitivity of each field attribute.

[0046] In this step, first determine the classification categories of highway network toll data. For example, the highway network toll data is divided into seven categories: entity basic information, contact information, business information, transaction information, geographical information, vehicle information, and certificate information. Each category of data includes at least one field attribute. In a specific embodiment, each category of data is composed of multiple field attributes to completely describe the information of each category of data.

[0047] Exemplarily, the entity basic information includes the identification information of the business entity and other information describing the basic attributes of the entity. The field attributes under the entity basic information may include, for example: ETC issuing service agency, customer service cooperation agency, service network, mobile service network, self-service terminal, online service channel, toll road owner, toll section, toll unit, toll station, toll plaza, toll lane, toll gantry, RSU controller, reader / writer, lane software, industrial control computer, ETC parking lot operator in service area, ETC parking lot operator, parking lot, ETC gas station operator, gas station, ETC operator for municipal expansion, municipal expansion bridges and tunnels, etc.

[0048] The contact information includes the contact information about customers / contacts in the business entity. The field attributes under the contact information may include, for example: ETC users, ETC handlers, names, phone numbers, addresses, email addresses of vehicle owners, etc., as well as names, phone numbers, addresses, email addresses of internal industry personnel users such as issuing agencies, customer service cooperation agencies, service networks, toll road owners, ETC parking lot operators in service area, ETC parking lot operators, ETC gas station operators, ETC operators for municipal expansion, etc.

[0049] The business information includes the attributes describing the business information in the business entity. The field attributes under the business information may include, for example: ETC transaction accounting, ETC dispute handling, ETC clearing, ETC splitting, transaction reconciliation, other transaction splitting, ETC expansion service accounting, ETC expansion service dispute handling, ETC expansion service settlement, toll invoice issuance, etc., including start / end time, business mode, status, business number, etc.

[0050] The transaction information includes the attributes describing the business transactions in the business entity. The field attributes under the transaction information may include, for example: ETC transactions at exit toll stations, summary of ETC gantries in passing provinces, other transactions at exits, online billing, green channel discounts, container discounts, toll exemptions, expansion services, refunds, supplements, audit surcharges, etc., including relevant card numbers, details, transaction amounts, balances, service locations (toll stations, parking lots, bridges, tunnels, gas stations, etc.), passing media, billing methods, payment types, billing mileage, etc., as well as information such as ETC recharge transactions, transaction accounting, transaction clearing, transaction splitting, monthly statements, transaction reconciliation, passing invoice identification, etc., including card numbers, details, transaction amounts, etc.

[0051] The geographical information includes the information about the geographical location in the business entity. The field attributes under the geographical information may include, for example: longitude, latitude, highway mileage stake numbers, location names of toll roads, toll sections, toll units, toll plazas, toll gantries, service areas, parking lots, gas stations, municipal expansion bridges and tunnels, etc.

[0052] Vehicle information includes information about vehicle parameters in the business entity. The field attributes under vehicle information may include, for example: license plate number, color, vehicle type, toll model, vehicle type on the driving license, brand model, vehicle usage nature, vehicle identification number (VIN), engine number, approved seating capacity, gross mass, curb mass, approved payload, number of wheels, number of axles, wheelbase, axle type, registration date, vehicle number, status of the corresponding ETC card access list and audit list, etc.

[0053] Certificate information includes information about personal certificates in the business entity. The field attributes under certificate information may include, for example: ID numbers of the account opener and operator, certificate type, signing bank, prepaid account number, withholding account number, ID number of the unit user, certificate type, bank and account number, bank address, etc.

[0054] It can be understood that the above-listed data classification categories and the field attributes under each category are only some examples and do not constitute a limitation on the classification categories and field attributes of this application.

[0055] In addition, after determining the above classification categories and the field attributes of the data under each category, the sensitivity levels of various types of data and each field attribute are further divided. In one embodiment, the sensitivity of the classification categories and field attributes is divided into three levels (Level I, Level II, and Level III), and different security processing measures are adopted for data at different sensitivity levels during the data request process. For example, Level I data belongs to data that is not used in the business and is private in the network toll collection business system. Therefore, when requesting Level I data, the data needs to be encrypted or desensitized. That is, the data processing algorithms corresponding to Level I data include masking, encryption, truncation, or offset rounding, etc. In addition, an approval process may be passed before processing Level I data; Level II data belongs to data that is used in the business and is private in the network toll collection business system. Therefore, when requesting Level II data, the data needs to be encrypted or desensitized. That is, the data processing algorithms corresponding to Level II data include masking, encryption, truncation, offset rounding, synonym replacement, or rearrangement, etc. In addition, an approval process may also be passed before processing Level II data; Level III data belongs to data that is used in the business and is not private in the network toll collection business system. Therefore, when requesting Level III data, the data does not need to be encrypted or desensitized, and an approval process may also be passed before processing Level III data. It can be understood that the above-listed division of the sensitivity of the classification categories and field attributes into three levels is only some examples. In other embodiments, the sensitivity of the classification categories and field attributes may also be divided into more levels or fewer levels.

[0056] Exemplarily, for the above seven types of data, the sensitivity levels of each field attribute are classified according to whether the field attribute is used and whether it involves sensitive attributes. Specifically, for the data of the entity basic information category, the identification information of the business entity is classified as level II, that is, encryption processing needs to be performed on it, and the encryption methods are such as MD5, SM3, SHA, etc. All other field attributes except the identification information of the business entity are classified as level III. For the data of the contact information category and the geographical information category, each of their field attributes is classified as level II; for the data of the business information category and the transaction information category, each of their field attributes is classified as level III; while for the data of the vehicle information category and the certificate information category, each of their field attributes is classified as level I.

[0057] In addition, according to the classification protection rules of highway network toll data, the sensitivity levels of each classification category as a whole are classified. For example, the vehicle information and certificate information categories are classified as level I, the contact information and geographical information categories are classified as level II, and the basic information, transaction information, and business information categories are classified as level III.

[0058] Step S20: Obtain a data request, where the data request includes a requested data type, and determine the data processing level of the highway network toll data to be requested based on the requested data type, the sensitive levels corresponding to each of the classification categories, and the sensitive levels corresponding to each of the field attributes.

[0059] When making a data request, first determine the requested data type, and further determine the data processing level of the requested data based on the requested data type and the sensitive levels of each classification category and each field attribute of the originally classified highway network toll data. In this step, if the requested data type is different, the method for determining the data processing level is also different. Exemplarily, the requested data type can be a single-field data request, a single-category data request, or a multi-category data request. A single-field data request means requesting data for a single field attribute, a single-category data request means requesting data for a single category, and a multi-category data request means simultaneously requesting data for multiple categories.

[0060] In a specific embodiment, determining the data processing level of the to-be-requested highway network toll data based on the request data type, the sensitivity levels corresponding to each classification category, and the sensitivity levels corresponding to each field attribute includes: determining a classification strategy based on the request data type, where the classification strategy is a single-field classification strategy, a single-category classification strategy, or a multi-category classification strategy; determining the data processing level of the to-be-requested highway network toll data based on the determined classification strategy, the sensitivity levels corresponding to each classification category, and the sensitivity levels corresponding to each field attribute. In this embodiment, single-field data, single-category data, or multi-category data corresponds to a single-field classification strategy, a single-category classification strategy, or a multi-category classification strategy respectively; that is, when requesting single-field data, the data processing level of the requested data is determined according to the sensitivity level corresponding to the requested field attribute; when requesting single-category data, the data processing level of the requested data is determined according to the sensitivity level corresponding to the requested classification category; and when requesting multi-category data, the final data processing level of the requested data is determined according to the multi-category classification strategy.

[0061] Specifically, the single-field classification strategy includes: using the sensitivity level corresponding to the field attribute of the to-be-requested highway network toll data as the data processing level. The single-category classification strategy includes: using the sensitivity level corresponding to the classification category of the to-be-requested highway network toll data as the data processing level. The multi-category classification strategy includes: if the sensitivity levels of multiple classification categories of the to-be-requested highway network toll data are all at the third level, then the data processing level of the to-be-requested highway network toll data is the third level; if the sensitivity level of the classification category of at least one type of data in the to-be-requested highway network toll data is at the first level, then the data processing level of the to-be-requested highway network toll data is the first level; if the sensitivity levels of the classification categories of at least two types of data in the to-be-requested highway network toll data are at the second level, then the data processing level of the to-be-requested highway network toll data is the first level; if the sensitivity level of the classification category of only one type of data in the to-be-requested highway network toll data is at the second level, and the sensitivity levels of at least three types of data in the to-be-requested highway network toll data are at the third level, then the data processing level of the to-be-requested highway network toll data is the first level; if the sensitivity level of the classification category of only one type of data in the to-be-requested highway network toll data is at the second level, and the sensitivity levels of less than or equal to two types of data in the to-be-requested highway network toll data are at the third level, then the data processing level of the to-be-requested highway network toll data is the second level.

[0062] When determining the data processing level corresponding to a data request for multi-category data in the above embodiments, dynamic combination grading of multi-category data is performed. For example, for a multi-category data application composed of at least two of basic information, transaction information, and business information, since the sensitivity levels of the three categories of data are all level III, the combination still follows the processing flow of level III data; if the multi-category data only contains one category of level II data and the number of level III data is less than or equal to two categories, the combination follows the processing flow of level II data; if the multi-category data only contains one category of level II data and the number of level III data is more than two categories, the combination follows the processing flow of level I data; if the multi-category data contains two categories of level II data, the combination follows the processing flow of level I data; and as long as the multi-category data contains at least one category of level I data, the combination follows the processing flow of level I data.

[0063] Step S30: Determine a data processing algorithm based on the data processing level corresponding to the to-be-requested highway network toll data, and perform data desensitization processing on the to-be-requested highway network toll data based on the data processing algorithm to obtain a desensitized data request result.

[0064] After determining the data processing level corresponding to the to-be-requested highway network toll data in step S20, further perform data desensitization processing on the data based on a data processing algorithm matching this level. Methods for data processing according to level I data may include masking, encryption, truncation, or offset rounding, etc., while methods for data processing according to level II data may include masking, encryption, truncation, offset rounding, synonym replacement, or rearrangement, etc.

[0065] In one embodiment, performing data desensitization processing on the to-be-requested highway network toll data based on the data processing algorithm may specifically include: determining a data cleaning strategy corresponding to the data request; performing data cleaning on the to-be-requested highway network toll data based on the data cleaning strategy; and performing data desensitization processing on the to-be-requested highway network toll data after data cleaning based on the data processing algorithm. This embodiment also completes data cleaning based on the determined data cleaning strategy when performing data desensitization processing on the to-be-requested highway network toll data. The data cleaning strategy is, for example, to perform checks on whether fields are the same, data consistency, invalid values, and missing values, and set a dictionary rule library for special requirements such as data related to national security.

[0066] In some other embodiments, before the step of performing data cleaning on the to-be-requested highway network toll data based on the data cleaning strategy, it may further include: generating a desensitization task based on the to-be-requested highway network toll data, the data processing level, and the data cleaning strategy; determining an approval result based on the desensitization task. This embodiment further approves the data processing tasks corresponding to the requested data, that is, generates a desensitization task application by incorporating data source / target source, desensitization template, and cleaning rules for approval. After approval, the task execution efficiency is improved through a distributed method, the ETC customer service data is desensitized, and the monitoring of the task execution situation is supported.

[0067] In addition, performing data cleaning on the to-be-requested highway network toll data based on the data cleaning strategy may specifically include: optimizing the data cleaning strategy to obtain an optimized data cleaning strategy; performing data cleaning on the to-be-requested highway network toll data based on the optimized data cleaning strategy. This embodiment can adjust and optimize the data cleaning strategy based on the data cleaning result, so as to perform data cleaning on the to-be-requested highway network toll data based on the optimized data cleaning strategy.

[0068] To better explain the present application, the highway network toll data security management method of the present application will be described in detail below by taking the ETC customer service scenario as an example:

[0069] After the cancellation of provincial boundary toll stations on national expressways, the number of ETC customers will experience explosive growth in a short period of time. The national expressway network has entered a new stage of "one-network operation and integrated services", with more complex business connections and interactions, and the number of operations growing exponentially. The public's requirements for travel service quality are also getting higher and higher, and each province (autonomous region, municipality directly under the Central Government) faces huge customer service pressure. The unimpeded single-passage has led to an increased impulse among some customers to evade tolls, and the operation and management order of toll roads faces huge challenges. Therefore, a powerful customer service system needs to be built. Each province is responsible for accepting customer complaints, providing consultation and inquiry services for customers, and handling ETC business. It organizes the local issuance service agencies and road owners to strictly complete the work order processing within the specified time limit according to the requirements. The ministry conducts service supervision work, accepts customer complaints, coordinates all participating parties to complete the complaint handling, tracks and urges the results of complaint handling, and organizes each province and city to reply to customers according to the results of work order processing. The toll road customer service system supports the consultation and complaint acceptance of various toll operations after the cancellation of provincial boundary stations through manual and intelligent customer service functions, and provides the public with customer information services, travel record information services, ETC card information services, and consultation processing information services. Customer service operations require a large amount of data support, and the relevant work is specifically undertaken by a third-party professional outsourcing agency. The data involved in customer service operations includes basic information, contact information, business information, transaction information, geographical information, vehicle information, and document information. To ensure data security, the highway network toll data security management method of this application classifies, grades, processes, approves, and desensitizes the above data to obtain desensitized data, protecting the security of users' personal information while ensuring the normal conduct of operations.

[0070] Such as Figure 2As shown in the figure, in step S01 of the method, the highway network toll collection data is first classified into seven categories, namely entity basic information, contact information, business information, transaction information, geographical information, vehicle information, and certificate information. Each category of data is composed of multiple field attributes to completely describe various types of data. In step S02, the network toll collection data is divided into level I, level II, and level III, different data processing measures are constructed for data at different levels, and their respective data approval processes are determined. In step S03, for data requests for a single column of attribute field data (single-field data), a single category of attribute data (single-category data), and multi-type data (multi-category data), their respective corresponding data processing levels are determined. For example, S03-1 is a data request for a single column of attribute field data: the seven categories of data are classified according to whether the field attributes are requested and whether they involve sensitive attributes, and each field is divided into level I, level II, or level III. S03-2 is a data request for a single category of attribute data: the seven categories of data are classified according to the situation of separately invoking a category of data, and each category of data is divided into level I, level II, or level III. The number of level I data categories is two (specifically vehicle information and certificate information), the number of level II data categories is two (specifically contact information and geographical information), and the number of level III data categories is three (specifically basic information, transaction information, and business information). S03-3 is a data request for multi-type data: dynamic combination grading of multi-type data is performed, and a multi-type data processing and approval matrix is formed according to the combination of the requested data types. The data processing and approval matrix is shown in Table 1. In step S04, for the data requirements of ETC customer service, the basic data source (Oracle, MySQL, DB2, SQLServer, Alibaba Cloud database, etc.) and the target source (Oracle, MySQL, DB2, SQLServer, Alibaba Cloud database, etc.) are first set to obtain the source data database and the desensitized database; the source data database stores the source data without desensitization processing, and the desensitized database stores the data after desensitization processing. In step S05, combined with the grading rules determined by data fields, data categories, and combined categories, the data processing and approval levels are determined according to the data application requirements (a single column of attribute field data, a single category of attribute data, multi-type data), the corresponding algorithm strategies are selected, and an ETC customer service desensitization template is formulated; the data application requirement for a single column of attribute field data is a single-field data request, the data application requirement for a single category of attribute data is a single-category data request, and the data application requirement for multi-type data is a multi-category data request. In step S06, a data cleaning strategy is set for the ETC customer service source data, and processing such as checking whether fields are the same, data consistency, invalid values, and missing values is performed. For special requirements such as data involving national security, a dictionary rule library is set.Step S07: By creating a new approval task, incorporating data sources / target sources, de - sensitization templates, and cleaning rules, a de - sensitization task application is generated and approved. After approval, the task execution efficiency is improved through a distributed method to desensitize ETC customer service data and support monitoring of task execution status. Step S08: After the task is completed, the desensitized ETC customer service data output can be obtained. The desensitized data is stored in the target database (also known as the desensitization database). ETC customer service obtains the requested data results by calling the target database to ensure the normal operation of the business while protecting user information security.

[0071] Table 1 Multi - type Data Processing and Approval Matrix

[0072]

[0073]

[0074] Figure 3 is a schematic flowchart of the highway network toll data security management method for another embodiment of this application. In Figure 3 , based on the requested data type, a hierarchical classification strategy is selected. Based on the determined hierarchical classification strategy, the data processing level of the to - be - requested highway network toll data is determined, and further, based on the data processing level, a data processing algorithm is determined. After determining the data processing algorithm, a data cleaning strategy is set, and a desensitization task and a desensitization task approval are created. After the desensitization task approval is passed, data cleaning is performed based on the data cleaning strategy. If the data cleaning result meets the requirements, the data is desensitized based on the data processing algorithm determined in the above steps. If the data cleaning result does not meet the requirements, the data cleaning strategy is optimized, and the data is re - cleaned based on the optimized data cleaning strategy. Additionally, if the desensitization task approval is not passed, the requested data is not desensitized, and the data request task is directly ended.

[0075] Figure 4 is a schematic flowchart of the ETC toll suspected over - deduction complaint business for an embodiment of this application. Taking the scenario of ETC toll suspected over - deduction complaint in customer service as an example, ETC users contact the customer service by phone to complain about the over - charged toll. The customer service center accepts the order according to the "first - inquiry responsibility system", verifies the identity information, transaction information, vehicle information, etc., and directly processes it or forwards it to the issuing agency of second - line ETC users for processing. Most of the customer service center staff are third - party outsourced personnel. To avoid exposing customer privacy information, they can only access the desensitized identity information, transaction information, vehicle information, etc. The specific process is as follows:

[0076] I. Pre - preparation:

[0077] 1. The original data of the toll road network toll collection is located in the toll data center, aggregating seven types of toll data.

[0078] 2. The desensitized database of the toll road network toll collection is located in the toll data center and is used to store the desensitized data.

[0079] 3. The source data stored in the original database is desensitized (A -> B) based on the data desensitization method mentioned above, and the desensitized data is stored in the desensitized database.

[0080] II. Processing Flow:

[0081] 1. ETC users call to connect with the intelligent call system.

[0082] 2. The intelligent call system guides users to provide information such as name, ID number, and mobile phone verification code for identity authentication through customized voice services, and forwards the request to the user identity authentication module of the data security control system.

[0083] 3. The user identity authentication module processes the authentication information, including but not limited to verifying the mobile phone verification code, comparing the name and ID number provided by the user with the information retained in the original database, verifying the user's identity, and completing the identity authentication.

[0084] 4. For users who pass the authentication, the user identity authentication module will send a notification of successful authentication to the intelligent call system and the customer service system respectively.

[0085] 5. After receiving the information that the user has passed the authentication, the intelligent call system will connect the circuit link between the customer service center staff and the user and establish an artificial customer service channel.

[0086] 6. The customer service staff records the suspected overcharge claim for the user's ETC toll, so as to query information such as the user's passing records through the customer service system for verification.

[0087] 7. The customer service system carries the user authentication information, passing date, etc., and requests data such as the user's certificate information, transaction information, and vehicle information from the data acquisition module of the data control system.

[0088] 8. The data acquisition module accesses the desensitized database in the toll data center according to the user authentication information, passing date, access personnel permissions, etc.

[0089] 9. The data acquisition module returns the desensitized user certificate information, transaction information, vehicle information, etc. to the customer service system for the customer service staff to verify the information.

[0090] As can be seen from the above embodiments, the highway network toll data of the present application follows the principle of data sensitivity level, with high-sensitivity levels taking precedence, classifying the data into levels one to three, and realizing the desensitization processing of data in typical business scenarios such as ETC customer service through steps such as data application, data template setting, processing level setting, cleaning strategy setting, desensitization task approval, data cleaning, and data desensitization, thereby realizing data security control.

[0091] Correspondingly, the present invention also provides a highway network toll data security management device, which includes a processor, a memory, and a computer program stored on the memory. The processor is used to execute the computer program, and when the computer program is executed, the device realizes the steps of the method described in any of the above embodiments.

[0092] The embodiments of the present invention also provide a computer-readable storage medium and a computer program product, on which a computer program is stored. When the computer program is executed by a processor, it realizes the steps of the method described in any of the above embodiments. The computer-readable storage medium may be a tangible storage medium, such as a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a floppy disk, a hard disk, a removable storage disk, a CD-ROM, or any other form of storage medium known in the technical field.

[0093] Those of ordinary skill in the art should understand that the various exemplary components, systems, and methods described in combination with the embodiments disclosed herein can be implemented in hardware, software, or a combination of both. Specifically, whether to implement in hardware or software depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present invention. When implemented in hardware, it can be, for example, an electronic circuit, an application-specific integrated circuit (ASIC), appropriate firmware, a plug-in, a functional card, etc. When implemented in software, the elements of the present invention are programs or code segments used to execute the required tasks. The program or code segment can be stored in a machine-readable medium or transmitted through a data signal carried in a carrier wave on a transmission medium or a communication link.

[0094] It should be clear that the present invention is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, the detailed description of known methods is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present invention is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order between the steps after understanding the spirit of the present invention.

[0095] In the present invention, features described and / or illustrated for one embodiment can be used in the same way or in a similar way in one or more other embodiments, and / or combined with the features of other embodiments or replace the features of other embodiments.

[0096] The above are only the preferred embodiments of the present invention and are not intended to limit the present invention. For those skilled in the art, various changes and modifications can be made to the embodiments of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.

Claims

1. A method for secure management of highway network toll collection data, characterized in that: The method comprises: Determine the classification categories of highway network toll collection data and the field attributes of the data under each category, and determine the sensitivity level corresponding to each classification category and the sensitivity level corresponding to each field attribute based on the sensitivity of each classification category and the sensitivity of each field attribute; Obtaining a data request, wherein the data request includes a requested data type, and determining a data processing level of the highway network toll collection data to be requested based on the requested data type, the sensitivity level corresponding to each of the classification categories, and the sensitivity level corresponding to each of the field attributes; A data processing algorithm is determined based on the data processing level corresponding to the highway network toll collection data to be requested, and data desensitization is performed on the highway network toll collection data to be requested based on the data processing algorithm to obtain a desensitized data request result.

2. The method for secure management of highway network toll collection data according to claim 1, characterized in that: The request data type is a single-field data request, a single-category data request, or a multi-category data request.

3. The method for secure management of highway network toll collection data according to claim 2, characterized in that: Determining the data processing level of the highway network toll collection data to be requested based on the requested data type, the sensitivity level corresponding to each of the classification categories, and the sensitivity level corresponding to each of the field attributes includes: Determine a grading strategy based on the request data type, where the grading strategy is a single-field grading strategy, a single-category grading strategy, or a multi-category grading strategy; The data processing level of the highway network toll collection data to be requested is determined based on the determined classification strategy, the sensitivity level corresponding to each of the classification categories, and the sensitivity level corresponding to each of the field attributes.

4. The method for secure management of highway network toll collection data according to claim 3, characterized in that: The single field classification strategy includes: taking the sensitivity level corresponding to the field attribute of the highway network toll collection data to be requested as the data processing level; and / or, The single-category classification strategy includes: using the sensitivity level corresponding to the classification category of the highway network toll collection data to be requested as the data processing level; and / or, The multi-category grading strategy includes: if the sensitivity levels of multiple classification categories of the highway network charging data to be requested are all the third level, then the data processing level of the highway network charging data to be requested is the third level; if the sensitivity level of the classification category of at least one type of data in the highway network charging data to be requested is the first level, then the data processing level of the highway network charging data to be requested is the first level; if the sensitivity level of the classification category of at least two types of data in the highway network charging data to be requested is the second level, then the data processing level of the highway network charging data to be requested is the first level; if the sensitivity level of the classification category of only one type of data in the highway network charging data to be requested is the second level, and the sensitivity level of the classification category of at least three types of data is the third level, then the data processing level of the highway network charging data to be requested is the first level; if the sensitivity level of the classification category of only one type of data in the highway network charging data to be requested is the second level, and the sensitivity level of the classification category less than or equal to the two types of data is the third level, then the data processing level of the highway network charging data to be requested is the second level.

5. The method for secure management of highway network toll collection data according to claim 4, characterized in that: Performing data desensitization processing on the to-be-requested highway network toll collection data based on the data processing algorithm includes: Determining a data cleaning strategy corresponding to the data request; Performing data cleaning on the requested highway network toll collection data based on the data cleaning strategy; Based on the data processing algorithm, the unrequested highway network toll collection data after data cleaning is desensitized.

6. The method for secure management of highway network toll collection data according to claim 5, characterized in that: Before performing data cleaning on the requested highway network toll collection data based on the data cleaning strategy, the following steps are included: Generate a desensitization task based on the highway network toll collection data to be requested, the data processing level, and the data cleaning strategy; An approval result is determined based on the desensitization task.

7. The method for secure management of highway network toll collection data according to claim 6, characterized in that: The requested highway network toll collection data is cleaned based on the data cleaning strategy, including: Optimizing the data cleaning strategy to obtain an optimized data cleaning strategy; The requested highway network toll collection data is cleaned based on the optimized data cleaning strategy.

8. The method for secure management of highway network toll collection data according to claim 4, characterized in that: The classification categories of the highway network charging data include: basic entity information, contact information, business information, transaction information, geographic information, vehicle information and certificate information; and / or The data processing algorithms corresponding to the first level include masking, encryption, truncation or offset rounding; The data processing algorithms corresponding to the second level include masking, encryption, truncation, offset rounding, synonym replacement or rearrangement.

9. A highway network toll data security management device, the device comprising a processor, a memory and a computer program stored in the memory, characterized in that: The processor is used to execute the computer program. When the computer program is executed, the device implements the steps of the method according to any one of claims 1 to 8.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.

Images