Vehicle charging management method, electronic device, and storage medium

Abstract

This application discloses a vehicle charging management method, electronic device, and storage medium. Relating to the field of vehicle control technology, the vehicle charging management method includes: responding to a charging strategy received at the application layer, writing a structured data packet corresponding to the charging strategy into an information processing box with an integrated hardware real-time clock; configuring a wake-up value for the hardware real-time clock based on the structured data packet; and controlling the vehicle to enter a low-power sleep mode. This application overcomes the technical defect of charging reservation failure due to fluctuations in the mobile terminal's operating environment, achieving stable triggering and reliable execution of charging reservations, and ensuring that the vehicle charging process is not affected by the terminal's state.

Description

Technical Field

[0001] This application relates to the field of vehicle control technology, and in particular to a vehicle charging management method, electronic device, and storage medium. Background Technology

[0002] Currently, users can use a mobile app or mini-program to view the number of available charging stations and electricity prices at different times in real time. Users can select an available charging station for immediate reservation. Once the reservation is successful, the charging station will be locked, and users can arrive within the reserved time and scan the code to start charging. Charging costs are calculated based on the time-of-use electricity price corresponding to the actual charging period.

[0003] However, the relevant technologies rely on mobile applications, network connections, and cloud command issuance. If any link in the communication process encounters a problem, such as the phone freezing, the application being killed in the background, poor network signal, or cloud delay, the charging reservation may fail. Summary of the Invention

[0004] The main objective of this application is to provide a vehicle charging management method, electronic device, and storage medium, which aims to solve the technical problem of charging reservation failure caused by fluctuations in the operating environment of mobile terminals in related technologies.

[0005] To achieve the above objectives, this application provides a vehicle charging management method, the vehicle charging management method comprising:

[0006] In response to the charging strategy received by the application layer, the structured data packet corresponding to the charging strategy is written into the information processing box of the integrated hardware real-time clock. Configure the wake-up value of the hardware real-time clock based on the structured data packet; Control the vehicle to enter a low-power sleep mode.

[0007] In one embodiment, writing the structured data packet corresponding to the charging strategy into the information processing box with an integrated hardware real-time clock includes: Through the application layer: generate and send the structured data packet corresponding to the charging strategy to the domain controller; The domain controller encapsulates the structured data packet into a request message and sends the request message to the information processing box of the integrated hardware real-time clock. The information processing box parses the request message to obtain the structured data packet and writes the structured data packet into the local flash memory.

[0008] In one embodiment, configuring the wake-up value of the hardware real-time clock based on the structured data packet includes: The wake-up value is determined based on the current time recorded by the hardware real-time clock and the charging time contained in the structured data packet; Configure the hardware real-time clock based on the wake-up value.

[0009] In one embodiment, controlling the vehicle to enter a low-power sleep mode includes: The circuit corresponding to the hardware real-time clock is kept powered, and other circuits in the information processing box except for the hardware real-time clock are kept powered off, so that the vehicle enters the low-power sleep mode.

[0010] In one embodiment, after setting the wake-up value of the hardware real-time clock based on the structured data packet, the process includes: In response to a hardware interrupt signal generated when the hardware real-time clock reaches the wake-up value, the information processing box, which is in a power-down state, is woken up. The information processing box reads the structured data packet from the local flash memory and generates a charging strategy message based on the structured data packet; Broadcast the charging strategy message to wake up the vehicle's controller; Based on the awakened controller, the vehicle is controlled to execute the charging process corresponding to the charging strategy message.

[0011] To achieve the above objectives, this application provides a vehicle charging management method, the vehicle charging management method comprising: In response to a configuration operation triggered by a charging strategy configuration control in the vehicle's interactive interface, or in response to terminal configuration data sent by the server, a charging strategy is determined, wherein the charging strategy includes at least one of charging period, charging date, desired charge level, and charging location.

[0012] In one embodiment, the charging strategy configuration control includes at least one of a first control, a second control, a third control, a fourth control, and a fifth control. The first control is used to configure the charging period, the second control is used to configure the desired power level, the third control is used to configure the charging date, the fourth control is used to configure the charging location, and the fifth control is used to configure both the charging period and the charging date.

[0013] In one embodiment, after determining the charging strategy, the process includes: If the current time and / or current location of the vehicle meet any set of the activation conditions corresponding to the charging strategy, the charging process corresponding to the charging strategy shall be executed.

[0014] In addition, to achieve the above objectives, this application also provides an electronic device, the electronic device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the vehicle charging management method as described above.

[0015] In addition, to achieve the above objectives, this application also provides a storage medium, which is a computer-readable storage medium, on which a program implementing a vehicle charging management method is stored, and the program implementing the vehicle charging management method is executed by a processor to implement the steps of the vehicle charging management method as described above.

[0016] This application provides a vehicle charging management method. Firstly, in response to a charging strategy received at the application layer, the method writes the structured data packet corresponding to the charging strategy into an information processing box with an integrated hardware real-time clock. This completely eliminates dependence on the mobile terminal's operating environment, network connection, and online status, breaking the inherent limitations of traditional charging reservations that rely on the mobile terminal to initiate, maintain, and trigger commands. Then, based on the structured data packet, the method configures the wake-up value of the hardware real-time clock and controls the vehicle to enter a low-power sleep mode. The entire charging reservation process is completed through independent hardware storage, autonomous hardware timing, and timed hardware triggering, without requiring continuous participation or operation of the mobile terminal.

[0017] In summary, this application, by combining the collaborative operations of writing the structured data packets corresponding to the charging strategy into the information processing box with an integrated hardware real-time clock, configuring the wake-up value of the hardware real-time clock based on the structured data packets, and controlling the vehicle to enter a low-power sleep mode, constructs a terminal-independent charging reservation execution mechanism with hardware-level local storage and independent timed wake-up as the core. This fundamentally overcomes the technical defects of charging reservation failure caused by fluctuations in the mobile terminal's operating environment, achieves stable triggering and reliable execution of charging reservations, and ensures that the vehicle charging process is not affected by the terminal's status.

[0018] This application also provides a vehicle charging management method. This application determines the charging strategy by combining configuration operations triggered by the charging strategy configuration control in the vehicle's interactive interface or by responding to terminal configuration data sent by the server. The charging strategy includes multi-dimensional configuration operations of at least one of charging time period, charging date, expected power, and charging location. It is a diversified charging strategy construction mechanism that combines local custom configuration and server remote configuration and defines multiple parameters. This fundamentally overcomes the technical defects of controlling charging start based on a single command mode, which makes it difficult to meet the diverse charging needs of users. It realizes the accurate adaptation of the charging strategy to different vehicle use scenarios, time planning, power targets and charging locations, and ensures that the vehicle charging solution can be flexibly executed to meet the personalized and differentiated charging and use needs of users. Attached Figure Description

[0019] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0020] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 This is a flowchart illustrating an embodiment of the vehicle charging management method of this application. Figure 2 This is a schematic diagram of the charging strategy configuration control in Embodiment 8 of the vehicle charging management method of this application; Figure 3 This is a schematic diagram of the first control in Embodiment 8 of the vehicle charging management method of this application; Figure 4 This is a schematic diagram of the vehicle architecture in Embodiment 10 of the vehicle charging management method of this application; Figure 5 This is a schematic diagram of the in-vehicle signaling interaction involved in Embodiment 10 of the vehicle charging management method of this application; Figure 6 This is a schematic diagram of the hardware structure involved in the embodiment of the electronic device of this application.

[0022] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0023] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of this application and are not intended to limit this application.

[0024] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0025] Currently, the vehicle charging reservation function relies on mobile application software, network connection and cloud command issuance. If any link in the communication process fails, such as the phone freezing, the application being killed in the background, poor network signal, or cloud delay, the charging reservation may fail.

[0026] The main solution of this application is: in response to the charging strategy received by the application layer, the structured data packet corresponding to the charging strategy is written into the information processing box of the integrated hardware real-time clock; the wake-up value of the hardware real-time clock is configured based on the structured data packet; and the vehicle is controlled to enter a low-power sleep mode.

[0027] This application constructs a terminal-independent charging reservation execution mechanism by combining a structured data packet corresponding to the charging strategy into an information processing box with an integrated hardware real-time clock, configuring the wake-up value of the hardware real-time clock based on the structured data packet, and controlling the vehicle to enter a low-power sleep mode. This mechanism is based on hardware-level local storage and independent timed wake-up. It fundamentally overcomes the technical defect of charging reservation failure caused by fluctuations in the mobile terminal's operating environment, achieves stable triggering and reliable execution of charging reservation, and ensures that the vehicle charging process is not affected by the terminal's status.

[0028] It should be noted that the executing entity in this embodiment can be a vehicle, or a computing service device with data processing, network communication, and program execution functions, such as a tablet computer, personal computer, or mobile phone, or an electronic device capable of performing the above functions. This embodiment does not specifically limit the specific implementation. The following uses a vehicle as the executing entity to describe this embodiment and the following embodiments.

[0029] Based on this, Embodiment 1 of this application proposes a vehicle charging management method, please refer to... Figure 1 The vehicle charging management method includes steps S10 to S30: Step S10: In response to the charging strategy received by the application layer, the structured data packet corresponding to the charging strategy is written into the information processing box of the integrated hardware real-time clock.

[0030] In this embodiment, the application layer is the application layer of the vehicle's infotainment system. It is the front-end processing unit that receives charging strategies and can respond to local configuration operations on the vehicle's interface or commands issued by the server to obtain the user-defined charging strategy. The charging strategy is a customized planning scheme used to guide the vehicle in performing charging operations. It can be set by the user according to their usage needs and its core components include at least one of the following: charging period, charging date, desired charge level, and charging location. The structured data packet is a standardized data carrier formed by the application layer after standardizing and arranging the control parameters such as charging period, charging date, desired charge level, and charging location in the charging strategy according to a pre-defined unified data format between vehicle hardware. It includes a unique strategy identifier, various control parameter information, data checksum, and format identifier, and can be stably transmitted between different vehicle hardware units and is resolvable. The information processing box with an integrated hardware real-time clock is a dedicated vehicle information processing device with a built-in hardware real-time clock module. It has independent data storage and hardware-level timed wake-up capabilities and can operate independently of the vehicle's main system while maintaining low power consumption. For example, in this embodiment, it could be a (TCAM, Telematics Control Unit Module).

