CN115242752B

CN115242752B - Address allocation method, device, equipment and medium of battery management system

Info

Publication number: CN115242752B
Application number: CN202210849102.5A
Authority: CN
Inventors: 张宁宁; 王义乐; 李大宝; 田云芳; 孙君起; 张桢帧; 孙阳; 薄丽丽
Original assignee: China Aviation Lithium Battery Co Ltd
Current assignee: China Aviation Lithium Battery Co Ltd
Priority date: 2022-07-19
Filing date: 2022-07-19
Publication date: 2024-04-12
Anticipated expiration: 2042-07-19
Also published as: CN115242752A

Abstract

The application discloses an address allocation method, device, equipment and medium of a battery management system, and relates to the technical field of battery management systems. The method comprises the following steps: and the current address information of each slave control unit is acquired by recalling the address information of each slave control unit, the address information fed back by each slave control unit is compared with the pre-stored address form, and the units to be processed with the address information different from the pre-stored address form are selected from each slave control unit according to the comparison result. The flow can determine the units to be processed which are not allocated with the address information currently according to the comparison result only by recalling the current address information of each slave control unit and comparing the current address information with the pre-stored address form without adding extra devices, and then issue the address information to be allocated to each unit to be processed based on the pre-stored address form.

Description

Address allocation method, device, equipment and medium of battery management system

Technical Field

The embodiment of the application relates to the technical field of battery management systems, in particular to an address allocation method, device, equipment and medium of a battery management system.

Background

Currently, the mainstream mass-produced electric vehicle model generally adopts a distributed battery management system (Battery Management System, BMS) architecture. The distributed BMS architecture can better realize hierarchical management at the module level and the system level. The BMS mainly comprises a main control unit (BCM, battery Control Module) and a plurality of slave control units (BMM, battery Management Module), and specifically monitors parameter information of the single battery through each slave control unit and feeds back the parameter information to the main control unit, so that the main control unit monitors states of each battery in real time according to feedback information.

In order to realize the communication between the master control unit and each slave control unit, the master control unit is required to distribute unique addresses to each slave control unit so as to ensure the integrity of the information collected by the single battery corresponding to each slave control unit. In the related art, each slave control unit is identified through the change of an electric signal, and then the address of the identified slave control unit is allocated. In the allocation method, an additional acquisition port or component is required to be added to realize the identification of the electric signals, so that the additional cost is caused by the additional component, and the stability of the additional component directly influences the accuracy of address allocation.

Disclosure of Invention

The embodiment of the application provides an address allocation method, device, equipment and medium of a battery management system, which are used for realizing address allocation of a master control unit to slave control units on the basis of not adding additional devices.

In a first aspect, an embodiment of the present application provides an address allocation method of a battery management system, where the method includes:

receiving address information of each slave control unit; the address information at least comprises a first address value representing the current address of the slave control unit and an identification code of the slave control unit;

monitoring a pre-stored code which is the same as the identification code in a pre-stored address form aiming at each address information; wherein, the pre-stored address form stores the association relation between a plurality of pre-stored codes and address values, and each pre-stored code is associated with a unique address value;

if the address value associated with the pre-stored code is different from the first address value, determining that the slave control unit sending the address information is a unit to be processed;

determining address information to be allocated of each unit to be processed based on the pre-stored address form, and issuing the address information to be allocated to each unit to be processed.

According to the embodiment of the application, the current address information of each slave control unit is obtained by recalling the address information of each slave control unit, and then the address information fed back by each slave control unit is compared with the pre-stored address form, and the address information is selected from each slave control unit according to the comparison result to be different from the pre-stored address form to be processed. The flow can determine the units to be processed which are not allocated with the address information currently according to the comparison result only by recalling the current address information of each slave control unit and comparing the current address information with the pre-stored address form without adding extra devices, and then issue the address information to be allocated to each unit to be processed based on the pre-stored address form.

In some possible embodiments, before the monitoring of the pre-stored codes in the pre-stored address form that are identical to the identification codes, the method further comprises:

determining that the prestored address form has the same prestored code as each identification code;

the method further comprises the steps of:

monitoring whether the pre-stored address form has the same pre-stored code as the identification code;

and if the identification code does not exist, taking the slave control unit corresponding to the identification code as the unit to be processed.

After receiving the current address information fed back by each slave control unit, the embodiment of the application determines whether a to-be-processed unit which is not assigned with an address is newly added in the battery management system by monitoring whether a pre-stored address form has a pre-stored code which is the same as an identification code in the address information.

In some possible embodiments, after the receiving address information of each slave unit, the method further includes:

if the number of the slave control units is greater than the number of the address values in the pre-stored address form, generating a designated number of newly-added address values and adding the newly-added address values into the pre-stored address form; wherein the specified number is a difference between the number of slave units and the number of address values.

In the embodiment of the application, if the number of slave units feeding back the address information is greater than the number of address values in the pre-stored address form, it is indicated that the address values in the pre-stored address form are not enough to be distributed by the slave units in the battery management system. At this time, a specified number of newly added address values are generated so that each slave unit can be assigned to a unique address.

