Method and system for regulating charging limit current, electronic device and medium

Abstract

This invention provides a method, system, electronic device, and medium for adjusting charging limits and current limiting, belonging to the field of automotive technology. The method includes constructing an architecture where an IVI (In-Vehicle Controller) and a T-Box are connected in parallel to a power domain controller; responding to a charging target SOC signal input from the vehicle's infotainment system, the charging target SOC signal is sent to the power domain controller based on an IVI event-driven mechanism to control the on-board charger; responding to a charging target SOC signal input from a mobile terminal, the charging target SOC signal is sent to the power domain controller based on a T-Box event-driven mechanism to control the on-board charger. This invention, by constructing an architecture where the IVI and T-Box are directly connected in parallel to the PDCU (Power Distribution Unit), achieves direct control paths from IVI to PDCU and from T-Box to PDCU, resulting in high reliability and eliminating single points of failure on the command path. Even if the T-Box fails, the local control of the IVI remains effective, improving robustness and availability.

Description

Technical Field

[0001] This invention relates to the field of automotive technology, and in particular to a method, system, electronic device, and medium for adjusting charging limit current. Background Technology

[0002] The battery pack is a very expensive and crucial component of an electric vehicle. While high-current DC fast charging is fast, it generates high temperatures and pressures, stressing the battery's internal chemical structure and irreversibly accelerating capacity degradation. By setting the charging current and charging capacity, compatibility can be improved and battery life maximized.

[0003] For example, in a remote air conditioning control solution, users can set the in-vehicle temperature via IVI or a mobile app. The control path is from IVI to T-BOX to PDCU, which presents a long signal path and the risk of single point of failure. Each command needs to pass through two network nodes (IVI to T-Box, T-Box to PDCU) before reaching the final actuator (PDCU), increasing the overall communication latency and resulting in problems such as response delay and low efficiency. Summary of the Invention

[0004] The present invention aims to solve at least one of the technical problems existing in the prior art, and proposes a method, system, electronic device and medium for adjusting charging limit current limiting.

[0005] In a first aspect, embodiments of the present invention provide a method for adjusting charging limit current limiting, comprising:

[0006] Construct an architecture that connects the IVI and T-BOX in parallel to the power domain controller;

[0007] In response to the charging target SOC signal input by the vehicle infotainment system, the charging target SOC signal is sent to the power domain controller based on the IVI event type to control the on-board charger to charge.

[0008] In response to the charging target SOC signal input by the mobile terminal, the charging target SOC signal is sent to the power domain controller based on the T-BOX event type to control the on-board charger to charge.

[0009] In some embodiments, the step of sending the target SOC signal to the power domain controller based on an IVI event-driven method in response to the target SOC signal input from the vehicle infotainment system to control the on-board charger to charge includes:

[0010] In response to the charging SOC value set by the user through the vehicle system, a charging target SOC signal is generated based on the charging SOC value;

[0011] Based on the IVI event, the target SOC signal is sent to the power domain controller, so that the power domain controller sends the corresponding charging SOC value to the on-board charger based on the target SOC signal.

[0012] In some embodiments, the step of sending the target SOC signal to the power domain controller based on an IVI event-driven method in response to the target SOC signal input from the vehicle infotainment system to control the on-board charger to charge includes:

[0013] In response to the current limit set by the user through the vehicle system, a charging target SOC signal is generated based on the current limit;

[0014] Based on the IVI event, the target SOC signal is sent to the power domain controller, so that the power domain controller sends the corresponding charging SOC value to the on-board charger based on the target SOC signal.

[0015] In some embodiments, the step of sending the target SOC signal to the power domain controller based on an IVI event-driven method in response to the target SOC signal input from the vehicle infotainment system to control the on-board charger to charge includes:

[0016] In response to the charging SOC value set by the user via a mobile terminal, a charging target SOC signal is generated based on the charging SOC value;

[0017] Based on the T-BOX event, the target SOC signal is sent to the power domain controller, so that the power domain controller sends the corresponding SOC value to the on-board charger based on the target SOC signal.

[0018] In some embodiments, the step of sending the target SOC signal to the power domain controller based on an IVI event-driven method in response to the target SOC signal input from the vehicle infotainment system to control the on-board charger to charge includes:

[0019] In response to a current limit set by the user via a mobile terminal, a target SOC signal is generated based on the current limit.

[0020] Based on the T-BOX event, the target SOC signal is sent to the power domain controller, so that the power domain controller sends the corresponding SOC value to the on-board charger based on the target SOC signal.

