SE1551240A1

SE1551240A1 - Apparatus and system for providing a connected battery

Info

Publication number: SE1551240A1
Application number: SE1551240A
Authority: SE
Inventors: wolfram Ted
Original assignee: Husqvarna Ab
Priority date: 2015-09-29
Filing date: 2015-09-29
Publication date: 2017-03-30
Also published as: WO2017056000A1; US20190058337A1

Abstract

A battery pack may include one or more rechargeable battery cells and processing circuitry. The processing circuitry may be configured to control extraction of operational parameters from a device to which the battery pack is operably coupled and wireless communication of the operational parameters from the battery pack to an access point. The operational parameters may include at least one parameter that is not determined based on measuring battery parameters. The device is one of a plurality of different devices with which the battery pack is configured to be operably coupled.

Description

P3l59SE00 APPARATUS AND SYSTEM FOR PROVIDING A CONNECTED BATTERY TECHNICAL FIELD[0001] EXample embodiments generally relate to battery technology and, more particularly,relate to a battery that can act as a gateway between a plurality of different devices and various nCtWOfk ICSOUICCS.

BACKGROUND id="p-2" id="p-2"

[0002] Property maintenance tasks are commonly performed using various tools and/ ormachines that are configured for the performance of corresponding specific tasks. Certain tasks,like cutting trees, trimming vegetation, blowing debris and the like, are typically performed byhand-held tools or power equipment. The hand-held power equipment may often be powered bygas or electric motors. Until the advent of battery powered electric tools, gas powered motorswere often preferred by operators that desired, or required, a great deal of mobility.Accordingly, many outdoor power equipment devices are powered by gas motors because theymay be required to operate over a relatively large range. However, as battery technologycontinues to improve, the robustness of battery powered equipment has also improved and suchdevices have increased in popularity. id="p-3" id="p-3"

[0003] The batteries employed in outdoor power equipment may, in some cases, beremovable and/or rechargeable assemblies of a plurality of smaller cells that are arrangedtogether in order to achieve desired output characteristics. The groups of smaller cells may belocated or housed within a housing to form a battery pack. The battery pack may have physicaland electrical design characteristics that determine which devices can be powered by the batterypack. ln the past, specific unique battery packs have often been employed for each specificdifferent type of outdoor power equipment or for different brands. Thus, each household orbusiness may have substantially an equal number of battery packs to the number of devices thatare powered by such battery packs. This can consume more storage space, and also typically means that a diverse array of different battery chargers is also necessary.

P3l59SE00 id="p-4" id="p-4"

[0004] Thus, there is a desire to reduce the diversity of battery pack designs used to poweroutdoor power equipment. However, there is also a desire to incorporate outdoor power equipment into the ever expanding world of the Internet of Things.

BRIEF SUMMARY OF SOME EXAMPLES id="p-5" id="p-5"

[0005] Some example embodiments may provide a battery pack that is capable of being usedwith a plurality of different types of power tools such as outdoor power equipment. However,example embodiments may further provide the capability for the battery pack to extract datafrom the various different types of devices that can be powered by the battery pack. Theextracted data can thereafter be stored and/or transn1itted to another device, which may beassociated with a management entity or a particular user. The battery pack may thereforebecome a gateway for entry of the device being powered by the battery pack into the Internet ofThings. id="p-6" id="p-6"

[0006] ln one example embodiment, a battery pack is provided. The battery pack mayinclude one or more rechargeable battery cells and processing circuitry. The processing circuitrymay be configured to control extraction of operational parameters from a device to which thebattery pack is operably coupled and wireless communication of the operational parameters fromthe battery pack to an access point. The operational parameters may include at least oneparameter that is not detern1ined based on measuring battery parameters. The device is one of aplurality of different devices with which the battery pack is configured to be operably coupled.[0007] ln another example embodiment, a communications manager for a battery packcomprising one or more rechargeable battery cells is provided. The communications managermay include processing circuitry configured to control extraction of operational parameters froma device to which the battery pack is operably coupled and wireless communication of theoperational parameters from the battery pack to an access point. The operational parameters mayinclude at least one parameter that is not determined based on measuring battery parameters.

The device is one of a plurality of different devices with which the battery pack is configured tobe operably coupled. id="p-8" id="p-8"

[0008] ln another example embodiment, a system including battery powered devices isprovided. The system includes a plurality of different battery powered devices, an access point configured for wireless communication, and a battery pack comprising one or more rechargeable P3l59SE00 battery cells and processing circuitry. The processing circuitry is configured to controlextraction of operational parameters from a selected one of the devices to Which the battery packis operably coupled, the operational parameters including at least one parameter that is notdetermined based on measuring battery parameters, and Wireless communication of theoperational parameters from the battery pack to an access point. id="p-9" id="p-9"

[0009] Some example embodiments may improve the user experience and/ or the efficacy of battery poWered equipment.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S) id="p-10" id="p-10"

[0010] Having thus described some example embodiments in general terms, reference Willnow be made to the accompanying draWings, Which are not necessarily draWn to scale, andWherein: id="p-11" id="p-11"

[0011] FIG. l illustrates a concept diagram of a system in Which a connected battery mayoperate in accordance With an example embodiment; id="p-12" id="p-12"

[0012] FIG. 2 illustrates a block diagram of circuitry for accomplishing tWo levels ofconnectivity for a connected battery in accordance With an example embodiment; id="p-13" id="p-13"

[0013] FIG. 3 illustrates a block diagram of processing circuitry of the connected battery inaccordance With an example embodiment; id="p-14" id="p-14"

[0014] FIG. 4 illustrates a control ﬂoW diagram for execution of a shutdoWn based on batterydata extracted from a device in accordance With an example embodiment; id="p-15" id="p-15"

[0015] FIG. 5 illustrates a control ﬂoW diagram for delayed transmission of operationalparameters using a connected battery in accordance With an example embodiment; id="p-16" id="p-16"

[0016] FIG. 6 illustrates a control ﬂoW diagram for substantially real-time transmission ofoperational parameters using a connected battery in accordance With an example embodiment;[0017] FIG. 7 illustrates a control ﬂoW diagram for identification based configuration of adevice using a connected battery in accordance With an example embodiment; and id="p-18" id="p-18"