[0031] As an optional implementation, after receiving the charging strategy, the vehicle application layer directly encapsulates the charging strategy into a standardized data frame and sends the data frame to the information processing box with an integrated hardware real-time clock via the vehicle Ethernet link. After receiving the data frame, the information processing box automatically performs data integrity verification. After the verification is successful, the charging strategy is written to the local non-volatile storage module to complete the storage.

[0032] As another optional implementation, the vehicle application layer first sends the charging strategy to the vehicle intelligent domain controller. The domain controller verifies the rationality of the parameters in the charging strategy, checks the logical validity of the time and date, and the value range of the power parameters. After the verification is passed, the charging strategy is converted into a private protocol message that the information processing box can recognize. Then, the message is sent to the information processing box with an integrated hardware real-time clock via the CAN bus. The information processing box parses the message, extracts the charging strategy, and completes local storage.

[0033] Step S20: Configure the wake-up value of the hardware real-time clock based on the structured data packet.

[0034] In this embodiment, the wake-up value of the hardware real-time clock is a time determination parameter set according to the charging strategy parameters to trigger the hardware real-time clock interrupt, and is the core basis for the information processing box to perform timed wake-up operations.

[0035] As an optional implementation, the information processing box with integrated hardware real-time clock extracts time and date parameters from the stored charging strategy, combines them with the current local time data of the hardware real-time clock, calculates the time difference between the current time and the charging start time, and uses it as the wake-up value of the hardware real-time clock. The wake-up value is then written into the configuration register of the hardware real-time clock through hardware configuration instructions to complete the setting.

[0036] As another optional implementation, the specific target wake-up time is first calculated based on the time and date parameters in the charging strategy. This target wake-up time is then sent directly as the wake-up value of the hardware real-time clock to the information processing box that integrates the hardware real-time clock. The information processing box then calibrates and synchronizes the received wake-up value with the local time of the hardware real-time clock to complete the configuration.

[0037] Step S30: Control the vehicle to enter a low-power sleep mode.

[0038] In this embodiment, the low-power sleep mode is an energy-saving operating state of the vehicle. In this state, only the clock circuit in the information processing box with the integrated hardware real-time clock is kept running normally, while the rest of the vehicle's control systems enter a power-off or low-power operating mode.

[0039] As an optional implementation, after the wake-up value is written into the configuration register of the hardware real-time clock by the hardware configuration instruction, the information processing box sends a sleep control instruction to the vehicle controller. After receiving the instruction, the vehicle controller sequentially controls the vehicle's battery management system, on-board charger, intelligent domain controller and other modules to enter a low-power mode, keeping only the clock circuit of the information processing box running.

[0040] As another optional implementation, the information processing box completes the configuration after calibrating and synchronizing the received wake-up value with the local time of the hardware real-time clock. Then, the information processing box triggers its local low-power mode and sends a power control command to the vehicle power management module. After receiving the command, the power management module cuts off the main power supply circuit of other power modules in the vehicle and provides only microampere power to the clock circuit of the information processing box, thereby realizing low-power sleep mode for the entire vehicle.

[0041] For example, based on the dual needs of daily commuting and weekend travel, a user sets two charging strategies on the vehicle's infotainment interface. The first strategy is for weekdays, with the dates set from Monday to Friday, the time set at 11 PM, and the battery level set to 90%. The second strategy is for weekends, with the dates set from Saturday to Sunday, the time set at 10 AM, and the battery level set to 80%. After receiving the two charging strategies set by the user, the vehicle's application layer encapsulates them into standardized data frames and sends them directly to the information processing box with an integrated hardware real-time clock via the vehicle's Ethernet. The information processing box performs integrity verification on the data frames. If the verification is successful, it stores the two charging strategies in its local non-volatile storage module. The information processing box extracts the time and date parameters corresponding to weekdays and weekends from the stored charging strategies, and calculates the time difference between the two strategies using the current local time of the hardware real-time clock. This time difference is used as the wake-up value for the hardware real-time clock, and the two wake-up values ​​are sequentially written into the configuration register of the hardware real-time clock to complete the setup. Subsequently, the information processing box sends a sleep control command to the vehicle controller. Upon receiving the command, the vehicle controller puts all modules, including the battery management system, on-board charger, and intelligent domain controller, into low-power sleep mode, while only the clock circuit within the information processing box remains operational. The vehicle then enters low-power sleep mode. When the hardware real-time clock detects that the current time is Monday night at 11 PM, it triggers the corresponding wake-up interrupt. The information processing box is then woken up, retrieves the weekday charging strategy from its local storage module, converts it into a CAN bus message, and broadcasts it. Upon receiving the message, the vehicle's underlying controller executes the charging operation, charging the battery to 90%. When the hardware real-time clock detects that the current time is Saturday morning at 10 AM, it triggers the wake-up interrupt corresponding to the weekend charging strategy. The information processing box is woken up again, retrieves the weekend charging strategy, and controls the vehicle's underlying controller to execute the charging operation, charging the battery to 80%. This completes automatic charging management for different usage scenarios.

[0042] This embodiment combines a structured data packet corresponding to the charging strategy into an information processing box with an integrated hardware real-time clock, a wake-up value for the hardware real-time clock configured based on the structured data packet, and a coordinated operation to control the vehicle to enter a low-power sleep mode. It constructs a terminal-independent charging reservation execution mechanism with hardware-level local storage and independent timed wake-up as the core. This fundamentally overcomes the technical defect of charging reservation failure caused by fluctuations in the mobile terminal's operating environment, realizes stable triggering and reliable execution of charging reservation, and ensures that the vehicle charging process is not affected by the terminal's status.

[0043] Based on any of the above embodiments, in Embodiment 2 of this application, storing the charging strategy in an information processing box with an integrated hardware real-time clock includes: Through the application layer: generate and send the structured data packets corresponding to the charging strategy to the domain controller.

[0044] In this embodiment, the domain controller is the in-vehicle intelligent domain controller (IPCP), which is the core computing node for in-vehicle hardware communication. It undertakes the functions of data relay, logic processing, instruction integrity verification and communication protocol conversion between in-vehicle devices. It is also a key intermediate control unit that connects the vehicle application layer and the information processing box of the integrated hardware real-time clock.

[0045] As an optional implementation, after receiving the charging strategy, the application layer first performs logical verification on various control parameters in the strategy. After confirming that the parameters are not conflicting or have abnormal values, it generates a structured data packet carrying a CRC data check code according to the transmission data format of the vehicle Ethernet. It then establishes a dedicated connection-oriented communication link with the domain controller through the vehicle Ethernet and sends the structured data packet completely to the domain controller. During the transmission, the data transmission status is fed back in real time. If data packet loss or transmission interruption is detected, a retransmission mechanism is immediately triggered until the data packet is successfully sent.

[0046] As another optional implementation, when the application layer receives the charging policy issued by the server, it first performs dual verification of the server data for signature validity and data integrity. After the verification is successful, the structured data packet corresponding to the charging policy is fragmented according to the transmission bandwidth limit of the vehicle CAN bus. A fragment identifier, sequence code and fragment check code are added to each data fragment. The data fragments are then sent to the domain controller in a non-connection-oriented communication method through the vehicle CAN bus. The domain controller then completes the subsequent data packet reassembly and integrity verification.

[0047] The domain controller encapsulates the structured data packet into a request message and sends the request message to the information processing box of the integrated hardware real-time clock.

[0048] In this embodiment, the request message is a dedicated communication message formed by the domain controller after converting and encapsulating structured data packets according to the proprietary communication protocol specifications of the information processing box with integrated hardware real-time clock. It includes three core parts: message header, message body, and check segment. The message header contains the proprietary device identifier of the information processing box, message type identifier, and data length information. The message body is a structured data packet related to the charging strategy or its core parameters. The check segment is a check code generated based on the message body, used for message integrity verification after the information processing box receives the message.

[0049] As an optional implementation, after receiving the structured data packet sent by the application layer, the domain controller first performs data integrity verification based on the checksum in the data packet. After the verification is successful, it extracts the core control parameters of the charging strategy from the data packet. According to the private communication protocol specification of the information processing box with integrated hardware real-time clock, it encapsulates the core parameters into a request message body with a preset format, adds the dedicated device identifier of the information processing box and the timed task message type identifier to the message header, generates a CRC checksum based on the message header and message body and fills it into the check segment, and finally sends the request message to the information processing box with integrated hardware real-time clock in a precise unicast manner through the vehicle CAN bus.

[0050] As another optional implementation, the domain controller retains the full data of the verified structured data packet and uses the entire structured data packet directly as the message body of the request message. A unified protocol header conforming to the vehicle general communication protocol is added to the message, which includes the general device identifier and data type information of the vehicle hardware network. At the same time, an MD5 checksum is generated and filled into the check segment to form a standard request message. The request message is broadcast to the vehicle local hardware network through the vehicle Ethernet. The information processing box with integrated hardware real-time clock filters and receives the target request message from the broadcast message based on its own unique device identifier, thus completing the accurate acquisition of the message.

[0051] The information processing box parses the request message to obtain the structured data packet and writes the structured data packet into the local flash memory.

[0052] In this embodiment, parsing refers to the information processing box performing layered processing on the received request message, stripping the communication layer information and verification information of the check segment from the message header, extracting the structured data packets in the message body, and performing dual verification operations on the extracted structured data packets in terms of format and parameter logic; the local flash memory is a non-volatile storage medium built into the information processing box, which has the characteristic of not losing data after power failure, and has a dedicated storage partition for charging strategy, supporting fast data reading and writing and long-term storage, and is the physical carrier of hardware-level storage for charging strategy.

