Stopping and charging integrated data management method and system

Abstract

The invention belongs to the field of parking lot management, and discloses a parking and charging integrated data management method and system, and the method comprises the steps: S1, enabling a server of a management system of a parking lot to transmit a communication request for building communication connection to a server of a unified management platform when the change of data is detected; s2, after the server of the unified management platform receives the communication request, judging whether the current CPU utilization rate exceeds a set threshold value or not, and if not, sending a first confirmation notification to the server of the management system of the parking lot; if yes, calculating a priority coefficient of the communication request, and entering 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. According to the invention, important data can be received preferentially, so that the emergency situation of the parking lot can be managed more timely, and the effect of unified management of the parking lot is ensured.

Description

Technical Field

[0001] The present invention relates to the field of parking lot management, and in particular to a parking and charging integrated data management method and system. Background Art

[0002] In order to manage parking lots under the same company, existing technologies usually establish a unified management platform, and connect the unified management platform with the management system of each parking lot, so as to achieve unified management of all parking lots.

[0003] The parking management system's servers establish a communication connection with the unified management platform's servers, allowing them to transmit the latest data to the unified management platform whenever the parking lot's data changes. Since parking lot data (such as entry and exit data and charging data) typically changes frequently during active hours (e.g., 8:00-21:00), when there are many parking management systems, the unified management platform may receive too many connection requests at the same time, causing some parking management system servers to fail to connect to it in time to upload important data (such as alarm data). This can affect the timely reception and processing of important data, and in turn, the effectiveness of unified parking management. Summary of the Invention

[0004] The purpose of the present invention is to disclose a method and system for managing data of a vehicle that is integrated with charging and stopping, so as to solve the technical problems pointed out in the background technology.

[0005] In order to achieve the above object, the present invention adopts the following technical solutions: In a first aspect, the present invention provides a method for managing data of a vehicle stopping and charging system, comprising: S1, when detecting a data change, the parking lot management system server sends a communication request for establishing a communication connection to the unified management platform server; S2, after receiving the communication request, the server of the unified management platform determines whether the current CPU usage exceeds the set threshold. 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 and enters S3; 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; The priority coefficient is obtained by weighted summing the normalized values ​​of the data type coefficient, the time decay coefficient, the access characteristic coefficient, and the transmission quality coefficient.

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

[0007] Further, the first confirmation notification includes the second synchronization sequence number and the third synchronization sequence number; The second synchronization sequence number is obtained by adding 1 to the first synchronization sequence number.

[0008] Furthermore, 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.

[0009] 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, a communication connection is established with the server of the parking lot management system.

[0010] Furthermore, the waiting notification includes a retransmission duration.

[0011] Furthermore, after receiving the waiting notification, the server of the parking lot management system performs a countdown, where the countdown duration is equal to the retransmission duration. When the countdown ends, the server re-sends a communication request for establishing a communication connection to the server of the unified management platform.

[0012] Furthermore, the communication request is processed according to the priority coefficient, including: Update priority coefficients based on adaptive update cycles; In each update period, each communication request is processed in descending order of priority coefficient, and a first confirmation notification is sent to the server of the management system of the parking lot corresponding to the communication request.

[0013] Furthermore, the update process of the adaptive update cycle includes: The update period is calculated based on the data type coefficient, service period coefficient and load coefficient of the communication request.

[0014] In a second aspect, the present invention provides a parking and charging integrated data management system, including a parking lot management system server and a unified management platform server; 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 a change in data; The server of the unified management platform is used to determine whether the current CPU usage exceeds a set threshold after receiving the 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; The server of the unified management platform is further 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 also used to process communication requests according to priority coefficients; The priority coefficient is obtained by weighted summing the normalized values ​​of the data type coefficient, the time decay coefficient, the access characteristic coefficient, and the transmission quality coefficient.

[0015] Beneficial effects: The present invention calculates the priority coefficient based on the communication request, so that when the server of the unified management platform is in a fully loaded state, the order of receiving data of different importance can be controlled based on the priority coefficient, thereby avoiding simple sorting according to the reception time of the communication request. In this way, it is possible to comprehensively consider multiple factors to evaluate the importance of the communication request and give priority to receiving important data, so that emergency situations in the parking lot can be managed more promptly, thereby effectively ensuring the effect of unified management of the parking lot. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the embodiments. It should be understood that the following drawings only illustrate certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can be obtained based on these drawings without paying any creative work.

