Modular sub-system using variable length frame length management

Abstract

A monitoring circuit (122) for use in a management system having modular subsystems (112A-112N) includes a sensor (124) configured to measure parameter values of a monitored electrical component (136) as a function of time and a storage device (126) coupled to the sensor (124) and configured to store the parameter values. The monitoring circuit (122) also includes frame preparation circuitry (130) coupled to the storage device (126) and configured to prepare frames including the parameter values, wherein the prepared frames vary in length as a function of time.

Description

Background Technology

[0001] With the development of new electronic devices and the advancement of integrated circuit (IC) technology, new IC products are being commercialized. One example of an IC product used in electronic devices is a monitoring circuit for rechargeable batteries or electronic components. In a conventional wired battery management system (BMS), the rechargeable battery is managed by a circuit system containing monitoring circuitry to ensure safe and efficient operation in real-world applications such as electric vehicles. A wired communication interface is used to connect the main microcontroller to each battery module, and each battery module is daisy-chained to the rest of the battery modules. The wired BMS utilizes serial wired communication lines and proprietary protocols with deterministic frame timing. The data transmission configuration of the wired BMS allows for the exclusion of certain types of failure modes and safety mechanisms, such as frame counters, while enabling the detection of a sufficient number of communication errors to achieve the target functional safety integrity level. Using a wired communication interface, the main microcontroller cannot monitor and control all parallel battery modules without complex wiring. This wiring makes the repair or replacement of individual battery cells more difficult.

[0002] A wireless connection has been proposed between the battery modules and the main microcontroller to make battery module management more flexible and easier to maintain. In a wireless battery management system (WBMS), the microcontroller monitors each battery module and communicates with it using a wireless communication interface. Some WBMSs or related ICs may lack frame counters or other communication security mechanisms developed for wired battery management systems to detect errors such as: unexpected frame duplication; incorrect frame sequences; frame loss; and frame insertion. Without frame counters or other such communication security mechanisms, the wireless communication interface is vulnerable to errors or attacks, which will prevent proper monitoring and management within the WBMS. Summary of the Invention

[0003] In at least one instance, a monitoring circuit for use in a management system having modular subsystems includes: a sensor configured to measure time-varying parameter values ​​of a monitored electrical component; and a storage device coupled to the sensor and configured to store the parameter values. The monitoring circuit further includes a frame preparation circuit system coupled to the storage device and configured to prepare frames containing the parameter values, wherein the length of the prepared frames varies over time.

[0004] In another example, a system includes: a main controller; and modular subsystems communicating with the main controller. Each of the modular subsystems has: an electrical component; and monitoring circuitry coupled to the electrical component. The monitoring circuitry is configured to: obtain parameter values ​​from monitoring the electrical component; store the parameter values; and prepare a frame having the stored parameter values ​​for transmission to the main controller, the prepared frame having a length that varies over time.

[0005] In another example, a frame counter simulation method in a communication system having a main controller and modular subsystems includes: obtaining time-varying parameter values ​​of a monitored electrical component via a monitoring circuit; and storing the parameter values ​​via the monitoring circuit. The method further includes preparing a frame containing the parameter values ​​via the monitoring circuit. The prepared frame varies in length over time. The method also includes transmitting the prepared frame via the monitoring circuit. Attached Figure Description

[0006] Figure 1 This is a block diagram of a system with modular subsystems and variable frame lengths, based on an example embodiment.

[0007] Figure 2 This is a block diagram of another system with modular subsystems and variable frame lengths, according to another example embodiment.

[0008] Figure 3 This is a diagram of a wireless battery management system (WBMS) with modular subsystems and variable frame lengths, based on an example embodiment.

[0009] Figure 4 This is a diagram of a wireless management network protocol based on an example embodiment.

[0010] Figure 5 This is a diagram of the battery control unit (BCU) and battery monitoring unit (CSU) according to an example embodiment.

[0011] Figure 6 This is a diagram of frames based on an example embodiment.

[0012] Figure 7 This is a diagram of a communication loop with variable frame length according to an example embodiment.

[0013] Figure 8 This is a method for simulating a frame counter in a communication system having a main controller and modular subsystems, according to an example embodiment.

[0014] The same reference numerals are used in the accompanying drawings to depict the same or similar features (structurally and / or functionally). Detailed Implementation