[0053] As an optional implementation, after receiving a request message from the domain controller, the information processing box first extracts the checksum of the check segment to verify the integrity of the message header and message body. After the verification is successful, the message header is parsed to confirm that the device identifier of the message matches itself and that it is a timed task type message. Then, the communication layer information is stripped to extract the structured data packet in the message body. The structured data packet is then checked for format identification and policy parameter logic. After both checks are successful, the structured data packet is completely written to the charging policy-specific storage partition of the local flash memory through a hardware write instruction. After the write is completed, a write success signal is sent back to the domain controller and the application layer through the vehicle CAN bus.

[0054] As another optional implementation, if the information processing box receives a request message containing multiple charging strategies, it first verifies the integrity and validity of the request message. After the verification is successful, it parses the message body sequentially according to the strategy group identifier in the message header, extracts the structured data packets corresponding to each group of charging strategies, performs batch format and parameter verification on all structured data packets, and after all verifications are successful, it writes each group of structured data packets into different storage addresses of the local flash memory in the order of the strategy group identifier. At the same time, it establishes a charging strategy index table in the local flash memory to record the identifier, storage address and core parameter information of each group of strategies, which facilitates quick retrieval during subsequent wake-up value configuration and charging strategy execution.

[0055] For example, a user sets two charging strategies on the vehicle's infotainment interface. The first strategy starts charging at 11 PM every day from Monday to Friday and charges the battery to 90% state of charge. The second strategy starts charging at 10 AM every day from Saturday to Sunday and charges the battery to 80% state of charge. After receiving the two charging strategies, the application layer first performs logical verification on the parameters of charging time, charging date, and expected charge. After confirming that there are no conflicts or abnormalities, it generates a structured data packet containing the unique IDs of the two strategies, all control parameters, and CRC data checksum according to the transmission data format of the vehicle Ethernet. Then, it establishes a dedicated connection-oriented communication link with the domain controller through the vehicle Ethernet and sends the structured data packet to the domain controller completely. After receiving the structured data packet, the domain controller first verifies the CRC checksum to confirm that the data packet is undamaged and unaltered. Next, it extracts the core control parameters of the two charging strategies and encapsulates these parameters into a pre-formatted request message body according to the proprietary communication protocol of the integrated hardware real-time clock information processing box. A dedicated device identifier and a timed task message type identifier for the information processing box are added to the message header. A CRC checksum is generated and filled into the checksum section. Finally, the request message is accurately sent to the integrated hardware real-time clock information processing box via unicast through the vehicle's CAN bus. Upon receiving the request message, the information processing box first verifies the CRC checksum in the checksum section to complete the message integrity verification. After parsing the message header to confirm it is the target timed task message, it extracts the structured data packet from the message body and performs dual verification of the data packet's format identifier and parameter logic. If the verification passes, it writes the structured data packet completely to the charging strategy's dedicated storage partition in the local flash memory using a hardware write command. After writing, it sends a write success signal to the domain controller and the application layer, thus completing the entire data interaction process of the charging strategy from the application layer to the information processing box's hardware-level storage.

[0056] This embodiment achieves standardized and highly reliable data transmission and implementation of charging strategies from the front end to the underlying hardware storage through layered collaborative operation of the application layer, domain controller, and information processing box. The application layer transforms charging strategies into standardized structured data packets, effectively avoiding data interaction errors between in-vehicle hardware caused by inconsistent data formats. Simultaneously, parameter verification and retransmission mechanisms improve the original accuracy and transmission reliability of the charging strategy data. The domain controller, acting as an intermediate control unit, performs integrity verification of the structured data packets and encapsulates them into request messages adapted to the communication protocol of the information processing box. This achieves protocol adaptation between in-vehicle hardware with different communication standards, resolving communication compatibility issues between the application layer and the information processing box. It also provides both unicast and broadcast transmission methods, flexibly adapting to different in-vehicle network hardware environments and transmission requirements. The information processing box ensures the validity of the extracted structured data packets through layered parsing and dual verification of the request messages. It writes these packets to local flash memory that is not lost even when power is off, achieving hardware-level non-volatile storage of the charging strategy. This frees the charging strategy from dependence on mobile terminals, external networks, and servers, laying a stable and reliable hardware foundation for the accurate execution of subsequent charging strategies from a storage perspective. Furthermore, the batch storage of multiple strategies and the index table design further enhance adaptability to diverse user charging needs.

[0057] Based on any of the above embodiments, in Embodiment 3 of this application, configuring the wake-up value of the hardware real-time clock based on the structured data packet includes: Step S21: Determine the wake-up value based on the current time recorded by the hardware real-time clock and the charging period contained in the structured data packet.

[0058] In this embodiment, the current time is the vehicle-mounted local real-time time independently recorded by the hardware real-time clock inside the information processing box with integrated hardware real-time clock. It does not rely on external network synchronization and can independently provide an accurate time reference.

[0059] As an optional implementation, the information processing box with integrated hardware real-time clock extracts the charging start time corresponding to the charging period from the stored charging strategy, directly calculates the absolute duration difference between the current time and the charging start time, converts the duration difference into a second-level value that can be recognized by the hardware real-time clock, and uses the second-level value as the wake-up value.

[0060] As another optional implementation, the information processing box integrating the hardware real-time clock extracts the timestamp corresponding to the charging start time of the charging period in the charging strategy and the current timestamp recorded by the hardware real-time clock, calculates the difference between the two timestamps to obtain the timestamp difference, and then adapts and converts the timestamp difference into the timing unit value required for the hardware real-time clock configuration, and determines the timing unit value as the wake-up value.

[0061] Step S22: Configure the hardware real-time clock based on the wake-up value.

[0062] In this embodiment, configuration refers to writing the wake-up value into the dedicated configuration register of the hardware real-time clock and enabling the timer interrupt function of the hardware real-time clock, so that the hardware real-time clock can perform a series of operations for timed wake-up based on the wake-up value.

[0063] As an optional implementation, the information processing box with integrated hardware real-time clock directly writes the determined wake-up value into the timer interrupt configuration register of the hardware real-time clock, and directly enables the timer interrupt function of the hardware real-time clock through hardware control instructions to complete the configuration of the hardware real-time clock. At the same time, it generates a configuration success electrical signal and feeds it back to the main processing module of the information processing box.

[0064] As another optional implementation, the information processing box integrating the hardware real-time clock first converts the wake-up value into a data format that matches the bit width and data type requirements of the hardware real-time clock configuration register. Then, the converted wake-up value is written into the corresponding configuration register in batches. After the writing is completed, the data in the register is read back for verification. If the verification is correct, the timer interrupt function of the hardware real-time clock is enabled through software instructions to complete the configuration of the hardware real-time clock.

[0065] This embodiment determines the wake-up value by combining the target time of the charging strategy with the local current time of the hardware real-time clock. Relying on the local time base of the hardware real-time clock, it eliminates the dependence on external network time synchronization, ensuring the accuracy and independence of the wake-up value calculation. The hardware real-time clock is configured by direct writing or format conversion followed by verification writing, which provides a flexible configuration method and ensures the accuracy of the configuration process through data verification, avoiding charging strategy triggering errors caused by incorrect wake-up value configuration.

[0066] Based on any of the above embodiments, in Embodiment 4 of this application, controlling the vehicle to enter a low-power sleep mode includes: Step S23: Control the circuit corresponding to the hardware real-time clock to keep powered on, and control the other circuits in the information processing box except the hardware real-time clock to keep powered off, so that the vehicle enters the low-power sleep mode.

[0067] In this embodiment, the circuit corresponding to the hardware real-time clock is an independent power supply link designed specifically for the hardware real-time clock module inside the information processing box that integrates the hardware real-time clock. This circuit adopts a low-power power supply design, providing basic power support only for the timing, wake-up value storage, and interrupt triggering of the hardware real-time clock. It is independent of the power supply links of other circuits in the information processing box and can achieve independent power protection control. Other circuits in the information processing box besides the hardware real-time clock include the main processor circuit of the information processing box, the vehicle bus communication transceiver circuit, the flash memory read / write control circuit, the power management extension circuit, and all other functional circuits. These circuits provide support for the normal operation of the information processing box and do not need to maintain power supply when the vehicle enters the sleep stage of charging reservation waiting. The low-power sleep mode is a deep sleep state of the vehicle designed for the charging reservation scenario in this application. It is achieved through fine-grained power supply control of the information processing box. Unlike the shallow sleep mode of traditional vehicles, in this mode, only the hardware core power supply required for the charging reservation timer is retained, and all other non-essential circuits are powered off, achieving the ultimate reduction of the vehicle's static power consumption.

[0068] As an optional implementation, the power management module of the information processing box initiates the power supply control operation. After detecting the identification signal that the hardware real-time clock wake-up value configuration is complete, the power management module of the information processing box first locks the power supply switch of the circuit corresponding to the hardware real-time clock, keeping the circuit continuously powered and the power supply voltage stable within the operating threshold range of the hardware real-time clock. Then, it sequentially cuts off the power supply links of all other circuits such as the main processor circuit, CAN / LIN bus communication transceiver circuit, and flash memory read / write control circuit, so that the information processing box retains only the low-power operating state of the hardware real-time clock module. After the information processing box completes the local power supply control, it sends a sleep ready signal to the vehicle controller through hardware level signals. After receiving the signal, the vehicle controller cuts off the power supply to non-core vehicle electrical components such as the vehicle application layer, domain controller, on-board charger, and body control module, retaining only the basic monitoring power supply of the battery management system, and finally puts the vehicle into a low-power sleep mode.

[0069] As another optional implementation, the vehicle controller initiates the full-domain power supply control operation as the main control unit. After the information processing box completes the hardware real-time clock wake-up value configuration, it sends a sleep trigger request to the vehicle controller, along with precise power supply control instructions. Upon receiving the request, the vehicle controller sends a directional power supply control instruction to the power management module of the information processing box via the vehicle power management bus. The instruction explicitly states that only the power supply to the circuit corresponding to the hardware real-time clock is maintained. The power management module of the information processing box executes the on / off control of the power supply link according to the instruction, maintaining the power supply to the circuit corresponding to the hardware real-time clock and cutting off the power supply to other circuits. While sending instructions to the information processing box, the vehicle controller cuts off the power supply to non-essential electrical components such as the vehicle infotainment screen, domain controller, and vehicle network switch in sequence according to the power supply priority of the vehicle hardware, realizing low-power control at the vehicle level and putting the vehicle into a low-power sleep mode. After sleep mode, the vehicle controller only retains the ability to monitor the hardware interrupt signal of the information processing box.

