Dynamic authority affirmation method and system of charging pile, medium and product

Abstract

The invention provides a dynamic permission affirmation method and system of a charging pile, a medium and a product, and relates to the technical field of cloud coordination. The method comprises the following steps of: locally storing a user account and corresponding NFC (Near Field Communication) information in a community charging pile; when a vehicle or a mobile phone approaches, the charging pile preferentially carries out local identification through the built-in NFC module. And if the matched local NFC information is detected, the system directly calls an account and starts charging, thereby realizing millisecond-level response and availability in network disconnection. And if the NFC information is not identified locally or the identification fails, the system automatically switches to a code scanning mode, guides the user to carry out identity verification through the server cloud, and starts charging after the verification is passed. The layered verification logic not only meets the quick charging requirement of a high-frequency user, but also guarantees the normal use permission of a temporary user, and effectively balances the verification efficiency and the system compatibility.

Description

Technical Field

[0001] This application relates to the field of cloud coordination technology, and in particular to a method, system, medium and product for dynamic permission determination of charging piles. Background Technology

[0002] With the popularization of low-carbon travel concepts and the surge in electric vehicle ownership, the construction of centralized charging facilities in residential communities has become an important part of smart communities. To improve user experience and management efficiency, modern charging stations generally integrate IoT technology, supporting various identification and payment methods such as QR code scanning, IC cards, or NFC (Near Field Communication). Among these, NFC technology, due to its contactless, fast-response, and convenient operation (such as direct sensing using a mobile phone or wristband), is gradually replacing the traditional coin-operated mode and becoming a frequently used authentication method for users.

[0003] In the existing charging pile technology architecture, authorization primarily relies on an "edge-cloud" interaction model. Specifically, when a user touches a charging pile with an NFC-enabled device, the charging pile uploads the read card number or device information to a cloud server. The server then queries the database for the account's balance and authorization status, and upon successful verification, issues an activation command to the charging pile. To improve response speed, some existing technical solutions cache whitelists locally or are designed with "instant activation" logic, meaning that once the NFC module detects a valid identity tag, it immediately closes the relay to supply power, reducing user waiting time.

[0004] However, the aforementioned existing technologies have significant drawbacks in practical applications. Cloud-based verification is limited by the network environment, and communication timeouts are prone to occur in underground parking garages or areas with signal blockage, resulting in charging failures. While local storage verification offers fast response times, conventional electric vehicle charging stations typically use low-performance MCUs with extremely limited storage space, making it unsuitable for scenarios with a large number of users. Therefore, there is an urgent need for a dynamic access control method for charging stations that balances verification response speed with optimized storage resources. Summary of the Invention

[0005] This application provides a dynamic permission authentication method, system, medium, and product for charging piles, which optimizes the response efficiency and storage resource utilization of NFC permission authentication for community charging piles, and improves the stability of smart community charging services.

[0006] Firstly, this application provides a dynamic access control method for charging piles, applied to a charging pile management system. The method includes: locally storing user account information on multiple charging piles within a residential community; extracting NFC information from the user account information and storing it in a local database within the community; when a target electric vehicle or mobile phone enters a preset NFC detection range, acquiring the target NFC information through the NFC identification module built into the charging pile; detecting whether NFC information corresponding to the target NFC information exists in the local database of the community; if NFC information corresponding to the target NFC information exists, accessing the corresponding user account, starting charging, and broadcasting a charging start reminder; if no NFC information corresponding to the target NFC information exists or NFC is not detected, performing server cloud verification after the target user scans a code; and after the target user passes the server cloud verification, starting charging and broadcasting a charging start reminder.

[0007] By adopting the above technical solution, the charging pile locally stores user accounts and NFC information and links to the local database of the community. When a user uses NFC, local verification is completed first, without relying on cloud communication. This directly avoids the communication timeout problem in signal blind spots such as underground parking garages, significantly improving the verification response speed. At the same time, cloud-based QR code verification is only triggered when local verification fails or NFC is not recognized, forming a two-layer verification mechanism of "local priority, cloud backup". This layered verification logic not only meets the fast charging needs of high-frequency users but also ensures the normal usage rights of temporary users, effectively balancing verification efficiency and system compatibility, and solving the network dependence drawbacks of the traditional end-to-cloud model and the limitations of pure local verification in applicable scenarios.

[0008] In conjunction with some embodiments of the first aspect, in some embodiments, the step of storing user account information locally through multiple charging piles set in the community includes: obtaining the historical charging records of each user account within a preset time period; determining the permanent charging pile of each user account based on the historical charging records, wherein the method for determining the permanent charging pile is as follows: counting the usage frequency of each charging pile of the target user account in the community; marking the first charging pile whose usage frequency exceeds a preset usage threshold as the permanent charging pile of the target user account; and sending and storing the account information and NFC information of each target user account to the local storage unit of the corresponding permanent charging pile.

[0009] By adopting the above technical solution, the system identifies the user's frequently used charging pile based on historical charging records and only sends account and NFC information to the frequently used device, rather than storing it all at all charging piles in the community. This feature specifically optimizes the storage space allocation of the charging pile's low-performance MCU, avoiding the excessive resource consumption caused by full storage. Simultaneously, frequent users can directly complete local verification at their frequently used charging pile without waiting for cross-device data retrieval or cloud interaction, further shortening the verification time for a single charge. This targeted storage strategy achieves precise allocation of storage resources, balancing user experience with hardware resource adaptability, and is suitable for application scenarios with a large number of users in the community.