In some possible embodiments, before the determining the address information to be allocated for each of the units to be processed based on the pre-stored address table, the method further includes:

determining whether each address information corresponds to the slave control unit to be a unit to be processed or not;

the unit to be processed comprises a first unit in which the pre-stored address form has the same pre-stored code as the identification code thereof, and a second unit in which the pre-stored address form does not have the same pre-stored code as the identification code thereof; the determining the address information to be allocated of each unit to be processed based on the pre-stored address form includes:

taking the address value of a pre-stored code which is the same as the first unit identification code in the pre-stored address form and the pre-stored code as the address information to be allocated of the first unit;

reassigning a pre-stored code for each second address value in the pre-stored address form according to the identification code of each second unit based on the receiving time sequence of the address information of each second unit; the second address value comprises the newly added address value, and address values, of which the pre-stored codes associated with the pre-stored address form are different from the identification codes of any slave control units;

And taking the reassigned pre-stored code and a second address value corresponding to the pre-stored code as address information to be assigned of a second unit with the same identification code as the pre-stored code.

In the embodiment of the application, the address value of the prestored code which is the same as the identification code exists in the form in advance, and the prestored code is used as the address information to be allocated of the unit to be processed corresponding to the prestored code. And then adopting second address values which are not allocated in the pre-stored address form, and sequentially allocating addresses for the second units based on the receiving time sequence of the address information of the second units. Therefore, the utilization rate of the address value can be improved, and the data maintenance amount can be reduced.

In some possible embodiments, the reassigning the pre-stored code to each second address value in the pre-stored address form based on the receiving timing of the address information of each second unit according to the identification code of each second unit includes:

sequentially issuing each second unit identification code to each second address value according to the receiving time sequence; wherein each second address value corresponds to an identification code of a unique second unit;

for each second address value, an identification code associated with the second address value is taken as the pre-stored code of the reassignment.

According to the embodiment of the application, each second address value in the pre-stored address form is sequentially issued to each second unit according to the receiving time sequence of the address information of each second unit, so that the utilization rate of the address value is improved, and the data maintenance amount is reduced.

In a second aspect, an embodiment of the present application provides an address allocation method of a battery management system, where the method includes:

responding to an address recall instruction of a main control unit, and sending address information to the main control unit; the address information at least comprises a first address value representing the current address of the user and a user identification code;

responding to an address allocation instruction of the main control unit, and acquiring address information to be allocated;

and modifying the current address information based on the address information to be allocated.

According to the embodiment of the application, the master control unit sends the address recall indication to the slave control units so that each slave control unit in the system feeds current address information back to the master control unit. And the slave control unit modifies the self address information into the address information to be allocated after receiving the address information to be allocated issued by the master control unit. The above flow does not need to add additional devices, and reduces the address allocation cost.

In some possible embodiments, the address information to be allocated includes a pre-stored code and a second address value bound to the pre-stored code;

The modifying the current address information based on the address information to be allocated includes:

if the pre-stored code is the same as the self-identification code, the self-current address is updated according to the second address value.

After receiving address information to be allocated issued by a main control unit, the embodiment of the application judges whether the main control unit has information issuing error conditions by comparing whether the pre-stored code is identical with the self-identification code. And when the address information to be allocated is the same, the second address value in the address information to be allocated is adopted to update the current address of the user, so that the address allocation precision is improved.

In some possible embodiments, the method further comprises:

and if the pre-stored code is different from the identification code, sending an address reassignment request to the main control unit so that the main control unit resends the address information to be assigned carrying the same pre-stored code as the identification code.

After receiving address information to be allocated issued by a main control unit, the embodiment of the application judges whether the main control unit has information issuing error conditions by comparing whether the pre-stored code is identical with the self-identification code. And when the address information to be allocated is not correct, the address allocation precision is improved by sending an address re-allocation request to the main control unit.

In a third aspect, an embodiment of the present application provides an address allocation apparatus of a battery management system, the apparatus including:

an information receiving module configured to perform receiving address information of each slave unit; the address information at least comprises a first address value representing the current address of the slave control unit and an identification code of the slave control unit;

an information detection module configured to perform monitoring of a pre-stored code in a pre-stored address form that is identical to the identification code for each address information; wherein, the pre-stored address form stores the association relation between a plurality of pre-stored codes and address values, and each pre-stored code is associated with a unique address value;

the unit selection module is configured to execute the determination that the slave control unit sending the address information is a unit to be processed if the address value associated with the pre-stored code is different from the first address value;

the address allocation module is configured to determine address information to be allocated for each unit to be processed based on the pre-stored address form, and send the address information to be allocated to each unit to be processed.

In some possible embodiments, before executing the monitoring of the same pre-stored code in the pre-stored address form as the identification code, the information detection module is further configured to:

the information detection module is further configured to:

In some possible embodiments, after performing the receiving the address information of each slave unit, the information receiving module is further configured to:

In some possible embodiments, before executing the determining the address information to be allocated for each of the units to be processed based on the pre-stored address table, the address allocation module is further configured to:

the unit to be processed comprises a first unit in which the pre-stored address form has the same pre-stored code as the identification code thereof, and a second unit in which the pre-stored address form does not have the same pre-stored code as the identification code thereof; executing the determining, based on the pre-stored address table, address information to be allocated for each of the units to be processed, the address allocation module being configured to:

In some possible embodiments, the receiving timing based on the address information of each second unit is performed, and a pre-stored code is reassigned to each second address value in the pre-stored address table according to the identification code of each second unit, and the address assignment module is configured to:

In a fourth aspect, an embodiment of the present application provides an address allocation apparatus of a battery management system, where the apparatus includes:

an information transmitting module configured to perform transmission of address information to a main control unit in response to an address recall instruction of the main control unit; the address information at least comprises a first address value representing the current address of the user and a user identification code;

the address acquisition module is configured to respond to the address allocation instruction of the main control unit and acquire address information to be allocated;

and the address updating module is configured to execute modification of the current address information based on the address information to be allocated.

In some possible embodiments, the address information to be allocated includes a pre-stored code and a second address value bound to the pre-stored code; executing the modifying of the current address information based on the address information to be allocated, the address update module being configured to:

In some possible embodiments, the address update module is further configured to:

In a fifth aspect, embodiments of the present application provide an electronic device, including:

a memory for storing program instructions;

a processor for invoking the program instructions stored in the memory and executing the steps comprised by the method of any of the first or second aspects in accordance with the obtained program instructions.

In a sixth aspect, embodiments of the present application provide a computer-readable storage medium storing a computer program comprising program instructions that, when executed by a computer, cause the computer to perform the method of any one of the first or second aspects.

In a seventh aspect, embodiments of the present application provide a computer program product comprising: computer program code which, when run on a computer, causes the computer to perform the method of any of the first or second aspects.

Drawings

Fig. 1 is a schematic view of an application scenario provided in an embodiment of the present application;

fig. 2 is a timing chart of an address allocation method of the battery management system according to the embodiment of the present application;

FIG. 3 is a schematic diagram of a new address value provided in an embodiment of the present application;

fig. 4 is a flowchart of determining a unit to be processed according to an embodiment of the present application;

fig. 5 is a schematic diagram of judging a unit to be processed according to an embodiment of the present application;

fig. 6 is a schematic diagram of address information to be allocated according to an embodiment of the present application;

fig. 7 is a flowchart of an overall address allocation method of the battery management system according to an embodiment of the present application;

fig. 8 is another flowchart of an address allocation method of the battery management system according to the embodiment of the present application;

fig. 9 is a block diagram of an address allocation device 900 of the battery management system according to the embodiment of the present application;

fig. 10 is a block diagram of an address allocation device 1000 of a battery management system according to an embodiment of the present application;

fig. 11 is a schematic diagram of an electronic device according to an embodiment of the present application.

Detailed Description

For the purposes of making the objects, technical solutions and advantages of the present application more apparent, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure. Embodiments and features of embodiments in this application may be combined with each other arbitrarily without conflict. Also, while a logical order of illustration is depicted in the flowchart, in some cases the steps shown or described may be performed in a different order than presented.

The terms first and second in the description and claims of the present application and in the above-described figures are used for distinguishing between different objects and not for describing a particular sequential order. Furthermore, the term "include" and any variations thereof is intended to cover non-exclusive protection. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may include other steps or elements not listed or inherent to such process, method, article, or apparatus. The term "plurality" in the present application may mean at least two, for example, two, three or more, and embodiments of the present application are not limited.

As mentioned above, in the related art, in order to implement communication between the master control unit and each slave control unit, each slave control unit is identified by a change of an electrical signal, and then address allocation is performed on the identified slave control unit. In the allocation method, an additional acquisition port or component is required to be added to realize the identification of the electric signals, so that the additional cost is caused by the additional component, and the stability of the additional component directly influences the accuracy of address allocation.

To solve the above problems, the inventive concept of the present application is: and the current address information of each slave control unit is acquired by recalling the address information of each slave control unit, the address information fed back by each slave control unit is compared with the pre-stored address form, and the units to be processed with the address information different from the pre-stored address form are selected from each slave control unit according to the comparison result. The flow can determine the units to be processed which are not allocated with the address information currently according to the comparison result only by recalling the current address information of each slave control unit and comparing the current address information with the pre-stored address form without adding extra devices, and then issue the address information to be allocated to each unit to be processed based on the pre-stored address form.

Referring to fig. 1, an application scenario is schematically shown according to an embodiment of the present application.

As shown in fig. 1, the application scenario includes a master control unit 101, a plurality of slave control units 102 (1 to N), and a single battery corresponding to each slave control unit 102.

After the battery management system is started, the master control unit 101 sends an address recall instruction to each slave control unit 102, so that each slave control unit 102 feeds back current address information to the master control unit 101. After receiving the address information fed back by each slave control unit 102, the master control unit 101 compares the fed back address information with a pre-stored address form to determine a to-be-processed unit to which an address is not allocated currently according to the comparison result.

Further, the master control unit 101 allocates an address value not yet allocated in the pre-stored address table to each unit to be processed, so that each slave control unit 102 in the battery management system has a unique address.

In some possible embodiments, the master control unit 101 communicates with each slave control unit 102 via a controller area network (Controller Area Network, CAN).

