Repair-right battery replacement methods and applications

Abstract

This document describes the technologies associated with the right-of-warranty battery replacement method and its application. These technologies include: detecting replacement batteries (new batteries or reinstalled identical batteries) in electronic devices, certifying replacement batteries, and monitoring the battery characterization and health of replacement batteries. The use of these technologies enables sustainability and right-of-warranty options, thereby complying with customer rights and government regulations. Furthermore, these technologies enable the replacement of embedded batteries in user devices, detecting that the replacement battery is installed and is safe for use by the device. A battery health monitor can be implemented on the device to monitor the health of the replacement battery. In some aspects, the battery health monitor can be implemented via an application running on the device or as a subscription-based service implemented via a system-level application.

Description

Background Technology

[0001] Lithium-ion (Li-ion) batteries are complex and pose safety risks if handled improperly. From both customer rights and sustainability perspectives, the right to repair and government regulations regarding customers' ability to replace embedded Li-ion batteries present both challenges and opportunities. Significant efforts have been made within the industry to ensure the correct batteries are used in electronic devices through battery certification. However, many systems still resort to deceptive practices to accept third-party batteries, which can lead to performance and safety issues. Summary of the Invention

[0002] This document describes technologies related to the right-to-repair (R2R) battery replacement method and its application. These technologies include: detecting replacement batteries (new batteries or reinstalled identical batteries) in electronic devices, certifying replacement batteries, and monitoring the battery characterization and health of replacement batteries. The use of these technologies enables sustainability and right-to-repair (R2R) options, thereby complying with customer rights and government regulations. Furthermore, these technologies enable the replacement of embedded batteries in user devices, detecting that the replacement battery is installed and is safe for use by the device. A battery health monitor can be implemented on the device to monitor the health of the replacement battery. In some aspects, the battery health monitor can be implemented via an application (“app”) running on the device or as a subscription-based service via a system-level application.

[0003] Among various aspects, a method for right-of-service battery replacement is disclosed, which can be performed at an electronic device. The method includes, for example, receiving a request at the electronic device to replace a battery in a target device with a replacement battery. The method also includes receiving at least one image of a replacement battery identification code associated with the replacement battery and a target device identification code associated with the target device. Furthermore, the method includes sending the replacement battery identification code and the target device identification code to a server. Additionally, the method includes receiving a compatibility message from the server, the compatibility message indicating, based on the replacement battery identification code and the target device identification code, that the replacement battery is compatible with the target device. The method also includes: in response to receiving the compatibility message from the server, instructing a user to replace the battery in the target device with the replacement battery. Furthermore, the method includes: in response to the target device being restarted, receiving an indication from the target device that, for example, a link including a sensing wire and / or a fuse and configured to physically and electrically couple the device-side connector of the target device to the battery is open, and that the replacement battery installed in the target device corresponds to the replacement battery identification code in at least one image. The method also includes: based on this indication, notifying the user that the replacement battery has been successfully installed in the target device.

[0004] In other aspects, an electronic device is disclosed. This electronic device includes a camera system, a memory, and one or more processors configured to execute instructions in the memory to implement a device management application configured to communicate with the camera system to capture one or more images and perform the methods described above.

[0005] The present invention is provided to introduce a simplified concept of a battery replacement method with repair rights and its application, which is further described below in specific embodiments. Attached Figure Description

[0006] This document describes in detail one or more aspects of the servicing battery replacement method and its application with reference to the following figures. The same reference numerals are used in the figures to refer to the same features and components:

[0007] Figure 1 The diagram illustrates an example network environment in which the battery replacement method with repair rights and its application can be implemented.

[0008] Figure 2 A more detailed illustration is provided. Figure 1 Example implementation of electronic devices;

[0009] Figure 3A The 3D illustrations show different examples of how to implement a circuit for detecting battery removal.

[0010] Figure 4 This diagram illustrates an example flowchart of battery replacement based on the technology described herein;

[0011] Figure 5 An example method for pairing a replacement battery with a target device is described;

[0012] Figure 6 An example method for battery authentication is described;

[0013] Figure 7 The diagram illustrates what can be achieved as shown in the reference. Figure 2 An example environment for the described home area network, the battery replacement method with repair rights, and its application.

[0014] Figure 8 The illustration shows an example wireless network device that can be implemented as any wireless network device in a home area network, based on one or more aspects of the right-of-care battery replacement method and its application as described herein; and

[0015] Figure 9 The illustration shows an example system including an example device, which can be implemented as described above with reference to the previous one. Figures 1 to 8 The described repair-right battery replacement method and its application aspects are applicable to any wireless network device. Detailed Implementation

[0016] This document describes a method for right-of-service battery replacement and its application. These techniques include battery replacement detection, replacement battery authentication, and battery characterization and health monitoring. In the example, a user triggers the battery replacement process via an application (e.g., a device management application) and is instructed to scan the replacement battery ID code (e.g., a QR code) and the target device ID code to pair the target device with the battery. After the battery is replaced and the target device is powered on, the target device detects that the battery has been removed by detecting an open link (e.g., an open fuse or sensing wire). After the target device is connected to an external power source, a battery characterization profile is initiated and completed to ensure proper installation and battery functionality.

[0017] The technologies described herein enable owners of consumer electronics products to repair and / or replace components within their devices. Furthermore, from a lifespan and sustainability perspective, the described technologies implement sustainability options under government regulations, which may require access to the device for user-performed repairs or replacements to ensure the device lasts a longer period before being sent to a landfill. Additionally, battery characterization features and applications can be realized (e.g., sales, purchases) in business-to-business (B2B) and business-to-consumer (B2C) contexts related to subscriptions and licensing. Therefore, these disclosed methods improve the sustainability, lifespan, and user satisfaction of such systems and devices.

[0018] Although the features and concepts of the described techniques for the repair-right battery replacement method and its application can be implemented in any number of different environments, these aspects are described in the context of the following examples.

[0019] Example device

[0020] Figure 1 An example network environment 100 is illustrated, which enables aspects of a right-of-care battery replacement method and its application. Network environment 100 includes a home area network (HAN). The HAN includes wireless network devices 102 (e.g., electronic devices) positioned around a structure 104, such as a house, and connected via one or more wireless and / or wired network technologies, as described below. The HAN includes a border router 106 that connects the HAN to an external network 108, such as the Internet, via a home router or access point 110.

[0021] To provide users with access to the functionality implemented using wireless network device 102 within the HAN, cloud service 112 connects to the HAN via a secure channel 114 through external network 108 and access point 110, via border router 106. Cloud service 112 uses a web-based application programming interface (API) 118 to facilitate communication between the HAN and internet clients 116—such as apps on mobile devices. Cloud service 112 also manages a home map describing the connections and relationships between wireless network device 102, the elements of architecture 104, and users. Cloud service 112 hosts controllers that orchestrate and arbitrate the home automation experience, as described in more detail below.

[0022] The HAN can include one or more wireless network devices 102 used as hub 120. Hub 120 can be a general-purpose home automation hub or a dedicated hub, such as a security hub, energy management hub, HVAC hub, etc. The functionality of hub 120 can also be integrated into any wireless network device 102, such as a smart thermostat device or border router 106. In addition to hosting the controller on cloud service 112, the controller can also be hosted on any hub 120 in structure 104, such as border router 106. Controllers hosted on cloud service 112 can be dynamically moved to hubs 120 in structure 104, such as moving an HVAC area controller to a newly installed smart thermostat.

[0023] The hosting functionality on hub 120 in structure 104 can improve reliability when the user’s Internet connection is unreliable, can reduce latency of operations that would normally have to be connected to cloud service 112, and can meet system and regulatory constraints surrounding local access between wireless network devices 102.

[0024] The wireless network device 102 in the HAN can also come from a single manufacturer providing cloud service 112, or the HAN can include wireless network devices 102 from partners. These partners can also provide partner cloud service 122, which provides services related to the partner's wireless network device 102 via partner Web API 124. Partner cloud service 122 can optionally or additionally provide services to Internet client 116 via web-based API 118, cloud service 112, and secure tunnel 114.

