Vehicle Reservation Charging Management Method and System

Abstract

This application discloses a vehicle reservation charging management method and system. The method includes: responding to a charging connection event of a target vehicle, obtaining target scenario information of the current location of the target vehicle, wherein the charging connection event includes: the charging gun being inserted into the target vehicle and being identified as a valid charging connection; the target scenario information includes at least one of the following: date information and location information; determining a target charging strategy matching the target scenario information from a preset scenario strategy configuration library, wherein the scenario strategy configuration library stores multiple pre-configured charging strategies and the effective scenario information corresponding to each charging strategy; and performing a charging operation on the target vehicle according to the target charging strategy. This application solves the technical problem that a single timed charging mode in the reservation charging scenario for new energy vehicles lacks flexibility and is difficult to meet the dynamic vehicle usage needs of the target users.

Description

Technical Field

[0001] This application relates to the field of vehicle management technology, and more specifically, to a method and system for vehicle reservation charging management. Background Technology

[0002] Currently, most new energy vehicles on the market with scheduled charging functions use a "single timer mode" for charging. Specifically, the user sets a fixed charging time window in the vehicle's human-machine interface, which usually includes a charging start time and a charging end time. When the user successfully connects the charging gun to the vehicle, the vehicle's battery management system enters a waiting state. When the system clock reaches the preset start time, the system automatically starts the charging process. When the system clock reaches the preset end time, the system will forcibly stop charging regardless of the battery level.

[0003] While the above solution addresses the fundamental issue of missing off-peak electricity hours when charging immediately after connecting the charging gun, achieving the economic goal of enjoying lower electricity prices during fixed periods, its rigid logic cannot adapt to the complex and ever-changing driving scenarios of car owners. For example, if a user only needs to charge to 80% for short commutes on weekdays, but needs to fully charge to 100% for long-distance weekend trips, they would be forced to manually adjust their strategy on Friday. This is not only cumbersome but also prone to being forgotten, easily leading to insufficient range the next day or misusing peak electricity, increasing costs and severely impacting the convenience and reliability of the intelligent driving experience.

[0004] There is currently no effective solution to the above problems. Summary of the Invention

[0005] This application provides a vehicle reservation charging management method and system to at least solve the technical problem that a single timed mode in the reservation charging scenario of new energy vehicles lacks flexibility and is difficult to meet the dynamic vehicle usage needs of the target users.

[0006] According to one aspect of the embodiments of this application, a vehicle reservation charging management method is provided, comprising: responding to a charging connection event of a target vehicle, obtaining target scene information of the current scene of the target vehicle, wherein the charging connection event includes: a charging gun being inserted into the target vehicle and being identified as a valid charging connection, and the target scene information including at least one of the following: date information and location information; determining a target charging strategy matching the target scene information from a preset scene strategy configuration library, wherein the scene strategy configuration library stores multiple pre-configured charging strategies and the effective scene information corresponding to each charging strategy; and performing a charging operation on the target vehicle according to the target charging strategy.

[0007] Optionally, the scenario strategy configuration library is in the format of a structured data table. The construction process of the scenario strategy configuration library includes: generating a charging strategy corresponding to the strategy configuration command input by the target object in the interactive interface; generating effective scenario information corresponding to the scenario configuration command in response to the scenario configuration command input by the target object in the interactive interface; establishing a mapping relationship between the charging strategy and the effective scenario information, and using the mapping relationship as a record in the structured data table.

[0008] Optionally, the charging strategy includes: a charging start time and a charging end time; or, a charging start time and a target state of charge; or, a charging start time, a charging end time, a target state of charge, and an execution flag, wherein the execution flag is used to indicate whether to continue charging until the vehicle's state of charge reaches the target state of charge if the charging end time has been reached but the vehicle's state of charge has not reached the target state of charge.

[0009] Optionally, the effective scenario information includes at least one of the following: effective date information and effective location information; wherein, the effective date information has a higher effective priority than the effective location information; the effective date information includes at least one of the following: a date determined according to a preset cycle, a specified date, and a date corresponding to the target event in the preset memo.

[0010] Optionally, the effective date information includes: a weekday mask; wherein the weekday mask is a 7-bit binary field, and each bit in the weekday mask is used to indicate whether the charging policy is effective on a day of the week.

[0011] Optionally, a target charging strategy matching the target scenario information is determined from a preset scenario strategy configuration library, including: determining a charging strategy whose effective scenario information matches the target scenario information as a candidate charging strategy from the scenario strategy configuration library; if no candidate charging strategy exists, determining a default charging strategy as the target charging strategy, or generating a prompt message to instruct the target object to configure the target charging strategy; if only one candidate charging strategy exists, determining the candidate charging strategy as the target charging strategy; if multiple candidate charging strategies exist, determining the preset priority of each candidate charging strategy and determining the candidate charging strategy with the highest preset priority as the target charging strategy, or obtaining the historical usage records of each candidate charging strategy and determining the most recently used candidate charging strategy as the target charging strategy.

[0012] Optionally, after determining the target charging strategy that matches the target scenario information from the preset scenario strategy configuration library, a confirmation message is generated in the interactive interface to confirm whether to execute the target charging strategy; in response to the confirmation command input by the target object in the interactive interface, a charging operation is performed on the target vehicle according to the target charging strategy; in response to the strategy change command input by the target object in the interactive interface, the target charging strategy is changed according to the strategy change command, and a charging operation is performed on the target vehicle according to the changed charging strategy.

[0013] According to another aspect of the embodiments of this application, a vehicle reservation charging management system is also provided, including: a strategy configuration module, used to respond to the configuration instructions of a target object and configure multiple charging strategies and effective scenario information corresponding to each charging strategy; a strategy storage module, used to store multiple charging strategies and effective scenario information corresponding to each charging strategy; a scenario detection module, used to respond to the charging connection event of a target vehicle and obtain the target scenario information of the current scenario of the target vehicle, wherein the charging connection event includes: the charging gun being inserted into the target vehicle and being identified as a valid charging connection, and the target scenario information includes at least one of the following: date information and location information; a strategy matching module, used to determine the target charging strategy that matches the target scenario information from the strategy storage module; and a charging control module, used to perform charging operations on the target vehicle according to the target charging strategy.

