Devices and methods for data transfer during charging of a portable device

[0001] Disclosed are methods and devices for data transfer between a portable device and another device, and more particularly methods and devices for data transfer between a portable device and another device during charging of the portable device.

[0002] Mobile communication devices, such as cellular telephones and PDAs, have become an important part of everyday life. Portable devices are now being used not only for communication, but also to store many forms of data generated or downloaded during their use, including personal information such as calendar appointments, emails, pictures, video clips, and sound clips.

[0003] Often a user will connect his or her portable device to a larger device having more memory or computing capability, in order to transfer data between the two devices, whether for data backup purposes or for example, to update a calendar, phonebook, text messages sent and received, music and other media downloaded, as well as received and placed call records. For example, the larger device could be in the form of a home media set-top box, a personal computer, a wide area network server, or an internet server. The mobile device may be connected with the larger device via for example a USB cable, a WiFi home network or hotspot, or a Bluetooth wireless connection.

[0004] Data transfer between the mobile communication device and another device typically requires that the mobile device be powered, for example from its battery or from a wall outlet. With the large amounts of data that can be stored on today's portable devices, the time for a data transfer can be longer than the time available on the device's battery. Alternatively, the device can be connected for data transfer while it is being charged, but one or more manual steps must be taken by a user after the portable device is connected to the other device, in order to initiate the transfer of data between the two devices during charging.

[0005] The manual steps a user must take to initiate data transfer between a mobile device and another device are cumbersome and time consuming. Initiating data transfer becomes even more problematic when a mobile device contains multiple mechanisms for connecting with another device, such as both a wired connection like a USB connection, and one or more wireless connectivity mechanisms like WiFi and Bluetooth. Each type of wireless connectivity must be set up and configured. Thus a more convenient solution for portable devices to the problem of data transfer may be desirable.

[0009] It would be beneficial to have methods and devices by which a user of a mobile communication device can easily transfer data between the mobile communication device and another device without cumbersome and time consuming manual setup procedures. It would further be beneficial if a data transfer could take place during charging so that the battery life of the device is not an issue during data transfer. It would also be beneficial if a data transfer is an automated process upon charging the device. It would in addition be beneficial if a user could better ensure safety of data of a mobile communication device by backing up the data and/or synchronizing data during regular charging of the mobile communication device, for example, during nightly charging.

[0010] Described below are methods and devices to automatically effect data transfer between a mobile communication device and another device, upon detection by the mobile communication device of charging current received for example from a charger. Data transfer can include for example, backing up calendar data, phonebook data, music and other media, placed and received messages and calls, as well as internet sites viewed. Data transfer can also include synchronizing calendars, contacts and/or email. When a charger or a charging current is detected, the mobile device detects what connectivity links, such as for example, USB, Bluetooth, and/or WiFi, are available between the mobile device and another device. An automated process selects an appropriate connectivity link and then initiates one or two-way transfer of data over the automatically selected connectivity link according to the data transfer rules set by the user or by a default mechanism or algorithm. A user may set up data transfer rules that govern data transfer, that is, the types of data transferred, between the mobile communication device and another device.

[0011] Rules that govern what data gets transferred could include transferring of the newest data, the most accessed data, the highest rated data, or data that is marked as favorite. The data transfer rules could also specify a specific device on a network with which to transfer the data, and could in addition specify one or more locations on that device (for example, one or more folders). Additionally, the data rules can also specify the most appropriate transfer mechanism for a particular kind of data, based on necessary bandwidth, quality of the connection, and duration of the transfer. It is understood that the data may include any type of data, including music, videos, games, contacts, calendars, call logs, etc. It is further understood that some types of data may be synchronized rather than transferred, meaning data is sent both to and from the device. In this manner backup and/or update of data, synchronization of data, or both update and synchronization of data may take place automatically upon connection of a user's mobile communication device to a source of charging current.

[0012] The instant disclosure is provided to explain in an enabling fashion the best modes of making and using various embodiments in accordance with the present invention. The disclosure is further offered to enhance an understanding and appreciation for the invention principles and advantages thereof, rather than to limit in any manner the invention. While the preferred embodiments of the invention are illustrated and described here, it is clear that the invention is not so limited. Numerous modifications, changes, variations, substitutions, and equivalents will occur to those skilled in the art having the benefit of this disclosure without departing from the spirit and scope of the present invention as defined by the following claims. It is understood that the use of relational terms, if any, such as first and second, up and down, and the like are used solely to distinguish one from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions.