After the application scenario of the embodiment of the present application is introduced, the technical solution provided by the embodiment of the present application is described in a time sequence manner. As shown in fig. 2, fig. 2 is a timing chart of a process of allocating addresses to slave units 102 by the master unit 101, including:

step 201: the main control unit 101 sends an address recall instruction;

in the embodiment of the application, the master control unit can send an address recall instruction to each slave control unit after being started. In addition, the master control unit can also automatically send address recall instructions to each slave control unit every preset time period after being started. The main control unit sends an address recall instruction to acquire current address information of each slave control unit in the battery management system. The specific trigger condition for sending the address recall instruction can be specifically set according to the actual requirement.

Step 202: in response to the address recall instruction, the slave control unit 102 feeds back current address information of itself to the master control unit 101;

the address information of the slave unit includes an identification code and a first address value. The identification code is a unique code set when the slave control units leave the factory, and the identification code of each slave control unit is different. The first address value of the slave control unit is the current network address of the slave control unit.

Step 203: determining a unit to be processed according to the comparison result of the address information and the pre-stored address form; specifically, the master control unit 101 takes the slave control unit 102, the identification code of which is not stored in the pre-stored address form, as a unit to be processed; the slave control unit 102 with the same pre-stored code as the identification code and different address values associated with the first address information and the pre-stored code is used as a unit to be processed;

in the embodiment of the application, the association relationship between a plurality of pre-stored codes and address values is stored in the pre-stored address form. Each pre-stored code stored in the pre-stored address form can be understood as the identification code of each slave unit recorded by the master control unit after the previous address allocation to all slave units in the battery management system. The address value associated with each pre-stored code is the address allocated to the corresponding control unit by the pre-stored code.

After the address information of each slave unit is obtained in step 202, it is required to detect whether the identification code in each address information has the same pre-stored code in the pre-stored address table. The aim is to determine whether there is a newly added slave unit in the battery management system. It is assumed that the pre-stored address form stores pre-stored codes A-D and address values 1-4 associated with the pre-stored codes A-D. If 5 pieces of address information are received this time, the identification codes included in the address information are A, B, C, E, F. It is illustrated that slave D is removed and slave E and F are newly added to the system. Obviously, at this time, 4 address values in the form are not sufficiently allocated to 5 slave modules. Therefore, a designated number of newly added address values is required to be generated and added to the pre-stored address form, and the designated number is the difference between the number of slave units feeding back the address information and the number of address values in the form.

In some possible embodiments, the address value allocated by the master control unit to each slave control unit is 1 to N, where N is the number of slave control units in the battery management system. As shown in fig. 3, a total of 4 address values 1 to 4 are assumed in the pre-stored address table. And the number of slave units feeding back the address information to the master control unit is 5, a new address value 5 needs to be generated in the form so as to ensure that each slave unit in the battery management system can be allocated to the address value. Compared with the mode of randomly generating the address values, the flow can avoid the problem of excessive number of generated address values caused by the replacement of slave control units in the system. Thereby improving the utilization rate of the address value and reducing the data maintenance amount.

The specific flow of how the main control unit determines the unit to be processed in the step 203 is shown in fig. 4, and the method includes the following steps:

step 401: detecting whether a pre-stored address form contains a pre-stored code identical to the identification code;

step 402: if the identification code does not exist, the slave control unit corresponding to the identification code is used as a unit to be processed;

specifically, if the form does not have the same pre-stored code as the identification code, it indicates that the slave unit corresponding to the identification code is newly added, so that an address needs to be allocated to the slave unit. At this time, the slave unit needs to be used as a unit to be processed waiting for address allocation.

Step 403: if yes, detecting whether the address value associated with the prestored code in the prestored address form is the same as the corresponding first address value;

step 404: if the identification codes are the same, the identification codes are characterized that the slave control units corresponding to the identification codes are allocated with addresses; at this time, the address information of the next slave unit is detected, and the above-mentioned step 401 is executed again. Otherwise, returning to the step 402, and taking the slave control unit corresponding to the identification code as a unit to be processed;

specifically, if the first address value is different from the address value associated with the pre-stored code, it is indicated that the current network address of the slave control unit is not allocated by the master control unit, and in order to ensure the integrity of the information collected by the unit cell corresponding to the slave control unit, the master control unit needs to allocate an address to the slave control unit, so that the slave control unit needs to be used as a unit to be processed waiting for allocating the address.

After determining the units to be processed in each slave control unit, each unit to be processed needs to be assigned with a unique address. See in particular the following steps.

Step 204: the main control unit 101 determines address information to be allocated of each unit to be processed based on a pre-stored address form;

when the method is implemented, the judgment of the unit to be processed needs to be firstly determined to be executed on each piece of received address information. Thus, the address value to be allocated in the pre-stored address form can be obtained. For example, a pre-stored address table such as that shown in FIG. 5 includes 4 pre-stored codes A-D and address values 1-4 associated with the pre-stored codes A-D. Suppose that 5 pieces of address information 1 to 5 are received this time: the address information 1 includes an identification code a, a first address value 1; the address information 2 includes an identification code B, a first address value 2; the address information 3 includes an identification code E, a first address value 4; the address information 4 includes an identification code D, a first address value 8; the address information 5 includes an identification code F, a first address value 9;

