CA2636425C - Battery authentication in a wireless communication device - Google Patents
Battery authentication in a wireless communication device Download PDFInfo
- Publication number
- CA2636425C CA2636425C CA2636425A CA2636425A CA2636425C CA 2636425 C CA2636425 C CA 2636425C CA 2636425 A CA2636425 A CA 2636425A CA 2636425 A CA2636425 A CA 2636425A CA 2636425 C CA2636425 C CA 2636425C
- Authority
- CA
- Canada
- Prior art keywords
- battery
- wireless communication
- communication device
- encrypted text
- causing
- 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.)
- Expired - Fee Related
Links
Classifications
-
- H—ELECTRICITY
- H01—ELECTRIC ELEMENTS
- H01M—PROCESSES OR MEANS, e.g. BATTERIES, FOR THE DIRECT CONVERSION OF CHEMICAL ENERGY INTO ELECTRICAL ENERGY
- H01M10/00—Secondary cells; Manufacture thereof
- H01M10/42—Methods or arrangements for servicing or maintenance of secondary cells or secondary half-cells
-
- H—ELECTRICITY
- H01—ELECTRIC ELEMENTS
- H01M—PROCESSES OR MEANS, e.g. BATTERIES, FOR THE DIRECT CONVERSION OF CHEMICAL ENERGY INTO ELECTRICAL ENERGY
- H01M10/00—Secondary cells; Manufacture thereof
- H01M10/42—Methods or arrangements for servicing or maintenance of secondary cells or secondary half-cells
- H01M10/425—Structural combination with electronic components, e.g. electronic circuits integrated to the outside of the casing
-
- H—ELECTRICITY
- H02—GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
- H02J—CIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
- H02J7/00—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries
- H02J7/00032—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries characterised by data exchange
- H02J7/00036—Charger exchanging data with battery
-
- H—ELECTRICITY
- H02—GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
- H02J—CIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
- H02J7/00—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries
- H02J7/00047—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries with provisions for charging different types of batteries
-
- H—ELECTRICITY
- H01—ELECTRIC ELEMENTS
- H01M—PROCESSES OR MEANS, e.g. BATTERIES, FOR THE DIRECT CONVERSION OF CHEMICAL ENERGY INTO ELECTRICAL ENERGY
- H01M10/00—Secondary cells; Manufacture thereof
- H01M10/42—Methods or arrangements for servicing or maintenance of secondary cells or secondary half-cells
- H01M10/4221—Methods or arrangements for servicing or maintenance of secondary cells or secondary half-cells with battery type recognition
-
- H—ELECTRICITY
- H01—ELECTRIC ELEMENTS
- H01M—PROCESSES OR MEANS, e.g. BATTERIES, FOR THE DIRECT CONVERSION OF CHEMICAL ENERGY INTO ELECTRICAL ENERGY
- H01M10/00—Secondary cells; Manufacture thereof
- H01M10/42—Methods or arrangements for servicing or maintenance of secondary cells or secondary half-cells
- H01M10/425—Structural combination with electronic components, e.g. electronic circuits integrated to the outside of the casing
- H01M2010/4278—Systems for data transfer from batteries, e.g. transfer of battery parameters to a controller, data transferred between battery controller and main controller
-
- Y—GENERAL 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
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02E—REDUCTION OF GREENHOUSE GAS [GHG] EMISSIONS, RELATED TO ENERGY GENERATION, TRANSMISSION OR DISTRIBUTION
- Y02E60/00—Enabling technologies; Technologies with a potential or indirect contribution to GHG emissions mitigation
- Y02E60/10—Energy storage using batteries
Abstract
Multiple battery authentication security levels and procedures alert a user of counterfeit or unapproved batteries that are installed after manufacture of the wireless communication device. In an exemplary a battery authentication system, a mobile device sends a pre-stored plain text to a battery installed in the mobile device. An approved battery receives the plain text and performs an encryption algorithm on the plain text. Encrypted text is sent back to the mobile device. The mobile device compares the received encrypted text with a pre-stored encrypted text. If the received encrypted text matches the pre-stored encrypted text, then the battery is authenticated. Upon completion of the authentication of the installed battery, the mobile phone conducts normal battery and charging operation. If the received encrypted text does not match the pre-stored encrypted text, then the device enters authentication failure events that limit the use of the battery.
Description
BATTERY AUTHENTICATION IN A WIRELESS COMMUNICATION
DEVICE
FIELD OF THE INVENTION
The present invention relates to the field of wireless communication devices.
More specifically, the invention relates to the authentication of a battery installed in a wireless communication device.
BACKGROUND OF THE INVENTION
A typical wireless communication device, such as a mobile phone, comprises, among other things, a processor coupled to a memory and to a transceiver, each enclosed in a housing. A mobile power source, such as a battery, is coupled to and supplies power to the processor, the memory and the transceiver. A speaker and a microphone are also enclosed within the housing for transmitting and receiving, respectively, acoustic signals to and from a user of the wireless communication device. A battery is typically installed in the device at the time of manufacture, and therefore, the manufacture can regulate these "authentic" batteries to ensure correct and safe performance of the batteries in the device. However, there is a growing concern for the mobile phone manufactures regarding the safety of replacement batteries that are later installed by the consumer.
Low quality, unauthenticated or counterfeit batteries, that is, batteries that are not approved by the manufacturers, can pose potential dangers to the device users. For example, counterfeit batteries may malfunction, explode or catch fire and cause injury to the user and damage to the wireless device.
Therefore, a need exists in the wireless communication device industry to implement safety mechanisms in the devices to ensure the use of approved batteries.
SUMMARY OF THE INVENTION
Multiple battery authentication security levels and mobile user interactive interfaces are disclosed which addresses and resolves one or more of the disadvantages associated with counterfeit or unapproved batteries that are installed in wireless communication devices after manufacture of the devices.
By way of illustration, in an exemplary a battery authentication system, a mobile device sends a pre-stored plain text to a battery installed in the mobile device. An approved battery receives the plain text, performs an encryption algorithm on the plain text, and outputs encrypted text. The encrypted text is sent back to the mobile device. The mobile device compares the received encrypted text with a pre-stored encrypted text. If the received encrypted text matches the pre-stored encrypted text, then the battery is authenticated. Upon completion of the authentication of the installed battery, the mobile phone conducts normal battery and charging operation. If the received encrypted text does not match the pre-stored encrypted text, then the device enters authentication failure events that limit the use of the battery.
In accordance with one aspect of the invention, there is provided a method for battery authentication in a wireless communication device with an attached battery. The method involves randomly choosing a pair including plain text and an associated encrypted text from a plurality of pairs of plain text and associated encrypted text stored in the wireless communication device. The method further involves causing the wireless communication device to send the plain text of the randomly chosen pair, to the attached battery and causing the wireless communication device to wait for a first time period after the step of sending to receive encrypted text from the attached battery. If encrypted text is not received within the first time period, then the wireless communication device repeats the steps of (a) and (b) up to a pre-defined number of attempts. If the encrypted text is not received within the first time period, and the pre-defined number of attempts is exhausted, then the wireless communication device enters a battery authentication failure event procedure. If encrypted text is received within the first time period, then the wireless communication device compares the received encrypted text with pre-stored encrypted text that is associated with the plain text, and if the received encrypted text matches the pre-stored encrypted text, the wireless communication device identifies the attached battery as an authentic battery.
If the received encrypted text does not match the pre-stored encrypted text, then the wireless communication device enters the battery authentication failure event procedure.
The method may involve causing the wireless communication device to enter a low power mode that prevents the wireless communication device from initiating and receiving calls.
The method may involve pre-storing the plurality of pairs of plain text and associated encrypted text in the wireless communication device.
The associated encrypted text may be generated by a tool external to the wireless communication device. The tool may use a first encryption algorithm, and the authentic battery may use the first encryption algorithm to generate the encrypted text received by the wireless communication device.
The first encryption algorithm may be a block cipher algorithm.
When a battery authentication security level is at a high level, the battery authentication failure event procedure may involve causing the wireless communication device to display a message in a pop-up window to indicate that the attached battery is not authentic, and causing the wireless communication device to provide an emergency call option in the pop-up window. The method may further involve causing the wireless communication device to power down the wireless communication device if the emergency call option is not selected within a second time period, and causing the wireless communication device to place an emergency call if the emergency call option is selected.
DEVICE
FIELD OF THE INVENTION
The present invention relates to the field of wireless communication devices.
More specifically, the invention relates to the authentication of a battery installed in a wireless communication device.
BACKGROUND OF THE INVENTION
A typical wireless communication device, such as a mobile phone, comprises, among other things, a processor coupled to a memory and to a transceiver, each enclosed in a housing. A mobile power source, such as a battery, is coupled to and supplies power to the processor, the memory and the transceiver. A speaker and a microphone are also enclosed within the housing for transmitting and receiving, respectively, acoustic signals to and from a user of the wireless communication device. A battery is typically installed in the device at the time of manufacture, and therefore, the manufacture can regulate these "authentic" batteries to ensure correct and safe performance of the batteries in the device. However, there is a growing concern for the mobile phone manufactures regarding the safety of replacement batteries that are later installed by the consumer.
Low quality, unauthenticated or counterfeit batteries, that is, batteries that are not approved by the manufacturers, can pose potential dangers to the device users. For example, counterfeit batteries may malfunction, explode or catch fire and cause injury to the user and damage to the wireless device.
Therefore, a need exists in the wireless communication device industry to implement safety mechanisms in the devices to ensure the use of approved batteries.
SUMMARY OF THE INVENTION
Multiple battery authentication security levels and mobile user interactive interfaces are disclosed which addresses and resolves one or more of the disadvantages associated with counterfeit or unapproved batteries that are installed in wireless communication devices after manufacture of the devices.
By way of illustration, in an exemplary a battery authentication system, a mobile device sends a pre-stored plain text to a battery installed in the mobile device. An approved battery receives the plain text, performs an encryption algorithm on the plain text, and outputs encrypted text. The encrypted text is sent back to the mobile device. The mobile device compares the received encrypted text with a pre-stored encrypted text. If the received encrypted text matches the pre-stored encrypted text, then the battery is authenticated. Upon completion of the authentication of the installed battery, the mobile phone conducts normal battery and charging operation. If the received encrypted text does not match the pre-stored encrypted text, then the device enters authentication failure events that limit the use of the battery.
In accordance with one aspect of the invention, there is provided a method for battery authentication in a wireless communication device with an attached battery. The method involves randomly choosing a pair including plain text and an associated encrypted text from a plurality of pairs of plain text and associated encrypted text stored in the wireless communication device. The method further involves causing the wireless communication device to send the plain text of the randomly chosen pair, to the attached battery and causing the wireless communication device to wait for a first time period after the step of sending to receive encrypted text from the attached battery. If encrypted text is not received within the first time period, then the wireless communication device repeats the steps of (a) and (b) up to a pre-defined number of attempts. If the encrypted text is not received within the first time period, and the pre-defined number of attempts is exhausted, then the wireless communication device enters a battery authentication failure event procedure. If encrypted text is received within the first time period, then the wireless communication device compares the received encrypted text with pre-stored encrypted text that is associated with the plain text, and if the received encrypted text matches the pre-stored encrypted text, the wireless communication device identifies the attached battery as an authentic battery.
If the received encrypted text does not match the pre-stored encrypted text, then the wireless communication device enters the battery authentication failure event procedure.
The method may involve causing the wireless communication device to enter a low power mode that prevents the wireless communication device from initiating and receiving calls.
The method may involve pre-storing the plurality of pairs of plain text and associated encrypted text in the wireless communication device.
The associated encrypted text may be generated by a tool external to the wireless communication device. The tool may use a first encryption algorithm, and the authentic battery may use the first encryption algorithm to generate the encrypted text received by the wireless communication device.
The first encryption algorithm may be a block cipher algorithm.
When a battery authentication security level is at a high level, the battery authentication failure event procedure may involve causing the wireless communication device to display a message in a pop-up window to indicate that the attached battery is not authentic, and causing the wireless communication device to provide an emergency call option in the pop-up window. The method may further involve causing the wireless communication device to power down the wireless communication device if the emergency call option is not selected within a second time period, and causing the wireless communication device to place an emergency call if the emergency call option is selected.
The step of placing an emergency call may involve causing the wireless communication device to enter an emergency call back mode, and causing the wireless communication device to allow the attached battery to drain. The method may further involve causing the wireless communication device to block normal battery charging operations, and causing the wireless communication device to enter a low power mode.
When a battery authentication security level is at a medium level, the battery authentication failure event procedure may involve causing the wireless communication device to display a message in a pop-up window to indicate that the attached battery is not authentic, and causing the wireless communication device to receive a message acknowledgement. The method may further involve causing the battery to conduct normal battery operations and causing the wireless. communication device to cause normal battery charging operations to be blocked.
When battery authentication security level is at a low level, the battery authentication failure event procedure may involve causing the wireless communication device to display a message in a pop-up window to indicate that the attached battery is not authentic, and causing the wireless communication device to receive a message acknowledgement. The method may further involve causing the battery to conduct normal battery operations and causing the wireless communication device to cause normal battery charging operations to be conducted.
The method may involve causing the attached battery to receive the plain text from the wireless communication device, and causing the attached battery to run an encryption algorithm on the received plain text to produce encrypted text. The method may further involve causing the attached battery to send the encrypted text to the wireless communication device, and causing the attached battery to power the wireless communication device for normal operations if the wireless communication device identifies the attached battery as authentic based upon the encrypted text sent from the battery.
When a battery authentication security level is at a medium level, the battery authentication failure event procedure may involve causing the wireless communication device to display a message in a pop-up window to indicate that the attached battery is not authentic, and causing the wireless communication device to receive a message acknowledgement. The method may further involve causing the battery to conduct normal battery operations and causing the wireless. communication device to cause normal battery charging operations to be blocked.
When battery authentication security level is at a low level, the battery authentication failure event procedure may involve causing the wireless communication device to display a message in a pop-up window to indicate that the attached battery is not authentic, and causing the wireless communication device to receive a message acknowledgement. The method may further involve causing the battery to conduct normal battery operations and causing the wireless communication device to cause normal battery charging operations to be conducted.
The method may involve causing the attached battery to receive the plain text from the wireless communication device, and causing the attached battery to run an encryption algorithm on the received plain text to produce encrypted text. The method may further involve causing the attached battery to send the encrypted text to the wireless communication device, and causing the attached battery to power the wireless communication device for normal operations if the wireless communication device identifies the attached battery as authentic based upon the encrypted text sent from the battery.
In accordance with another aspect of the invention, there is provided a computer readable medium encoded with codes for directing a processor in a wireless communication device with an attached battery to execute the method and/or any of its variations mentioned above.
In accordance with another aspect of the invention, there is provided a wireless communication device having an attached battery. The wireless communication device includes a processor circuit and the computer-readable medium mentioned above, and the computer readable medium is in communication with the processor circuit to cause the processor circuit to execute the method and/or any of its variations above in response to the codes encoded on the computer readable medium.
In accordance with another aspect of the invention, there is provided a wireless communication device. The device includes a memory for pre-storing a plurality of pairs of plain text and associated encrypted text, the pre-stored associated encrypted text having been generated by a tool external to the wireless communication device that utilizes an encryption algorithm. The device further includes a processor coupled to the memory for randomly choosing a pair of the plain text and its associated encrypted text from the plurality of pairs, for sending to an attachable battery. The device further includes a transceiver coupled to the processor, an input device coupled to the processor, and a display coupled to the processor. The attachable battery is coupled to the processor. The device further includes a computer-readable medium encoded with codes for directing the processor to (a) send the plain text of the randomly chosen pair to the attachable battery, wherein if the attachable battery is authentic, then the authentic battery includes a processing device for running the encryption algorithm on the plain text to produce an encrypted text, (b) wait for a first time period to receive the encrypted text from the attachable battery, (c) repeat steps (a) and (b) a pre-defined number of attempts if encrypted text is not received within the first time period, (d) if encrypted text is not received within the first time period and the pre-defined number of attempts is exhausted, then enter a battery authentication failure event procedure, (e) if encrypted text is received within the first time period, then compare the received encrypted text with the pre-stored encrypted text that is associated with the plain text, (f) if the received encrypted text matches the pre-stored encrypted text, then identify the attached battery as an authentic battery, and (g) if the received encrypted text does not match the pre-stored encrypted text, then enter the battery authentication failure event procedure.
The computer readable medium may include codes for directing the processor to execute the battery authentication failure event procedure when a battery authentication security level is at a high level, the authentication failure event procedure being defined by codes stored on the computer readable medium that direct the processor to cause a message to appear in a pop-up window on the display to indicate that the attachable battery is not authentic and provide an emergency call option in the pop-up window, power down the wireless communication device if the emergency call option is not selected within a second time period, and place an emergency call if the emergency call option is selected.
The codes for directing the processor to place an emergency call may include codes for directing the processor to enter an emergency call back mode, allowing the attachable battery to drain, blocking normal battery charging operations, and entering a low power mode.
The computer readable medium may include codes for directing the processor to execute the battery authentication failure event procedure when a battery authentication security level is at a medium level. The authentication failure event procedure is defined by codes stored on the computer readable medium that direct the processor to cause a message to appear in a pop-up window on the display to indicate that the attachable battery is not authentic, receive a message acknowledgement, conduct normal battery operations, and block normal battery charging operations.
The computer readable medium may include codes for directing the processor to execute the battery authentication failure event procedure when a battery authentication security level is at a low level. The battery authentication failure event procedure is defined by codes stored on the computer readable medium that direct the processor to cause a message to appear in a pop-up window on the display to indicate that the attachable battery is not authentic, receive a message acknowledgement, conduct normal battery operations, and conduct normal battery charging operations.
Other features and advantages of the present invention will become more readily apparent to those of ordinary skill in the art after reviewing the following detailed description and accompanying drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
Figure 1 illustrates an exemplary method and device for providing battery authentication in a wireless communication device according to one embodiment of the present invention.
Figure 2 is a table showing capabilities of the wireless communication device for various battery authentication levels according to an embodiment of the present invention.
Figure 3 is a flow diagram of an exemplary method of battery authentication for a battery authentication level set to "high" according to one embodiment of the present invention.
Figure 4 is a flow diagram of an exemplary method of battery authentication for a battery authentication level set to "medium" according to one embodiment of the present invention.
Figure 5 is a flow diagram of an exemplary method of battery authentication for a battery authentication level set to "low" according to one embodiment of the present invention.
In accordance with another aspect of the invention, there is provided a wireless communication device having an attached battery. The wireless communication device includes a processor circuit and the computer-readable medium mentioned above, and the computer readable medium is in communication with the processor circuit to cause the processor circuit to execute the method and/or any of its variations above in response to the codes encoded on the computer readable medium.
In accordance with another aspect of the invention, there is provided a wireless communication device. The device includes a memory for pre-storing a plurality of pairs of plain text and associated encrypted text, the pre-stored associated encrypted text having been generated by a tool external to the wireless communication device that utilizes an encryption algorithm. The device further includes a processor coupled to the memory for randomly choosing a pair of the plain text and its associated encrypted text from the plurality of pairs, for sending to an attachable battery. The device further includes a transceiver coupled to the processor, an input device coupled to the processor, and a display coupled to the processor. The attachable battery is coupled to the processor. The device further includes a computer-readable medium encoded with codes for directing the processor to (a) send the plain text of the randomly chosen pair to the attachable battery, wherein if the attachable battery is authentic, then the authentic battery includes a processing device for running the encryption algorithm on the plain text to produce an encrypted text, (b) wait for a first time period to receive the encrypted text from the attachable battery, (c) repeat steps (a) and (b) a pre-defined number of attempts if encrypted text is not received within the first time period, (d) if encrypted text is not received within the first time period and the pre-defined number of attempts is exhausted, then enter a battery authentication failure event procedure, (e) if encrypted text is received within the first time period, then compare the received encrypted text with the pre-stored encrypted text that is associated with the plain text, (f) if the received encrypted text matches the pre-stored encrypted text, then identify the attached battery as an authentic battery, and (g) if the received encrypted text does not match the pre-stored encrypted text, then enter the battery authentication failure event procedure.
The computer readable medium may include codes for directing the processor to execute the battery authentication failure event procedure when a battery authentication security level is at a high level, the authentication failure event procedure being defined by codes stored on the computer readable medium that direct the processor to cause a message to appear in a pop-up window on the display to indicate that the attachable battery is not authentic and provide an emergency call option in the pop-up window, power down the wireless communication device if the emergency call option is not selected within a second time period, and place an emergency call if the emergency call option is selected.
The codes for directing the processor to place an emergency call may include codes for directing the processor to enter an emergency call back mode, allowing the attachable battery to drain, blocking normal battery charging operations, and entering a low power mode.
The computer readable medium may include codes for directing the processor to execute the battery authentication failure event procedure when a battery authentication security level is at a medium level. The authentication failure event procedure is defined by codes stored on the computer readable medium that direct the processor to cause a message to appear in a pop-up window on the display to indicate that the attachable battery is not authentic, receive a message acknowledgement, conduct normal battery operations, and block normal battery charging operations.
The computer readable medium may include codes for directing the processor to execute the battery authentication failure event procedure when a battery authentication security level is at a low level. The battery authentication failure event procedure is defined by codes stored on the computer readable medium that direct the processor to cause a message to appear in a pop-up window on the display to indicate that the attachable battery is not authentic, receive a message acknowledgement, conduct normal battery operations, and conduct normal battery charging operations.
Other features and advantages of the present invention will become more readily apparent to those of ordinary skill in the art after reviewing the following detailed description and accompanying drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
Figure 1 illustrates an exemplary method and device for providing battery authentication in a wireless communication device according to one embodiment of the present invention.
Figure 2 is a table showing capabilities of the wireless communication device for various battery authentication levels according to an embodiment of the present invention.
Figure 3 is a flow diagram of an exemplary method of battery authentication for a battery authentication level set to "high" according to one embodiment of the present invention.
Figure 4 is a flow diagram of an exemplary method of battery authentication for a battery authentication level set to "medium" according to one embodiment of the present invention.
Figure 5 is a flow diagram of an exemplary method of battery authentication for a battery authentication level set to "low" according to one embodiment of the present invention.
Figure 6 illustrates an exemplary detailed embodiment of the method of Figure 1 for providing battery authentication in a wireless communication device.
Figure 7 is a block diagram of an exemplary battery authentication system according to one embodiment of the present invention.
DETAILED DESCRIPTION
Battery authentication is a process in which the authenticity of the battery in use in a wireless communication device is identified specifically, as an approved device or as an unapproved device. Figure 1 illustrates a simplified exemplary battery authentication system 10 according to one embodiment of the invention. The illustrated embodiment 10 utilizes a cipher technology approach in which the battery 14 in test returns cipher text 20, also referred to herein as encrypted text, to the wireless device 12 in response to a plain text input 16 sent by the wireless communication device 12. The battery 14 utilizes an encrypting algorithm 18 on plain text received from the wireless communication device 12. Cipher text 20 is output from the battery 14 to the wireless communication device 12. Upon receiving the cipher text 20 from the battery 14, the wireless communication device 12 determines whether the cipher text 20 is correct by comparing the received cipher text 20 with pre-stored cipher text that is stored in a memory of the device 12, block 22. The pre-stored cipher text is generated by the same encrypting algorithm used by the battery 14.
An exemplary encryption algorithm 18 that may be utilized in an embodiment of battery authentication is a block cipher. A block cipher is a symmetric key cipher which operates on groups of bits with fixed lengths, i.e., "blocks", with an unvarying transformation. For example, during encryption, a block of plain text is input into a block cipher. The block cipher outputs a corresponding block of cipher text. The exact transformation is controlled using a key that is also provided to the block cipher. Decryption in the wireless device is accomplished by a similar process in which the decryption algorithm accepts the block of cipher text together with the key, and outputs the original block of plain text. An encryption algorithm may be performed utilizing firmware or software or other suitable techniques.
Figure 6 illustrates a battery authentication method 100 according to one embodiment of the invention. In block 102, plain and encrypted texts are supplied to the wireless communication device for use with the battery authentication method. Encrypted texts also are referred to herein as cipher texts. For security issues, an encryption algorithm and a key do not reside in the device. Instead, a separate tool generates two pairs of a plain text and a corresponding encrypted text using an encryption algorithm. The two pairs are provided with each mobile during provisioning. Since the plain text is a number that is generated randomly, each device is expected to have two distinct pairs of plain texts and encrypted texts. This minimizes any attempt to bypass the algorithm by extracting the encrypted text and attempting to use it on other mobiles.
Continuing with block 104 of Figure 6, battery authentication events trigger the device to perform the procedures to verify the authenticity of the battery in use. In one embodiment of the method, preconditions are assumed as follows: a battery is not attached to the mobile device and no external power source is connected to the mobile device. Given this precondition, there can be various triggering events for battery authentication. A first triggering event occurs if the user attaches a battery to the wireless device and powers on the device. In another triggering event, the user attaches a battery to the mobile device which is in the power down state. The user then connects an external power source to the mobile. In another triggering scenario, an external power source is connected to the device without a battery attached. The user then attaches a battery to the device.
Upon sensing one of the battery authentication triggering events, the mobile device enters into a low power mode, and remains in the low power mode throughout the verification procedure. The low power mode prevents the mobile device from originating and terminating calls during the battery authentication procedure. A variable which indicates battery authentication attempts is set to zero, block 106, for example, "BA(attempts)" = 0. The device fetches a pair of the pre-stored plain and cipher texts from the device database in a random manner. In block 108, the device sends the plain text 110 through a serial communication link through, a connector 376, also shown in Figure 7, to the battery. According to one embodiment of the invention, the communication link is a Universal Asynchronous Receiver/Transmitter (UART).
The mobile device then increments the battery authentication attempts counter and starts a timer, block 112. If encrypted text 136 is not received from the battery within a pre-determined time limit T(BAI), as shown by decision block 114, then the mobile determines the current number of authentication attempts, block 122. In the exemplary embodiment of Figure 2, the number of acceptable attempts is shown as two. That is, if the number of attempts equals or exceeds two, then the mobile device enters battery authentication failure events, block 124. However, it should be understood that the number of acceptable attempts may be increased or decreased according to other embodiments of the invention. For example, re-sending the plain text and the key is desirable to account for possible communication errors between the mobile device and the battery. According to one embodiment of the invention, the time limit T(BA1) is approximately 150 msec.
However, the time limit of other embodiments may be lower or higher depending on phone configuration. If the number of attempts is less than the predetermined limit, block 122, then the mobile device resends the pre-stored plain text to the battery, block 108, and continues in the loop until the number of allowed attempts is exceeded, or until the battery returns encrypted text to the mobile device, block 114.
Continuing with block 116, if the encrypted text is received within the predetermined time limit T(BA1), then the device compares the received encrypted text with the pre-stored encrypted text. In block 118, if the received encrypted text matches the pre-stored encrypted text, then the battery is authentic and normal battery and charging operations can proceed, block 120.
Figure 7 is a block diagram of an exemplary battery authentication system according to one embodiment of the present invention.
DETAILED DESCRIPTION
Battery authentication is a process in which the authenticity of the battery in use in a wireless communication device is identified specifically, as an approved device or as an unapproved device. Figure 1 illustrates a simplified exemplary battery authentication system 10 according to one embodiment of the invention. The illustrated embodiment 10 utilizes a cipher technology approach in which the battery 14 in test returns cipher text 20, also referred to herein as encrypted text, to the wireless device 12 in response to a plain text input 16 sent by the wireless communication device 12. The battery 14 utilizes an encrypting algorithm 18 on plain text received from the wireless communication device 12. Cipher text 20 is output from the battery 14 to the wireless communication device 12. Upon receiving the cipher text 20 from the battery 14, the wireless communication device 12 determines whether the cipher text 20 is correct by comparing the received cipher text 20 with pre-stored cipher text that is stored in a memory of the device 12, block 22. The pre-stored cipher text is generated by the same encrypting algorithm used by the battery 14.
An exemplary encryption algorithm 18 that may be utilized in an embodiment of battery authentication is a block cipher. A block cipher is a symmetric key cipher which operates on groups of bits with fixed lengths, i.e., "blocks", with an unvarying transformation. For example, during encryption, a block of plain text is input into a block cipher. The block cipher outputs a corresponding block of cipher text. The exact transformation is controlled using a key that is also provided to the block cipher. Decryption in the wireless device is accomplished by a similar process in which the decryption algorithm accepts the block of cipher text together with the key, and outputs the original block of plain text. An encryption algorithm may be performed utilizing firmware or software or other suitable techniques.
Figure 6 illustrates a battery authentication method 100 according to one embodiment of the invention. In block 102, plain and encrypted texts are supplied to the wireless communication device for use with the battery authentication method. Encrypted texts also are referred to herein as cipher texts. For security issues, an encryption algorithm and a key do not reside in the device. Instead, a separate tool generates two pairs of a plain text and a corresponding encrypted text using an encryption algorithm. The two pairs are provided with each mobile during provisioning. Since the plain text is a number that is generated randomly, each device is expected to have two distinct pairs of plain texts and encrypted texts. This minimizes any attempt to bypass the algorithm by extracting the encrypted text and attempting to use it on other mobiles.
Continuing with block 104 of Figure 6, battery authentication events trigger the device to perform the procedures to verify the authenticity of the battery in use. In one embodiment of the method, preconditions are assumed as follows: a battery is not attached to the mobile device and no external power source is connected to the mobile device. Given this precondition, there can be various triggering events for battery authentication. A first triggering event occurs if the user attaches a battery to the wireless device and powers on the device. In another triggering event, the user attaches a battery to the mobile device which is in the power down state. The user then connects an external power source to the mobile. In another triggering scenario, an external power source is connected to the device without a battery attached. The user then attaches a battery to the device.
Upon sensing one of the battery authentication triggering events, the mobile device enters into a low power mode, and remains in the low power mode throughout the verification procedure. The low power mode prevents the mobile device from originating and terminating calls during the battery authentication procedure. A variable which indicates battery authentication attempts is set to zero, block 106, for example, "BA(attempts)" = 0. The device fetches a pair of the pre-stored plain and cipher texts from the device database in a random manner. In block 108, the device sends the plain text 110 through a serial communication link through, a connector 376, also shown in Figure 7, to the battery. According to one embodiment of the invention, the communication link is a Universal Asynchronous Receiver/Transmitter (UART).
The mobile device then increments the battery authentication attempts counter and starts a timer, block 112. If encrypted text 136 is not received from the battery within a pre-determined time limit T(BAI), as shown by decision block 114, then the mobile determines the current number of authentication attempts, block 122. In the exemplary embodiment of Figure 2, the number of acceptable attempts is shown as two. That is, if the number of attempts equals or exceeds two, then the mobile device enters battery authentication failure events, block 124. However, it should be understood that the number of acceptable attempts may be increased or decreased according to other embodiments of the invention. For example, re-sending the plain text and the key is desirable to account for possible communication errors between the mobile device and the battery. According to one embodiment of the invention, the time limit T(BA1) is approximately 150 msec.
However, the time limit of other embodiments may be lower or higher depending on phone configuration. If the number of attempts is less than the predetermined limit, block 122, then the mobile device resends the pre-stored plain text to the battery, block 108, and continues in the loop until the number of allowed attempts is exceeded, or until the battery returns encrypted text to the mobile device, block 114.
Continuing with block 116, if the encrypted text is received within the predetermined time limit T(BA1), then the device compares the received encrypted text with the pre-stored encrypted text. In block 118, if the received encrypted text matches the pre-stored encrypted text, then the battery is authentic and normal battery and charging operations can proceed, block 120.
According to one embodiment, the battery authentication process is transparent to the user if the authenticity of the battery is identified as genuine. If the received encrypted text does not match the pre-stored encrypted text, block 118, then the device determines whether the number of attempts has exceeded the allowed limit, block 122. If the number of allowed attempts has exceeded the limit, the mobile device executes block 124 to enter battery authentication failure events, which are discussed further with references to Figures 3, 4 and 5. If the number of allowed attempts has not exceeded the allowed limit, block 122, then the mobile device resends the pre-stored plain text to the battery, block 108, and continues the loop until the number of allowed attempts is exceeded, or until the battery returns the expected encrypted text.
Continuing with Figure 6 from the perspective of the battery, the battery receives plain text from the mobile device, block 130. The battery runs an encryption algorithm on the plain text, block 132. The encryption algorithm is the same algorithm used to generate the pre-stored encrypted text that is stored in the mobile device. The battery then sends the encrypted text 136 to the mobile device, block 134. As discussed above, the mobile device does not store the encryption algorithm. Rather the plain text and the encrypted text are generated from another source and stored in the phone during provisioning of the mobile phone.
Once the installed battery is identified as counterfeit, that is, the battery authentication fails, the mobile handset will follow different security procedures based upon the security levels set by the service provider's needs while provisioning the mobile handset. The user also is provided with warning pop-up messages with different options based on the security level setting.
The security level is used to set different levels of the battery security including disabling the battery authentication feature.
A security level table 30 of Figure 2, illustrates battery authentication security levels and mobile phone capabilities when the battery is identified as a counterfeit. This feature allows service providers to apply different security levels to meet their specific market needs. As shown in Figure 2, the battery security level settings 32 can be "high", "medium", "low" or "disabled". This setting can be configured during provisioning of the mobile device. According to one embodiment, the authentication process can be disabled through the user interface with proper security access. The battery discharge column 34 indicates whether the battery is allowed to discharge for a particular security level. That is, if the battery is allowed to discharge, then the phone can be used for initiating and receiving calls. The battery charge column 36 indicates whether the battery is permitted to be charged for a particular security level.
The E911 column 38 indicates whether an E911 call can be made, whether the mobile can originate a call (MO, mobile origination), and whether a mobile can accept incoming calls (MT, mobile terminating). The warning message column 40 indicates whether the mobile device will display a warning message to the user that the installed battery is not an authentic battery and that power down may occur with the exception that power will be provided for making an E911 call.
Continuing with the security level table 30, if the security level setting is set to "disabled", then the battery can be used to power the mobile, the battery can be charged, E911 calls are enabled, the mobile phone can initiate calls and receive incoming calls, and the mobile does. not display warning messages.
According to one embodiment of the invention, if the battery authentication level is set to "disabled" then the mobile device does not send a plain text to perform the battery authentication procedure. In an alternate embodiments, battery authentication may proceed, for example, in a background procedure that is transparent to the user.
If the security level setting is set to "low", then the battery can be used to power the mobile, the battery can be charged, E911 calls are enabled, the mobile phone can initiate calls and receive incoming calls, and the mobile does display warning messages that the battery is not authentic. If the security level setting is set to "medium", then the battery can be used to power the mobile, the battery cannot be charged, E911 calls are enabled, the mobile phone can initiate calls and receive incoming calls, and the mobile displays a warning message that the battery is not authentic. If the security level setting is set to "high", then the battery is only used to power the mobile when an E911 call is made, the battery cannot be charged, E911 calls are enabled, the mobile phone cannot initiate calls and cannot receive incoming calls, and the mobile does display warning messages that the battery is not authentic. In addition to message display, embodiments of battery authentication may provide an audible alert sound if the battery is not authentic.
The battery authentication failure events of block 124 of Figure 6 are described in detail with reference to Figures 3, 4 and 5. Figure 3 illustrates a failure event method for a battery authentication security level set to "high".
Starting in block 41, the mobile has entered a battery authentication failure event with a security level set to high. The device remains in a lower power mode from the battery authentication process. The mobile device displays a pop-up window informing the user that the installed battery is not authentic and that the device cannot be used for normal purposes, block 42. However, in case of an emergency, the pop-up window provides an option for the user to make an E911 call. In block 44, a timer T(BA2) is started.
The device then determines whether a pre-determined time period T(BA2) has expired or whether an emergency call has been made, block 46. If the pre-determined time has expired, the mobile device automatically powers down and battery re-charging is not allowed, block 50. According to one embodiment of the invention, the pop-up window clears after the timer, T(BA2), expires. According to an exemplary embodiment of the invention, if a device user dials E911 to make an emergency call, upon the first digit entry, the mobile clears the pop-up window and exits the low power mode, block 48.
The battery is allowed to drain, but charging of the battery is not allowed.
The mobile device then enters the system determination state as directed by the preferred roaming list (PRL), and acquires a system. The E911 call is placed upon service availability, block 52. The phone then enters emergency call back mode (ECBM) if applicable, block 54. The device then re-enters low power mode, block 56. In ECBM, the device idles on a system to stay available for a call back from a local Public Safety Answering Point (PSAP).
If the user exits the emergency call back mode after placing the E911 call, then the device powers down.
In some circumstances, the user may connect an external power source to the mobile phone during the battery authentication process. If the external power source uses a low power adapter, the mobile remains in the low power mode since the low power adapter cannot provide sufficient power to allow a call to be initiated. If the external power source is connected using a high power adapter, then the mobile clears the pop-up window upon detection of the external power source. The mobile then is operational using the external power source, and the mobile does not charge the battery. According to one embodiment of the invention, the mobile powers down if the user disconnects the external power source.
Referring to Figure 4, the device has entered a battery authentication failure event for a medium security level, block 60. The mobile device displays a pop-up window with a message informing the user that the installed battery is not authentic, block 62. The window also provides a soft-key option "OK". The device waits for the user to acknowledge the message. If the user presses the 'OK' soft key, block 64, the pop-up window is cleared, block 66, and the device exits low power mode and enters the system determination state as directed by the PRL. For the medium security level, the battery is allowed to drain and the mobile device operates as normal with the authentication-failed battery. However, if an external power source is connected, the mobile operates from the external source, but the battery is not charged.
Figure 5 illustrates battery authentication failure event procedures when the battery security level is set to low. In block 70, the mobile has entered the battery authentication failure event. The mobile device displays a pop-up window informing the user that installed battery is not authentic, block 72.
The pop-up window also provides an "OK" soft key to prompt the user to acknowledge the message regarding the battery. If the soft key is selected, block 74, then the device clears the pop-up window and exits the low power mode. Normal battery and charging operations are allowed to proceed, block 76, and the mobile device enters the system determination state as directed by the PRL.
Figure 7 is a block diagram illustrating an exemplary wireless communications device 350 that may be used in connection with the various embodiments described herein. For example, the wireless communications device 350 may be used in conjunction with a handset or PDA network device. However, other wireless communications devices and/or architectures may also be used, as will be clear to those skilled in the art.
In the illustrated embodiment, wireless communications device 350 comprises an antenna 352, a multiplexor 354, a low noise amplifier ("LNA") 356, a power amplifier ("PA") 358, a modulation circuit 360, a baseband processor 362, a speaker 364, a microphone 366, a processor 368, a data storage area 370, a power circuit 374, and a hardware interface 372. Various user interface devices (not shown), such as keypads and display devices, may be communicably couple to hardware interface 372 for receiving user input and communicating output messages. In the wireless communications device 350, radio frequency ("RF") signals are transmitted and received by antenna 352.
Elements 354, 356, 358, and 360 may be collectively referred to as a transceiver.
Multiplexor 354 acts as a switch, coupling antenna 352 between the transmit and receive signal paths. In the receive path, received RF signals are coupled from a multiplexor 354 to LNA 356. LNA 356 amplifies the received RF signal and couples the amplified signal to a demodulation portion of the modulation circuit 360. The demodulator strips away the RF carrier signal leaving a baseband receive signal, which is sent from the demodulator output to the baseband processor 362.
If the baseband receive audio signal contains audio information, then baseband processor 362 decodes the signal and converts it to an analog signal. Then the signal is amplified and sent to the speaker 364. The baseband processor 362 also receives analog audio signals from the microphone 366. These analog audio signals are converted to digital signals and encoded by the baseband processor 362. The baseband processor 362 also codes the digital signals for transmission and generates a baseband transmit audio signal that is routed to the modulator portion of modulation circuit 360. The modulator mixes the baseband transmit audio signal with an RF carrier signal generating an RF transmit signal that is routed to the power amplifier 358. The power amplifier 358 amplifies the RF transmit signal and routes it to the multiplexor 354 where the signal is switched to the antenna port for transmission by antenna 352.
The baseband processor 362 is also communicatively coupled with the processor 368. The processor 368 has access to a data storage area 370.
The processor 368 is preferably configured to execute instructions embodied in software such as the methods of Figures 1 through 6 that can be stored in the data storage area 370. A battery 384 is connected to the power circuit 374 through the connector 376. The battery 384 is typically housed within the device in a recessed compartment 386. An external power source (not shown) can also be connected through a connector 378 to provide power to the device and to re-charge the battery 384. The battery 384 includes a processor-type element 388 which runs the encryption algorithm of block 132, as shown in Figure 6.
The present invention further relates to machine readable media on which are stored embodiments of the present invention. It is contemplated that any media suitable for storing instructions is within the scope of the present invention. By way of example, such media may take the form of magnetic, optical, or semiconductor media. The invention also relates to data structures that contain embodiments of the present invention, and to the transmission of data structures containing embodiments of the present invention.
From the above description of exemplary embodiments of the invention, it is manifest that various techniques can be used for implementing the concepts of the present invention without departing from its scope. Moreover, while the invention has been described with specific reference to certain embodiments, a person of ordinary skill in the art would recognize that changes could be made in form and detail without departing from the spirit and the scope of the invention. The described exemplary embodiments are to be considered in all respects as illustrative and not restrictive. It should also be understood that the invention is not limited to the particular exemplary embodiments described herein, but is capable of many rearrangements, modifications, and substitutions without departing from the scope of the invention.
Continuing with Figure 6 from the perspective of the battery, the battery receives plain text from the mobile device, block 130. The battery runs an encryption algorithm on the plain text, block 132. The encryption algorithm is the same algorithm used to generate the pre-stored encrypted text that is stored in the mobile device. The battery then sends the encrypted text 136 to the mobile device, block 134. As discussed above, the mobile device does not store the encryption algorithm. Rather the plain text and the encrypted text are generated from another source and stored in the phone during provisioning of the mobile phone.
Once the installed battery is identified as counterfeit, that is, the battery authentication fails, the mobile handset will follow different security procedures based upon the security levels set by the service provider's needs while provisioning the mobile handset. The user also is provided with warning pop-up messages with different options based on the security level setting.
The security level is used to set different levels of the battery security including disabling the battery authentication feature.
A security level table 30 of Figure 2, illustrates battery authentication security levels and mobile phone capabilities when the battery is identified as a counterfeit. This feature allows service providers to apply different security levels to meet their specific market needs. As shown in Figure 2, the battery security level settings 32 can be "high", "medium", "low" or "disabled". This setting can be configured during provisioning of the mobile device. According to one embodiment, the authentication process can be disabled through the user interface with proper security access. The battery discharge column 34 indicates whether the battery is allowed to discharge for a particular security level. That is, if the battery is allowed to discharge, then the phone can be used for initiating and receiving calls. The battery charge column 36 indicates whether the battery is permitted to be charged for a particular security level.
The E911 column 38 indicates whether an E911 call can be made, whether the mobile can originate a call (MO, mobile origination), and whether a mobile can accept incoming calls (MT, mobile terminating). The warning message column 40 indicates whether the mobile device will display a warning message to the user that the installed battery is not an authentic battery and that power down may occur with the exception that power will be provided for making an E911 call.
Continuing with the security level table 30, if the security level setting is set to "disabled", then the battery can be used to power the mobile, the battery can be charged, E911 calls are enabled, the mobile phone can initiate calls and receive incoming calls, and the mobile does. not display warning messages.
According to one embodiment of the invention, if the battery authentication level is set to "disabled" then the mobile device does not send a plain text to perform the battery authentication procedure. In an alternate embodiments, battery authentication may proceed, for example, in a background procedure that is transparent to the user.
If the security level setting is set to "low", then the battery can be used to power the mobile, the battery can be charged, E911 calls are enabled, the mobile phone can initiate calls and receive incoming calls, and the mobile does display warning messages that the battery is not authentic. If the security level setting is set to "medium", then the battery can be used to power the mobile, the battery cannot be charged, E911 calls are enabled, the mobile phone can initiate calls and receive incoming calls, and the mobile displays a warning message that the battery is not authentic. If the security level setting is set to "high", then the battery is only used to power the mobile when an E911 call is made, the battery cannot be charged, E911 calls are enabled, the mobile phone cannot initiate calls and cannot receive incoming calls, and the mobile does display warning messages that the battery is not authentic. In addition to message display, embodiments of battery authentication may provide an audible alert sound if the battery is not authentic.
The battery authentication failure events of block 124 of Figure 6 are described in detail with reference to Figures 3, 4 and 5. Figure 3 illustrates a failure event method for a battery authentication security level set to "high".
Starting in block 41, the mobile has entered a battery authentication failure event with a security level set to high. The device remains in a lower power mode from the battery authentication process. The mobile device displays a pop-up window informing the user that the installed battery is not authentic and that the device cannot be used for normal purposes, block 42. However, in case of an emergency, the pop-up window provides an option for the user to make an E911 call. In block 44, a timer T(BA2) is started.
The device then determines whether a pre-determined time period T(BA2) has expired or whether an emergency call has been made, block 46. If the pre-determined time has expired, the mobile device automatically powers down and battery re-charging is not allowed, block 50. According to one embodiment of the invention, the pop-up window clears after the timer, T(BA2), expires. According to an exemplary embodiment of the invention, if a device user dials E911 to make an emergency call, upon the first digit entry, the mobile clears the pop-up window and exits the low power mode, block 48.
The battery is allowed to drain, but charging of the battery is not allowed.
The mobile device then enters the system determination state as directed by the preferred roaming list (PRL), and acquires a system. The E911 call is placed upon service availability, block 52. The phone then enters emergency call back mode (ECBM) if applicable, block 54. The device then re-enters low power mode, block 56. In ECBM, the device idles on a system to stay available for a call back from a local Public Safety Answering Point (PSAP).
If the user exits the emergency call back mode after placing the E911 call, then the device powers down.
In some circumstances, the user may connect an external power source to the mobile phone during the battery authentication process. If the external power source uses a low power adapter, the mobile remains in the low power mode since the low power adapter cannot provide sufficient power to allow a call to be initiated. If the external power source is connected using a high power adapter, then the mobile clears the pop-up window upon detection of the external power source. The mobile then is operational using the external power source, and the mobile does not charge the battery. According to one embodiment of the invention, the mobile powers down if the user disconnects the external power source.
Referring to Figure 4, the device has entered a battery authentication failure event for a medium security level, block 60. The mobile device displays a pop-up window with a message informing the user that the installed battery is not authentic, block 62. The window also provides a soft-key option "OK". The device waits for the user to acknowledge the message. If the user presses the 'OK' soft key, block 64, the pop-up window is cleared, block 66, and the device exits low power mode and enters the system determination state as directed by the PRL. For the medium security level, the battery is allowed to drain and the mobile device operates as normal with the authentication-failed battery. However, if an external power source is connected, the mobile operates from the external source, but the battery is not charged.
Figure 5 illustrates battery authentication failure event procedures when the battery security level is set to low. In block 70, the mobile has entered the battery authentication failure event. The mobile device displays a pop-up window informing the user that installed battery is not authentic, block 72.
The pop-up window also provides an "OK" soft key to prompt the user to acknowledge the message regarding the battery. If the soft key is selected, block 74, then the device clears the pop-up window and exits the low power mode. Normal battery and charging operations are allowed to proceed, block 76, and the mobile device enters the system determination state as directed by the PRL.
Figure 7 is a block diagram illustrating an exemplary wireless communications device 350 that may be used in connection with the various embodiments described herein. For example, the wireless communications device 350 may be used in conjunction with a handset or PDA network device. However, other wireless communications devices and/or architectures may also be used, as will be clear to those skilled in the art.
In the illustrated embodiment, wireless communications device 350 comprises an antenna 352, a multiplexor 354, a low noise amplifier ("LNA") 356, a power amplifier ("PA") 358, a modulation circuit 360, a baseband processor 362, a speaker 364, a microphone 366, a processor 368, a data storage area 370, a power circuit 374, and a hardware interface 372. Various user interface devices (not shown), such as keypads and display devices, may be communicably couple to hardware interface 372 for receiving user input and communicating output messages. In the wireless communications device 350, radio frequency ("RF") signals are transmitted and received by antenna 352.
Elements 354, 356, 358, and 360 may be collectively referred to as a transceiver.
Multiplexor 354 acts as a switch, coupling antenna 352 between the transmit and receive signal paths. In the receive path, received RF signals are coupled from a multiplexor 354 to LNA 356. LNA 356 amplifies the received RF signal and couples the amplified signal to a demodulation portion of the modulation circuit 360. The demodulator strips away the RF carrier signal leaving a baseband receive signal, which is sent from the demodulator output to the baseband processor 362.
If the baseband receive audio signal contains audio information, then baseband processor 362 decodes the signal and converts it to an analog signal. Then the signal is amplified and sent to the speaker 364. The baseband processor 362 also receives analog audio signals from the microphone 366. These analog audio signals are converted to digital signals and encoded by the baseband processor 362. The baseband processor 362 also codes the digital signals for transmission and generates a baseband transmit audio signal that is routed to the modulator portion of modulation circuit 360. The modulator mixes the baseband transmit audio signal with an RF carrier signal generating an RF transmit signal that is routed to the power amplifier 358. The power amplifier 358 amplifies the RF transmit signal and routes it to the multiplexor 354 where the signal is switched to the antenna port for transmission by antenna 352.
The baseband processor 362 is also communicatively coupled with the processor 368. The processor 368 has access to a data storage area 370.
The processor 368 is preferably configured to execute instructions embodied in software such as the methods of Figures 1 through 6 that can be stored in the data storage area 370. A battery 384 is connected to the power circuit 374 through the connector 376. The battery 384 is typically housed within the device in a recessed compartment 386. An external power source (not shown) can also be connected through a connector 378 to provide power to the device and to re-charge the battery 384. The battery 384 includes a processor-type element 388 which runs the encryption algorithm of block 132, as shown in Figure 6.
The present invention further relates to machine readable media on which are stored embodiments of the present invention. It is contemplated that any media suitable for storing instructions is within the scope of the present invention. By way of example, such media may take the form of magnetic, optical, or semiconductor media. The invention also relates to data structures that contain embodiments of the present invention, and to the transmission of data structures containing embodiments of the present invention.
From the above description of exemplary embodiments of the invention, it is manifest that various techniques can be used for implementing the concepts of the present invention without departing from its scope. Moreover, while the invention has been described with specific reference to certain embodiments, a person of ordinary skill in the art would recognize that changes could be made in form and detail without departing from the spirit and the scope of the invention. The described exemplary embodiments are to be considered in all respects as illustrative and not restrictive. It should also be understood that the invention is not limited to the particular exemplary embodiments described herein, but is capable of many rearrangements, modifications, and substitutions without departing from the scope of the invention.
Claims (17)
1. A method for battery authentication in a wireless communication device with an attached battery, comprising the steps of:
randomly choosing a pair comprising plain text and associated encrypted text from a plurality of pairs of plain text and associated encrypted text stored in the wireless communication device;
(a) causing the wireless communication device to send said plain text of the randomly chosen pair, to the attached battery;
(b) causing the wireless communication device to wait for a first time period after the step of sending to receive encrypted text from the attached battery;
if encrypted text is not received within the first time period, then causing the wireless communication device to repeat the steps of (a) and (b) up to a pre-defined number of attempts, if the encrypted text is not received within the first time period, and the pre-defined number of attempts is exhausted, then causing the wireless communication device to enter a battery authentication failure event procedure, if encrypted text is received within the first time period, then causing the wireless communication device to compare the received encrypted text with pre-stored encrypted text that is associated with the plain text;
if the received encrypted text matches the pre-stored encrypted text, then causing the wireless communication device to identify the attached battery as an authentic battery; and if the received encrypted text does not match the pre-stored encrypted text, then causing the wireless communication device to enter the battery authentication failure event procedure.
randomly choosing a pair comprising plain text and associated encrypted text from a plurality of pairs of plain text and associated encrypted text stored in the wireless communication device;
(a) causing the wireless communication device to send said plain text of the randomly chosen pair, to the attached battery;
(b) causing the wireless communication device to wait for a first time period after the step of sending to receive encrypted text from the attached battery;
if encrypted text is not received within the first time period, then causing the wireless communication device to repeat the steps of (a) and (b) up to a pre-defined number of attempts, if the encrypted text is not received within the first time period, and the pre-defined number of attempts is exhausted, then causing the wireless communication device to enter a battery authentication failure event procedure, if encrypted text is received within the first time period, then causing the wireless communication device to compare the received encrypted text with pre-stored encrypted text that is associated with the plain text;
if the received encrypted text matches the pre-stored encrypted text, then causing the wireless communication device to identify the attached battery as an authentic battery; and if the received encrypted text does not match the pre-stored encrypted text, then causing the wireless communication device to enter the battery authentication failure event procedure.
2. The method of claim 1, further comprising the step of causing the wireless communication device to enter a low power mode, wherein the low power mode prevents the wireless communication device from initiating and receiving calls.
3. The method of claim 1, further comprising pre-storing the plurality of pairs of plain text and associated encrypted text in the wireless communication device.
4. The method of claim 1, wherein the associated encrypted text is generated by a tool external to the wireless communication device;
wherein the tool uses a first encryption algorithm; and wherein the authentic battery uses the first encryption algorithm to generate the encrypted text received by the wireless communication device.
wherein the tool uses a first encryption algorithm; and wherein the authentic battery uses the first encryption algorithm to generate the encrypted text received by the wireless communication device.
5. The method of claim 4, wherein the first encryption algorithm is a block cipher algorithm.
6. The method of claim 1, wherein when a battery authentication security level is at a high level, the battery authentication failure event procedure comprises:
causing the wireless communication device to display a message in a pop-up window to indicate that the attached battery is not authentic;
causing the wireless communication device to provide an emergency call option in the pop-up window;
causing the wireless communication device to power down the wireless communication device if the emergency call option is not selected within a second time period; and causing the wireless communication device to place an emergency call if the emergency call option is selected.
causing the wireless communication device to display a message in a pop-up window to indicate that the attached battery is not authentic;
causing the wireless communication device to provide an emergency call option in the pop-up window;
causing the wireless communication device to power down the wireless communication device if the emergency call option is not selected within a second time period; and causing the wireless communication device to place an emergency call if the emergency call option is selected.
7. The method of claim 6, wherein the step of placing an emergency call further comprises:
causing the wireless communication device to enter an emergency call back mode;
causing the wireless communication device to allow the attached battery to drain;
causing the wireless communication device to block normal battery charging operations; and causing the wireless communication device to enter a low power mode.
causing the wireless communication device to enter an emergency call back mode;
causing the wireless communication device to allow the attached battery to drain;
causing the wireless communication device to block normal battery charging operations; and causing the wireless communication device to enter a low power mode.
8. The method of claim 1, wherein when a battery authentication security level is at a medium level, the battery authentication failure event procedure comprises:
causing the wireless communication device to display a message in a pop-up window to indicate that the attached battery is not authentic;
causing the wireless communication device to receive a message acknowledgement;
causing the battery to conduct normal battery operations; and causing the wireless communication device to cause normal battery charging operations to be blocked.
causing the wireless communication device to display a message in a pop-up window to indicate that the attached battery is not authentic;
causing the wireless communication device to receive a message acknowledgement;
causing the battery to conduct normal battery operations; and causing the wireless communication device to cause normal battery charging operations to be blocked.
9. The method of claim 1, wherein a battery authentication security level is at a low level the battery authentication failure event procedure comprises:
causing the wireless communication device to display a message in a pop-up window to indicate that the attached battery is not authentic;
causing the wireless communication device to receive a message acknowledgement;
causing the battery to conduct normal battery operations; and causing the wireless communication device to cause normal battery charging operations to be conducted.
causing the wireless communication device to display a message in a pop-up window to indicate that the attached battery is not authentic;
causing the wireless communication device to receive a message acknowledgement;
causing the battery to conduct normal battery operations; and causing the wireless communication device to cause normal battery charging operations to be conducted.
10. The method of claim 1, further comprising:
causing the attached battery to receive the plain text from the wireless communication device;
causing the attached battery to run an encryption algorithm on the received plain text to produce encrypted text; and causing the attached battery to send the encrypted text to the wireless communication device; and causing the attached battery to power the wireless communication device for normal operations if the wireless communication device identifies the attached battery as authentic based upon the encrypted text sent from the battery.
causing the attached battery to receive the plain text from the wireless communication device;
causing the attached battery to run an encryption algorithm on the received plain text to produce encrypted text; and causing the attached battery to send the encrypted text to the wireless communication device; and causing the attached battery to power the wireless communication device for normal operations if the wireless communication device identifies the attached battery as authentic based upon the encrypted text sent from the battery.
11. A computer readable medium encoded with codes for directing a processor in a wireless communication device with an attached battery to execute the method of any one of claims 1 - 10.
12. A wireless communication device having an attached battery, the wireless communication device comprising a processor circuit and the computer-readable medium of claim 11, wherein the computer readable medium is in communication with the processor circuit and the processor circuit executes the method of any one of claims 1- 10 under the direction of the codes encoded on the computer readable medium.
13. A wireless communication device comprising:
a memory for pre-storing a plurality of pairs of a plain text and an associated encrypted text, wherein the pre-stored associated encrypted text is generated by a tool external to the wireless communication device that utilizes an encryption algorithm;
a processor coupled to the memory for randomly choosing a pair of the plain text and the associated encrypted text from the plurality of pairs for sending to an attachable battery;
a transceiver coupled to the processor;
an input device coupled to the processor;
a display coupled to the processor;
the attachable battery coupled to the processor;
a computer-readable medium encoded with codes for directing the processor to:
(a) send said plain text of the randomly chosen pair to the attachable battery, wherein if the attachable battery is authentic, then the authentic battery includes a processing device for running the encryption algorithm on the plain text to produce an encrypted text;
(b) wait for a first time period to receive the encrypted text from the attachable battery;
(c) repeat steps (a) and (b) a pre-defined number of attempts if encrypted text is not received within the first time period;
(d) if encrypted text is not received within the first time period and the pre-defined number of attempts is exhausted, then enter a battery authentication failure event procedure;
(e) if encrypted text is received within the first time period, then compare the received encrypted text with the pre-stored encrypted text that is associated with the plain text;
(f) if the received encrypted text matches the pre-stored encrypted text, then identify the attached battery as an authentic battery; and (g) if the received encrypted text does not match the pre-stored encrypted text, then enter the battery authentication failure event procedure.
a memory for pre-storing a plurality of pairs of a plain text and an associated encrypted text, wherein the pre-stored associated encrypted text is generated by a tool external to the wireless communication device that utilizes an encryption algorithm;
a processor coupled to the memory for randomly choosing a pair of the plain text and the associated encrypted text from the plurality of pairs for sending to an attachable battery;
a transceiver coupled to the processor;
an input device coupled to the processor;
a display coupled to the processor;
the attachable battery coupled to the processor;
a computer-readable medium encoded with codes for directing the processor to:
(a) send said plain text of the randomly chosen pair to the attachable battery, wherein if the attachable battery is authentic, then the authentic battery includes a processing device for running the encryption algorithm on the plain text to produce an encrypted text;
(b) wait for a first time period to receive the encrypted text from the attachable battery;
(c) repeat steps (a) and (b) a pre-defined number of attempts if encrypted text is not received within the first time period;
(d) if encrypted text is not received within the first time period and the pre-defined number of attempts is exhausted, then enter a battery authentication failure event procedure;
(e) if encrypted text is received within the first time period, then compare the received encrypted text with the pre-stored encrypted text that is associated with the plain text;
(f) if the received encrypted text matches the pre-stored encrypted text, then identify the attached battery as an authentic battery; and (g) if the received encrypted text does not match the pre-stored encrypted text, then enter the battery authentication failure event procedure.
14. The wireless communication device of claim 13, wherein the computer readable medium includes codes for directing the processor to execute the battery authentication failure event procedure when a battery authentication security level is at a high level, the authentication failure event procedure being defined by codes stored on the computer readable medium that direct the processor to:
cause a message to appear in a pop-up window on the display to indicate that the attachable battery is not authentic;
provide an emergency call option in the pop-up window;
power down the wireless communication device if the emergency call option is not selected within a second time period; and place an emergency call if the emergency call option is selected.
cause a message to appear in a pop-up window on the display to indicate that the attachable battery is not authentic;
provide an emergency call option in the pop-up window;
power down the wireless communication device if the emergency call option is not selected within a second time period; and place an emergency call if the emergency call option is selected.
15. The wireless communication device of claim 14, wherein the codes for directing the processor to place an emergency call include codes for directing the processor to:
enter an emergency call back mode;
allow the attachable battery to drain;
block normal battery charging operations; and enter a low power mode.
enter an emergency call back mode;
allow the attachable battery to drain;
block normal battery charging operations; and enter a low power mode.
16. The wireless communication device of claim 13, wherein the computer readable medium includes codes for directing the processor to execute the battery authentication failure event procedure when a battery authentication security level is at a medium level, the authentication failure event procedure being defined by codes stored on the computer readable medium that direct the processor to:
cause a message to appear in a pop-up window on the display to indicate that the attachable battery is not authentic;
receive a message acknowledgement;
conduct normal battery operations; and block normal battery charging operations.
cause a message to appear in a pop-up window on the display to indicate that the attachable battery is not authentic;
receive a message acknowledgement;
conduct normal battery operations; and block normal battery charging operations.
17. The wireless communication device of claim 13, wherein the computer readable medium includes codes for directing the processor to execute the battery authentication failure event procedure when a battery authentication security level is at a low level, the battery authentication failure event procedure being defined by codes stored on the computer readable medium that direct the processor to:
cause a message to appear in a pop-up window on the display to indicate that the attachable battery is not authentic;
receive a message acknowledgement;
conduct normal battery operations; and conduct normal battery charging operations.
cause a message to appear in a pop-up window on the display to indicate that the attachable battery is not authentic;
receive a message acknowledgement;
conduct normal battery operations; and conduct normal battery charging operations.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US11/336,447 | 2006-01-20 | ||
| US11/336,447 US7877815B2 (en) | 2006-01-20 | 2006-01-20 | Battery authentication in a wireless communication device |
| PCT/US2007/001311 WO2007084601A2 (en) | 2006-01-20 | 2007-01-18 | Battery authentication in a wireless communication device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2636425A1 CA2636425A1 (en) | 2007-07-26 |
| CA2636425C true CA2636425C (en) | 2011-08-30 |
Family
ID=38171344
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2636425A Expired - Fee Related CA2636425C (en) | 2006-01-20 | 2007-01-18 | Battery authentication in a wireless communication device |
Country Status (11)
| Country | Link |
|---|---|
| US (1) | US7877815B2 (en) |
| EP (1) | EP1974415B1 (en) |
| JP (1) | JP2009526344A (en) |
| KR (1) | KR101007800B1 (en) |
| CN (1) | CN101375460A (en) |
| AT (1) | ATE449431T1 (en) |
| AU (1) | AU2007207487B2 (en) |
| CA (1) | CA2636425C (en) |
| DE (1) | DE602007003316D1 (en) |
| ES (1) | ES2333062T3 (en) |
| WO (1) | WO2007084601A2 (en) |
Families Citing this family (36)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070260892A1 (en) * | 2006-05-08 | 2007-11-08 | Paul Christopher R | System and method for authenticating a power source |
| JP2009151953A (en) * | 2007-12-18 | 2009-07-09 | Mitsumi Electric Co Ltd | Battery pack, and electronic apparatus |
| JP5194964B2 (en) * | 2008-04-07 | 2013-05-08 | 日本電気株式会社 | Electric vehicle battery charging system |
| ATE539478T1 (en) | 2009-02-25 | 2012-01-15 | Research In Motion Ltd | METHOD AND SYSTEM FOR DETECTING COUNTERFEIT BATTERIES |
| US9043474B2 (en) * | 2010-01-20 | 2015-05-26 | Microsoft Technology Licensing, Llc | Communication sessions among devices and interfaces with mixed capabilities |
| WO2011107119A1 (en) | 2010-03-05 | 2011-09-09 | Husqvarna Ab | Battery powered product |
| US8898461B2 (en) | 2011-03-03 | 2014-11-25 | Lenovo (Singapore) Pte. Ltd. | Battery authentication method and apparatus |
| US10678905B2 (en) * | 2011-03-18 | 2020-06-09 | Lenovo (Singapore) Pte. Ltd. | Process for controlling battery authentication |
| EP2689598B1 (en) | 2011-03-25 | 2015-11-25 | Certicom Corp. | Interrogating an authentication device |
| EP2705725B1 (en) | 2011-05-06 | 2017-07-19 | Certicom Corp. | Managing data for authentication devices |
| WO2013016548A2 (en) * | 2011-07-26 | 2013-01-31 | Gogoro, Inc. | Apparatus, method and article for authentication, security and control of power storage devices, such as batteries |
| US8996212B2 (en) | 2011-07-26 | 2015-03-31 | Gogoro Inc. | Apparatus, method and article for providing vehicle diagnostic data |
| US8560147B2 (en) | 2011-07-26 | 2013-10-15 | Gogoro, Inc. | Apparatus, method and article for physical security of power storage devices in vehicles |
| CN102361104B (en) * | 2011-10-28 | 2013-04-17 | 深圳市欣视景科技有限公司 | Battery and battery identification circuit |
| CN103092303A (en) * | 2011-10-31 | 2013-05-08 | 富泰华工业（深圳）有限公司 | Electronic device and starting method thereof |
| KR101872472B1 (en) * | 2011-11-04 | 2018-06-29 | 삼성에스디아이 주식회사 | Battery Pack, Battery protection circuit, and battery system |
| US8793810B2 (en) | 2012-01-09 | 2014-07-29 | Blackberry Limited | Semiconductor-based device authentication |
| JP5113950B1 (en) * | 2012-05-28 | 2013-01-09 | 兵庫ベンダ工業株式会社 | Battery device, information processing device, control method thereof, and control program |
| US9275218B1 (en) | 2012-09-12 | 2016-03-01 | Emc Corporation | Methods and apparatus for verification of a user at a first device based on input received from a second device |
| US9280645B1 (en) * | 2012-11-15 | 2016-03-08 | Emc Corporation | Local and remote verification |
| US9369290B2 (en) | 2012-11-30 | 2016-06-14 | Certicom Corp. | Challenge-response authentication using a masked response value |
| US9727720B2 (en) | 2012-11-30 | 2017-08-08 | Certicom Corp. | Challenge-response authentication using a masked response value |
| US9633655B1 (en) * | 2013-05-23 | 2017-04-25 | Knowles Electronics, Llc | Voice sensing and keyword analysis |
| PT3231617T (en) | 2013-08-30 | 2018-11-16 | Hewlett Packard Development Co | Supply authentication via timing challenge response |
| US9953634B1 (en) | 2013-12-17 | 2018-04-24 | Knowles Electronics, Llc | Passive training for automatic speech recognition |
| JP6346438B2 (en) * | 2013-12-27 | 2018-06-20 | キヤノン株式会社 | Electronic device, control method therefor, program, and storage medium |
| WO2016025392A1 (en) | 2014-08-11 | 2016-02-18 | Gogoro Inc. | Multidirectional electrical connector, plug and system |
| JP6376913B2 (en) * | 2014-09-10 | 2018-08-22 | キヤノン株式会社 | Electronics |
| DE102015002077B3 (en) * | 2015-02-18 | 2016-06-09 | Audi Ag | Battery cell for a battery of a motor vehicle, battery, motor vehicle and method for operating a battery cell |
| US20180293408A1 (en) * | 2015-05-11 | 2018-10-11 | Hewlett Packard Enterprise Development Lp | Peripheral device security |
| CN109050293A (en) * | 2018-07-28 | 2018-12-21 | 深圳市烽焌信息科技有限公司 | A kind of continuation of the journey base station applied to unmanned plane |
| CN111295776A (en) * | 2019-03-28 | 2020-06-16 | 深圳市大疆创新科技有限公司 | Electricity core subassembly, intelligent battery and unmanned aerial vehicle |
| CN110955165A (en) * | 2019-11-27 | 2020-04-03 | 深圳拓邦股份有限公司 | Control method of cleaning equipment and cleaning equipment |
| US11561592B2 (en) * | 2020-05-08 | 2023-01-24 | Canon Kabushiki Kaisha | Power receiving apparatus and control method |
| CN113093678B (en) * | 2021-04-07 | 2022-12-20 | 国能(泉州)热电有限公司 | Data processing method for power plant DCS (distributed control System) |
| JP2024009537A (en) * | 2022-07-11 | 2024-01-23 | トヨタ自動車株式会社 | Battery determination method |
Family Cites Families (27)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4670857A (en) | 1981-10-26 | 1987-06-02 | Rackman Michael I | Cartridge-controlled system whose use is limited to authorized cartridges |
| JP2680426B2 (en) * | 1989-06-08 | 1997-11-19 | 三菱電機株式会社 | Authentication method |
| US5717306A (en) * | 1994-11-18 | 1998-02-10 | Shipp; John I. | Battery identification and power interrupt system |
| US6190257B1 (en) | 1995-11-22 | 2001-02-20 | Nintendo Co., Ltd. | Systems and method for providing security in a video game system |
| EP1080415B1 (en) * | 1998-05-21 | 2017-01-18 | Equifax Inc. | System and method for authentication of network users |
| US6163361A (en) | 1999-04-23 | 2000-12-19 | Eastman Kodak Company | Digital camera including a printer for receiving a cartridge having security control circuitry |
| KR100367295B1 (en) | 2000-03-13 | 2003-01-09 | 엘지전자 주식회사 | An apparatus and method for writing a region code in a DVD driver |
| JP2003162986A (en) * | 2001-11-27 | 2003-06-06 | Sanyo Electric Co Ltd | Id generating device and id confirming device |
| JP2004083002A (en) * | 2002-04-12 | 2004-03-18 | Aisin Aw Co Ltd | Electric power source control system for on-vehicle device |
| JP3919650B2 (en) * | 2002-10-23 | 2007-05-30 | キヤノン株式会社 | Electronic equipment system |
| JP4337474B2 (en) * | 2002-11-27 | 2009-09-30 | セイコーエプソン株式会社 | Printer and printing system |
| US7190947B2 (en) * | 2003-02-07 | 2007-03-13 | Motorola Inc. | Priority E911 call back during access class restrictions |
| US7324801B2 (en) * | 2003-03-06 | 2008-01-29 | Motorola, Inc. | Emergency call-back for a wireless communication device equipped with a user removable module |
| JP3955285B2 (en) * | 2003-03-27 | 2007-08-08 | 松下電器産業株式会社 | Inverter control device for motor drive and air conditioner |
| US6975092B2 (en) * | 2003-07-03 | 2005-12-13 | Dell Products L.P. | Encrypted response smart battery |
| JP2005073053A (en) * | 2003-08-26 | 2005-03-17 | Sanyo Electric Co Ltd | Id confirmation unit, id generation unit and authentication system |
| JP2005094128A (en) * | 2003-09-12 | 2005-04-07 | Matsushita Electric Ind Co Ltd | Authentication system |
| JP2005151368A (en) * | 2003-11-19 | 2005-06-09 | Matsushita Electric Ind Co Ltd | Authentication system |
| JP2005176462A (en) * | 2003-12-09 | 2005-06-30 | Canon Inc | Battery, charger, and information processing apparatus |
| US7596699B2 (en) | 2004-02-24 | 2009-09-29 | Intersil Americas Inc. | Battery authentication system |
| US20050227669A1 (en) * | 2004-04-08 | 2005-10-13 | Ixi Mobile (R&D) Ltd. | Security key management system and method in a mobile communication network |
| JP3817249B2 (en) * | 2004-04-28 | 2006-09-06 | 株式会社エヌ・ティ・ティ・ドコモ | Mobile device and communication control method |
| JP3765544B1 (en) * | 2004-11-26 | 2006-04-12 | 株式会社ソニー・コンピュータエンタテインメント | Battery and authentication request device |
| US20060178170A1 (en) * | 2005-02-08 | 2006-08-10 | Samsung Electronics Co., Ltd. | Wireless communication device having battery authentication, and associated method |
| ATE489670T1 (en) | 2005-10-14 | 2010-12-15 | Research In Motion Ltd | MOBILE COMMUNICATION DEVICE WITH AN INTELLIGENT BATTERY SYSTEM |
| KR100990466B1 (en) * | 2005-10-14 | 2010-10-29 | 리서치 인 모션 리미티드 | Battery pack authentication for a mobile device |
| US20070143864A1 (en) * | 2005-12-15 | 2007-06-21 | Symbol Technologies, Inc. | Methods and apparatus for power source authentication |
-
2006
- 2006-01-20 US US11/336,447 patent/US7877815B2/en not_active Expired - Fee Related
-
2007
- 2007-01-18 CN CNA2007800031756A patent/CN101375460A/en active Pending
- 2007-01-18 DE DE602007003316T patent/DE602007003316D1/en active Active
- 2007-01-18 JP JP2008551386A patent/JP2009526344A/en active Pending
- 2007-01-18 ES ES07716756T patent/ES2333062T3/en active Active
- 2007-01-18 KR KR1020087019715A patent/KR101007800B1/en not_active IP Right Cessation
- 2007-01-18 AT AT07716756T patent/ATE449431T1/en not_active IP Right Cessation
- 2007-01-18 WO PCT/US2007/001311 patent/WO2007084601A2/en active Application Filing
- 2007-01-18 AU AU2007207487A patent/AU2007207487B2/en not_active Ceased
- 2007-01-18 EP EP07716756A patent/EP1974415B1/en active Active
- 2007-01-18 CA CA2636425A patent/CA2636425C/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| CA2636425A1 (en) | 2007-07-26 |
| JP2009526344A (en) | 2009-07-16 |
| KR101007800B1 (en) | 2011-01-14 |
| WO2007084601A2 (en) | 2007-07-26 |
| DE602007003316D1 (en) | 2009-12-31 |
| ATE449431T1 (en) | 2009-12-15 |
| WO2007084601A3 (en) | 2007-09-13 |
| US7877815B2 (en) | 2011-01-25 |
| EP1974415A2 (en) | 2008-10-01 |
| AU2007207487B2 (en) | 2010-10-21 |
| ES2333062T3 (en) | 2010-02-16 |
| EP1974415B1 (en) | 2009-11-18 |
| CN101375460A (en) | 2009-02-25 |
| US20070192877A1 (en) | 2007-08-16 |
| AU2007207487A2 (en) | 2008-09-25 |
| AU2007207487A1 (en) | 2007-07-26 |
| KR20080083065A (en) | 2008-09-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2636425C (en) | Battery authentication in a wireless communication device | |
| JP5530003B2 (en) | Wireless communication method and apparatus using acoustic signal | |
| US8145194B2 (en) | Wireless device monitoring system including unauthorized apparatus and authentication apparatus with security authentication function | |
| US8467770B1 (en) | System for securing a mobile terminal | |
| JP4865807B2 (en) | Method and apparatus for authenticating a mobile phone accessory | |
| CN101095318B (en) | Method and device for bluetooth pairing | |
| US20130029596A1 (en) | Pairing devices using data exchanged in an out-of-band channel | |
| US20060178170A1 (en) | Wireless communication device having battery authentication, and associated method | |
| EP1161031A2 (en) | Access point device and authentication method thereof | |
| US20050090267A1 (en) | Method and apparatus for enabling a device by proximity | |
| WO2009045826A1 (en) | Flash pairing between bluetooth devices | |
| US20110021174A1 (en) | Method and apparatus for automatically damaging circuitry of a mobile device when one or more conditions are detected | |
| CN101594695A (en) | Wireless communication system, radio communication device, its method for disconnection process, storage medium | |
| JPH05336108A (en) | Radio communication system | |
| EP1534030B1 (en) | Preventing unauthorized use of a mobile communication terminal | |
| CN102625301A (en) | Wireless module, mobile phone and key transport method | |
| WO2023000139A1 (en) | Credential transmission method and apparatus, communication device, and storage medium | |
| KR100645218B1 (en) | Mobile communication terminal and server for authenticating wirelss data service to cut off it from connecting with wirelss data communication | |
| US20070298759A1 (en) | Alarm device for mobile phone | |
| WO2015024188A1 (en) | Working method of mobile station terminal in pseudo shutdown mode, and mobile station terminal | |
| KR100632104B1 (en) | Mobile communication terminal and System for intercept to connect illegal terminal with voice call |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKLA | Lapsed |
Effective date: 20130118 |