[0017] Figure 1 Schematic diagram of the charging and stopping integrated data management method of the present invention.

[0018] Figure 2 Schematic diagram of the charging and stopping integrated data management system of the present invention. DETAILED DESCRIPTION

[0019] The technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments. The components of the embodiments of the present invention generally described and shown in the drawings herein can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present invention provided in the drawings is not intended to limit the scope of the claimed invention, but merely represents selected embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without making creative work are within the scope of protection of the present invention.

[0020] Example 1: like Figure 1 In one embodiment shown, the present invention provides a method for managing data of charging and stopping, including: S1, when detecting a data change, 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.

[0021] Specifically, the data change may be a change in the value of the original data or a detection that new data is generated.

[0022] For example, if the number of vehicles entering a parking lot within a certain period is continuously counted, the number of vehicles entering the parking lot will also change as time changes.

[0023] New data may be generated by new user registration, etc.

[0024] In the present invention, the data includes parking data and charging data of the parking lot, so the present invention can realize the centralized management of parking lot and charging pile operation data across the country.

[0025] The parking lot management system's server connects to the parking lot gates to obtain all parking lot entry and exit records and orders using different gates; it also connects to the charging piles to enable the platform to centrally manage charging orders and remotely control the start and stop of charging piles; Through the unified management of parking lot data and charging pile data on a unified management platform, you can view the overall operating data or the parking or charging data of a single project, and also know the equipment operation status and equipment warning status from a general level.

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

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

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

[0029] The first synchronization sequence number is a sequence number generated by a pseudo-random number generator (PRNG) and may be a 32-bit sequence number.

[0030] Randomly generated initial sequence numbers effectively prevent replay attacks. If an attacker intercepts a packet from a connection and attempts to resend it, the random initial sequence number makes it difficult for the attacker to forge a legitimate sequence number that matches the current connection state, thus preventing a successful replay attack.

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

[0032] Furthermore, emergency data includes fault alarms (damaged barriers), safety accidents, fire alarms, etc.

[0033] Core data includes vehicle entry and exit records, real-time parking space status, payment results, etc.

[0034] General data includes device heartbeat detection results, ambient temperature and humidity, etc.

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

[0036] S2, after receiving the communication request, the server of the unified management platform determines whether the current CPU usage exceeds the set threshold. 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 and enters S3.

[0037] Furthermore, the threshold value may be set to 90%. When the threshold value is exceeded, it indicates that the server is close to being fully loaded, and therefore, the server stops accepting new data for processing.

[0038] Further, the first confirmation notification includes the second synchronization sequence number and the third synchronization sequence number; The second synchronization sequence number is obtained by adding 1 to the first synchronization sequence number.

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

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

[0041] Furthermore, 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.

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

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

[0044] Fourth synchronization sequence number: used to indicate that the server of the parking lot management system has received the first confirmation notification from the server of the unified management platform, and expects that the sequence number of the next data packet from the server of the unified management platform is the fourth synchronization sequence number.

[0045] 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, a communication connection is established with the server of the parking lot management system.

[0046] Specifically, if the second synchronization sequence number generated by the server of the unified management platform does not exist in the received second confirmation notification, it means that the second synchronization sequence number is incorrect; 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.

[0047] Furthermore, the priority coefficient is obtained by weighted summing the normalized values ​​of the data type coefficient, the time decay coefficient, the access characteristic coefficient, and the transmission quality coefficient.

[0048] Specifically, in the present invention, the data type coefficients corresponding to urgent data, core data, regular data and batch data are set to 5, 4, 3 and 1 respectively.

[0049] Correspondingly, the normalized values ​​of the data type coefficients corresponding to urgent data, core data, regular data, and batch data are 1, 0.75, 0.5, and 0, respectively.

[0050] The calculation formula for the normalized value of the aging attenuation coefficient is:

[0051] is the time-dependent attenuation coefficient, The time when the priority coefficient is calculated. is the time when the priority coefficient of the communication request is first calculated, Indicates the preset duration. Represents normalized calculation.

[0052] In the present invention, the preset duration may be 3 seconds.

[0053] The calculation formula of the access characteristic coefficient is:

[0054] represents the normalized calculation, To access the characteristic coefficients, The total number of times that data of the same type as the data included in the communication request is read on the server of the unified management platform within a preset time interval, It is the maximum total number of times that data of various data types are read on the server of the unified management platform within a preset time interval.