[0018] FIG. 8 illustrates a control ﬂoW diagram for remote provisioning of configuration information for a device using a connected battery in accordance With an example embodiment.

P3l59SE00 DETAILED DESCRIPTION id="p-19" id="p-19"

[0019] Some example embodiments now will be described more fully hereinafter withreference to the accompanying drawings, in which some, but not all example embodiments areshown. Indeed, the examples described and pictured herein should not be construed as beinglirr1iting as to the scope, applicability or configuration of the present disclosure. Rather, theseexample embodiments are provided so that this disclosure will satisfy applicable legalrequirements. Like reference numerals refer to like elements throughout. Furthermore, as usedherein, the term "or" is to be interpreted as a logical operator that results in true whenever one ormore of its operands are true. As used herein, operable coupling should be understood to relateto direct or indirect connection that, in either case, enables functional interconnection orinteraction of components that are operably coupled to each other. id="p-20" id="p-20"

[0020] Some example embodiments may provide for a battery pack that can be useful inconnection with battery powered tools or battery powered outdoor power equipment. Outdoorpower equipment that is battery powered, and battery powered tools generally, typically includebattery packs that have a given voltage or power rating, and have physical characteristics thatmust match the receptacle of the device that is to be powered. ln order to achieve sufficientpower, cells of the battery pack may be organized and interconnected (e. g., in an arrangement ofseries and/ or parallel electrical connections) to group the cells within the battery pack in amanner that achieves desired electrical characteristics. The battery pack may be inserted into anaperture (e. g., a receptacle) of the piece of equipment that is to be powered so that thecorresponding piece of equipment (e.g., hand-held, ride-on, or walk-behind outdoor powerequipment) is enabled to be mobile. However, in some cases, the battery pack may be insertedinto a backpack or other carrying implement that the equipment operator may wear, and thebackpack may have an interface portion to be inserted into the aperture of the piece ofequipment. id="p-21" id="p-21"

[0021] The battery pack is typically rechargeable, and may generate heat during chargeand/or discharge due to the electrochen1ical reactions that are employed to produce electricity.Thus, the battery packs and/or their chargers may sometimes incorporate cooling assemblies forpreventing heat generation from becoming excessive, and damaging the cells of the battery pack.Accordingly, it should be appreciated that the battery pack generally needs to have a physical structure that supports the cells of the battery pack and cooling equipment (if employed), and that P3159SE00 physical structure needs to further incorporate electrical contacts that allow the battery pack to beoperably coupled to the electric motor of the device being powered and to the charger that willrecharge the battery pack. To make the battery pack suitable for use with a plurality of differenttypes of devices (including outdoor power equipment and chargers), the devices themselves musthave consistently designed apertures or other battery receptacles that correspond to the physicalcharacteristics of the battery pack. Moreover, the electrical contacts of the different types ofdevices must also be suitable for coupling with the contacts of the battery pack when the batterypack is inserted into the respective different types of devices. id="p-22" id="p-22"

[0022] Example embodiments are directed to a battery pack that has a physical structure thatenables the battery pack to be used with a plurality of different types of devices. However,example embodiments further enable the battery pack to include a communication capability thatenables processing circuitry on or associated with the battery pack to be used to extract (e. g.,receive, collect, obtain, etc.) operational parameters or other such data from or about the devicebeing powered by the battery pack. Furthermore, the battery pack may include communicationscircuitry that enables the operational parameters to be communicated to one or more networkdevices. As such, the battery pack is essentially connected and connectable to network resourceson a real time or post hoc basis. Thus, the battery pack may be referred to as a "connectedbattery." id="p-23" id="p-23"

[0023] FIG. 1 illustrates a concept diagram of a system 100 in which a connected battery ofan example embodiment may operate. As shown in FIG. 1, the system 100 includes a pluralityof individual pieces of outdoor power equipment including a first device 110, a second device120, and a third device 130. The system 100 also includes a charger 140 for charging aconnected battery 150 of an example embodiment and an access point 160. The access point 160enables the devices to be operably coupled to a network 170 to which user equipment 180 maybe connected. id="p-24" id="p-24"

[0024] ln the pictured example, the first device 110 is a blower, the second device 120 is atrimmer, and the third device 130 is a chainsaw. However, these three example devices aremerely shown to illustrate the potential for interoperability of the connected battery 150 with aplurality of different types of devices in the outdoor power equipment context. Thus, otherpieces of outdoor power equipment could be substituted or added in other examples. For example, string trimmers, hedgers, and even lawn mowers (walk behind and/or ride-on) or other P3159SE00 devices could be utilized in connection with other example embodiments. Any battery poweredpiece of outdoor power equipment that can be operably coupled to the connected battery 150 forboth power provision purposes and communication purposes, as described herein, could be partof the system 100, and the system 100 could include as few as a single device or as many asdozens of devices. id="p-25" id="p-25"

[0025] Additionally, the fact that three devices that could be powered by the connectedbattery 150 are shown is merely illustrative of the potential for multiplicity relative to thenumber of devices that the connected battery 150 can power, and the number of differentinstances of the connected battery 150 that can communicate with the access point 160.Moreover, it should further be appreciated that one instance of the connected battery 150 couldbe charged using the charger 140, and that same instance of the connected battery 150 couldpower each respective different one of the first, second and third devices 110, 120 and 130 in anyorder while charged. After charge depletion, the instance of the connected battery 150 could berecharged at the charger 140. Alternatively, separate instances of the connected battery 150could power each respective one of the first, second and third devices 110, 120 and 130 while afourth instance of the connected battery 150 is charging at the charger 140. id="p-26" id="p-26"

[0026] ln the example in which a single instance of the connected battery 150 is used witheach device, the single instance of the connected battery 150 may communicate with the accesspoint 160 while powering each of the first, second and third devices 110, 120 and 130, and whilebeing charged on the charger 140. Meanwhile, in an example in which multiple instances of theconnected battery 150 are employed to power respective ones of the first, second and thirddevices 110, 120 and 130, each such instance may communicate with the access point 160simultaneously or in sequence. id="p-27" id="p-27"

[0027] The connected battery 150 is shown communicating with the access point 160 whileinstalled for powering each of the first, second and third devices 110, 120 and 130, and beingcharged by the charger 140. However, it should be appreciated that the connected battery 150may also communicate with the access point 160 when not installed or being charged in somealternative examples. Moreover, in some cases, the connected battery 150 could be used indifferent ones of the first, second and third devices 110, 120 and 130 at respective different times and extract operational parameters from each respective device while installed therein.