[0025] Network environment 100 can be implemented on various hosts, such as battery-powered microcontroller-based devices, line-powered devices, and servers hosting cloud services. Protocols operating in wireless network device 102 and cloud service 112 provide multiple services supporting the operation of the home automation experience within distributed computing environment 100. These services include, but are not limited to, real-time distributed data management and subscription, command and response control, real-time event notification, historical data logging and storage, password-controlled security groups, time synchronization, network and service pairing, and software updates.

[0026] Figure 2 A more detailed illustration is provided. Figure 1 An example implementation of an electronic device. Figure 2 Electronic devices 202 (e.g., wireless network device 102, mobile devices) are shown as having various example devices, including smartphones 202-1, tablets 202-2, laptops 202-3, security cameras 202-4, computing watches 202-5, computing glasses 202-6, gaming systems 202-7, video recording doorbells 202-8, and speakers 202-9. Electronic devices 202 may also include other devices, such as televisions, entertainment systems, desktop computers, audio systems, projectors, automobiles, drones, tracking boards, drawing tablets, netbooks, e-readers, home security systems, camera systems, thermostats, and other household appliances. Note that electronic devices 202 can be mobile, wearable, non-wearable but mobile, or relatively stationary (e.g., desktop computers and appliances).

[0027] Electronic device 202 includes a battery (e.g., battery 204). Battery 204 can be any suitable rechargeable battery. As described herein, battery 204 can be a lithium-ion battery. A wide variety of lithium-ion battery chemistry can be implemented, some examples of which include lithium cobalt oxide (LiCoO2), lithium iron phosphate (LiFePO4), lithium manganese oxide (LiMn2O4 spinel or lithium-rich layered materials based on Li2MnO3, LMR-NMC), and lithium nickel manganese cobalt oxide (LiNiMnCoO2, Li-NMC, LNMC, NMC, or NCM, and various Co stoichiometry ranges). Furthermore, lithium-ion batteries can include a wide variety of anode materials, including graphite-based anodes, silicon (Si), graphene, and other cation sandwich / intercalation / alloyed anode materials.

[0028] Electronic device 202 includes one or more processors 206 (e.g., any of a microprocessor, controller, or other controller), which can process various computer-executable instructions to control the operation of electronic device 202 and implement techniques for servicing battery replacement methods and their applications. The processor 206 is further described in detail below.

[0029] Electronic device 202 also includes a computer-readable medium 208 (CRM 208) providing storage for various applications 210 and system data. Applications 210 and / or operating systems 214, implemented as computer-readable instructions on the computer-readable medium 208 (e.g., a storage medium), can be executed by processor 206 to provide some or all of the functions described herein. The computer-readable medium 208 provides a data storage mechanism to store various device applications 210, operating systems 214, memory / storage devices, and other types of information and / or data related to operational aspects of electronic device 202. For example, operating system 214 can be maintained as a computer application within the computer-readable medium 208 and executed by processor 206 to provide some or all of the functions described herein. Device applications 210 may include device managers, such as any form of control application, software application, or signal processing and control module. Device applications 210 may also include system components, engines, or managers to implement techniques for the right-of-service battery replacement method and its applications, such as identity manager module 216, battery detection module 218, battery characterization module 220, etc. Electronic device 202 may also include or be able to access one or more machine learning systems.

[0030] Various implementations of the identity manager module 216, battery detection module 218, and battery characterization module 220 may include a system-on-a-chip (SoC), one or more integrated circuits (ICs), a processor having embedded processor instructions or configured to access processor instructions stored in memory, hardware with embedded firmware, a printed circuit board with various hardware components, or any combination thereof, or communicate with the SoC, one or more integrated circuits (ICs), a processor having embedded processor instructions or configured to access processor instructions stored in memory, hardware with embedded firmware, a printed circuit board with various hardware components, or any combination thereof.

[0031] Identity manager module 216 is configured to obtain a battery identifier (e.g., battery ID) from an image (e.g., a first image) of an ID code associated with a battery replacement, captured by an image capture device (e.g., a camera). This ID code can be a machine-readable optical label (e.g., a QR code, barcode, unique graphic). Furthermore, identity manager module 216 is configured to obtain a device ID from an image (e.g., a second image) captured by the image capture device from an ID code associated with electronic device 202. In another example, the battery ID and / or device ID may be obtained from images of non-fungible tokens (NFTs) or other unique symbols or codes associated with the battery and / or device, respectively.

[0032] The battery detection module 218 is configured to detect the battery identifier (e.g., battery ID) of a battery installed in or coupled to the electronic device 202. Using the detected battery ID, the battery detection module 218 can authenticate that the battery is an authorized battery, and / or that the detected battery ID matches a battery ID obtained from a previously scanned ID code.

[0033] Battery detection module 218 can use any suitable method to detect the battery ID and authenticate the battery. In one example, battery detection module 218 can measure the voltage drop across a resistor on a connector within the battery pack, which can be used to determine the specific version of the battery. In another example, battery detection module 218 can perform a handshake with an integrated circuit within the battery pack. In this case, the battery pack may include an erasable programmable read-only memory (EPROM) chip or an electrically erasable programmable read-only memory (EEPROM) chip that stores the battery ID and / or other information corresponding to the battery pack, including battery pack capacity information. This functionality can also be implemented via a discrete fuel gauge and an integrated power management integrated circuit (PMIC) chip. Using a challenge / response scheme, battery detection module 218 can send commands to the battery pack and read back data in the response from the battery pack. The data may include a family code, a unique ID (e.g., battery ID), or other information that can be used to identify the battery pack. In another example, pins can be used to communicate with the integrated circuit in the battery pack, allowing battery detection module 218 to read the internals of the integrated circuit programmed by the manufacturer to obtain the battery ID.

[0034] In another example, a cryptographic authentication architecture (e.g., challenger and responder) can be used, which provides an additional layer of security. For instance, both the challenger (e.g., electronic device 202) and the responder (e.g., integrated circuit in a battery pack) can have keys that can be used with an authentication transformation algorithm (e.g., SHA-1) to compute the answer to the challenge. The challenger can then authenticate the responder if the answer computed by the challenger itself matches the responder's answer.

[0035] Battery characterization module 220 is configured to characterize a replaced battery and generate a battery characterization profile representing the health status of the replaced battery. For example, battery characterization module 220 is configured to run a charge / discharge profile on the battery to determine battery health. Any suitable charge / discharge profile can be executed, including step charge profiles and step discharge profiles. Battery characterization module 220 monitors the battery's behavior (e.g., charge rate, discharge rate) during the execution of the charge / discharge profile to understand battery impedance, capacity, and health status.

[0036] Electronic device 202 may also include a network interface 222. Electronic device 202 can use network interface 222 to transmit data over wired, wireless, optical, or audio (e.g., acoustic) networks. By way of example and not limitation, network interface 222 can transmit data over a local area network (LAN), wireless local area network (WLAN), home area network (HAN), personal area network (PAN), wide area network (WAN), intranet, internet, peer-to-peer network, point-to-point network, or mesh network. Network interface 222 can be implemented as one or more of a serial and / or parallel interface, wireless interface, any type of network interface, modem, or any other type of communication interface. Using network interface 222, electronic device 202 can communicate via cloud computing services (e.g., cloud service 112) to access platforms with resources.

[0037] Electronic device 202 also includes a camera system 224. Camera system 224 is configured to capture images, video, and / or audio. Any suitable camera system 224 can be implemented within electronic device 202 or communicatively coupled to electronic device 202. Camera system 224 can be a digital camera that converts light captured by a lens into digital data representing the scene within the lens's field of view. Furthermore, camera system 224 can be used to scan ID codes (e.g., QR codes, barcodes) associated with the battery pack and / or device. Camera system 224 may also include audio functionality configured to provide and receive audio communication. Audio functionality can be provided by an integrated audio sensor for receiving audio input (e.g., via a microphone) and / or providing audio output (e.g., via a speaker). In the example, if the camera is disabled or inactive, the audio functionality of electronic device 202 can listen for and detect voice input of a serial number or barcode number (e.g., a user reading aloud). This voice input can also be voice-authenticated via an application on electronic device 202 to verify that the voice belongs to the owner of electronic device 202.