[0010] In conjunction with some embodiments of the first aspect, in some embodiments, after the step of sending and storing the account information and NFC information of each target user account to the local storage unit of the corresponding permanent charging pile, the method further includes: calculating the latest charging record of each user account at each set update interval, and dynamically adjusting the local storage data according to the latest charging record. The specific adjustment method includes: if it is detected that the usage frequency of the target user account on the second charging pile where the corresponding account information is not currently stored exceeds the usage frequency on the first charging pile, and is greater than the preset usage threshold, then the target user account information is transferred from the first charging pile to the second charging pile, and the NFC index is updated; if it is detected that the usage frequency of the target user account on the local charging pile is lower than the preset cleanup threshold, then the target user account information is removed from the local storage unit and transferred to the cloud server; if it is detected that the verification frequency of the target user account in the cloud server exceeds the preset usage threshold, then the target user account information is obtained from the cloud server and transferred to the local storage unit of the corresponding charging pile, and a corresponding NFC index is established in the local database of the community.

[0011] By adopting the above technical solution, setting update intervals and dynamically adjusting local storage data based on the latest charging records, account information can be automatically transferred to new, frequently used charging stations when user habits change, ensuring that verification efficiency always matches user behavior. Low-frequency user information is removed locally and transferred to the cloud, freeing up limited storage resources at charging stations. Frequently verified users from the cloud are retrieved back to local storage, forming a dynamic "storage-release-return" loop mechanism. This dynamic adjustment logic keeps the local storage list highly efficient and available, avoiding resource waste or data corruption issues in static storage mode, achieving dynamic optimal allocation of storage resources, and balancing efficiency stability and resource utilization during long-term use.

[0012] In conjunction with some embodiments of the first aspect, in some embodiments, the step of accessing the corresponding user account includes: detecting whether the local storage unit of the current charging pile stores target user account information corresponding to the target NFC information; if the current charging pile does not store the target user account information, determining the target charging pile storing the target user account information through the NFC index in the database, wherein the NFC index is a mapping table pre-established in the local database of the cell that associates user NFC information with the corresponding resident charging pile device identifier and storage address; sending an account information acquisition request to the target charging pile; and, after receiving the target user account information, completing the user account access based on the target user account information.

[0013] By adopting the above technical solution and relying on the NFC index mapping relationship of the community's local database, when a user senses NFC at a non-resident charging station, the system can quickly locate the target charging station storing account information and initiate a retrieval request. This technical feature overcomes the device limitations of local storage, allowing users to retrieve cross-device data through the community intranet even at charging stations that are not frequently used, without needing to directly initiate cloud requests. Simultaneously, the NFC index mapping mechanism simplifies the addressing process for cross-device data interaction, shortening data retrieval time. This cross-device collaborative verification mode not only maintains the efficiency of local verification but also expands the applicability of local storage strategies, enhancing the overall service capabilities of charging stations within the community.

[0014] In conjunction with some embodiments of the first aspect, in some embodiments, after the step of sending an account information acquisition request to the target charging pile, the method further includes: starting a built-in response timer for real-time monitoring; if the target user account information is not received from the target charging pile within a preset timeout period, the target charging pile is determined to be in an inaccessible state, and an account information acquisition request is sent to the cloud server; after receiving the target user account information returned by the cloud server, the target user account information is stored in the local storage unit of the current charging pile, and a temporary NFC index is generated; when the status of the target charging pile is detected to have returned to normal, the target user account information in the local storage unit of the current charging pile is deleted, and the temporary NFC index is deleted simultaneously.

[0015] By adopting the above technical solution, a response timer is set to monitor the cross-device data acquisition status. If no response is received within the timeout period, the system automatically switches to cloud request mode, ensuring that the user's charging needs are not affected by target charging pile failures or network anomalies. Simultaneously, the account information returned from the cloud is temporarily stored and indexed. Once the target charging pile recovers, the temporary data is automatically cleared, avoiding the occupation of local long-term storage resources. This timeout fallback mechanism constructs a dual protection system of "cross-device retrieval - cloud backup," prioritizing the efficiency of local intranet interaction while preventing service interruptions through cloud backup. The automatic clearing design of temporary storage further optimizes the recycling of storage resources, improving the system's fault tolerance and stability.

[0016] In conjunction with some embodiments of the first aspect, in some embodiments, the step of initiating charging specifically includes: generating a charging pre-authorization instruction for the user account, switching the current working state of the charging pile to a pre-start standby state, and simultaneously opening a valid connection detection window of a preset duration; within the valid connection detection window, detecting the physical contact signal set in the socket in real time; if the physical contact signal is detected within the valid connection detection window, then charging is initiated; if the physical contact signal is not detected within the valid connection detection window, then the current NFC recognition is determined to be a mis-touch operation, and the charging pre-authorization instruction is cancelled.

[0017] By adopting the above technical solution, after successful NFC verification, a pre-authorization command is generated and the system enters standby mode. Then, the actual charging intention is confirmed via the physical contact signal of the socket. Accidental touches cancel the pre-authorization. This technical feature effectively avoids the problem of NFC mis-sensing without intended operation, preventing invalid startup of the charging pile and waste of power resources due to accidental touches. Simultaneously, the pre-authorization mode shortens the startup response time after successful contact detection, achieving a seamless connection between "verification-confirmation-startup." This dual confirmation mechanism ensures user convenience while improving the operational safety and energy efficiency of the charging pile, reducing the impact of invalid commands on equipment lifespan and grid load.