[0014] According to another aspect of the embodiments of this application, a computer program product is also provided, the computer program product comprising: a computer program, wherein the computer program, when executed by a processor, implements the above-described vehicle reservation charging management method.

[0015] According to another aspect of the embodiments of this application, a vehicle is also provided, the vehicle including: the vehicle reservation charging management system described above.

[0016] In this embodiment, in response to a charging connection event of the target vehicle, firstly, by acquiring target scenario information including date and location information, the target object's demand scenario corresponding to the current charging environment is accurately identified. Then, based on a preset multi-scenario strategy configuration library, a target charging strategy matching the aforementioned target scenario information is selected, and the charging operation is automatically executed. This achieves intelligent adaptation of vehicle charging behavior to the target object's periodic life scenarios, enabling the automatic determination of the charging strategy on different dates or locations without the target object needing to manually adjust charging settings. This improves the target object's experience and the level of charging intelligence, effectively solving the technical problem that the single timed mode in the new energy vehicle reservation charging scenario lacks flexibility and is difficult to meet the target object's dynamic vehicle usage needs. Attached Figure Description

[0017] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0018] Figure 1 This is a flowchart illustrating an optional vehicle reservation charging management method according to an embodiment of this application;

[0019] Figure 2 This is a schematic diagram illustrating the process of performing a charging operation according to an optional vehicle reservation charging management system based on an embodiment of this application.

[0020] Figure 3 This is a schematic diagram of hardware and data interaction in the scenario setting stage of an optional vehicle reservation charging management system according to an embodiment of this application;

[0021] Figure 4 This is a schematic diagram of hardware and data interaction during the charging execution phase of an optional vehicle reservation charging management system according to an embodiment of this application;

[0022] Figure 5 This is a schematic diagram of an optional vehicle reservation charging management system according to an embodiment of this application;

[0023] Figure 6 This is a schematic diagram of the hardware structure of an optional electronic device according to an embodiment of this application. Detailed Implementation

[0024] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0025] It should be noted that the terms "first," "second," etc., used in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0026] Example 1

[0027] According to an embodiment of this application, a vehicle reservation charging management method is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Also, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0028] Figure 1 This is a flowchart illustrating a vehicle reservation charging management method according to an embodiment of this application, as shown below. Figure 1 As shown, the method includes the following steps S102-S106:

[0029] Step S102: In response to the charging connection event of the target vehicle, obtain the target scene information of the current scene of the target vehicle. The charging connection event includes: the charging gun is inserted into the target vehicle and is identified as a valid charging connection. The target scene information includes at least one of the following: date information and location information.

[0030] Step S104: Determine the target charging strategy that matches the target scenario information from the preset scenario strategy configuration library. The scenario strategy configuration library stores multiple pre-configured charging strategies and the effective scenario information corresponding to each charging strategy.

[0031] Step S106: Perform a charging operation on the target vehicle according to the target charging strategy.

[0032] The following section explains each step of the vehicle reservation charging management method in conjunction with the specific implementation process.

[0033] In the technical solution provided in step S102, the charging connection event is a confirmation process in which the charging interface of the target vehicle completes a physical connection with the external charging device and confirms that the charging device has the conditions for safe start-up through a series of built-in electrical safety detection mechanisms. This includes, but is not limited to, the target vehicle's charging gun being fully inserted into the charging device socket, the connection confirmation signal and control guidance signal in the charging guidance circuit reaching a stable level threshold, the target vehicle's battery management system confirming that the electrical circuit insulation impedance of the charging device is qualified, and the target vehicle's energy storage module completing a communication handshake with the charging pile and receiving an enable signal that allows charging. The connection confirmation signal is used to detect whether the target vehicle's charging gun is physically inserted into the external charging device and to establish a stable connection resistance detection signal; the control guidance signal is used to implement the pulse width modulation (PWM) signal for charging start / stop control and power negotiation, which is sent from the charging pile to the target vehicle.

[0034] Optionally, the target vehicle mentioned above is a vehicle equipped with a Controller Area Network (CAN), an On-Board Charger (OBC), a Battery Management System (BMS), a charging interface, an on-board charger, a real-time clock module, a positioning module, and an interactive interface.

[0035] Specifically, when the charging gun is inserted into the charging port of the target vehicle, the vehicle's charging port senses the current physical connection status. After completing a communication handshake and security verification through the charging guidance circuit, the vehicle's scheduled charging management system automatically wakes up the real-time clock module and the positioning module, reads the current precise date information, including year, month, day, and weekday values, as well as the vehicle's geographical coordinates, and calls the pre-set geofence database to map the location coordinates to preset location information (such as home, company, public charging station, etc.). The above date and location information is encapsulated into a structured data object as the target scene information of the target vehicle's current scenario, and stored in the strategy configuration module as input for subsequent scenario and charging strategy matching.

[0036] In the technical solution provided in step S104, the vehicle reservation charging management system determines the target charging strategy that matches the target scenario information obtained in step S102 from the preset scenario strategy configuration library. The scenario strategy configuration library is in the format of a structured data table, and the type, length and storage order of each field are predefined. It is used to store multiple sets of charging strategies set by the target object and their binding effective conditions. Each row represents an independent charging scenario, and each column corresponds to a specific charging strategy.

[0037] Optionally, the construction process of the above-mentioned scenario strategy configuration library includes:

[0038] Step S21: In response to the strategy configuration command input by the target object in the interactive interface, generate a charging strategy corresponding to the strategy configuration command.

[0039] Step S22: In response to the scene configuration command input by the target object in the interactive interface, generate the effective scene information corresponding to the scene configuration command;

[0040] Step S23: Establish a mapping relationship between the charging strategy and the effective scenario information, and treat the mapping relationship as a record in the structured data table.