P3159SE00 However, the operational parameters may be stored locally at the connected battery 150 forcommunication to the access point 160 at some later time. id="p-28" id="p-28"

[0028] lt should also be appreciated that the connected battery 150 may have differenttriggers or stimuli that cause the connected battery 150 to communicate with the access point160. ln some cases, initiation of connection of the connected battery 150 with a device (e. g., thefirst, second and third devices 110, 120 and 130, or the charger 140) may trigger communicationwith the access point 160. Alternatively or additionally, termination of connection may triggercommunication, or various time or event based triggers may cause the connected battery 150 toconnect to the access point 160. However, in some cases, the access point 160 may pollinstances of the connected battery 150 for data, or may otherwise initiate communication withone or more instances of the connected battery 150. id="p-29" id="p-29"

[0029] Once data (such as the operational parameters) has been eXtracted from devices towhich the connected battery 150 is operably coupled and has been communicated to the accesspoint 160, the data may be accessible by user equipment 180 via the network 170. The network170 may therefore be a local area network, or a wide area network (e.g., the Internet), and theuser equipment 180 could be a personal computer, laptop computer, smart phone, tablet, smartwatch, server, or any of a number of other such devices. The access point 160 may communicatewith the connected battery 150 and/or other devices via short range wireless communication(e.g., Bluetooth, WiFi, and/or the like), and the access point 160 may have a wired or longerrange wireless connection to the network 170 and/or to the user equipment 180. Moreover, insome cases, if the user equipment 180 has wireless communication capabilities, the userequipment 180 could actually act as the access point 160. Thus, for example, in some cases, theaccess point 160 could be a communication node that provides a gateway to the network 170 sothat user equipment that is capable of communication with the network 170 can interface withthe connected battery 150 and the devices (via the connected battery 150). However, in othercases, the access point 160 could be, e. g., a smart phone or smart watch having Bluetoothcapability, and the user can interact directly with the connected battery 150 (via the smart phoneor smart watch) without other network resources therebetween. id="p-30" id="p-30"

[0030] As may be appreciated from the discussion above, the connected battery 150 includescircuitry to enable the batteries of the connected battery 150 to be charged (e.g., by the charger 140) and to enable the power from the batteries to be delivered to the devices being powered by P3159SE00 the connected battery 150, and also includes communication circuitry to support communicationwith the access point 160. Thus, the connected battery 150 is configured to be operably coupledto a device on two levels. First, there is a power transfer communication level of connectivity,and secondly there is a data communication level of connectivity. As such, the connected battery150 can, for example, both provide power to a device and communicate with the device andother external devices or networks. In some cases, the connected battery 150 is configured toextract information about the operation of the device (e. g., operational parameters) that are bothrelated to the power provision function of the connected battery 150 and unrelated to the powerprovision function of the connected battery 150. Thus, for example, the connected battery 150may be configured to simultaneously power the device, manage that power provision, extractinformation from the device and provide the extracted information to the network 170.Moreover, the connected battery 150 may connect the device to a local and/ or remote networkvia which a user may be enabled to appreciate certain performance characteristics of the devices(or operators thereof) or otherwise interact with such devices to enhance maintenance,management or otherwise enhance the user experience. id="p-31" id="p-31"

[0031] FIG. 2 illustrates a block diagram of the circuitry for accomplishing the two levels ofconnectivity described above. As shown in FIG. 2, a device 200 (which could be any of the first,second and third devices 110, 120 and 130, or the charger 140, of FIG. 1) is operably coupled tothe connected battery 150 via power provision circuitry including power coupling 210 andground coupling 212. In some cases, the power coupling 210 and the ground coupling 212 maybe embodied as electrical contacts that mate with each other when the connected battery 150 isinserted fully into a battery receptacle of the device 200. The power provision circuitry mayenable the cells of the connected battery 150 to be coupled to the electric motor of the device 200(e.g., when the device 200 is one of the first, second and third devices 110, 120 and 130) or to anoutput of the charger 140 (e. g., when the device 200 is embodied as the charger 140). id="p-32" id="p-32"

[0032] The device 200 may include an electronic control unit (ECU) 220, which may includeprocessing circuitry for controlling various components of the device 200. The ECU 220 maycontrol a working assembly (e. g., a blade and/or electric motor) of the device 200 and may alsogather data (e. g., operational parameters) from various sensors of the device, or generate or storesuch data locally as it is available based on operation of the working assembly or other components of the device 200.

P3159SE00 id="p-33" id="p-33"

[0033] The connected battery 150 may include a battery manager 230 configured to managethe power transfer communication level of connectivity between the device 200 and theconnected battery 150, and a communications manager 240 configured to manage datacommunication level of connectivity between the device 200 and the connected battery 150. Aspart of managing power transfer, the battery manager 230 may institute safe guards based onmonitoring data over a battery data line 232. The battery data line 232 may be a serial dataconnection involving various input/ output ports on the ECU 220 and on the battery manager 230.The battery data line 232 may be supplemented by a shutdown line 236 that may operate toprotect the device 200 and/ or the battery cells of the connected battery 150 by interrupting powertransfer if certain shutdown conditions are detected by the battery manager 230. Meanwhile, aseparate service line 242 may be provided for transfer of operational parameters regarding device200 operation that can be passed along to the network 170 of FIG. 1 via the access point 160 bythe communications manager 240. The service line 242 may be a serial data line connectingvarious input/ output ports of the ECU 220 to corresponding input/output ports of thecommunications manager 240. id="p-34" id="p-34"

[0034] Of note, although the communications manager 240 and the battery manager 230 areshown as separate entities in FIG. 2, it should be appreciated that they may be embodied on thesame or different physical components in various example embodiments. Thus, for example, insome cases, the battery manager 230 may be embodied on a single chip having its own processorand/or processing circuitry and the communications manager 240 may be embodied by aseparate chip having separate processor and/ or processing circuitry resources. However, in stillanother example, the connected battery 150 may have a single processing chip that may beconfigured to act as both the battery manager 230 and the communications manager 240.Additionally, the battery data line 232 and the service data line 242 could also be combined intoa single communication interface or bus in some embodiments. Thus, the battery data andservice data (e. g., all operational parameters) could pass over a single communication interfaceor bus in some cases. id="p-35" id="p-35"