[0013] At least some inventive functionality and inventive principles may be implemented with or in software programs or instructions and integrated circuits (ICs) such as application specific ICs. In the interest of brevity and minimization of any risk of obscuring the principles and concepts according to the present invention, discussion of such software and ICs, if any, is limited to the essentials with respect to the principles and concepts within the preferred embodiments.

[0014] FIG. 1 shows an embodiment of a mobile communication device 102 that may automatically transfer data upon detection of a charging current such as may be received from, for example, a charger 104. The mobile communication device 102 may automatically detect what connectivity links may be available for the purpose of transferring data between the mobile communication device 102 and, for example a data storage device 106 which may be a stationary or a portable device. In this way, the data transfer may be substantially automatically initiated without a cumbersome and time consuming setup process by the user. In this disclosure the mobile communication device 102 may be referred to as a first device and the data storage device 106 may be referred to as a second device. It is understood that the data storage device 106 may be one of a plurality of data storage devices. A second data storage device 107 of the plurality of data storage devices is shown.

[0015] The connectivity links that as discussed below are determined by a connectivity module or application may include, for example, Universal Serial Bus (USB), Bluetooth, WiFi, Ultra Wideband (UWB), and/or other types of connectivity for data transfer. Upon successful setup of a connectivity link for data transfer between the mobile communication device 102 and the data storage device 106 and/or 107, the data transfer may commence. In this manner a user of a mobile communication device 102 may transfer data between the two devices 102 and 106, for example, for purposes of data backup or data update, with a minimal number of manual steps. It is understood that data transfer may take place between the devices 102 and 107 as well.

[0016] The mobile communication device 102 includes a controller 108 configured to execute instructions that may be, for example, application instructions. The mobile communication device 102 may in addition include a transceiver 110 coupled to the controller 108. The transceiver 110 may provide a wireless connectivity link with another device. The transceiver 110 may support, for example, Bluetooth, Worldwide Interoperability for Microwave Access (WiMAX), WiFi, UWB, or another wireless technology that may be used for a data transfer.

[0017] The mobile communication device 102 may be implemented for example, as a cellular telephone (also called a mobile station or user equipment). The mobile communication device 102 represents a wide variety of devices that have been developed for use within various networks. Such communication devices include, for example, cellular telephones, messaging devices, personal digital assistants (PDAs), notebook or laptop computers incorporating communication modems, mobile data terminals, application specific gaming devices, video gaming devices incorporating wireless modems, and the like. Herein, wireless communication technologies may include, for example, voice communication, the capability of transferring digital data, SMS messaging, Internet access, multi-media content access, and/or voice over internet protocol (VoIP).

[0018] As discussed above, the initiation and processing of a data transfer occurs upon detection of a charging current. Also as mentioned, it may be beneficial to process a data transfer during charging because data transfer may consume substantial power, and may otherwise deplete a power source or battery. The power source 112 that provides power to the mobile communication device 102 may be, for example, a Li-Ion battery, a NiCad battery, or a battery that uses another rechargeable battery technology and therefore may need regular recharging. The power source 112 is configured to receive a charging current, for example from the charger 104. A charger port 114 may be provided on the device 102 for connection to the charger 104. The mobile communication device 102 further includes a memory 116 coupled to the controller 108 and configured to store data.

[0019] As discussed briefly above, a user may set up data transfer rules that govern data transfer between the mobile communication device 102 and another device. Alternatively, the data transfer rules may be previously stored default rules. It is understood that any manner in which to provide data transfer rules is within the scope of this discussion. Accordingly, the mobile communication device 102 may include a data transfer rules setup application 132 configured to receive rules input to govern data transfer between the mobile communication device 102 and the data storage device 106 and/or data storage device 107. That is, the data transfer rules indicate which data to transfer, for example, via a menu delivered when charging is initiated, or may automatically determine when there has been a change in data and automatically store new or revised data stored in the device 102. Moreover, the data transfer rules may indicate which data to transfer between the device 102 and the data storage device 106, and which data to transfer between the device 102 and the data storage device 107. In this manner data synchronization among the multiple devices 102, 106, and 107 may be accomplished via the data transfer rules.