[0038] Electronic device 202 may also include display 226 (e.g., display device 226). Display 226 may include any suitable touch-sensitive display device, such as touch screen, liquid crystal display (LCD), thin-film transistor (TFT) LCD, in-plane switching (IPS) LCD, capacitive touch screen display, organic light-emitting diode (OLED) display, active-matrix organic light-emitting diode (AMOLED) display, super AMOLED display, etc. Display 226 may be referred to as a display or screen, enabling digital content to be displayed on the screen.

[0039] Electronic device 202 also includes a housing 228 (e.g., a casing). Housing 228 houses various components of electronic device 202, including, for example, battery 204 and camera system 224. In various aspects, housing 228 includes at least two parts coupled together. These at least two parts of housing 228 can be tightly fitted together with a seal to prevent dust and water from entering the circuitry and other components housed within housing 228. These parts of housing 228 may also include physical links (e.g., fuses or sensing lines) that complete the circuitry when housing 228 is closed during factory assembly and that are interrupted when housing 228 is opened. Electronic device 202 can use this link to determine whether the housing has been tampered with (e.g., opened) after assembly. This indication of tampering points to the possibility that one or more internal components (e.g., battery 204) may have been removed and / or replaced, or that one or more objects may have been added to the housing. In the example, the physical link may be measured by an analog-to-digital converter (ADC) or equivalent. After factory assembly and before the housing is opened, the ADC can measure a "1" on the physical link, indicating a short circuit or a complete circuit. After the housing is opened, the physical link is interrupted, and the ADC measures a "0" on the physical link, indicating an open circuit. After the interruption, the physical link remains open even after the housing is closed, enabling the electronic device 202 to detect that the housing 228 has been opened at least once after factory assembly (and possibly by the consumer).

[0040] The following elaborates on these and other capabilities and configurations, as well as... Figure 1 and Figure 2 The actions and interactions of entities. These entities can be further divided, combined, etc. Figure 1 Network environment 100 and Figures 2 to 9 The detailed illustrations depict some of the many possible environments, devices, and methods in which the described techniques can be employed individually or in combination with each other.

[0041] Figure 3A The 3D illustrations show different examples of how to implement a circuit for detecting battery removal. Figure 3AAn example implementation 300 of a battery-side connector 302 coupled to a device-side connector 304 is illustrated. The device-side connector 304 includes electrical wiring 306, and the battery-side connector 302 includes corresponding wiring 308. Wiring 306 and 308 include various lines, some examples of which include one or more power lines 310 (e.g., positive and negative power), a data line 312, a clock line 314, a thermistor line 316, and a battery ID line 318. Wiring 306 and 308 may include additional external sensing lines 320 (e.g., sensing lines 320-1 and 320-2, respectively), which can be used to detect when the battery 204 is disconnected from the electronic device 202.

[0042] Sensing line 320 may be open (e.g., at opening 322) until factory assembly, where battery-side connector 302 is coupled to device-side connector 304, and sensing line 320-1 is physically and electrically coupled to sensing line 320-2. In the example, opening 322 may be a fuse or an open circuit. Sensing lines 320-1 and 320-2 may then be mated or coupled together to close opening 322 using, for example, a solder joint, additional wires, or any other suitable conductive coupling mechanism that electrically connects sensing lines 320-1 and 320-2 together. Such a coupling mechanism may provide a relatively weak point in sensing line 320 that fails (e.g., breaks) when battery-side connector 302 is decoupled from device-side connector 304 (e.g., when battery 204 is removed from electronics 202).

[0043] Electronic device 202 may have an ADC or equivalent that measures a closed loop (e.g., 1 bit) in sensing line 320 after factory assembly. After factory assembly, sensing line 320 is interrupted when the user removes battery 204. Then, when a replacement battery is installed and the device is turned on, the ADC measures an open loop (e.g., 0 bits) in sensing line 320, indicating that the original battery has been tampered with (e.g., removed). There is also the possibility that the currently installed battery is not the original battery.

[0044] Figure 3B Another example implementation 330 of the battery-side connector 302 coupled to the device-side connector 304 is illustrated. Similar to... Figure 3A Example implementations 300 and 330 illustrate a device-side connector 304 coupled to a battery-side connector 302. The device-side connector 304 has electrical wiring 306, and the battery-side connector 302 has corresponding wiring 308. Figure 3BIn the sensing line 320, weak points are filled with conductive material 332 to create a short circuit in the sensing line 320. The conductive material 332 may be conductive epoxy resin or other brittle conductive filler, which interrupts the conductive path in the sensing line 320 when the battery-side connector 302 is decoupled from the device-side connector 304 (e.g., pulled out).

[0045] Figure 3C Another example implementation 340 of the battery-side connector 302 coupled to the device-side housing connector 304 is illustrated. In various aspects, the battery-side connector 302 may include an opening 342 (e.g., a notch, recess). Connectors 302 and 304 can use pins (e.g., pin 344) to engage electrical wiring 306 with corresponding wiring 308. However, in the illustrated example, the opening 342 may be formed in the location of one of the pins, such as where a pin will otherwise connect sensing lines 320-1 and 320-2. Therefore, when the battery-side connector 302 is coupled to the device-side connector 304, the sensing line 320 remains open due to the opening 342 in the battery-side connector 304.

[0046] During factory assembly, opening 342 may be filled with conductive material 346 (e.g., conductive epoxy or other brittle conductive material) to close sensing line 320 by providing a conductive path between sensing lines 320-1 and 320-2. In all respects, conductive material 346 may be opaque to the user and flush with the outer surface of battery-side connector 302. Furthermore, the color of conductive material 346 may match the color of battery-side connector 302, making it less noticeable to the user and reducing the possibility of counterfeiting and / or user deception of the system. When the user removes battery 204 from electronic device 202, conductive material 346 interrupts the connection in sensing line 320, and sensing line 320 remains open when a replacement battery (e.g., a third-party battery) is installed. An open sensing line 320 results in an ADC reading of 0 bits, indicating that the replacement battery is not the original battery. Even if the same connector (or the same type of connector) is used as a replacement, the opening 342 will not be filled with conductive material 346, and the system will read the line as an interrupt, and the ADC will record the line as "0", thus indicating that the battery 204 has been tampered with.

[0047] Example Workflow

[0048] Figure 4An example flowchart 400 of battery replacement according to the technology described herein is illustrated. At block 402, the device receives a request to replace the battery. In various aspects, this request may be triggered by a user. For example, a user may provide user input via a device application (e.g., application 210) running on electronic device 202 to request a replacement of battery 204 in a target device (e.g., electronic device 202 or another device communicatively coupled to electronic device 202, such as wireless network device 102). In other aspects, the request may be generated by electronic device 202 based on the detection of poor battery health or other problems with battery 204 embedded in electronic device 202.

[0049] In response to a request to replace the battery in the target device, at box 404, instructions are provided to the user to capture images of the battery replacement ID code and the target device ID code, and to load these images into the device application. (As in...) Figure 5 and Figure 6 As described further in detail, the captured images can be uploaded to a server to pair the replacement battery with the target device. This device battery pairing at the server may include verifying compatibility between the battery and the device.

[0050] If the target device is powered on (e.g., box 406), then at box 408, when the user opens the device housing, the additional sensing wire or fuse is interrupted, and at box 410, the device is powered off in response to the interrupted fuse or sensing wire. In the example, the additional sensing wire or fuse connects to at least two portions of the target device housing 228, and when housing 228 is opened, the additional sensing wire or fuse is physically interrupted (e.g., cut, severed).

[0051] If the power to the target device is turned off before opening the housing at box 408 (e.g., box 412), then after opening the housing at box 408, the process skips box 410 because the target device is already powered off.