[0070] For example, after the information processing box completes the local flash memory writing of the structured data packet corresponding to the charging strategy, and configures and locks the hardware real-time clock wake-up value based on the data packet, the power management module of the information processing box initiates power supply control: First, it locks the independent power supply link of the circuit corresponding to the hardware real-time clock to ensure that the circuit is continuously powered by the standard 3.3V operating voltage to meet the timing and interrupt triggering requirements of the hardware real-time clock. Then, it immediately cuts off the power supply to the main processor circuit, CAN bus communication transceiver circuit, flash memory read / write control circuit, and all other circuits. The information processing box enters a low-power state where only the hardware real-time clock operates. After completing the local power supply control, the information processing box sends a sleep ready signal to the vehicle controller through a hardware level signal. After receiving the signal, the vehicle controller cuts off the power supply to the vehicle application layer, domain controller, on-board charger, body control module, and other non-core vehicle components in sequence according to the preset sleep power supply strategy, only retaining the power supply for the battery management system to monitor the battery's basic voltage and temperature. At this point, the vehicle has completely entered a low-power sleep mode. In this state, only the circuit corresponding to the hardware real-time clock of the information processing box operates at a microampere level of power consumption, the static power consumption of the whole vehicle is reduced to a minimum, and the hardware real-time clock module continues to keep accurate time according to the configured wake-up value, waiting to trigger a hardware interrupt when the preset time is reached.

[0071] This embodiment achieves deep low-power sleep mode during the vehicle charging reservation waiting phase through refined hardware-level power supply control of the information processing box. It employs a control method where the hardware real-time clock circuit is independently powered while other circuits are completely powered off. This allows the information processing box to retain only the core functions required for timed wake-up. The micro-ampere-level power consumption of its hardware real-time clock circuit significantly reduces the vehicle's idle power consumption, effectively minimizing unnecessary battery drain. The power supply control link of the information processing box is independent of other vehicle hardware, avoiding interference from other circuits that could affect the timing accuracy of the hardware real-time clock, and ensuring the security of the stored wake-up value of the hardware real-time clock in sleep mode. This provides hardware assurance for the accurate triggering of subsequent charging reservations. Two implementation methods are provided: local master control of the information processing box and global master control of the vehicle controller. This allows for flexible adaptation to the vehicle power management architecture of different models, improving the scenario compatibility and engineering practicality of this method. Unlike the shallow sleep mode in traditional charging reservation schemes where vehicles maintain some network and software module operation, the low-power sleep mode of this application cuts off all unnecessary power supply at the hardware level, completely eliminating the extra power consumption caused by software module background operation and network monitoring. At the same time, it avoids the program freezing and wake-up failure problems that may occur in software sleep, and further improves the reliability of charging reservation execution while achieving low power consumption.

[0072] Based on any of the above embodiments, in Embodiment 5 of this application, after setting the wake-up value of the hardware real-time clock based on the charging strategy and controlling the vehicle to enter low-power sleep mode, the process includes: Step S41: In response to the hardware interrupt signal generated when the hardware real-time clock reaches the wake-up value, the information processing box that is in a power-down state is woken up.

[0073] In this embodiment, the hardware interrupt signal is a hardware-level electrical signal interrupt actively triggered when the hardware real-time clock module integrated in the information processing box reaches a preset wake-up value. Unlike software-level interrupt instructions, this signal features zero-delay trigger response and strong anti-interference capabilities, making it the core trigger source for waking up the information processing box. Wake-up refers to the operation of restoring the information processing box from a low-power sleep state to a fully functional operating state, after which the information processing box can perform subsequent business operations such as instruction retrieval and message generation.

[0074] As an optional implementation, the hardware real-time clock detects that the current time has reached the charging start time corresponding to the wake-up value and directly generates a hardware interrupt signal. This interrupt signal triggers the main power supply circuit of the information processing box to automatically turn on, and the main processing module, storage module, communication module and other functional modules of the information processing box start up in sequence to complete the overall wake-up of the information processing box.

[0075] As another optional implementation, if the hardware real-time clock module is configured with multiple wake-up values, when any wake-up value is reached, the module will generate a hardware interrupt signal with a policy identifier. This signal contains the unique identifier information of the corresponding charging policy. After receiving the signal, the interrupt detection circuit of the information processing box first parses out the policy identifier and stores it temporarily, and then triggers the power management module to restore power to the information processing box. After waking up, the information processing box can directly retrieve the corresponding charging policy data according to the policy identifier, thereby improving the execution efficiency of subsequent operations.

[0076] Step S42: Read the structured data packet from the local flash memory and generate a charging strategy message based on the structured data packet.

[0077] In this embodiment, the charging strategy message is a standardized control message generated by the information processing box according to the core parameters of the charging strategy in the structured data packet and in accordance with the communication protocol specification of the vehicle CAN / LIN bus. This message is communication data that can be directly recognized and parsed by the vehicle's underlying controller. It contains core execution parameters such as charging start command, target power, and charging period, and is accompanied by a data check code to ensure that the data is not tampered with during transmission.

[0078] As an optional implementation, after the information processing box is woken up, it accurately retrieves the charging strategy that matches the wake-up value from the local non-volatile storage module, extracts the core execution parameters such as the target power and charging mode from the strategy, encodes the parameters according to the standard frame format of the vehicle CAN bus, and generates a charging strategy message containing a unique frame ID, data segment and CRC check segment.

[0079] As another optional implementation, after the information processing box retrieves the matching charging strategy, it first performs a secondary verification of the validity of the strategy parameters. After confirming that there are no logical abnormalities in the time and power parameters, it generates a charging strategy message according to the communication specifications of the vehicle LIN bus and adds a dedicated wake-up flag bit to the message.

[0080] Step S43: Broadcast the charging strategy message to wake up the vehicle's controller.

[0081] In this embodiment, the broadcast method involves the information processing box sending charging strategy messages to the vehicle hardware network via the vehicle CAN / LIN bus. All vehicle controllers within the vehicle network can receive the message. Unlike the unicast method, the broadcast method ensures that all relevant controllers can receive the wake-up and execution commands synchronously. The vehicle controllers are the underlying charging control execution units of the vehicle, including the battery management system (BMS), vehicle controller (VCU), and on-board charger (OBC). These controllers are in a sleep or power-off state after the vehicle enters a low-power sleep mode. They have the function of automatically waking up after receiving the message via the vehicle bus and are the core hardware units for executing the charging process.

[0082] As an optional implementation, after the information processing box generates the charging strategy message, it broadcasts the charging strategy message to the entire vehicle CAN bus network with the highest priority through the communication transceiver circuit of the vehicle CAN bus. During the broadcast, the message is sent three times in accordance with the requirements of the vehicle communication protocol to ensure that the vehicle controller can effectively receive it. The bus receiving modules of the battery management system, vehicle controller, on-board charger and other vehicle controllers in the sleep state all maintain a low-power listening state. After receiving the charging strategy message, they first verify the CRC check code of the message. After the verification is successful, they immediately trigger their own wake-up program and switch from the sleep state to the working state.

[0083] As another optional implementation, when the information processing box generates multiple sets of charging strategy messages, it groups all messages into packets according to the strategy identifier and broadcasts them to the vehicle LIN bus in the form of broadcast data packets. After receiving the broadcast data packets, each controller in the vehicle first parses out the strategy identifier in the data packet, and then filters out the charging strategy messages related to itself according to its own functional permissions. After verification, it triggers wake-up, and irrelevant messages are directly discarded. This achieves accurate wake-up of the controller and reduces invalid data processing operations of the controller.

[0084] Step S44: Based on the awakened controller, control the vehicle to execute the charging process corresponding to the charging strategy message.

[0085] In this embodiment, the charging process is the complete charging operation process from starting charging to reaching the preset target power level, according to the parameter requirements in the charging strategy message. It includes key steps such as charging start, power adjustment, real-time power monitoring, and charging stop.

[0086] As an optional implementation, after receiving the charging strategy message, the vehicle controller first parses the message and extracts execution parameters such as the target charge level and charging power. The vehicle controller first completes the detection of the charging gun connection status, vehicle parking status, and power supply circuit status. After all the detections pass, it sends a charging start command to the battery management system and the on-board charger. The on-board charger starts charging according to the preset fixed power. The battery management system monitors the battery's state of charge in real time. When it detects that the battery's state of charge has reached the target charge level, it immediately sends a charging stop command to the vehicle controller and the on-board charger. The on-board charger stops working, completing the entire charging process.

[0087] As another optional implementation, after the vehicle controller parses the charging strategy message and extracts the core parameters, the battery management system first formulates a personalized dynamic charging curve based on the current real-time temperature, remaining charge, and cell balance status of the battery. The vehicle controller sends a dynamic power adjustment command to the on-board charger according to the charging curve. The on-board charger performs step-by-step charging according to the dynamic power. During the charging process, each controller works together to monitor the battery status in real time. If the battery temperature is too high or the charging circuit is abnormal, the charging is immediately suspended. After the fault is cleared, the charging operation continues until the battery's state of charge reaches the target charge level, thus completing the charging process.

[0088] For example, a user sets a weekday charging strategy on the vehicle's infotainment system, specifically charging the battery to 90% by 11 PM from Monday to Friday. The information processing box completes the storage of this strategy, sets the wake-up value, and enters a low-power sleep state at 6 PM on the same day. When the hardware real-time clock reaches the wake-up value of 23:00, a hardware interrupt signal is directly generated, triggering the main power supply circuit of the information processing box to conduct, and each functional module starts up sequentially to complete the wake-up. After the information processing box is woken up, it retrieves the charging strategy for the workday from the local non-volatile storage module, extracts the core parameter of 90% of the target power, encodes it into a charging strategy message according to the standard frame format of the vehicle CAN bus, and broadcasts the message through the CAN bus. The wake-up signal segment of the message directly triggers the vehicle's battery management system, vehicle controller, and on-board charger to wake up from the dormant state. After receiving the message, the vehicle controller completes the parsing, immediately checks the charging gun connection status and vehicle parking status, and after confirming that the status is normal, sends a charging start command to the battery management system and the on-board charger. The on-board charger starts charging at a constant power, and the battery management system monitors the battery state of charge in real time. When it detects that the battery power has reached 90%, it immediately sends a charging stop command, the on-board charger stops charging, and the vehicle controller records the charging completion status, thus completing the entire charging process.