as can be seen from the above determination in step 203, the identification codes in the "address information 1" and the "address information 2" have the same pre-stored code in the form, and the address value associated with the pre-stored code is the same as the first address value. This means that the current address information of the slave unit a corresponding to the [ address information 1 ] and the slave unit B corresponding to the [ address information 2 ] is correct, i.e. the address values 1 and 2 in the token form have been assigned to the slave unit a and the slave unit B. Next, the identification codes in the [ address information 3 ] and the [ address information 5 ] are not stored in the pre-stored address table, but the identification code in the [ address information 4 ] is the same as the pre-stored code D, but the address value associated with the pre-stored code D corresponding to the first address value is different. From this, it can be determined that the slave unit E, D, F corresponding to the address information 3 to 5 is a unit to be processed.

In addition, because the number of the slave control units corresponding to the feedback address information is greater than the number of the address values in the pre-stored address form, a designated number of newly added address values 5 are required to be generated so that the number of the address values in the pre-stored address form is enough to be distributed by each slave control unit. At this time, address values 1 and 2 in the pre-stored address form are allocated to the slave units a and B, while address values 3 to 5 are not yet allocated, and at this time, the address values 3 to 5 are the address values to be allocated.

In the embodiment of the application, the units to be processed are divided into a first unit and a second unit; the first unit is a unit to be processed, wherein the pre-stored address form contains the same pre-stored code as the identification code. Such as slave unit D in the example of fig. 5 described above; the second unit is a unit to be processed, such as the slave units E and F in the example of fig. 5, which does not have the same pre-stored code as the identification code in the pre-stored address table. Next, how to determine the address information to be allocated for each unit to be processed in step 204 of the present application is described, and the pre-stored address table shown in fig. 5 is still described below, specifically, as shown in fig. 6, each slave unit shown in fig. 6 is ordered to be a-F according to the time sequence of receiving the address information. I.e. the ordering of the pending units E, D and F is D, E, F.

When the method is implemented, firstly, the address value of the pre-stored code which is the same as the first unit identification code in the pre-stored address form and the pre-stored code which is related to the address value are taken as the address information to be allocated of the pre-stored code corresponding to the first unit. Because the prestored address form contains the prestored code D which is the same as the identification code of the unit D to be processed, the unit D to be processed is a first unit; at this time, the pre-stored code D in the pre-stored address form and the address value 4 associated with the pre-stored code D are required to be used as the address information to be allocated for the first unit D.

And then, based on the receiving time sequence of the address information of each second unit, reassigning the pre-stored code for each second address value in the pre-stored address form according to the identification code of each second unit, and taking the reassigned pre-stored code and the second address value corresponding to the pre-stored code as the address information to be assigned of the second unit with the same identification code as the pre-stored code.

The identification codes of the units E and F to be processed are not stored in the pre-stored address form corresponding to the pre-stored codes, so that the units E and F to be processed are second units. The second address value is the aforementioned newly added address value (e.g. the newly added address value 5 in the example of fig. 5) and the address value (e.g. the address value 3 in the example of fig. 5) that the pre-stored code associated in the pre-stored address table is different from the identification code of any slave unit.

In practice, after the address value 4 in the pre-stored address table is allocated to the first unit D, the address value not yet allocated in the table (i.e. the second address value) includes the address value 3 and the address value 5. At this time, according to the receiving time sequence of each second unit, each second unit identification code can be issued to each second address value in turn; for each second address value, the identification code associated with the second address value is taken as a pre-stored code which is reassigned.

Specifically, according to the receiving time sequence of the second unit E and F address information, an association relation is established with each second address value in the form in sequence. Because the number of the second address values is the same as that of the second units, the receiving time sequence of each second unit can be in one-to-one correspondence with the ordering of each second address value in the form, for example, the identification code E of the second unit E is associated with the second address value 3 which is not allocated in the form, and is used as a pre-stored code for reallocating the address value; and associating the identification code F of the second unit F with the second address value 5 which is not allocated yet in the form, and taking the identification code F as a pre-stored code which is reallocated by the address value. Thus, the address information to be allocated of the second unit E includes a pre-stored code E and a second address value 3 associated with the pre-stored code E, and the address information to be allocated of the second unit F includes a pre-stored code F and a second address value 5 associated with the pre-stored code F. It should be understood that each address value in the pre-stored address table has a sorting order, and the sorting order may be determined by the size of the pre-stored code associated with each address value, or may be determined according to the time sequence of updating the address value, which is not limited in this application.

And in the process, the pre-stored codes of the second address values in the pre-stored address form are updated in sequence according to the receiving time sequence of the address information of each second unit, and the updated pre-stored codes and the second address values related to the pre-stored codes are issued to the second units corresponding to the pre-stored codes. Therefore, the utilization rate of the address value can be improved, a large number of redundant address values are prevented from being increased, and the data maintenance amount is reduced.