[0052] The flowchart then branches based on whether the battery includes or excludes EEPROM. If the battery does not have EEPROM (e.g., block 414), then at block 416, when the battery is decoupled (e.g., removed), a physical fuse or sensing line is interrupted at the battery connector. For example, when the battery-side connector 302 separates from the device-side connector 304, the sensing line 320 is physically interrupted at its weak point (e.g., solder joint, conductive material 332, conductive material 346). Then, at block 418, the user replaces the battery, and at block 420, after the housing is closed and the target device is powered on, the target device performs a software update to connect the replaced battery to the target device. In one example, when the electronic device 202 is powered on, the electronic device 202 performs a software update to authenticate the battery 204 and pair the battery 204 with the electronic device 202. The target device also reads the now-interrupted (e.g., open-circuit) fuse or sensing line and determines that the original battery has been tampered with (e.g., removed).

[0053] If the battery does indeed have an EEPROM (e.g., block 422), flowchart 400 proceeds directly to block 418, where the battery is replaced, and at block 420, after the casing is closed and the target device is powered on, a software update is performed to connect the replaced battery to the target device. The EEPROM contains battery information that the target device can use to determine that the replaced battery is not the original battery.

[0054] Example Method

[0055] Figure 5 and Figure 6 Example methods 500 and 600 for the right-of-service battery replacement as described herein are depicted respectively. Figure 5 An example method for pairing a replacement battery with a target device is described. Figure 6 An example method for battery authentication is described.

[0056] Methods 500 and 600 can be executed by electronic device 202, which uses identity manager module 216, battery detection module 218, and / or battery characterization module 220 to implement the described techniques. Methods 500 and 600 together provide enhanced sustainability of electronic device 202, reliability of battery 204, and improved user experience for consumers. Method 600 complements method 500 and may optionally be executed in conjunction with method 500.

[0057] Methods 500 and 600 are shown as a set of boxes that specify the operations to be performed, but are not necessarily limited to the order or combination of operations shown for performance by the individual boxes. Furthermore, any one or more operations may be repeated, combined, reorganized, or linked to provide a wide range of additional and / or alternative methods. References may be made in the sections discussed below. Figure 1 Example network environment 100 or such Figures 2 to 4 The entities or processes described in detail are for illustrative purposes only. These techniques are not limited to the execution of one or more entities operating on a single device.

[0058] At point 502, a request to replace the embedded battery in the target device is received. For example, user input may be received by electronic device 202 and may include a request to replace battery 204 in electronic device 202. In various aspects, user input may be received via an application (e.g., application 210) running on electronic device 202. In another example, user input received by electronic device 202 may include a request to replace the battery in a remote device communicatively coupled to electronic device 202 (e.g., wireless network device 102 communicating with electronic device 202 via a HAN). In one example, the user interacts with an application on a mobile phone to request a battery replacement embedded in a smart thermostat device. In another example, the target device may generate a request to replace the target device's battery and send that request to electronic device 202.

[0059] At 504, one or more images are received, including a replacement battery ID code (e.g., a first image) and a target device ID code (e.g., a second image). For example, in response to a request instructing a user to capture an image using a camera, electronic device 202 presents the instruction to the user in the form of text, audio, and / or video. In one example, the ID codes for the replacement battery and the target device are QR codes printed on labels affixed to the replacement battery and the target device, respectively. The instruction may also direct the user to capture an image of the replacement battery (e.g., a third image). In one example, receiving the request at 502 and receiving the image at 504 is a single operation.

[0060] At point 506, the user is instructed to load the captured image into the application. For example, electronic device 202 provides the user with instructions to enable the application to access the captured image. In some aspects, the application may access the camera system 224 of electronic device 202 to automatically load the image into the application when it is captured or in response to confirmation that the captured image is another acceptable user input. In another example, the instructions include the following for the user: enabling electronic device 202 to upload the captured image to cloud service 112 so that cloud service 112 can associate the replacement battery ID code with the target device ID code. Furthermore, cloud service 112 can use the image of the replacement battery to verify the replacement battery ID code (e.g., to reduce the use of counterfeit batteries). For example, cloud service 112 may verify whether the replacement battery ID code corresponds to a battery that is at least geometrically similar (e.g., shape, size) to the replacement battery in the image.

[0061] At point 508, the battery is recorded as a replacement battery designated for the target device. For example, application 210 associates the replacement battery ID code with electronic device 202 to indicate that the replacement battery will be installed to replace the original battery of electronic device 202. If the target device is a remote device, application 210 associates the replacement battery ID code with the target device ID code to indicate that the replacement battery is designated to replace the battery in the remote target device.

[0062] At point 510, the replacement battery ID code is sent (e.g., uploaded) to the server for association with the battery characterization profile. In one example, electronic device 202 sends a captured image of the replacement battery ID code (e.g., a QR code) to cloud service 112 so that cloud service 112 can obtain the identifier of the replacement battery (e.g., battery ID) from the replacement battery ID code. In another example, electronic device 202 obtains the replacement battery ID code from the captured image and sends the replacement battery ID code to cloud service 112. In yet another example, electronic device 202 obtains the battery ID from the replacement battery ID code in the captured image and sends the battery ID to cloud service 112. Cloud service 112 uses the battery ID to associate the replacement battery with a known or stored characterization profile corresponding to the replacement battery or battery type. The stored characterization profile provides instructions on how the battery replacement should be performed.

[0063] At point 512, the target device ID code is uploaded to the server for pairing with the replacement battery ID code. In one example, electronic device 202 sends a captured image of the target device ID code (e.g., a QR code) to cloud service 112. In another example, electronic device 202 obtains the target device ID code from the captured image and sends it to cloud service 112, enabling cloud service 112 to obtain the target device identifier (e.g., the target device ID) of the target device from the target device ID code. Cloud service 112 pairs the target device ID with the replacement battery ID. This pairing allows cloud service 112 to determine the compatibility of the replacement battery with the target device.

[0064] At point 514, a message regarding the compatibility of the replacement battery with the target device is received from the server. For example, electronic device 202 receives the following communication from cloud service 112: based on the uploaded battery ID and device ID code, the replacement battery is compatible with the target device and can be safely installed in the target device. In another example, a message from cloud service 112 could indicate that the replacement battery specified for installation in the target device is incompatible and should not be installed in the target device.

[0065] At point 516, the user is instructed to replace the battery in the target device with a replacement battery. For example, in response to receiving a compatibility message indicating that the replacement battery is compatible with the target device, the electronic device 202 presents instructions to the user to proceed with the installation of the replacement battery in the target device.

[0066] Then, method 500 proceeds to describe the example method for battery authentication. Figure 6 At point 602, after the battery has been replaced and the casing has been closed, the target device is powered on and paired with the app. For example, if the app runs on electronic device 202 and the target device is a remote device, the target device pairs with the app on electronic device 202 via a network (e.g., HAN, external network 108) or a direct wireless connection established between electronic device 102 and the target device. In another example, if electronic device 202 is the target device, electronic device 202 runs the app.

[0067] At 604, the device detects whether one or both of the housing and battery sensing lines are open. If the battery pack sensing line 320 and / or the housing sensing line are open, the target device detects the open circuit and determines that the battery has been tampered with. For example, the target device's ADC can read a "0" on the sensing line, indicating an open circuit.

[0068] At 606, the device determines whether the EEPROM or battery ID code matches. For example, if the replacement battery has an EEPROM onboard fuel gauge, the replacement battery may have a communication chip configured to perform a handshake with at least the target device (e.g., with battery detection module 218). Based on the handshake with the communication chip in the EEPROM on the replacement battery, battery detection module 218 can determine whether the replacement battery is the same battery specified by the application to be installed in the target device.

[0069] Similar detection can be performed by comparing the battery ID code (e.g., a QR code) obtained from a captured image with the ID code detected from a battery replacement. If the battery ID code matches the detected ID code, the device will replace the battery with the same battery specified by the application as the one to be installed in the target device.

[0070] If the EEPROM or battery ID code does not match ("No" at 606), then at 608, the device instructs the user that an incompatible battery has been installed. The device may further notify the user that the device cannot use an incompatible battery and may instruct the user to remove the incompatible battery. The device can then be powered off.