[0089] This embodiment wakes up the information processing box by triggering a hardware interrupt based on the wake-up value of the hardware real-time clock, eliminating the instability of software wake-up. The hardware triggering characteristic ensures the accuracy and timeliness of the wake-up operation, with errors controlled within milliseconds. By converting the charging strategy into standardized charging strategy messages and broadcasting them on the bus, efficient and stable communication between the information processing box and the vehicle's underlying controller is achieved. Simultaneously, the controller wake-up is directly completed using these messages, simplifying the control chain, reducing intermediate steps in command transmission, and improving command transmission efficiency. Through the collaborative work of multiple controllers at the vehicle's underlying level to execute the charging process, combined with real-time monitoring of battery status, precise closed-loop control of the charging operation is achieved, ensuring that the vehicle strictly follows the charging strategy to complete charging and accurately reaches the target charge level, avoiding overcharging or undercharging. The entire series of steps completes the entire process from hardware-level wake-up to standardized command transmission and precise charging execution, relying entirely on the vehicle's local hardware, eliminating dependence on external networks and cloud services. This fundamentally solves the technical problems of inaccurate triggering, imprecise execution, and low reliability caused by reliance on external devices in traditional charging solutions, further improving the reliability, stability, and intelligence level of vehicle charging management, while accurately matching users' personalized charging needs.

[0090] Based on any of the above embodiments, in Embodiment Six of this application, after the awakened controller controls the vehicle to execute the charging process corresponding to the charging strategy message, the process includes: Step S45: Obtain charging data of the charging process.

[0091] In this embodiment, charging data is a general term for various core operating and status parameters generated during the vehicle charging process, including parameters such as charging voltage, charging current, real-time battery level, cumulative charging time, battery temperature, charging fault codes, and progress towards achieving the target battery level.

[0092] As an optional implementation, during the charging process, the vehicle controller collects all operating parameters in real time through its own sensing and detection module and data acquisition port. The collected parameters cover charging voltage, charging current, real-time battery state of charge, cumulative charging time, battery cell temperature and overall temperature. After formatting all the collected parameters, they are integrated into complete charging data.

[0093] As another optional implementation, the controller first pre-configures the key items and collection cycle of charging data. The key items only select core data such as real-time battery level, charging fault codes, and progress of achieving the target level. The collection cycle is set to a fixed time interval. The controller periodically collects the key item data according to the preset cycle. At the same time, when abnormal fluctuations in parameters are detected, real-time supplementary collection is triggered to integrate the regular collection data and the supplementary collection data into charging data.

[0094] Step S46: The charging data is fed back to the information processing box and the domain controller to update the charging status of the vehicle based on the charging data.

[0095] In this embodiment, the charging status refers to the specific operating stage and state type of the vehicle during the charging process, including states such as charging in progress, charging completed, charging failure, power level reached, and charging paused. It is the core identifier reflecting the execution status of the vehicle charging process.

[0096] As an optional implementation, the controller will uniformly summarize and compress the acquired charging data to generate standardized charging data feedback messages. These messages will be sent to the information processing box and the domain controller via unicast through the vehicle CAN bus. Upon receiving the messages, the information processing box and the domain controller will parse and verify the data and update the vehicle's charging status based on the parsed charging data.

[0097] As another optional implementation, the controller classifies charging data by type into regular operating data and abnormal alarm data. Regular operating data is pushed in batches at preset time intervals, while abnormal alarm data is pushed in real time. Different types of charging data are sent to the information processing box and the domain controller via the vehicle Ethernet. After receiving the data, the two types of devices update the vehicle charging status immediately. If abnormal data is detected, a status abnormality flag is triggered synchronously.

[0098] For example, a user-defined weekday charging strategy is to charge the battery to 90% by 11 PM from Monday to Friday. The information processing box is woken up at 11 PM, generates and broadcasts a charging strategy message, and the vehicle controller is woken up to execute the charging process. The vehicle controller, battery management system, and onboard charger work together to initiate constant power charging. During the charging process, the battery management system uses its cell detection module and data acquisition port to collect all parameters in real time, including charging voltage, charging current, real-time battery level, and battery temperature. After formatting, these parameters are integrated into charging data. The battery management system then summarizes and compresses the integrated charging data to generate standardized charging data feedback messages, which are unicast to the information processing box and domain controller with integrated hardware real-time clocks via the vehicle's CAN bus. Upon receiving the feedback messages, the information processing box and domain controller parse the data. When the real-time battery level is detected to be 80%, the vehicle charging status is updated to "Charging -80%". When the real-time battery level is detected to be 90%, the vehicle charging status is updated to "Charging Complete", and relevant data such as cumulative charging time and average charging power are recorded simultaneously.

[0099] This embodiment uses a controller to collect charging data in a targeted manner, supporting both full real-time collection to ensure data integrity and periodic collection of key items to balance data collection efficiency. It can flexibly adapt to different vehicle charging monitoring needs, while ensuring the entire charging process is under data monitoring, effectively avoiding the problem of charging anomalies going undetected. By standardizing the charging data and feeding it back to the information processing box and domain controller, and synchronizing the charging status, unified synchronization of charging status is achieved among the vehicle's core control devices, constructing a complete charging management closed loop of "charging execution, data collection, status feedback, and status update." This allows the execution of the vehicle charging process to be accurately perceived and recorded. Furthermore, the real-time update of the charging status provides core data support for the visualization of the status on subsequent user interaction terminals such as the vehicle's large screen and mobile app, allowing users to keep track of the vehicle's charging status at any time. This further enhances the intelligence and interactivity of vehicle charging management, while also providing detailed data for optimizing charging strategies and subsequent troubleshooting, making the execution of the entire vehicle charging management solution more traceable and ensuring the reliability and accuracy of charging management from a data perspective.

[0100] Based on any of the above embodiments, in Embodiment Seven of this application, the vehicle charging management method includes: Step A10: In response to a configuration operation triggered by a charging strategy configuration control in the vehicle's interactive interface, or in response to terminal configuration data sent by the server, a charging strategy is determined, wherein the charging strategy includes at least one of charging period, charging date, desired charge level, and charging location.

[0101] In this embodiment, the vehicle's interactive interface is a visual touch-screen interface of the vehicle's infotainment system. It serves as the core interactive platform for users to configure charging strategies locally, integrated into in-vehicle display devices such as the large in-vehicle screen. It supports visual operations such as parameter input, option selection, and time selection. The charging strategy configuration controls are standardized functional operation controls on the interactive interface, including dedicated controls such as a time selection box, a power input box, a date selection bar, and a location selection button. These are the physical entry points for users to trigger charging strategy configuration operations, with each control corresponding to a specific parameter type in the charging strategy. Configuration operations are various valid interactive operations initiated by the user on the charging strategy configuration controls, including manual parameter input, time / date option selection, charging location selection, and configuration information saving and confirmation. Upon triggering, corresponding parameter configuration information is generated. The server provides remote configuration services for vehicle charging management; it can be a backend server, a cloud relay for communication between the vehicle and the user terminal, or the user terminal itself. The user terminal is not limited to devices such as mobile phones, computers, tablets, or all-in-one machines. The terminal configuration data is standardized data generated by the server according to the in-vehicle hardware data transmission specifications. It includes charging strategy-related parameters, data integrity verification codes, and server-side legal identifiers, and can be transmitted to the vehicle via a wireless communication network. The charging period is the time range for starting or ending charging; the charging date is the specific date or cycle for charging execution; the desired charge level is the target battery state of charge; and the charging location is the geographical area or charging station location for charging execution. Each parameter can be configured individually or in combination to adapt to different charging scenario requirements.

[0102] As an optional implementation, the charging strategy is determined based on the configuration operation of the vehicle's interactive interface. Users can sequentially complete the personalized settings of various parameters through the charging strategy configuration controls within the vehicle's interactive interface. This includes selecting charging dates for single or multi-day cycles, setting specific charging start / end times, inputting the desired charge level within the battery's state of charge range, and selecting charging locations such as home charging stations or public charging stations. After completing all parameter settings, a save confirmation operation is triggered on the interface, and the interactive interface sends all collected configuration parameter information to the vehicle's application layer. Upon receiving the parameter information, the application layer performs logical validity checks on each parameter, including checks on the timing of charging periods, the range of desired charge levels, and the validity of the charging location. If the checks pass, the application layer integrates and encapsulates all parameters into a standardized charging strategy, thus determining the charging strategy. If the checks fail, the application layer will provide specific parameter error prompts to the user through the interactive interface, guiding the user to correct the abnormal parameters until the checks pass.

[0103] As another optional implementation, the charging strategy is determined based on the terminal configuration data sent by the server. The user completes the remote parameter configuration of the charging strategy through the remote operation terminal associated with the server. After receiving the user's remote configuration command, the server first verifies the user's operation permission and the legality of the configuration command. After successful verification, the server encapsulates the configured parameters according to the preset format of vehicle data transmission to generate terminal configuration data containing parameter information, verification code and server identifier. The server sends the terminal configuration data to the vehicle's application layer through wireless communication networks such as 4G / 5G. After receiving the data, the application layer performs server identifier verification, data signature verification and integrity verification in sequence to confirm that the data is legally sent by the server and has no packet loss or tampering. After successful verification, the application layer parses the terminal configuration data, extracts parameters such as charging period, charging date, expected power, and charging location, integrates all parameters to generate the charging strategy, and completes the determination of the charging strategy. If any verification step fails, the application layer will send a data reception error feedback message to the server. After receiving the feedback, the server will trigger the terminal configuration data retransmission mechanism until the vehicle application layer successfully receives and verifies the data.