[0035] FIG. 3 illustrates a block diagram of the processing circuitry of the connected battery150 in accordance with an example embodiment. The connected battery 150 may includeprocessing circuitry 310 of an example embodiment as described herein. In this regard, for example, the connected battery 150 may utilize the processing circuitry 310 to provide electronic P3159SE00 control inputs to one or more functional units of the connected battery 150 and to process datareceived at or generated by the one or more functional units regarding various indications ofdevice activity (e.g., operational parameters and/or location information) relating to acorresponding one of the devices 200. ln some cases, the processing circuitry 310 may beconfigured to perform data processing, control function execution and/ or other processing andmanagement services according to an example embodiment. HoWever, in other examples, theprocessing circuitry 310 may be configured to manage extraction, storage and/or communicationof data received at the processing circuitry 310. id="p-36" id="p-36"

[0036] ln some embodiments, the processing circuitry 310 may be embodied as a chip orchip set. ln other Words, the processing circuitry 310 may comprise one or more physicalpackages (e.g., chips) including materials, components and/or Wires on a structural assembly (e. g., a baseboard). The structural assembly may provide physical strength, conservation of size,and/or limitation of electrical interaction for component circuitry included thereon. Theprocessing circuitry 310 may therefore, in some cases, be configured to implement anembodiment of the present invention on a single chip or as a single "system on a chip." As such,in some cases, a chip or chipset may constitute means for performing one or more operations forproviding the functionalities described herein. id="p-37" id="p-37"

[0037] ln an example embodiment, the processing circuitry 310 may include one or moreinstances of a processor 312 and memory 314 that may be in communication With or otherWisecontrol other components or modules that interface With the processing circuitry 310. As such,the processing circuitry 310 may be embodied as a circuit chip (e.g., an integrated circuit chip)configured (e. g., With hardware, softWare or a combination of hardware and softWare) to performoperations described herein. HoWever, in some embodiments, the processing circuitry 310 maybe embodied as a portion of an on-board computer housed in a battery pack With the batterymanager 230 and/or the communications manager 240 to control operation of the connectedbattery 150 relative to its interaction With other devices. id="p-38" id="p-38"

[0038] Although not required, some embodiments of the connected battery 150 may employa user interface 330. The user interface 330 may be in communication With the processingcircuitry 310 to receive an indication of a user input at the user interface 330 and/or to provide anaudible, visual, tactile or other output to the user. As such, the user interface 330 may include, for example, a display, one or more sWitches, lights, buttons or keys (e.g., function buttons), P3159SE00 and/or other input/ output mechanisms. In an example embodiment, the user interface 330 mayinclude one or a plurality of colored lights or a simple display to indicate charge status or otherrelatively basic information. However, more complex interface mechanisms could be providedin some cases. id="p-39" id="p-39"

[0039] As shown in FIG. 3, the connected battery 150 may further include the batterymanager 230 and the communications manager 240. The battery manager 230 and thecommunications manager 240 may be embodied as or otherwise controlled by the processingcircuitry 310. However, in some cases, the processing circuitry 310 may be associated with onlya specific one of the battery manager 230 or the communications manager 240, and a separateinstance of processing circuitry may be associated with the other. Yet in some cases, theprocessing circuitry 310 could be shared between the battery manager 230 and thecommunications manager 240 and/ or the processing circuitry 310 could be configured toinstantiate both such entities. Thus, although FIG. 3 illustrates such an instance of sharing theprocessing circuitry 310 between the battery manager 230 and the communications manager 240,it should be appreciated that FIG. 3 is not lirr1iting in that regard. id="p-40" id="p-40"

[0040] Each of the battery manager 230 and the communications manager 240 may employor utilize components or circuitry that acts as a device interface 320. The device interface 320may include one or more interface mechanisms for enabling communication with other devices(e. g., device 200, the access point 160, and/or internal components). In some cases, the deviceinterface 320 may be any means such as a device or circuitry embodied in either hardware, or acombination of hardware and software that is configured to receive and/ or transmit data from/tocomponents in communication with the processing circuitry 310 via internal communicationsystems of the connected battery 150. With respect to the communications manager 240, thedevice interface 320 may further include wireless communication equipment (e.g., a one way ortwo way radio) for at least communicating information from the connected battery 150 to theaccess point 160. As such, the device interface 320 of the communications manager 240 mayinclude an antenna and radio equipment for conducting Bluetooth, WiFi, or other short rangecommunication with the access point 160, or for employing other longer range wirelesscommunication protocols for communicating with the access point 160 in instances where the access point 160 is directly associated with provision of access to a wide area network. 11 P3159SE00 id="p-41" id="p-41"

[0041] The processor 312 may be embodied in a number of different ways. For example, theprocessor 312 may be embodied as various processing means such as one or more of amicroprocessor or other processing element, a coprocessor, a controller or various othercomputing or processing devices including integrated circuits such as, for example, an ASIC(application specific integrated circuit), an FPGA (field programmable gate array), or the like. lnan example embodiment, the processor 312 may be configured to execute instructions stored inthe memory 314 or otherwise accessible to the processor 312. As such, whether configured byhardware or by a combination of hardware and software, the processor 312 may represent anentity (e. g., physically embodied in circuitry -in the form of processing circuitry 310) capable ofperforming operations according to embodiments of the present invention while configuredaccordingly. Thus, for example, when the processor 312 is embodied as an ASIC, FPGA or thelike, the processor 312 may be specifically configured hardware for conducting the operationsdescribed herein. Alternatively, as another example, when the processor 312 is embodied as anexecutor of software instructions, the instructions may specifically configure the processor 312to perform the operations described herein. id="p-42" id="p-42"

[0042] ln an example embodiment, the processor 312 (or the processing circuitry 310) maybe embodied as, include or otherwise control the operation of the connected battery 150 based oninputs received by the processing circuitry 310. As such, in some embodiments, the processor312 (or the processing circuitry 310) may be said to cause each of the operations described inconnection with the connected battery 150 in relation to operation the connected battery 150relative to undertaking the corresponding functionalities associated therewith responsive toexecution of instructions or algorithms configuring the processor 312 (or processing circuitry310) accordingly. id="p-43" id="p-43"