[0021] In some embodiments, the method further includes:

[0022] Based on the setting status of the memory charging SOC value of the power domain controller;

[0023] When power is restored after a power outage, the setting status of the charging SOC value is fed back to the vehicle system and the mobile device.

[0024] When charging in OFF or ON position, the charging process is initiated based on the charging SOC value.

[0025] Secondly, embodiments of the present invention provide a charging limit current limiting adjustment system, comprising:

[0026] Architecture building module, used to build the architecture of IVI and T-BOX connected in parallel to the power domain controller;

[0027] The vehicle infotainment system setting module is used to respond to the charging target SOC signal input by the vehicle infotainment system and send the charging target SOC signal to the power domain controller based on IVI event type to control the on-board charger to charge.

[0028] The mobile terminal setting module is used to respond to the charging target SOC signal input by the mobile terminal and send the charging target SOC signal to the power domain controller based on the T-BOX event type to control the on-board charger to charge.

[0029] In some embodiments, the power domain controller is used to periodically send slow charging SOC limit setting feedback signals to the vehicle system and the telematics box;

[0030] The power domain controller includes an instruction arbitration and management module, which processes instructions according to a preset arbitration strategy.

[0031] Thirdly, embodiments of the present invention provide an electronic device, including:

[0032] One or more processors;

[0033] Memory, used to store one or more programs;

[0034] When the one or more programs are executed by the one or more processors, the one or more processors implement any of the methods described above.

[0035] Fourthly, embodiments of the present invention provide a computer-readable medium on which a computer program is stored, the computer program being executed by a processor to implement the steps of any of the methods described above.

[0036] The charging limit and current limiting adjustment method provided by this invention includes: constructing an architecture in which the IVI and T-Box are connected in parallel to the power domain controller; responding to the charging target SOC signal input by the vehicle-mounted unit, sending the charging target SOC signal to the power domain controller based on IVI event-type to control the on-board charger to charge; and responding to the charging target SOC signal input by the mobile terminal, sending the charging target SOC signal to the power domain controller based on T-Box event-type to control the on-board charger to charge. This invention, by constructing an architecture in which the vehicle-mounted IVI and the telematics box (T-Box) are directly connected in parallel to the power domain controller (PDCU), realizes the vehicle-mounted IVI→PDCU path and the T-Box→PDCU path. The path is direct and highly reliable, eliminating single points of failure in the command path. Even if the T-Box fails, the local control of the IVI remains effective, greatly improving robustness and availability. Attached Figure Description

[0037] Figure 1 A flowchart illustrating a method for adjusting charging limit current limiting according to an embodiment of the present invention;

[0038] Figure 2 This is a schematic diagram of the charging limit and current limiting process involved in the embodiments of the present invention;

[0039] Figure 3 A structural block diagram of a charging limit current limiting adjustment system provided in an embodiment of the present invention;

[0040] Figure 4 This is a schematic diagram of the vehicle charging control system involved in an embodiment of the present invention;

[0041] Figure 5 This is a structural block diagram of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0042] To enable those skilled in the art to better understand the technical solutions of the present invention, exemplary embodiments of the present invention are described below in conjunction with the accompanying drawings, including various details of the embodiments of the present invention to aid understanding. These should be considered merely exemplary. Therefore, those skilled in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0043] Where there is no conflict, the various embodiments of the present invention and the features thereof may be combined with each other.

[0044] As used herein, the term “and / or” includes any and all combinations of one or more related enumerated entries.

[0045] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the invention. As used herein, the singular forms “a” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that when the terms “comprising” and / or “made of” are used in this specification, the presence of the stated feature, integral, step, operation, element, and / or component is specified, but the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or groups thereof is not excluded. Terms such as “connected” or “linked” are not limited to physical or mechanical connections but can include electrical connections, whether direct or indirect.

[0046] Unless otherwise specified, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art. It will also be understood that terms such as those defined in commonly used dictionaries should be interpreted as having the meaning consistent with their meaning in the context of the relevant art and the invention, and will not be interpreted as having an idealized or overly formal meaning unless expressly so defined herein.

[0047] In the technical solution of this invention, the collection, storage, use, processing, transmission, provision, and disclosure of user personal information all comply with relevant laws and regulations and do not violate public order and good morals. The use of user data in this technical solution follows relevant national laws and regulations (e.g., the "Information Security Technology - Personal Information Security Specification"). For example: appropriate measures are taken for personal information access control; restrictions are imposed on the display of personal information; the purpose of using personal information does not exceed the scope of direct or reasonable association; and explicit identity targeting is eliminated when using personal information to avoid precisely locating a specific individual.