[0020] In one embodiment, a data transfer rule may indicate for example, which devices are “my devices” on the network. Any device that is “my device” may be desired to have the same data as each additional “my device”, with certain exceptions, such as data that is too large for the storage capacity of a mobile device. In the case where the data is too large a sub-folder or special algorithm may be used to select which subset of data will be identical on all “my devices”. A sub-folder may be created by the user, for example. Files to be synced may be stored in the sub-folder.

[0021] An example of an algorithm is one that adds the file size of the most recent data files until the storage amount available in the mobile device is reached. The most recent data is synchronized, instead of all of the data. The synchronization process transfers data to and from each “my device” until all devices' data becomes identical. This may require multiple passes and user intervention for conflict resolution since data may have changed differently on each device. A similar method can be used for data that is transferred (one-way) instead of synced (two-way).

[0022] Other data transfer rules may include selection of specific data types to be synced and/or transferred, for example, contacts, calendar data, pictures, videos, music, call logs, and other specific data types. A user may choose some or all of the data types. Other data transfer rules may include more details within a specific data type, for example via the use of meta tags. Pictures or videos may have meta tags identifying content of the pictures or videos, such as who is in it, the location, the date, and/or the time. A user can select to sync or transfer for example, only pictures of a certain person or pictures taken on a certain date, range of dates or at a specific location. It is understood that many other possible data transfer rules in addition to the examples provided above are within the scope of this discussion.

[0023] The mobile communication device 102 further includes a charge detector 136 configured to detect a charging current to recharge the power source 112 to initiate the data transfer by executing one or more data transfer rules. As mentioned, by initiating a data transfer during a charge, the likelihood that the data transfer will be complete is high since the device is less likely to run out of power during the data transfer. Moreover, the mobile communication device 102 in addition includes a connectivity link determination application 144 that is configured to determine a connectivity link, for example, connectivity link 120, for data transfer between the mobile communication device 102 and the data storage device 106 and/or the data storage device 107, based on circumstances. It is understood that the connectivity link 120 may be a network connection, for example, a USB connection to a router or hub, or a wireless link to a wireless local area network (WLAN). It is further understood that the connectivity link 120 may include connections to more than the data storage devices 106 and 107, for example. The connectivity link determination application 144 is configured to decide among different connectivity links 129, as discussed further below. That is, the connectivity link determination application 144 will choose which link to use to transfer the data. Accordingly, the mobile communication device 102 also includes a data transfer initiator 150 that is configured to initiate data transfer between the mobile communication device 102 and the data storage devices 106 and/or 107, or other data storage devices, based on detection of a charging current to recharge the power source 112.

[0024] The data transfer rules setup application 132, the charge detector 136, the connectivity link determination application 144 and the data transfer initiator 150 can carry out certain processes of the methods as described herein. Steps of methods may involve modules, applications, and devices, and other modules, applications, and devices not discussed here may be inferred by the methods discussed herein. The modules, applications, and devices can be implemented in software, such as in the form of one or more sets of prestored instructions, and/or hardware, which can facilitate the operation of the mobile communication device as discussed below. The modules, applications, and devices may be installed at the factory or can be installed after distribution by, for example, a downloading operation in the case of software. The operations in accordance with the modules, applications and devices will be discussed in more detail below.

[0025] FIG. 2 shows an embodiment of a mobile communication device 202 that includes a charge detection handshake module and that can be coupled to another device 206 for data transfer. The charge detection handshake module allows for synchronization of two or more devices. In FIG. 2, many of the modules are similar or analogous to the devices and applications of the mobile communication device 102 of FIG. 1, but not all are located on the mobile communication device 202; instead, some are located in device 206. As discussed below, only a charge detector and charge initiator, along with the charge detection handshake module mentioned above, are located on the mobile communication device 202.

[0026] FIG. 2 also includes a storage device or data store 206 analogous to the data storage device 106 or 107 of FIG. 1. The device 206 may be a stationary device, for example, a desktop computer or a server, or may be a portable device, for example, a laptop computer, a PDA, or even a cellular telephone. In this discussion, the storage device 206 is typically referred to as a stationary device 206, however it is understood that the device 206 may be any type of device including a portable device, as described above. The stationary device 206 can include data storage capability that may be analogous to the data storage device 106. As discussed, the charge detection by the mobile communication device 202 may cause initiation of a data transfer between the mobile communication device 202 and the stationary device 206. The mobile communication device 202 may automatically transfer data to and from the stationary device 206 upon detection of a charging current such as may be received from, for example, a charger 104. The stationary device 206 may also be referred to herein as a data store or a data storage device.

