Charging and stopping integrated data management method and system

Abstract

The application belongs to the field of parking lot management, and discloses a parking and charging integrated data management method and system. The method comprises the following steps: S1, when detecting that data changes, a server of a management system of a parking lot sends a communication request for establishing a communication connection to a server of a unified management platform; S2, after receiving the communication request, the server of the unified management platform judges whether the current CPU usage rate exceeds a set threshold, if not, the server sends a first confirmation notification to the server of the management system of the parking lot, if yes, the server calculates a priority coefficient of the communication request and enters S3; S3, the server of the unified management platform sends a waiting notification to the server of the management system of the parking lot; and S4, the server of the unified management platform processes the communication request according to the priority coefficient. The application can preferentially receive important data, so that the emergency of the parking lot can be managed more timely, and the effect of uniformly managing the parking lot is ensured.

Description

Technical Field

[0001] This invention relates to the field of parking lot management, and more particularly to a method and system for integrated parking and charging data management. Background Technology

[0002] To manage parking lots under the same company, existing technologies typically establish a unified management platform, which is then connected to the management system of each parking lot to achieve unified management of all parking lots.

[0003] The parking management system's server establishes a communication connection with the unified management platform's server, enabling it to transmit the latest data to the unified management platform when parking data changes. Because parking data (such as entry / exit data, charging data, etc.) typically changes frequently during peak hours (e.g., 8-9 PM), when there are many parking management systems, the unified management platform may receive too many connection requests simultaneously. This could cause some parking management system servers to fail to connect in time to upload important data (such as alarm data), thus affecting the timely reception and processing of critical data and consequently impacting the effectiveness of unified parking management. Summary of the Invention

[0004] The purpose of this invention is to disclose an integrated data management method and system for charging and stopping, thereby solving the technical problems mentioned in the background art.

[0005] To achieve the above objectives, the present invention adopts the following technical solution:

[0006] In a first aspect, the present invention provides a method for integrated data management of charging and stopping, comprising:

[0007] S1, When a change in data is detected, the parking lot management system server sends a communication request to the unified management platform server to establish a communication connection.

[0008] S2: After receiving the communication request, the server of the unified management platform determines whether the current CPU utilization exceeds the set threshold. If not, it sends the first confirmation notification to the server of the parking lot management system. If so, it calculates the priority coefficient of the communication request and proceeds to S3.

[0009] S3, the server of the unified management platform sends a waiting notification to the server of the parking management system;

[0010] S4, the unified management platform's server processes communication requests based on priority levels;

[0011] The priority coefficient is obtained by weighted summation of the normalized values ​​of the data type coefficient, time-related attenuation coefficient, access characteristic coefficient, and transmission quality coefficient.

[0012] Furthermore, the communication request includes the data type, data size, and first synchronization sequence number.

[0013] Furthermore, the first confirmation notification includes a second synchronization sequence number and a third synchronization sequence number;

[0014] The second synchronization sequence number is obtained by adding 1 to the first synchronization sequence number.

[0015] Furthermore, after receiving the first confirmation notification, the parking management system server generates a fourth synchronization sequence number based on the third synchronization sequence number; the fourth synchronization sequence number is obtained by adding 1 to the third synchronization sequence number.

[0016] And generate a second confirmation notification including a second synchronization sequence number and a fourth synchronization sequence number and send it to the server of the unified management platform.

[0017] Furthermore, after receiving the second confirmation notification, the server of the unified management platform determines whether the second synchronization sequence number and the fourth synchronization sequence number are correct. If so, it establishes a communication connection with the server of the parking lot management system.

[0018] Furthermore, the waiting notification includes the retransmission duration.

[0019] Furthermore, after receiving the waiting notification, the parking management system server starts a countdown. The countdown duration is equal to the retransmission duration. When the countdown ends, it resends the communication request to the unified management platform server to establish a communication connection.

[0020] Furthermore, communication requests are processed according to priority levels, including:

[0021] Priority coefficients are updated based on an adaptive update cycle;