[0104] For example, users need to configure a weekday home charging strategy. In the vehicle's infotainment screen, users select the charging dates from Monday to Friday in the date selection bar of the charging strategy configuration control, set 23:00 as the charging start time in the time selection box, input the desired charge level of 90% in the power input box, and select the charging location of the "home charging station" using the location selection button. After completion, users click the "Save" button on the interface to trigger the configuration operation. The interface sends the above configuration parameters to the vehicle's application layer. The application layer performs logical verification on the parameters. After confirming that the charging time, power level, and location information are all normal, it integrates and generates a charging strategy of "starting at 23:00 from Monday to Friday, charging to 90%, and charging at the home charging station," thus completing the determination of the strategy. In another exemplary scenario, a user remotely configures a weekend public charging station charging strategy on the server via a mobile client. The user sets the charging period to 10:00-12:00 on Saturday and Sunday, the desired battery level to 80%, and the charging location to the XX Commercial Center public charging station. After verifying the user's permissions, the server generates the corresponding terminal configuration data and sends it to the vehicle application layer via the 5G network. After verifying that the data is legally sent by the server and is complete and error-free, the application layer parses and extracts all configuration parameters, integrates them to generate the charging strategy for the weekend public charging station, and completes the strategy determination.

[0105] This embodiment achieves flexibility and diversity in charging strategy configuration by supporting both local vehicle configuration and remote server-side distribution, adapting to different user needs for local operation and remote management. It expands the core parameters of the charging strategy to multiple dimensions, including charging time period, charging date, desired power level, and charging location, breaking through the limitations of traditional single-time parameter configuration. It allows for personalized configuration combinations based on the user's daily routine, usage scenarios, power requirements, and charging locations, accurately matching diverse user charging needs. Simultaneously, a dual verification mechanism at the application layer, verifying both local configuration parameters and server-side data, ensures the rationality, legality, and completeness of the charging strategy parameters. This prevents errors in subsequent charging process execution due to parameter anomalies, laying a reliable parameter foundation for subsequent hardware-level storage and accurate execution of the charging strategy, further improving the scenario adaptability and execution accuracy of the vehicle charging management method.

[0106] Based on any of the above embodiments, in Embodiment 8 of this application, the charging strategy configuration control includes at least one of a first control, a second control, a third control, a fourth control, and a fifth control. The first control is used to configure the charging period, the second control is used to configure the desired power level, the third control is used to configure the charging date, the fourth control is used to configure the charging location, and the fifth control is used to configure both the charging period and the charging date.

[0107] In this embodiment, the charging strategy configuration control is a set of dedicated visual operation controls integrated on the vehicle's interactive interface. Each control is an independent functional operation unit, and they can also be combined and enabled according to configuration requirements. The display state of the controls can be flexibly switched to enabled, grayed out, or hidden according to the user's configuration operation to adapt to different strategy configuration scenarios. The first control is a dedicated configuration control for charging periods, which is a time-related operation control on the vehicle's interactive interface, including a time selection box, a time period slider, a time input bar, etc. It supports setting the charging start time and end time individually or in intervals, and can accurately configure the charging time range. The second control is a dedicated configuration control for the desired power level, which is a power level-related visual operation control, including a percentage slider, a numerical input box, a fixed power level option button, etc. It configures the value range to match a reasonable range of battery charge status, and supports users to accurately set the target power level for charging. The third control is a dedicated configuration control for the charging date, which is a date-related operation control, including a date checkbox, a cycle selection button, etc. The system includes several control options, such as buttons and single / multi-day toggles, supporting flexible selection of single-day, consecutive multi-day, and weekly fixed-cycle dates for precise configuration of charging execution dates. The fourth control is a dedicated configuration control for charging locations, including charging station location selection buttons, address input boxes, and quick selection bars for frequently used charging locations. It supports selection of different charging locations, such as home charging stations and public charging stations, and allows configuration of the geographical area for charging execution. The fifth control is a combined configuration control for charging time periods and dates, an integrated operation control that combines time and date configuration functions. It includes a time period selection panel with date selection and a periodic time period configuration window, allowing for linked configuration of charging time periods and dates within the same control interface, simplifying the operation process for combined parameters. "At least one" indicates that any control can be enabled individually or in combination according to the user's charging strategy configuration needs. The configuration parameters of each control are independent and can be linked in real time, jointly providing support for the parameter configuration of the charging strategy.

[0108] As an optional implementation, for basic charging strategy scenarios that only require configuring a single parameter, a single control with the corresponding function is enabled to complete the configuration, while the other controls are grayed out or hidden. The vehicle interface only displays the currently enabled controls and configuration items. After the user completes the setting of the corresponding parameter through the single control, a basic charging strategy containing only that parameter can be generated. For example, when only the charging period needs to be configured, only the first control is enabled, and the second to fifth controls are hidden. After the user completes the setting of the charging period through the first control, a basic charging strategy based on the charging period is directly generated. The operation is simple and efficient, and it meets the user's basic timed charging needs.

[0109] As another optional implementation, for complex charging strategy scenarios requiring configuration of multiple parameters, multiple single-function controls can be combined or a fifth combined control can be used in conjunction with other single-function controls to complete the configuration. Each enabled control is displayed in sections on the interactive interface, and the configured parameters are synchronized to the strategy preview area of ​​the interactive interface in real time. Users can view the complete strategy configuration information in real time. At the same time, the configuration parameters of each control support mutual verification to avoid parameter conflicts. For example, when configuring a periodic time period + power + location charging strategy, the fifth control can be directly enabled to complete the integrated configuration of charging time period and charging date. Then, the second and fourth controls can be enabled to sequentially complete the configuration of the desired power and charging location. The configuration parameters of each control are linked in real time and displayed in the preview area. Users can modify any parameter at any time to adapt to the diverse and complex charging needs of users.

[0110] For example, users have two types of charging strategy configuration needs. The first type is a basic need: configuring a charging strategy for fixed daily time periods. In this case, the vehicle interface only uses the first control, displayed as a time selection box, while the second to fifth controls are grayed out and unselectable. Users set the charging period from 22:00 to 06:00 the next day through the time selection box of the first control. After configuration, the interface immediately generates the basic charging strategy of "charging from 22:00 to 06:00 the next day," meeting the user's basic timed charging needs. The second type is a complex need: configuring a charging strategy from 10:00 to 12:00 AM on Saturdays and Sundays at the XX Commercial Center public charging station to charge to 80%. In this case, two configuration methods can be selected. Method 1: Combine and enable the third, first, second, and fourth controls. Users first select Saturday through the date selection bar of the third control. On Sunday, the user sets the charging period from 10:00 to 12:00 using the first control, then adjusts the desired charge level to 80% using the percentage slider in the second control, and finally selects the XX Commercial Center public charging station using the location selection button in the fourth control. During the configuration of each control, the strategy preview area of ​​the interactive interface displays the complete configuration information in real time: "Saturday to Sunday 10:00-12:00, XX Commercial Center public charging station, charge to 80%". Method 2: Using the fifth control in conjunction with the second and fourth controls, the user selects Saturday and Sunday and sets the charging period from 10:00 to 12:00 through the integrated time period and date configuration panel of the fifth control, and then completes the configuration of the desired charge level and charging location through the second and fourth controls. Both configuration methods can accurately complete the parameter settings of complex strategies, and users can choose flexibly according to their own operating habits.

[0111] For example, refer to Figure 2 , Figure 2This diagram illustrates one form of a charging strategy configuration control, including a fifth control and a second control. The fifth control is used to configure the charging period and charging date, and can display multiple time configurations, including charging periods or combinations of charging periods and dates. The second control is used to configure the desired charge level, such as the desired State of Charge (SOC) value.

[0112] Specifically, refer to Figure 3 , Figure 3 This is an example of a first control used to configure the charging period, that is, to configure the charging start time and the charging end time.

[0113] This embodiment divides the charging strategy configuration control into single-function controls and combined-function controls, and supports the flexible selection and activation of at least one control. This breaks through the operational limitations of traditional single-control charging configuration and realizes refined and hierarchical configuration of charging strategy parameters. The first to fourth single-function controls can meet the user's basic single parameter configuration needs. The interface is simple, the operation threshold is low, and it is suitable for simple charging scenarios. The fifth combined-function control realizes the integrated configuration of charging time period and charging date, which simplifies the configuration steps of periodic charging strategy and improves the user's operation efficiency. Meanwhile, the multi-control combination mode can meet users' multi-dimensional configuration needs for charging time period, date, power, and location. The parameters of each control are linked in real time and can be previewed, avoiding parameter configuration conflicts. This allows users to flexibly combine controls to complete the configuration of personalized charging strategies according to their daily routines, vehicle usage scenarios, charging locations, and other actual needs, further enhancing the adaptability of charging strategies to users' diverse and differentiated charging needs. In addition, the functions of the controls correspond one-to-one with the charging strategy parameters, with clear division and strong visual operation, reducing the difficulty of configuration operations for users and improving the overall interactive experience of charging strategy configuration. This lays a convenient and accurate operational foundation for the subsequent determination and execution of charging strategies.

[0114] Based on any of the above embodiments, in Embodiment 9 of this application, after determining the charging strategy, the process includes: Step A20: If the current time and / or current location of the vehicle meet any set of the start conditions corresponding to the charging strategy, execute the charging process corresponding to the charging strategy.