[0027] In the embodiment of FIG. 2, the stationary device 206 may detect what connectivity links may be available between the mobile communication device 202 and the stationary device 206. As discussed above in connection with FIG. 1, connectivity links may include, for example, USB, Bluetooth, WiMAX, WiFi, UWB, and/or other types of connectivity for data transfer. When the data transfer between the mobile communication device 202 and the data storage device 206 has been successful set up, the data transfer may commence. In this manner a user of a mobile communication device 202 may transfer data between the two devices 202 and 206, and may, therefore, effect data backup or data update, with a minimal number of manual steps.

[0028] As mentioned the data transfer can occur in one direction or in both directions 120 (see FIG. 1). It is understood that there may be more than one device analogous to device 202, and/or more than one device analogous to device 206. In this way, there may be data transfer between more than two devices. It is understood that there may be any number of devices between which data transfer may take place in a system as described herein.

[0029] The mobile communication device 202 includes a controller 208 configured to execute instructions in particular, data transfer rules to determine which data to transfer. The mobile communication device 202 may in addition include a transceiver 210 that may be coupled to the controller 208. The transceiver 210 may provide a wireless connectivity link with another device, for example, the stationary or portable device 206. The transceiver 210 may support, for example, Bluetooth, WiMAX, WiFi, UWB, and/or another wireless technology and which of these connectivity links to use may be determined by a connectivity module or application.

[0030] Similar to device 102 (see FIG. 1), the mobile communication device 202 includes a power source 212 that is configured to provide power to the mobile communication device. The power source 212 uses a rechargeable battery technology, and may be for example, a Li-Ion battery, a NiCad battery, or another type of battery. The power source 212 is configured to receive a charging current, for example from the charger 104. As described above in connection with FIG. 1, a charger port 114 may be provided on the device 202 for connection to the charger 104. The mobile communication device 202 further includes a memory 216 coupled to the controller 208 and configured to store data and instruction modules 218 that can carry out certain processes of the methods as described herein.

[0031] In the device 202, the modules 218 may include, for example, a charge detector module 236 configured to monitor the presence of a charging current. The modules 218 may further include a charge initiator module 238 that is configured to initiate charging of the power source 212 upon detection of a charging current. The modules 218, as mentioned above, may in addition include a charge detection handshake module 240 configured to send an indication to another device, such as, for example, the stationary device 206, that a charging current has been detected by the mobile communication device 202. As will be discussed below, the storage device 206 also includes a handshake module 242 to receive an indication that a charger has been detected by the device 202. Before discussing the modules 218 further, the stationary device 206 is described in more detail.

[0032] Analogous to the stationary device 106 (see FIG. 1) in that it can be configured to store data, the stationary device 206 includes a controller 220 configured to execute instructions, for example, of instruction modules. The stationary device 206 can in addition include a transceiver 222 coupled to the controller 220. The transceiver 222 can provide a wireless connectivity link with the mobile communication device 202. As discussed above in connection with the transceiver 210, the transceiver 222 may support, for example, Bluetooth, WiMAX, WiFi, UWB, and/or another wireless technology. In an embodiment there may be one or more wireless links 224 between the stationary device 206 and the mobile communication device 202. As mentioned above, the two devices 202 and 206 may alternatively or in addition be connected by one or more wired links 226, for example by USB.

[0033] The stationary device 206 further includes a memory 228 coupled to the controller 220 and configured to store data and instruction modules 230 that can carry out certain processes of the methods as described herein. The modules 230 may include, for example, a data transfer rules module 234 that is configured to process data transfer between the stationary device 206 and the mobile communication device 202. The modules 230 may in addition include a charge detection handshake module 242 configured to receive an indication from another device, such as, for example, the mobile communication device 202, that a charging current has been detected by the mobile communication device 202. As mentioned above, the charge detection handshake module 242 of the stationary device 206 is a counterpart to the charge detection handshake module 240 of the mobile communication device 202.