[0041] Optionally, the aforementioned interactive interface is a touch screen integrated into the central infotainment system of the target vehicle or a mobile terminal application bound to the vehicle. It includes, but is not limited to, a time selection control for setting the start and end times of charging, a slider or numerical input box for inputting the target state of charge, a weekday checkbox matrix for selecting the effective period, a switch option for configuring charging behavior logic, and a confirmation button and list management area for saving or deleting strategies. The above components work together to enable the target object to complete the parameter definition and scenario binding of multiple charging strategies in a graphical manner. The input information is processed locally and converted into structured data for the vehicle controller to call.

[0042] For example, step S21 above can be understood as follows: First, the target object inputs a strategy configuration instruction through the central control screen or mobile application of the target vehicle. This strategy configuration instruction includes at least the charging start time and charging end time, and may also include the target state of charge and execution flags (e.g., whether timeout is allowed), to clarify the charging behavior logic of the target vehicle in a specific scenario. Then, the vehicle reservation charging management system obtains the strategy configuration instruction set by the target object and performs format verification and legality verification on the instruction, including: whether the charging end time is after the charging start time, whether the target state of charge is within a safe range, etc. After verification, the vehicle reservation charging management system converts the above strategy configuration into a unified standardized numerical format. For example, the charging start time and charging end time are converted into minute offsets starting from 0:00 of the day (i.e., integers), the target state of charge is converted into an integer between 0 and 100, and the execution flag is converted into a bitmask of 0 or 1, where 0 indicates that timeout is not allowed and 1 indicates that timeout is allowed. Finally, the vehicle reservation charging management system calls the predefined charging strategy data structure and fills the above numerical fields into key-value pairs containing strategy identifier, period mask, time parameter, target state of charge, and execution flag to form a charging strategy corresponding to the strategy configuration instruction input by the target object.

[0043] Optionally, the above charging strategy includes: charging start time and charging end time; or, charging start time and target state of charge; or, charging start time, charging end time, target state of charge and execution flag, wherein the execution flag is used to indicate whether to continue charging until the vehicle's state of charge reaches the target state of charge if the charging end time has been reached but the vehicle's state of charge has not reached the target state of charge.

[0044] It should be noted that the above charging strategy is highly flexible, allowing the target entity to selectively define strategy configuration instructions according to actual needs, forming three effective charging strategy forms, including:

[0045] (1) The target object only sets the charging start time and charging end time. This strategy configuration instruction means that the target object only cares about the charging time window and does not specify the charging target. The target vehicle will start charging within the specified charging start time and forcibly stop when the charging end time is reached, regardless of the battery level when charging stops. This strategy is suitable for scenarios where the target object only wants to charge during off-peak hours and has no strict requirements on the final battery level, such as charging after daily commuting.

[0046] (2) Setting only the charging start time and target state of charge indicates that the target user is concerned with how much charge the battery needs to reach, rather than the charging time. The vehicle reservation charging management system will start charging within the charging start time and continue charging until the battery state of charge reaches the target value, regardless of the charging time. This strategy is suitable for scenarios where the target user wants to ensure that the battery is fully charged before the next trip and has no limit on the charging time, such as a full charge preparation before a long trip.

[0047] (3) Setting the charging start time, charging end time, target state of charge, and execution flag is the most complete strategy configuration instruction. The target vehicle will be constrained in both time and energy dimensions simultaneously, and the execution flag will specify the response strategy when the charging end time is reached but the target state of charge is not reached. Specifically, if the execution flag is "stop", charging will be terminated when the charging end time is reached, even if the battery energy has not reached the target state of charge; if the execution flag is "continue charging", charging will continue after the end time is reached until the target state of charge of the battery is reached, realizing the dual constraints and intelligent trade-off of time and energy, taking into account both cost control and range assurance.

[0048] For example, step S22 above can be understood as follows: First, the target object inputs a strategy configuration command or scenario configuration command through the central control screen or mobile application of the target vehicle. The scenario configuration command includes at least: a periodic date range (e.g., Monday to Friday, Saturday to Sunday, etc.), a geographical location label (e.g., home, company, public charging station), and a date type (e.g., weekday, rest day, etc.), used to define the trigger scenario conditions applicable to a certain charging strategy. Then, the vehicle reservation charging management system obtains the scenario configuration command set by the target object and converts the scenario configuration command set by the target object into a corresponding binary mask value (e.g., "Monday to Friday" corresponds to 0b1111100). At the same time, it can support custom dates, holiday linkage, or location labels and other extended fields to form structured effective scenario information.

[0049] Optionally, the above-mentioned effective scenario information includes at least one of the following: effective date information and effective location information. In actual application scenarios, both effective date information and effective location information may affect the triggering of the charging strategy, but effective date information often reflects the charging needs of the target object based on time patterns and has obvious periodic characteristics. Therefore, the effective date information has a higher priority than the effective location information.

[0050] The effective date information includes at least one of the following: a date determined according to a preset cycle, a specified date, or the date corresponding to the target event in the preset memo. The specific forms of the above-mentioned effective date information are as follows:

[0051] A date determined by a preset cycle is a date set based on a fixed time cycle. It divides time into repetitive cycles, and the charging strategy takes effect at specific times or time periods within each cycle. Common cycles are based on days, weeks, months, years, etc. For example, setting the weekdays (Monday to Friday) as the effective cycle for a certain charging strategy, or the 1st and 15th of each month as the effective cycle for another charging strategy, can help the target audience achieve a regular charging schedule according to their daily life and work rhythm.

[0052] The specified date: This refers to a specific day or several consecutive days that the target user manually specifies as the effective date of the charging strategy based on their specific needs. These dates usually do not follow a fixed cycle, but are determined based on the target user's temporary arrangements or specific events. When the target user has special travel plans, activity arrangements, or electricity needs, specifying a date can ensure that the vehicle has sufficient battery power at a specific time to cope with various emergencies.