[0043] ln an exemplary embodiment, the memory 314 may include one or more non-transitory memory devices such as, for example, volatile and/ or non-volatile memory that maybe either fixed or removable. The memory 314 may be configured to store information, data,applications, instructions or the like for enabling the processing circuitry 310 to carry out variousfunctions in accordance with exemplary embodiments of the present invention. For example, thememory 314 could be configured to buffer input data for processing by the processor 312.Additionally or alternatively, the memory 314 could be configured to store instructions for execution by the processor 312. As yet another alternative or additional capability, the memory 12 P3159SE00 314 may include one or more databases that may store a variety of data sets responsive to inputfrom the device 200, or any other functional units or devices from which the connected battery150 has previously extracted data while powering such devices. Among the contents of thememory 314, applications may be stored for execution by the processor 312 in order to carry outthe functionality associated with each respective application. ln some cases, the applicationsmay include instructions for recognition of patterns of activity and for initiation of one or moreresponses to the recognition of any particular pattern of activity as described herein.Additionally or alternatively, the applications may prescribe particular reporting paradigms orprotocols for reporting of information from the connected battery 150 to a network device via thecommunications manager 240. id="p-44" id="p-44"

[0044] ln some embodiments, the battery manager 230 may be any means such as a device orcircuitry embodied in either hardware, or a combination of hardware and software that isconfigured to receive and/or transmit battery data (e. g., operational parameters) frorn/to thedevice 200. The battery manager 230 may also control and/ or provide electrical connectionsand/or interfaces between the cells 350 of the connected battery 150 and the device 200 tomonitor power provision parameters and enable the battery manager 230 to implement safety orprotective functions as appropriate. The protective functions may be implemented based uponexamination of the battery data and comparison of such data to various thresholds or safetylirr1its. Thus, the battery data may, in some cases, be acted upon locally by the battery manager230. However, alternatively or additionally, the battery data may be provided to thecommunication manager 240 for transmission to the network 170 (or entities accessible throughthe network 170). ln these and other instances, the battery data may be stored locally prior tosuch transmission or may be transn1itted in real-time (or substantially real-time). id="p-45" id="p-45"

[0045] ln an example embodiment, the battery manager 230 may receive or generateidentification information that correlates the battery data to a specific device (e.g., a specific oneof the first device 110, the second device 120, the third device 130, or the charger 140), or tousers of such devices. Thus, all data may be transn1itted and/ or stored in association with theidentification information so that such data can be associated with its respective device, devicetype, or user for analytical purposes. The identification information may include a specificdevice identifier, a type identifier indicating the type or model of the device 200, and/ or a specific user identifier. The battery data may include, for example, information indicative of 13 P3159SE00 current draw at discrete intervals, continuously, or at discrete times. Temperature data,maximum current, state of charge, and other data related to the state of the cells 350 or otheraspects of the devices 200 or connected battery 150 relative to current draw or batteryperformance may also be included in the battery data. id="p-46" id="p-46"

[0046] ln an example embodiment, the communications manager 240 may be any meanssuch as a device or circuitry embodied in either hardware, or a combination of hardware andsoftware that is configured to receive and/or transmit service data fron1/to the device 200. Thecommunications manager 240 may also control the storage and/or further communication (e. g.,relaying) of service data (e. g., operational parameters) extracted from the device 200. Thus, forexample, the service data may be extracted from the device 200 to which the connected battery150 is operably coupled during such coupling. The extracted operational parameters of theservice data may then be immediately transmitted (e.g., relayed) to the access point 160 forfurther provision to the network 170 or devices connected to the network 170 such as the UE180, or the extracted operational parameters may be temporarily stored prior to later transmissionto the access point 160. The service data may include information specific to deviceperformance, at least some of which is not detern1ined based on measuring battery parameters.Thus, for example, the service data may include engine RPM, working assembly RPM, torque,run time or run hours, position, orientation, vibration data, temperature data, speed data, mode ofoperation, lubricating oil pressure or level, instances of protective actions, and/or the like. As aspecific example, where the device 200 is a chainsaw (e. g., the device 130), the connectedbattery 150 may be configured to receive (e. g., via the communications manager 240) servicedata specific to the chainsaw, such as, for example, the temperature of the chainsaw engine, theRPM of the chainsaw engine, vibration of the chainsaw (e.g., detected/felt in the handle and/ortrigger of the chainsaw), the speed of the chain, the amount of bar and chain oil, the idle time ofthe chainsaw, the run time of the chainsaw, the GPS position of the chainsaw, the orientation ofthe chainsaw bar, and/or the like. id="p-47" id="p-47"

[0047] ln some example embodiments, the service data may be used for local analysis andprotective action initiation at the device 200. For example, RPM lin1its may be enforced basedon analysis of the RPM data provided via the service data. However, in some embodiments, the data may instead be analyzed at the UE 180 after provision thereto. Corrective or protective 14 P3159SE00 instructions may then, in some cases, be provided to the user via a display or other user interfaceat the UE 180. id="p-48" id="p-48"

[0048] Similar to the battery data, the service data may also be transrnitted and/ or stored inassociation With the identification information so that all operational parameters (e. g., includingboth service data and battery data) are associated With a respective device, device type, or user.The identification information may therefore include a specific device identifier, a type identifierindicating the type or model of the device 200, and/or a specific user identifier. ln someembodiments, operational parameters may also be transmitted and/ or stored in association Withtemporal information that may indicate the time (or time period) that the operational parametersWere obtained from the device 200 and/ or the time that the operational parameters Weretransmitted from the connected battery 150. id="p-49" id="p-49"

[0049] The operational parameters may be extracted from the device 200 by the connectedbattery 150 at regular intervals, continuously, and/or as a response to specific predefined stimuli.After eXtraction, the communications manager 240 may determine Whether to store the datatemporarily or relay the operational parameters to the access point 160 in real-time (orsubstantially in real-time). The relaying may therefore be at the same schedule (e.g., at regularintervals, continuously, and/or in response to the specific predefined stimuli) as the dataeXtraction occurs or may occur at a different schedule. Thus, for example, if the operationalparameters are at least temporarily stored, the communications manager 240 may define aseparate interval or period at Which to communicate the operational parameters to the accesspoint 160. Alternatively or additionally, the communications manager 240 may define differentstimuli to trigger transmission of the operational parameters to the access point 160. id="p-50" id="p-50"

