(19)
(11)EP 3 624 295 B1

(12)EUROPEAN PATENT SPECIFICATION

(45)Mention of the grant of the patent:
23.12.2020 Bulletin 2020/52

(21)Application number: 19192752.4

(22)Date of filing:  21.08.2019
(51)International Patent Classification (IPC): 
H02J 7/00(2006.01)
H04B 7/00(2006.01)
H04W 72/00(2009.01)
H04B 17/00(2015.01)
H04W 52/02(2009.01)

(54)

BATTERY MANAGEMENT SYSTEM, AND METHOD AND APPARATUS FOR TRANSMITTING INFORMATION

BATTERIEVERWALTUNGSSYSTEM, VERFAHREN UND VORRICHTUNG ZUR INFORMATIONSÜBERTRAGUNG

SYSTÈME DE GESTION DE BATTERIE ET PROCÉDÉ ET APPAREIL DE TRANSMISSION D'INFORMATIONS


(84)Designated Contracting States:
AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

(30)Priority: 12.09.2018 CN 201811061368

(43)Date of publication of application:
18.03.2020 Bulletin 2020/12

(73)Proprietor: Contemporary Amperex Technology Co., Limited
Jiaocheng District Ningde City, Fujian 352100 (CN)

(72)Inventors:
  • DAN, Zhimin
    Ningde City, Fujian 352100 (CN)
  • LU, Wenbin
    Ningde City, Fujian 352100 (CN)
  • ZHANG, Wei
    Ningde City, Fujian 352100 (CN)
  • HOU, Yizhen
    Ningde City, Fujian 352100 (CN)
  • XU, Jia
    Ningde City, Fujian 352100 (CN)
  • LUO, Jiechao
    Ningde City, Fujian 352100 (CN)
  • YU, Teng
    Ningde City, Fujian 352100 (CN)

(74)Representative: Slingsby Partners LLP 
1 Kingsway
London WC2B 6AN
London WC2B 6AN (GB)