[0053] Dates corresponding to target events in preset memos: Target users record various target events in their memos, such as meetings, appointments, trips, and medical checkups. Target vehicles can trigger corresponding charging strategies based on the dates of preset events in these memos, closely linking the charging strategy to the target user's important events. This ensures that the target vehicle has adequate battery power when important events occur. For example, if the target user records in their memo that they need to pick someone up from the airport the next day, the vehicle's scheduled charging management system will detect this event and automatically execute the corresponding charging strategy that evening, preventing insufficient battery power from affecting the pick-up plan. This achieves more intelligent charging management and improves the user experience.

[0054] Optionally, the aforementioned effective date information includes a weekday mask; wherein the weekday mask is a 7-bit binary field, and each bit in the binary field is used to indicate whether the corresponding charging strategy is effective on a given day of the week (for example, a bit value of 1 indicates that the strategy is effective on that day, and a bit value of 0 indicates that the strategy is not effective on that day). The target device does not need to manually set the charging time each time; it only needs to set the cycle once, and the vehicle reservation charging management system will automatically execute the charging strategy according to the stored effective date information, reducing the management burden on the target device.

[0055] For example, step S23 above can be understood as follows: by constructing a structured data table, the charging strategy set by the target object and the corresponding effective scenario information are semantically bound and stored in a fixed area. The specific steps are as follows: First, after generating the charging strategy, the vehicle reservation charging management system extracts its core parameters, including charging start time, charging end time, target state of charge, execution flag, etc., and encapsulates them into a unified key-value pair structure; then, the effective scenario information is converted into a weekday mask that can be recognized by the vehicle reservation charging management system; subsequently, the vehicle reservation charging management system combines the above charging strategy key-value pair structure and the corresponding effective scenario information mask as a pair of related fields into an independent record entry, establishes a mapping relationship between the charging strategy and the effective scenario information, and assigns a unique strategy identifier to the entry and writes it into non-volatile memory, establishing a scenario strategy configuration library in memory to achieve fast location and reading from the effective scenario information to the charging strategy.

[0056] In this embodiment, by deeply analyzing the strategy configuration instructions and scenario configuration instructions of the target object, and establishing a one-to-one mapping relationship between the two, the information is stored in the strategy configuration library of the vehicle reservation charging management system in a structured form, forming a knowledge base from scenario to strategy that can be called directly and for a long time. This enables the target object to build multiple sets of differentiated charging solutions at once, achieving an efficient management solution of one-time configuration and multi-scenario reuse.

[0057] Optionally, a target charging strategy matching the target scenario information is determined from a preset scenario strategy configuration library, including the following steps:

[0058] Step S31: Determine the charging strategy that matches the effective scenario information and the target scenario information from the scenario strategy configuration library as the candidate charging strategy;

[0059] Step S32: If no candidate charging strategy exists, determine the default charging strategy as the target charging strategy, or generate a prompt message to instruct the target object to configure the target charging strategy.

[0060] Step S33: If there is only one candidate charging strategy, determine the candidate charging strategy as the target charging strategy.

[0061] Step S34: In the case of multiple candidate charging strategies, determine the preset priority of each candidate charging strategy and determine the candidate charging strategy with the highest preset priority as the target charging strategy; or, obtain the historical usage records of each candidate charging strategy and determine the most recently used candidate charging strategy as the target charging strategy.

[0062] For example, step S31 above can be understood as follows: After the vehicle reservation charging management system detects that the charging gun is connected to the charging equipment and completes a physical handshake, it triggers a charging strategy matching process. The specific steps are as follows: First, the vehicle reservation charging management system obtains the current precise year, month, day, and week information through the real-time clock module and converts the current week number into a week mask; it obtains the current vehicle location information through the positioning module; if calendar event linkage is enabled, it reads the marked events associated with the current date in the local or cloud calendar through the synchronization module, and uses the week mask, date, location, and event information read above as the target scenario information. Next, it retrieves effective scenario information that matches the target scenario information from the scenario strategy configuration library, including: week mask matching, specified date matching, calendar event matching, and location matching. Finally, according to the preset mapping relationship in the scenario strategy configuration library, the charging strategy corresponding to the successfully matched effective scenario information is determined as a candidate charging strategy, and a candidate charging set is formed.

[0063] For example, step S32 above can be understood as follows: If the vehicle reservation charging management system fails to find an effective scenario information matching the target scenario information in the scenario strategy configuration library, i.e., the candidate charging strategy set is empty, the vehicle reservation charging management system enters the default strategy processing mechanism. The specific steps are as follows: The vehicle reservation charging management system determines whether a default charging strategy is configured. If the default charging strategy has been preset and stored in non-volatile memory, the default charging strategy is directly read as the target charging strategy. The parameters of the default strategy include the preset start charging time, end charging time, target state of charge, and execution flag, etc. The above parameter values ​​are initialized at the factory or during the first configuration, or are manually set by the target object in the interactive interface. If no default charging strategy is configured, the vehicle reservation charging management system generates a prompt message to instruct the target object to configure the target charging strategy, and outputs a visual or voice prompt message through the interactive interface to instruct the target object to configure an effective charging strategy. The prompt content includes, but is not limited to: No charging strategy was matched, please set the current charging plan or please configure the charging parameters for the current date, etc.

[0064] For example, step S33 above can be understood as follows: when the vehicle reservation charging management system retrieves effective scenario information that uniquely matches the target scenario information in the scenario strategy configuration library, that is, when the number of elements in the candidate charging strategy set is one, the vehicle reservation charging management system directly determines the candidate charging strategy as the target charging strategy without further arbitration or intervention by the target object.