[0050] As an example, in some cases, insertion or removal of the connected battery 150 intothe device 200 may trigger immediate transmission of operational parameters stored in thememory 314 of the connected battery 150 to the access point 160. Thus, the beginning and/orending of a poWer provision cycle for the device 200 may trigger the communications manager240 to transmit operational parameters to the access point 160. The fact that the transmissionoccurs from the connected battery 150 means that even after the device 200 is left unpoWered(and therefore incapable of reporting information about the just completed session) theoperational parameters associated With the just completed session can still be reported by the connected battery 150 (Which remains powered by the cells 350).

P3159SE00 id="p-51" id="p-51"

[0051] HoWever, if the cells 350 are depleted fully, then the connected battery 150 may notactually be able to transmit the data until power levels are recharged sufficiently. Thus, in somecases, insertion of the connected battery 150 may trigger transmission of the data from animmediately previous session With What is presumably a recharged group of cells 350.

Moreover, in some cases, the connected battery 150 may be configured to check to see ifoperational parameters are available for transmission as soon as recharging of the cells 350 isaccomplished to at least a predetermined charge level. Thus, for example, if removal generallytriggers transmission, a transmission instruction may be provided at the communicationsmanager 240. HoWever, the communications manager 240 may determine that the power levelof the cells 350 is too loW to complete transmission of the operational parameters. Thus, thecommunications manager 240 may provide the transmission instruction, but monitor batterycharge status to determine When the cells 350 are sufficiently recharged to support transmissionof the operational parameters to carry out the transmission instruction. After battery chargestatus reaches the predetern1ined charge level, the communications manager 240 may execute thetransmission instruction and report the operational parameters to the access point 160. id="p-52" id="p-52"

[0052] As an alternative, an identity based communication trigger may be employed. Forexample, insertion of the connected battery 150 into the device 200 may trigger an initial identityquery Whereby the connected battery 150 obtains identification information from the device 200.Once the identification information is received, the connected battery 150 may start a data log foroperational parameters associated With the identity provided in the identification information.The connected battery 150 may also determine Whether the identification information is differentfrom the prior identification detern1ined from the previous connected battery 150 insertion into adevice. ln some cases, the transmission instruction may be generated When the comparison ofidentification information indicates a change in identity. HoWever, as an alternative, thetransmission instruction could be generated When the comparison of identification informationindicates the same identity. id="p-53" id="p-53"

[0053] ln some cases, the UE 180 may receive the operational parameters and execute one ormore applications on the operational parameters. As such, the UE 180 may include processingcircuitry that may be similar in capability and perhaps also structure to the processing circuitrydescribed above. The UE 180 may execute applications for storage and/or analysis of the service and/or battery data. Thus, for example, the UE 180 may be configured to analyze RPM data, 16 P3159SE00 engine run hours, and/ or Various other aspects of the operational parameters to determine Whenservicing of the device should be performed or When there are technical issues or problems thatthe operator or a ﬂeet manager should be informed of have occurred. The UE 180 may beconfigured to provide an alert to the user or ﬂeet manager and the alert may be descriptive of thespecific issue that has been identified. id="p-54" id="p-54"

[0054] The applications executable at the UE 180 may include an application for revieWing,monitoring, and/ or analyzing individual device or device type performance. ln some cases, theapplications at the UE 180 may include an application for cloud management of tools. Thus, forexample, adaptive tool settings, instructions and/or the like may be used to specifically configuretools under specifically identified circumstances or scenarios to maximize control over, forexample, a ﬂeet of tools. Guided tool operation may therefore be controlled via the connectedbattery 150. Applications may also define triggers, codes and/or the like for locking orunlocking tools, and for the extraction of operational data. id="p-55" id="p-55"

[0055] ln some example embodiments, either the UE 180 or the connected battery 150 maystore configuration information specific to the device 200. Thus, for example, the operator mayconfigure the device 200 in a particular Way that is desirable by the specific user of the device200. The configuration information may be input at the device 200 and transmitted for storage atthe connected battery 150 and/ or at the UE 180. Alternatively, the configuration informationmay be input at the UE 180 and transmitted to the connected battery 150 for storage andcommunication to the device 200 When the device 200 is operably coupled to the connectedbattery 150. The configuration information may provide torque or RPM limits or settings, andsuch information may be stored to guide operation of the device 200. id="p-56" id="p-56"

[0056] Of note, although FIG. 1 shows only one UE 180 it should be appreciated that severalcould be employed in some embodiments. For example, one UE could be a central node (e.g., aserver or computer associated With a particular organization, household, ﬂeet of devices, devicemanufacturer, and/ or the like). Other UEs could be distributed nodes associated With individualusers of the devices, or smaller organizations, individual households, and/or the like. The centralnode may perform analysis of the operational parameters, and generate alerts or processedinformation that is specific to the devices associated With respective ones on the distributednodes to each respective UE of the corresponding distributed nodes. Thus, identification information With Which the operational parameters are associated could be the discrin1inating 17 P3159SE00 factor to allow the central node to store data. The stored data, on a ﬂeet wide basis or for alldevices registered to the manufacturer, may then be analyzed for trends or other specific issues,and individual users or organizations can receive information specific to their devices. However,the information specific to their devices may be benchmarked against the performance of otherdevices not associated with the individual users or organizations. Thus, the individual users ororganizations can determine how hard they run their equipment, how frequently they servicetheir equipment, and/or how well their equipment performs relative to all other equipmentmonitored by the central node. id="p-57" id="p-57"

[0057] As can be appreciated from the example embodiments above, some embodimentsmay provide a connected battery 150 that can extract operational parameters (e. g., battery dataand/or service data) from devices to which the connected battery 150 is operably connectable(e.g., the device 200). That extracted information may be transn1itted by the connected battery150 to the access point 160 and to other devices (e. g., the UE 180) that may be connected to thenetwork 170. Various different communication paradigms and analyses may then be performedon the operational parameters. However, the connected battery 150 becomes the gatewaybetween the device 200 and the network 170 and any devices on the network 170. Because theconnected battery 150 is or includes a power source itself, the ability to report information aboutdevice operation is more reliably supported than if the device 200 itself was expected to report itsoperational parameters to some central node. id="p-58" id="p-58"