[0048] The key terms involved in this invention are defined as follows:

[0049] IVI: In-vehicle infotainment system, an integrated hardware and software system within the vehicle's cockpit that provides information, entertainment, and connectivity functions for the driver and passengers.

[0050] T-BOX: Telematics Box, an embedded system installed in a car, responsible for wireless communication, data exchange, and remote control.

[0051] PDCU: Powertrain Domain Controller, an electronic control unit responsible for the unified control and management of vehicle powertrain-related functions.

[0052] OBC: On-board charger, a device that is fixedly installed on an electric vehicle to convert alternating current (AC) from the external power grid into direct current (DC) to charge the battery.

[0053] TSP: Telematics Service Provider, which receives various data uploaded from the vehicle's T-BOX and provides services to users through a mobile app.

[0054] Among related technologies, a remote air conditioning control solution is adopted, allowing users to set the in-vehicle temperature via IVI or a mobile app. The IVI sends the SOC value (60%~100%; inclusive) corresponding to the "Charging Power Setting Value" signal (IVI_UserSetChrgSOCTargeReq) to the TBOX; the T-Box sends the SOC value (60%~100%; inclusive) corresponding to the "Charging Power Setting Value" signal (TBOX_ChrgElectricitySetReq) to the PDCU; during charging, when the SOC reaches the set charging limit, the PDCU controls the charging to end and sends a charging completion signal (PDCU_ChrgEn; 0: normally disabled) to the OBC and BMS; the PDCU periodically feeds back the "Limit setting successful" signal (PDCU_ChrgElectricitySetSt) to the IVI and T-Box (APP); the PDCU remembers the SOC limit setting state, and when power is turned off and on again, it feeds back the SOC limit setting state to the IVI and T-Box (APP); when charging in the OFF position, the charging process is started directly according to the remembered charging SOC limit.

[0055] This solution controls the air conditioning system, not the charging management system. This presents a lengthy signal path and a single point of failure risk: the path is IVI → T-BOX → PDCU, and all SOC setting requests initiated from the IVI (in-vehicle screen) must be forwarded through the T-BOX. The T-BOX's primary function is remote communication between the vehicle and the cloud; its stability and real-time priority may be lower than other controllers in the vehicle network. Using it as a signal relay station introduces a potential point of failure. If the T-BOX experiences slow response or even communication interruption due to network problems or high load, the user's setting commands will not reach the PDCU, resulting in operation failure and a poor user experience. There is also a system response delay and low efficiency issue: each command needs to pass through two network nodes (IVI to T-Box, T-Box to PDCU) before reaching the final actuator (PDCU), increasing the overall communication latency.

[0056] To address at least one of the technical problems existing in the aforementioned related technologies, the present invention provides a method for adjusting charging limit current limiting. Figure 1 This is a flowchart illustrating a method for adjusting charging limit current limiting according to an embodiment of the present invention.

[0057] As an embodiment of the present invention, such as Figure 1 As shown, the method for adjusting the charging limit current limit includes:

[0058] Step S1: Construct an architecture that connects the IVI and T-BOX in parallel to the power domain controller;

[0059] Step S2: In response to the charging target SOC signal input by the vehicle system, the charging target SOC signal is sent to the power domain controller based on the IVI event type to control the on-board charger to charge.

[0060] Step S3: In response to the charging target SOC signal input by the mobile terminal, the charging target SOC signal is sent to the power domain controller based on the T-BOX event type to control the on-board charger to charge.

[0061] It should be noted that the execution subject in this embodiment can be an electronic device, which can be a computer device with data processing function, or other devices that can achieve the same or similar functions. This embodiment does not limit this. In this embodiment, the execution subject is a computer device as an example for explanation.

[0062] Specifically, such as Figure 2 As shown, this embodiment constructs an architecture where the IVI and T-Box are directly connected to the PDCU in parallel. The following is combined with... Figure 2 The workflow shown illustrates the method for adjusting the charging limit and current limiting in this embodiment.

[0063] In some embodiments, in response to a target SOC signal input by the vehicle infotainment system, the target SOC signal is sent to the power domain controller based on an IVI event to control the on-board charger to charge. This includes: in response to a user-set SOC value via the vehicle infotainment system, generating a target SOC signal based on the SOC value; and sending the target SOC signal to the power domain controller based on an IVI event, so that the power domain controller sends a corresponding SOC value to the on-board charger based on the target SOC signal.