[0015] This document describes a variable frame length option to provide functional safety and / or communication error identification in a management system with a main controller and modular subsystems. Between the main controller and the modular subsystems is a wired or wireless communication interface. Each modular subsystem includes monitoring circuitry and monitored electrical components. In some examples, the monitoring circuitry includes: a sensor configured to measure time-varying parameter values ​​of the monitored electrical components; a storage device coupled to the sensor and configured to store the parameter values; and a frame preparation circuitry coupled to the storage device. In some examples, the sensor is a voltage sensing circuit or a current sensing circuit, and the monitored electrical component is a rechargeable battery. The frame preparation circuitry is configured to prepare frames containing the parameter values, wherein the length of the prepared frames varies over time. In some examples, the frame length varies based on a predetermined frame length pattern stored or generated by the frame preparation circuitry. Alternatively, the frame preparation circuitry is configured to prepare frames of varying lengths that vary over time based on instructions received from the main controller. Alternatively, the frame preparation circuitry is configured to prepare frames of varying lengths that vary over time based on information included in each parameter query received from the main controller. For example, different frame length settings may be included in the parameter queries received from the main controller. Alternatively, the frame preparation circuitry is configured to prepare frames of varying lengths that vary over time in response to individual queries from the main controller. By using frames of different lengths, frame counting is simulated without the cost of a frame counter. Frame differentiation enables the detection of security issues or communication errors, such as duplicates, deletions, insertions, reordering, corruption, and / or delays.

[0016] Figure 1 This is a block diagram of a system 100 with modular subsystems 112A to 112N and variable frame lengths, according to an example embodiment. As shown, system 100 includes a main controller 102 coupled to a main communication interface 110. The main communication interface 110 may be wired or wireless. In some example embodiments, the main controller 102 includes a parameter analysis element 104, a subsystem control element 105, and a frame identification element 106. The parameter analysis element 104 includes hardware, firmware, and / or software configured to analyze parameter values ​​received from the modular subsystems 112A to 112N. For example, the parameter analysis element 104 is configured to determine how the monitored electrical components 136 of the modular subsystem 112A behave individually and in combination. As an example, if system 100 is a battery management system and the monitored electrical components 136 are rechargeable batteries, then the parameter analysis element 104 is configured to determine the behavior of the batteries individually and in combination.

[0017] Subsystem control element 105 includes hardware, firmware, and / or software configured to control or guide the operation of monitored electrical components 136 and related components of modular subsystems 112A to 112N. At least in part, subsystem control element 105 uses the results of parameter analysis element 104 to determine instructions for modular subsystems 112A to 112N and related components to manage each corresponding monitored electrical component 136 over time.

[0018] Frame identification element 106 includes hardware, firmware, and / or software configured to identify frames received from modular subsystems 112A to 112N. As shown, frame identification element 106 includes a variable frame length instruction or setting 108 for identifying the expected frame length of frames received from modular subsystems 112A to 112N. In some embodiments, the expected frame length varies over time based on different data collection cycles for each of modular subsystems 112A to 112N or for all modular subsystems 112A to 112N. In some embodiments, the data collection cycle is initiated by the main controller 102. In other embodiments, the data collection cycle is initiated by modular subsystems 112A to 112N using predetermined scheduling, shared scheduling, or other techniques.

[0019] As shown, the modular subsystem 112A includes an auxiliary communication interface 114. The auxiliary communication interface 114 can be a wired or wireless communication interface. The modular subsystem 112A also includes monitoring circuitry 122 coupled to the auxiliary communication interface 114. Figure 1 In one example, the monitoring circuit 122 includes a sensor 124, a storage device 126, an adjustment controller 128, and a frame preparation element 130. In some example embodiments, the sensor 124 includes a voltage sensor and / or a current sensor configured to obtain voltage and / or current sensed values ​​with respect to the monitored electrical component 136. In other example embodiments, the sensor 124 tracks parameters such as temperature, power, or other parameters.

[0020] Storage device 126 is a volatile or non-volatile memory (e.g., random access memory (RAM), read-only memory (ROM), flash memory, etc.) configured to store parameter values ​​acquired by sensor 124. Adjustment controller 128 includes circuitry configured to adjust characteristics or settings of the monitored electrical component 136f. As an example, if system 100 is a battery management system, then adjustment controller 128 may be configured to adjust battery recharge settings in response to continuous monitoring and analysis of parameter values ​​for individual and / or all batteries in system 100.