[0034] The modules 230 may in addition include a connectivity detector module 246 configured to detect at least one connectivity link between the stationary device 206 and the mobile communication device 202. The modules 230 may further include a connectivity selector module 248 configured to select a connectivity link to use for data transfer in accordance with an automated selection determination. The automated selection determination may be based on an algorithm or based on predefined criteria. An algorithm may include, for example, examining all available connectivity links for data transfer speed, then choosing the connectivity link with the highest data transfer speed. Predetermined criteria may include, for example, to always use a wired connectivity link, such as a USB cable connection, if available, for connectivity reliability. The modules 230 may further include a data transfer initiator module 250 that is configured to initiate data transfer between the stationary device 206 and the mobile communication device 202, based on detection of a charging current to the power source 212 and based on data transfer rules. In this manner a user may better ensure safety of data of the mobile communication device 202 by backing up the data during regular charging of the mobile communication device 202, for example, during nightly charging, for storage on the stationary device 206.

[0035] Steps of methods may involve modules and other modules (not discussed here) may be inferred by the methods discussed herein. The modules 218 and 230 can be implemented in software, such as in the form of one or more sets of prestored instructions, and/or hardware, which can facilitate the operation of the mobile communication device 202 and the stationary device 206 as discussed below. The modules may be installed at the factory or can be installed after distribution by, for example, a downloading operation. The operations in accordance with the modules will be discussed in more detail below. As in the embodiment described relating to FIG. 1, the user may simply initiate recharging the power source 212 by any suitable means, and based on the data transfer rules, the data may be transferred between devices in either or both directions 120 (see FIG. 1) automatically. In this way, the user avoids cumbersome and time consuming setup for data transfer during a charging process.

[0036] FIG. 3 shows a flow chart of an embodiment of a method 300 of data transfer between a mobile communication device 102 (see FIG. 1) and a storage device 106 and/or 107, and/or between a mobile communication device 202 (see FIG. 2) and another device 206. It is understood that method steps may occur in a different order without departing from the scope of this disclosure. The differences between the embodiments described with respect to FIGS. 1 and 2 relate to which devices include certain functions. Therefore, the flow chart of FIG. 3 may be read to describe either embodiment shown, and those not shown but described.

[0037] The stationary device 206 may receive 332 data transfer rules to process a data transfer between the stationary device 206 and the mobile communication device 202. As mentioned, the data transfer rules may be generated by a user or may be default rules. It is understood that in another embodiment, for example the embodiment of FIG. 1, the mobile communication device 102, rather than the stationary device 106 and/or 107, may receive the data transfer rules to process a data transfer between the stationary device 106 and the mobile communication device 102. The receiving 332 of the data transfer rules may take place in accordance with a data transfer rules setup application 132 (see FIG. 1) or in accordance with a data transfer rules module 234. As discussed above, a user may determine which data to transfer, such as sent and received messages, phonebook updates, media downloads and calendar updates. Data transfer rules may be by default as well.

[0038] When a user connects the mobile communication device 202 (see FIG. 2) to a charger, for example charger 104 (see FIG. 1), the mobile communication device 202 may detect 336 the presence of a charging current to recharge the power source 212 of the mobile communication device 202, in accordance with the charge detector 136 and/or the charger detection module 236.

[0039] The charge detector 136 (see FIG. 1) and/or the charger detection module 236 (see FIG. 2) may detect that the mobile communication device 202 receives a charging current. In an embodiment the charge detector 136 and/or the charger detection module 236 may detect the presence of an external source of charging current, for example, a charger cable, coupled to the charger port 114. In an embodiment the charge detector 136 and the charger detection module 236 may be distinct. In another embodiment the charge detector 136 for example, may be a component of the charger detection module 236.

[0040] The charging of the power source 212 (see FIG. 2) may commence in accordance with the charge initiator module 238. The charge initiator module 238 may for example, monitor the charge state of the power source. The charge initiator module 238 may in addition monitor whether a charging current has been detected by the charge detector 136 (see FIG. 1) or the charger detection module 236. In an embodiment, the charge detector 136 or the charger detection module 236 may notify the charge initiator module 238 when a charging current has been detected. The charge initiator module 238 may provide that the power source 212 receive charge appropriate to its charge state, and based on the presence of a charging current. In this manner the power source 212 may be replenished by connection of the mobile communication device 202 to a charger 104.