[0064] Specifically, the vehicle infotainment system settings. Users select the charging SOC value through the vehicle infotainment system. The IVI (Internet Audio Controller) sends the user-set charging target SOC signal (IVI_UserSetChrgSOCTargeReq) to the PDCU (Power Delivery Control Unit). The PDCU sends the corresponding SOC value to the OBC (On-Board Control Unit) via a signal (PDCU_ChrgElectricitySet). The PDCU periodically feeds back the "Slow Charge SOC Limit Setting Feedback" signal (PDCU_ChrgSOCFb) to both the IVI and the T-BOX (APP).

[0065] For example, a user can select or swipe to set a target SOC value (e.g., 80%) on the touchscreen of the in-vehicle infotainment system (IVI). The IVI system generates an IVI_UserSetChrgSOCTargeReq signal (charging target SOC signal). This signal is event-driven, meaning it is sent only when the user sets the value, not periodically, to conserve bus resources. The charging target SOC signal includes the SOC target value the user wishes to set (e.g., 80%). The PDCU (Powertrain Domain Controller) receives the IVI request and verifies its validity (e.g., whether the value is within the allowed range, whether the current vehicle status permits the setting, etc.). The PDCU generates and sends a PDCU_ChrgElectricitySet signal, transmitting the verified or processed SOC target value to the actual actuator, i.e., the OBC (On-Board Charger). Upon receiving the target SOC value from the PDCU, the OBC continuously monitors the current SOC reported by the battery management system (BMS) during the subsequent slow charging process. When the battery SOC reaches the set value, the OBC stops charging.

[0066] For example, status feedback. The PDCU needs to inform the user interface of the status of the "Slow Charge SOC Limit Setting" function. The PDCU generates and sends a PDCU_ChrgSOCFb signal. The signal type is periodic, meaning it is continuously sent at fixed time intervals (e.g., every 100ms or 1 second) to ensure the status displayed on the interface is real-time and continuous. The PDCU_ChrgSOCFb signal can include: the currently effective SOC limit, i.e., the target value actually being used by the OBC; and the status code for the setting feedback status, such as setting successful, setting failed (invalid value), setting rejected (vehicle in motion), etc. The PDCU_ChrgSOCFb signal is sent to both the IVI and the T-BOX. It is sent to the IVI to display the current charging target value on the vehicle's infotainment screen (e.g., displaying "Current charging limit: 80%" on the charging settings page). It is sent to the T-BOX remote communication terminal, which can then send this status to the cloud via the mobile network, ultimately synchronizing it to the user's mobile app. This allows the user to check the vehicle's charging setting status via their mobile phone even when they are not near the vehicle.

[0067] In this embodiment, the user sets the target charge level (e.g., to 80% or 90%) during slow charging via the vehicle infotainment system (IVI) and transmits this instruction to the execution unit (OBC). At the same time, status feedback is provided, allowing the user to customize the charging limit to protect battery life (avoid long-term full charging), save time, or meet temporary travel needs.

[0068] In some embodiments, in response to a target SOC signal input from the vehicle infotainment system, the target SOC signal is sent to the power domain controller based on an IVI event to control the on-board charger to charge. This includes: in response to a current limit set by the user through the vehicle infotainment system, generating a target SOC signal based on the current limit; and sending the target SOC signal to the power domain controller based on an IVI event, so that the power domain controller sends a corresponding SOC value to the on-board charger based on the target SOC signal.

[0069] Specifically, the logic for setting the current limit of the vehicle's IVI is the same as the logic for setting the charging SOC value of the vehicle's IVI mentioned above, and will not be repeated here. Users can select the charging current value (5A, 10A, 16A, 32A, with 32A as the default) through the vehicle's IVI.

[0070] In some embodiments, in response to a target SOC signal input from the vehicle infotainment system, the target SOC signal is sent to the power domain controller based on an IVI event to control the on-board charger to charge. This includes: in response to a SOC value set by a user via a mobile terminal, generating a target SOC signal based on the SOC value; and sending the target SOC signal to the power domain controller based on a T-BOX event, so that the power domain controller sends a corresponding SOC value to the on-board charger based on the target SOC signal.