[0022] Within each update cycle, each communication request is processed sequentially according to its priority coefficient from largest to smallest, and a first confirmation notification is sent to the server of the parking management system corresponding to the communication request.

[0023] Furthermore, the adaptive update cycle update process includes:

[0024] The update cycle is calculated based on the data type coefficient, business period coefficient, and load coefficient of the communication request.

[0025] Secondly, the present invention provides an integrated parking and charging data management system, including a server for a parking management system and a server for a unified management platform;

[0026] The parking lot management system's server is used to send a communication request to the unified management platform's server to establish a communication connection when it detects a change in data.

[0027] The server of the unified management platform is used to determine whether the current CPU utilization exceeds the set threshold after receiving a communication request. If not, it sends a first confirmation notification to the server of the parking lot management system; if so, it calculates the priority coefficient of the communication request.

[0028] The unified management platform's server is also used to send a waiting notification to the parking management system's server after calculating the priority coefficient;

[0029] The unified management platform's servers are also used to process communication requests based on priority levels;

[0030] The priority coefficient is obtained by weighted summation of the normalized values ​​of the data type coefficient, time-related attenuation coefficient, access characteristic coefficient, and transmission quality coefficient.

[0031] Beneficial effects:

[0032] This invention calculates a priority coefficient based on communication requests, enabling the unified management platform's server to control the receiving order of data of varying importance when the server is at full load. This avoids simply sorting data according to the time of receipt, allowing for a comprehensive assessment of the importance of communication requests and prioritizing the reception of important data. This facilitates more timely management of parking lot emergencies, effectively ensuring the unified management of parking lots. Attached Figure Description

[0033] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0034] Figure 1 This is a schematic diagram of the integrated charging and stopping data management method of the present invention.

[0035] Figure 2 This is a schematic diagram of the integrated charging and stopping data management system of the present invention. Detailed Implementation

[0036] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. The components of the embodiments of the present invention described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present invention provided in the accompanying drawings is not intended to limit the scope of the claimed invention, but merely to illustrate selected embodiments of the invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without inventive effort are within the scope of protection of the present invention.

[0037] Example 1:

[0038] like Figure 1 As shown in one embodiment, the present invention provides an integrated data management method for charging / stopping, comprising:

[0039] S1, when a change in data is detected, the parking lot management system server sends a communication request to the unified management platform server to establish a communication connection.

[0040] Specifically, data changes can occur either by altering the value of existing data or by detecting the generation of new data.

[0041] For example, if the number of vehicles entering a parking lot is continuously counted within a certain period, then this number of vehicles will change over time.

[0042] New data can be generated, such as new user registrations.

[0043] In this invention, the data includes parking data and charging data of parking lots, thus enabling centralized management of parking lot and charging pile operation data nationwide.

[0044] The parking management system's server connects to the parking gate to obtain all parking lot entry and exit records and orders using different gates; it also connects to charging piles to enable the platform to uniformly manage charging orders and remotely control the start and stop of charging piles.

[0045] By managing parking lot and charging pile data through a unified management platform, one can view overall operational data or parking or charging data for individual projects, and also gain a comprehensive understanding of equipment operation and early warning status.

[0046] Furthermore, the communication request includes the data type, data size, and first synchronization sequence number.

[0047] Specifically, data types include urgent data, core data, regular data, and batch data. Each communication request includes only one data type.

[0048] Data size refers to the storage space occupied by the data.

[0049] The first synchronization sequence number is a sequence number generated using a pseudo-random number generator (PRNG). The first synchronization sequence number can be a 32-bit sequence number.

[0050] Randomly generated initial sequence numbers can effectively prevent replay attacks. If an attacker intercepts data packets for a connection and attempts to retransmit them, because the initial sequence number is random, it is difficult for the attacker to forge a legitimate sequence number that matches the current connection state, thus preventing a successful replay attack.

[0051] For example:

[0052] If an attacker intercepts a data packet with sequence number X + 10 sent by the parking management system server, and attempts to resend this packet to the unified management platform server, the unified management platform server will detect the duplicate sequence number X + 10 and discard it because it already received the packet with sequence number X + 10, and subsequent packets should have sequence numbers like X + 11, X + 12, etc. Even if the attacker attempts to forge a new data packet, the unified management platform server will reject it because it cannot predict the correct sequence number.

[0053] Furthermore, emergency data includes fault alarms (damaged gates), security incidents, fire alarms, etc.

[0054] The core data includes vehicle entry and exit records, real-time parking space status, and payment results.

[0055] Routine data includes equipment heart rate monitoring results, ambient temperature and humidity, etc.

[0056] Batch data includes historical logs, statistical reports, etc.

[0057] S2: After receiving the communication request, the server of the unified management platform determines whether the current CPU utilization exceeds the set threshold. If not, it sends the first confirmation notification to the server of the parking lot management system. If so, it calculates the priority coefficient of the communication request and proceeds to S3.

[0058] Furthermore, the threshold can be set to 90%. When the threshold is exceeded, it indicates that the server is close to full load, so accepting new data for processing is paused.

[0059] Furthermore, the first confirmation notification includes a second synchronization sequence number and a third synchronization sequence number;

[0060] The second synchronization sequence number is obtained by adding 1 to the first synchronization sequence number.

[0061] The second synchronization sequence number is used to enable the parking management system server to confirm that the unified management platform server has received the communication request it sent.

[0062] Furthermore, the third synchronization sequence number is a sequence number generated by a pseudo-random number generator on the unified management platform server, and its length can be 32 bits.

[0063] Furthermore, after receiving the first confirmation notification, the parking management system server generates a fourth synchronization sequence number based on the third synchronization sequence number; the fourth synchronization sequence number is obtained by adding 1 to the third synchronization sequence number.

[0064] And generate a second confirmation notification including a second synchronization sequence number and a fourth synchronization sequence number and send it to the server of the unified management platform.

[0065] Specifically, the fourth synchronization sequence number is used by the unified management platform server to confirm that the parking management system server has received the first confirmation notification it sent.

[0066] The second synchronization sequence number is the sequence number of the next data packet of the parking management system server, indicating that the parking management system server has received the first confirmation notification from the unified management platform server and is ready to send the next data packet.

[0067] Fourth synchronization sequence number: This indicates that the parking management system server has received the first confirmation notification from the unified management platform server and expects the next data packet from the unified management platform server to have the fourth synchronization sequence number.

[0068] Furthermore, after receiving the second confirmation notification, the server of the unified management platform determines whether the second synchronization sequence number and the fourth synchronization sequence number are correct. If so, it establishes a communication connection with the server of the parking lot management system.

[0069] Specifically, if the second confirmation notification received does not contain the second synchronization sequence number generated by the unified management platform's server, it indicates that the second synchronization sequence number is incorrect.

[0070] If the fourth synchronization sequence number is not obtained by adding 1 to the third synchronization sequence number, it means that the fourth synchronization sequence number is incorrect.

[0071] Furthermore, the priority coefficient is obtained by weighted summation of the normalized values ​​of the data type coefficient, time-related attenuation coefficient, access characteristic coefficient, and transmission quality coefficient.

[0072] Specifically, in this invention, the data type coefficients for emergency data, core data, regular data, and batch data are set to 5, 4, 3, and 1, respectively.

[0073] Correspondingly, the normalized values ​​of the data type coefficients for emergency data, core data, regular data, and batch data are 1, 0.75, 0.5, and 0, respectively.

[0074] The formula for calculating the normalized value of the aging decay coefficient is as follows:

[0075]

[0076] This is the time-related decay coefficient. This is the time when the priority coefficient calculation begins. The time when the priority coefficient of the first communication request is calculated. This indicates the preset duration. This indicates normalized calculation.

[0077] In this invention, the preset duration can be 3 seconds.

[0078] The formula for calculating the access characteristic coefficient is:

[0079]

[0080] This indicates normalized calculation. For access characteristic coefficients, This refers to the total number of times data of the same type as the data contained in the communication request is read from the server of the unified management platform within a preset time interval. This represents the maximum number of times data of various data types is read from the unified management platform's server within a preset time interval.

[0081] The preset time range can be . This indicates the preset interval length (e.g., 1 hour).

[0082] like Less than or equal to The formula for calculating the transmission quality coefficient is:

[0083]

[0084] This indicates normalized calculation. Indicates the transmission quality factor. The communication latency between the parking management system server and the unified management platform server (for example, the average of the last 5 communication latency can be used as...) (value) The preset communication delay (e.g., 5 seconds).

[0085] like Greater than Then Set to 0.

[0086] Specifically, the formula for calculating the priority coefficient is as follows:

[0087]

[0088] , , and These are the normalized weights of the data type coefficient, timeliness attenuation coefficient, access characteristic coefficient, and transmission quality coefficient, respectively. `typ` is the normalized value of the data type coefficient corresponding to the data type included in the communication request. `prio` represents the priority coefficient.

[0089] The priority coefficients of this invention are calculated by weighting observation values ​​from multiple different directions, thus more accurately representing the urgency of data requests. A larger timeliness attenuation coefficient indicates a longer waiting time for the communication request; a larger access characteristic coefficient indicates that this type of data is read more frequently by the unified management platform server; and a larger transmission quality coefficient indicates faster communication speed between the parking management system server and the unified management platform server, allowing data transmission to be completed in a shorter time. Therefore, a larger data type coefficient, a larger timeliness attenuation coefficient, a larger access characteristic coefficient, and a larger transmission quality coefficient indicate that the communication request is processed with higher priority, enabling more timely management of parking emergency situations and effectively ensuring the unified management of parking lots.

[0090] In this invention, the weights of the normalized values ​​of the data type coefficient, time-related attenuation coefficient, access characteristic coefficient, and transmission quality coefficient can be 0.4, 0.3, 0.2, and 0.1, respectively.

[0091] S3: The server of the unified management platform sends a waiting notification to the server of the parking management system.

[0092] Specifically, sending a waiting notification can prevent the parking management system's server from resending communication requests too frequently, thus reducing the processing pressure on the unified management platform's server.

[0093] Furthermore, the waiting notification includes the retransmission duration.

[0094] In this invention, the retransmission duration is related to the priority coefficient, and its calculation formula is as follows:

[0095]

[0096] tpre is the retransmission duration, where tpre is the preset maximum retransmission duration.

[0097] The retransmission duration of this invention can vary with the priority coefficient. Therefore, the more urgent the data, the shorter its retransmission duration. This allows the unified management platform's server to prioritize receiving and processing data with high urgency.

[0098] In this invention, the maximum retransmission duration can be 3 seconds.

[0099] Furthermore, after receiving the waiting notification, the parking management system server starts a countdown. The countdown duration is equal to the retransmission duration. When the countdown ends, it resends the communication request to the unified management platform server to establish a communication connection.

[0100] The countdown is performed to wait for the unified management platform server to send the first confirmation notification. This reduces the proximity of the resending of communication requests between the servers of different parking management systems and the unified management platform server, thereby reducing the data processing pressure on the unified management platform server.

[0101] Furthermore, if a first confirmation notification is received from the unified management platform server during the countdown, the countdown will stop, and a second confirmation notification will be generated and sent to the unified management platform server.

[0102] S4, the unified management platform's server, processes communication requests based on priority levels.

[0103] Furthermore, communication requests are processed according to priority levels, including:

[0104] Priority coefficients are updated based on an adaptive update cycle;

[0105] Within each update cycle, each communication request is processed sequentially according to its priority coefficient from largest to smallest, and a first confirmation notification is sent to the server of the parking management system corresponding to the communication request.