[0071] If the EEPROM or battery ID code does match ("Yes" at 606), then at 610, the device instructs the user to keep the target device plugged in for at least a threshold amount of time (e.g., 8 hours, 12 hours, 24 hours) to characterize the battery replacement. For example, an app running on electronic device 202 could instruct the user to connect the target device to line power overnight so that the target device can perform battery characterization processing. For additional safety, the device may also instruct the user to place the target device in a safe area (e.g., away from any flammable materials or substances) to prevent the battery from overheating during the characterization process.

[0072] At point 612, the target device generates a battery characterization profile. In various aspects, the target device generates the battery characterization profile by running a charge / discharge profile. The charge / discharge profile may include step charging and / or step discharging of the battery at various charging and discharging rates to monitor the battery's response and behavior, such as frequency response time, temperature, etc. The battery characterization profile provides information related to the overall health of the battery (e.g., actual performance metrics relative to the battery's design specifications). For example, the battery characterization profile may indicate whether the battery is charging correctly or not correctly based on a specific charging rate applied to the battery over a predetermined amount of time. Furthermore, the target device may disable connection to line power (e.g., an external power source) and perform one or more operations consuming a certain amount of power (e.g., playing a video with a specific audio level and / or displaying a video with specific brightness, resolution, and color) to discharge the battery and monitor the duration for which the battery's state of charge reaches a threshold level. In some implementations, the device may run the charge / discharge profile multiple times (e.g., 2, 3, 4, 5) within a duration (e.g., overnight, 4 hours, 6 hours). Determining battery health improves the safety of the target device and the user.

[0073] At point 614, the user is notified whether the battery replacement was successfully installed. For example, electronic device 202 may provide notification via application 210 that the battery replacement was successfully installed and that the replacement battery is sufficiently healthy for use by the target device. In this case, a healthy battery is one that is safe for operation by the target device (e.g., meets one or more safety standards) and will not cause damage or injury (e.g., due to overheating). A healthy battery may not necessarily meet the battery's original design specifications, but it can be safely used by the target device for its power output. If the battery is determined to be unhealthy (e.g., fails one or more safety standards), electronic device 202 may notify the user via application 210 that the battery installation was unsuccessful and / or that there was a problem with the battery installation.

[0074] Optionally, at 616, a battery characterization profile is sent to the server. For example, electronic device 202 may send a battery characterization profile generated for a replacement battery to cloud service 112, enabling cloud service 112 to track the target device relative to the replacement battery installed in the target device. Cloud service 112 may monitor the battery health of the replacement battery installed in the target device over a period of time. Cloud service 112 may utilize any suitable algorithm or model associated with charge / discharge curves, including machine learning models, to determine and track battery health. This tracking of battery health allows cloud service 112 to verify that the target device is safe for travel and complies with regulations (e.g., regulations for air travel, local government regulations). Cloud service 112 may provide device battery pairing information to requesting entities (e.g., governments, international organizations), where pairing information includes the battery health status of the replacement battery in the target device.

[0075] In some respects, the battery health monitoring service provided by cloud service 112 can be subscription-based. In others, cloud service 112 can provide the battery health monitoring service as part of a service agreement with a service provider for electronic device 202. In this way, over time, the battery health monitoring service can monitor battery health and notify the user about battery problems (e.g., battery temperature exceeding threshold limits, improper charging or discharging) and / or the need for battery replacement. The battery health monitoring service can track the battery health of various batteries paired with various devices to provide data on such replacement batteries—particularly third-party batteries. Such data can help make recommendations to the user regarding comparable (better or worse) options for replacement batteries to be installed in a particular device. These recommendations can be made via, including... Figure 9 Application 210, which describes the device management application, is provided to the user.

[0076] Example environment and equipment

[0077] Figure 7 The diagram illustrates what can be achieved as shown in the reference. Figure 1An example environment 700 is described for aspects of the home local area network and the right-of-care battery replacement method and its application. Generally, environment 700 includes a home local area network (HAN) implemented as part of a home or other type of structure with any number of wireless network devices (e.g., wireless network device 102) configured to communicate in a wireless network. For example, the wireless network devices may include a thermostat 702, a hazard detector 704 (e.g., for smoke and / or carbon monoxide), a camera 706 (e.g., indoor and outdoor), a lighting unit 708 (e.g., indoor and outdoor), and any other type of wireless network device 710 implemented inside and / or outside the structure 712 (e.g., in a home environment). In this example, the wireless network devices may also include any previously described devices, such as a border router 106 and electronic devices 202.

[0078] In Environment 700, any number of wireless network devices can be wirelessly interconnected to communicate and interact with each other. These wireless network devices are modular, intelligent, multi-sensing, and network-connected, capable of seamless integration with each other and / or with a central server or cloud computing system to provide any of a variety of useful automation goals and implementation methods. Reference Figure 8 Examples of wireless network devices that can be implemented as any of the devices described herein are shown and described.

[0079] In the implementation, the thermostat 702 may include: A learning thermostat detects environmental climate characteristics (e.g., temperature and / or humidity) and controls the HVAC system 714 in a home environment. Learning thermostats 702 and other network-connected devices "learn" by capturing the occupant settings of the device. For example, the thermostat learns preferred temperature setpoints for the following times: morning and evening, when the occupant of the structure is asleep or awake, and when the occupant is typically away from home or at home.

[0080] Hazard detector 704 can be implemented to detect the presence of hazardous substances or substances that indicate hazardous substances (e.g., smoke, fire, or carbon monoxide). In a wirelessly interconnected example, hazard detector 704 can detect the presence of smoke, thus indicating a fire in the structure. In this case, the hazard detector that first detects the smoke can broadcast a low-power wake-up signal to all connected wireless network devices. Then, other hazard detectors 704 can receive the broadcast wake-up signal and activate a high-power state for hazard detection and wireless communication to receive alarm messages. Furthermore, lighting unit 708 can receive the broadcast wake-up signal and activate in the detected hazardous area to illuminate and identify the problem area. In another example, lighting unit 708 can be activated with one illumination color to indicate a problem area or region in the structure, such as for a detected fire or forced entry, and activated with different illumination colors to indicate safe areas and / or escape routes outside the structure.

[0081] In various configurations, the wireless network device 710 may include: an entry channel interface device 716 that works in conjunction with a network-connected door lock system 718 and detects and responds to the approach or departure of persons, such as the exterior door of structure 712. The entry channel interface device 716 may interact with other wireless network devices based on whether someone has approached or entered the smart home environment. The entry channel interface device 716 may control doorbell functionality, notify persons of their approach or departure via audio or video means, and control settings for security systems, such as activating or deactivating the security system when an occupant arrives or leaves. The wireless network device 710 may also include: other sensors and detectors, such as those for detecting ambient lighting conditions, detecting room occupancy status (e.g., using an occupancy sensor 720), and controlling the power and / or dimming status of one or more lights. In some instances, the sensors and / or detectors may also control the power status or speed of a fan, such as a ceiling fan 722. Furthermore, the sensors and / or detectors may detect occupancy in a room or enclosure and control the power supply to electrical outlets or devices 724, such as if the room or structure is not occupied.

[0082] The wireless network device 710 may also include connected appliances and / or controlled systems 726—such as refrigerators, stoves and ovens, washing machines, dryers, air conditioners, pool heaters 728, irrigation systems 730, security systems 732, etc.—and other electronic and computing devices, such as televisions, entertainment systems, computers, intercom systems, garage door openers 734, ceiling fans 722, control panels 736, etc. When plugged in, the appliance, device, or system can advertise itself to the home area network as described above and can automatically integrate with controls and devices such as those on the home area network within the home. It should be noted that the wireless network device 710 may include devices physically located outside the structure but within wireless communication range, such as devices controlling the pool heater 728 or the irrigation system 730.