[0071] Specifically, the settings are configured via a mobile app. Users select the charging SOC value through the mobile app. The T-BOX sends the user-set target charging SOC signal (TBOX_ChrgCurrentSetReq) to the PDCU via an event-based method. The PDCU then sends the corresponding SOC value to the OBC via a signal (PDCU_ChrgElectricitySet). The PDCU also periodically feeds back a "slow charging SOC limit setting feedback" signal (PDCU_ChrgSOCFb) to both the IVI and the T-BOX (app).

[0072] For example, a user finds the charging settings option on a mobile app (such as the brand's official app) and selects or enters a target SOC value (e.g., 85%). The app can send this setting request to a cloud server via mobile internet, and the cloud server then sends it to the vehicle. The T-BOX in the vehicle receives the instruction from the cloud and converts it into a signal TBOX_ChrgCurrentSetReq (target SOC signal) that can be recognized by the in-vehicle network. This signal is event-driven, meaning it is only sent once when a remote instruction arrives. The target SOC signal includes the SOC target value set by the user from the app, which the T-BOX sends directly to the PDCU. The PDCU verifies the request and then sends the PDCU_ChrgElectricitySet signal to the OBC. The OBC receives the instruction and executes it during charging, stopping when the specified SOC value is reached.

[0073] For example, regarding status feedback, the PDCU continues to periodically broadcast the PDCU_ChrgSOCFb signal, simultaneously sending it to the IVI and T-BOX. Sending it to the T-BOX creates a "status loop." After receiving this feedback signal, the T-BOX uploads it to the cloud via the mobile network and then pushes it back to the user's mobile app. This allows the user to see in real-time on the app that "the vehicle's current charging limit has been set to 85%", confirming that their remote command has been successfully executed. Sending it to the IVI ensures consistency between the status display inside and outside the vehicle. Even if the settings are made via mobile phone, the user will see the correct settings on the vehicle's infotainment screen the next time they get in the car.

[0074] In some embodiments, in response to a target SOC signal input from the vehicle infotainment system, the target SOC signal is sent to the power domain controller based on an IVI event to control the on-board charger to charge. This includes: in response to a current limit set by a user via a mobile terminal, generating a target SOC signal based on the current limit; and sending the target SOC signal to the power domain controller based on a T-BOX event, so that the power domain controller sends a corresponding SOC value to the on-board charger based on the target SOC signal.

[0075] Specifically, the current limit setting logic of the mobile APP is the same as the charging SOC value setting logic of the mobile APP mentioned above, and will not be repeated here. Users can select the charging current value (5A, 10A, 16A, 32A, default 32A) through the mobile APP.

[0076] In this embodiment, by constructing an architecture where the IVI and T-Box are directly connected to the PDCU in parallel, single points of failure on the instruction path are eliminated. Even if the T-Box fails, the local control of the IVI remains effective, greatly improving the robustness and availability of the system. This overcomes the risk of complete functional failure caused by the failure of a single node (such as the T-Box) in a serial control link. The IVI and T-Box, as two parallel instruction entry points and status display exit points, do not need to communicate directly; they exchange information through the PDCU as a central hub. This results in low system coupling and ease of maintenance and upgrades.

[0077] In some embodiments, the method further includes: memorizing the setting state of the charging SOC value based on the power domain controller; feeding back the setting state of the charging SOC value to the vehicle system and mobile device when power is turned on again after power-off; and starting the charging process based on the charging SOC value when charging in OFF or ON position.

[0078] Specifically, state memory: The PDCU remembers the setting state of the slow charging SOC limit. When power is turned off and then on again, the slow charging SOC limit setting state is fed back to IVI and T-BOX (APP): When charging in OFF or ON position, the charging process is started directly according to the remembered charging current limit.

[0079] For example, the PDCU stores the user's previously set slow charging SOC limit and charging current value in non-volatile memory, achieving state memory. When the vehicle is powered on again (whether in the OFF or ON position) and starts charging, the PDCU automatically recalls these stored values ​​as the default settings for this charging session, eliminating the need for the user to reset them each time. This achieves a one-time setting that remains effective indefinitely, significantly improving convenience.

[0080] It should be noted that the power domain controller includes an instruction arbitration and management module, which is used to process instructions according to a preset arbitration strategy.

[0081] Specifically, this embodiment designs two independent, parallel command input channels (IVI is the human-machine interface, and T-BOX is the remote interface), both of which are authorized to directly send control commands to the Power Domain Controller (PDCU). The PDCU implements a command arbitration and management module to handle potential command conflicts.

[0082] For example, by introducing a centralized and intelligent command arbitration and management module at the PDCU end, and formulating a clear preset arbitration strategy (such as "last command takes precedence"), it is ensured that there is only one clear execution target regardless of where the command comes from. At the same time, the PDCU acts as the sole authoritative source to uniformly broadcast the status, ensuring strong consistency between the information displayed by the IVI and the T-Box (mobile APP), and solving the problems of command conflicts and status consistency under multiple control sources.

[0083] In this embodiment, the IVI (local operation) and T-BOX (remote APP operation) serve as two independent request sources, both directly sending control commands to the PDCU. The control paths from IVI to PDCU and from T-BOX to PDCU in this embodiment are direct and highly reliable, eliminating the single point of failure risk found in related technologies. Even if the T-BOX temporarily malfunctions, the user can still successfully set charging limits through the in-vehicle IVI screen, resulting in stronger robustness. This method, by reducing signal relay links, allows commands to reach the processing end directly from the sending end, achieving shortest path communication, faster response speed, higher efficiency, and a smoother user experience. The PDCU, as the core controller of the power domain, uniformly receives and executes all charging-related commands, with a clearly defined role, reasonable architecture, and clear responsibilities. The IVI, as the human-machine interface, is responsible for inputting local user commands and displaying status. The T-BOX, as the remote communication gateway, is responsible for receiving and forwarding remote user commands. Each component performs its specific function with low coupling, conforming to the best practices of modern automotive electronic and electrical architecture design. In this embodiment, the signal flow is clear and direct, reducing the number of network signal definitions and relay logic, making software development, testing, and subsequent fault diagnosis simpler and reducing development and maintenance costs.

[0084] Understandably, compared to the shortcomings of related technologies (long signal paths, poor reliability, and single-point failure of the T-BOX), the charging limit and current limiting adjustment method proposed in this embodiment improves response speed and reliability (due to path optimization), eliminates the risk of control function failure caused by single-point failure of the T-BOX, and enhances robustness. Through centralized arbitration and state synchronization, it solves the problems of instruction conflicts and state inconsistencies in multi-control source scenarios, optimizing the user experience. It aligns with the development trend of domain-centralized electronic and electrical architectures, reducing system coupling and maintenance costs.

[0085] The charging limit and current limiting adjustment method provided in this embodiment includes: constructing an architecture in which the IVI and T-Box are connected in parallel to the power domain controller; responding to the charging target SOC signal input by the vehicle-mounted unit, sending the charging target SOC signal to the power domain controller based on IVI event type to control the on-board charger to charge; responding to the charging target SOC signal input by the mobile terminal, sending the charging target SOC signal to the power domain controller based on T-Box event type to control the on-board charger to charge. This embodiment constructs an architecture in which the vehicle-mounted IVI and the telematics box (T-Box) are directly connected in parallel to the power domain controller (PDCU), realizing the vehicle-mounted IVI→PDCU path and the T-Box→PDCU path. The path is direct and highly reliable, eliminating single points of failure on the command path. Even if the T-Box fails, the local control of the IVI remains effective, greatly improving robustness and availability.

[0086] Reference Figure 3 , Figure 3 This is a structural block diagram of an embodiment of the charging limit current limiting adjustment system of the present invention. Figure 3 As shown, the charging limit current limiting adjustment system includes:

[0087] Architecture building module 10 is used to build the architecture of IVI and T-BOX connected in parallel to the power domain controller;

[0088] The vehicle infotainment system setting module 20 is used to respond to the charging target SOC signal input by the vehicle infotainment system and send the charging target SOC signal to the power domain controller based on the IVI event type to control the on-board charger to charge.

[0089] The mobile terminal setting module 30 is used to respond to the charging target SOC signal input by the mobile terminal and send the charging target SOC signal to the power domain controller based on the T-BOX event type to control the on-board charger to charge.

[0090] Specifically, this embodiment combines Figure 4 The vehicle charging control system shown is explained below, for reference. Figure 4 The vehicle charging control system includes: an in-vehicle infotainment system (IVI), a telematics processor (T-BOX), and a power domain controller (PDCU); the IVI and T-BOX are configured to independently and directly send charging target power and slow charging current setting commands to the PDCU; the PDCU is configured to receive commands from the IVI and T-BOX and execute the final power control target based on a preset arbitration strategy.

[0091] For example, the PDCU, as the core controller of the power domain, uniformly receives and executes all charging-related commands, with a clearly defined role, reasonable architecture, and clear responsibilities. The IVI, as the human-machine interface, is responsible for the input of local user commands and the display of status. The T-BOX, as the remote communication gateway, is responsible for receiving and forwarding remote user commands.

[0092] In some embodiments, the power domain controller is used to periodically send slow charging SOC limit setting feedback signals to the vehicle system and the telematics box;

[0093] The power domain controller includes an instruction arbitration and management module, which processes instructions according to a preset arbitration strategy.

[0094] Specifically, by introducing a centralized and intelligent command arbitration and management module at the PDCU end, and formulating clear preset arbitration strategies (such as "last command first"), it is ensured that there is only one clear execution target regardless of where the command comes from. At the same time, the PDCU acts as the sole authoritative source to uniformly broadcast the status, ensuring strong consistency between the information displayed by the IVI and the T-Box (mobile APP), and resolving the command conflict and status consistency issues under multiple control sources.

[0095] The charging limit and current limiting adjustment system provided in this embodiment constructs an architecture in which the vehicle infotainment system (IVI) and the telematics box (T-Box) are directly connected in parallel to the power domain controller (PDCU). This achieves direct and highly reliable paths between the IVI and PDCU, eliminating single points of failure in the command path. Even if the T-Box fails, the local control of the IVI remains effective, greatly improving robustness and availability.

[0096] In addition, for technical details not described in detail in this embodiment of the charging limit and current limiting adjustment system, please refer to the charging limit and current limiting adjustment method provided in any embodiment of the present invention, which will not be repeated here.

[0097] Based on the same inventive concept, embodiments of the present invention also provide an electronic device. Figure 5 This is a structural block diagram of an electronic device provided in an embodiment of the present invention. Figure 5 As shown, an embodiment of the present invention provides an electronic device including: one or more processors 101, a memory 102, and one or more I / O interfaces 103. The memory 102 stores one or more programs, which, when executed by the one or more processors, cause the one or more processors to implement a current limiting adjustment method for charging limits as described in any of the above embodiments; the one or more I / O interfaces 103 are connected between the processor and the memory, configured to enable information interaction between the processor and the memory.

[0098] The processor 101 is a device with data processing capabilities, including but not limited to a central processing unit (CPU); the memory 102 is a device with data storage capabilities, including but not limited to random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and flash memory (FLASH); the I / O interface (read / write interface) 103 is connected between the processor 101 and the memory 102, and can realize information interaction between the processor 101 and the memory 102, including but not limited to a data bus (Bus).

[0099] In some embodiments, the processor 101, memory 102, and I / O interface 103 are interconnected via bus 104, and thus connected to other components of the computing device.

[0100] In some embodiments, the one or more processors 101 include a field-programmable gate array.

[0101] This invention also provides a computer-readable medium. The computer-readable medium stores a computer program, which, when executed by a processor, implements the steps in any of the charging limit current limiting adjustment methods described in the above embodiments. The computer-readable storage medium may be volatile or non-volatile.

[0102] This invention also provides a computer program product, including computer-readable code, or a non-volatile computer-readable storage medium carrying computer-readable code. When the computer-readable code is run in the processor of an electronic device, the processor in the electronic device executes the above-mentioned charging limit current limiting adjustment method.

[0103] Those skilled in the art will understand that all or some of the steps, systems, and apparatuses disclosed above, and their functional modules / units, can be implemented as software, firmware, hardware, or suitable combinations thereof. In hardware implementations, the division between functional modules / units mentioned above does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed collaboratively by several physical components. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit (ASIC). Such software can be distributed on a computer-readable storage medium, which may include computer storage media (or non-transitory media) and communication media (or transient media).

[0104] As is known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information, such as computer-readable program instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), static random access memory (SRAM), flash memory or other memory technologies, portable compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, it is known to those skilled in the art that communication media typically contain computer-readable program instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0105] The computer-readable program instructions described herein can be downloaded from computer-readable storage media to various computing / processing devices, or downloaded via a network, such as the Internet, local area network, wide area network, and / or wireless network, to an external computer or external storage device. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards them to the computer-readable storage media in the respective computing / processing device.