[0106] Specifically, for low-urgency data, it may take a relatively long time to be received and processed, but it cannot remain unprocessed indefinitely. Therefore, this invention reduces the time it takes for low-urgency data to be processed by periodically updating the priority coefficient of communication requests that have not yet been processed.

[0107] Furthermore, communication requests that have not yet been processed are those whose time interval between the moment they were received and the current moment is less than the maximum retransmission duration. If the time interval is greater than the maximum retransmission duration, the corresponding communication request will be deleted.

[0108] Furthermore, the adaptive update cycle update process includes:

[0109] The update cycle is calculated based on the data type coefficient, business period coefficient, and load coefficient of the communication request.

[0110] Specifically, the formula for calculating the update cycle is:

[0111]

[0112] upt represents the update cycle, and U represents the set of communication requests that have not yet been processed after the end of the previous update cycle. Here, NU represents the normalized value of the data type coefficient corresponding to communication request i, and NU represents the total number of communication requests contained in U. The business time period coefficient timtyp is determined by the following rules: if the current time is a peak time period, the value of timtyp is 0, otherwise it is 1. The load coefficient load is determined by the following rules: if the CPU utilization of the unified management platform server is greater than 0.8 times the set threshold at the current time, then load is 0, otherwise load is 1. bt is the set update period. , and These are the weights for data type coefficient, business period coefficient, and load coefficient, respectively.

[0113] The update cycle of this invention is calculated by comprehensively considering the urgency of communication requests, the business hours, and the server's CPU utilization. During peak hours and when CPU utilization is high, a longer update cycle is used to update the priority coefficients of communication requests. This allows computing resources to be prioritized for the actual processing of communication requests (e.g., receiving data, calculating data), thereby reducing the impact of priority updates on the processing speed of communication requests. Conversely, when the overall urgency of communication requests in U is high, a shorter update cycle is used to update the priority coefficients, effectively increasing the probability that more urgent communication requests are processed first. This invention effectively balances processing speed and urgency, resulting in better overall processing performance.

[0114] In this invention, the update cycle can be set to 1 second. The peak period can be from 8:00 to 21:00.

[0115] In this invention, the weights of the data type coefficient, the business period coefficient, and the load coefficient are 0.5, 0.3, and 0.2, respectively.

[0116] like Figure 2 As shown, the present invention also provides an integrated parking and charging data management system, including a server for the parking lot management system and a server for the unified management platform;

[0117] The parking lot management system's server is used to send a communication request to the unified management platform's server to establish a communication connection when it detects a change in data.

[0118] The server of the unified management platform is used to determine whether the current CPU utilization exceeds the set threshold after receiving a communication request. If not, it sends a first confirmation notification to the server of the parking lot management system; if so, it calculates the priority coefficient of the communication request.

[0119] The unified management platform's server is also used to send a waiting notification to the parking management system's server after calculating the priority coefficient;

[0120] The unified management platform's servers are also used to process communication requests based on priority levels;

[0121] The priority coefficient is obtained by weighted summation of the normalized values ​​of the data type coefficient, time-related attenuation coefficient, access characteristic coefficient, and transmission quality coefficient.

[0122] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for integrated data management of cut-off, characterized in that, Comprise: S1, when detecting data changes, the server of the parking lot management system sends a communication request for establishing a communication connection to the server of the unified management platform; S2, after receiving the communication request, the server of the unified management platform judges whether the current CPU usage rate exceeds the set threshold, if not, the first confirmation notification is sent to the server of the parking lot management system; if yes, the priority coefficient of the communication request is calculated, and S3 is entered; S3, the server of the unified management platform sends a waiting notification to the server of the parking lot management system; S4, the server of the unified management platform processes the communication request according to the priority coefficient; Wherein, the priority coefficient is obtained by weighted summation of the normalized values of data type coefficient, time decay coefficient, access feature coefficient and transmission quality coefficient; Processing the communication request according to the priority coefficient comprises: Updating the priority coefficient based on adaptive update cycle; In each update cycle, each communication request is processed in turn according to the order from large to small according to the priority coefficient, and the first confirmation notification is sent to the server of the parking lot management system corresponding to the communication request; The update process of adaptive update cycle comprises: Calculating the update cycle based on the data type coefficient, business period coefficient and load coefficient of the communication request; The calculation formula of the update cycle is: ； UPT is an update period, U is a set of communication requests that have not been processed since the end of the last update period, is a normalized value of the data type coefficient corresponding to the communication request i, NU represents the total number of communication requests contained in U, the value of the service period coefficient timtyp is: if the current time is a peak period, the value of timtyp is 0, otherwise it is 1; the value of the load coefficient load is: if the CPU usage rate of the server of the unified management platform at the current time is greater than 0.8 times of the set threshold, load is 0, otherwise load is 1; bt is a set update period; , and are the weights of the data type coefficient, the service period coefficient and the load coefficient respectively.