[0083] As described above, the HAN includes: a border router 106, which interfaces for communication with external networks outside the HAN. The border router 106 is connected to an access point 110, which is connected to an external network 108, such as the Internet. A cloud service 112 connected via the external network 108 provides services related to and / or use of devices within the HAN. As an example, the cloud service 112 may include applications for: connecting end-user devices 738—such as smartphones, tablets, etc.—to devices in the home LAN; processing data acquired in the HAN and presenting that data to the end user; linking one or more devices in the HAN 200 to a user account in the cloud service 112; providing and updating devices in the HAN; etc. For example, a user can use a network-connected computer or portable device—such as a mobile phone or tablet—to control the thermostat 702 and other wireless network devices in the home environment. Furthermore, wireless network devices can transmit information to any central server or cloud computing system via the border router 106 and access point 110. Data communication can be performed using any of a variety of custom or standard wireless protocols (e.g., Wi-Fi, ZigBee for low power, 6LoWPAN, Thread, etc.) and / or by using a variety of custom or standard wired protocols (CAT6 Ethernet, HomePlug, etc.).

[0084] Any wireless network device within a home HAN can be used as a low-power communication node to create a HAN in a home environment. Individual low-power nodes in the network can periodically send messages about what the node is sensing, and other low-power nodes in the environment—in addition to sending their own messages—can repeat these messages, thus transmitting messages between nodes (e.g., between devices) throughout the home LAN. Wireless network devices can be implemented to conserve power, particularly when battery powered, thereby utilizing low-power communication protocols to receive messages, convert the messages to other communication protocols, and send the converted messages to other nodes and / or a central server or cloud computing system. For example, an occupancy sensor 720 and / or an ambient light sensor 740 can detect occupants in a room and measure ambient light, activating the light source when the ambient light sensor 720 detects darkness in the room and when the occupancy sensor 720 detects someone in the room. Furthermore, sensors can include low-power wireless communication chips (e.g., IEEE 802.15.4 chips, Thread chips, ZigBee chips) that periodically send messages about room occupancy and the amount of light in the room, including immediate messages consistent with those from the occupancy sensor detecting the presence of a person in the room. As described above, these messages can be wirelessly sent between nodes within a home environment (e.g., between network-connected devices) and to a central server or cloud computing system via the Internet using a home LAN.

[0085] In other configurations, various wireless network devices can be used as "tripwires" for alarm systems in a home environment. For example, an alarm can still be triggered by receiving occupancy, movement, heat, sound, or other messages from one or more low-power mesh nodes in the home LAN, even if an intruder bypasses detection by alarm sensors located at windows, doors, and other entry points into the structure or environment. In other implementations, the home LAN can be used to automatically turn lighting units 708 on and off as people move between rooms within the structure. For example, wireless network devices can detect movement of people through the structure and transmit corresponding messages via nodes in the home LAN. Using messages indicating which rooms are occupied, other wireless network devices receiving the messages can be activated and / or deactivated accordingly. As mentioned above, the home LAN can also be used to provide exit lighting in emergency situations, such as by activating appropriate lighting units 708 leading to safe exits. Lighting units 708 can also be activated to indicate the direction along the exit route that people should proceed to safely leave the structure.

[0086] Various wireless network devices can also be integrated and communicate with wearable computing devices 742, such as those used to identify and locate occupants of a structure and adjust temperature, lighting, sound systems, etc. accordingly. Other implementations include RFID sensing (e.g., people with RFID bracelets, necklaces, or key cards), synthetic vision technologies (e.g., cameras and facial recognition processors), audio technologies (e.g., voice, sound pattern, and vibration pattern recognition), ultrasonic sensing / imaging technologies and infrared or near-field communication (NFC) technologies (e.g., people wearing infrared or NFC-enabled smartphones), and rule-based inference engines or artificial intelligence technologies to derive useful conclusions about the location of occupants in a structure or environment based on the sensed information.

[0087] In other implementations, such human-oriented functions of human comfort zone networks, human health zone networks, human safety zone networks, and / or service robots can be enhanced through logical integration with other wireless network devices and sensors in the environment, based on rule-based inference techniques or artificial intelligence, to achieve better performance for these functions. In an example related to human health zones, the system could use rule-based inference and artificial intelligence techniques to detect whether a household pet is moving toward the occupant's current location (e.g., using any wireless network devices and sensors). Similarly, a hazard detector service robot could be notified that temperature and humidity levels in the kitchen are rising, and a hazard detection threshold, such as a smoke detection threshold, could be temporarily raised based on the inference that any slight increase in ambient smoke levels is likely due to cooking activity rather than a genuine hazardous situation. Any service robot configured for any type of monitoring, detection, and / or service can be implemented as a mesh node device on a home LAN, thus conforming to wireless interconnection protocols used for communication on the home LAN.

[0088] The wireless network device 710 may also include a network-connected alarm clock 744 for each individual occupant in a home environment. For example, an occupant may customize and set the alarm device for a wake-up time (such as for the next day or week). Artificial intelligence can be used to consider the occupant's reaction to the alarm when it is triggered and to infer preferred sleep patterns over time. Individual occupants can then be tracked within the home network based on a unique signature determined from data obtained from sensors located in the wireless network device—such as sensors including ultrasonic sensors, passive IR sensors, etc. The occupant's unique signature can be based on a combination of movement patterns, voice, height, size, etc., and using facial or audio recognition technology.

[0089] In the example of wireless interconnection, an individual's wake-up time can be correlated with thermostat 702 to effectively control the HVAC system to preheat or cool the structure to desired sleep and wake-up temperature settings. Preferred settings can be learned over time, such as by capturing the temperature set in the thermostat before a person goes to sleep and upon waking. The collected data may also include biometric indicators of the person, such as breathing patterns, heart rate, movement, etc., based on which inferences are made in conjunction with data indicating when the person actually wakes up. Other wireless network devices can use the data to provide other automation objectives, such as adjusting thermostat 702 to preheat or cool the environment to desired settings, and turning lighting unit 708 on or off.

[0090] In some implementations, wireless network devices can also be used for sound, vibration, and / or motion sensing, such as to detect tap water and determine inferences about water use in the home environment based on algorithms and mappings of water use and consumption. This can be used to determine the characteristics or fingerprint of each water source in the home, and is also known as “audio fingerprint water use.” Similarly, wireless network devices can be used to detect subtle sounds, vibrations, and / or movements of unwanted pests—such as rats and other rodents—as well as termites, cockroaches, and other insects. The system can then notify occupants of suspected pests in the environment, such as by using warning messages to help facilitate early detection and prevention.

[0091] Environment 700 may include one or more wireless network devices acting as hub 746. Hub 746 (e.g., hub 120) may be a general-purpose home automation hub or a hub for specific applications, such as a security hub, energy management hub, HVAC hub, etc. The functionality of hub 746 can also be integrated into any wireless network device, such as a network-connected thermostat device or border router 106. The managed functionality on hub 746 in architecture 712 can improve reliability when the user's internet connection is unreliable, can reduce latency in operations that would typically require a connection to cloud service 112, and can meet system and regulatory constraints regarding local access between wireless network devices.

[0092] Furthermore, example environment 700 includes a network-connected speaker 748. The network-connected speaker 748 provides voice assistance services, including providing voice control of network-connected devices. The functionality of hub 746 can be hosted within the network-connected speaker 748. The network-connected speaker 748 can be configured to communicate via a HAN, which may include a wireless mesh network, a Wi-Fi network, or both.

[0093] Figure 8An example wireless network device 800 is illustrated, which can be implemented as any of the wireless network devices 102 (e.g., electronic device 202 or other target devices) in a home local area network according to one or more aspects of the right-of-care battery replacement method and its application as described herein. Device 800 can be integrated with electronic circuitry, microprocessors, memory, input / output (I / O) logic control, communication interfaces and components, and other hardware, firmware, and / or software to implement a device in a home local area network. Furthermore, wireless network device 800 can be implemented using various components, such as reference... Figure 9 The example device shown is further described with respect to any number of components and combinations of different components.