[0065] For example, step S34 above can be understood as follows: When the vehicle reservation charging management system retrieves multiple effective scenario information matching the target scenario information from the scenario strategy configuration library, i.e., when the number of elements in the candidate charging strategy set is greater than one, the multi-strategy conflict problem can be resolved through two decision logics: static priority matching or dynamic usage frequency. The static priority matching includes: the vehicle reservation charging management system extracts the preset priority of the effective scenario information corresponding to each candidate charging strategy, compares the priorities of each effective scenario information, selects the effective scenario information with the highest priority, and uses the candidate charging strategy corresponding to that effective scenario information as the target strategy. For example, when "Thursday corresponds to 10:00–6:00 charging strategy" and "not at home corresponds to no charging strategy" match simultaneously, the charging strategy is selected to be executed based on the principle that the priority of the effective date information is higher than that of the effective location information, to meet the commuting needs of the next day. The dynamic usage frequency includes: the vehicle reservation charging management system reads the timestamp of the most recent execution of each candidate charging strategy in the candidate charging strategy set, compares the timestamps of each candidate charging strategy, and selects the candidate charging strategy with the latest timestamp as the target charging strategy.

[0066] In this embodiment, the system first automatically matches target scenario information such as the current date, time, or location to accurately filter all candidate strategies that match the target scenario, avoiding mismatches caused by fuzzy rules. If no matching strategy exists, the system actively executes the default charging strategy or guides the user to configure a charging strategy, ensuring that the charging function is always available and improving the system's fault tolerance and availability. When only a single candidate charging strategy exists, it is directly used as the target charging strategy to ensure response efficiency. When multiple candidate strategies exist, the target charging strategy is determined according to preset priorities to ensure the determinism of strategy execution. At the same time, historical usage records are introduced as a basis for dynamic optimization, realizing a dual intelligent judgment of "rule priority and habit assistance," which significantly reduces the execution uncertainty caused by strategy conflicts, making the target charging strategy both conform to preset rules and fit the user's actual usage habits.

[0067] After determining the target charging strategy that matches the target scenario information from the preset scenario strategy configuration library, in order to ensure that the execution of the charging strategy conforms to the user's current actual charging intention and avoid unexpected charging behavior due to charging strategy conflicts or scenario misjudgment, a manual confirmation mechanism is further added. The specific steps are as follows:

[0068] Step S41: Generate confirmation information in the interactive interface to confirm whether to execute the target charging strategy;

[0069] Step S42: In response to the confirmation command input by the target object in the interactive interface, perform a charging operation on the target vehicle according to the target charging strategy;

[0070] Step S43: In response to the strategy change instruction input by the target object in the interactive interface, the target charging strategy is changed according to the strategy change instruction, and the charging operation is performed on the target vehicle according to the changed charging strategy.

[0071] For example, step S41 above can be understood as follows: after the vehicle reservation charging management system completes the automatic matching and determination of the target charging strategy, a human-machine interaction confirmation process is triggered. The system displays the information of the currently selected target charging strategy to the target object through the interactive interface with graphic or voice prompts, including but not limited to the charging start time, end time, target charge state and effective scenario description, so as to clearly inform the target vehicle of the charging behavior that is about to be performed, and generates confirmation information on whether to execute the charging strategy.

[0072] For example, step S42 above can be understood as follows: After the prompt information is presented, the vehicle reservation charging management system enters a waiting state, monitors the input commands on the interactive interface, and if the target object is detected to input a confirmation command (such as clicking the "Start Charging" button, voice confirmation, or physical button confirmation), the vehicle reservation charging management system immediately terminates the waiting state, writes the parameters of the target charging strategy into the execution buffer of the charging control module, and sends a start command to the on-board charger and battery management system through the vehicle controller local area network, and performs charging operation on the target vehicle according to the target charging strategy.

[0073] For example, step S43 above can be understood as follows: After the prompt information is presented, the vehicle reservation charging management system enters a waiting state and monitors the input commands on the interactive interface. If it detects that the target object has entered a strategy change command (such as clicking the modify strategy option, switching to other preset strategies, or manually entering new parameters), the vehicle reservation charging management system will stop the execution preparation of the current target charging strategy and enter the charging strategy reconfiguration process: First, the interactive interface switches to the strategy selection or parameter editing interface and receives the target object's reset of charging time, target state of charge, or execution conditions; then, the vehicle reservation charging management system uses the newly input charging parameter combination as the new charging strategy, updates it to the execution buffer, and re-verifies its integrity and legality; finally, after confirming that there are no errors, the vehicle reservation charging management system uses the changed charging strategy as the new target charging strategy and performs charging operations on the target vehicle according to the target charging strategy.

[0074] This application's embodiments take into account the potential for temporary changes in the target user's lifestyle (such as canceled weekend trips or the need to charge in advance for unexpected overtime work). The system allows the target user to change the charging strategy through the interactive interface, rather than forcibly implementing a preset target charging strategy. This gives the system the flexibility of "preset as the primary method and manual intervention as a supplement," retaining both the efficiency of intelligent automation and the flexibility of manual intervention, significantly improving system applicability and target user satisfaction.

[0075] The steps of the vehicle reservation charging management method in this application embodiment are explained below with reference to optional examples.

[0076] Step 1: The target user sets up the following two charging scenarios at once through the vehicle's central control screen (i.e., the interactive interface):

[0077] Scenario A (Weekday Scenario): Effective Date Information: Monday, Tuesday, Wednesday, Thursday, Friday. Charging Start Time: 23:00, Charging End Time: 05:00 the next day, Target State of Charge: 80%, Execution Flag: No need to reach the target state of charge.

[0078] Scenario B (Weekend Scenario): Effective Date Information: Friday and Saturday. Charging Start Time: 22:30, Charging End Time: 08:00 the next day, Target State of Charge: 100%, Execution Flag: Target State of Charge needs to be reached.