[0106] The computer program instructions used to perform the operations of this invention may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++, etc., and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The computer-readable program instructions may 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 a remote computer, the remote computer may 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 may be connected to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, electronic circuitry, such as programmable logic circuitry, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), is personalized by utilizing state information from the computer-readable program instructions. This electronic circuitry can execute the computer-readable program instructions to implement various aspects of the invention.

[0107] The computer program product described herein can be implemented specifically through hardware, software, or a combination thereof. In one alternative embodiment, the computer program product is specifically embodied in a computer storage medium; in another alternative embodiment, the computer program product is specifically embodied in a software product, such as a software development kit (SDK), etc.

[0108] Various aspects of the present invention are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.

[0109] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processor of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner; thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0110] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0111] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction, which contains one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than those shown in the drawings. For example, two consecutive 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 action, or using a combination of dedicated hardware and computer instructions.

[0112] Example embodiments have been disclosed herein, and while specific terminology has been used, it is for illustrative purposes only and should be construed as such, and is not intended to be limiting. In some instances, it will be apparent to those skilled in the art that features, characteristics, and / or elements described in conjunction with particular embodiments may be used alone, or in combination with features, characteristics, and / or elements described in conjunction with other embodiments, unless otherwise expressly indicated. Therefore, those skilled in the art will understand that various changes in form and detail may be made without departing from the scope of the invention as set forth in the appended claims.