[0115] In this embodiment, the vehicle's current time is the real-time time independently recorded by the hardware real-time clock module within the information processing box integrated with the hardware real-time clock. This time is generated by hardware timing, does not rely on external network time synchronization, and has millisecond-level timing accuracy, serving as the sole benchmark for determining time-related triggering conditions. The vehicle's current location is the real-time geographic coordinate information or charging point identification information obtained by the vehicle through the onboard GPS / BeiDou positioning module and the charging pile Bluetooth / RFID module. This information can accurately match the preset location parameters in the charging strategy, with positioning errors controlled within a preset reasonable range. Any set of charging strategies refers to any strategy among multiple sets of charging strategies stored in the vehicle's local flash memory. Each set of strategies is independently configured with triggering conditions and charging execution parameters, without mutual interference, supporting parallel detection and independent triggering of multiple strategies. The triggering condition is a preset trigger threshold in each charging strategy, consisting of a time condition composed of the charging period and charging date, and / or a location condition composed of the charging location. It supports single-condition triggering, i.e., only time / only location, and also supports combined-condition triggering, i.e., time + location. The conditions for meeting the conditions refer to the real-time parameters of the vehicle's current time and / or location being completely matched with the preset start-up condition parameters of a certain charging strategy, or falling within the preset parameter threshold range. The charging process is the complete operation process of the vehicle's underlying controller completing charging start-up, power regulation, and charging stop according to the parameter requirements of the corresponding charging strategy. It is led by the vehicle controller, with the battery management system and on-board charger working together to strictly match the core parameters such as the expected power and charging period in the strategy.

[0116] As an optional implementation, the charging process is triggered based on a single condition. If the charging strategy only presets time-based start conditions, the information processing box monitors the current time of the hardware real-time clock. When the current time reaches the preset charging start time or falls within the preset charging time period, the start condition is determined to be met, and the charging process of that strategy is immediately triggered. If the charging strategy only presets location-based start conditions, the vehicle positioning module collects the current location information in real time and sends it to the information processing box. The information processing box accurately matches the current location with the preset charging location in the strategy. When the vehicle is detected to have arrived at a preset charging point, such as a home charging pile or a designated public charging station, the start condition is determined to be met, and the charging process of that strategy is immediately triggered. In the single-condition trigger mode, the time / location conditions of multiple strategies are detected in parallel. Once the start condition of any strategy is met, the corresponding charging process is executed independently without interference.

[0117] As another optional implementation, the charging process is triggered based on combined conditions. If the charging strategy simultaneously presets both time-based and location-based activation conditions, the information processing box will jointly detect the vehicle's current time and current location. Only when the current time meets the preset time condition and the current location matches the preset location condition will the activation condition be determined to be met, and the charging process of that set of strategies will be triggered. If only one condition is met, or neither condition is met, the charging process will not be triggered, effectively avoiding erroneous execution of the charging process due to mismatch of a single condition. In the combined condition triggering mode, the information processing box will cyclically detect the combined conditions of multiple sets of strategies. When all the combined conditions of a set of strategies are detected to be met, the parameters of that set of strategies will be automatically called and the corresponding charging process will be executed, supporting precise time-based and location-based triggering of multiple sets of combined condition strategies.

[0118] For example, the vehicle's local flash memory stores two sets of charging strategies. The first set starts charging at 23:00 from Monday to Friday, charging to 90%, which is a time-only start condition. The second set starts charging at 10:00-12:00 on Saturdays at the XX Commercial Center public charging station, charging to 80%, which is a time + location combination start condition. The information processing box performs real-time parallel detection of the start conditions of the two sets of strategies. At 23:00 on Monday, the information processing box detected that the current time of the hardware real-time clock precisely matched the time start conditions of the first set of strategies, immediately determined that the triggering requirements were met, and then read the structured data packet of this set of strategies from the local flash memory, generated a charging strategy message and broadcast it to wake up the vehicle controller. The vehicle controller took the lead, and the battery management system and the on-board charger cooperated to execute the charging process to 90%. At 9:50 on Saturday, the vehicle drove to the XX Commercial Center public charging station. The positioning module collected the current location and found that it matched the location conditions of the second set of strategies, but the current time did not fall within the time range of 10:00-12:00. The information processing box determined that the combined start conditions were not met and did not trigger the charging process. At 10:10 on Saturday, the information processing box detected that the current time fell within the preset time period and the current location still matched the preset charging point. It immediately determined that the combined start conditions of the second set of strategies were met and triggered the charging process. The on-board charger charged to 80% according to the strategy requirements and then stopped, completing the charging process of this set of strategies. If a vehicle leaves the XX Commercial Center public charging station at 11:00 on Saturday, even if the current time is still within the preset time period, the information processing box will immediately control the on-board charger to stop charging because the location conditions are no longer met, ensuring that the charging process strictly matches the combination of start-up conditions.

[0119] This embodiment supports multi-dimensional start condition detection based on current time and / or current location, and enables automatic matching and triggering of multiple charging strategies. This breaks through the limitations of traditional charging solutions that rely on single-time triggering, achieving scenario-based and intelligent adaptation of charging strategies. This further improves the automation and intelligence level of vehicle charging management. At the same time, it strictly follows the strategy parameters to execute charging, which not only meets the user's personalized power needs, but also avoids invalid charging through precise condition triggering, thus achieving dual optimization for battery health protection and vehicle energy consumption management.

[0120] Based on any of the above embodiments, in Embodiment Ten of this application, referring to Figure 4 and Figure 5 The implementation method is described in conjunction with the overall vehicle architecture. The vehicle includes a user interaction layer: providing a settings interface and receiving multiple sets of charging strategies set by the user, including at least one of charging time period, charging date, desired battery level, and charging location. The in-vehicle hardware platform consists of: an application layer (AppLayer): located within the vehicle's infotainment system, processing user input and generating standardized reservation instruction data packets; an In-Vehicle Infotainment Controller Platform (IPCP): acting as a high-performance computing node, responsible for logic processing, instruction verification, and forwarding; a Telematics Control Unit Module (TCAM): integrating a hardware real-time clock, possessing extremely low-power timed wake-up capabilities. It receives and stores instructions from the IPCP, enters sleep mode, and wakes up precisely at a preset time. The underlying controllers (BMS / VCU / OBC): the final execution unit, receiving wake-up instructions from the TCAM and controlling charging behavior. The overall system may also include a cloud service layer: enabling multi-terminal synchronization and remote management of mobile app and vehicle infotainment system settings, as an optional component.

[0121] For example, in the instruction issuance and storage phase (App to IPCP): the user completes the charging policy settings on the vehicle's infotainment interface. The application layer generates a structured data packet containing information such as a unique ID, start timestamp, and target battery level, and sends it to the IPCP domain controller via the vehicle network.

[0122] (IPCP to CAM): IPCP performs verification and format conversion on the command, encapsulates it into a timed task request message that TCAM can recognize, and sends it to the TCAM module via CAN or a private protocol.

[0123] Upon receiving an instruction, the TCAM non-volatilely stores it in its local flash memory and configures the timing interrupt of its internal hardware real-time clock (RTC) according to the start time in the instruction. Once completed, the TCAM enters a low-power sleep mode, with only the RTC circuitry remaining operational, resulting in extremely low power consumption.

[0124] Timed wake-up and execution phase: (RTC interrupt): When the preset time point is reached, the RTC inside the TCAM generates a hardware interrupt, which fully wakes up the entire TCAM module from the low-power mode.

[0125] The TCAM main processor starts up, retrieves the corresponding reservation instruction from the NVM, and translates it into a standard CAN / LIN message that the underlying controller can directly recognize, such as: 0x2XX frame ID, data segment: 0x01 0x45 (start charging, target battery level 70%).

[0126] (TCAM to BMS / VCU): TCAM actively broadcasts the wake-up message via the CAN bus.

[0127] The BMS, VCU and other controllers in a dormant state are awakened by the CAN message, and the instructions are parsed and executed to control the charger to start working and to manage charging according to the strategy (such as the target power).

[0128] Status feedback phase: The underlying controller feeds back the charging status (such as "Charging", "Completed", "Fault") to TCAM and IPCP via the CAN bus. IPCP and TCAM update the task status. The vehicle's infotainment screen / App can obtain the latest status upon the next wake-up, enabling user visualization.

[0129] It should be noted that TCAM refers to the information processing box in this embodiment, IPCP refers to the domain controller, and the controller refers to BMS (Battery Management System) / VCU (Vehicle Control Unit) / OBC (On-Board Charger).

[0130] This embodiment utilizes the hardware timing and storage capabilities of the TCAM module as an "in-vehicle alarm clock," pushing the scheduled charging function down from the application layer to the hardware driver layer, thus constructing the shortest, most reliable, and lowest power consumption execution path. This is not only a software optimization but also a model of software-hardware co-design, fundamentally surpassing traditional solutions that rely on mobile internet and cloud scheduling, achieving comprehensive leadership in functionality, performance, and reliability.

[0131] Compared to traditional time-of-use pricing-guided instant reservation and charging technologies, the electric vehicle charging reservation system proposed in this application achieves comprehensive technological improvements. Firstly, it completely solves the problem of low reservation reliability caused by traditional technologies relying on mobile apps, network connections, and cloud-based command transmission. This application stores charging commands in the TCAM module hardware with an integrated real-time clock, triggering charging through an RTC hardware timed wake-up mechanism. It does not rely on any external network, ensuring a near 100% reservation trigger success rate. Furthermore, traditional technologies require some vehicle network modules to monitor, resulting in high power consumption. This application allows the vehicle to completely sleep, with only the TCAM's RTC circuit operating at microamplitude power consumption, significantly reducing vehicle power consumption during idle periods and improving the range of electric vehicles. Secondly, traditional technologies suffer from long command transmission paths leading to high latency. This application constructs an extremely short command execution path, with the TCAM directly sending commands to the vehicle's underlying controller via the CAN bus, achieving real-time response and millisecond-level precision in timed execution. Thirdly, traditional technologies only... Traditional technologies, with their single-command mode, limited functionality and limited triggering at a single time point, cannot meet the diverse usage scenarios of users. This application achieves deep functional integration, allowing for easy setting of multiple charging strategies and conditional triggering. It also enables refined management by combining navigation destinations and battery status, while providing the underlying hardware foundation for more complex energy management strategies such as V2G and smart grids in the future. Fourthly, traditional technologies are solely cost-oriented, only achieving off-peak charging to save on electricity costs, and the fragmented operation cannot create an integrated "human-vehicle-charging station" experience. This application achieves a leap from a single-cost orientation to full-dimensional value. Through the seamless integration design native to the vehicle, the operation process is smoother. It can also avoid overcharging or undercharging through precise SOC power target setting and coordinated management of charging periods, keeping the battery in the optimal power range for a long time, effectively delaying battery degradation and improving the long-term value of the vehicle. At the same time, it ensures that users charge to the target power before using the vehicle, completely eliminating range anxiety, and achieving a comprehensive improvement in personalized power management, vehicle performance, and user experience.