[0018] In conjunction with some embodiments of the first aspect, in some embodiments, the step of performing server cloud verification after the target user scans the code if no NFC information corresponding to the target NFC information exists or no NFC is recognized includes: obtaining the target user's scanning request and parsing it to obtain the target user's unique identifier; querying the unique identifier in the registered user database of the cloud server to determine whether the target user is a new user; if it is a new user, executing the new user registration process to generate a new user account, extracting the target user's new user NFC information, establishing the binding relationship between the new user NFC information and the new user account, and marking the verification as successful; if it is not a new user, retrieving the user account to be verified corresponding to the unique identifier and marking the verification as successful.

[0019] By adopting the above technical solution, differentiated processing is applied to new and existing users during QR code verification. Existing users directly access their accounts to complete verification, while new users simultaneously complete registration, NFC binding, and verification. This technical feature simplifies the user process for new users, eliminating the need for separate account registration and NFC binding, thus improving their initial user experience. Simultaneously, the rapid access mechanism for existing users shortens the processing time for QR code verification, narrowing the efficiency gap with local NFC verification. This scenario-based processing logic caters to the needs of both new and existing users, expands the system's user coverage, and enhances the service inclusiveness and ease of use of charging stations.

[0020] In a second aspect, this application provides a charging pile management system, which includes: one or more processors and a memory; the memory is coupled to the one or more processors, and the memory is used to store computer program code, which includes computer instructions, and the one or more processors call the computer instructions to cause the charging pile management system to perform the methods described in the first aspect and any possible implementation thereof.

[0021] Thirdly, this application provides a computer-readable storage medium including instructions that, when executed on a charging pile management system, cause the charging pile management system to perform the method described in the first aspect and any possible implementation thereof.

[0022] Fourthly, this application provides a computer program product, including a computer program that, when run on a charging pile management system, causes the charging pile management system to perform the method described in the first aspect and any possible implementation thereof.

[0023] One or more technical solutions provided in the embodiments of this application have at least the following technical effects or advantages:

[0024] 1. By adopting a two-layer permission authentication technology that combines local priority verification with cloud QR code scanning as a backup, the technology effectively solves the technical problems of cloud verification relying on the network and being prone to timeouts in signal blind spots, as well as the poor adaptability of pure local verification. This achieves a balance between verification response speed and system compatibility, ensuring fast charging for high-frequency users and normal use for temporary users.

[0025] 2. By adopting dynamic migration, elimination, and recirculation technology for stored data based on user charging frequency, the technology effectively solves the technical problems of local static storage in the prior art, which is prone to resource waste or data failure and cannot adapt to changes in user habits. This enables dynamic optimal configuration of local storage resources of charging piles, ensuring the technical effect of verifying efficiency stability and resource utilization during long-term use.

[0026] 3. By adopting a three-layer fault-tolerant technology approach of cross-device data retrieval, response timing, and automatic cloud backup, the technical problem of cross-charging pile data interaction being easily affected by equipment failure or network anomalies, leading to service interruption, is effectively solved. This achieves the technical effect of improving the system's fault tolerance and ensuring that users' charging needs are not affected by equipment status. Attached Figure Description

[0027] Figure 1 This is a flowchart illustrating the dynamic permission determination method for charging piles in this application embodiment;

[0028] Figure 2 This is another flowchart illustrating the dynamic access control method for charging piles in this application embodiment;

[0029] Figure 3 This is a schematic diagram of the physical device structure of a charging pile management system in the embodiments of this application. Detailed Implementation

[0030] The terminology used in the following embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. As used in the specification and appended claims of this application, the singular expressions “a,” “an,” “the,” “the,” “the,” and “this” are intended to include the plural expressions as well, unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used in this application refers to and includes any or all possible combinations of one or more of the listed items.

[0031] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature, and in the description of the embodiments of this application, unless otherwise stated, "multiple" means two or more.

[0032] For ease of understanding, the charging pile management system provided in this implementation is described below: The charging pile management system includes a local storage unit, an NFC identification module, a contact signal detection module, an answer timer, and a voice module. The local storage unit stores user account information and NFC information extracted from the user account information through multiple charging piles located within the community. The NFC identification module acquires the target NFC information when a target electric vehicle or mobile phone enters a preset NFC detection range. The contact signal detection module detects the physical contact signals within the socket in real time within a preset effective connection detection window to determine whether charging is enabled. The answer timer monitors in real time after sending an account information acquisition request to the target charging pile; if a timeout occurs, it triggers a request to the cloud server. The voice module announces a charging start reminder when charging is enabled or announces fault prompts when an anomaly is detected.

[0033] The above modules work together to achieve dynamic access control for charging piles. When a user performs NFC sensing, the system prioritizes rapid verification through the local storage unit and the local database of the community. Cloud-based QR code verification is triggered only when local verification fails or recognition fails. The system also uses a contact signal detection module to confirm the true charging intention. This ensures millisecond-level response for high-frequency users and availability even when the network is down, while also accommodating the normal usage rights of temporary users, effectively balancing verification efficiency and system compatibility.

[0034] The following describes the process of the method provided in this implementation, based on the structure of the charging pile management system described above. Please refer to [link / reference]. Figure 1 This is a flowchart illustrating the dynamic permission determination method for charging piles in this application embodiment.

[0035] S101. User account information is stored locally through multiple charging piles set up in the community;