[0058] FIGS. 4-8 illustrate various example control ﬂow diagrams illustrating a series ofcommunication operations associated with operation of the connected battery 150 of an exampleembodiment. As shown in FIG. 4, the connected battery 150 may initially detect insertion intothe device 200 at operation 400. Thereafter, operational parameters may be extracted from thedevice 200 by the connected battery 150 at operation 402. The battery data may indicate ashutdown condition at operation 404 (e.g., current draw above a predetermined threshold). Theconnected battery 150 may initiate a shutdown to remove power provision to the device 200 atoperation 406. At operation 408, the connected battery 150 may report the operationalparameters and/ or the occurrence of the shutdown condition to the access point 160 at operation408. id="p-59" id="p-59"

[0059] ln the example of FIG. 5, the connected battery 150 may initially detect insertion into the device 200 at operation 400. Thereafter, operational parameters may be extracted from the 18 P3159SE00 device 200 by the connected battery 150 at operation 402. Operational parameters may be storedin association With identification information at operation 410. At operation 412, a triggeringevent may be detected to cause the connected battery 150 to generate or execute a transmissioninstruction. At operation 414, the operational parameters and/or an indication of the triggeringevent may be transrnitted to the access point 160. id="p-60" id="p-60"

[0060] In the example of FIG. 6, the connected battery 150 may initially detect insertion intothe device 200 at operation 400. Thereafter, operational parameters may be extracted from thedevice 200 by the connected battery 150 at operation 402. Operational parameters may berelayed in association With identification information at operation 420 so that the operationalparameters are provided in real-time (or substantially in real-time) to the access point 160.Although not required, the access point 160 may provide the operational parameters to the UE180 (e. g., via the netWork 170) at operation 422. The UE 180 may perform analysis at operation424, and may provide a notification to the user at operation 426 and/or provide information orinstruction back to the connected battery 150 (via the access point 160) at operation 428. id="p-61" id="p-61"

[0061] In the example of FIG. 7, the connected battery 150 may initially detect insertion intothe device 200 at operation 400. Thereafter, the connected battery 150 may determineidentification information associated With the device 200 at operation 430. The connectedbattery 150 then may determine configuration information for the device 200 at operation 432.The configuration information may then be sent to the device 200 to configure the device 200accordingly at operation 434. Operational parameters may then be extracted from the device 200by the connected battery 150 during device operation in accordance With the configurationinformation at operation 436. Operational parameters may be relayed in association Withidentification information at operation 438 and/ or stored at operation 440, so that the operationalparameters are provided in real-time (or substantially in real-time) to the access point 160.Although not required, the access point 160 may provide the operational parameters to the UE180 (e. g., via the netWork 170) at operation 422. The UE 180 may perform analysis at operation424, and may provide a notification to the user at operation 426 and/or provide information orinstruction back to the connected battery 150 (via the access point 160) at operation 428. id="p-62" id="p-62"

[0062] In the example of FIG. 8, the user may insert configuration information into the UE180 to configure the device 200 at operation 450. The UE 180 may provide the configuration information to the access point 160 at operation 452, and the access point 160 may provide the 19 P3159SE00 configuration information to the connected battery 150 at operation 454. The configurationinformation may then be stored at the connected battery 150 at operation 456. Thereafter,insertion of the connected battery 150 into the device 200 for Which the configurationinformation is intended may be detected at operation 458. The connected battery 150 may thenprovide the configuration information to the device 200 to configure the device 200 accordinglyat operation 460. Thereafter, operational parameters may be extracted from the device 200 bythe connected battery 150 during device operation in accordance With the configurationinformation at operation 462. Operational parameters may be relayed in association Withidentification information at operation 464 and/or stored at operation 466. id="p-63" id="p-63"

[0063] Accordingly, in one example embodiment, a battery pack may include one or morerechargeable battery cells and processing circuitry. The processing circuitry may be configuredto control extraction of operational parameters from a device to Which the battery pack isoperably coupled and Wireless communication of the operational parameters from the batterypack to an access point. The operational parameters may include at least one parameter that isnot determined based on measuring battery parameters. The device is one of a plurality ofdifferent devices With Which the battery pack is configured to be operably coupled. id="p-64" id="p-64"

[0064] ln some cases, modifications or amplifications may further be employed as optionalalterations or augmentations to the description above. These alterations or augmentations maybe performed exclusive of one another or in any combination With each other. ln some cases,such modifications or amplifications may include (1), the operational parameters may includebattery data and service data. ln an example embodiment (2), the battery data may includecurrent data, state of charge, or temperature data, and the processing circuitry may be configuredto initiate a protective function based upon comparing the battery data to a predetern1inedthreshold. ln some cases (3), the service data may include RPM data, torque, run time, deviceposition, device orientation, temperature data, speed data, mode of operation, or an instance of aprotective action. ln some embodiments (4), the Wireless communication of the operationalparameters may be performed substantially in real-time relative to extraction of the operationalparameters. ln an example embodiment (5), the operational parameters may be stored at amemory of the processing circuitry prior to Wireless communication of the operationalparameters. ln some cases (6), the operational parameters may be stored in association With identification information indicative of a device identity, device type or user identity. ln some P3159SE00 embodiments (7), a transmission instruction may be generated to direct the Wirelesscommunication based at least in part on the identification information. ln an exampleembodiment (8), the operational parameters may be stored in association With temporalinformation indicative of a time or time period at Which the operational parameters Wereextracted from the device. ln some cases (9), the operational parameters may be stored at amemory of the processing circuitry, and the Wireless communication may be executed inresponse to a predetermined level of charge of the battery cells being achieved. ln someembodiments (10), the processing circuitry may be configured to receive configurationinformation for configuring the device from a user via the access point. ln some cases (11), theconfiguration information may be stored at the processing circuitry and loaded onto the device inresponse to detection of installation of the battery pack in the device. ln some embodiments(12), the access point may provide access to a network, and user equipment may be enabled tointeract With the processing circuitry via the network and the access point. ln some cases (13),the access point may provide a user With access to interact With the processing circuitry toreceive alerts associated With the device or to provide an instruction for operation of the device.[0065] ln an example embodiment, some, any or all of modifications/amplifications ( 1) to(13) may be employed in any combination With each other. id="p-66" id="p-66"

