CN103311584A - Battery unit, terminal device and battery verifying method - Google Patents

Battery unit, terminal device and battery verifying method Download PDF

Info

Publication number
CN103311584A
CN103311584A CN2012100640333A CN201210064033A CN103311584A CN 103311584 A CN103311584 A CN 103311584A CN 2012100640333 A CN2012100640333 A CN 2012100640333A CN 201210064033 A CN201210064033 A CN 201210064033A CN 103311584 A CN103311584 A CN 103311584A
Authority
CN
China
Prior art keywords
battery
terminal
length
validation
unit
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN2012100640333A
Other languages
Chinese (zh)
Other versions
CN103311584B (en
Inventor
赵双成
程孝仁
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Lenovo Beijing Ltd
Original Assignee
Lenovo Beijing Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo Beijing Ltd filed Critical Lenovo Beijing Ltd
Priority to CN201210064033.3A priority Critical patent/CN103311584B/en
Publication of CN103311584A publication Critical patent/CN103311584A/en
Application granted granted Critical
Publication of CN103311584B publication Critical patent/CN103311584B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02EREDUCTION OF GREENHOUSE GAS [GHG] EMISSIONS, RELATED TO ENERGY GENERATION, TRANSMISSION OR DISTRIBUTION
    • Y02E60/00Enabling technologies; Technologies with a potential or indirect contribution to GHG emissions mitigation
    • Y02E60/10Energy storage using batteries

Abstract

The invention relates to a battery unit, a terminal device and a battery verifying method. The battery unit comprises a battery interface unit and a battery management unit, wherein the battery interface unit is used for being connected with a terminal part and powering the terminal part; the battery management unit is used for actuating the battery matching between the battery unit and the terminal part and supporting a first battery verification mode and a second battery verification mode, and when the terminal part is connected with the battery unit, the battery management unit receives a random verification code from the terminal part through the battery interface unit; the length of the random verification code is judged by the battery management unit; whether the battery verification is actuated through the first battery verification mode or the second battery verification mode is determined according to the length of the random verification code, and the battery verification response is fed back to the terminal part.

Description

Battery unit, terminal equipment and battery verification method
Technical field
The present invention relates to a kind of battery unit, terminal equipment and battery verification method.
Background technology
Current, along with popularizing of the terminal equipment such as notebook computer, more and more palm off battery and appear on the market.Use the personation battery may affect flying power and the useful life of terminal equipment.Therefore, current exist the multiple battery verification technique take the battery of verification terminal equipment whether as legal battery.Here, because different types of terminal equipment (as, Thinkpad or Ideapad) common (support) the different battery verification technique of using, therefore must support for above-mentioned terminal equipment design the battery of different battery verification techniques, cause the above-mentioned battery can not be general in different types of terminal equipment.
Summary of the invention
In order to solve above-mentioned technical problem of the prior art, according to an aspect of the present invention, provide a kind of battery unit, comprising: the battery interface unit, configuration is connected with terminal part, and provides electric power to described terminal part; And battery management unit, the battery coupling of battery unit and terminal part is carried out in configuration, and support the first battery Validation Mode and the second battery Validation Mode, wherein when described terminal part was connected with described battery unit, described battery management unit was by the accidental validation code of described battery interface unit reception from described terminal part; Described battery management unit is judged the length of described accidental validation code; And determine whether to carry out the battery checking by described the first battery Validation Mode or described the second battery Validation Mode based on the length of described accidental validation code, and to the auth response of described terminal part feedback battery.
In addition, according to one embodiment of present invention, if wherein the length of described accidental validation code is the first length, then described battery management unit is carried out the battery checking by described the first battery Validation Mode, and to the auth response of described terminal part feedback battery; And if the length of described accidental validation code is the second length, then described battery management unit is carried out the battery checking by described the second battery Validation Mode, and to the auth response of described terminal part feedback battery.
In addition, according to one embodiment of present invention, wherein said the first length is 20 bytes, and described the first battery Validation Mode is the SHA1 pattern; And described the second length is 17 bytes, and described the second battery Validation Mode is the ECC pattern.
In addition, according to a further aspect in the invention, provide a kind of battery that is applied to battery unit to verify other method, described battery unit is supported the first battery Validation Mode and the second battery Validation Mode, described method comprises: when terminal part is connected with described battery unit, receive the accidental validation code from described terminal part; Judge the length of described accidental validation code; Length based on described accidental validation code determines whether to carry out the battery checking by described the first battery Validation Mode or described the second battery Validation Mode; And to the auth response of described terminal part feedback battery.
In addition, according to one embodiment of present invention, if wherein the length of described accidental validation code is the first length, then carry out the battery checking by described the first battery Validation Mode, and to the auth response of described terminal part feedback battery; And if the length of described accidental validation code is the second length, then carry out the battery checking by described the second battery Validation Mode, and to the auth response of described terminal part feedback battery.
In addition, according to one embodiment of present invention, wherein said the first length is 20 bytes, and described the first battery Validation Mode is the SHA1 pattern; And described the second length is 17 bytes, and described the second battery Validation Mode is the ECC pattern.
In addition, according to a further aspect in the invention, provide a kind of terminal equipment, comprising: terminal part comprises: control unit, and configuration sends the accidental validation code, and the battery auth response of battery partial feedback is analyzed; The battery part comprises: the battery interface unit, and configuration is connected with terminal part, and provides electric power to described terminal part; And battery management unit, the battery coupling of battery unit and terminal part is carried out in configuration, and support the first battery Validation Mode and the second battery Validation Mode, wherein partly be connected with described battery or described control unit when resetting at described terminal part, described control unit partly sends described accidental validation code to described battery; Described battery management unit is by the accidental validation code of described battery interface unit reception from described terminal part; Described battery management unit is judged the length of described accidental validation code; And determine whether to carry out the battery checking by described the first battery Validation Mode or described the second battery Validation Mode based on the length of described accidental validation code, and to the auth response of described terminal part feedback battery.
In addition, according to one embodiment of present invention, if wherein the length of described accidental validation code is the first length, then described battery management unit is carried out the battery checking by described the first battery Validation Mode, and to the auth response of described terminal part feedback battery; And if the length of described accidental validation code is the second length, then described battery management unit is carried out the battery checking by described the second battery Validation Mode, and to the auth response of described terminal part feedback battery.
In addition, according to one embodiment of present invention, wherein said the first length is 20 bytes, and described the first battery Validation Mode is the SHA1 pattern; And described the second length is 17 bytes, and described the second battery Validation Mode is the ECC pattern.
In addition, according to one embodiment of present invention, if wherein the length of described accidental validation code is the first length, then described control unit is carried out the battery checking by described the first battery Validation Mode, and checking produces the first battery the result based on battery; And described control unit is analyzed with described the first battery the result and from the battery auth response of described battery part; And if described the first battery the result and battery auth response coupling from described battery part, then control unit judges that described battery partly is legal battery.
In addition, according to one embodiment of present invention, if wherein the length of described accidental validation code is the second length, then described control unit is carried out the battery checking by described the second battery Validation Mode, and checking produces the second battery the result based on battery; And described control unit is analyzed with described the second battery the result and from the battery auth response of described battery part; And if described the second battery the result and battery auth response coupling from described battery part, then control unit judges that described battery partly is legal battery.
In addition, according to a further aspect in the invention, a kind of battery verification method is provided, be applied to terminal equipment, described terminal equipment comprises terminal part and battery part, described battery verification method comprises: partly be connected with described battery or the control unit of described terminal part when resetting at described terminal part, partly send described accidental validation code to described battery; Reception is from the accidental validation code of described terminal part; Judge the length of described accidental validation code; And determine whether to carry out the battery checking by described the first battery Validation Mode or described the second battery Validation Mode based on the length of described accidental validation code, and to the auth response of described terminal part feedback battery.
By above-mentioned configuration, battery unit can be supported the multiple battery Validation Mode, and needs to carry out any battery Validation Mode based on the length judgement of the accidental validation code that receives.In this case, battery unit can be general between the terminal equipment of supporting different types of battery Validation Mode, and do not affect the battery verification the verifying results of battery unit.
Description of drawings
Fig. 1 is that diagram is according to the schematic block diagram of the battery unit of the embodiment of the invention;
Fig. 2 is that diagram is according to the flow chart of the battery verification method of the embodiment of the invention;
Fig. 3 is that diagram is according to the schematic block diagram of the terminal equipment of the embodiment of the invention; And
Fig. 4 is that diagram is according to the flow chart of the battery verification method of the embodiment of the invention.
Embodiment
Describe in detail with reference to the accompanying drawings according to each embodiment of the present invention.Here, it should be noted that in the accompanying drawings, identical Reference numeral is given basically had part identical or similar structures and function, and will omit being repeated in this description about them.
Below, with reference to the battery unit of Fig. 1 description according to the embodiment of the invention.Fig. 1 is that diagram is according to the schematic block diagram of the battery unit of the embodiment of the invention.Here, can be rechargeable battery (such as, lithium battery) for the terminal equipment such as notebook computer according to the battery unit of the embodiment of the invention.
As shown in Figure 1, the battery unit 1 according to the embodiment of the invention can comprise battery interface unit 11 and battery management unit 12.
Battery interface unit 11 can be realized by battery interface arbitrarily, and connects with the corresponding battery interface of the terminal part (terminal equipment does not comprise the part of battery unit) of terminal equipment.Here, can provide electric power to terminal part by battery interface unit 11, and can with the terminal part exchange message.
Battery management unit 12 can be by microcontroller implementation arbitrarily.Battery management unit 12 can be carried out battery unit 1 and verify with the battery of terminal part.According to embodiments of the invention, battery management unit 12 supports the first battery Validation Mode (as, the SHA1 pattern) and the second battery Validation Mode (as, the ECC pattern).
According to embodiments of the invention, be connected with battery unit 1 at terminal part (as, battery unit 1 is installed on the terminal part) time, perhaps when the control unit of terminal part was reset, battery management unit 12 was by the accidental validation code of battery interface unit 11 receptions from terminal part.After the accidental validation code that receives from terminal part, battery management unit 12 is judged the length of accidental validation code.Then, battery management unit 12 determines whether to carry out the battery checking by the first battery Validation Mode or the second battery Validation Mode based on the length of accidental validation code, and to the auth response of terminal part feedback battery.
Particularly, after the accidental validation code that receives from terminal part, battery management unit 12 is judged the length of accidental validation code.For example, if battery management unit 12 determines that the length of accidental validation code is the first length, then battery management unit 12 is carried out the battery checking by the first battery Validation Mode, and passes through battery interface unit 11 to the auth response of terminal part feedback battery.Here, for example, in the situation that the first battery Validation Mode is the SHA1 pattern, the length of its accidental validation code is generally 20 bytes.Therefore, determine that at battery management unit 12 length of accidental validation code is in the situation of 20 bytes, battery management unit 12 is carried out the battery checking and is produced the battery auth response based on the accidental validation code that obtains by the SHA1 pattern.
In addition, if the length of accidental validation code is the second length, then 12 yuan of battery management lists are carried out the battery checking by the second battery Validation Mode, and by battery interface unit 11 to the auth response of terminal part feedback battery.Here, for example, in the situation that the second battery Validation Mode is the ECC pattern, the length of its accidental validation code is generally 17 bytes.Therefore, determine that at battery management unit 12 length of accidental validation code is in the situation of 17 bytes, battery management unit 12 is carried out the battery checking and is produced the battery auth response based on the accidental validation code that obtains by the ECC pattern.Here, it should be noted that owing to knowing to those skilled in the art by the battery checking processing of SHA1 pattern and the execution of ECC pattern, therefore omitted the detailed description about them here.
In addition, if the length of accidental validation code neither is the first length (20 byte), be not the second length (17 byte) yet, then 12 yuan of definite battery units 1 of battery management list do not mate with terminal part, and feed back the unmatched battery auth response of pilot cell by battery interface unit 11 to terminal part.
Here, take the first length as 20 bytes, the second length is 17 bytes, and the first battery Validation Mode is the SHA1 pattern, and the second battery Validation Mode is that the ECC pattern is that example is described.Yet, the invention is not restricted to this, battery unit 1 can also adopt other battery Validation Mode.In this case, because the accidental validation code of other battery Validation Mode may change according to the design needs, therefore in the situation that battery unit 1 is supported other battery Validation Mode, the first length and the second length are not limited to 20 bytes and 17 bytes of before description.In addition, battery unit 1 can also be supported two or more battery Validation Modes.In this case, because battery unit 1 judges that based on the length of accidental validation code the mode of carrying out which kind of battery checking is similar with the description of Fig. 1, so repeat no more here.
By above-mentioned configuration, battery unit 1 can be supported the multiple battery Validation Mode, and needs to carry out any battery Validation Mode based on the length judgement of the accidental validation code that receives.In this case, battery unit 1 can support the terminal equipment of different types of battery Validation Mode (as, Thinkpad supports the ECC pattern, Ideapad supports the SHA1 pattern) between general, and do not affect the battery verification the verifying results of battery unit 1.
Below, with reference to the battery verification method of Fig. 2 description according to the embodiment of the invention.Battery verification method shown in Figure 2 can be applied to the battery unit 1 of support shown in Figure 1 the first battery Validation Mode and the second battery Validation Mode.
As shown in Figure 2, at step S201, when terminal part is connected with battery unit, receive the accidental validation code from terminal part.
Particularly, be connected with battery unit 1 at terminal part (as, battery unit 1 is installed on the terminal part) time, perhaps when the control unit of terminal part was reset, battery management unit 12 was by the accidental validation code of battery interface unit 11 receptions from terminal part.
At step S202, judge the length of accidental validation code.
Particularly, after the accidental validation code that receives from terminal part, battery management unit 12 is judged the length of accidental validation code.For example, battery management unit 12 is judged the length of accidental validation code by the byte number that calculates received accidental validation code.
At step S203, determine whether to carry out the battery checking by the first battery Validation Mode or the second battery Validation Mode based on the length of accidental validation code.
Particularly, if battery management unit 12 determines that the length of accidental validation code is the first length, then battery management unit 12 is carried out the battery checking by the first battery Validation Mode.Here, for example, in the situation that the first battery Validation Mode is the SHA1 pattern, the length of its accidental validation code is generally 20 bytes.Therefore, determine that at battery management unit 12 length of accidental validation code is in the situation of 20 bytes, battery management unit 12 is carried out the battery checking and is produced the battery auth response based on the accidental validation code that obtains by the SHA1 pattern.
In addition, if the length of accidental validation code is the second length, then 12 yuan of battery management lists are carried out the battery checking by the second battery Validation Mode.Here, for example, in the situation that the second battery Validation Mode is the ECC pattern, the length of its accidental validation code is generally 17 bytes.Therefore, determine that at battery management unit 12 length of accidental validation code is in the situation of 17 bytes, battery management unit 12 is carried out the battery checking and is produced the battery auth response based on the accidental validation code that obtains by the ECC pattern.
In addition, if the length of accidental validation code neither is the first length (20 byte), be not the second length (17 byte), then 12 yuan of definite battery units 1 of battery management list do not mate with terminal part, and produce the unmatched battery auth response of pilot cell yet.
Then, at step S204, to the auth response of terminal part feedback battery.
Particularly, after battery management list 12 is based on the first battery Validation Mode or the auth response of the second battery Validation Mode generation battery, perhaps after battery management unit 12 produced the unmatched battery auth response of pilot cell, battery management list 12 fed back the battery auth response by battery interface unit 11 to terminal part.
Below, with reference to the terminal equipment of Fig. 3 description according to the embodiment of the invention.Fig. 3 is that diagram is according to the schematic block diagram of the terminal equipment of the embodiment of the invention.Here, terminal equipment shown in Figure 3 can be notebook computer.
As shown in Figure 3, terminal equipment 3 can comprise battery part 31 and terminal part 32, and wherein terminal part 32 is removed the part of battery part 31 for terminal equipment.
Here, similar with the description of Fig. 1, battery part 31 can comprise battery interface unit 311 and battery management unit 312.
The corresponding battery interface of the terminal part 32 of battery interface unit 311 and terminal equipment connects, and can by battery interface unit 11 to terminal part 32 provide electric power and with terminal part 32 exchange messages.Battery management unit 312 can be carried out battery part 31 and verify with the battery of terminal part 32.Here, battery management unit 12 supports the first battery Validation Mode (as, the SHA1 pattern) and the second battery Validation Mode (as, the ECC pattern).
Terminal part 32 can comprise control unit 321.Control unit 321 can be realized by embedded controller (EC).Control unit 321 can send the accidental validation code under predetermined case, and the battery auth response of battery part 31 feedbacks is analyzed.
According to embodiments of the invention, be connected with battery part 31 at terminal part 32 (as, battery part 31 is inserted terminal part 32) time, perhaps reset at control unit 321 (as, restarting of terminal equipment 3) time, control unit 321 sends the accidental validation code to battery part 13.Here, the difference of the battery Validation Mode of supporting according to terminal part 32, the control unit 321 of dissimilar terminal part 32 can send the accidental validation code with different length.For example, support in the first battery Validation Mode situation of (such as, SHA1 pattern) at terminal part 32, control unit 321 can send and have the first length the accidental validation code of (such as, 20 bytes).In addition, support in the second battery Validation Mode situation of (such as, ECC pattern) at terminal part 32, control unit 321 can send and have the second length the accidental validation code of (such as, 17 bytes).
In this case, similar with the description for Fig. 1, the accidental validation code that the battery management unit 312 of battery part 31 receives from terminal part 32 by battery interface unit 311.After the accidental validation code that receives from terminal part 32, battery management unit 312 is judged the length of accidental validation code.Then, battery management unit 312 determines whether to carry out the battery checking by the first battery Validation Mode or the second battery Validation Mode based on the length of accidental validation code, and to terminal part 32 feedback battery auth responses.
Particularly, after the accidental validation code that receives from terminal part 32, battery management unit 312 is judged the length of accidental validation code.For example, if battery management unit 312 determine the length of accidental validation codes be the first length (as, 20 bytes), then battery management unit 312 is carried out the battery checking and is produced the battery auth response by the first battery Validation Mode (SHA1 pattern), and passes through battery interface unit 311 to terminal part 32 feedback battery auth responses.In addition, if the length of accidental validation code be the second length (as, 17 bytes), then 312 yuan of battery management lists are carried out the battery checking and are produced the battery auth response by the second battery Validation Mode, and by battery interface unit 311 to terminal part 32 feedback battery auth responses.In addition, if the length of accidental validation code neither is the first length (20 byte), be not the second length (17 byte) yet, then 312 yuan of definite battery parts 31 of battery management list are not mated with terminal part 32, and feed back the unmatched battery auth response of pilot cells by battery interface unit 311 to terminal part 32.
Here, according to embodiments of the invention, the control unit 321 of terminal part 32 is also carried out corresponding battery checking and is processed.Here, control unit 321 can be carried out immediately corresponding battery checking and process after sending the accidental validation code, perhaps in the situation that receive the battery auth response from battery part 31, carries out corresponding battery checking processing.
For example, support in the first battery Validation Mode situation of (such as, SHA1 pattern) at terminal part 32, control unit 321 sends and has the first length the accidental validation code of (such as, 20 bytes) to battery part 31.Then control unit 321 is carried out battery checking by the first battery Validation Mode based on this accidental validation code, and produces the first battery the result (such as, the battery the result of SHA1 pattern).In addition, if control unit 321 receives the battery auth response from battery part 31, then control unit 321 will be analyzed from battery auth response and the first battery the result of battery part 31.Here, if battery part 31 is the battery units according to the embodiment of the invention, then battery part 31 also should correspondingly be carried out the first battery Validation Mode (SHA1 pattern) and feed back the battery auth response.In the situation that the first battery Validation Mode is the SHA1 pattern, control unit 321 will compare from battery auth response and the first battery the result of battery part 31, if the two is identical, then control unit 321 can determine that battery part 31 is legal battery.In addition, if the two difference, then control unit 321 can determine that battery part 31 is non-legal battery.
In addition, support in the second battery Validation Mode situation of (such as, ECC pattern) at terminal part 32, control unit 321 sends and has the second length the accidental validation code of (such as, 17 bytes) to battery part 31.Then control unit 321 is carried out battery checking by the second battery Validation Mode based on this accidental validation code, and produces the second battery the result (such as, the battery the result of ECC pattern).In addition, if control unit 321 receives the battery auth response from battery part 31, then control unit 321 will be analyzed from battery auth response and the second battery the result of battery part 31.Here, if battery part 31 is the battery units according to the embodiment of the invention, then battery part 31 also should correspondingly be carried out the second battery Validation Mode (ECC pattern) and feed back the battery auth response.In the situation that the second battery Validation Mode is the ECC pattern, control unit 321 will compare from battery auth response and the second battery the result of battery part 31, if the two is complementary (mutually corresponding), then control unit 321 can determine that battery part 31 is legal battery.In addition, if the two does not mate (not corresponding), then control unit 321 can determine that battery part 31 is non-legal battery.
Here, before control unit 321 determined that battery parts 31 be non-legal battery, control unit 321 can also repeat above-mentioned processing for several times, with guarantee battery checking processing can not be subject to data transmission fault (as, lose data) impact.In addition, after control unit 321 determined that battery part 31 is non-legal battery, control unit 321 can point out battery part 31 to be non-legal battery to the user.For example, control unit 321 can show at the display screen of terminal equipment 3 information of relevant non-legal battery, perhaps can make the power lights of terminal equipment glimmer prompting user using non-legal battery.
By above-mentioned configuration, even the terminal part of terminal equipment 3 32 is supported different battery Authentication-Types, battery part 31 also can support that different battery Authentication-Types is general, and can adjust adaptively employed battery Validation Mode according to the battery Authentication-Type that terminal part 32 is supported, can make thus terminal equipment 32 finish the battery checking and process.
The below is with reference to the battery verification method of Fig. 4 description according to the embodiment of the invention.Fig. 4 is that diagram is according to the flow chart of the battery verification method of the embodiment of the invention.Here, the battery verification method of Fig. 4 can be applied on the terminal equipment shown in Figure 33.
As shown in Figure 4, at step S401, partly be connected with battery at terminal part, when perhaps the control unit of terminal part is reset, partly send the accidental validation code to battery.
Particularly, be connected with battery part 31 at terminal part 32 (as, battery part 31 is inserted terminal part 32) time, perhaps reset at control unit 321 (as, restarting of terminal equipment 3) time, control unit 321 sends the accidental validation code to battery part 13.Here, the difference of the battery Validation Mode of supporting according to terminal part 32, the control unit 321 of dissimilar terminal part 32 can send the accidental validation code with different length.For example, support in the first battery Validation Mode situation of (such as, SHA1 pattern) at terminal part 32, control unit 321 can send and have the first length the accidental validation code of (such as, 20 bytes).In addition, support in the second battery Validation Mode situation of (such as, ECC pattern) at terminal part 32, control unit 321 can send and have the second length the accidental validation code of (such as, 17 bytes).
At step S402, receive the accidental validation code from terminal part.
Particularly, the battery management unit 312 of battery part 31 is by the accidental validation code of battery interface unit 311 receptions from terminal part 32.
At step S403, judge the length of accidental validation code.
Particularly, after the accidental validation code that receives from terminal part 32, battery management unit 312 is judged the length of accidental validation code.
Then, at step S404, determine whether to carry out the battery checking by the first battery Validation Mode or the second battery Validation Mode based on the length of accidental validation code, and to the auth response of terminal part feedback battery.
Particularly, for example, if battery management unit 312 determine the length of accidental validation codes be the first length (as, 20 bytes), then battery management unit 312 is carried out the battery checking and is produced the battery auth response by the first battery Validation Mode (SHA1 pattern), and passes through battery interface unit 311 to terminal part 32 feedback battery auth responses.In addition, if the length of accidental validation code be the second length (as, 17 bytes), then 312 yuan of battery management lists are carried out the battery checking and are produced the battery auth response by the second battery Validation Mode, and by battery interface unit 311 to terminal part 32 feedback battery auth responses.In addition, if the length of accidental validation code neither is the first length (20 byte), be not the second length (17 byte) yet, then 312 yuan of definite battery parts 31 of battery management list are not mated with terminal part 32, and feed back the unmatched battery auth response of pilot cells by battery interface unit 311 to terminal part 32.
Battery verification method according to the embodiment of the invention has been described in the above.In addition, method shown in Figure 4 can also be included in terminal part and also carry out corresponding battery checking processing, produces the battery the result, and battery the result and battery auth response are analyzed to judge whether the battery part is the step of legal battery.Here, this step can be carried out after step S401 immediately, also can carry out after step S404.
Particularly, for example, terminal part 32 support the first battery Validation Mode (as, the SHA1 pattern) in the situation, control unit 321 is by the first battery Validation Mode, carry out battery checking based on this accidental validation code, and produce the first battery the result (such as, the battery the result of SHA1 pattern).In addition, if control unit 321 receives the battery auth response from battery part 31, then control unit 321 will be analyzed from battery auth response and the first battery the result of battery part 31.In this case, if the two is identical, then control unit 321 can determine that battery part 31 is legal battery.In addition, if the two difference, then control unit 321 can determine that battery part 31 is non-legal battery.In addition, terminal part 32 support the second battery Validation Mode (as, the ECC pattern) in the situation, control unit 321 is by the second battery Validation Mode, carry out the battery checking based on this accidental validation code, and produce the second battery the result (such as, the battery the result of ECC pattern).According to embodiments of the invention, if control unit 321 receives the battery auth response from battery part 31, control unit 321 will be analyzed from battery auth response and the second battery the result of battery part 31.In this case, if the two is complementary (mutually corresponding), then control unit 321 can determine that battery part 31 is legal battery.In addition, if the two does not mate (not corresponding), then control unit 321 can determine that battery part 31 is non-legal battery.
Describe each embodiment of the present invention in the above in detail.Yet, it should be appreciated by those skilled in the art that without departing from the principles and spirit of the present invention, can carry out various modifications to these embodiment, combination or sub-portfolio, and such modification should fall within the scope of the present invention.

Claims (12)

1. battery unit comprises:
The battery interface unit, configuration is connected with terminal part, and provides electric power to described terminal part; And
Battery management unit, configuration are carried out the battery coupling of battery unit and terminal part, and support the first battery Validation Mode and the second battery Validation Mode,
Wherein when described terminal part was connected with described battery unit, described battery management unit was by the accidental validation code of described battery interface unit reception from described terminal part;
Described battery management unit is judged the length of described accidental validation code; And
Length based on described accidental validation code determines whether to carry out the battery checking by described the first battery Validation Mode or described the second battery Validation Mode, and to the auth response of described terminal part feedback battery.
2. battery unit as claimed in claim 1, wherein
If the length of described accidental validation code is the first length, then described battery management unit is carried out the battery checking by described the first battery Validation Mode, and to the auth response of described terminal part feedback battery; And
If the length of described accidental validation code is the second length, then described battery management unit is carried out the battery checking by described the second battery Validation Mode, and to the auth response of described terminal part feedback battery.
3. battery unit as claimed in claim 2, wherein
Described the first length is 20 bytes, and described the first battery Validation Mode is the SHA1 pattern; And
Described the second length is 17 bytes, and described the second battery Validation Mode is the ECC pattern.
4. a battery that is applied to battery unit is verified other method, and described battery unit is supported the first battery Validation Mode and the second battery Validation Mode, and described method comprises:
When terminal part is connected with described battery unit, receive the accidental validation code from described terminal part;
Judge the length of described accidental validation code;
Length based on described accidental validation code determines whether to carry out the battery checking by described the first battery Validation Mode or described the second battery Validation Mode; And
To the auth response of described terminal part feedback battery.
5. battery verification method as claimed in claim 4, wherein
If the length of described accidental validation code is the first length, then carry out the battery checking by described the first battery Validation Mode, and to the auth response of described terminal part feedback battery; And
If the length of described accidental validation code is the second length, then carry out the battery checking by described the second battery Validation Mode, and to the auth response of described terminal part feedback battery.
6. battery verification method as claimed in claim 4, wherein
Described the first length is 20 bytes, and described the first battery Validation Mode is the SHA1 pattern; And
Described the second length is 17 bytes, and described the second battery Validation Mode is the ECC pattern.
7. terminal equipment comprises:
Terminal part comprises:
Control unit, configuration sends the accidental validation code, and the battery auth response of battery partial feedback is analyzed;
The battery part comprises:
The battery interface unit, configuration is connected with terminal part, and provides electric power to described terminal part; And
Battery management unit, configuration are carried out the battery coupling of battery unit and terminal part, and support the first battery Validation Mode and the second battery Validation Mode,
Wherein
Partly be connected with described battery or described control unit when resetting at described terminal part, described control unit partly sends described accidental validation code to described battery;
Described battery management unit is by the accidental validation code of described battery interface unit reception from described terminal part;
Described battery management unit is judged the length of described accidental validation code; And
Length based on described accidental validation code determines whether to carry out the battery checking by described the first battery Validation Mode or described the second battery Validation Mode, and to the auth response of described terminal part feedback battery.
8. terminal equipment as claimed in claim 7, wherein
If the length of described accidental validation code is the first length, then described battery management unit is carried out the battery checking by described the first battery Validation Mode, and to the auth response of described terminal part feedback battery; And
If the length of described accidental validation code is the second length, then described battery management unit is carried out the battery checking by described the second battery Validation Mode, and to the auth response of described terminal part feedback battery.
9. terminal equipment as claimed in claim 8, wherein
Described the first length is 20 bytes, and described the first battery Validation Mode is the SHA1 pattern; And
Described the second length is 17 bytes, and described the second battery Validation Mode is the ECC pattern.
10. terminal equipment as claimed in claim 7, wherein
If the length of described accidental validation code is the first length, then described control unit is carried out the battery checking by described the first battery Validation Mode, and checking produces the first battery the result based on battery; And
Described control unit is analyzed with described the first battery the result and from the battery auth response of described battery part; And
If described the first battery the result and battery auth response coupling from described battery part, then control unit judges that described battery partly is legal battery.
11. terminal equipment as claimed in claim 7, wherein
If the length of described accidental validation code is the second length, then described control unit is carried out the battery checking by described the second battery Validation Mode, and checking produces the second battery the result based on battery; And
Described control unit is analyzed with described the second battery the result and from the battery auth response of described battery part; And
If described the second battery the result and battery auth response coupling from described battery part, then control unit judges that described battery partly is legal battery.
12. a battery verification method is applied to terminal equipment, described terminal equipment comprises terminal part and battery part, and described battery verification method comprises:
Partly be connected with described battery or the control unit of described terminal part when resetting at described terminal part, partly send described accidental validation code to described battery;
Reception is from the accidental validation code of described terminal part;
Judge the length of described accidental validation code; And
Length based on described accidental validation code determines whether to carry out the battery checking by described the first battery Validation Mode or described the second battery Validation Mode, and to the auth response of described terminal part feedback battery.
CN201210064033.3A 2012-03-12 2012-03-12 Battery unit, terminal equipment and battery verification method Active CN103311584B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201210064033.3A CN103311584B (en) 2012-03-12 2012-03-12 Battery unit, terminal equipment and battery verification method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201210064033.3A CN103311584B (en) 2012-03-12 2012-03-12 Battery unit, terminal equipment and battery verification method

Publications (2)

Publication Number Publication Date
CN103311584A true CN103311584A (en) 2013-09-18
CN103311584B CN103311584B (en) 2016-03-30

Family

ID=49136554

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201210064033.3A Active CN103311584B (en) 2012-03-12 2012-03-12 Battery unit, terminal equipment and battery verification method

Country Status (1)

Country Link
CN (1) CN103311584B (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103607505A (en) * 2013-11-13 2014-02-26 四川长虹电器股份有限公司 Mutual verification-based mobile phone and charger thereof, and working method thereof
CN104682522A (en) * 2015-03-30 2015-06-03 北京中科盛康科技有限公司 Charger for battery
CN106291383A (en) * 2016-08-25 2017-01-04 乐视控股(北京)有限公司 Battery detection method and battery check device

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1444835A (en) * 2000-08-03 2003-09-24 奥林奇私人通讯服务有限公司 Authentication in mobile communications network
CN1779743A (en) * 2004-11-26 2006-05-31 索尼计算机娱乐公司 Battery and authentication requesting device
CN101438219A (en) * 2006-03-10 2009-05-20 爱特梅尔公司 Random number generator in a battery pack
CN101655814A (en) * 2008-08-18 2010-02-24 联想(北京)有限公司 Method for authenticating smart battery and terminal
US20100049976A1 (en) * 2008-08-21 2010-02-25 Gm Global Technology Operations, Inc. Adaptive data verification for resource-constrained systems
CN102111272A (en) * 2010-12-24 2011-06-29 武汉天喻信息产业股份有限公司 Method for authenticating external equipment by using mobile terminal

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1444835A (en) * 2000-08-03 2003-09-24 奥林奇私人通讯服务有限公司 Authentication in mobile communications network
CN1779743A (en) * 2004-11-26 2006-05-31 索尼计算机娱乐公司 Battery and authentication requesting device
CN101438219A (en) * 2006-03-10 2009-05-20 爱特梅尔公司 Random number generator in a battery pack
CN101655814A (en) * 2008-08-18 2010-02-24 联想(北京)有限公司 Method for authenticating smart battery and terminal
US20100049976A1 (en) * 2008-08-21 2010-02-25 Gm Global Technology Operations, Inc. Adaptive data verification for resource-constrained systems
CN102111272A (en) * 2010-12-24 2011-06-29 武汉天喻信息产业股份有限公司 Method for authenticating external equipment by using mobile terminal

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103607505A (en) * 2013-11-13 2014-02-26 四川长虹电器股份有限公司 Mutual verification-based mobile phone and charger thereof, and working method thereof
CN104682522A (en) * 2015-03-30 2015-06-03 北京中科盛康科技有限公司 Charger for battery
CN106291383A (en) * 2016-08-25 2017-01-04 乐视控股(北京)有限公司 Battery detection method and battery check device

Also Published As

Publication number Publication date
CN103311584B (en) 2016-03-30

Similar Documents

Publication Publication Date Title
CN203191896U (en) Host device for judging whether accessory comprises specific circuit or not and accessory
US7498766B2 (en) System and method for authenticating a battery
JP2016527779A (en) Access control communication apparatus, method, computer program, and computer program product
CN103078393A (en) Usb hub and electric power supply method for the same
US9459604B2 (en) Methods and system for joining a smart energy device to a zigbee network
CN103888422A (en) Security certificate updating method, client and server
CN106569853B (en) Software upgrading test method for double-core electric energy meter
CA2573997A1 (en) Method and apparatus for displaying battery fault notifications on wireless devices
US10840721B2 (en) System and method for controlling an electrical receptacle
CN104080086A (en) Wireless connection establishment method and wireless connection establishment device
CN103220153A (en) Encrypting method based on two-dimensional codes as well as encrypting device and information system
CN108848163A (en) The upgrade method and TWS earphone of TWS earphone
CN103311584A (en) Battery unit, terminal device and battery verifying method
US20090177593A1 (en) Portable base station device and charging method
WO2017143226A1 (en) Computing devices with centralized power sources
US20100271226A1 (en) Electrical outlet arrangements and system
CN103533545A (en) Method, device and equipment for acquiring effective communication account number
EP2937963B1 (en) Power supply control device, battery device, power supply system, and power supply control method
KR20160029061A (en) Portable access control communication device, method, computer program and computer program product
WO2018088375A1 (en) Wireless transmitter receiver and vehicle
CN105871946A (en) Data transmission system and data transmission method of charging station
CN106707194B (en) Rechargeable battery detection method and electronic equipment
CN103957304A (en) Mobile terminal and abnormity prompting method thereof
US9801216B1 (en) Peer-to-peer configuration
US10664930B2 (en) Device for powering an electrical appliance

Legal Events

Date Code Title Description
PB01 Publication
C06 Publication
SE01 Entry into force of request for substantive examination
C10 Entry into substantive examination
GR01 Patent grant
C14 Grant of patent or utility model