Step 205: the main control unit 101 issues an address allocation instruction to the unit to be processed, and issues address information to be allocated to the unit to be processed; it should be noted that, in practical applications, the battery management system includes a plurality of slave units 102, and for convenience in understanding the address allocation flow in the embodiments of the present application, the slave unit 102 shown only in fig. 2 is referred to as a unit to be processed. It should be understood that the actual unit to be processed should be some one or more of the several slave units 102.

Step 206: in response to the address allocation instruction, the slave control unit 102 receives address information to be allocated issued by the master control unit 101;

step 207: the slave control unit 102 detects whether a pre-stored code in the address information to be allocated is identical to the self-identification code;

specifically, in order to avoid the master control unit from misplacing the address information to be allocated, the slave control unit needs to check whether the pre-stored code in the address information to be allocated is the same as the identification code of the slave control unit in advance after receiving but allocating the address information.

Step 208: if the address information is the same, the slave control unit 102 updates the current address according to the second address value in the address information to be allocated;

step 209: the slave control unit 102 sends prompt information representing that the address updating is completed to the master control unit 101;

step 210: after receiving the prompt information of the address updating completion of the slave control unit 102, the master control unit 101 updates the pre-stored address form according to the updated address information of the slave control unit 102.

Specifically, the slave unit D, E, F in the example of fig. 6 is described. Assuming that the slave control unit D, E, F feeds back the prompt information of the completion of the address updating of the master control unit, the master control unit changes the association item of the address value 3 in the pre-stored address form from the pre-stored code C to the pre-stored code D, changes the association item of the address value 4 from the D to the E, and newly adds the address value 5 and the pre-stored code F associated with the address value 5 in the form.

Thereby, the recording of each slave unit of the assigned address in the current battery management system is completed.

Step 211: if the two addresses are different, the slave control unit 102 sends a request for reassigning the addresses to the master control unit 101;

specifically, the self-identification code can be added to the request in a mode of sending a request message or a message, so that the main control unit can inquire the address information to be allocated again based on the identification code in the request, and further the second address value bound with the pre-stored code identical to the identification code in the address information to be allocated is determined.

Step 212: the main control unit 101 reselects address information to be allocated and issues to the unit to be processed in response to the request for reallocating addresses.

The main control unit re-inquires the address information to be allocated determined in the step 204 based on the identification code in the request, and further selects a second address value bound by the same pre-stored code as the identification code in the address information to be allocated. If the address information to be allocated has the same pre-stored code as the identification code, the address information to be allocated is sent to the slave control unit corresponding to the identification code. If the address information to be allocated does not have the pre-stored code which is the same as the identification code, the address allocation instruction of the main control unit is issued by the wrong slave control unit, and at the moment, the instruction information representing the allocated address of the slave control unit is transmitted.

Based on the same inventive concept, the embodiment of the present application provides an address allocation method of a battery management system, which is applied to a main control unit, and specifically as shown in fig. 7, including:

step 701: receiving address information of each slave control unit; the address information at least comprises a first address value representing the current address of the slave control unit and an identification code of the slave control unit;

Step 702: monitoring a pre-stored code which is the same as the identification code in a pre-stored address form aiming at each address information; wherein, the pre-stored address form stores the association relation between a plurality of pre-stored codes and address values, and each pre-stored code is associated with a unique address value;

step 703: if the address value associated with the pre-stored code is different from the first address value, determining that the slave control unit sending the address information is a unit to be processed;

step 704: determining address information to be allocated of each unit to be processed based on the pre-stored address form, and issuing the address information to be allocated to each unit to be processed.

the method further comprises the steps of:

the determining the address information to be allocated of each unit to be processed based on the pre-stored address form includes:

based on the first order of the units to be processed in the battery management system, pre-stored codes are allocated to the second address values in the pre-stored address form again; the second address value comprises the newly added address value and an address value corresponding to a pre-stored code which is the same as the identification code of any unit to be processed in the pre-stored address form;

and taking the reassigned pre-stored code and a second address value corresponding to the pre-stored code as address information to be assigned of a unit to be processed, the identification code of which is the same as that of the pre-stored code.

In some possible embodiments, each address value stored in the pre-stored address form is provided with a second ordering; the re-allocating pre-stored codes to each second address value based on the first ordering of each unit to be processed in the battery management system comprises the following steps:

sequentially associating a second address value in the second ordering with each unit to be processed according to the first ordering of each unit to be processed;

for each second address value, taking the identification code of the unit to be processed associated with the second address value as the pre-stored code of the reassignment.

Based on the same inventive concept, the embodiment of the present application provides an address allocation method of a battery management system, which is applied to a slave unit, specifically as shown in fig. 8, and includes:

step 801: responding to an address recall instruction of a main control unit, and sending address information to the main control unit; the address information at least comprises a first address value representing the current address of the user and a user identification code;

step 802: responding to an address allocation instruction of the main control unit, and acquiring address information to be allocated;

step 803: and modifying the current address information based on the address information to be allocated.

In some possible embodiments, the address information to be allocated includes a pre-stored code and a second address value bound to the pre-stored code; the modifying the current address information based on the address information to be allocated includes:

In some possible embodiments, the method further comprises:

Based on the same inventive concept, the embodiment of the present application provides an address allocation apparatus 900 of a battery management system, specifically as shown in fig. 9, including:

an information receiving module 901 configured to perform reception of address information of each slave unit; the address information at least comprises a first address value representing the current address of the slave control unit and an identification code of the slave control unit;

an information detection module 902 configured to perform monitoring, for each address information, a pre-stored code in a pre-stored address form that is the same as the identification code; wherein, the pre-stored address form stores the association relation between a plurality of pre-stored codes and address values, and each pre-stored code is associated with a unique address value;

A unit selecting module 903 configured to determine that a slave unit that sends the address information is a unit to be processed if the address value associated with the pre-stored code is different from the first address value;

the address allocation module 904 is configured to determine address information to be allocated for each of the units to be processed based on the pre-stored address table, and send the address information to be allocated to each of the units to be processed.

In some possible embodiments, before executing the monitoring of the same pre-stored code in the pre-stored address form as the identification code, the information detection module 902 is further configured to:

the information detection module 902 is further configured to:

In some possible embodiments, after performing the receiving the address information of each slave unit, the information receiving module 901 is further configured to:

In some possible embodiments, before executing the determining the address information to be allocated for each of the units to be processed based on the pre-stored address table, the address allocation module 904 is further configured to:

the unit to be processed comprises a first unit in which the pre-stored address form has the same pre-stored code as the identification code thereof, and a second unit in which the pre-stored address form does not have the same pre-stored code as the identification code thereof; executing the determining, based on the pre-stored address table, address information to be allocated for each of the units to be processed, the address allocation module 904 being configured to:

Based on the same inventive concept, an embodiment of the present application provides an address allocation apparatus 1000 of a battery management system, specifically as shown in fig. 10, including:

an information transmission module 1001 configured to perform transmission of address information to a main control unit in response to an address recall instruction of the main control unit; the address information at least comprises a first address value representing the current address of the user and a user identification code;

An address acquisition module 1002 configured to perform acquisition of address information to be allocated in response to an address allocation instruction of the main control unit;

an address update module 1003 is configured to perform modifying the current address information based on the address information to be allocated.

In some possible embodiments, the address information to be allocated includes a pre-stored code and a second address value bound to the pre-stored code; performing the modifying the current address information based on the address information to be allocated, the address update module 1003 is configured to:

In some possible embodiments, the address update module 1003 is further configured to:

An electronic device 130 according to this embodiment of the present application is described below with reference to fig. 11. The electronic device 130 shown in fig. 11 is merely an example, and should not be construed to limit the functionality and scope of use of embodiments of the present application in any way.

As shown in fig. 11, the electronic device 130 is embodied in the form of a general-purpose electronic device. Components of electronic device 130 may include, but are not limited to: the at least one processor 131, the at least one memory 132, and a bus 133 connecting the various system components, including the memory 132 and the processor 131.

Bus 133 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a processor, and a local bus using any of a variety of bus architectures.

Memory 132 may include readable media in the form of volatile memory such as Random Access Memory (RAM) 1321 and/or cache memory 1322, and may further include Read Only Memory (ROM) 1323.

Memory 132 may also include a program/utility 1325 having a set (at least one) of program modules 1324, such program modules 1324 include, but are not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.

The electronic device 130 may also communicate with one or more external devices 134 (e.g., keyboard, pointing device, etc.), one or more devices that enable a user to interact with the electronic device 130, and/or any device (e.g., router, modem, etc.) that enables the electronic device 130 to communicate with one or more other electronic devices. Such communication may occur through an input/output (I/O) interface 135. Also, electronic device 130 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet, through network adapter 136. As shown, network adapter 136 communicates with other modules for electronic device 130 over bus 133. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 130, including, but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.

In an exemplary embodiment, a computer readable storage medium is also provided, such as a memory 132, comprising instructions executable by the processor 131 of the apparatus 400 to perform the above-described method. Alternatively, the computer readable storage medium may be ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.

In an exemplary embodiment, a computer program product is also provided, comprising a computer program/instruction which, when executed by the processor 131, implements any one of the methods of address allocation for a battery management system as provided herein.

In an exemplary embodiment, aspects of an address allocation method of a battery management system provided herein may also be implemented in the form of a program product comprising program code for causing a computer device to perform the steps of the address allocation method of a battery management system according to the various exemplary embodiments of the present application as described herein above, when the program product is run on the computer device.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The program product for address assignment for battery management systems of embodiments of the present application may employ a portable compact disc read-only memory (CD-ROM) and include program code and may be run on an electronic device. However, the program product of the present application is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

The readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for carrying out operations of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the language or similar programming languages. The program code may execute entirely on the consumer electronic device, partly on the consumer electronic device, as a stand-alone software package, partly on the consumer electronic device, partly on the remote electronic device, or entirely on the remote electronic device or server. In the case of remote electronic devices, the remote electronic device may be connected to the consumer electronic device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external electronic device (e.g., connected through the internet using an internet service provider).