[0036] First, the system retrieves historical charging records for all registered user accounts within the community within a preset time period from the data storage node and categorizes them according to user account ID. Then, for each target user account, the system iterates through all charging records under that account, calculating the user's usage frequency at each charging station within the community, creating a corresponding list of "user account - charging station number - usage frequency". Next, the system compares the calculated usage frequency of each charging station with a preset usage threshold, filtering out charging stations with usage frequencies exceeding the threshold. If multiple charging stations meet the criteria, the one with the highest usage frequency is selected and marked as the user's primary charging station, i.e., the frequently used charging station. If the user's usage frequency at all charging stations does not reach the threshold, the user is not marked as a frequently used charging station, and their account information remains in the cloud or is retrieved as needed. Next, the system retrieves the complete information of the target user's account and the corresponding NFC information from the cloud server, generates a targeted storage data packet, and sends it to the marked permanent charging piles via the community's intranet. Upon receiving the data packet, the charging pile stores it in its local storage unit and establishes a dedicated data index to ensure rapid retrieval during subsequent NFC sensing. Simultaneously, the system records the binding relationship of each user's permanent charging pile and synchronizes it to the NFC index table in the community's local database. If, during the next preset time period, this step reveals a change in the charging pile with the user's highest charging frequency, the system updates the permanent charging pile's marker and triggers the migration and storage of account information, deleting the user data from the original permanent charging pile and resending it to the new permanent charging pile.

[0037] In some embodiments, after the target user account information is stored locally on the permanent charging pile, the charging pile management system will retrieve the latest charging records of each user account from all charging piles in the community and the cloud server at each update time interval, and classify and summarize them according to the user account ID, and respectively count the core data such as the frequency of use of each user on each charging pile and the frequency of cloud verification.

[0038] For the first adjustment scenario, the system will compare the latest usage frequency of the target user at the second charging pile with that at the original first charging pile. If the usage frequency of the second charging pile is higher and exceeds the preset usage threshold, it will be determined that the user's permanent charging pile has been migrated. The system will issue a data deletion command to the original first charging pile to clear the user's account information and NFC data. At the same time, it will retrieve the user's complete data from the first charging pile and send it to the local storage unit of the second charging pile. Simultaneously, it will update the NFC index table in the local database of the community, rebinding the user's NFC information with the device identifier and storage address of the second charging pile to ensure that the user can directly perform local fast verification at the second charging pile in the future.

[0039] For the second adjustment scenario, the system will check the frequency of local charging station usage by the target user within a set period. If the frequency is lower than the preset cleanup threshold, the user will be determined to be a low-frequency user. The system will issue a data removal instruction to the corresponding charging station to delete the user's account information and NFC data from the local storage unit and simultaneously transfer them to the cloud server for backup, freeing up the charging station's limited local storage resources. At the same time, the local database index will be updated to mark that the user's data has been migrated to the cloud, and the cloud verification process will be directly triggered when the user initiates a charging request in the future.

[0040] For the third adjustment scenario, the system will count the frequency of cloud verification for the target user within a set period. If the frequency exceeds a preset usage threshold, the user is determined to be a high-frequency cloud user with local storage value. The system will retrieve the user's account information and NFC data from the cloud server, determine the corresponding target charging pile based on the user's latest charging frequency, and send the data to the local storage unit of the charging pile. A new NFC index will be created for the user in the community's local database, linking the user's NFC information with the device information of the target charging pile, realizing the return of user data from the cloud to the local storage, and improving the verification efficiency of the user's subsequent charging.

[0041] S102. Extract the NFC information from the user account information and store it in the local database of the cell;

[0042] This step is executed after S101 completes local storage of user account information and forms a linked execution process with S101. The execution scenario is that the local database of the community is in normal operation and maintains stable communication with the charging pile management system. In this step, the charging pile management system will traverse the user account information stored locally on each charging pile in S101. For each account information, it will accurately extract the NFC information field and remove redundant data. Subsequently, the system will standardize the extracted NFC information, unify the data format and encoding rules, and ensure the consistency of information for different types of NFC devices. Then, the system will upload the processed NFC information to the local database of the community and create a unique index for each NFC information. This index is associated with key information such as the user account ID and the corresponding permanent charging pile number, forming a mapping relationship table of "NFC information-user account-charging pile". Meanwhile, the community's local database will set up an NFC information update mechanism. When a user adds or unbinds an NFC device, the management system will promptly extract the updated NFC information and synchronize it to the local database, overwriting the original old data. In addition, the database will back up the stored NFC information to prevent data loss due to device failure, and it supports charging piles to quickly query the user account and charging pile association data corresponding to the NFC information through the intranet without accessing the cloud server.

[0043] S103. When the target electric vehicle or target mobile phone enters the preset NFC detection range, the target NFC information is obtained through the NFC identification module built into the charging pile.

[0044] This step is executed when a user intends to use the charging station and actively brings the target electric vehicle or mobile phone close to the NFC recognition area of ​​the charging station. The scenario is that the charging station is in standby mode, the NFC recognition module is powered on, and there is no strong external electromagnetic interference. In this step, the NFC recognition module built into the charging station continuously emits low-frequency detection signals. When the target electric vehicle or mobile phone enters the preset NFC detection range, the NFC chip of the target device is activated by the detection signal, establishing a communication link with the NFC recognition module of the charging station. Subsequently, the NFC recognition module sends an identity reading request to the target device. After verifying the legitimacy of the request, the target device will return its own NFC information. After receiving the feedback data, the NFC recognition module of the charging station will decode it, extract the valid target NFC information, and remove noise interference during data transmission. Simultaneously, to avoid misidentification, the NFC recognition module sets up multiple verification mechanisms, such as format verification of the read NFC information. If it does not conform to the preset standard, it is determined as invalid information and no further processing is performed. If the target NFC information is not successfully read within a preset time, the module will automatically stop the current identification process and re-enter the standby detection state. In addition, the charging station will record NFC identification log information in real time, including identification time, target NFC information, identification result, etc., which will facilitate subsequent troubleshooting and data analysis.