[0132] This application provides an electronic device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the electronic device charging management method of Embodiment 1 described above.

[0133] The following is for reference. Figure 6The diagram illustrates a structural schematic of an electronic device suitable for implementing embodiments of this application. The electronic devices in these embodiments may include, but are not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, personal digital assistants (PDAs), tablets, and in-vehicle terminals, as well as fixed terminals such as digital TVs and desktop computers. Figure 6 The electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0134] like Figure 6 As shown, the electronic device may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1003 into a random access memory (RAM) 1004. The RAM 1004 also stores various programs and data required for the operation of the electronic device. The processing unit 1001, the ROM 1002, and the RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to the I / O interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. Communication device 1009 allows electronic devices to communicate wirelessly or wiredly with other devices to exchange data. While electronic devices with various systems are shown in the figures, it should be understood that implementation or possession of all the systems shown is not required. More or fewer systems may be implemented alternatively.

[0135] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from ROM 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0136] The electronic device provided in this application, employing the electronic device charging management method described in the above embodiments, can solve the technical problem that related technologies, based on time-segmented charging schemes, struggle to meet diverse user needs. Compared to the prior art, the beneficial effects of the electronic device provided in this application are the same as those of the electronic device provided in the above embodiments, and other technical features of this electronic device are the same as those disclosed in the method of the previous embodiment, and will not be repeated here.

[0137] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

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

[0139] This application also provides a vehicle charging management device, the vehicle charging management device comprising: The policy management unit is configured to write the structured data packet corresponding to the charging policy received by the application layer into the information processing box with the integrated hardware real-time clock in response to the charging policy.

[0140] The configuration unit is configured to configure the wake-up value of the hardware real-time clock based on the structured data packet.

[0141] The low-power unit is configured to control the vehicle to enter a low-power sleep mode.

[0142] Optionally, the policy management unit is further configured to generate and send a structured data packet corresponding to the charging policy to the domain controller; encapsulate the structured data packet into a request message and send the request message to the information processing box of the integrated hardware real-time clock; parse the request message to obtain the structured data packet and write the structured data packet to local flash memory.

[0143] Optionally, the configuration unit is further configured to determine the wake-up value based on the current time recorded by the hardware real-time clock and the charging period contained in the structured data packet; and configure the hardware real-time clock based on the wake-up value.

[0144] Optionally, the low-power unit is further configured to control the circuit corresponding to the hardware real-time clock to maintain power supply, and to control other circuits in the information processing box except for the hardware real-time clock to remain powered off, so that the vehicle enters the low-power sleep mode.

[0145] Optionally, the low-power unit is further configured to wake up the information processing box, which is in a power-down state, in response to a hardware interrupt signal generated when the hardware real-time clock reaches the wake-up value.

[0146] Optionally, the vehicle charging management device further includes a charging control unit configured to read the structured data packet from local flash memory and generate a charging strategy message based on the structured data packet; broadcast the charging strategy message to wake up the vehicle's controller; and, based on the woken-up controller, control the vehicle to execute the charging process corresponding to the charging strategy message.

[0147] The vehicle charging management device provided in this application, employing the vehicle charging management method described in the above embodiments, can solve the technical problem in related technologies where fluctuations in the operating environment of mobile terminals lead to charging reservation failures. Compared with the prior art, the beneficial effects of the vehicle charging management device provided in this application are the same as those of the vehicle charging management method provided in the above embodiments, and other technical features in the vehicle charging management device are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0148] This application also provides a vehicle charging management device, the vehicle charging management device comprising: The strategy management unit is configured to determine a charging strategy in response to a configuration operation triggered by a charging strategy configuration control in the vehicle's interactive interface, or in response to terminal configuration data sent by the server. The charging strategy includes at least one of charging period, charging date, desired charge level, and charging location.

[0149] Optionally, the vehicle charging management device further includes an interaction unit configured to receive a configuration operation triggered by a charging strategy configuration control in the vehicle's interactive interface. The charging strategy configuration control includes at least one of a first control, a second control, a third control, a fourth control, and a fifth control. The first control is used to configure the charging period, the second control is used to configure the desired charge level, the third control is used to configure the charging date, the fourth control is used to configure the charging location, and the fifth control is used to configure both the charging period and the charging date.

[0150] Optionally, the vehicle charging management device further includes a charging control unit, which is configured to obtain the current time and / or current location of the vehicle, and execute the charging process corresponding to any set of charging strategies if the current time and / or current location of the vehicle meets the activation conditions corresponding to any set of charging strategies.

[0151] The vehicle charging management device provided in this application, employing the vehicle charging management method described in the above embodiments, can solve the technical problem in related technologies where controlling charging activation based solely on a single command mode is insufficient to meet the diverse charging needs of users. Compared with the prior art, the beneficial effects of the vehicle charging management device provided in this application are the same as those of the vehicle charging management method provided in the above embodiments, and other technical features in the vehicle charging management device are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0152] This application also provides a vehicle, the vehicle including: a processing unit for storing at least one executable instruction, the executable instruction causing the processing unit to execute the vehicle charging management method of any of the above embodiments, determine a charging strategy, and start a power component when the current time and / or current location of the vehicle are determined to meet any set of start conditions corresponding to the charging strategy; The power supply component is communicatively connected to the processing unit and, upon startup, executes the charging process corresponding to the charging strategy.

[0153] The vehicle also includes communication components that connect with the server to receive terminal configuration data from the server in order to determine the charging strategy.

[0154] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, which are used to execute the electronic device charging management method in the above embodiments.

[0155] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. More 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 disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, radio frequency (RF), or any suitable combination thereof.

[0156] The aforementioned computer-readable storage medium may be included in an electronic device or may exist independently without being assembled into an electronic device.

[0157] The aforementioned computer-readable storage medium carries one or more programs. When the aforementioned one or more programs are executed by an electronic device, the electronic device: responds to a charging strategy received at the application layer by writing a structured data packet corresponding to the charging strategy into an information processing box of an integrated hardware real-time clock; configures the wake-up value of the hardware real-time clock based on the structured data packet; and controls the vehicle to enter a low-power sleep mode.

[0158] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0159] 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 this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing 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 indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0160] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0161] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described electronic device charging management method. This addresses the technical problem that related technologies, which rely on time-based charging schemes, struggle to meet diverse user needs. Compared to existing technologies, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the electronic device charging management method provided in the above embodiments, and will not be elaborated upon here.

[0162] This application provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the vehicle charging management method described above.

[0163] The computer program product provided in this application can solve the technical problem that related technologies, which are based on time-segmented charging schemes, are difficult to meet the diverse needs of users. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as those of the vehicle charging management method provided in the above embodiments, and will not be repeated here.

[0164] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent scope of this application.

Claims

1. A vehicle charging management method, characterized by, The vehicle charging management method includes: In response to the charging strategy received by the application layer, the structured data packet corresponding to the charging strategy is written into the information processing box of the integrated hardware real-time clock. Configure the wake-up value of the hardware real-time clock based on the structured data packet; Control the vehicle to enter a low-power sleep mode.

2. The vehicle charge management method of claim 1, wherein, The step of writing the structured data packet corresponding to the charging strategy into the information processing box of the integrated hardware real-time clock includes: Through the application layer: generate and send the structured data packet corresponding to the charging strategy to the domain controller; The domain controller encapsulates the structured data packet into a request message and sends the request message to the information processing box of the integrated hardware real-time clock. The information processing box parses the request message to obtain the structured data packet and writes the structured data packet into the local flash memory.

3. The vehicle charge management method of claim 1, wherein, The step of configuring the wake-up value of the hardware real-time clock based on the structured data packet includes: The wake-up value is determined based on the current time recorded by the hardware real-time clock and the charging period contained in the structured data packet; Configure the hardware real-time clock based on the wake-up value.

4. The vehicle charging management method as described in claim 1, characterized in that, The control of the vehicle to enter a low-power sleep mode includes: The circuit corresponding to the hardware real-time clock is kept powered, and other circuits in the information processing box except for the hardware real-time clock are kept powered off, so that the vehicle enters the low-power sleep mode.

5. The vehicle charging management method as described in claim 1, characterized in that, After setting the wake-up value of the hardware real-time clock based on the structured data packet, the process includes: In response to a hardware interrupt signal generated when the hardware real-time clock reaches the wake-up value, the information processing box, which is in a power-down state, is woken up. Read the structured data packet from the local flash memory and generate a charging policy message based on the structured data packet; Broadcast the charging strategy message to wake up the vehicle's controller; Based on the awakened controller, the vehicle is controlled to execute the charging process corresponding to the charging strategy message.

6. A vehicle charging management method, characterized in that, The vehicle charging management method includes: In response to a configuration operation triggered by a charging strategy configuration control in the vehicle's interactive interface, or in response to terminal configuration data sent by the server, a charging strategy is determined, wherein the charging strategy includes at least one of charging period, charging date, desired charge level, and charging location.

7. The vehicle charging management method as described in claim 6, characterized in that, The charging strategy configuration control includes at least one of a first control, a second control, a third control, a fourth control, and a fifth control. The first control is used to configure the charging period, the second control is used to configure the desired power level, the third control is used to configure the charging date, the fourth control is used to configure the charging location, and the fifth control is used to configure both the charging period and the charging date.

8. The vehicle charging management method as described in claim 6, characterized in that, After determining the charging strategy, the following steps are included: If the current time and / or current location of the vehicle meet any set of the activation conditions corresponding to the charging strategy, the charging process corresponding to the charging strategy shall be executed.

9. An electronic device, characterized in that, The electronic device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the vehicle charging management method as described in any one of claims 1-5 or 6-8.

10. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the computer-readable storage medium. When the computer program is executed by a processor, it implements the steps of the vehicle charging management method as described in any one of claims 1-5 or 6-8.

Images