[0021] exist Figure 1In one example, frame preparation element 130 includes circuitry, hardware, firmware, and / or software configured to prepare frames with variable frame lengths as described herein. Example frames contain parameter values ​​obtained by sensor 124, where different frames vary in length over time. In some example embodiments, the frame length varies based on a predetermined frame length pattern stored or generated by frame preparation element 130. Alternatively, frame preparation element 130 is configured to prepare frames with varying lengths over time based on instructions received from master controller 102. Alternatively, frame preparation circuitry is configured to prepare frames with varying lengths over time based on information included in each parameter query received from master controller 102. For example, different frame length settings may be included in parameter queries received from master controller 102. Alternatively, frame preparation element 130 is configured to prepare frames with varying lengths over time in response to individual queries from master controller 102.

[0022] Without limitations, each of the modular subsystems 112B to 112N may have the same topology as modular subsystem 112A. As desired, the functionality of the monitored electrical components (e.g., monitored electrical component 126) used in each of the modular subsystems 112B to 112N is combined, and the combined functionality of all monitored electrical components is monitored and adjusted as needed. Over time, the performance of the monitored electrical components and / or other components of the modular subsystems 112A to 112N may degrade. In such cases, it may be necessary to adjust or replace specific monitored electrical components or other components of a given modular subsystem. Such replacements (i.e., using fewer wired connections) are facilitated by using the wireless interface for the primary and secondary communication interfaces 110 and 114, while supporting monitoring, adjustment, status updates, parameter transmission, and / or data storage operations of the monitored electrical components of the modular subsystems 112A to 112N. However, it should be understood that the variable frame length option described herein can also be used with the wired communication interface.

[0023] exist Figure 1 In this configuration, the main controller 102 is also coupled to other components 142 via a communication interface 140. Examples of other components 142 are electronic control units (ECUs), which manage the electrical subsystems of the vehicle or other systems in response to the ongoing state and operation of modular subsystems 112A to 112N.