[0066] Many modifications and other embodiments of the inventions set forth herein Willcome to mind to one skilled in the art to Which these inventions pertain having the benefit of theteachings presented in the foregoing descriptions and the associated draWings. Therefore, it is tobe understood that the inventions are not to be limited to the specific embodiments disclosed andthat modifications and other embodiments are intended to be included Within the scope of theappended claims. Moreover, although the foregoing descriptions and the associated draWingsdescribe exemplary embodiments in the context of certain exemplary combinations of elementsand/or functions, it should be appreciated that different combinations of elements and/orfunctions may be provided by alternative embodiments Without departing from the scope of theappended claims. ln this regard, for example, different combinations of elements and/orfunctions than those explicitly described above are also contemplated as may be set forth in someof the appended claims. ln cases Where advantages, benefits or solutions to problems aredescribed herein, it should be appreciated that such advantages, benefits and/or solutions may be applicable to some example embodiments, but not necessarily all example embodiments. Thus, 21 P3159SE00 any advantages, benefits or solutions described herein should not be thought of as being critical,required or essential to all embodiments or to that Which is claimed herein. Although specificterms are employed herein, they are used in a generic and descriptive sense only and not for purposes of 1irr1itation. 22

Claims

P3l59SE00 THAT WHICH IS CLAIMED:

1. l. A battery pack comprising:one or more rechargeable battery cells; andprocessing circuitry configured to control: eXtraction of operational parameters from a device to Which the battery pack isoperably coupled, the operational parameters comprising at least one parameter that is notdetermined based on measuring battery parameters; and Wireless communication of the operational parameters from the battery pack to anaccess point,Wherein the device is one of a plurality of different devices With Which the battery pack is configured to be operably coupled.

2. The battery pack of claim l, Wherein the operational parameters comprise battery data and service data.

3. The battery pack of claim 2, Wherein the battery data comprises current data, stateof charge, or temperature data, and Wherein the processing circuitry is configured to initiate a protective function based upon comparing the battery data to a predetermined threshold.

4. The battery pack of claim 2, Wherein the service data comprises RPM data,torque, run time, device position, device orientation, temperature data, speed data, mode of operation, or an instance of a protective action.

5. The battery pack of claim l, Wherein the Wireless communication of theoperational parameters is performed substantially in real-time relative to eXtraction of the operational parameters.

6. The battery pack of claim l, Wherein the operational parameters are stored at amemory of the processing circuitry prior to Wireless communication of the operational parameters. 23 P3159SE00

7. The battery pack of claim 6, Wherein the operational parameters are stored inassociation With identification information indicative of a device identity, device type or user identity.

8. The battery pack of claim 7, Wherein a transrr1ission instruction is generated to direct the Wireless communication based at least in part on the identification information.

9. The battery pack of claim 6, Wherein the operational parameters are stored inassociation With temporal information indicative of a time or time period at Which the operational parameters Were eXtracted from the device.

10. The battery pack of claim 1, Wherein the operational parameters are stored at amemory of the processing circuitry, and Wherein the Wireless communication is eXecuted in response to a predetermined level of charge of the battery cells being achieved.

11. The battery pack of claim 1, Wherein the processing circuitry is configured to receive configuration information for configuring the device from a user via the access point.

12. The battery pack of claim 11, Wherein the configuration information is stored atthe processing circuitry and loaded onto the device in response to detection of installation of the battery pack in the device.

13. The battery pack of claim 1, Wherein the access point provides access to anetWork, and Wherein user equipment is enabled to interact With the processing circuitry via the network and the access point.14. The battery pack of claim 1, Wherein the access point provides a user With access to interact With the processing circuitry to receive alerts associated With the device or to provide an instruction for operation of the device. 24

14. P3159SE00

15. A communications manager for a battery pack comprising one or morerechargeable battery cells, the communications manager comprising: processing circuitry configured to control: eXtraction of operational parameters from a device to Which the battery pack isoperably coupled, the operational parameters comprising at least one parameter that is notdetermined based on measuring battery parameters; and Wireless communication of the operational parameters from the battery pack to anaccess point,Wherein the device is one of a plurality of different devices With Which the battery pack is configured to be operably coupled.

16. The communications manager of claim 15, Wherein the operational parameters comprise battery data and service data.

17. The communications manager of claim 16, Wherein the battery data comprisescurrent data, state of charge, or temperature data, and Wherein the processing circuitry isconfigured to initiate a protective function based upon comparing the battery data to a predetern1ined threshold.

18. The communications manager of claim 16, Wherein the service data comprisesRPM data, torque, run time, device position, device orientation, temperature data, speed data, mode of operation, or an instance of a protective action.

19. The communications manager of claim 15, Wherein the Wireless communicationof the operational parameters is performed substantially in real-time relative to eXtraction of the operational parameters.20. The communications manager of claim 15, Wherein the operational parameters are stored at a memory of the processing circuitry prior to Wireless communication of the operational parameters.

20. P3159SE00

21. The communications manager of claim 20, Wherein the operational parameters arestored in association With identification information indicative of a device identity, device type or user identity.

22. The communications manager of claim 21, Wherein a transmission instruction isgenerated to direct the Wireless communication based at least in part on the identification information.

23. The communications manager of claim 20, Wherein the operational parameters arestored in association With temporal information indicative of a time or time period at Which the operational parameters Were eXtracted from the device.

24. The communications manager of claim 15, Wherein the operational parameters arestored at a memory of the processing circuitry, and Wherein the Wireless communication is eXecuted in response to a predetermined level of charge of the battery cells being achieved.

25. The communications manager of claim 15, Wherein the processing circuitry isconfigured to receive configuration information for configuring the device from a user via the access point.

26. The communications manager of claim 25, Wherein the configuration informationis stored at the processing circuitry and loaded onto the device in response to detection of installation of the battery pack in the device.

27. A system comprising: a plurality of different devices, each of the devices comprising outdoor power equipmentthat is battery poWered; an access point configured for Wireless communication; and a battery pack comprising one or more rechargeable battery cells and processing circuitry configured to control: 26 P3l59SE00 eXtraction of operational parameters from a selected one of the devices to Whichthe battery pack is operably coupled, the operational parameters comprising at least oneparameter that is not detern1ined based on measuring battery parameters; and Wireless communication of the operational parameters from the battery pack to the access point. 27