[0094] In this example, the wireless network device 800 includes a low-power microprocessor 802 and a high-power microprocessor 804 (e.g., a microcontroller or digital signal processor) that process executable instructions. The device also includes input / output (I / O) logic control 806 (e.g., including electronic circuitry). The microprocessor may include integrated circuits, programmable logic devices, logic devices formed using one or more semiconductors, and components implemented in silicon and / or other hardware forms, such as processors and memory systems implemented as a system-on-a-chip (SoC). Alternatively or additionally, the device may be implemented using software, hardware, firmware, or any one or a combination of fixed logic circuitry that can be implemented using processing and control circuitry. The low-power microprocessor 802 and the high-power microprocessor 804 may also support one or more different device functions. For example, the high-power microprocessor 804 may perform computationally intensive operations, while the low-power microprocessor 802 may manage less complex processing, such as detecting hazard or temperature from one or more sensors 808. The low-power microprocessor 802 may also wake up or initialize the high-power microprocessor 804 for computationally intensive processing.

[0095] One or more sensors 808 can be implemented to detect various properties, such as acceleration, temperature, humidity, water, supplied power, proximity, external motion, device motion, sound signals, ultrasonic signals, light signals, fire, smoke, carbon monoxide, GPS signals, radio frequency (RF), other electromagnetic signals or fields, etc. Therefore, sensor 808 can include any one or a combination of temperature sensors, humidity sensors, hazard-related sensors, other environmental sensors, accelerometers, microphones, light sensors including cameras (e.g., charge-coupled devices or video cameras), active or passive radiation sensors, GPS receivers, and RFID detectors. In an implementation, wireless network device 800 can include one or more primary sensors and one or more auxiliary sensors, such as primary sensors that sense data from the core operating center of the device (e.g., sensing temperature in a thermostat or smoke in a smoke detector), while auxiliary sensors can sense other types of data (e.g., motion, light, or sound), which can be used for energy efficiency or automation goals. In some aspects, sensor 808 may include an ADC sensor configured to measure voltages on one or more sensing lines (e.g., sensing line 320) or on one or more pins coupled to the sensing lines using an ADC integrated with electronic device 202. As described herein, the ADC sensor may (i) measure a “1” on the sensing line when sensing line 320 is closed to indicate that battery 204 is an original installation, or (i) measure a “0” on the sensing line when sensing line 320 is open (e.g., interrupted), indicating that battery 204 has been tampered with (e.g., removed and possibly replaced). The ADC sensor may also measure a second sensing line connected to the housing of electronic device 202. For example, the ADC sensor may (i) measure a “1” on the second sensing line, indicating that the housing has not been opened since factory assembly, or (ii) measure a “0” when the second sensing line is interrupted, indicating that the housing has been opened.

[0096] Wireless network device 800 includes a memory device controller 810 and a memory device 812, such as any type of non-volatile memory and / or other suitable electronic data storage device. Wireless network device 800 may also include various firmware and / or software, such as an operating system 814 maintained by memory as computer-executable instructions and executed by a microprocessor. Device software may also include a battery management application 816, which implements aspects of a right-of-service battery replacement method and its application. Wireless network device 800 also includes a device interface 818 for interfacing with another device or peripheral component, and includes an integrated data bus 820 that couples various components of the wireless network device for data communication between components. The data bus in the wireless network device may also be implemented as any one or a combination of different bus structures and / or bus architectures.

[0097] Device interface 818 may receive input from and / or provide information to the user (e.g., as a user interface), and the received input may be used to determine settings. Device interface 818 may also include mechanical or virtual components responsive to user input. For example, the user may mechanically move a sliding or rotatable component, or movement along a touchpad may be detected, and such movement may correspond to adjustments in device settings. Physical and virtual movable user interface components may allow the user to adjust settings along a portion of a surface continuity. Device interface 818 may also receive input from any number of peripheral devices, such as buttons, keypads, switches, microphones, and imaging devices (e.g., camera devices).

[0098] Wireless network device 800 may include a network interface 822 (e.g., network interface 222), such as a home LAN interface for communicating with other wireless network devices in a home LAN, and an external network interface for network communication, such as via the Internet. Wireless network device 800 also includes a wireless radio system 824 for wirelessly communicating with other wireless network devices via the home LAN interface and for multiple different wireless communication systems. The wireless radio system 824 may include Wi-Fi, Bluetooth, etc. TM Mobile broadband, BLE, and / or point-to-point IEEE 802.15.4. Each of the different radio systems may include radio equipment, antennas, and chipsets implemented for a specific wireless communication technology. The wireless network device 800 also includes a power supply 826, such as a battery (e.g., battery 204) and / or a cable connecting the device to line voltage. AC power can also be used to charge the device's battery.

[0099] Figure 9 The illustration depicts an example system 900 including an example device 902 that can be implemented as any of the example devices 102 (e.g., electronic device 202 or other target devices), the wireless network device 102 being implemented as previously described. Figures 1 to 8 The aforementioned battery replacement method for maintenance rights and its applications are described. Example device 902 can be any type of computing device, client device, mobile phone, tablet, communication, entertainment, gaming, media playback, and / or other type of device. Furthermore, example device 902 can be implemented as any other type of wireless network device configured for communication on a home local area network, such as a thermostat, hazard detector, camera, lighting unit, debugging device, router, border router, connection router, connection device, terminal device, bootloader, access point, and / or other wireless network device.

[0100] Device 902 includes a communication device 904 that enables wired and / or wireless communication of device data 906, such as data transmitted between devices in a home area network, data being received, data scheduled for broadcast, data packets, data synchronized between devices, etc. Device data may include any type of communication data, as well as audio, video, and / or image data generated by applications running on the device. Communication device 904 may also include transceivers for cellular telephone communication and / or for network data communication.

[0101] Device 902 also includes an input / output (I / O) interface 908, such as a data network interface (e.g., network interface 222) that provides connections and / or communication links between the device, data networks (e.g., home area networks, external networks, etc.) and other devices. The I / O interface can be used to couple the device to any type of component, peripheral device, and / or accessory device. The I / O interface also includes a data input port through which any type of data, media content, and / or input can be received, such as user input to the device and any type of communication data, as well as audio, video, and / or image data received from any content and / or data source.

[0102] Device 902 includes a processing system 910 (e.g., processor 206), which may be implemented at least partially in hardware, such as any type of microprocessor, controller, etc., that processes executable instructions. The processing system may include integrated circuits, programmable logic devices, logic devices formed using one or more semiconductors, and components implemented in silicon and / or other hardware forms, such as processors and memory systems implemented as a system-on-a-chip (SoC). Alternatively or additionally, the device may be implemented using software, hardware, firmware, or any one or a combination of fixed logic circuitry that can be implemented using processing and control circuitry. Device 902 may further include any type of system bus or other data and command transfer systems coupling various components within the device. The system bus may include different bus structures and architectures, and any one or a combination of control lines and data lines.

[0103] Device 902 also includes computer-readable storage memory 912 (e.g., CRM 208), such as a data storage device accessible by a computing device, providing persistent storage for data and executable instructions (e.g., software applications, modules, programs, functions, etc.). The computer-readable storage memory described herein excludes propagated signals. Examples of computer-readable storage memory include volatile and non-volatile memory, fixed and removable media devices, and any suitable memory device or electronic data storage device that maintains data for access by a computing device. Computer-readable storage memory can include various implementations of random access memory (RAM), read-only memory (ROM), flash memory, EPROM, EEPROM, and other types of storage memory in various memory device configurations.

[0104] Computer-readable storage 912 provides storage for device data 906 and various device applications 914 (e.g., application 210), such as an operating system (e.g., operating system 214) maintained in computer-readable storage and executed by processing system 910 as a software application. Device application 914 may also include a device manager, such as any form of control application, software application, signal processing and control module, device-specific native code, device-specific hardware abstraction layer, etc. In this example, the device application also includes a device management application 212 that implements aspects of the right-of-service battery replacement method and its applications, such as when example device 902 is implemented as electronic device 202 and the target device is remote and implemented as any wireless network device described herein. In various aspects, device management application 212 implements identity manager module 216, battery detection module 218, and battery characterization module 220 according to the techniques described herein.