[0024] Figure 2 It is according to another example embodiment having modular subsystems 222A to 222N ( Figure 1 Block diagram of the modular subsystems 112A to 112N (examples of which) and the system 200 used for variable frame length. Figure 2In this system, system 200 includes a lower voltage (e.g., 12, 24, or 48 volts) domain 202 with control circuitry 204. Figure 2 In this example, the modular subsystems 222A to 222N operate in a higher voltage (e.g., hundreds of volts) domain 203 compared to control circuitry 204. As shown, control circuitry 204 includes microcontroller 102A (… Figure 1 Example of main controller 102) and wired communication interface 110A ( Figure 1 (Example of the main communication interface 110). The control circuit 204 also includes a communication bridge 208 between the microcontroller 102A and the wired communication interface 110A. Figure 2 In this example, the main ECU 250 of system 200 communicates via communication interface 140A ( Figure 1 (An example of the communication interface 140) is coupled to the control circuit 204.

[0025] As shown, the modular subsystem 222A includes module 230A, such as a printed circuit board (PCB) or other circuitry, said module 230A having a wired communication interface 114A. Figure 1 Example of auxiliary communication interface 114), monitoring circuit 122A ( Figure 1 Example of monitoring circuit 122), and adjustment controller 128A ( Figure 1 Example of adjustment controller 128 in the example). Module 230A is coupled to monitored electrical component 136A ( Figure 1 (Example of monitored electrical component 136). Each of the modular subsystems 222B to 222N includes a corresponding module 230B to 230N coupled to the corresponding monitored electrical component 136B to 136N. In some example embodiments, the monitored electrical components 136A to 136N are rechargeable batteries or other components with variable states. Without limitation, each of the modules 230B to 230N includes components of the same type as module 230A (e.g., wireless interface, monitor, and adjustment controller).

[0026] exist Figure 2 In this system, monitored electronic components 136A to 136N can be coupled together to provide combined functionality. As shown, system 200 includes switches 240, 242 and component 244. In some example embodiments, component 244 is an electric motor / engine. In this case, closing the circuit at 240 and 242 causes current to flow through the engine / motor to operate the vehicle. During parking or when the vehicle is off, the circuit is open, and no energy is wasted. Switch 240 is controlled by a control signal from microcontroller 102A, which is transmitted to switch 240 via interface 216. Figure 2In this context, the microcontroller 102A also receives a current sensing signal 248 via interface 218, wherein the current sensing signal 248 is generated from loop 245 or associated sensor 246.

[0027] In some example embodiments, the wired communication interface 110A is configured to send parameter queries to modular subsystems 222A to 222N using an addressing scheme. Alternatively, the wired communication interface 110A is configured to receive frames with parameter values ​​from modular subsystems 222A to 222N. Frames received from modular subsystems 222A to 222N may be response frames (frames generated in response to parameter queries from microcontroller 102A) or scheduling frames (e.g., frames generated in a cycle based on predetermined data updates). In either case, a variable frame length is used to facilitate the detection of communication errors and / or security issues.

[0028] Figure 3 This is a diagram illustrating the use of a wireless battery management system (WBMS) 300 and variable frame length according to an example embodiment. As shown, the WBMS 300 includes battery cells 302A to 302H (e.g., lithium-ion cells) connected in series. Each of the battery cells 302A to 302H is coupled to a corresponding module 304A to 304H (an example of modules 222A to 222N) to form a corresponding modular subsystem (e.g., battery cell 302A and module 304A are...). Figure 1 Modular subsystem 112A or Figure 2 (An example of modular subsystem 222A in the example). Each of modules 304A to 304H contains a corresponding wireless interface 314A to 314H ( Figure 1 An example of auxiliary communication interface 114 in the WBMS 300 is included to perform monitoring, adjustment, and / or wireless communication operations involving the use of variable frame lengths as described herein. The WBMS 300 also includes a microcontroller 102B (…). Figure 1 Examples of microcontrollers 102 and wireless transceivers 110B (in the example). Figure 1 Examples of main communication interface 110 and communication interface 140B (in the example). Figure 1 The control circuit 204A (example of communication interface 140) Figure 2 (Example of control circuit 204). Control circuit 204A is coupled to antenna 308 for wireless communication with modules 304A to 304H. In operation, wireless interface 110B is configured to receive frames with variable frame lengths as described herein.

[0029] For WBMS 300, the functions of battery cells 302A to 302H are combined, and the combined functions of all battery cells 302A to 302H are monitored and adjusted. Over time, the performance of battery cells 302A to 302H may degrade. In this case, it may be necessary to adjust or replace a specific component of battery cells 302A to 302H or other components of the modular subsystem. Such replacement is facilitated by using wireless interface 110B and the corresponding wireless interfaces 314A to 314H of modules 304A to 304H, while supporting monitoring, adjustment, status updates, parameter transmission, and / or other operations related to battery cells 302A to 302H. The use of variable frame length in WBMS 300 helps ensure the proper management of battery cells 302A to 302H by facilitating the detection of communication errors and / or security issues as described herein.

[0030] In some example embodiments, the system (e.g., Figures 1 to 3 Systems 100, 200, and 300 in the system include: a main controller (e.g., Figures 1 to 3 The main controllers 102, 102A, and 102B are included; and modular subsystems that communicate with the main controllers (e.g., Figures 1 to 3 Modular subsystems 112A to 112N, 222A to 222N, and 304A to 304H are included. Each of the modular subsystems has: electrical components (e.g., Figure 1 and 2 The monitored electrical components 136 and 136A are included; the monitoring circuit coupled to the electrical components (e.g., Figure 1 and 2 (Monitors 122 and 122A in the system). The monitoring circuit is configured to: obtain parameter values ​​from monitoring the electrical components; store the parameter values; and prepare frames with the stored parameter values ​​for transmission to the main controller, wherein the length of the prepared frames varies over time.

[0031] In some example embodiments, the monitoring circuitry includes a frame preparation circuitry system (e.g., Figure 1The frame preparation element 130 in the monitoring circuitry is configured to prepare frames of varying lengths that vary over time based on a predetermined frame length pattern stored or generated by the frame preparation circuitry. Alternatively, the monitoring circuitry may include a frame preparation circuitry configured to prepare frames of varying lengths that vary over time based on instructions received from the main controller. Alternatively, the monitoring circuitry may include a frame preparation circuitry configured to prepare frames of varying lengths that vary over time based on settings included in each parameter query received from the main controller. Alternatively, the monitoring circuitry may include a frame preparation circuitry configured to prepare frames of varying lengths that vary over time based on different frame length settings included in parameter queries received from the main controller. Alternatively, the monitoring circuitry may include a frame preparation circuitry configured to prepare frames of varying lengths that vary over time in response to individual queries from the main controller of the management system. In some example embodiments, the frame preparation circuitry is configured to: obtain a frame length setting from each of the individual queries; and use the obtained frame length setting to prepare a response frame for each of the individual queries. While a wired communication interface is possible, other example embodiments include: a main wireless communication interface coupled to the main controller; and auxiliary wireless communication interfaces for each corresponding modular subsystem. In some example embodiments, the monitored electrical component is a rechargeable battery.

[0032] In some implementations, the master controller helps manage the changes in the length of response frames from the secondary radio interface for each refresh cycle. When no errors are present, the response frames from the secondary radio interface will have the length requested by the master controller. In some implementations, the total length of security-related data frames is:

[0033] L TOT =L H +L PL =L H +L PL_F +L PL_V Equation 1

[0034] In equation 1, L TOT It is the total frame length, L H It is the frame header (e.g., address, frame length, cyclic redundancy check, or "CRC"), and L PL It is the length of the payload. In some example embodiments, L PL It can change. More specifically, L PL It can be divided into a fixed payload portion (L) PL_F ) and variable payload section (L PL_V For example, LPL_F Used for data transmission (e.g., parameter values), while L PL_V It is a variable set of virtual bytes (e.g., the number of virtual bytes that varies for different frames). Variable virtual bytes can be discarded after transmission. Alternatively, there are no variable virtual bytes. Instead, the payload length used for data transmission varies over time. In either case, the total variable frame length is simulated as a frame counter without the cost of frame counter hardware.

[0035] Figure 4 This is a diagram of a wireless management network protocol 400 according to an example embodiment. Protocol 400 supports data exchange between the main controller in a wireless management system or WBMS and N auxiliary nodes (parts of each modular subsystem). Figure 4 In this architecture, time is divided into time slots, where the primary node transmits packets in the downlink (DL) time slot, while the secondary node transmits its data packets in its corresponding uplink (UL) time slot. The total time interval, including a single DL time slot (for primary node transmission) and the corresponding UL time slot for secondary node transmission, is called the superframe interval. Figure 4 In this context, DL time slots can be used to transmit parameter queries from the main controller to modular subsystems. UL time slots can be used to transmit frames with parameter values ​​and variable frame lengths, as described herein.

[0036] Figure 5 The battery control unit (BCU) 502 according to an example embodiment (e.g., Figures 1 to 3 The main controllers 102, 102A, and 102B and the battery monitoring unit (CSU) (e.g., Figure 1 and 2 The diagram shows monitoring circuits 122 and 122A. BCU 502 and CSU 510 can be used as part of a management system for monitored electrical components (e.g., Figures 1 to 3 (Parts of systems 100, 200, and 300). As shown, the battery control unit 502 includes control logic 504, such as a microcontroller (MCU). Figure 5 In this configuration, BCU502 is coupled to a wireless transceiver 506 configured to transmit and receive wireless data using frames. Additionally, CSU 510 includes a control state machine 512. Figure 1 (Example of frame preparation element 130 in the image), data acquisition block 514 (e.g., having such...) Figure 1 Sensor 124 and battery balance block 516 (in the middle) Figure 1 (An example of the adjustment controller 128 in the example).

[0037] A secure communication layer is provided between the BCU 502 and CSU 510 using variable frame lengths to mitigate the risk of various communication errors. Typical communication errors include: unexpected duplication of data frames; incorrect data frame sequences; data frame loss; and / or insertion of incorrect data frames.

[0038] In some example implementations, variable frame lengths are used based on the request-response principle. Under unrestricted conditions, several architectural assumptions are required: 1) In error-free operation, the wireless communication channel appears transparent to the data frame exchange between BCU 502 and CSU 510; 2) No CSU 510 in the system will communicate with BCU 502 without being requested; 3) MCU 504 in BCU 502 is the only node that can request the transmission of functional safety-related data and evaluate its validity, integrity, authenticity, and correct timing; 4) MCU 504 in BCU 502 requests data from the battery module and the cell respectively in the form of command frames; 5) Command frames sent from BCU 502 to CSU 510 must be able to specify the payload length of each response frame sent from CSU 510 to BCU 502; 6) The payload length of frames that are both sent and received is determined separately by MCU 504; and 7) The above also applies even when communication between MCU 504 and CSU 510 is completed via an intermediate CSU. This is because the command and response frames are between the two end nodes, and the intermediate node is just a relay node.

[0039] In some implementations, the variable frame length described herein addresses communication errors by specifying and deterministically varying the payload length of the response frame expected to be received by BCU 502. The payload length varies by changing the range of values ​​to be read while adding dummy reads to the response frame (which may not contain useful data). Considering the above assumptions and using a deterministic variable length approach, the variable frame length allows MCU 504 to uniquely identify frames upon reception. Using the described techniques, a frame counter function is simulated to uniquely identify frames without requiring additional hardware. In some implementations, the response frame includes: a fixed-length header specific to a particular communication protocol; and a variable payload. In some implementations, the header includes payload length information, which simplifies the implementation of the error detection mechanism.

[0040] The variable response frame length specification described above can be used to detect communication errors by the MCU 504. By strictly ensuring that the MCU 504 is responsible for sending the request frame, the MCU 504 can detect communication errors, as summarized below.

[0041] Table 1: Communication Error Detection

[0042]

[0043] The example automotive battery monitoring chip supports monitoring up to 16 lithium-based batteries connected in series. These chips are developed according to ISO 26262 and achieve system functionality up to the Automotive Safety Integrity Level (ASIL). When monitoring more than 16 cells is required, the chip can be daisy-chained with other chips. The chip communicates with the main controller via a serial bus on a command-response basis. This wired serial communication can be replaced by a communication system based on a proprietary WBMS protocol and a wireless connectivity chip. The combination of the WBMS protocol and the wireless connectivity chip enables transparent communication between the MCU 504 and each battery monitor.

[0044] In some example implementations, the MCU 504 does not handle the WBMS protocol at all during normal operation. Specifically, the MCU 504 uses a compatible wired communication protocol to help manage the operation of the CSU 510. In this example, the CSU 510's communication protocol (e.g., the BQ protocol) uses the following structure for frames that are both sent and received. To demonstrate frame recognition using this example, a command frame is sent by the MCU 504. This frame instructs the CSU 510 to send function safety-related data from the CSU's storage devices (e.g., register space) along with the next response frame to the MCU 504.

[0045] In some example implementations, MCU 504 waits for presentation from CSU 510. Figure 6The response is in the format shown in frame 600. As shown, frame 600 includes an initialization section (labeled INIT[7:0]) 602, a first address section (labeled DEV ADR[7:0]) 604, a second address section (labeled REG ADR[15:8]) 606, a third address section (labeled REGADR[7:0]) 608, payload sections (labeled DATA MSB[7:0] to DATA LSB[7:0]) 610A to 610G, a first CRC section (labeled CRC[15:8]) 612, and a second CRC section (labeled CRC[7:0]) 614. The initialization section 602 indicates the length of the data payload in bytes. The first address section 604 indicates a device address (e.g., indicating a given modular subsystem). The second and third address sections 606 and 608 indicate the starting address in a specific register space within the device indicated by the first address section 604. The memory range is indicated in DATA MSB byte 610A. Payload segments 610A to 610G carry data such as parameter values. First and second CRC segments 612 and 614 indicate CRC data. During operation, the CSU510 sends back the number of data bytes in payload segments 610A to 610G. Upon reception, the MCU 504 compares the requested number of data bytes with the actual number of data bytes sent. If the comparison shows a match, then no error exists. If the comparison shows a mismatch, then an error is indicated (see, for example, Table 1).

[0046] As an example, if the MCU 504 requires 54 bytes of functional safety-related data from the CSU 510, and the frame length varies by 3, then these 54 bytes represent L in Equation 1. PL_F And the number 3 represents L from equation 1. PL_V The maximum number of different locations that need to be reached. This means L PL_V It will cycle between values ​​0, 1, and 2. Figure 7 The example provided is a regular update of functional safety-related data. Here, the correct L is verified. PL_V The value allows the system to comply with IEC 61784-3 (Section 5.4.2) and ISO 26262-5 (Section D.2.5.7).

[0047] Figure 7 Figure 700 illustrates a communication loop with a variable frame length according to an example embodiment. In Figure 700, BCU502A ( Figure 5 (Examples of BCU 502) and CSU 510A ( Figure 5 (The CSU 510 instance in the example communicates). As shown, there are 6 complete security data update cycles 702. Furthermore, L PL_VValue 704 varies for each of the cycles 702 in the displayed pattern (0, 1, 2, 0, 1, 2). In L PL_V When = 0, the payload contains 54 bytes of data. In this case, the BCU 502A sends a read command to read 54 bytes (CMD Read, DATA_MSB = 54), and the CSU510A responds with 54 bytes (RESP, DATA_SIZE = 54). In L PL_V When = 1, the payload contains 55 bytes of data. In this case, the BCU 502A sends a 55-byte read command (CMD Read, DATA MSB = 55), and the CSU 510A responds with 55 bytes (RESP, DATA_SIZE = 55). In L PL_V When L=2, the number of data bytes in the payload is 56 bytes. In this case, the BCU 502A sends a 56-byte read command (CMD Read, DATA MSB=56), and the CSU 510A responds with 56 bytes (RESP, DATA_SIZE=56). The variable frame length mode is repeated in Figure 700. Although L=2 for 0, 1, and 2 PL_V Variable frame length modes are available, but it should be understood that other L... PL_V Values ​​are also possible.

[0048] Figure 8 It is used in situations where there is a main controller (e.g., Figure 1 The main controller 102 in Figure 2 The main controller 102A in Figure 3 The main control 102B in Figure 5 BCU 502 and Figure 7 BCU 502A in the middle) and modular subsystems (e.g., Figure 1 Modular subsystems 112A to 112N in Figure 2 The communication system of the modular subsystems 222A to 222N in the system (e.g., Figures 1 to 3 A method 800 for simulating a frame counter in one of systems 100, 200, and 300. Method 800 includes, at block 802, a monitoring circuit (e.g., Figure 1 Monitoring circuit 122 in Figure 2 The monitoring circuit 122A in the middle, or Figure 5 CSU 510 or Figure 7The CSU 510A in the monitoring circuitry obtains parameter values ​​of a monitored electrical component (e.g., a rechargeable battery or other monitored electrical component) that vary over time. At block 804, the parameter values ​​are stored by the monitoring circuitry. At block 806, the monitoring circuitry prepares a frame containing the parameter values, wherein the length of the prepared frame varies over time. At block 808, the monitoring circuitry transmits the prepared frame.

[0049] In some implementations, preparing frames with varying lengths over time in block 806 is based on a predetermined frame length pattern. In some implementations, method 800 includes: a monitoring circuit receiving parameter queries, each parameter in the query including a frame length indicator; and the monitoring circuit preparing a frame based on the frame length indicator. In some implementations, method 800 includes: a master controller receiving a prepared frame; the master controller extracting a frame length from each received frame; the master controller comparing each extracted frame length with an expected frame length; if the extracted frame length matches its expected frame length, then the master controller accepts the corresponding frame; and if the extracted frame length does not match its expected frame length, then the master controller asserts an error signal.

[0050] In this description, the term "coupling" may encompass a connection, communication, or signaling path that achieves a functional relationship consistent with this description. For example, if device A generates a signal to control device B to perform an action: then (a) in a first instance, device A is coupled to device B via a direct connection; or (b) in a second instance, if the intermediary component C does not alter the functional relationship between device A and device B such that device B is controlled by device A via a control signal generated by device A, then device A is coupled to device B via the intermediary component C.

[0051] Modifications are possible in the described embodiments, and other embodiments are possible within the scope of the claims.

Claims

1. A monitoring circuit for use in a management system having modular subsystems, the monitoring circuit comprising: A communication interface configured to receive information from the main controller of the management system; and A frame preparation circuit system configured to prepare multiple frames containing parameter values ​​of monitored electrical components, wherein the frame preparation circuit system is configured to: Prepare one frame from the plurality of frames, the frame comprising a first header and a first payload portion, the first payload portion comprising a fixed length portion and a second payload portion; as well as Prepare another frame of the plurality of frames, the other frame including a second header and a third payload portion, the third payload portion including a fixed-length portion and a fourth payload portion, wherein the second payload portion includes fewer virtual bytes than the fourth payload portion, and wherein the first payload portion has the same length as the fixed-length portion of the third payload portion.

2. The monitoring circuit of claim 1, wherein the frame preparation circuit system is configured to prepare frames of varying lengths that vary over time based on a predetermined frame length pattern stored or generated by the frame preparation circuit system.

3. The monitoring circuit of claim 1, wherein the communication interface is configured to receive the information having a first parameter query from the main controller, and wherein the frame preparation circuit system is configured to prepare frames having different lengths that vary over time based on the information contained in each parameter query received from the main controller.

4. The monitoring circuit of claim 1, wherein the frame preparation circuit system is configured to prepare frames of varying lengths that vary over time based on different frame length settings included in a parameter query received from the main controller.

5. The monitoring circuit of claim 1, wherein the frame preparation circuit system is configured to prepare frames of varying lengths that vary over time in response to individual queries from the main controller of the management system.

6. The monitoring circuit of claim 5, wherein the frame preparation circuit system is configured to: Obtain the frame length setting from each of the individual queries; and Use the frame length setting to prepare a response frame for each of the individual queries.

7. The monitoring circuit according to claim 6, wherein the monitored electrical component is a battery of an electric vehicle.

8. The monitoring circuit of claim 1, further comprising a voltage sensing circuit or a current sensing circuit, wherein the monitored electrical component is a battery.

9. The monitoring circuit according to claim 1, wherein the first header and the second header have the same length.

10. The monitoring circuit of claim 1, wherein the fourth payload portion comprises a single virtual byte.

11. The monitoring circuit of claim 1, wherein the communication interface is configured to sequentially transmit one frame of the plurality of frames and another frame of the plurality of frames.

12. The monitoring circuit of claim 11, wherein the communication interface is configured to transmit one of the plurality of frames as the next frame following the other of the plurality of frames.

13. The monitoring circuit of claim 1, wherein the communication interface is configured to wirelessly receive the information from the main controller.

14. The monitoring circuit according to claim 1, wherein the first header includes length information of the first payload portion.

15. A system comprising: Main controller; and Modular subsystems, which communicate with the main controller, each of the modular subsystems having: Electrical components; and Monitoring circuitry, coupled to the electrical component and configured to: Parameter values ​​are obtained from monitoring the electrical components; Store the parameter values; Receive information from the main controller; and Prepare multiple frames having the stored parameter values ​​for transmission to the main controller, wherein preparing the multiple frames includes preparing one frame of the multiple frames, the one frame including a first header and a first payload portion, the first payload portion including a fixed-length portion and a second payload portion; and preparing another frame of the multiple frames, the other frame including a second header and a third payload portion, the third payload portion including a fixed-length portion and a fourth payload portion, wherein the second payload portion includes fewer virtual bytes than the fourth payload portion, and wherein the first payload portion and the fixed-length portion of the third payload portion have the same length.

16. The system of claim 15, wherein the monitoring circuit includes a frame preparation circuit system configured to prepare frames of varying lengths that vary over time based on a predetermined frame length pattern stored or generated by the frame preparation circuit system.

17. The system of claim 15, wherein the monitoring circuitry includes a frame preparation circuitry configured to prepare frames of varying lengths that vary over time based on settings included in each parameter query received from the master controller.

18. The system of claim 15, wherein the monitoring circuit includes a frame preparation circuit system configured to prepare frames of varying lengths that vary over time based on different frame length settings included in a parameter query received from the main controller.

19. The system of claim 15, wherein the monitoring circuitry includes a frame preparation circuitry configured to prepare frames of varying lengths that vary over time as a response to individual queries from the master controller.

20. The system of claim 19, wherein the frame preparation circuitry is configured to: Obtain the frame length setting from each of the individual queries; and Use the obtained frame length to prepare a response frame for each of the individual queries.

21. The system of claim 15, further comprising: A main wireless communication interface, which is coupled to the main controller; and An auxiliary wireless communication interface is provided for each corresponding modular subsystem, wherein the monitored electrical component is a battery.

22. A method for simulating a frame counter in a communication system having a main controller and modular subsystems, the method comprising: The monitoring circuit obtains the parameter values ​​of the monitored electrical components that vary over time; The parameter values ​​are stored by the monitoring circuit; The monitoring circuit receives information from the main controller; The monitoring circuit prepares multiple frames containing the parameter values, wherein preparing the multiple frames includes: Prepare one frame from the plurality of frames, the frame comprising a first header and a first payload portion, the first payload portion comprising a fixed-length portion and a second payload portion; and Prepare another frame from the plurality of frames, the other frame comprising a second header and a third payload portion, the third payload portion comprising a fixed-length portion and a fourth payload portion, wherein the second payload portion contains fewer virtual bytes than the fourth payload portion, and wherein the first payload portion has the same length as the fixed-length portion of the third payload portion; and The prepared multiple frames are transmitted by the monitoring circuit.

23. The method of claim 22, wherein preparing frames having different lengths that vary over time is based on a predetermined frame length pattern.

24. The method of claim 22, further comprising: The monitoring circuit receives parameter queries, each of which contains a frame length indicator; and The monitoring circuit prepares the plurality of frames based on the frame length indicator.

25. The method of claim 22, further comprising: The prepared plurality of frames are received by the main controller; The main controller extracts the frame length from each received frame; The main controller compares the length of each extracted frame with the expected frame length. If the extracted frame length matches its expected frame length, then the main controller accepts the corresponding frame; and If the extracted frame length does not match its expected frame length, then the main controller asserts an error signal.

Images