[0055] The preset time interval can be . Indicates the preset interval length (for example, 1 hour).

[0056] like Less than or equal to , the calculation formula of the transmission quality coefficient is:

[0057] represents the normalized calculation, represents the transmission quality coefficient, The communication delay between the server of the parking lot management system and the server of the unified management platform (for example, the average value of the last five communication delays can be used as ), is the preset communication delay (e.g. 5 seconds).

[0058] like Greater than , then Set to 0.

[0059] Specifically, the calculation formula of the priority coefficient is as follows:

[0060] 、 、 and The weights of the normalized values ​​of the data type coefficient, time decay coefficient, access characteristic coefficient, and transmission quality coefficient, respectively. typ is the normalized value of the data type coefficient corresponding to the data type contained in the communication request. prio represents the priority coefficient.

[0061] The priority coefficient of the present invention is obtained by weighted calculation based on observation values ​​from multiple different directions. Therefore, it can more accurately represent the urgency of the data request. The larger the time decay coefficient, the longer the waiting time for the communication request. The larger the access characteristic coefficient, the more frequently this type of data is read by the server of the unified management platform. The larger the transmission quality coefficient, the faster the communication speed between the server of the parking lot management system and the server of the unified management platform, and the shorter the time it takes for data transmission to be completed. Therefore, if the data type coefficient is larger, the time decay coefficient is larger, the access characteristic coefficient is larger, and the transmission quality coefficient is larger, the communication request will be processed with higher priority, so that the emergency situation of the parking lot can be managed more promptly, which can effectively ensure the effect of unified management of the parking lot.

[0062] In the present invention, the weights of the normalized values ​​of the data type coefficient, the time decay coefficient, the access characteristic coefficient, and the transmission quality coefficient may be 0.4, 0.3, 0.2, and 0.1, respectively.

[0063] S3, the server of the unified management platform sends a waiting notification to the server of the parking lot management system.

[0064] Specifically, sending the waiting notification can prevent the server of the parking lot management system from resending the communication request too frequently, thereby alleviating the processing pressure of the server of the unified management platform.

[0065] Furthermore, the waiting notification includes a retransmission duration.

[0066] In the present invention, the retransmission duration is related to the priority coefficient, and its calculation formula is:

[0067] is the retransmission time, and tpre is the preset maximum retransmission time.

[0068] The retransmission duration of the present invention can vary with the change of the priority coefficient. Therefore, the more urgent the data is, the shorter the retransmission duration is. In this way, the server of the unified management platform can give priority to receiving and processing the data with high urgency.

[0069] In the present invention, the maximum retransmission duration may be 3 seconds.

[0070] Furthermore, after receiving the waiting notification, the server of the parking lot management system performs a countdown, where the countdown duration is equal to the retransmission duration. When the countdown ends, the server re-sends a communication request for establishing a communication connection to the server of the unified management platform.

[0071] The countdown is to wait for the server of the unified management platform to send the first confirmation notification, reduce the proximity of the time when the servers of different parking management systems and the server of the unified management platform resend communication requests, and thus reduce the data processing pressure of the server of the unified management platform.

[0072] Furthermore, if a first confirmation notification is received from the server of the unified management platform during the countdown, the countdown is stopped, and a second confirmation notification is generated and sent to the server of the unified management platform.

[0073] S4, the server of the unified management platform processes the communication request according to the priority coefficient.

[0074] Furthermore, the communication request is processed according to the priority coefficient, including: Update priority coefficients based on adaptive update cycles; In each update period, each communication request is processed in descending order of priority coefficient, and a first confirmation notification is sent to the server of the management system of the parking lot corresponding to the communication request.

[0075] Specifically, for data with low urgency, it may take a long time to be received and processed, but it cannot be left unprocessed. Therefore, the present invention can reduce the time it takes for data with low urgency to wait for processing by regularly updating the priority coefficients of communication requests that have not yet been processed.

[0076] Furthermore, the communication request that has not yet been processed is a communication request whose time length from the moment the communication request is received to the current moment is less than the maximum retransmission duration. If the time length is greater than the maximum retransmission duration, the corresponding communication request is deleted.

[0077] Furthermore, the update process of the adaptive update cycle includes: The update period is calculated based on the data type coefficient, service period coefficient and load coefficient of the communication request.

[0078] Specifically, the calculation formula for the update period is:

[0079] upt is the update period, U is the set of communication requests that have not been processed since the end of the previous update period, is the normalized value of the data type coefficient corresponding to communication request i, NU represents the total number of communication requests contained in U, and the value of the business period coefficient timtyp is set as follows: if the current time is the peak period, then the value of timtyp is 0, otherwise it is 1; the value of the load coefficient load is set as follows: if the CPU usage of the server of the unified management platform is greater than 0.8 times the set threshold, then load is 0, otherwise load is 1; bt is the set update period; 、 and They are the weights of data type coefficient, business period coefficient and load coefficient respectively.

[0080] The update cycle of the present invention is calculated by comprehensively considering the urgency of communication requests, the business hours, and the server's CPU usage. During peak hours and when CPU usage is high, the longer the update cycle, the more priority coefficients are updated for communication requests. This allows computing resources to be prioritized for the actual processing of communication requests (e.g., receiving data, calculating data, etc.), thereby reducing the impact of priority coefficient updates on the processing speed of communication requests. Furthermore, when the overall urgency of communication requests in U increases, the shorter the update cycle, the more likely it is to be updated. This effectively increases the probability that more urgent communication requests will be prioritized. The present invention effectively balances processing speed and processing urgency, resulting in better overall processing results.

[0081] In the present invention, the set update period may be 1 second. The peak period may be 8-21 o'clock.

[0082] In the present invention, the weights of the data type coefficient, the service period coefficient and the load coefficient are 0.5, 0.3 and 0.2 respectively.

[0083] like Figure 2 As shown, the present invention also provides a parking and charging integrated data management system, including a parking lot management system server and a unified management platform server; 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 a change in data; The server of the unified management platform is used to determine whether the current CPU usage exceeds a set threshold after receiving the 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; The server of the unified management platform is further 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 also used to process communication requests according to priority coefficients; The priority coefficient is obtained by weighted summing the normalized values ​​of the data type coefficient, the time decay coefficient, the access characteristic coefficient, and the transmission quality coefficient.

[0084] 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 modifications or substitutions that can be easily conceived by a person 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 based on the scope of protection of the claims.

Claims

1. A method for managing data of charging and stopping, characterized in that: include: S1, when detecting a data change, the parking lot management system server sends a communication request for establishing a communication connection to the unified management platform server; S2, after receiving the communication request, the server of the unified management platform determines whether the current CPU usage exceeds the set threshold. 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 and enters S3; 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; The priority coefficient is obtained by weighted summing the normalized values ​​of the data type coefficient, the time decay coefficient, the access characteristic coefficient, and the transmission quality coefficient.

2. The method for managing charging and stopping data according to claim 1, characterized in that: The communication request includes a data type, a data size, and a first synchronization sequence number.

3. The method for managing charging and stopping data according to claim 1, characterized in that: The first confirmation notification includes the second synchronization sequence number and the third synchronization sequence number; The second synchronization sequence number is obtained by adding 1 to the first synchronization sequence number.

4. The method for managing charging and stopping data according to claim 3, characterized in that: 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 method for managing charging and stopping data according to claim 4, characterized in that: 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, a communication connection is established with the server of the parking lot management system.

6. The method for managing charging and stopping data according to claim 1, characterized in that: Waiting for notification includes retransmission time.

7. The method for managing charging and stopping data according to claim 6, characterized in that: After receiving the waiting notification, the server of the parking lot management system starts a countdown, and the countdown duration is equal to the retransmission duration. When the countdown ends, the server resends a communication request for establishing a communication connection to the server of the unified management platform.

8. The method for managing charging and stopping data according to claim 1, characterized in that: Process the communication request according to the priority coefficient, including: Update priority coefficients based on adaptive update cycles; In each update cycle, each communication request is processed in descending order of priority coefficient, and a first confirmation notification is sent to the server of the management system of the parking lot corresponding to the communication request.

9. The method for managing charging and stopping data according to claim 1, characterized in that: The update process of the adaptive update cycle includes: The update period is calculated based on the data type coefficient, service period coefficient and load coefficient of the communication request.

10. The charging and stopping integrated data management system is characterized by: Including the parking lot management system server and the unified management platform server; 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 a change in data; The server of the unified management platform is used to determine whether the current CPU usage exceeds a set threshold after receiving the 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; The server of the unified management platform is further 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 also used to process communication requests according to priority coefficients; The priority coefficient is obtained by weighted summing the normalized values ​​of the data type coefficient, the time decay coefficient, the access characteristic coefficient, and the transmission quality coefficient.

Images