[0105] Device 902 also includes an audio and / or video system 916 that generates audio data for audio device 918 and / or display data for display device 920 (e.g., monitor 226). The audio and / or display devices include any device that processes, displays, and / or otherwise renders audio, video, display, and / or image data—such as image content from digital photographs. In some implementations, the audio and / or display devices are integrated components of example device 902. Alternatively, the audio and / or display devices are peripheral components external to the example device. In various aspects, at least a portion of the techniques described for the right-of-service battery replacement method and its application can be implemented in a distributed system—such as a “cloud” 922 in platform 924. Cloud 922 includes and / or represents platform 924 for services 926 and / or resources 928.

[0106] Platform 924 abstracts the underlying functionality of hardware, such as server devices (e.g., included in service 926) and / or software resources 928 (e.g., included as resource 928), and connects example device 902 to other devices, servers, etc. Resource 928 may also include applications and / or data that can be utilized while performing computer processing on a remote server of example device 902. Furthermore, service 926 and / or resource 928 can facilitate subscriber network services, such as via the Internet, cellular networks, or Wi-Fi networks. Platform 924 can also be used to abstract and scale resources to serve the demand for resource 928 implemented via the platform, such as in interconnected devices with functionality distributed throughout system 900. For example, this functionality may be implemented partly at example device 902 and partly via platform 924 through the abstract cloud 922.

[0107] The following describes some examples:

[0108] A method for servicing battery replacement in at least one electronic device, the method comprising: receiving a request to replace a battery in a target device with a replacement battery; receiving at least one image of a replacement battery identification code associated with the replacement battery and a target device identification code associated with the target device; sending the replacement battery identification code and the target device identification code to a server; receiving a compatibility message from the server, the compatibility message indicating, based on the replacement battery identification code and the target device identification code, that the replacement battery is compatible with the target device; in response to receiving the compatibility message from the server, instructing a user to replace the battery in the target device with the replacement battery; in response to the target device being restarted, receiving from the target device an indication that: a link configured to physically and electrically couple a device-side connector of the target device to a battery-side connector of the battery is open, and that the replacement battery installed in the target device corresponds to the replacement battery identification code in the at least one image; and, based on the indication, notifying the user that the replacement battery has been successfully installed in the target device.

[0109] Receiving a request and receiving at least one image can be a single operation, such that the request and the at least one image are received simultaneously at the electronic device.

[0110] At least one of the replacement battery identification code or the target device identification code may be a machine-readable optical tag.

[0111] The method may further include instructing the user to capture the at least one image using a camera; and the transmission of the battery replacement identifier and the target device identifier may include sending the at least one image to the server.

[0112] The method may further include: instructing the user to capture a second image of the replaced battery using the camera; and sending the second image to the server to verify the battery replacement identification code.

[0113] The link may include at least one of a sensing line or a fuse.

[0114] The method may further include receiving a notification from the target device indicating that the target device has been tampered with based on the detection that an additional link has been interrupted, and that the casing of the target device has been opened.

[0115] The method may further include: determining that the replacement battery has an electrically erasable programmable read-only memory (EEPROM) chip storing a battery identifier of the replacement battery; and instructing the user to keep the target device connected to an external power source for at least a threshold time period based on the determination that the battery identifier matches the replacement battery identification code captured in the first image, to characterize the replacement battery.

[0116] The method may further include: informing the user of the health status of the replacement battery based on a battery characterization profile generated by running a charge / discharge profile on the replacement battery installed in the target device during the threshold time period.

[0117] The charging / discharging profile may include a step charging profile and a step discharging profile.

[0118] The battery characterization profile can represent the health status of the replaced battery based on the charging and discharging rates of the replaced battery during the execution of the charging / discharging profile.

[0119] The method may further include: sending the battery characterization profile to the server for tracking the target device relative to the replacement battery installed in the target device, and for monitoring the battery health of the replacement battery over a period of time.

[0120] The method may further include: determining, in response to receiving the instruction, that the replacement battery has been successfully installed in the target device; and determining, in response to receiving the battery characterization profile, that the battery is safe for use in the target device.

[0121] The target device may be a wireless network device that is remotely coupled to the electronic device and communicates with the electronic device via a home area network.

[0122] The target device may be an electronic device, such that the target device and the electronic device are the same device.

[0123] The method may further include recording the battery replacement as specified as replacing the battery in the target device.

[0124] An electronic device includes: a camera system; a memory; and one or more processors configured to execute instructions in the memory to implement a device management application, the device management application being configured to: communicate with the camera system to capture one or more images; and perform the methods described above.

[0125] in conclusion

[0126] Although aspects of the right-of-service battery replacement method and its application have been described in language specific to features and / or methods, the subject matter of the appended claims is not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as exemplary implementations of the technology for the right-of-service battery replacement method and its application, and other equivalent features and methods are intended to be within the scope of the appended claims. Furthermore, various different aspects have been described, and it should be appreciated that each described aspect can be implemented independently or in combination with one or more other described aspects.

Claims

1. A method for replacing a repairable battery in at least one electronic device, the method comprising: Receive a request to replace the battery in the target device using a battery replacement service; Receive at least one image of a replacement battery identification code associated with the replacement battery and a target device identification code associated with the target device; Send the battery replacement identifier code and the target device identifier code to the server; The server receives a compatibility message indicating that the replacement battery is compatible with the target device based on the replacement battery identifier and the target device identifier. In response to receiving the compatibility message from the server, the user is instructed to replace the battery in the target device with the replacement battery. In response to the target device being restarted, an indication is received from the target device that the link is open and that the replacement battery installed in the target device corresponds to the replacement battery identification code in the at least one image, the link being configured to physically and electrically couple the device-side connector of the target device to the battery-side connector of the battery; as well as Based on the instructions, the user is notified that the replacement battery has been successfully installed in the target device.

2. The method according to claim 1, wherein, Receiving a request and receiving at least one image are a single operation, such that the request and the at least one image are received simultaneously at the electronic device.

3. The method according to claim 1, wherein, At least one of the battery replacement identification code and the target device identification code is a machine-readable optical tag.

4. The method according to claim 1, wherein: The method further includes: instructing the user to capture the at least one image using a camera; and Sending the battery replacement identifier and the target device identifier includes sending the at least one image to the server.

5. The method of claim 4, further comprising: The instruction states that the user uses the camera to capture a second image of the battery replacement. as well as The second image is sent to the server to verify the battery replacement identification code.

6. The method according to claim 1, wherein, The link includes at least one of a sensing line or a fuse.

7. The method of claim 1, further comprising: A notification is received from the target device indicating that the target device has been tampered with based on the detection of an interruption of an additional link, and that the casing of the target device has been opened.

8. The method of claim 1, further comprising: It is determined that the replacement battery has an electrically erasable programmable read-only memory (EEPROM) chip that stores the battery identifier of the replacement battery; as well as Based on determining that the battery identifier matches the replacement battery identification code captured in the at least one image, the user is instructed to keep the target device connected to an external power source for at least a threshold time period to characterize the replacement battery.

9. The method of claim 8, further comprising: The user is notified of the health status of the replacement battery based on a battery characterization profile generated by running a charge / discharge profile on the replacement battery installed in the target device during the threshold time period.

10. The method according to claim 9, wherein, The battery characterization profile represents the health status of the replaced battery based on the charging and discharging rates of the replaced battery during the execution of the charge / discharge profile.

11. The method of claim 9, further comprising: The battery characterization profile is sent to the server for tracking the target device relative to the replacement battery installed in the target device and for monitoring the battery health of the replacement battery over a period of time.

12. The method of claim 9, further comprising: In response to receiving the instruction, it is determined that the replacement battery has been successfully installed in the target device; as well as In response to receiving the battery characterization profile, it is determined that the battery is safe for use in the target device.

13. The method according to claim 1, wherein, The target device is a wireless network device that is remotely coupled to the electronic device and communicates with it via a home area network.

14. The method according to any one of claims 1 to 13, wherein, The target device is the electronic device.

15. An electronic device comprising: Camera system; Memory; as well as One or more processors, configured to execute instructions in the memory to implement a device management application, the device management application being configured to: Communicate with the camera system to capture one or more images; as well as Perform the method according to any one of claims 1 to 14.

Images