[0045] S104. Detect whether there is NFC information corresponding to the target NFC information in the local database of the cell;

[0046] This step is executed after S103 successfully acquires the target NFC information. It is a crucial step connecting NFC information reading and subsequent permission verification. The execution scenario is that the local database of the community is in a queryable state, and the communication link between the charging pile and the local database is unobstructed. In this step, the charging pile management system, as the executing entity, first receives the target NFC information uploaded by the charging pile in S103. Subsequently, the system sends the target NFC information as a search keyword to the local database of the community and initiates a data query request. After receiving the request, the local database of the community calls the NFC information index table established in S102 and quickly locates the data record that matches the target NFC information through index matching. If a completely matching NFC information record exists in the database, it is determined that "corresponding NFC information exists," and the user account ID, resident charging pile number, and other information associated with the record are fed back to the management system. If no matching record is found in the database, or the matching record has expired (e.g., the user has unbound the NFC device), it is determined that "corresponding NFC information does not exist," and feedback of no matching result is returned to the management system. Meanwhile, to improve detection efficiency, the community's local database employs a highly efficient retrieval algorithm to shorten data matching time. If communication between the charging pile and the local database is briefly interrupted, the system will activate a temporary detection mechanism for locally cached NFC information, and perform data synchronization and verification once communication is restored. Furthermore, a timeout period is set for the detection process. If no feedback is received from the database within the preset time, it is directly determined that "corresponding NFC information does not exist," triggering the subsequent cloud verification process.

[0047] S105. If NFC information corresponding to the target NFC information exists, access the corresponding user account, start charging, and announce the start charging reminder.

[0048] This step is executed after determining that the local database of the community contains NFC information corresponding to the target NFC information. The execution scenario is that the power supply module of the charging pile is in normal working order, and the user has physically connected the electric vehicle charging plug to the charging pile. In this step, the charging pile management system will retrieve the corresponding user account details based on the matching result fed back in S104, including account balance, remaining charging package time, and account permission status (such as whether it is disabled). Subsequently, the system will verify the account permissions; the specific method for accessing the corresponding user account will be explained in detail in subsequent steps S201-S204.

[0049] If the account balance is sufficient, the subscription plan is valid, and the user's permissions are in good standing, a charging authorization command is generated and sent to the corresponding charging station. Upon receiving the authorization command, the charging station immediately closes its internal relay, initiates the power supply process, and outputs stable power to the electric vehicle. Simultaneously, the charging station triggers a notification mechanism, playing a message such as "Charging has started" via its built-in voice module, or displaying information such as the charging start time and estimated charging time on the screen. If account permission verification fails (e.g., insufficient balance, expired subscription plan), the system will issue a charging refusal command to the charging station, which will then provide the user with the specific reason for the failure via voice or display. Furthermore, during charging, the system monitors the charging station's operational status and the user's account spending in real time, sending an early warning to the user when the account balance is about to run out.

[0050] In some embodiments, the charging pile management system can generate a charging pre-authorization instruction containing the user account ID, the pre-authorization validity period, and the maximum charging power limit based on the verified user account information, and send it to the current charging pile. After receiving the instruction, the charging pile immediately switches its working state from normal standby to pre-start standby state. In this state, the control circuit of the charging pile is activated, but the relay of the main power supply circuit remains open to avoid meaningless power output. At the same time, the charging pile automatically opens a valid connection detection window for a preset period of time and starts the built-in contact signal detection module.

[0051] During the effective connection detection window, the contact signal detection module collects the on / off status data of the physical contacts inside the socket in real time at a millisecond frequency. If a physical contact signal is detected, it means that the user has inserted the electric vehicle charging plug into the socket, and the charging circuit has completed physical connection. At this time, the charging pile will respond immediately, close the relay of the main power supply circuit, officially start the power output process, and start measuring the charging time and power consumption, while updating the user's account charging status data synchronously. If no physical contact signal is detected before the effective connection detection window ends, the NFC sensing is determined to be a false touch operation. The charging pile will immediately send a false touch judgment signal to the management system. After receiving the signal, the management system generates a cancellation command and sends it to the charging pile. The charging pile revokes the charging pre-authorization, restores the working state to the normal standby state, and does not generate any charging records or billing data.

[0052] S106. If there is no NFC information corresponding to the target NFC information or NFC is not recognized, then the server cloud verification will be performed after the target user scans the code.

[0053] In this step, the charging pile management system first receives the target user's QR code scanning request data packet uploaded by the charging pile. This data packet contains the charging pile device number, the scanning timestamp, and the original data generated by the user's QR code scanning. The system decodes and parses the original data to extract a unique user identity identifier, and encrypts the identifier to prevent it from being tampered with or stolen during transmission.

[0054] Subsequently, the system sends the encrypted unique identifier to the cloud server and initiates a database query request. Upon receiving the request, the cloud server calls the retrieval interface of the registered user database and compares the identifier according to a preset matching algorithm. If no matching record is found in the database, the user is determined to be a new user, and the cloud server triggers the new user registration process: First, a registration page is pushed to the user's mobile terminal, guiding the user to fill in basic information such as mobile phone number and set payment password to generate a new user account; then, the user is prompted to enter NFC information (such as placing the mobile phone's NFC module close to the charging pile's sensing area, where the system automatically reads the NFC chip serial number), and a one-to-one correspondence between the new user account and the NFC information is established in the database; after the binding is completed, the server marks the account status as "normal and available" and sends a "verification passed" result to the management system.