2. The integrated charge termination data management method of claim 1, wherein The communication request includes data type, data size and first synchronization sequence number.

3. The integrated charge termination data management method of claim 1, wherein The first confirmation notification includes second synchronization sequence number and third synchronization sequence number; The second synchronization sequence number is obtained by adding 1 to the first synchronization sequence number.

4. The integrated charge termination data management method of claim 3, wherein After receiving the first confirmation notification, the server of the parking lot management system generates a fourth synchronization sequence number based on the third synchronization sequence number; the fourth synchronization sequence number is obtained by adding 1 to the third synchronization sequence number; And generate a second confirmation notification including the second synchronization sequence number and the fourth synchronization sequence number and send it to the server of the unified management platform.

5. The integrated charge termination data management method of claim 4, wherein After receiving the second confirmation notification, the server of the unified management platform judges whether the second synchronization sequence number and the fourth synchronization sequence number are correct, if yes, the communication connection is established with the server of the parking lot management system.

6. The integrated charge termination data management method of claim 1, wherein The waiting notification includes retransmission duration.

7. The integrated charge termination data management method of claim 6, wherein After receiving the waiting notification, the server of the parking lot management system performs countdown, and the duration of countdown is equal to the retransmission duration, when the countdown ends, the communication request for establishing a communication connection is sent to the server of the unified management platform again.

8. The integrated data management system of claim 1, wherein, The server of the parking lot management system and the server of the unified management platform are included; The server of the parking lot management system is used to send a communication request for establishing a communication connection to the server of the unified management platform when detecting data changes; The server of the unified management platform is used to judge whether the current CPU usage rate exceeds the set threshold after receiving the communication request, if not, the first confirmation notification is sent to the server of the parking lot management system; if yes, the priority coefficient of the communication request is calculated; The server of the unified management platform is also used to send a waiting notification to the server of the parking lot management system after completing the calculation of the priority coefficient; The server of the unified management platform is further configured to process the communication requests according to the priority coefficients; The priority coefficient is obtained by weighted summation of normalized values of the data type coefficient, the time decay coefficient, the access feature coefficient and the transmission quality coefficient; The processing of the communication requests according to the priority coefficients comprises: The priority coefficients are updated based on an adaptive update period; In each update period, each communication request is processed in turn according to the order from large to small of the priority coefficients, and a first confirmation notification is sent to the server of the management system of the parking lot corresponding to the communication request; The update process of the adaptive update period comprises: The update period is calculated based on the data type coefficient, the business time period coefficient and the load coefficient of the communication request; The calculation formula of the update period is: ； UPT is an update period, U is a set of communication requests that have not been processed since the end of the last update period, is a normalized value of the data type coefficient corresponding to the communication request i, NU represents the total number of communication requests contained in U, the value of the service period coefficient timtyp is: if the current time is a peak period, the value of timtyp is 0, otherwise it is 1; the value of the load coefficient load is: if the CPU usage rate of the server of the unified management platform at the current time is greater than 0.8 times of the set threshold, load is 0, otherwise load is 1; bt is a set update period; , and are the weights of the data type coefficient, the service period coefficient and the load coefficient respectively.

Images