[0079] The second step involves the vehicle reservation charging management system executing the charging process, such as... Figure 2 As shown, from the moment a charging connection event is detected, the vehicle reservation charging management system first reads the target vehicle's date, day of the week, and location to determine the target charging scenario. Next, it determines the target charging strategy based on the number of matches between the target charging scenario and the effective scenario information. The determination of the target charging strategy falls into three categories: if the match count is 0, the default charging strategy is determined as the target charging strategy; if the match count is 1, the candidate charging strategy corresponding to the unique effective scenario information is directly selected as the target charging strategy; if the match count is greater than 1, the target charging strategy is selected based on the preset priority of the effective scenario information. Then, based on the selected target charging strategy, a charging plan is generated and issued. The system reads the target strategy identifier and the current state of charge (SOC) of the battery management system. Based on the relationship between the current SOC and the target SOC, as well as the relationship between the current time and the start charging time, it generates "Do not charge," "Charge immediately," or "Reserve charging" commands, respectively. These commands are encapsulated into CAN messages and sent to the onboard charger and battery management system, subsequently entering the real-time monitoring stage of the charging process. When the charging deadline is reached, the target state of charge reaches the target value, or a charging stop command is received from the target object, a stop charging command is sent to end the charging process. The entire process realizes fully automated control from charging connection triggering to charging end, ensuring that the charging process meets the preset scenario and target object requirements.

[0080] Taking Thursday evening as an example: When the target user inserts the charging gun into the charging device, the system reads the date as Thursday. After matching it with the scene period mask, it determines the unique matching scene A, selects the charging strategy corresponding to the scene, and generates the target charging strategy: "Wait until the start charging time of 23:00 to start, and stop charging when the charge status reaches 80% or the end charging time of 05:00".

[0081] Taking Friday evening as an example: The target user inserts the charging gun into the charging device, and the system reads the date as Friday, which matches the period mask of both scenarios A and B. Scenario B is selected based on preset rules (e.g., weekend scenarios are prioritized). The system generates the instruction: "Wait until 22:30 to start, charge to 100%". After charging starts, the system continuously monitors until the battery reaches 100% on Saturday morning, at which point it automatically stops.

[0082] Sunday evening: The date is "Sunday". There is no matching scenario. The system can execute the default strategy (such as charging immediately or prompting the target user that there is no appointment). The target user can choose not to charge or start manually.

[0083] The hardware and data interaction of the vehicle reservation charging management system is divided into a scenario setting phase and a charging execution phase. The specific interaction process is as follows:

[0084] The specific interaction process during the scene setup phase is as follows: Figure 3 As shown: The target object sends scene configuration commands to the vehicle reservation charging management system through the interactive interface, sets charging-related parameters and scene rules, and completes the scene configuration. The real-time clock module provides accurate date and time information to the vehicle reservation charging management system via the CAN (Controller Area Network) bus, while the battery management system provides real-time feedback on the battery's current state of charge (SOC). The charging control module, as the core of the vehicle reservation charging management system, receives scene configuration commands from the interactive interface, date / time information from the real-time clock, and current SOC data from the battery management system, and performs comprehensive processing and decision-making based on this information. On one hand, the charging control module stores the parameters of scenes A and B, including period masks 0x7C and 0x60, time, and SOC values, in a structure form in its on-chip Flash memory, performs read and store operations with the scene configuration storage area, and selects the target object's preset target charging strategy. On the other hand, based on the target charging strategy, it sends charging control commands to the on-board charger to precisely regulate the charging process, achieving intelligent and personalized vehicle charging control.

[0085] The specific interaction process during the charging execution phase (taking Friday as an example) is as follows: Figure 4 The signal transmission architecture of the vehicle reservation charging management system is shown, encompassing four parts: the user interaction layer, the core control layer, the vehicle communication network, and the execution and sensing layer. The user interface of the user interaction layer is connected to the main control unit of the core control layer via serial communication, used for transmitting target object commands and displaying information; the real-time clock module in the core control layer connects via I / O... 2The C-band (Inter-Integrated Circuit) bus communicates with the charging control module, providing precise date and day-of-week information, e.g., day of the week = 5 (i.e., Friday). The charging control module reads the scenario strategy configuration table to obtain the effective scenario information (including scenario A and scenario B) that matches the target scenario information, queries the priority configuration table, and determines to execute scenario B. Subsequently, it connects to the CAN bus transceiver in the vehicle communication network via the parallel data / address bus to request the current state of charge from the battery management system. The charging control module calculates the difference between the current time and the start charging time, and transmits the charging control command to the on-board charger in the execution and sensing layer via the differential signal line of the CAN bus transceiver, e.g., scheduled start time: 22:30, target state of charge 100%. In the execution and sensing layer, the on-board charger receives the charging control command signal and interacts with the battery management system via the charging guidance circuit and DC power supply line. During charging, the battery management system periodically reports the state of charge to the charging control module. When the target state of charge reaches 100%, the charging control module immediately sends a stop charging command to the on-board charger. The entire system uses different communication methods and signal transmission paths to achieve the issuance of charging commands, monitoring of vehicle status, and precise control of the charging process.

[0086] Through the above steps, a scenario strategy configuration library based on date and weekday is built into the vehicle reservation charging management system. This allows users to preset multiple complete strategies, including charging start and end times, target state of charge, and execution flags, for typical life scenarios such as weekday commutes and weekend long-distance trips. These strategies are stored in the strategy storage module, forming repeatable and predictable charging behavior templates. Each time a charging connection event is triggered, the system, based on a real-time clock module, automatically identifies the target charging strategy corresponding to the current target scenario and executes the charging operation through a simple and reliable strategy matching mechanism. No user intervention is required throughout the process, completely eliminating the operational burden and range anxiety caused by users forgetting to manually adjust the charging strategy. By abandoning complex algorithms and cloud dependencies and adopting a low-power, localized, and deterministic decision-making mechanism, the system not only significantly improves stability and response speed but also achieves the intelligent charging goal of "one-time setup, long-term maintenance-free" at the user experience level. This precisely matches users' regular driving habits and achieves a comprehensive balance of economy, safety, and convenience.

[0087] Example 2

[0088] According to an embodiment of this application, a system for implementing the vehicle reservation charging management method in Embodiment 1 is also provided, such as... Figure 5 As shown, the system includes at least: a policy configuration module 51, a policy storage module 52, a scene detection module 53, a policy matching module 54, and a charging control module 55, wherein:

[0089] The strategy configuration module 51 is used to respond to the configuration instructions of the target object and configure multiple charging strategies and the effective scenario information corresponding to each charging strategy.