Claims

1. A method for adjusting charging limit current limiting, characterized in that, include: Construct an architecture that connects the IVI and T-BOX in parallel to the power domain controller; In response to the charging target SOC signal input by the vehicle infotainment system, the charging target SOC signal is sent to the power domain controller based on the IVI event type to control the on-board charger to charge. In response to the charging target SOC signal input by the mobile terminal, the charging target SOC signal is sent to the power domain controller based on the T-BOX event type to control the on-board charger to charge.

2. The method according to claim 1, characterized in that, The method of responding to the target SOC signal input by the vehicle infotainment system and sending the target SOC signal to the power domain controller based on an IVI event to control the on-board charger to charge includes: In response to the charging SOC value set by the user through the vehicle system, a charging target SOC signal is generated based on the charging SOC value; Based on the IVI event, the target SOC signal is sent to the power domain controller, so that the power domain controller sends the corresponding charging SOC value to the on-board charger based on the target SOC signal.

3. The method according to claim 1, characterized in that, The method of responding to the target SOC signal input by the vehicle infotainment system and sending the target SOC signal to the power domain controller based on an IVI event to control the on-board charger to charge includes: In response to the current limit set by the user through the vehicle system, a charging target SOC signal is generated based on the current limit; Based on the IVI event, the target SOC signal is sent to the power domain controller, so that the power domain controller sends the corresponding charging SOC value to the on-board charger based on the target SOC signal.