[0055] If a matching record is found in the database, the user is determined to be a non-new user. The cloud server directly retrieves the user account to be verified associated with the unique identifier and verifies the account's current status, including whether the account is disabled, whether the balance is sufficient, and whether there are any outstanding charging fees. If the account status meets all charging requirements, the account is marked as "verified" and the account permission information is synchronized to the charging pile management system. If the account status is abnormal (such as insufficient balance or frozen account), an abnormal prompt message is pushed to the user's terminal, terminating the verification process. The user can only re-initiate the scanning request after recharging the account or restoring the status.

[0056] S107. After the target user is verified through the cloud server, charging is started and a charging reminder is broadcast.

[0057] This step is executed after S106 completes the cloud server verification and the server sends a verification pass instruction to the charging pile management system. The execution scenario is that the charging pile power supply module is functioning normally and the user has completed the physical connection of the charging plug. In this step, the charging pile management system receives the verification pass instruction and user account permission information from the cloud server. Subsequently, the system sends a charging authorization instruction to the corresponding charging pile, which includes parameters such as charging power limits and billing standards. Upon receiving the authorization instruction, the charging pile immediately closes its internal relay, starts the power output process, and records information such as the charging start time and initial metering data. Simultaneously, the charging pile triggers a reminder broadcast mechanism, playing a "Charging started" prompt through the voice module or displaying information such as the charging account, current charging power, and estimated cost on the screen for the user's real-time viewing. If the charging pile detects an abnormal state during the charging start process (such as a short circuit or poor plug contact), it will immediately disconnect the relay, stop the power supply, broadcast a fault message to the user, and upload the fault data to the management system. In addition, during the charging process, the system will synchronize the user's charging time, power consumption and other data to the cloud server in real time for real-time billing; when the user actively ends the charging or the charging is completed, the charging pile will automatically disconnect the power supply and broadcast a charging end reminder and fee details.

[0058] In the above embodiment, due to the adoption of a hierarchical permission authentication technology of "charging pile local storage + community local database NFC verification + cloud QR code scanning as a backup", it can prioritize NFC fast verification through the local area and community intranet, and trigger cloud verification only when local verification fails. This effectively solves the problems of traditional end-to-cloud mode relying on the network, easy timeout in signal blind spots, and poor adaptability of pure local storage. As a result, it achieves a dual improvement in verification response speed and system compatibility, which not only meets the fast charging needs of high-frequency users, but also ensures the normal use rights of temporary users, and adapts to the complex network environment and diverse user scenarios of the community.

[0059] Following the above embodiments, the method provided in this embodiment will now be described in more detail. Please refer to [link / reference]. Figure 2 This is another flowchart illustrating the dynamic permission determination method for charging piles in this application embodiment.

[0060] S201. Detect whether the local storage unit of the current charging pile stores the target user account information corresponding to the target NFC information;

[0061] This step is executed after successfully acquiring the target NFC information but before detecting the corresponding NFC information in the local database of the community. The execution scenario is that the charging pile is in normal standby mode and the format of the target NFC information read by the NFC recognition module is correct. In this step, the system extracts the core feature fields from the target NFC information as search keywords. Then, it calls the search interface of the local storage unit and, according to preset matching rules, it iterates and searches through the locally stored user account information dataset. The search process is completed only locally on the charging pile and does not rely on external network communication. If user account information that completely matches the target NFC information is found, it is determined that "the current charging pile has stored the target user account information," and the system directly enters the account authorization verification stage. If no matching record is found, it is determined that "the current charging pile has not stored the target user account information," triggering the subsequent cross-charging pile data retrieval process.

[0062] S202. If the current charging pile does not store the target user account information, the target charging pile that stores the target user account information is determined through the NFC index in the database. The NFC index is a mapping table pre-established in the local database of the community that associates user NFC information with the corresponding permanent charging pile device identifier and storage address.

[0063] This step is executed after step S201 determines that the current charging pile does not store the target user account information. The execution scenario is that the community's local database is operating normally, and the intranet communication link between the current charging pile and the local database is unobstructed. In this step, the charging pile management system receives the target NFC information uploaded by the current charging pile and the determination result that no matching account is stored. Subsequently, the system uses the target NFC information as a search condition, sends it to the community's local database, and initiates an NFC index query request. After receiving the request, the community's local database calls its built-in NFC index table for precise matching, quickly locates the resident charging pile device identifier bound to the target NFC information, and simultaneously obtains the specific storage address of the user account information in the target charging pile's local storage unit. The system then feeds back the target charging pile's device identifier and storage address to the management system.

[0064] S203. Send an account information retrieval request to the target charging station;

[0065] This step is executed after successfully determining the target charging pile and the storage address of the account information, and the target charging pile is online with a stable intranet communication link with the current charging pile. In this step, the charging pile management system generates a standardized account information retrieval request data packet based on the returned target charging pile device identifier and storage address. This data packet includes the current charging pile's device number, request timestamp, and encrypted verification information for the target charging pile to verify the request's legitimacy. Subsequently, the system forwards the request data packet to the target charging pile via the intranet. Upon receiving the request data packet, the target charging pile first verifies the legitimacy of the requester and the validity of the encrypted information. If the verification fails, the request is rejected, and an error message is sent to the management system. If the verification passes, the target charging pile retrieves the corresponding target user account information from its local storage unit based on the storage address in the data packet, encrypts the information, and prepares to send it back to the current charging pile.

[0066] In some embodiments, when the charging pile management system sends an account information retrieval request to the target charging pile, it can immediately start a built-in response timer and enter a real-time monitoring mode. The timer counts down with millisecond precision, synchronously recording the request sending time and the remaining duration. Within a preset timeout period, the system continuously listens for feedback signals from the target charging pile. If it receives complete and valid user account information from the target charging pile before the countdown ends, it immediately terminates the timer, enters the account access process in S204, and resets the timer to its initial state, waiting for the next request to be triggered.