[0090] The strategy storage module 52 is used to store multiple charging strategies and the effective scenario information corresponding to each charging strategy;

[0091] The scene detection module 53 is used to respond to the charging connection event of the target vehicle and obtain the target scene information of the current scene of the target vehicle. The charging connection event includes: the charging gun is inserted into the target vehicle and is identified as a valid charging connection. The target scene information includes at least one of the following: date information and location information.

[0092] The strategy matching module 54 is used to determine the target charging strategy that matches the target scenario information from the strategy storage module;

[0093] The charging control module 55 is used to perform charging operations on the target vehicle according to the target charging strategy.

[0094] The following section describes the functions of each module of the system in conjunction with the specific implementation process.

[0095] Optionally, the strategy configuration module responds to the strategy configuration command input by the target object in the interactive interface, generates a charging strategy corresponding to the strategy configuration command; responds to the scene configuration command input by the target object in the interactive interface, generates effective scene information corresponding to the scene configuration command; establishes a mapping relationship between the charging strategy and the effective scene information, and uses the mapping relationship as a record in a structured data table.

[0096] Optionally, the above charging strategy includes: charging start time and charging end time; or, charging start time and target state of charge; or, charging start time, charging end time, target state of charge and execution flag, wherein the execution flag is used to indicate whether to continue charging until the vehicle's state of charge reaches the target state of charge if the charging end time has been reached but the vehicle's state of charge has not reached the target state of charge.

[0097] Optionally, the above-mentioned effective scenario information includes at least one of the following: effective date information and effective location information; wherein, the effective date information has a higher effective priority than the effective location information; the effective date information includes at least one of the following: a date determined according to a preset cycle, a specified date, and a date corresponding to the target event in the preset memo.

[0098] Optionally, the above effective date information includes: a weekday mask; wherein the weekday mask is a 7-bit binary field, and each bit in the weekday mask is used to indicate whether the charging strategy is effective on a day of the week.

[0099] Optionally, the strategy matching module can determine the target charging strategy that matches the target scenario information from the strategy storage module in the following ways: determine the charging strategy that matches the effective scenario information with the target scenario information from the strategy storage module as a candidate charging strategy; if there is no candidate charging strategy, determine the default charging strategy as the target charging strategy, or generate a prompt message to instruct the target object to configure the target charging strategy; if there is only one candidate charging strategy, determine the candidate charging strategy as the target charging strategy; if there are multiple candidate charging strategies, determine the preset priority of each candidate charging strategy and determine the candidate charging strategy with the highest preset priority as the target charging strategy, or obtain the historical usage records of each candidate charging strategy and determine the most recently used candidate charging strategy as the target charging strategy.

[0100] Optionally, after determining the target charging strategy that matches the target scenario information from the strategy storage module, the charging control module generates confirmation information in the interactive interface to confirm whether to execute the target charging strategy; in response to the confirmation command input by the target object in the interactive interface, it performs a charging operation on the target vehicle according to the target charging strategy; in response to the strategy change command input by the target object in the interactive interface, it changes the target charging strategy according to the strategy change command, and performs a charging operation on the target vehicle according to the changed charging strategy.

[0101] It should be noted that each module in the system of this application embodiment corresponds one-to-one with each implementation step of the vehicle reservation charging management method in embodiment 1. Since embodiment 1 has been described in detail, some details not shown in this embodiment can be referred to embodiment 1, and will not be elaborated further here.

[0102] Example 3

[0103] According to an embodiment of this application, a computer program product is also provided, which includes a computer program, wherein when the computer program is executed by a processor, it implements the vehicle reservation charging management method in Embodiment 1.

[0104] According to an embodiment of this application, a non-volatile storage medium is also provided, which includes a stored computer program, wherein the device containing the non-volatile storage medium executes the vehicle reservation charging management method in Embodiment 1 by running the computer program.

[0105] According to an embodiment of this application, a processor is also provided for running a computer program, wherein the computer program executes the vehicle reservation charging management method in Embodiment 1 when it runs.

[0106] According to an embodiment of this application, an electronic device is also provided, comprising: a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the vehicle reservation charging management method of Embodiment 1 through the computer program.

[0107] Specifically, the computer program executes the following steps during runtime: In response to a charging connection event of the target vehicle, it obtains target scene information of the current scene of the target vehicle, wherein the charging connection event includes: the charging gun is inserted into the target vehicle and is identified as a valid charging connection, and the target scene information includes at least one of the following: date information and location information; it determines a target charging strategy that matches the target scene information from a preset scene strategy configuration library, wherein the scene strategy configuration library stores multiple pre-configured charging strategies and the effective scene information corresponding to each charging strategy; and it performs a charging operation on the target vehicle according to the target charging strategy.

[0108] According to an embodiment of this application, a vehicle is also provided, comprising: the vehicle reservation charging management system of Embodiment 2, wherein the vehicle reservation charging management system comprises: a strategy configuration module, configured to respond to configuration instructions of a target object and configure multiple charging strategies and effective scenario information corresponding to each charging strategy; a strategy storage module, configured to store multiple charging strategies and effective scenario information corresponding to each charging strategy; a scenario detection module, configured to respond to charging connection events of a target vehicle and obtain target scenario information of the current scenario of the target vehicle, wherein the charging connection event includes: the charging gun being inserted into the target vehicle and being identified as a valid charging connection, and the target scenario information includes at least one of the following: date information and location information; a strategy matching module, configured to determine a target charging strategy matching the target scenario information from the strategy storage module; and a charging control module, configured to perform charging operations on the target vehicle according to the target charging strategy.