It should be noted that although several units or sub-units of the apparatus are mentioned in the above detailed description, such a division is merely exemplary and not mandatory. Indeed, the features and functions of two or more of the elements described above may be embodied in one element in accordance with embodiments of the present application. Conversely, the features and functions of one unit described above may be further divided into a plurality of units to be embodied.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable image scaling device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable image scaling device, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable image scaling device to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

While preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiments and all such alterations and modifications as fall within the scope of the application.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present application without departing from the spirit or scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims and the equivalents thereof, the present application is intended to cover such modifications and variations.

Claims

1. A method for assigning addresses to a battery management system, the method comprising:

Sending an address recall instruction to each slave control unit and receiving address information of each slave control unit; the address information at least comprises a first address value representing the current address of the slave control unit and an identification code of the slave control unit;

if the number of the slave control units is greater than the number of the address values in the pre-stored address form, generating a designated number of newly-added address values and adding the newly-added address values into the pre-stored address form; wherein the specified number is a difference between the number of slave units and the number of address values;

if the address value associated with the pre-stored code is different from the first address value, determining that the slave control unit sending the address information is a unit to be processed; the unit to be processed comprises a first unit in which the pre-stored address form has the same pre-stored code as the identification code thereof, and a second unit in which the pre-stored address form does not have the same pre-stored code as the identification code thereof;

taking the reassigned pre-stored code and a second address value corresponding to the pre-stored code as address information to be assigned of a second unit with the same identification code as the pre-stored code; and transmitting the address information to be allocated to each unit to be processed.

2. The method of claim 1, wherein prior to monitoring the pre-stored address form for the same pre-stored code as the identification code, the method further comprises:

the method further comprises the steps of:

3. The method of claim 1, wherein reassigning pre-stored codes for each second address value in the pre-stored address form based on the received timing of the address information for each second unit based on the identification code for each second unit, comprising:

4. A method for assigning addresses to a battery management system, the method comprising:

modifying current address information based on the address information to be allocated; the address information to be allocated is issued to a unit to be processed by the main control unit; the to-be-processed unit is determined from each slave control unit according to the comparison result of the address information reported by each slave control unit and a pre-stored address form by the master control unit; the address information at least comprises a first address value representing the current address of the slave control unit and an identification code of the slave control unit; if the number of the slave control units is greater than the number of the address values in the pre-stored address form, the master control unit generates a designated number of newly-added address values and adds the newly-added address values into the pre-stored address form; the specified number is the difference between the number of slave units and the number of address values;

The unit to be processed comprises a first unit in which the pre-stored address form has the same pre-stored code as the identification code thereof, and a second unit in which the pre-stored address form does not have the same pre-stored code as the identification code thereof; the address information to be allocated is issued to each unit to be processed by the main control unit in the following manner:

taking the address value of a pre-stored code which is the same as the first unit identification code in a pre-stored address form and the pre-stored code as address information to be allocated of the first unit;

5. The method of claim 4, wherein the address information to be allocated comprises a pre-stored code and a second address value bound to the pre-stored code; the modifying the current address information based on the address information to be allocated includes:

6. The method of claim 5, wherein the method further comprises:

7. An address allocation apparatus of a battery management system, the apparatus comprising:

the information receiving module is configured to send an address recall instruction to each slave control unit and receive the address information of each slave control unit; the address information at least comprises a first address value representing the current address of the slave control unit and an identification code of the slave control unit;

an address allocation module configured to perform an address value of a pre-stored code in the pre-stored address form that is the same as the first unit identification code, and the pre-stored code as address information to be allocated for the first unit;

8. The apparatus of claim 7, wherein prior to executing the monitoring of the pre-stored address form for the same pre-stored code as the identification code, the information detection module is further configured to:

the information detection module is further configured to:

9. The apparatus of claim 7, wherein the timing of receiving the address information based on each second unit is performed, and wherein the pre-stored codes are reassigned for each second address value in the pre-stored address form based on the identification code of each second unit, and wherein the address assignment module is configured to:

10. An address allocation apparatus of a battery management system, the apparatus comprising:

an address update module configured to perform modification of current address information based on the address information to be allocated; the address information to be allocated is issued to a unit to be processed by the main control unit; the to-be-processed unit is determined from each slave control unit according to the comparison result of the address information reported by each slave control unit and a pre-stored address form by the master control unit; the address information at least comprises a first address value representing the current address of the slave control unit and an identification code of the slave control unit; if the number of the slave control units is greater than the number of the address values in the pre-stored address form, the master control unit generates a designated number of newly-added address values and adds the newly-added address values into the pre-stored address form; the specified number is the difference between the number of slave units and the number of address values;

11. The apparatus of claim 10, wherein the address information to be allocated comprises a pre-stored code and a second address value bound to the pre-stored code; executing the modifying of the current address information based on the address information to be allocated, the address update module being configured to:

12. The apparatus of claim 11, wherein the address update module is further configured to:

13. An electronic device, comprising:

a memory for storing program instructions;

a processor for invoking program instructions stored in said memory and for performing the steps comprised in the method according to any of claims 1-6 in accordance with the obtained program instructions.

14. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program comprising program instructions which, when executed by a computer, cause the computer to perform the steps comprised by the method according to any of claims 1-6.