(56)References cited: : 
WO-A1-2015/189898
US-A1- 2018 123 705
  
      
    Note: Within nine months from the publication of the mention of the grant of the European patent, any person may give notice to the European Patent Office of opposition to the European patent granted. Notice of opposition shall be filed in a written reasoned statement. It shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention).


    Description

    FIELD



    [0001] The present disclosure relates to the technical field of new energy, and in particular, to a battery management system, and a method and apparatus for transmitting information in a battery management system.

    BACKGROUND



    [0002] A battery management system may include a master node and a plurality of slave nodes. The master node and each slave node may use wireless communication technology for data interaction, and may complete tasks such as a command request, data upload, etc. Before normal communication between the master node and the slave nodes, physical serial number coding is required. After the coding is completed, the slave nodes may collect data of a battery such as voltage, temperature, current, diagnosis, etc., and report the data to the master node periodically or based on an event through a wireless signal for the master node to perform data processing and perform corresponding actions.

    [0003] In the battery management system, if the master node and the slave nodes communicate wirelessly using a wireless signal of a fixed frequency, and there is an interference signal of the same frequency or approximate frequency in the external environment, communication between the master node and the slave nodes will be seriously interfered. Furthermore, due to differences in structural layout of different battery management systems, there may be media between nodes in the battery management system that seriously interfere with wireless communication, which may result in poor communication or communication interruption between the master node and a certain slave node. In addition, since the nodes in the battery management system may cause a multipath fading phenomenon due to reflections from structural members or other nodes, this may also result in poor communication or communication interruption between the master node and a certain slave node. Various communication problems between the master node and the slave nodes caused by different reasons will reduce the reliability of transmitting information in the battery management system.

    [0004] Document WO 2015/189898 A1 discloses a battery management system (BMS) with wireless communication between a master and slave nodes. In paragraph [0043] it discloses to change the communication frequency when the communication quality of the frequency channel has deteriorated.

    SUMMARY



    [0005] Embodiments of the present invention are defined
    in independent claim 1, which provides a battery management system wireless communication method,
    in independent claim 6 which provides a corresponding method from the point of view of the master,
    in independent claim 9 which is a corresponding method from the point of view of the intermediate slave node,
    in independent claim 12 which provides an apparatus counterpart of claim 1,
    in independent claim 13 which provides an apparatus counterpart of claim 6,
    in independent claim 14 which provides an apparatus counterpart of claim 9 and
    in claim 15 which provides a battery management system depending on claims 12, 13 and 14.

    [0006] According to embodiments of the present disclosure, there is provided a battery management system, and a method and apparatus for transmitting information in a battery management system, which may improve the reliability of wireless communication in the battery management system.

    [0007] According to an aspect of the embodiments of the present disclosure, there is provided a method for transmitting information in a battery management system. The method may include: determining, from a plurality of slave nodes, a fault slave node that communicates abnormally with a master node in the battery management system; selecting a target slave node from the plurality of slave nodes, wherein the target slave node is a slave node that communicates normally with both the master node and the fault slave node; transmitting frequency conversion information to the target slave node, so that the target slave node forwards the frequency conversion information to the fault slave node, and the fault slave node performs a frequency conversion based on the frequency conversion information; and transmitting information with the fault slave node using a frequency after the frequency conversion.

    [0008] In an embodiment, selecting a target slave node from the plurality of slave nodes may include: selecting, from the plurality of slave nodes, any slave node other than the fault slave node as a first slave node; determining the first slave node as the target slave node, if the first slave node communicates normally with both the master node and the fault slave node; and reselecting the first slave node if the first slave node communicates abnormally with at least one of the master node and the fault slave node.

    [0009] In an embodiment, if transmission of information with the fault slave node using the frequency after the frequency conversion is successful, the method may further include: transmitting the frequency after the frequency conversion to all slave nodes of the plurality of slave nodes except the fault slave node.

    [0010] In an embodiment, if transmission of information with the fault slave node using the frequency after the frequency conversion fails, the method may further include: forwarding data between the master node and the fault slave node using the target slave node.

    [0011] In an embodiment, the method for transmitting information in the battery management system may further include: determining that no target slave node is selected from the plurality of slave nodes; performing a timed frequency hopping based on a preset frequency hopping rule, and transmitting information with the fault slave node using a frequency after the frequency hopping, wherein the frequency after the frequency hopping is consistent with a frequency of the fault slave node after a timed frequency hopping based on the preset frequency hopping rule.

    [0012] According to another aspect of the embodiments of the present disclosure, there is provided a method for transmitting information in a battery management system. The method may include: receiving frequency conversion information transmitted by a master node in the battery management system; forwarding the frequency conversion information to a fault slave node, so that the fault slave node performs a frequency conversion based on the frequency conversion information, and the master node transmits information with the fault slave node using the frequency after the frequency conversion, wherein the fault slave node is a slave node, determined by the master node from a plurality of slave nodes, that communicates abnormally with the master node.

    [0013] In an embodiment, if the master node successfully transmits information with the fault slave node using the frequency after the frequency conversion, the method for transmitting information in the battery management system may further include: receiving and storing the frequency after the frequency conversion transmitted by the master node.

    [0014] In an embodiment, if the master node fails to transmit information with the fault slave node using the frequency after the frequency conversion, the method for transmitting information in the battery management system may further include: forwarding data between the master node and the fault slave node.

    [0015] According to yet another aspect of the embodiments of the present disclosure, there is provided a method for transmitting information in a battery management system. The method may include: receiving frequency conversion information transmitted by a target slave node, wherein the target slave node is a slave node selected from a plurality of slave nodes by a master node in the battery management system, and the target slave node is a slave node that communicates normally with both the master node and a fault slave node, and wherein the fault slave node is a slave node, determined by the master node from the plurality of slave nodes, that communicates abnormally with the master node; and performing a frequency conversion based on the frequency conversion information, so that the master node uses a frequency after the frequency conversion to transmit information with the fault slave node.

    [0016] In an embodiment, if the master node fails to transmit information with the fault slave node using the frequency after the frequency conversion, the method for transmitting information in the battery management system may further include: forwarding data between the master node and the fault slave node using the target slave node.

    [0017] In an embodiment, if the master node fails to select the target slave node from the plurality of slave nodes, the method for transmitting information in the battery management system may further include: performing a timed frequency hopping based on a preset frequency hopping rule within a preset time period, and transmitting information with the master node using a frequency after the frequency hopping, wherein the frequency after the frequency hopping is consistent with a frequency of the master node after a timed frequency hopping based on the preset frequency hopping rule.

    [0018] According to yet another aspect of the embodiments of the present disclosure, there is provided an apparatus for transmitting information in a battery management system. The apparatus may include: a fault slave node determination module configured to determine, from a plurality of slave nodes, a fault slave node that communicates abnormally with a master node in the battery management system; a target slave node selection module configured to select a target slave node from the plurality of slave nodes, wherein the target slave node is a slave node that communicates normally with both the master node and the fault slave node; a first transmission module configured to transmit frequency conversion information to the target slave node, so that the target slave node forwards the frequency conversion information to the fault slave node, and the fault slave node performs a frequency conversion based on the frequency conversion information; and an information transmission module configured to transmit information with the fault slave node using a frequency after the frequency conversion.

    [0019] According to yet another aspect of the embodiments of the present disclosure, there is provided an apparatus for transmitting information in a battery management system. The apparatus may include: a first reception module configured to receive frequency conversion information transmitted by a master node in the battery management system; and a second transmission module configured to forward the frequency conversion information to a fault slave node, so that the fault slave node performs a frequency conversion based on the frequency conversion information, and the master node transmits information with the fault slave node using a frequency after the frequency conversion, wherein the fault slave node is a slave node, determined by the master node from a plurality of slave nodes, that communicates abnormally with the master node.

    [0020] According to yet another aspect of the embodiments of the present disclosure, there is provided an apparatus for transmitting information in a battery management system. The apparatus may include: a second reception module configured to receive frequency conversion information transmitted by a target slave node, wherein the target slave node is a slave node selected from a plurality of slave nodes by a master node in the battery management system, and the target slave node is a slave node that communicates normally with both the master node and a fault slave node, and wherein the fault slave node is a slave node, determined by the master node from the plurality of slave nodes, that communicates abnormally with the master node; and a frequency conversion module configured to perform a frequency conversion based on the frequency conversion information, so that the master node uses a frequency after the frequency conversion to transmit information with the fault slave node.

    [0021] According to yet another aspect of the embodiments of the present disclosure, there is provided a battery management system. The battery management system may include the apparatus for transmitting information in a battery management system according to various aspects described above.

    [0022] According to the battery management system, and the method and apparatus for transmitting information in the battery management system according to the embodiments of the present disclosure, the master node may transmit frequency conversion information to the fault slave node using the target slave node that may communicate normally with both the master node and the fault slave node, to change a frequency of the fault slave node, so as to recover normal communication between the master node and the fault slave node automatically, thereby improving the reliability of wireless communication in the battery management system.

    BRIEF DESCRIPTION OF THE DRAWINGS



    [0023] In order to illustrate technical solutions of the embodiments of the present disclosure more clearly, drawings that need to be used in the embodiments of the present disclosure will be briefly introduced below. For those ordinary skilled in the art, other drawings can be obtained from these drawings without any creative work.

    Fig. 1 illustrates a schematic structural diagram of a battery management system according to an embodiment of the present disclosure;

    Fig. 2 illustrates a schematic flow chart of selecting a target slave node by a master node according to an embodiment of the present disclosure;

    Fig. 3 illustrates a schematic flow chart of a method for a fault slave node to perform frequency conversion based on frequency conversion information according to an embodiment of the present disclosure;

    Fig. 4 illustrates a schematic diagram of a result of dividing a data packet according to an embodiment of the present disclosure;

    Fig. 5 illustrates a schematic flow chart of a method for transmitting information in a battery management system according to an embodiment of the present disclosure;

    Fig. 6 illustrates a schematic flow chart of a method for transmitting information in a battery management system according to another embodiment of the present disclosure;

    Fig. 7 illustrates a schematic flow chart of a method for transmitting information in a battery management system according to yet another embodiment of the present disclosure;

    Fig. 8 is a schematic structural diagram of an apparatus for transmitting information in a battery management system according to an embodiment of the present disclosure;

    Fig. 9 is a schematic structural diagram of an apparatus for transmitting information in a battery management system according to another embodiment of the present disclosure;

    Fig. 10 is a schematic structural diagram of an apparatus for transmitting information in a battery management system according to yet another embodiment of the present disclosure.


    DETAILED DESCRIPTION



    [0024] The features and exemplary embodiments of the various aspects of the present disclosure will be described in detail below. In order to make objects, technical solutions and advantages of the present disclosure more comprehensible, the present disclosure will be further described in detail below with reference to the drawings and embodiments. It should be understood that the specific embodiments described herein are intended to be illustrative only and not to limit the present disclosure. For those skilled in the art, the present disclosure may be practiced without some of these specific details. The following description of embodiments is only provided, by illustrating examples of the present disclosure, for a better understanding of the present disclosure.

    [0025] It should be noted that, in the present disclosure, relational terms such as first, second, etc. are merely used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply there is any such actual relationship or order among these entities or operations. Furthermore, terms such as "comprising", "including" or any other variations thereof are intended to encompass a non-exclusive inclusion, such that a process, method, article, or device that comprises a plurality of elements may include not only these elements but also other elements that are not listed explicitly, or may further include elements that are inherent to such a process, method, article, or device. An element defined by a phrase "comprising..." does not exclude the presence of an additional same element in the process, method, article, or device that comprises the element, without further limitation.

    [0026] A system for transmitting information in a battery management system according to an embodiment of the present disclosure will first be described in detail below with reference to the drawings.

    [0027] Fig. 1 illustrates a schematic structural diagram of a battery management system 100 according to an embodiment of embodiments of the present disclosure. Referring to Fig. 1, the battery management system may include a master node M and a plurality of slave nodes S0, S1, S2.....Sk, wherein k is a positive integer greater than or equal to 1. Dotted lines in Fig. 1 may represent that the master node M and each slave node may transmit information wirclcssly.

    [0028] The master node M may store communication frequencies of each slave node in the battery management system, so that the master node M and each slave node may achieve data interaction through a certain communication frequency, and communication between the master node M and each slave node may be independent. As an example, the master node M may interact with a slave node Sj through a frequency fj, where j=0, 1, 2...k. There is no limit on a relationship among the k+1 frequencies of f0, f1, f2...fk, and they may be equal or unequal.

    [0029] In an embodiment of the present disclosure, both the master node and each slave node in the battery management system may have a storage space for storing frequencies of all slave nodes in the battery management system, to achieve data transmission between any two slave nodes.

    [0030] In the battery management system, when the master node and the slave nodes transmit information, due to the influence of factors such as external environment, structural layout or structural components, the master node may fail to transmit information with a certain slave node, that is, abnormal communication occurs.

    [0031] In an embodiment, if the master node M transmits information to the slave node S0 at the frequency f0, but the master node M has not received feedback information from the slave node S0 within a preset time period, then the master node M may determine that communication with the slave node S0 is abnormal, that is, the slave node So may be determined as a fault slave node.

    [0032] In the battery management system according to an embodiment of the present disclosure, when the master node determines that there is a fault slave node that communicates abnormally with the master node among the plurality of slave nodes in the battery management system, a target slave node may be selected from the plurality of slave nodes, and frequency conversion information may be transmitted to the target slave node. The target slave node may forward the frequency conversion information to the fault slave node, and then the fault slave node may perform frequency conversion based on the frequency conversion information. The master node may use a frequency after the frequency conversion to transmit information with the fault slave node successfully, thereby automatically recovering information transmission between the master node and the fault slave node, and improving the reliability of transmitting information in the battery management system.

    [0033] In an embodiment of the present disclosure, the target slave node may be a slave node that may communicate normally with both the master node and the fault slave node. Fig. 2 illustrates a schematic flow chart 200 of selecting a target slave node by a master node according to an embodiment of the present disclosure. As shown in Fig. 2, in this embodiment, a method for a master node to select a target node from a plurality of slave nodes may include the following steps.

    [0034] In step S20, the master node may select any slave node, from a target set including i slave nodes, as a first slave node.

    [0035] In an embodiment of the present disclosure, the target set may be a set of all slave nodes among the plurality of slave nodes in the battery management system except a fault slave node determined by the master node, wherein i may be a positive integer greater than 1. That is to say, the master node may select, from the plurality of slave nodes in the battery management system, any slave node other than the fault slave node as the first slave node.

    [0036] As an example, the battery management system may include slave nodes S0, S1, S2.....Sk, namely, may include k+1 slave nodes. If the slave node So is a fault slave node, then the target set may include k slave nodes, namely, slave nodes S1, S2.....Sk.

    [0037] In step S21, whether communication between the master node and the first slave node is normal may be determined.

    [0038] In an embodiment of the present disclosure, if communication between the master node and the first slave node is normal, then the method may proceed to step S22.

    [0039] If communication between the master node and the first slave node is abnormal, then i=i-1. The master node may reselect the first slave node in the target set including i-1 slave nodes. The target set including i-1 slave nodes may be obtained by removing the slave node selected in step S20 from the target set including i slave nodes.

    [0040] As an example, the master node may select the slave node S1, from the target set including the slave nodes S1, S2.....Sk, as the first slave node. If communication between the slave node S1 and the master node is abnormal, then the master node may reselect, from the target set excluding the slave node S1 (namely the target set including S2, S3.....Sk), any slave node as the first slave node.

    [0041] In step S22, whether communication between the first slave node and the fault slave node is normal may be determined.

    [0042] In an embodiment of the present disclosure, if communication between the first slave node and the fault slave node is normal, that is, the first slave node may communicate normally with both master node and the fault slave node, the first slave node may be determined as the target slave node.

    [0043] In an embodiment of the present disclosure, since the failure slave node may maintain, within a preset time period, a frequency f at which abnormal communication with the master node occurs, the following situation may occur: communication between the master node and the selected first slave node is normal, however, the first slave node communicates abnormally with the fault slave node using the frequency f. In this case, the master node fails to transmit frequency conversion information to the fault slave node through the first slave node, causing that the master node fails to modify the frequency of the fault slave node. At this time, the first slave node may transmit to the master node a signal indicating that frequency conversion fails, then i=i-1, and the master node may reselect the first slave node.

    [0044] That is, if the first slave node communicates abnormally with at least one of the master node and the fault slave node, the master node may reselect the first slave node.

    [0045] In the above examples, if communication between the master node M and the slave node S1 is normal, and communication between the slave node S1 and the slave node So is normal, then the slave node S1 may be determined as the target slave node.

    [0046] If communication between the master node M and the slave node S1 is normal, and communication between the slave node S1 and the slave node So is abnormal, then the slave node S1 cannot be determined as the target slave node. The master node may reselect S2 as the first slave node among slave nodes excluding the slave node S0 and the slave node S1, that is, among nodes S2, S3, ... Sk.

    [0047] Then, the master node may continue to determine whether the updated first slave node, namely, the slave node S2, is able to communicate with the master node M normally. That is, the steps S20-S22 may be repeated until it is determined whether there is a target slave node among the slave nodes S1, S2 ... Sk.

    [0048] In an embodiment of the present disclosure, if the master node succeeds in selecting the target slave node from the plurality of slave nodes, then the master node may transmit the frequency conversion information to the target slave node. The frequency conversion information may be information determined by the master node based on a frequency table of the fault slave node, and the frequency conversion information may include a new frequency that the fault slave node needs to convert to. The target slave node may receive the frequency conversion information transmitted by the master node, and forward the frequency conversion information to the fault slave node.

    [0049] In an embodiment of the present disclosure, the master node may communicate with the target slave node using a certain frequency in a frequency table of the target slave node, so that the target slave node may receive the frequency conversion information transmitted by the master node. A frequency table of a node may include a plurality of frequencies at which the node can transmit information.

    [0050] In an embodiment of the present disclosure, the target slave node may communicate with the fault slave node using a frequency at which abnormal communication between the fault slave node and the master node occurs. The fault slave node may receive the frequency conversion information transmitted by the target slave node, and perform frequency conversion based on the frequency conversion information.

    [0051] A method for a fault slave node to perform frequency conversion based on frequency conversion information will be described in detail below in conjunction with an embodiment. Fig. 3 illustrates a method 300 for a fault slave node to perform frequency conversion based on frequency conversion information according to an embodiment of the present disclosure. The method may include the following steps.

    [0052] In step S30, the fault slave node may perform frequency conversion based on the received frequency conversion information.

    [0053] In an embodiment of the present disclosure, the frequency conversion information may include a frequency that the fault slave node needs to convert to, and the frequency may be any frequency among the frequency table of the fault slave node other than a frequency when abnormal communication between the fault slave node and the master node occurs.

    [0054] As an example, a frequency table of the slave node S0 above may include a frequency f0, a frequency f01,..., a frequency f0h, wherein h may be a positive integer. If abnormal communication occurs when the master node M and the slave node S0 transmit information at the frequency f0, it is determined that the fault slave node is the slave node S0. It may be assumed that the master node M selects, from the slave nodes except the slave node S0, the slave node S3 as the target slave node.

    [0055] The master node M may select, from frequencies in the frequency table of the slave node S0 except the frequency f0, the frequency f01 as a new frequency included in the frequency conversion information. The master node M may forward the frequency conversion information including the frequency f01 to the slave node S0 through the slave node S3. The slave node S0 may convert the frequency f0 to the frequency f01 based on the frequency conversion information.

    [0056] In step S31, the master node may determine whether communication between the master node and the fault slave node is normal.

    [0057] In the above examples, if the master node M successfully transmits information with the slave node S0 using the frequency f01, then the method may proceed to step S32.

    [0058] If the master node fails to transmit information with the slave node S0 using the frequency f01, then the method may proceed to step S33.

    [0059] In step S32, the master node may transmit the frequency conversion information to the slave nodes except the fault slave node.

    [0060] In the above examples, after the master node M successfully transmits information with the slave node S0 using the frequency f01, the master node M may transmit the frequency foi to the slave nodes S1, S2,.., Sk. The slave nodes S1, S2,.., Sk may receive and store the frequency f01.

    [0061] In step S33, the master node may update the frequency conversion information based on the frequency table of the fault slave node.

    [0062] In the above examples, if the master node fails to transmit information with the slave node S0 using the frequency f01, the master node may reselect any frequency from frequencies in the frequency table of the slave node S0 except the frequency f0 and the frequency f01, and may determine the reselected frequency as the new frequency included in the frequency conversion information, to update the frequency conversion information. That is, if the master node fails to transmit information with the slave node S0 using the frequency f01, the method may return to step S30 to determine whether there is a frequency in the frequency table of the slave node S0 that may enable information transmission between the master node M and the slave node S0 to be successful.

    [0063] When there is a frequency in the frequency table of the slave node S0 that may enable information transmission between the master node M and the slave node S0 to be successful, the master node may succeed in transmitting information with the fault slave node using a frequency after frequency conversion.

    [0064] Moreover, the fault slave node may forward a feedback signal indicating success to the master node through the target slave node, and the master node may transmit the frequency that enables information transmission between the master node M and the slave node So to be successful to all slave nodes among the plurality of slave nodes except the fault slave node.

    [0065] All slave nodes except the fault slave node may receive and store the frequency of the fault slave node after frequency conversion transmitted by the master node, to achieve subsequent communication among the slave nodes.

    [0066] In an embodiment of the present disclosure, the master node may change the frequency of the fault slave node by selecting a slave node that may communicate normally with both the master node and the fault slave node as a repeater, to achieve normal communication between the master node and the fault slave node. That is to say, the master node may automatically recover abnormal communication by utilizing slave nodes in the battery management system, thereby improving the reliability of wireless communication in the battery management system.

    [0067] When there is no frequency in the frequency table of the slave node S0 that may enable information transmission between the master node M and the slave node S0 to be successful, the master node may forward data between the master node and the fault slave node using the target slave node.

    [0068] Specifically, if the master node fails to transmit information with the fault slave node using the frequency after frequency conversion, application layer data of the fault slave node may be forwarded to the master node through the target slave node.

    [0069] In the case that the master node fails to transmit information with the fault slave node using the frequency of the fault slave node after frequency conversion, the data between the master node and the fault slave node may be forwarded by using the selected target slave node as a repeater, to ensure indirect communication between the master node and the fault slave node, thereby further improving the reliability of wireless communication in the battery management system.

    [0070] In an embodiment of the present disclosure, if the master node fails to receive a message transmitted by the fault slave node within a preset period, the master node may determine whether there is a target slave node in the plurality of slave nodes. If the master node fails to select the target slave node from the plurality of slave nodes (namely, the master node fails to communicate with any slave node), that is, there is no target slave node, the master node may perform a timed frequency hopping based on a preset frequency hopping rule, and may transmit information with the fault slave node using a frequency after the frequency hopping.

    [0071] The fault slave node may automatically enter the timed frequency hopping after a first preset time period. The frequency hopping rule of the fault slave node may be consistent with the frequency hopping rule of the master node. In order to avoid a time delay between the fault slave node and the master node in entering the timed frequency hopping, a value of the first preset time period needs to be set. Specifically, the value of the first preset time period may be set to a time period required to complete polling all slave nodes by the master node and to determine that the target slave node does not exist, so as to ensure that a frequency of the fault slave node after the timed frequency hopping is consistent with a frequency of the master node after the timed frequency hopping.

    [0072] In an embodiment of the present disclosure, if the master node determines that there is no target slave node in the plurality of slave nodes, the master node may perform a timed frequency hopping based on a preset frequency hopping rule. Correspondingly, the fault slave node may enter the timed frequency hopping almost simultaneously with the master node after the first preset time period. The preset frequency hopping rule may refer to a rule that the fault slave node converts its frequency at a fixed time interval based on a plurality of frequencies included in the frequency table of the fault slave node.

    [0073] After the master node and the fault slave node perform a first frequency hopping, the master node and the fault slave node may attempt to transmit information based on a frequency after the first frequency hopping.

    [0074] If information transmission between the master node and the fault slave node is successful, the master node may transmit the frequency after the frequency hopping to all slave nodes except the fault slave node.

    [0075] If information transmission between the master node and the fault slave node fails, the master node and the fault slave node may continue to perform a second frequency hopping, and the master node and the fault slave node may attempt to transmit information based on a frequency after the second frequency hopping.

    [0076] If information transmission between the master node and the fault slave node using the frequency after the second frequency hopping fails, the master node and the fault slave node may continue to perform a timed frequency hopping based on the preset frequency hopping rule, to determine whether there is a frequency for frequency hopping that may enable information transmission between the master node and the fault slave node to be successful within a range of the frequency table of the fault slave node.

    [0077] If there is no frequency for frequency hopping that may enable information transmission between the master node and the fault slave node to be successful within the range of the frequency table of the fault slave node, the communication failure of the fault slave node may be reported.

    [0078] In an embodiment of the present disclosure, before reporting a communication failure of the fault slave node, the frequency of the fault slave node may be changed using a selected target slave node, or data between the master node and the fault slave node may be forwarded through the target slave node, or the timed frequency hopping may be performed, so as to automatically recover normal communication between the master node and the fault slave node, thereby avoiding abnormal communication caused by factors such as external interference, a structural layout of nodes, etc., which improves the reliability of wireless communication.

    [0079] In some embodiments of the present disclosure, within a time range allowed by an application layer, data may be transmitted in divided packets by reducing a size of a transmitted frame, i.e., by dividing a data packet. Since a short data packet may have a higher reliability than a long data packet, therefore the reliability of wireless communication in the battery management system may be improved.

    [0080] As an example, Fig. 4 illustrates a schematic diagram of a result of dividing a data packet according to an embodiment of the present disclosure. The first row in Fig. 4 shows a format of a data packet to be transmitted, which may include a destination address, a source address, application layer data, and a check code of the data packet to be transmitted. The application layer data of the data packet to be transmitted may include n+1 bit data.

    [0081] The application layer data in the data packet to be transmitted in the first row in Fig. 4 may be divided into a first application layer data block in the second row and a second application layer data block in the third row.

    [0082] The first application layer data block in the second row may include the 1st bit data to the (m+1)th bit data in the n+1 bit data of the application layer data in the first row. The second application layer data block in the third row may include the (m+2)th bit data to the (n+1)th bit data in the n+1 bit data of the application layer data in the first row.

    [0083] Since the reliability of the short packets in the second row and the third row is higher than the reliability of the long packet in the first row, the reliability of wireless communication in the battery management system may be further improved.

    [0084] The embodiments of the present disclosure does not specifically limit the dividing manner of the data packet, and the data packet may be divided into data packets of different numbers depending on an actual data length.

    [0085] In some embodiments of the present disclosure, during transmission of data in the battery management system, a data verification mechanism may be provided at a transmitting end and a receiving end of the data. The receiving end of the data may use a preset verification mechanism to verify the received data. If the verification result is a verification failure, a feedback signal indicating the verification failure may be transmitted to the transmitting end, so that the transmitting end may perform data retransmission, that is, may retransmit the data to the receiving end.

    [0086] In an embodiment of the present disclosure, data retransmission may ensure the integrity and correctness of data transmission, thereby further improving the reliability of wireless communication in the battery management system.

    [0087] Based on the above process, a method for wirelessly transmitting information in the battery management system applied to a master node side according to an embodiment of the present disclosure may be summarized as the steps shown in Fig. 5. Fig. 5 illustrates a schematic flow chart of a method 500 for transmitting information in a battery management system applied to a master node side according to an embodiment of the present disclosure. As shown in Fig. 5, the method for wirelessly transmitting information in the battery management system according to an embodiment of the present disclosure may include the following steps.

    [0088] In step S510, a fault slave node that communicates abnormally with a master node in the battery management system may be determined from a plurality of slave nodes.

    [0089] In step S520, a target slave node may be selected from the plurality of slave nodes, wherein the target slave node may be a slave node that may communicate normally with both the master node and the fault slave node.

    [0090] In step S530, frequency conversion information may be transmitted to the target slave node, so that the target slave node may forward the frequency conversion information to the fault slave node, and the fault slave node may perform a frequency conversion based on the frequency conversion information.

    [0091] In step S540, a frequency after the frequency conversion may be used to transmit information with the fault slave node.

    [0092] In an embodiment of the present disclosure, step S520 may include the following steps.

    [0093] In step S5201, any slave node other than the fault slave node may be selected from the plurality of slave nodes as a first slave node.

    [0094] In step S5202, the first slave node may be determined as the target slave node, if the first slave node may communicate normally with both the master node and the fault slave node. The first slave node may be reselected if the first slave node communicates abnormally with at least one of the master node and the fault slave node.

    [0095] In some embodiments of the present disclosure, if transmission of information with the fault slave node using the frequency after the frequency conversion is successful, the method for transmitting information in the battery management system may further include the following step.

    [0096] In step S550, the frequency after the frequency conversion may be transmitted to all slave nodes of the plurality of slave nodes except the fault slave node.

    [0097] In some embodiments of the present disclosure, if transmission of information with the fault slave node using the frequency after the frequency conversion fails, the method for transmitting information in the battery management system may further includes the following step.

    [0098] In step S560, data between the master node and the fault slave node may be forwarded using the target slave node.

    [0099] In some embodiments of the present disclosure, if the target slave node fails to be selected from the plurality of slave nodes, the method for transmitting information in the battery management system may further include the following step.

    [0100] In step S570, a timed frequency hopping may be performed based on a preset frequency hopping rule, and a frequency after the frequency hopping may be used to transmit information with the fault slave node.

    [0101] The frequency after the frequency hopping is consistent with a frequency of the fault slave node after a timed frequency hopping based on the preset frequency hopping rule.

    [0102] Based on the above process, a method for transmitting information in the battery management system applied to a target slave node side according to an embodiment of the present disclosure may be summarized as the steps shown in Fig. 6. Fig. 6 illustrates a schematic flow chart of a method 600 for transmitting information in a battery management system applied to a target slave node side according to an embodiment of the present disclosure. As shown in Fig. 6, the method for transmitting information in the battery management system according to an embodiment of the present disclosure may include the following steps.

    [0103] In step S610, frequency conversion information transmitted by a master node in the battery management system may be received.

    [0104] In step S620, the frequency conversion information may be forwarded to a fault slave node, so that the fault slave node may perform a frequency conversion based on the frequency conversion information, and the master node may transmit information with the fault slave node using the frequency after the frequency conversion.

    [0105] The fault slave node may be a slave node, determined by the master node from a plurality of slave nodes, that communicates abnormally with the master node.

    [0106] In some embodiments of the present disclosure, if the master node successfully transmits information with the fault slave node using the frequency after the frequency conversion, the method for transmitting information in the battery management system may further include the following step.

    [0107] In step S630, the frequency after the frequency conversion transmitted by the master node may be received and stored.

    [0108] In some embodiments of the present disclosure, if the master node fails to transmit information with the fault slave node using the frequency after the frequency conversion, the method for transmitting information in the battery management system may further include the following step.

    [0109] In step S640, data between the master node and the fault slave node may be forwarded.

    [0110] Based on the above process, a method for transmitting information in the battery management system applied to a fault slave node side according to an embodiment of the present disclosure may be summarized as the steps shown in Fig. 7. Fig. 7 illustrates a schematic flow chart of a method 700 for transmitting information in a battery management system applied to a fault slave node side according to an embodiment of the present disclosure. As shown in Fig. 7, the method for transmitting information in the battery management system according to an embodiment of the present disclosure may include the following steps.

    [0111] In step S710, frequency conversion information transmitted by a target slave node may be received, wherein the target slave node may be a slave node selected from a plurality of slave nodes by a master node in the battery management system, and the target slave node may be a slave node that may communicates normally with both the master node and a fault slave node, and wherein the fault slave node may be a slave node, determined by the master node from the plurality of slave nodes, that communicates abnormally with the master node.

    [0112] In step S720, a frequency conversion may be performed based on the frequency conversion information, so that the master node may use the frequency after the frequency conversion to transmit information with the fault slave node.

    [0113] In some embodiments of the present disclosure, if the master node fails to transmit information with the fault slave node using the frequency after the frequency conversion, the method for transmitting information in the battery management system may further include the following step.

    [0114] In step S730, data between the master node and the fault slave node may be forwarded using the target slave node.

    [0115] In some embodiments of the present disclosure, if the master node fails to select the target slave node from the plurality of slave nodes, the method for transmitting information in the battery management system may further include the following step.

    [0116] In step S740, a timed frequency hopping may be performed based on a preset frequency hopping rule within a preset time period, and a frequency after the frequency hopping may be used to transmit information with the master node.

    [0117] The frequency after the frequency hopping is consistent with a frequency of the master node after a timed frequency hopping based on the preset frequency hopping rule.

    [0118] In the method for transmitting information in a battery management system according to an embodiment of the present disclosure, by using a selected target slave node as a repeater, frequency conversion may be achieved or data between the master node and the fault slave node may be forwarded, thereby automatically recovering communication between the master node and the fault slave node, which may improve the reliability of communication in the battery management system.

    [0119] It should be noted that, in an embodiment of the present disclosure, the number of fault slave nodes may be one or more. The number of fault slave nodes may be less than or equal to the number of slave nodes in the battery management system. When the number of fault slave nodes is more than one, the method for transmitting information in the battery management system according to an embodiment of the present disclosure may be used to select a target slave node for each fault slave node, so that the master node may recover communication with the fault slave node through the target slave node, thereby improving the reliability of wireless communication in the battery management system.

    [0120] Fig. 8 illustrates a schematic structural diagram of an apparatus 800 for transmitting information in a battery management system according to an embodiment of the present disclosure. The apparatus in Fig. 8 may perform the method in Fig. 5, and the apparatus may include: a fault slave node determination module 810 configured to determine, from a plurality of slave nodes, a fault slave node that communicates abnormally with a master node in the battery management system; a target slave node selection module 820 configured to select a target slave node from the plurality of slave nodes, wherein the target slave node may be a slave node that may communicate normally with both the master node and the fault slave node; a first transmission module 830 configured to transmit frequency conversion information to the target slave node, so that the target slave node may forward the frequency conversion information to the fault slave node, and the fault slave node may perform a frequency conversion based on the frequency conversion information; and an information transmission module 840 configured to transmit information with the fault slave node using a frequency after the frequency conversion.

    [0121] Fig. 9 illustrates a schematic structural diagram of an apparatus 900 for transmitting information in a battery management system according to an embodiment of the present disclosure. The apparatus in Fig. 9 may perform the method in Fig. 6, and the apparatus may include: a first reception module 910 configured to receive frequency conversion information transmitted by a master node in the battery management system; and a second transmission module 920 configured to forward the frequency conversion information to a fault slave node, so that the fault slave node may perform a frequency conversion based on the frequency conversion information, and the master node may transmit information with the fault slave node using the frequency after the frequency conversion, wherein the fault slave node may be a slave node, determined by the master node from a plurality of slave nodes, that communicates abnormally with the master node.

    [0122] Fig. 10 illustrates a schematic structural diagram of an apparatus 1000 for transmitting information in a battery management system according to an embodiment of the present disclosure. The apparatus in Fig. 10 may perform the method in Fig. 7, and the apparatus may include: a second reception module 1010 configured to receive frequency conversion information transmitted by a target slave node, wherein the target slave node may be a slave node selected from a plurality of slave nodes by a master node in the battery management system, and the target slave node may be a slave node that may communicate normally with both the master node and a fault slave node, and wherein the fault slave node may be a slave node, determined by the master node from the plurality of slave nodes, that communicates abnormally with the master node; and a frequency conversion module 1020 configured to perform a frequency conversion based on the frequency conversion information, so that the master node may use the frequency after the frequency conversion to transmit information with the fault slave node.

    [0123] In the apparatus for transmitting information in the battery management system according to an embodiment of the present disclosure, the master node may transmit frequency conversion information to the fault slave node by using a selected target slave node, so that the fault slave node may perform frequency conversion based on the frequency conversion information, and thus the master node may recover communication with the fault slave node using a frequency after the frequency conversion, thereby improving the reliability of wireless communication in the battery management system.

    [0124] Other details of the apparatus for transmitting information in the battery management system according to an embodiment of the present disclosure are similar to those of the method for transmitting information in the battery management system according to an embodiment of the present disclosure described above with reference to Figs. 5 to 7, which will not be described herein again.

    [0125] It should also be noted that the exemplary embodiments mentioned in the present disclosure describe some methods or systems based on a series of steps or devices. However, the present disclosure is not limited to the order of the above steps, that is, the steps may be performed in the order mentioned in the embodiments, or may be performed in an order different from the order in the embodiments, or several steps may be performed simultaneously.

    [0126] The description above only refers to specific implementations of the present disclosure, and those skilled in the art can clearly understand that for the convenience and brevity of the description, specific operating processes of systems, modules and units described above can refer to corresponding processes in the foregoing method embodiments, which will not be repeated here. It should be understood that the scope of the present disclosure is not limited thereto, and various equivalent modifications or substitutions may be easily conceived by those skilled in the art within the scope of the present disclosure. Those modifications or substitutions should be covered by the scope of the present disclosure.


    Claims

    1. A method (500) for transmitting information in a battery management system (100), characterized by comprising:

    determining (S510), from a plurality of slave nodes (S0, S1, S2, Sk), a fault slave node that communicates abnormally with a master node (M) in the battery management system (100);

    selecting (S520) a target slave node from the plurality of slave nodes (S0, S1, S2, Sk), wherein the target slave node is a slave node that communicates normally with both the master node (M) and the fault slave node;

    transmitting (S530) frequency conversion information to the target slave node, so that the target slave node forwards the frequency conversion information to the fault slave node, and the fault slave node performs a frequency conversion based on the frequency conversion information; and

    transmitting (S540) information with the fault slave node using a frequency after the frequency conversion.


     
    2. The method (500) of claim 1, wherein the selecting (S520) a target slave node from the plurality of slave nodes (S0, S1, S2, Sk) comprises:

    selecting, from the plurality of slave nodes (S0, S1, S2, Sk), any slave node other than the fault slave node as a first slave node;

    determining the first slave node as the target slave node, if the first slave node communicates normally with both the master node (M) and the fault slave node; and

    reselecting the first slave node if the first slave node communicates abnormally with at least one of the master node (M) and the fault slave node.


     
    3. The method (500) of claim 1, wherein if transmission of information with the fault slave node using the frequency after the frequency conversion is successful, the method (500) further comprises:
    transmitting the frequency after the frequency conversion to all slave nodes of the plurality of slave nodes (S0, S1, S2, Sk) except the fault slave node.
     
    4. The method (500) of claim 1, wherein if transmission of information with the fault slave node using the frequency after the frequency conversion fails, the method (500) further comprises:
    forwarding data between the master node (M) and the fault slave node using the target slave node.
     
    5. The method (500) of claim 1, wherein the method (500) further comprises:

    determining that no target slave node is selected from the plurality of slave nodes (S0, S1, S2, Sk);

    performing a timed frequency hopping based on a preset frequency hopping rule, and transmitting information with the fault slave node using a frequency after the frequency hopping,

    wherein the frequency after the frequency hopping is consistent with a frequency of the fault slave node after a timed frequency hopping based on the preset frequency hopping rule.


     
    6. A method (600) for transmitting information in a battery management system (100), characterized by comprising:

    receiving (S610) frequency conversion information transmitted by a master node (M) in the battery management system (100);

    forwarding (S620) the frequency conversion information to a fault slave node, so that the fault slave node performs a frequency conversion based on the frequency conversion information, and the master node (M) transmits information with the fault slave node using the frequency after the frequency conversion,

    wherein the fault slave node is a slave node, determined by the master node (M) from a plurality of slave nodes (S0, S1, S2, Sk), that communicates abnormally with the master node (M).


     
    7. The method (600) of claim 6, wherein if the master node (M) successfully transmits information with the fault slave node using the frequency after the frequency conversion, the method (600) further comprises:
    receiving and storing the frequency after the frequency conversion transmitted by the master node (M).
     
    8. The method (600) of claim 6, wherein if the master node (M) fails to transmit information with the fault slave node using the frequency after the frequency conversion, the method (600) further comprises:
    forwarding data between the master node (M) and the fault slave node.
     
    9. A method (700) for transmitting information in a battery management system (100), characterized by comprising:

    receiving (S710) frequency conversion information transmitted by a target slave node, wherein the target slave node is a slave node selected from a plurality of slave nodes (S0, S1, S2, Sk) by a master node (M) in the battery management system (100), and the target slave node is a slave node that communicates normally with both the master node (M) and a fault slave node, and wherein the fault slave node is a slave node, determined by the master node (M) from the plurality of slave nodes (S0, S1, S2, Sk), that communicates abnormally with the master node (M); and

    performing (S720) a frequency conversion based on the frequency conversion information, so that the master node (M) uses a frequency after the frequency conversion to transmit information with the fault slave node.


     
    10. The method (700) of claim 9, wherein if the master node (M) fails to transmit information with the fault slave node using the frequency after the frequency conversion, the method (700) further comprises:
    forwarding data between the master node (M) and the fault slave node using the target slave node.
     
    11. The method (700) of claim 9, wherein if the master node (M) fails to select the target slave node from the plurality of slave nodes (S0, S1, S2, Sk), the method (700) further comprises:

    performing a timed frequency hopping based on a preset frequency hopping rule within a preset time period, and transmitting information with the master node (M) using a frequency after the frequency hopping,

    wherein the frequency after the frequency hopping is consistent with a frequency of the master node (M) after a timed frequency hopping based on the preset frequency hopping rule.


     
    12. An apparatus (800) for transmitting information in a battery management system (100), characterized by comprising:

    a fault slave node determination module (810) configured to determine, from a plurality of slave nodes (S0, S1, S2, Sk), a fault slave node that communicates abnormally with a master node (M) in the battery management system (100);

    a target slave node selection module (820) configured to select a target slave node from the plurality of slave nodes (S0, S1, S2, Sk), wherein the target slave node is a slave node that communicates normally with both the master node (M) and the fault slave node;

    a first transmission module (830) configured to transmit frequency conversion information to the target slave node, so that the target slave node forwards the frequency conversion information to the fault slave node, and the fault slave node performs a frequency conversion based on the frequency conversion information; and

    an information transmission module (840) configured to transmit information with the fault slave node using a frequency after the frequency conversion.


     
    13. An apparatus (900) for transmitting information in a battery management system (100), characterized by comprising:

    a first reception module (910) configured to receive frequency conversion information transmitted by a master node (M) in the battery management system (100); and

    a second transmission module (920) configured to forward the frequency conversion information to a fault slave node, so that the fault slave node performs a frequency conversion based on the frequency conversion information, and the master node (M) transmits information with the fault slave node using a frequency after the frequency conversion,

    wherein the fault slave node is a slave node, determined by the master node (M) from a plurality of slave nodes (S0, S1, S2, Sk), that communicates abnormally with the master node (M).


     
    14. An apparatus (1000) for transmitting information in a battery management system (100), characterized by comprising:

    a second reception module (1010) configured to receive frequency conversion information transmitted by a target slave node, wherein the target slave node is a slave node selected from a plurality of slave nodes (S0, S1, S2, Sk) by a master node (M) in the battery management system (100), and the target slave node is a slave node that communicates normally with both the master node (M) and a fault slave node, and wherein the fault slave node is a slave node, determined by the master node (M) from the plurality of slave nodes (S0, S1, S2, Sk), that communicates abnormally with the master node (M); and

    a frequency conversion module (1020) configured to perform a frequency conversion based on the frequency conversion information, so that the master node (M) uses a frequency after the frequency conversion to transmit information with the fault slave node.


     
    15. A battery management system (100), characterized by comprising the apparatus (800) for transmitting information in a battery management system (100) according to claim 12, the apparatus (900) for transmitting information in a battery management system (100) according to claim 13, and the apparatus (1000) for transmitting information in a battery management system (100) according to claim 14.
     


    Ansprüche

    1. Verfahren (500) zum Übertragen von Informationen in einem Batteriemanagementsystem (100), dadurch gekennzeichnet, dass es umfasst:

    Bestimmen (S510) eines ausgefallenen Slave-Knotens aus mehreren Slave-Knoten (S0, S1, S2, Sk), der mit einem Master-Knoten (M) in dem Batteriemanagementsystem (100) abnormal kommuniziert;

    Auswählen (S520) eines Ziel-Slave-Knotens aus mehreren Slave-Knoten (S0, S1, S2, Sk), wobei der Ziel-Slave-Knoten ein sowohl mit dem Master-Knoten (M) als auch mit dem ausgefallenen Slave-Knoten normal kommunizierter Slave-Knoten ist;

    Übertragen (S530) von Frequenzumwandlungsinformationen an den Ziel-Slave-Knoten, so dass der Ziel-Slave-Knoten die Frequenzumwandlungsinformationen an den ausgefallenen Slave-Knoten weiterleitet und der ausgefallene Slave-Knoten eine Frequenzumwandlung basierend auf den Frequenzumwandlungsinformationen durchführt; und

    Übertragen (S540) von Informationen mit dem ausgefallenen Slave-Knoten unter Verwendung einer Frequenz nach der Frequenzumwandlung.


     
    2. Verfahren (500) nach Anspruch 1, wobei das Auswählen (S520) eines Ziel-Slave-Knotens aus mehreren Slave-Knoten (S0, S1, S2, Sk) umfasst:

    Auswählen eines anderen Slave-Knotens mit Ausnahme des ausgefallenen Slave-Knotens aus mehreren Slave-Knoten (S0, S1, S2, Sk) als ersten Slave-Knoten;

    Bestimmen des ersten Slave-Knotens als Ziel-Slave-Knoten, wenn der erste Slave-Knoten sowohl mit dem Master-Knoten (M) als auch mit dem ausgefallenen Slave-Knoten normal kommuniziert; und

    erneutes Auswählen des ersten Slave-Knotens, wenn der erste Slave-Knoten mit mindestens einem von dem Master-Knoten (M) und dem ausgefallenen Slave-Knoten abnormal kommuniziert.


     
    3. Verfahren (500) nach Anspruch 1, wobei, wenn das Übertragen von Informationen mit dem ausgefallenen Slave-Knoten unter Verwendung der Frequenz nach der Frequenzumwandlung erfolgreich ist, das Verfahren (500) ferner umfasst:
    Übertragen der Frequenz nach der Frequenzumwandlung an alle Slave-Knoten mehrerer Slave-Knoten (S0, S1, S2, Sk) mit Ausnahme des ausgefallenen Slave-Knotens.
     
    4. Verfahren (500) nach Anspruch 1, wobei, wenn das Übertragen von Informationen mit dem ausgefallenen Slave-Knoten unter Verwendung der Frequenz nach der Frequenzumwandlung ausfällt, das Verfahren (500) ferner umfasst:
    Weiterleiten von Daten zwischen dem Master-Knoten (M) und dem ausgefallenen Slave-Knoten unter Verwendung des Ziel-Slave-Knotens.
     
    5. Verfahren (500) nach Anspruch 1, wobei das Verfahren (500) ferner umfasst:

    Bestimmen, dass kein Ziel-Slave-Knoten aus mehrerer Slave-Knoten (S0, S1, S2, Sk) ausgewählt ist;

    Durchführen eines zeitgesteuerten Frequenzsprungs basierend auf einer voreingestellten Frequenzsprungregel und Übertragen von Informationen mit dem ausgefallenen Slave-Knoten unter Verwendung einer Frequenz nach dem Frequenzsprung;

    wobei die Frequenz nach dem Frequenzsprung mit einer Frequenz des ausgefallenen Slave-Knotens nach einem zeitgesteuerten Frequenzsprung basierend auf der voreingestellten Frequenzsprungregel übereinstimmt.


     
    6. Verfahren (600) zum Übertragen von Informationen in einem Batteriemanagementsystem (100), gekennzeichnet durch, dass es umfasst:

    Empfangen (S610) von Frequenzumwandlungsinformationen, die von einem Master-Knoten (M) in dem Batteriemanagementsystem (100) gesendet wurden;

    Weiterleiten (S620) der Frequenzumwandlungsinformationen an einen ausgefallenen Slave-Knoten, so dass der ausgefallene Slave-Knoten eine Frequenzumwandlung basierend auf den Frequenzumwandlungsinformationen durchführt und der Master-Knoten (M) Informationen mit dem ausgefallenen Slave-Knoten unter Verwendung der Frequenz nach der Frequenzumwandlung übertragt,

    wobei der ausgefallene Slave-Knoten ein durch den Master-Knoten (M) aus mehreren Slave-Knoten (S0, S1, S2, Sk) bestimmter Slave-Knoten ist, der mit dem Master-Knoten (M) abnormal kommuniziert.


     
    7. Verfahren (600) nach Anspruch 6, wobei, wenn der Master-Knoten (M) Informationen mit dem ausgefallenen Slave-Knoten unter Verwendung der Frequenz nach der Frequenzumwandlung erfolgreich überträgt, das Verfahren (600) ferner umfasst:
    Empfangen und Speichern von der Frequenz nach der vom Master-Knoten (M) gesendeten Frequenzumwandlung.
     
    8. Verfahren (600) nach Anspruch 6, wobei, wenn das übertragen von Informationen durch den Master-Knoten (M) mit dem ausgefallenen Slave-Knoten unter Verwendung der Frequenz nach der Frequenzumwandlung ausfällt, das Verfahren (600) ferner umfasst:
    Weiterleiten von Daten zwischen dem Master-Knoten (M) und dem ausgefallenen Slave-Knoten.
     
    9. Verfahren (700) zum Übertragen von Informationen in einem Batteriemanagementsystem (100), gekennzeichnet durch, dass es umfasst:

    Empfangen (S710) von Frequenzumwandlungsinformationen, die von einem Ziel-Slave-Knoten gesendet wurden, wobei der Ziel-Slave-Knoten ein durch einen Master-Knoten (M) im Batteriemanagementsystem (100) aus mehreren Slave-Knoten (S0, S1, S2, Sk) ausgewählter Slave-Knoten ist, und der Ziel-Slave-Knoten ein sowohl mit dem Master-Knoten (M) als auch mit einem ausgefallenen Slave-Knoten normal kommunizierter Slave-Knoten ist, und wobei der ausgefallene Slave-Knoten ein durch den Master-Knoten (M) aus mehreren Slave-Knoten (S0, S1, S2, Sk) bestimmter Slave-Knoten ist, die mit dem Master-Knoten (M) abnormal kommuniziert; und

    Durchführen (S720) einer Frequenzumwandlung basierend auf den Frequenzumwandlungsinformationen, so dass der Master-Knoten (M) eine Frequenz nach der Frequenzumwandlung verwendet, um Informationen mit dem ausgefallenen Slave-Knoten zu übertragen.


     
    10. Verfahren (700) nach Anspruch 9, wobei, wenn das Übertragen von Informationen durch den Master-Knoten (M) mit dem ausgefallenen Slave-Knoten unter Verwendung der Frequenz nach der Frequenzumwandlung ausfällt, das Verfahren (700) ferner umfasst:
    Weiterleiten von Daten zwischen dem Master-Knoten (M) und dem ausgefallenen Slave-Knoten unter Verwendung des Ziel-Slave-Knotens.
     
    11. Verfahren (700) nach Anspruch 9, wobei, wenn das Auswählen vom Ziel-Slave-Knoten durch den Master-Knoten (M) aus mehreren Slave-Knoten (S0, S1, S2, Sk) ausfällt, das Verfahren (700) ferner umfasst:

    Durchführen eines zeitgesteuerten Frequenzsprungs basierend auf einer voreingestellten Frequenzsprungregel innerhalb eines voreingestellten Zeitraums und Übertragen von Informationen mit dem Master-Knoten (M) unter Verwendung einer Frequenz nach dem Frequenzsprung;

    wobei die Frequenz nach dem Frequenzsprung mit einer Frequenz des Master-Knotens (M) nach einem zeitgesteuerten Frequenzsprung basierend auf der voreingestellten Frequenzsprungregel übereinstimmt.


     
    12. Vorrichtung (800) zum Übertragen von Informationen in einem Batteriemanagementsystem (100), gekennzeichnet durch, dass es umfasst:

    ein Ausgefallenes-Slave-Knoten-Bestimmungsmodul (810), das dazu konfiguriert ist, einen ausgefallenen Slave-Knoten aus mehreren Slave-Knoten (S0, S1, S2, Sk) zu bestimmen, der mit einem Master-Knoten (M) in dem Batteriemanagementsystem (100) abnormal kommuniziert; ein Ziel-Slave-Knoten-Auswahlmodul (820), das dazu konfiguriert ist, einen Ziel-Slave-Knoten aus mehreren Slave-Knoten (S0, S1, S2, Sk) auszuwählen, wobei der Ziel-Slave-Knoten ein sowohl mit dem Master-Knoten (M) und als auch mit dem ausgefallenen Slave-Knoten normal kommunizierter Slave-Knoten ist;

    ein erstes übertragungsmodul (830), das dazu konfiguriert ist, Frequenzumwandlungsinformationen an den Ziel-Slave-Knoten zu übertragen, so dass der Ziel-Slave-Knoten die Frequenzumwandlungsinformationen an den ausgefallenen Slave-Knoten weiterleitet und der ausgefallene Slave-Knoten eine Frequenzumwandlung basierend auf den Frequenzumwandlungsinformationen durchführt; und

    ein Informationsübertragungsmodul (840), das dazu konfiguriert ist, Informationen mit dem ausgefallenen Slave-Knoten unter Verwendung einer Frequenz nach der Frequenzumwandlung zu übertragen.


     
    13. Vorrichtung (900) zum Übertragen von Informationen in einem Batteriemanagementsystem (100), gekennzeichnet durch, dass es umfasst:

    ein erstes Empfangsmodul (910), das dazu konfiguriert ist, Frequenzumwandlungsinformationen zu empfangen, die von einem Master-Knoten (M) in dem Batteriemanagementsystem (100) gesendet wurden; und

    ein zweites übertragungsmodul (920), das dazu konfiguriert ist, die Frequenzumwandlungsinformationen an einen ausgefallenen Slave-Knoten weiterzuleiten, so dass der ausgefallene Slave-Knoten eine Frequenzumwandlung basierend auf den Frequenzumwandlungsinformationen durchführt und der Master-Knoten (M) Informationen mit dem ausgefallenen Slave-Knoten unter Verwendung einer Frequenz nach der Frequenzumwandlung überträgt,

    wobei der ausgefallene Slave-Knoten ein durch den Master-Knoten (M) aus mehreren Slave-Knoten (S0, S1, S2, Sk) bestimmter Slave-Knoten ist, der mit dem Master-Knoten (M) abnormal kommuniziert.


     
    14. Vorrichtung (1000) zum Übertragen von Informationen in einem Batteriemanagementsystem (100), gekennzeichnet durch, dass es umfasst:

    ein zweites Empfangsmodul (1010), das dazu konfiguriert ist, Frequenzumwandlungsinformationen zu empfangen, die von einem Ziel-Slave-Knoten gesendet wurden, wobei der Ziel-Slave-Knoten ein durch einen Master-Knoten (M) in dem Batteriemanagementsystem (100) aus mehreren Slave-Knoten (S0, S1, S2, Sk) ausgewählter Slave-Knoten ist, und der Ziel-Slave-Knoten ist ein sowohl mit dem Master-Knoten (M) als auch mit einem ausgefallenen Slave-Knoten normal kommunizierter Slave-Knoten, wobei der ausgefallene Slave-Knoten ein durch den Master-Knoten (M) aus mehreren Slave-Knoten (S0, S1, S2, Sk) bestimmter Slave-Knoten ist, der mit dem Master-Knoten (M) abnormal kommuniziert; und

    ein Frequenzumwandlungsmodul (1020), das dazu konfiguriert ist, eine Frequenzumwandlung basierend auf den Frequenzumwandlungsinformationen durchzuführen, so dass der Master-Knoten (M) eine Frequenz nach der Frequenzumwandlung verwendet, um Informationen mit dem ausgefallenen Slave-Knoten zu übertragen.


     
    15. Batteriemanagementsystem (100), gekennzeichnet durch, dass es umfasst: die Vorrichtung (800) zum Übertragen von Informationen in einem Batteriemanagementsystem (100) nach Anspruch 12, die Vorrichtung (900) zum Übertragen von Informationen in einem Batteriemanagementsystem (100) nach Anspruch 13 und die Vorrichtung (1000) zum Übertragen von Informationen in einem Batteriemanagementsystem (100) nach Anspruch 14.
     


    Revendications

    1. Procédé (500) de transmission d'informations dans un système de gestion de batterie (100), caractérisé en ce qu'il comprend :

    la détermination (S510), parmi une pluralité de nœuds esclaves (S0, S1, S2, Sk), d'un nœud esclave par défaut qui communique de façon anormale avec un nœud maître (M) dans le système de gestion de batterie (100) ;

    la sélection (S520) d'un nœud esclave cible parmi la pluralité de nœuds esclaves (S0, S1, S2, Sk), le nœud esclave cible étant un nœud esclave qui communique normalement avec à la fois le nœud maître (M) et le nœud esclave par défaut ;

    la transmission (S530) d'informations de conversion de fréquence au nœud esclave cible, de telle sorte que le nœud esclave cible transfère les informations de conversion de fréquence au nœud esclave par défaut, et le nœud esclave par défaut réalise une conversion de fréquence basée sur les informations de conversion de fréquence ; et

    la transmission (S540) d'informations avec le nœud esclave par défaut à l'aide d'une fréquence après la conversion de fréquence.


     
    2. Procédé (500) selon la revendication 1, dans lequel la sélection (S520) d'un nœud esclave cible parmi la pluralité de nœuds esclaves (S0, S1, S2, Sk) comprend :

    la sélection, parmi la pluralité de nœuds esclaves (S0, S1, S2, Sk), de n'importe quel nœud esclave autre que le nœud esclave par défaut comme premier nœud esclave ;

    la détermination du premier nœud esclave comme nœud esclave cible, si le premier nœud esclave communique normalement avec à la fois le nœud maître (M) et le nœud esclave par défaut ; et

    la sélection à nouveau du premier nœud esclave si le premier nœud esclave communique de façon anormale avec au moins le nœud maître (M) et/ou le nœud esclave par défaut.


     
    3. Procédé (500) selon la revendication 1, le procédé (500) comprenant en outre, si la transmission d'informations avec le nœud esclave par défaut à l'aide de la fréquence après la conversion de fréquence réussit :
    la transmission de la fréquence après la conversion de fréquence à tous les nœuds esclaves de la pluralité de nœuds esclaves (S0, S1, S2, Sk) à l'exception du nœud esclave par défaut.
     
    4. Procédé (500) selon la revendication 1, le procédé (500) comprenant en outre, si la transmission d'informations avec le nœud esclave par défaut à l'aide de la fréquence après la conversion de fréquence échoue :
    le transfert de données entre le nœud maître (M) et le nœud esclave par défaut à l'aide du nœud esclave cible.
     
    5. Procédé (500) selon la revendication 1, le procédé (500) comprenant en outre :

    la détermination qu'aucun nœud esclave cible n'est sélectionné parmi la pluralité de nœuds esclaves (S0, S1, S2, Sk) ;

    la réalisation d'un saut de fréquence temporisé sur la base d'une règle de saut de fréquence prédéfinie, et la transmission d'informations avec le nœud esclave par défaut à l'aide d'une fréquence après le saut de fréquence,

    dans lequel la fréquence après le saut de fréquence est cohérente avec une fréquence du nœud esclave par défaut après un saut de fréquence temporisé sur la base de la règle de saut de fréquence prédéfinie.


     
    6. Procédé (600) de transmission d'informations dans un système de gestion de batterie (100), caractérisé en ce qu'il comprend :

    la réception (S610) d'informations de conversion de fréquence transmises par un nœud maître (M) dans le système de gestion de batterie (100) ;

    le transfert (S620) des informations de conversion de fréquence à un nœud esclave par défaut, de telle sorte que le nœud esclave par défaut réalise une conversion de fréquence basée sur les informations de conversion de fréquence, et le nœud maître (M) transmette des informations avec le nœud esclave par défaut à l'aide de la fréquence après la conversion de fréquence,

    dans lequel le nœud esclave par défaut est un nœud esclave, déterminé par le nœud maître (M) parmi une pluralité de nœuds esclaves (S0, S1, S2, Sk), qui communique de façon anormale avec le nœud maître (M).


     
    7. Procédé (600) selon la revendication 6, le procédé (600) comprenant en outre, si le nœud maître (M) transmet avec succès des informations avec le nœud esclave par défaut à l'aide de la fréquence après la conversion de fréquence :
    la réception et le stockage de la fréquence après la conversion de fréquence transmise par le nœud maître (M).
     
    8. Procédé (600) selon la revendication 6, le procédé (600) comprenant en outre, si le nœud maître (M) ne transmet pas avec succès d'informations avec le nœud esclave par défaut au moyen de la fréquence après la conversion de fréquence :
    le transfert de données entre le nœud maître (M) et le nœud esclave par défaut.
     
    9. Procédé (700) de transmission d'informations dans un système de gestion de batterie (100), caractérisé en ce qu'il comprend :

    la réception (S710) d'informations de conversion de fréquence transmises par un nœud esclave cible, le nœud esclave cible étant un nœud esclave sélectionné parmi une pluralité de nœuds esclaves ((S0, S1, S2, Sk) par un nœud maître (M) dans le système de gestion de batterie (100), et le nœud esclave cible étant un nœud esclave qui communique normalement avec à la fois le nœud maître (M) et un nœud esclave par défaut, et le nœud esclave par défaut étant un nœud esclave , déterminé par le nœud maître (M) parmi la pluralité de nœuds esclaves (S0, S1, S2, Sk), qui communique de façon anormale avec le nœud maître (M) ; et

    la réalisation (S720) d'une conversion de fréquence basée sur les informations de conversion de fréquence, de telle sorte que le nœud maître (M) utilise une fréquence après la conversion de fréquence pour transmettre des informations avec le nœud esclave par défaut.


     
    10. Procédé (700) selon la revendication 9, le procédé (700) comprenant en outre, si le nœud maître (M) ne transmet pas avec succès d'informations avec le nœud esclave par défaut à l'aide de la fréquence après la conversion de fréquence :
    le transfert de données entre le nœud maître (M) et le nœud esclave par défaut à l'aide du nœud esclave cible.
     
    11. Procédé (700) selon la revendication 9, le procédé (700) comprenant en outre, si le nœud maître (M) ne sélectionne pas le nœud esclave cible parmi la pluralité de nœuds esclaves (S0, S1, S2, Sk) ;
    la réalisation d'un saut de fréquence temporisé basé sur une règle de saut de fréquence prédéfinie dans une période de temps prédéfinie, et la transmission d'informations avec le nœud maître (M) à l'aide d'une fréquence après le saut de fréquence,
    dans lequel la fréquence après le saut de fréquence est cohérente avec une fréquence du nœud maître (M) après un saut de fréquence temporisé basé sur la règle de saut de fréquence prédéfinie.
     
    12. Appareil (800) de transmission d'informations dans un système de gestion de batterie (100), caractérisé en ce qu'il comprend :

    un moyen de détermination de nœud esclave par défaut (810) configuré pour déterminer, parmi une pluralité de nœuds esclaves (S0, S1, S2, Sk), un nœud esclave par défaut qui communique de façon anormale avec un nœud maître (M) dans le système de gestion de batterie (100) ;

    un module de sélection de nœud esclave cible (820) configuré pour sélectionner un nœud esclave cible parmi la pluralité de nœuds esclaves (S0, S1, S2, Sk), le nœud esclave cible étant un nœud esclave qui communique normalement avec à la fois le nœud maître (M) et le nœud esclave par défaut ;

    un premier module de transmission (830) configuré pour transmettre des informations de conversion de fréquence au nœud esclave cible, de telle sorte que nœud esclave transfère les informations de conversion de fréquence au nœud esclave par défaut, et le nœud esclave par défaut réalise une conversion de fréquence sur la base des informations de conversion de fréquence ; et

    un module de transmission d'informations (840) configuré pour transmettre des informations avec le nœud esclave par défaut à l'aide d'une fréquence après la conversion de fréquence.


     
    13. Appareil (900) de transmission d'informations dans un système de gestion de batterie (100), caractérisé en ce qu'il comprend :

    un premier module de réception (910) configuré pour recevoir des informations de conversion de fréquence transmises par un nœud maître (M) dans le système de gestion de batterie (100) ; et

    un second module de transmission (920) configuré pour transférer les informations de conversion de fréquence à un nœud esclave par défaut, de telle sorte que le nœud esclave par défaut réalise une conversion de fréquence basée sur les informations de conversion de fréquence, et le nœud maître (M) transmette des informations avec le nœud esclave par défaut à l'aide d'une fréquence après la conversion de fréquence,

    dans lequel le nœud esclave par défaut est un nœud esclave, déterminé par le nœud maître (M) parmi une pluralité de nœuds esclaves (S0, S1, S2, Sk), qui communique de façon anormale avec le nœud maître (M).


     
    14. Appareil (1000) de transmission d'informations dans un système de gestion de batterie (100), caractérisé en ce qu'il comprend :

    un second module de réception (1010) configuré pour recevoir des informations de conversion de fréquence transmises par un nœud esclave cible, le nœud esclave cible étant un nœud esclave sélectionné parmi une pluralité de nœuds esclaves (S0, S1, S2, Sk) par un nœud maître (M) dans le système de gestion de batterie (100), et le nœud esclave cible étant un nœud esclave qui communique normalement avec à la fois le nœud maître (M) et un nœud esclave par défaut, et le nœud esclave par défaut étant un nœud esclave, déterminé par le nœud maître (M) parmi la pluralité de nœuds esclaves (S0, S1, S2, Sk), qui communique de façon anormale avec le nœud maître (M) ; et

    un module de conversion de fréquence (1020) configuré pour réaliser une conversion de fréquence basée sur les informations de conversion de fréquence, de telle sorte que le nœud maître (M) utilise une fréquence après la conversion de fréquence pour transmettre des informations avec le nœud esclave par défaut.


     
    15. Système de gestion de batterie (100), caractérisé en ce qu'il comprend l'appareil (800) de transmission d'informations dans un système de gestion de batterie (100) selon la revendication 12, l'appareil (900) de transmission d'informations dans un système de gestion de batterie (100) selon la revendication 13, et l'appareil (1000) de transmission d'informations dans un système de gestion de batterie (100) selon la revendication 14.
     




    Drawing

















    Cited references

    REFERENCES CITED IN THE DESCRIPTION



    This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.

    Patent documents cited in the description