[0041] As mentioned, the embodiment of FIG. 2 includes charger detection handshake modules of devices 202 and 206. The mobile communication device 202 (see FIG. 2) and the stationary device 206 may execute 340 a handshaking process between the devices, for example by sending an indication of charger detection from the mobile communication device 202 to the stationary device 206. The handshaking 340 may be accomplished by a charger detection handshaking module 240 in the mobile communication device 202, together with a complementary charger detection handshaking module 242 in the stationary device 206.

[0042] The stationary device 206 (see FIG. 2) may monitor 344 at least one connectivity link between the stationary device and the mobile communication device 202. For example, the controller 220 may regularly poll or otherwise assess the status of the transceiver 222. In an embodiment, the transceiver 222 may represent a variety of transceivers, for example in the case where the stationary device 206 may communicate wirelessly according to more than one wireless technology 228. The controller 220 may then acquire connectivity link status information for one or more wireless connectivity links 228 and one or more wired connectivity links 230 in accordance with connectivity link determination application 144 (see FIG. 1) and/or in accordance with connectivity detector module 246. The connectivity link determination application 144 may be configured to determine a connectivity link based on an algorithm and/or based on predefined criteria, as discussed below in connection with the connectivity selector module 248.

[0043] The controller 220 selects 348 a connectivity link between the stationary device 206 and the mobile communication device 202 based on the connectivity link status information for the one or more wireless connectivity links 228 and the one or more wired connectivity links 230. The selection 348 may be accomplished according to the connectivity selector module 248. As mentioned above, the connectivity selector module 248 is configured to select a connectivity link to use for data transfer in accordance with an automated selection determination. The automated selection determination may be based on an algorithm, or based on predefined criteria. An example of selecting a connectivity link based on an algorithm or predefined criteria includes choosing the fastest connectivity link, for example, WiFi, WiMAX, or UWB over Bluetooth. Another example of selecting a connectivity link based on an algorithm or predetermined criteria includes choosing the most reliable connectivity link, for example, a wired link like a USB cable. Other predefined criteria may include the most available link, that is, the link with the least traffic, the link with the least number of devices serviced by the link, and/or the link with the most optimal quality of service, where quality of service may be defined according to, for example, signal strength.

[0044] The stationary device 206 (see FIG. 2) and the mobile communication device 202 initiate 350 data transfer between the devices 202 and 206 according to data transfer rules, and based upon detecting a charging current by the first device, as discussed above in connection with step 336. The initiation 350 of the data transfer may be effected by a data transfer initiator module 250. In another embodiment, the initiation 350 of the data transfer may be effected by a data transfer initiator 150 (see FIG. 1). The activation and operation of the data transfer initiator 150 and/or the data transfer initiator module 250 may be coupled with the activation and operation of the charge initiator module 238. The data transfer may continue for example, so long as the charger 104 is connected to the mobile communication device 202. As mentioned previously, the data transfer may include, for example, calendar entries, emails, phonebook data, video and/or music clips, and images, among other data. Therefore, a user may ensure backup of their data during regular charging of the mobile communication device, for example, during nightly charging, without needing to remember to back up their data.

[0045] Methods and devices that may automatically transfer data upon detection of a charging current have been described. A mobile communication device may detect what connectivity links such as WiFi, Bluetooth, USB, etc., may be available between the mobile communication device 102 (see FIG. 1) and, for example a data storage device 106. Upon successful setup of data transfer such as transfer of calendar information, phonebook updates, sent and received messages, downloaded media files, etc., between the mobile communication device and the data storage device, the data transfer may commence. In this manner a user of a mobile communication device may transfer data between the mobile communication device and the data storage device, for purposes of, for example, data backup or data update, with a minimal number of manual steps, and may better ensure safety of the data of the mobile communication device by backing up the data, for example, during nightly charging.

[0046] This disclosure is intended to explain how to fashion and use various embodiments in accordance with the technology rather than to limit the true, intended, and fair scope and spirit thereof. The foregoing description is not intended to be exhaustive or to be limited to the precise forms disclosed. Modifications or variations are possible in light of the above teachings. The embodiment(s) was chosen and described to provide the best illustration of the principle of the described technology and its practical application, and to enable one of ordinary skill in the art to utilize the technology in various embodiments and with various modifications as are suited to the particular use contemplated. All such modifications and variations are within the scope of the invention as determined by the appended claims, as may be amended during the pendency of this application for patent, and all equivalents thereof, when interpreted in accordance with the breadth to which they are fairly, legally and equitably entitled.