[0109] As an alternative implementation, the above-mentioned electronic device may exist in the form of a mobile terminal, a computer terminal, or a similar computing device. Figure 6 A hardware block diagram of an electronic device for implementing a vehicle reservation charging management method is shown. Figure 6 As shown, the electronic device 60 may include one or more (shown as 602a, 602b, ..., 602n) processors 602 (processors 602 may include, but are not limited to, processing devices such as microprocessors or programmable logic devices), a memory 604 for storing data, and a transmission device 606 for communication functions. In addition, it may also include: a display, an input / output interface, a universal serial bus port (which may be included as one of the ports of a BUS bus), a network interface, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 6The structure shown is for illustrative purposes only and does not limit the structure of the aforementioned electronic device. For example, electronic device 60 may also include components that are more... Figure 6 The more or fewer components shown, or having the same Figure 6 The different configurations shown.

[0110] It should be noted that the aforementioned one or more processors 602 and / or other data processing circuits are generally referred to herein as "data processing circuits". These data processing circuits may be embodied, in whole or in part, in software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuits may be a single, independent processing module, or may be integrated, in whole or in part, into any other element of the electronic device 60. As involved in the embodiments of this application, the data processing circuits serve as a processor control mechanism (e.g., selection of a variable resistor termination path connected to an interface).

[0111] The memory 604 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the vehicle reservation charging management method in this embodiment. The processor 602 executes various functional applications and data processing by running the software programs and modules stored in the memory 604, thereby realizing the aforementioned vehicle reservation charging management method. The memory 604 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 604 may further include memory remotely located relative to the processor 602, and these remote memories can be connected to the electronic device 60 via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0112] The transmission device 606 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of the electronic device 60. In one example, the transmission device 606 includes a network adapter that can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 606 may be a radio frequency module used for wireless communication with the Internet.

[0113] The display can be, for example, a touchscreen LCD display, which enables the target object to interact with the target object interface of the electronic device 60.

[0114] The sequence numbers of the above embodiments are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0115] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0116] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between units or modules may be electrical or other forms.

[0117] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0118] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0119] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, read-only memory, random access memory, portable hard drive, magnetic disk, or optical disk.

[0120] The above are merely preferred embodiments of this application. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for managing vehicle reservation charging, characterized in that, include: In response to a charging connection event of a target vehicle, target scene information of the current location of the target vehicle is obtained, wherein the charging connection event includes: the charging gun is inserted into the target vehicle and is identified as a valid charging connection, and the target scene information includes at least one of the following: date information and location information; A target charging strategy matching the target scenario information is determined from a preset scenario strategy configuration library, wherein the scenario strategy configuration library stores multiple pre-configured charging strategies and the effective scenario information corresponding to each charging strategy. The target vehicle is charged according to the target charging strategy.

2. The method according to claim 1, characterized in that, The scenario strategy configuration library is in the format of a structured data table, and the construction process of the scenario strategy configuration library includes: In response to the strategy configuration command input by the target object in the interactive interface, a charging strategy corresponding to the strategy configuration command is generated; In response to the scene configuration command input by the target object in the interactive interface, generate effective scene information corresponding to the scene configuration command; Establish a mapping relationship between the charging strategy and the effective scenario information, and treat the mapping relationship as a record in the structured data table.

3. The method according to claim 1, characterized in that, The charging strategy includes: Charging start time and charging end time; or, Charging start time and target state of charge; or, The charging start time, charging end time, target state of charge, and execution flag are specified. The execution flag indicates whether to continue charging until the vehicle's state of charge reaches the target state of charge if the charging end time has been reached but the vehicle's state of charge has not yet reached the target state of charge.

4. The method according to claim 1, characterized in that, The effective scenario information includes at least one of the following: effective date information, effective location information; wherein... The effective date information has a higher priority than the effective location information; The effective date information includes at least one of the following: a date determined according to a preset cycle, a specified date, or a date corresponding to a target event in a preset memo.

5. The method according to claim 4, characterized in that, The effective date information includes: a weekday mask; wherein the weekday mask is a 7-bit binary field, and each bit in the weekday mask is used to indicate whether the charging strategy is effective on a day of the week.

6. The method according to claim 1, characterized in that, Determine a target charging strategy from a preset scenario strategy configuration library that matches the target scenario information, including: The charging strategy that matches the effective scenario information with the target scenario information is determined from the scenario strategy configuration library as a candidate charging strategy; If no candidate charging strategy exists, determine the default charging strategy as the target charging strategy, or generate a prompt message to instruct the target object to configure the target charging strategy. If only one candidate charging strategy exists, the candidate charging strategy is determined as the target charging strategy. In the presence of multiple candidate charging strategies, a preset priority is determined for each candidate charging strategy, and the candidate charging strategy with the highest preset priority is determined as the target charging strategy. Alternatively, the historical usage records of each candidate charging strategy are obtained, and the candidate charging strategy used most recently is determined as the target charging strategy.

7. The method according to claim 1, characterized in that, After determining a target charging strategy that matches the target scenario information from a preset scenario strategy configuration library, the method further includes: Generate confirmation information in the interactive interface to confirm whether to execute the target charging strategy; In response to the confirmation command input by the target object in the interactive interface, a charging operation is performed on the target vehicle according to the target charging strategy; In response to a strategy change command input by the target object in the interactive interface, the target charging strategy is changed according to the strategy change command, and a charging operation is performed on the target vehicle according to the changed charging strategy.

8. A vehicle reservation charging management system, characterized in that, include: The strategy configuration module is used to respond to the configuration instructions of the target object and configure multiple charging strategies and the effective scenario information for each charging strategy. The strategy storage module is used to store the multiple charging strategies and the effective scenario information corresponding to each charging strategy; The scene detection module is used to respond to the charging connection event of the target vehicle and obtain the target scene information of the current scene of the target vehicle. The charging connection event includes: the charging gun is inserted into the target vehicle and is identified as a valid charging connection. The target scene information includes at least one of the following: date information and location information. A strategy matching module is used to determine a target charging strategy that matches the target scenario information from the strategy storage module; The charging control module is used to perform charging operations on the target vehicle according to the target charging strategy.

9. A computer program product, characterized in that, include: A computer program, wherein when executed by a processor, the computer program implements the vehicle reservation charging management method according to any one of claims 1 to 7.

10. A vehicle, characterized in that, include: The vehicle reservation charging management system as described in claim 8.

Images