[0067] If the response timer expires and the system still hasn't received feedback data from the target charging pile, it determines that the target charging pile is inaccessible and triggers a cloud-based fallback verification mechanism. The system automatically generates a cloud query data packet containing the target NFC information, the current charging pile number, and the reason for the request failure, and sends it to the cloud server via the public network to initiate an account information retrieval request. Upon receiving the request, the cloud server retrieves account information matching the target NFC information from the registered user database, completes authorization verification, and then sends the encrypted account data back to the current charging pile. After receiving the account information returned from the cloud, the current charging pile temporarily stores it in its local storage unit and generates a temporary NFC index. This index is only associated with data related to this charging request and is marked as "temporarily valid" to avoid conflicts with the official index in the community's local database, ensuring the accuracy of data retrieval during subsequent NFC identification.

[0068] Meanwhile, the system continuously monitors the operational status of the target charging pile, periodically sending heartbeat detection packets via the community intranet. If it receives multiple consecutive normal heartbeat responses from the target charging pile, it determines that its status has returned to normal. The system immediately triggers a temporary data cleanup process, issuing an instruction to the current charging pile to delete the temporarily stored user account information in the local storage unit, and simultaneously delete the corresponding temporary NFC index, releasing the storage resources of the current charging pile. This ensures that the local storage unit is always primarily used for officially stored data, avoiding resource shortages caused by excessive temporary data occupying too much space.

[0069] S204. After receiving the target user account information, complete the user account access based on the target user account information.

[0070] This step is executed after the current charging station successfully receives the target user account information from the target charging station. The execution scenario is that the account information data packet is decrypted and in a complete format with no signs of data tampering. In this step, the system first decrypts the received encrypted account information data packet, then verifies the integrity of the decrypted information. If data is missing or tampered with, the process is immediately terminated and the management system is notified of the data anomaly. If the verification is successful, the system extracts the core fields from the account information, including the user account ID, account balance, charging permission status, and package validity period. Next, the charging station uses the extracted information to complete account access and permission verification: checking if the account is in normal activation status, if the balance meets the minimum charging threshold, and if the package is valid. If all permission conditions are met, account access is considered successful, generating the prerequisites for charging authorization. If any permission condition is not met (e.g., insufficient balance, frozen account), account access is considered failed, and the user is informed of the specific reason for the failure via voice or display screen.

[0071] In this embodiment, the collaborative verification technology of "local priority detection of the current charging pile + NFC index positioning of the local database of the community + retrieval of cross-charging pile account information" is adopted. Therefore, it can realize efficient verification of account information within the community intranet without relying on cloud servers. This effectively solves the problem that users can only fast charge at the permanent charging pile under the traditional pure local storage mode, and cross-pile use requires cloud access and is easily restricted by the network environment. Thus, it realizes local-level fast verification capability coverage for all charging piles in the community, which not only ensures the convenience of users charging across piles, but also avoids the risk of charging failure caused by signal blind spots, and maximizes the use of the local storage resources of the charging pile and the communication advantages of the community intranet.

[0072] The charging pile management system in the embodiments of this invention is described below from the perspective of hardware processing. Please refer to [link / reference]. Figure 3 This is a schematic diagram of the physical device structure of a charging pile management system in an embodiment of this application.

[0073] It should be noted that, Figure 3 The structure of the charging pile management system shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0074] like Figure 3 As shown, the charging pile management system includes a Central Processing Unit (CPU) 301, which can perform various appropriate actions and processes based on programs stored in Read-Only Memory (ROM) 302 or programs loaded from storage section 308 into Random Access Memory (RAM) 303, such as executing the methods described in the above embodiments. The RAM 303 also stores various programs and data required for system operation. The CPU 301, ROM 302, and RAM 303 are interconnected via a bus 304. An Input / Output (I / O) interface 305 is also connected to the bus 304.

[0075] The following components are connected to I / O interface 305: input section 306 including audio input devices, push-button switches, etc.; output section 307 including a liquid crystal display (LCD) and audio output devices, indicator lights, etc.; storage section 308 including a hard disk, etc.; and communication section 309 including a network interface card such as a LAN (Local Area Network) card, modem, etc. Communication section 309 performs communication processing via a network such as the Internet. Drive 310 is also connected to I / O interface 305 as needed. Removable media 311, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 310 as needed so that computer programs read from them can be installed into storage section 308 as needed.

[0076] In particular, according to embodiments of the present invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of the present invention include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing computer programs for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 309, and / or installed from removable medium 311. When the computer program is executed by central processing unit (CPU) 301, it performs the various functions defined in the present invention.

[0077] It should be noted that specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0078] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. Each block in a flowchart or block diagram may represent a module, program segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those shown in the drawings.

[0079] Specifically, the charging pile management system of this embodiment includes a processor and a memory. The memory stores a computer program. When the computer program is executed by the processor, it implements the dynamic permission determination method for charging piles provided in the above embodiment.

[0080] In another aspect, the present invention also provides a computer-readable storage medium, which may be included in the charging pile management system described in the above embodiments; or it may exist independently and not be assembled into the charging pile management system. The storage medium carries one or more computer programs, which, when executed by a processor of the charging pile management system, cause the charging pile management system to implement the dynamic access control method for charging piles provided in the above embodiments.

[0081] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