4. The method according to claim 1, characterized in that, The method of responding to the target SOC signal input by the vehicle infotainment system and sending the target SOC signal to the power domain controller based on an IVI event to control the on-board charger to charge includes: In response to the charging SOC value set by the user via a mobile terminal, a charging target SOC signal is generated based on the charging SOC value; Based on the T-BOX event, the target SOC signal is sent to the power domain controller, so that the power domain controller sends the corresponding SOC value to the on-board charger based on the target SOC signal.

5. The method according to claim 1, characterized in that, The method of responding to the target SOC signal input by the vehicle infotainment system and sending the target SOC signal to the power domain controller based on an IVI event to control the on-board charger to charge includes: In response to a current limit set by the user via a mobile terminal, a target SOC signal is generated based on the current limit. Based on the T-BOX event, the target SOC signal is sent to the power domain controller, so that the power domain controller sends the corresponding SOC value to the on-board charger based on the target SOC signal.

6. The method according to any one of claims 1 to 5, characterized in that, The method further includes: Based on the setting status of the memory charging SOC value of the power domain controller; When power is restored after a power outage, the setting status of the charging SOC value is fed back to the vehicle system and the mobile device. When charging in OFF or ON position, the charging process is initiated based on the charging SOC value.

7. A charging limit current limiting regulation system, characterized in that, include: Architecture building module, used to build the architecture of IVI and T-BOX connected in parallel to the power domain controller; The vehicle infotainment system setting module is used to respond to the charging target SOC signal input by the vehicle infotainment system and send the charging target SOC signal to the power domain controller based on IVI event type to control the on-board charger to charge. The mobile terminal setting module is used to respond to the charging target SOC signal input by the mobile terminal and send the charging target SOC signal to the power domain controller based on the T-BOX event type to control the on-board charger to charge.

8. The system according to claim 7, characterized in that, The power domain controller is used to periodically send slow-charge SOC limit setting feedback signals to the vehicle system and remote information processing box; The power domain controller includes an instruction arbitration and management module, which processes instructions according to a preset arbitration strategy.

9. An electronic device, characterized in that, include: One or more processors; Memory, used to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1 to 6.

10. A computer-readable medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1 to 6.

Images