[0082] As used in the above embodiments, depending on the context, the term "when..." can be interpreted as meaning "if...", "after...", "in response to determining...", or "in response to detecting...". Similarly, depending on the context, the phrase "when determining..." or "if (the stated condition or event) is interpreted as meaning "if determining...", "in response to determining...", "when (the stated condition or event) is detected", or "in response to detecting (the stated condition or event)".

[0083] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This program can be stored in a computer-readable storage medium, and when executed, it can include the processes described in the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.

Claims

1. A dynamic access control method for charging piles, applied to a charging pile management system, characterized in that, The method includes: User account information is stored locally through multiple charging stations set up within the community; Extract the NFC information from the user account information and store it in the local database of the cell; When the target electric vehicle or target mobile phone enters the preset NFC detection range, the target NFC information is obtained through the NFC identification module built into the charging pile; Detect whether NFC information corresponding to the target NFC information exists in the local database of the cell; If NFC information corresponding to the target NFC information exists, the corresponding user account is accessed, charging is started, and a charging reminder is broadcast. If no NFC information corresponding to the target NFC information exists or no NFC is identified, then server cloud verification will be performed after the target user scans the code. After the target user is verified through the cloud server, charging is started and a charging reminder is broadcast.

2. The method according to claim 1, characterized in that, The step of storing user account information locally through multiple charging piles set up in the community includes: Obtain the historical charging records of each user account within a preset time period; Based on the historical charging records, the permanent charging stations for each user account are determined. The specific method for determining the permanent charging stations is as follows: Statistical analysis of the frequency of use of each charging station by the target user account within the community; The first charging pile whose usage frequency exceeds a preset usage threshold is marked as the permanent charging pile of the target user account; The account information and NFC information of each target user account are sent and stored in the local storage unit of the corresponding permanent charging pile.

3. The method according to claim 2, characterized in that, After the step of sending and storing the account information and NFC information of each target user account to the local storage unit of the corresponding permanent charging pile, the method further includes: At each set update interval, the latest charging records of each user account are statistically analyzed, and the locally stored data is dynamically adjusted based on the latest charging records. The specific adjustment method includes: If it is detected that the frequency of use of the target user account on the second charging pile where the corresponding account information is not currently stored exceeds the frequency of use on the first charging pile, and is greater than the preset usage threshold, then the target user account information is transferred from the first charging pile to the second charging pile and the NFC index is updated. If the frequency of use of the target user account at the local charging station is found to be lower than the preset cleanup threshold, the target user account information is removed from the local storage unit and transferred to the cloud server. If the verification frequency of the target user account in the cloud server exceeds the preset usage threshold, the target user account information is obtained from the cloud server and transferred to the local storage unit of the corresponding charging pile, and a corresponding NFC index is established in the local database of the community.

4. The method according to claim 1, characterized in that, The steps for accessing the corresponding user account include: Detect whether the local storage unit of the current charging pile stores the target user account information corresponding to the target NFC information; If the current charging pile does not store the target user account information, the target charging pile that stores the target user account information is determined through the NFC index in the database. The NFC index is a mapping table pre-established in the local database of the community that associates user NFC information with the corresponding permanent charging pile device identifier and storage address. Send an account information retrieval request to the target charging pile; After receiving the target user account information, user account access is completed based on the target user account information.

5. The method according to claim 4, characterized in that, After the step of sending an account information retrieval request to the target charging pile, the method further includes: Start the built-in response timer for real-time monitoring; If the target user account information is not received from the target charging pile within the preset timeout period, the target charging pile is determined to be inaccessible, and an account information retrieval request is sent to the cloud server. After receiving the target user account information returned by the cloud server, the target user account information is stored in the local storage unit of the current charging pile, and a temporary NFC index is generated; Once the target charging pile is detected to have returned to normal status, the target user account information in the local storage unit of the current charging pile is deleted, and the temporary NFC index is deleted simultaneously.

6. The method according to claim 1, characterized in that, The steps for starting charging specifically include: Generate a charging pre-authorization instruction for the user account, switch the current working state of the charging pile to the pre-start standby state, and open a valid connection detection window for a preset duration. Within the effective connection detection window, the physical contact signals located in the socket are detected in real time. If the physical contact signal is detected within the valid connection detection window, charging is initiated. If no physical contact signal is detected within the valid connection detection window, the current NFC identification is determined to be a false touch operation, and the charging pre-authorization command is cancelled.

7. The method according to claim 1, characterized in that, The step of performing server cloud verification after the target user scans the code if no NFC information corresponding to the target NFC information exists or no NFC is detected includes: Obtain the QR code scanning request from the target user and parse it to obtain the unique identifier of the target user; The unique identifier is queried in the registered user database on the cloud server to determine whether the target user is a new user; If it is a new user, the new user registration process is executed to generate a new user account, the new user's NFC information is extracted, the binding relationship between the new user's NFC information and the new user account is established, and the verification is marked as successful; If it is not a new user, then retrieve the user account to be verified corresponding to the unique identifier and mark it as verified.

8. A charging pile management system, characterized in that, The charging pile management system includes: one or more processors and a memory; the memory is coupled to the one or more processors, the memory is used to store computer program code, the computer program code including computer instructions, and the one or more processors call the computer instructions to cause the charging pile management system to perform the method as described in any one of claims 1-7.

9. A computer-readable storage medium comprising instructions, characterized in that, When the instruction is executed on the charging pile management system, the charging pile management system performs the method as described in any one of claims 1-7.

10. A computer program product, comprising a computer program, characterized in that, When the computer program runs on the charging pile management system, it causes the charging pile management system to perform the method as described in any one of claims 1-7.

Images