WO2023159194A2 - Système et procédé pour fournir des stations de charge de dispositifs mobiles interconnectées et sécurisées - Google Patents

Système et procédé pour fournir des stations de charge de dispositifs mobiles interconnectées et sécurisées Download PDF

Info

Publication number
WO2023159194A2
WO2023159194A2 PCT/US2023/062840 US2023062840W WO2023159194A2 WO 2023159194 A2 WO2023159194 A2 WO 2023159194A2 US 2023062840 W US2023062840 W US 2023062840W WO 2023159194 A2 WO2023159194 A2 WO 2023159194A2
Authority
WO
WIPO (PCT)
Prior art keywords
worker
devices
charging stations
users
storage housings
Prior art date
Application number
PCT/US2023/062840
Other languages
English (en)
Other versions
WO2023159194A3 (fr
Inventor
Douglas BALDASARE
Sheri TATE
Robert Kay
Jeffrey Bergeland
David ANDREASEN
Saran Singh Sound
Michael Weinberg
Ashwin Muthiah
Omkar Borse
Jake Brigham
Charles Williams
Original Assignee
ChargeItSpot, LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US17/675,136 external-priority patent/US20220181887A1/en
Application filed by ChargeItSpot, LLC filed Critical ChargeItSpot, LLC
Publication of WO2023159194A2 publication Critical patent/WO2023159194A2/fr
Publication of WO2023159194A3 publication Critical patent/WO2023159194A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H02—GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
    • H02J—CIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
    • H02J7/00—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries
    • H02J7/00032—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries characterised by data exchange
    • H—ELECTRICITY
    • H02—GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
    • H02J—CIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
    • H02J7/00—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries
    • H02J7/0013—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries acting upon several batteries simultaneously or sequentially
    • H—ELECTRICITY
    • H02—GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
    • H02J—CIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
    • H02J2310/00—The network for supplying or distributing electric power characterised by its spatial reach or by the load
    • H02J2310/10—The network having a local or delimited stationary reach
    • H02J2310/20—The network being internal to a load
    • H02J2310/22—The load being a portable electronic device
    • H—ELECTRICITY
    • H02—GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
    • H02J—CIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
    • H02J7/00—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries
    • H02J7/0042—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries characterised by the mechanical construction
    • H02J7/0044—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries characterised by the mechanical construction specially adapted for holding portable devices containing batteries

Definitions

  • the instant disclosure relates to mobile devices, and, in particular, to systems and methods for providing interconnected, secure public or private mobile device charging stations.
  • Mobile devices such as cellular phones, personal digital assistants, tablets, and the like, are now widely used and heavily depended upon for voice and data communications.
  • the battery of the mobile device needs to be recharged from time to time.
  • mobile device users may be located at public or private locations without the ability to recharge the mobile device battery.
  • public mobile device charging stations these stations are limited in number and location. Consequently, a mobile device user runs the risk of his mobile device battery being exhausted before locating an available station to recharge the mobile device.
  • Figure 1 illustrates a diagram of a system according to embodiments of the present invention
  • Figure 2 illustrates a block diagram of a mobile device according to embodiments of the present invention
  • Figure 3 illustrates a block diagram of a system according to embodiments of the present invention
  • Figure 4A illustrates an example of a mobile device charging station according to embodiments of the present invention
  • Figure 4B illustrates another example of a mobile device charging station according to embodiments of the present invention.
  • Figure 4C illustrates an example of an open locker of a mobile device charging station according to embodiments of the present invention
  • Figure 5 is a schematic illustration of an exemplary computing device, in accordance with at least some exemplary embodiments of the present disclosure.
  • Figure 6 is a schematic illustration of an exemplary network, in accordance with at least some exemplary embodiments of the present disclosure.
  • Figure 7 is a schematic illustration of an exemplary network, in accordance with at least some exemplary embodiments of the present disclosure.
  • Figure 8 illustrates an example of a charging station according to embodiments of the present invention.
  • Figure 9 illustrates an example of a charging station according to embodiments of the present invention.
  • Figure 10 illustrates an example of a charging station according to embodiments of the present invention.
  • Figure 11 illustrates an example of a charging station according to embodiments of the present invention.
  • Figure 12 illustrates a block diagram of a system according to embodiments of the present invention.
  • Figure 13 illustrates an example of a charging station according to embodiments of the present invention.
  • Figure 14 illustrates an example of a charging station according to embodiments of the present invention.
  • Figure 15 illustrates an example of a charging system according to embodiments of the present invention.
  • Figure 16 illustrates a flowchart of an exemplary method according to embodiments of the present invention.
  • the present disclosure is directed to a system for charging a plurality of worker devices for use by a plurality of users, comprising one or more charging stations, each charging station including a plurality of storage housings, one or more detection devices, and an identification device, and a controller.
  • the controller is configured to: selectively lock and unlock the plurality of worker devices in the plurality of storage housings of the one or more charging stations; electrically charge the plurality of worker devices when locked in the plurality of storage housings of the one or more charging stations; validate an identity of the plurality of users with the identification device of the one or more charging stations when the plurality of users removes or returns the plurality of worker devices to the plurality of storage housings of the one or more charging stations; detect a presence of the plurality of worker devices in the plurality of storage housings using the one or more detection devices of the one or more charging stations; update data of the plurality of worker devices or the plurality of storage housings based on data transferred from the identification device and the one or more detection devices of the one or more charging stations; and identify available worker devices of the plurality of worker devices or available storage housings of the plurality of storage housings to the plurality of users based on the data of the plurality of worker devices or the plurality of storage housings.
  • the present disclosure is directed to a method, comprising: providing a plurality of worker devices for use by a plurality of users; providing one or more charging stations, each charging station including a plurality of storage housings; selectively locking and unlocking the plurality of worker devices in the plurality of storage housings of the one or more charging stations; electrically charging the plurality of worker devices when locked in the plurality of storage housings of the one or more charging stations; validating an identity of the plurality of users when the plurality of users removes or returns the plurality of worker devices to the plurality of storage housings of the one or more charging stations; detecting a presence of the plurality of worker devices in the plurality of storage housings of the one or more charging stations; updating data of the plurality of worker devices or the plurality of storage housings based on data transferred from the one or more charging stations; and identifying available worker devices of the plurality of worker devices or available storage housings of the plurality of storage housings to the plurality of users based on the data of the
  • a user would be advantageous for a user to use a system to be alerted of the locations of nearby public or private charging stations to charge his mobile device when the battery power level of his mobile device decreases to a low level. It would be particularly advantageous if such a system and method also provided: advertising opportunities for retailers; the ability for retailers to drive traffic to a store or stores; a mobile application, such as a mobile application that would indicate and/or suggest charging station locations, and/or that would monitor a user’s use and the correspondent battery charge; and the like.
  • Mobile devices such as cellular phones, personal digital assistants, tablets, and the like are now widely used and heavily depended upon for voice and data communications, and for information generally.
  • mobile devices In order to be operational, mobile devices typically employ the use of rechargeable batteries. These batteries need to be recharged from time to time in order to maintain proper power levels for the operation of the mobile device. For example, some estimate that the typical user runs very low on battery power in a mobile device multiple times each week.
  • a conventional charger generally utilizes alternating current, and specifically typically uses either 110V or 220V “household” current designed for general use, it is often difficult to recharge a mobile device battery in a public place or while traveling without access to a suitable power terminal.
  • the amount of current a phone accepts is generally “stepped down” from the 110V or 220V alternating current, such as typically using a “wall wart” charger that comes with the phone, as would be apparent to the skilled artisan.
  • such charging would require the user to also be traveling with a charger, which may be inconveniently bulky or easily forgotten.
  • the present invention provides for a user to have readily available, secure charging capabilities. This is contrary to presently available charging solutions, which are typically non-secure at least in that the only security generally provided is when the user stands nearby to “guard” his/her phone.
  • the inventive aspects may also provide for a user to be alerted of the locations of available public charging stations when the battery power level of his mobile device decreases to a low level.
  • the mobile device may request, from the server, information of one or more registered businesses, i.e., any place of business that includes a charging unit, that house a charging station within a specified distance from the mobile device.
  • the disclosed system and method may also provide: advertising and differentiating opportunities for retailers; the ability for retailers to drive traffic to, and maintain traffic in, a store or stores; a mobile application, such as a mobile application that would indicate and/or suggest charging station locations, and/or that would monitor a user’s use and the correspondent battery charge; and the like.
  • a mobile application such as a mobile application that would indicate and/or suggest charging station locations, and/or that would monitor a user’s use and the correspondent battery charge; and the like.
  • a user’s time in-store in a retail establishment is likely to be increased as the user shops while awaiting a recharge.
  • the user is also provided with a differentiated, enhanced customer shopping experience that increases consumer loyalty.
  • GPS satellites (or other known mobile device locating technologies, such as triangulation) 100 operate to determine a location of a mobile device 104 that contains features, some of which features may be available based upon the location data.
  • mobile device 104 may refer to cellular phones, personal digital assistants, tablets, and the like.
  • the mobile device 104 may determine its location through the use of received GPS signals, or through the use of a filter which may combine location data from the GPS signals and/or from another system, such as cell-tower-triangulation or a WLAN system in order to obtain a location or a more accurate location.
  • the mobile device 104 may be wirelessly coupled to server 106.
  • the server 106 may be communicatively coupled to a datastore 108, as well as to a plurality of charging stations 110.
  • the server 106 periodically receives and stores location information associated with the mobile device 104. This location information may be sent from the mobile device 104; pulled from the mobile device 104; or obtained from another service that is able to determine the location of the mobile device (e.g., Location Based Services (LBS), Assisted GPS (A-GPS), eGPS, GSM Localization, Multilaterilization, Radiolocation, Trilateration, etc.).
  • LBS Location Based Services
  • A-GPS Assisted GPS
  • eGPS GSM Localization
  • Multilaterilization Radiolocation
  • Trilateration Trilateration
  • Wi-Fi access points that consumers are allowed to utilize. These access points may also be used to help ascertain the location of a user or his relation to publicly available charging stations. For example, a Skyhook Wireless system may be used. This location information may be analyzed independent of or in conjunction with other forms of information or location information. For example, Wi-Fi location information may be particularly useful in certain indoor environments where other technologies (e.g. GPS) may have more difficulty functioning, such as in a shopping mall housing a collection of retail businesses.
  • technologies e.g. GPS
  • Embodiments of the present invention allow a mobile device user (who may become registered with the system upon using the charging station 110 for the first time) to be alerted of the locations of available public charging stations when the battery power level of his mobile device decreases, such as to a predetermined threshold level, which may be automatically set or which may be previously set by the user. Accordingly, when the battery power of the mobile device decreases below this predetermined threshold level (for example, 20% of its maximum power), the mobile device may request, from the server, information of one or more registered businesses housing a charging station within a specified distance from the mobile device.
  • a predetermined threshold level for example, 20% of its maximum power
  • the location information of the mobile device may be sent to the server and compared with: the location information of one or more of the registered businesses housing a charging station; a list or a preferential list of registered businesses housing a charging station; a list of registered businesses having charging stations and making offers to consumers that those businesses wish to be known to the consumers; and the like.
  • a mobile device user may be out in public, shopping. Becoming occupied with his shopping, the user may forget or neglect to check the battery power level of his mobile device.
  • the system and method may notify the user via his mobile device that the battery power of the device is indeed low, and then may display to the user a nearby store which houses a charging station, and that has a charging unit, such as a charging “locker,” available.
  • the mobile device app may display the number of charging lockers available so a user does not waste time going to a charging station that does not have any charging lockers available.
  • the user may have enough time to locate and subsequently recharge his mobile device battery for continued use of his mobile device without having to cut short his shopping experience or risk losing operation of his mobile device.
  • the business may experience increased consumer traffic, as potential consumers enter the business to recharge their phone, and the opportunity to make targeted enticements to consumers having a known location proximate to the registered business.
  • usage of the disclosed cell phone charging kiosk resulted in an increase in dwell time of 130%, an increase in spend of 51%, and an increase in Net Promoter Score of 26%.
  • Fig. 2 shows a block diagram of a mobile device 104 according to an embodiment.
  • a receiver 202 may receive signals transmitted from GPS satellites, cell-towers, and/or access points for WLAN communication.
  • a transmitter 204 may transmit signals including location information to the remote server or other access points.
  • Power is provided to the various components of the mobile device 104 through battery 206.
  • a station location module 208 may monitor a power level of the battery 206, and, based on the power level, the station location module 208 may provide station location information to the user of the mobile device 104. It should be noted that the station location module 208 may be able to monitor other functions and features of the mobile device as well. This information may be stored in one or more of databases described in datastore 108.
  • the various modules within the mobile device 104 may operate as described hereinthroughout.
  • a controller/processor 210 may direct the operation of various modules within mobile device 104, such as by execution of software program code to perform the functions discussed hereinthroughout.
  • a memory 212 may store data and program codes for mobile device 104.
  • Fig. 3 shows a block diagram of a system 300 according to embodiments of the present invention.
  • the system 300 comprises one or more charging stations 110, server 106 and data store 108.
  • the server 106 performs the tasks of providing charging station information to the mobile device.
  • This charging station information may include geographical locations and/or directions to one or more respective charging stations and registered businesses in which these charging stations are housed or otherwise associated.
  • This charging station information may also include advertisements or other types of information related to the associated businesses.
  • This charging station information is stored in one of the various databases 302-310 in data store 108. It should be noted that the various databases 302-310 shown in data store 108 may be organized as separate databases, portions of a single database, or by any other logical structure appropriate for storing the data.
  • an alternative embodiment may include a UPS
  • this locally stored information may be periodically purged, such as when a phone is obtained, or daily or weekly.
  • data store 108 stores user information in user database 302. This information may include email addresses, phone numbers, user photos, survey responses, duration of charge, and the like.
  • a map database 304 may also be included. This database 304 may provide the background maps that are displayed on each user’s mobile device and that correspond to an area or region around the user at the time the application is invoked (i.e., when the user’ s mobile device battery is low). For example, a map tile of the United States may provide an image of the continental U.S. that can be zoomed to display a regional street level map for any area in the U.S. The map may further be zoomed to display locations within a venue housing a collection of businesses. For example, a user may be located within a mall, and the application may be invoked due to his mobile device battery being low. The mobile device may display locations of retail stores within the mall which house available charging stations to charge the user’s mobile device, either upon zooming in on the application by the user, or by a predetermined setting for displaying a location.
  • a location database 306 may store geographic locations of charging stations and/or geographic locations of mobile devices 104 and/or clusters thereof.
  • a charging station database 308 may store the current status of available lockers within any charging stations. This status may include a number of lockers of a particular charging station not currently in use, or, available, for charging.
  • the data store 108 may also comprise a registered business database 310, which may store information related to businesses currently registered with the charging system according to embodiments of the present invention.
  • the business database 310 may include approved advertisements, or associated content describing respective registered businesses.
  • Fig. 4A illustrates a mobile device charging station 110 according to embodiments of the present invention.
  • This station 110 may be located in a retail store, mall, hospital, stadium, casino, building lobby, or any other location suitable for accessibility.
  • station 110 includes a housing 402 mounted on a support 404.
  • Embodiments may also include, on a face of the charging station 110, branding or advertising space 409 for a registered business to provide information about its business, which may include, by non-limiting example, advertisements, coupons, or any other suitable content related to its business.
  • Each housing 402 may comprise one or more lockers 407, preferably having resident therein supplied power, such as a plurality of charging cords or other wireless charging options, such as supplied power having different plugs, power mats, or like proprietary or third party charging formats for mating to different mobile devices, such as USB plugs, micro-USB, mini-USB or USB-C plugs, laptop tip plugs, and/or one or more proprietary plugs, such as plugs for an iPhone 3, 4,5, 6, 7, 8, and so on.
  • any other charging plugs that presently exist or are subsequently developed may be included, as well as any other current or subsequent charging methodologies, such as charging mats, wireless charging, etc.
  • housing 402, support 404, locker 407, and branding space 409 may have any desired dimension or configuration, depending, at least in part, on the particular location of the station 110, and that the overall design of station 110 shown in Fig. 4A is for exemplary purposes only.
  • charging stations may comprise eight lockers, each with multi-use charging cables, and/or multiple different charging cables, there within.
  • the lockers may reside in a structure formed of a suitably durable composition, such as metal, acrylic, plastics or other, and combinations thereof.
  • the door of a charging locker may allow for the user to see inside the locker, but may be formed of a combination or metal or other, and/or an acrylic panel that can withstand forces up to or exceeding, by way of non-limiting example, 10,000 psi.
  • a durable cabinet construction may allow for usage in a variety of environments, and the durable construction may be formed accordingly, such as by metal treated with rust proofing.
  • other measures may be taken for kiosks for use in outdoor environments such as gasketing, heating and ventilation systems, etc.
  • the durable housing may house there within a variety of other features, such as antennas, PCBs, and the like, as referenced herein throughout.
  • antennas may be placed atop, behind, or alongside in physical association with a cabinet.
  • the antennas and associated or alternative hardware may be suitable to communicate and/or connect to a network, such as a local or global network, such as the Internet, using any of a variety of different communication methodologies dependent upon the context in which the cabinet is placed, such as using 4G LTE, 3G, a wide area network, a local area network, or the like.
  • a network such as a local or global network, such as the Internet
  • 4G LTE, 3G, a wide area network, a local area network, or the like such as using 4G LTE, 3G, a wide area network, a local area network, or the like.
  • multiple different antennas may provide this functionality, where a single antenna may provide multiple different functionalities for communication purposes. Accordingly, and dependent in part on location, communication speeds may be optimized by software or firmware algorithms within the cabinet, or remotely by an administrator, by way of non-limiting example.
  • each individual charging locker can be at least partially transparent to a user
  • other features may be added within each individual charging locker, such as multi-color LEDs or blinking LEDs, also as referenced herein. These additional features may be controlled locally or remotely, such as to provide optionality correspondent to time of year, i.e., Christmas lights, branding of the unit, whether or not a locker is in use (i.e., a red light may mean that locker is in use), and the like.
  • Different mechanisms may be mounted on or associated with the housing 402 to enable a user to access, lock, and subsequently unlock an individual locker 407 for charging his mobile device 104.
  • the locking mechanism associated with a charging locker such as in order to provide optimal security, may be break proof or resistant, such as withstanding up to or in excess of 1,000 pounds of force before yielding.
  • FIG. 4A another mechanism, such as a bar code scanner or card or key FOB reader, and/or a display 408, such as a touch screen display (which may also display ads, coupons, codes and/or other aspects referenced herein), and/or a keypad 406 mounted to the housing 402, may allow for the collection of more user information.
  • a display 408 and microcontroller (not shown) connected to an electronic, keyless lock 413 (Fig. 4C), a user may be provided with instructions and options for charging his or her mobile device 104.
  • the locker 407 may be preprogrammed by the microcontroller (not shown) to accept a selected sequence or information entry by a new user when the electronic lock is unlatched (i.e. the locker 407 is open).
  • the microcontroller (not shown) may be configured to accept the same sequence or information first entered by the user causing the lock to unlatch, allowing the user to remove his phone from the locker after use.
  • This sequence or information may include user identifying information, such as the user’s telephone number, key code, pin numbers, security questions, email addresses, selection of security images, scanning of a bar code (such as on a ticket provided by the kiosk to a user when the user placed the phone in the locker), etc.
  • the display 408 may thus prompt the user for other identifying information for the collection and subsequent storage of user shopping information which may be valuable to retailers/registered businesses.
  • the display 408 may prompt the user to enter his name, a telephone number, an email address, a name and/or telephone number in conjunction with other information, such as a security “pin” having 2, 3, 4, 5, 6 or more digits or such as a security image, a loyalty program identifier, or the like.
  • the display may prompt the user to enter his telephone number.
  • additional user identifying information may be gathered as a part of these instructions. This gathered information may be used to serve several purposes. One purpose may be to provide verification information that the user is, indeed, who he says he is (such as by way of comparison to registered user information for system 300, by way of verification with information stored in the mobile application having associated therewith the aforementioned map and battery charge level capabilities, and/or by comparison with personal information on or associated with the mobile device.
  • Another purpose is to ensure that only the user (or, an individual authorized by the user) is able to access the mobile device 104 from the locker 407 after the mobile device has been locked in the given locker 407.
  • another purpose for the prompted user identifying information is to gather information about the user’s shopping habits and/or frequented registered businesses, and/or other information as described hereinthroughout, which may be subsequently stored in user database 302 (as shown in Fig. 3).
  • the embodiments may thus include one or more remote, or local, data warehouses/databases 302.
  • the data warehouse may include user information as discussed above and throughout, and/or may comprise reports, calculations, and the like, run over a predetermined time period in association with a kiosk or a group of kiosks, such as once per day.
  • the data in the data warehouse may be segregated by user, user type, brand, group, and so on. For example, phone numbers and emails may be indicative of uniquely personal identifying information, and as such may be segregated by brand or group to which the user is willing to allow that information to be provided. Needless to say, this may provide enhanced security of use to users.
  • the display 408 may display an image of which a user has previously selected upon initially accessing an available locker. For example, the user may enter a telephone number, and then either select or be shown an image, such as a black dog. Upon returning to unlock the locker, the user may be prompted to enter his phone number, and then to select the appropriate image that matches the preselected image in order to unlock the locker.
  • the exemplary disclosed process and system may include a safety system having safety components such as, for example, gloves, styli, shields, and other suitable safety components.
  • the exemplary disclosed system may include a safety assembly 490.
  • Safety assembly 490 may provide one or more safe and/or contactless techniques for users (e.g., consumers) to interact with stations or kiosks (e.g., phone charging kiosks) of the exemplary disclosed system.
  • Safety assembly 490 may include a dispenser that may be provided on a station or kiosk housing and that may operate to dispense gloves that a user may wear while interacting with the exemplary disclosed user interface (e.g., a touch screen). The gloves may be dispensed manually or automatically by safety assembly 490.
  • safety assembly 490 may include a motion sensor that detects a presence or approach of a user (e.g., or may detect when users wave their hands), and based on this detection safety assembly 490 may automatically dispense a glove or pair or gloves to the user.
  • the gloves may be single-use gloves (e.g., latex, PVC, PVA, neoprene or any other suitable type of glove for preventing a transmission of bacteria, viruses, or other pathogens), which may provide a contactless experience (e.g., avoid direct contact).
  • Safety assembly 490 may also dispense contact devices such as styli, “hooks,” or other similar contact devices similarly to the exemplary dispensing of gloves described above.
  • a user may utilize the manually or automatically dispensed contact devices to press buttons on the exemplary disclosed user interface of the station or kiosk (e.g., screen) and/or to push a door (e.g., locker door) closed after a device such as a user phone is connected or disconnected (e.g., to a charging cable of the exemplary disclosed station or kiosk).
  • Safety assembly 490 may also include a glove, styli, and/or waste disposal bin that may be attached or mounted to the station or kiosk to provide an efficient and effective technique for a user (e.g., customer) to dispose of any materials used to facilitate touchless interaction.
  • Users and/or venue operators may opt into one or more of the exemplary disclosed components of safety assembly 490 as add-ons (e.g., via entering input or making selections via the exemplary disclosed user interface) to utilize to reduce the spread of germs and viruses from the kiosk at a given venue.
  • users and/or venue operators may provide suitable payment to have access to the exemplary disclosed components of safety assembly 490 (e.g., and to pay for use of one-time use components of safety assembly 490) to reduce a probability of infection to a user or to users at a given station or kiosk located at a given venue.
  • the exemplary disclosed system may also include a shield component 495 disposed at any desired components, for example as illustrated at Fig. 4C.
  • Shield component 495 may be for example a shield layer.
  • shield component 495 may be disposed at the exemplary disclosed user interface (e.g., touchscreen) and/or other touchable areas of the station or kiosk.
  • Shield component 495 may be an anti-pathogen shield such as an anti-virus shield.
  • shield component 495 may be a layer that is mechanically attached (e.g., or magnetically attached) or adhered to surfaces of the station or kiosk.
  • shield component 495 may be formed from thin transparent or translucent (or opaque material).
  • Shield component 495 may be formed from any suitable metallic or plastic material.
  • Shield component 495 may include materials that may prevent pathogens such as viruses and bacteria from replicating or spreading, thereby rendering the pathogens inactive over a period of time (e.g., with no additional cleaning involved to maintain sanitization).
  • pathogens such as viruses and bacteria
  • Fig. 5 An illustrative representation of a computing device appropriate for use with embodiments of the system of the present disclosure is shown in Fig. 5.
  • the computing device lOOd can generally be comprised of a Central Processing Unit (CPU, lOld), optional further processing units including a graphics processing unit (GPU), a Random Access Memory (RAM, 102d), a mother board 103d, or alternatively/additionally a storage medium (e.g., hard disk drive, solid state drive, flash memory, cloud storage), an operating system (OS, 104d), one or more application software 105d, a display element 106d, and one or more input/output devices/means 107d, including one or more communication interfaces (e.g., RS232, Ethernet, Wi-Fi, Bluetooth, USB).
  • communication interfaces e.g., RS232, Ethernet, Wi-Fi, Bluetooth, USB
  • Useful examples include, but are not limited to, personal computers, smart phones, laptops, mobile computing devices, tablet PCs, and servers. Multiple computing devices can be operably linked to form a computer network in a manner as to distribute and share one or more resources, such as clustered computing devices and server banks/farms.
  • data may be transferred to the system, stored by the system and/or transferred by the system to users of the system across local area networks (LANs) (e.g., office networks, home networks) or wide area networks (WANs) (e.g., the Internet).
  • LANs local area networks
  • WANs wide area networks
  • the system may be comprised of numerous servers communicatively connected across one or more LANs and/or WANs.
  • LANs local area networks
  • WANs wide area networks
  • the system may be comprised of numerous servers communicatively connected across one or more LANs and/or WANs.
  • the system and methods provided herein may be employed by a user of a computing device whether connected to a network or not.
  • some steps of the methods provided herein may be performed by components and modules of the system whether connected or not. While such components/modules are offline, and the data they generated will then be transmitted to the relevant other parts of the system once the offline component/module comes again online with the rest of the network (or a relevant part thereof). According to an embodiment of the present disclosure, some of the applications of the present disclosure may not be accessible when not connected to a network, however a user or a module/component of the system itself may be able to compose data offline from the remainder of the system that will be consumed by the system or its other components when the user/offline system component or module is later connected to the system network.
  • FIG. 6 a schematic overview of a system in accordance with an embodiment of the present disclosure is shown.
  • the system is comprised of one or more application servers 203d for electronically storing information used by the system.
  • Applications in the server 203d may retrieve and manipulate information in storage devices and exchange information through a WAN 201d (e.g., the Internet).
  • Applications in server 203d may also be used to manipulate information stored remotely and process and analyze data stored remotely across a WAN 201d (e.g., the Internet).
  • exchange of information through the WAN 20 Id or other network may occur through one or more high speed connections.
  • high speed connections may be over-the-air (OTA), passed through networked systems, directly connected to one or more WANs 201d or directed through one or more routers 202d.
  • Router(s) 202d are completely optional and other embodiments in accordance with the present disclosure may or may not utilize one or more routers 202d.
  • server 203d may connect to WAN 201d for the exchange of information, and embodiments of the present disclosure are contemplated for use with any method for connecting to networks for the purpose of exchanging information. Further, while this application refers to high speed connections, embodiments of the present disclosure may be utilized with connections of any speed.
  • Components or modules of the system may connect to server 203d via WAN 201d or other network in numerous ways.
  • a component or module may connect to the system i) through a computing device 212d directly connected to the WAN 201d, ii) through a computing device 205d, 206d connected to the WAN 201d through a routing device 204d, iii) through a computing device 208d, 209d, 210d connected to a wireless access point 207d or iv) through a computing device 21 Id via a wireless connection (e.g., CDMA, GMS, 3G, 4G, 5G) to the WAN 201d.
  • a wireless connection e.g., CDMA, GMS, 3G, 4G, 5G
  • server 203d may connect to server 203d via WAN 201d or other network, and embodiments of the present disclosure are contemplated for use with any method for connecting to server 203d via WAN 201d or other network.
  • server 203d could be comprised of a personal computing device, such as a smartphone, acting as a host for other computing devices to connect to.
  • the communications means of the system may be any means for communicating data, including image and video, over one or more networks or to one or more peripheral devices attached to the system, or to a system module or component.
  • Appropriate communications means may include, but are not limited to, wireless connections, wired connections, cellular connections, data port connections, Bluetooth® connections, near field communications (NFC) connections, or any combination thereof.
  • NFC near field communications
  • the cloud-based system is shown as it may interact with users and other third party networks or APIs (e.g., APIs associated with the exemplary disclosed E-Ink displays).
  • a user of a mobile device 801 may be able to connect to application server 802.
  • Application server 802 may be able to enhance or otherwise provide additional services to the user by requesting and receiving information from one or more of an external content provider API/wcbsitc or other third party system 803, a constituent data service 804, one or more additional data services 805 or any combination thereof.
  • application server 802 may be able to enhance or otherwise provide additional services to an external content provider API/wcbsitc or other third party system 803, a constituent data service 804, one or more additional data services 805 by providing information to those entities that is stored on a database that is connected to the application server 802.
  • an external content provider API/wcbsitc or other third party system 803 may be able to enhance or otherwise provide additional services to an external content provider API/wcbsitc or other third party system 803, a constituent data service 804, one or more additional data services 805 by providing information to those entities that is stored on a database that is connected to the application server 802.
  • One of ordinary skill in the art would appreciate how accessing one or more third-party systems could augment the ability of the system described herein, and embodiments of the present invention are contemplated for use with any third-party system.
  • a computer program includes a finite sequence of computational instructions or program instructions. It will be appreciated that a programmable apparatus or computing device can receive such a computer program and, by processing the computational instructions thereof, produce a technical effect.
  • a programmable apparatus or computing device includes one or more microprocessors, microcontrollers, embedded microcontrollers, programmable digital signal processors, programmable devices, programmable gate arrays, programmable array logic, memory devices, application specific integrated circuits, or the like, which can be suitably employed or configured to process computer program instructions, execute computer logic, store computer data, and so on.
  • a computing device can include any and all suitable combinations of at least one general purpose computer, special-purpose computer, programmable data processing apparatus, processor, processor architecture, and so on.
  • a computing device can include a computer-readable storage medium and that this medium may be internal or external, removable and replaceable, or fixed.
  • a computing device can include a Basic Input/Output System (BIOS), firmware, an operating system, a database, or the like that can include, interface with, or support the software and hardware described herein.
  • BIOS Basic Input/Output System
  • Embodiments of the system as described herein are not limited to applications involving conventional computer programs or programmable apparatuses that run them. It is contemplated, for example, that embodiments of the disclosure as claimed herein could include an optical computer, quantum computer, analog computer, or the like.
  • a computer program can be loaded onto a computing device to produce a particular machine that can perform any and all of the depicted functions.
  • This particular machine (or networked configuration thereof) provides a technique for carrying out any and all of the depicted functions.
  • the computer readable medium may be a computer readable signal medium or a computer readable storage medium.
  • a computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
  • Illustrative examples of the computer readable storage medium may include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • a data store may be comprised of one or more of a database, file storage system, relational data storage system or any other data system or structure configured to store data.
  • the data store may be a relational database, working in conjunction with a relational database management system (RDBMS) for receiving, processing and storing data.
  • RDBMS relational database management system
  • a data store may comprise one or more databases for storing information related to the processing of moving information and estimate information as well one or more databases configured for storage and retrieval of moving information and estimate information.
  • Computer program instructions can be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to function in a particular manner.
  • the instructions stored in the computer-readable memory constitute an article of manufacture including computer-readable instructions for implementing any and all of the depicted functions.
  • a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof.
  • a computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
  • Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
  • computer program instructions may include computer executable code.
  • languages for expressing computer program instructions are possible, including without limitation C, C++, Java, JavaScript, assembly language, Lisp, HTML, Perl, and so on. Such languages may include assembly languages, hardware description languages, database programming languages, functional programming languages, imperative programming languages, and so on.
  • computer program instructions can be stored, compiled, or interpreted to run on a computing device, a programmable data processing apparatus, a heterogeneous combination of processors or processor architectures, and so on.
  • embodiments of the system as described herein can take the form of web-based computer software, which includes client/server software, software-as-a-service, peer-to-peer software, or the like.
  • a computing device enables execution of computer program instructions including multiple programs or threads.
  • the multiple programs or threads may be processed more or less simultaneously to enhance utilization of the processor and to facilitate substantially simultaneous functions.
  • any and all methods, program codes, program instructions, and the like described herein may be implemented in one or more thread.
  • the thread can spawn other threads, which can themselves have assigned priorities associated with them.
  • a computing device can process these threads based on priority or any other order based on instructions provided in the program code.
  • process and “execute” are used interchangeably to indicate execute, process, interpret, compile, assemble, link, load, any and all combinations of the foregoing, or the like. Therefore, embodiments that process computer program instructions, computer-executable code, or the like can suitably act upon the instructions or code in any and all of the ways just described.
  • the exemplary disclosed system may utilize sophisticated machine learning and/or artificial intelligence techniques to prepare and submit datasets and variables to cloud computing clusters and/or other analytical tools (e.g., predictive analytical tools) which may analyze such data using artificial intelligence neural networks.
  • the exemplary disclosed system may for example include cloud computing clusters performing predictive analysis.
  • the exemplary neural network may include a plurality of input nodes that may be interconnected and/or networked with a plurality of additional and/or other processing nodes to determine a predicted result.
  • Exemplary artificial intelligence processes may include filtering and processing datasets, processing to simplify datasets by statistically eliminating irrelevant, invariant or superfluous variables or creating new variables which are an amalgamation of a set of underlying variables, and/or processing for splitting datasets into train, test and validate datasets using at least a stratified sampling technique.
  • the exemplary disclosed system may utilize prediction algorithms and approach that may include regression models, treebased approaches, logistic regression, Bayesian methods, deep-learning and neural networks both as a stand-alone and on an ensemble basis, and final prediction may be based on the model/structure which delivers the highest degree of accuracy and stability as judged by implementation against the test and validate datasets.
  • the exemplary disclosed system, apparatus, and method may be a system for use by workers performing tasks in a facility or location that may be for example any suitable type of store (e.g., a location selling goods or services to consumers), medical or healthcare facilities such as hospitals, warehouse, distribution facility, factory, government services location (e.g., social security office, department of motor vehicles office, or unemployment office), transportation facility (e.g., airport or train station), maintenance facility (e.g., location for facilitating maintenance of a building or bridge), military or law enforcement facility, and/or any other suitable facility or location in which workers are located. Workers may be service operators. Workers may be non-customers or non-consumers.
  • store e.g., a location selling goods or services to consumers
  • medical or healthcare facilities such as hospitals, warehouse, distribution facility, factory, government services location (e.g., social security office, department of motor vehicles office, or unemployment office), transportation facility (e.g., airport or train station), maintenance facility (e.g., location for facilitating maintenance of a building or
  • Workers may include any suitable type of employees, contractors (e.g., independent contractors), individuals performing any suitable tasks, and/or any other suitable type of worker performing work for any type of organization (e.g., a company or any other type of business association, a government agency or department, any suitable type of profit or not-for-profit organization, or any other suitable type of organization) with which the exemplary disclosed system, apparatus, and method is associated.
  • workers may be retail store workers, maintenance workers, government workers, security forces (e.g., government, commercial, private, law enforcement, military, and/or any other suitable type of security forces), and/or any other suitable type of worker who performs tasks for an organization with which the exemplary disclosed system, apparatus, and method is associated.
  • the exemplary disclosed system, apparatus, and method may be a worker-based system, apparatus, and method.
  • the exemplary disclosed system, apparatus, and method may be a back-of-house system, apparatus, and method. Workers may utilize worker devices (e.g., back-of-house devices) with the system for example as described herein.
  • the exemplary disclosed system, apparatus, and method may include one or more charging stations.
  • the exemplary disclosed system, apparatus, and method may include one or more charging stations for devices such as mobile devices.
  • the exemplary disclosed system, apparatus, and method may include one or more charging stations for charging back-of-house devices.
  • the exemplary disclosed system, apparatus, and method may provide secure charging and inventory management for worker devices (e.g., back-of-house devices).
  • the worker devices may be handheld devices.
  • the worker devices may be provided (e.g., access provided to) or issued by an organization utilizing the exemplary disclosed system, apparatus, and method to workers of the organization.
  • the worker devices may be used by the workers to perform tasks or work (e.g., job functions).
  • the worker devices may be any suitable type of electronic device such as, for example, tablets (e.g., smart tablets), phones (e.g., smartphones), handheld computers, scanners, walkie-talkies, credit card readers, security scanners or devices (e.g., metal or explosive detectors or tasers), remote controls, drones or drone equipment, and/or any other suitable equipment or devices utilized by workers in any suitable field or activity.
  • tablets e.g., smart tablets
  • phones e.g., smartphones
  • handheld computers e.g., scanners, walkie-talkies, credit card readers, security scanners or devices (e.g., metal or explosive detectors or tasers), remote controls, drones or drone equipment, and/or any other suitable equipment or devices utilized by workers in any suitable field or activity.
  • scanners e.g., walkie-talkies
  • credit card readers e.g., metal or explosive detectors or tasers
  • remote controls e.g., metal or explosive detectors or
  • Figs. 8 and 9 illustrate an exemplary embodiment of the exemplary disclosed system, apparatus, and method.
  • System 500 may include a charging station 505 (e.g., a charging kiosk) that may for example include components generally similar to the exemplary disclosed charging stations disclosed above regarding Figs. 4A-4C.
  • Data transfer and reporting may be provided during an operation of system 500 via a user device such as a mobile device, email reporting, via a website or portal, via a user interface of charging station 505, and/or any other suitable technique.
  • charging station 505 may include a user interface 510 that may be similar for example to the exemplary disclosed user interfaces described herein.
  • user interface 510 may be a touchscreen.
  • Charging station 505 may also include one or more storage housings 515, 520, and 525 that may be similar to the storage housings described herein.
  • storage housings 515, 520, and 525 may each be storage or security lockers including cavities for securing and charging one or more worker devices 530.
  • Storage housings 515, 520, and 525 may be compartments or lockers that may be selectively locked and unlocked for example as described above.
  • Storage housings 515, 520, and 525 may be of varying sizes and configurations for securing and charging different types of worker devices 530.
  • storage housing 525 may be larger than storage housing 520, and storage housing 520 may be larger than storage housing 515.
  • Charging station 505 may also include a scanner 535.
  • Scanner 535 may be any suitable type of scanner such as, for example, a radio-frequency identification (RFID) scanner.
  • Scanner 535 may also include a barcode scanner or a QR scanner.
  • Scanner 535 may scan or read any suitable object including a code such as, for example, a barcode or QR code and/or RFID.
  • the scanned object may be an object carried or located with a user (e.g., a worker) such as a tag, card, or any other suitable item.
  • Scanner 535 may also include a biometric device such as a biometric scanner (e.g., finger scanner or optical scanner).
  • a worker may identify himself or herself to charging station 505 by any suitable technique. For example, a worker may enter a password or code via user interface 510 and/or may provide identification via scanner 535. For example via user interface 510 and/or scanner 535, workers may input employee codes, scan or swipe badges, scan QR codes from their phone, or provide input via RFID cards or tags.
  • Charging station 505 may also include imaging devices for example as described herein that may take a photo and/or video of a worker who may access storage housings 515, 520, and/or 525 to remove one or more worker devices 530. Charging station 505 may also operate to record a date and timestamp recording the time at which a given worker device 530 was retrieved from charging station 505.
  • a first worker 540 may return a given worker device 530, and a second worker 540 (e.g., who may be a different worker than the first worker) may retrieve the given worker device 530 after worker device 530 has been charged. Any number of different workers may utilize the same worker device 530 at different times based on an operation of system 500.
  • Various worker devices 530 may be stored in select storage housings 515, 520, and 525 based on a level of access granted to different types of workers. For example, a given worker 540 may be given access to select storage housings 515, 520, and 525 storing and charging worker devices 530 to which that given worker 540 has access.
  • Such role-based access may provide for a given worker 540 gaining access to select worker devices 530 (e.g., select storage housings 515, 520, and 525 storing and charging select types of worker devices 530) appropriate for performing his or her job functions, while other worker devices 530 may remain securely locked and not accessible to that given worker 540.
  • select worker devices 530 e.g., select storage housings 515, 520, and 525 storing and charging select types of worker devices 530
  • each worker device 530 may be stored (e.g., housed and charged) in a single storage housing 515, 520, or 525. Also in at least some exemplary embodiments, one or more worker devices 530 may be stored (e.g., housed and charged) in storage housings 515, 520, and 525.
  • System 500 may operate (e.g., as described herein) to record each worker device 530 that is removed or returned by one or more of the following mechanisms: worker 540 may indicate via user interface (e.g., touchscreen) which worker device 530 is removed; worker device 530 may include an RFID chip that may be automatically detected as having been removed from charging station 505 when worker device 530 passes through a predetermined portion (e.g., a locker door opening) of storage housing 515, 520, or 525; and/or system 500 may detect a change in current in one of the charging cables (e.g., similar to the exemplary disclosed charging cable described herein) and/or detects a physical detachment when worker device 530 is unplugged from the exemplary disclosed charging cable.
  • worker 540 may indicate via user interface (e.g., touchscreen) which worker device 530 is removed
  • worker device 530 may include an RFID chip that may be automatically detected as having been removed from charging station 505 when worker device 530 passes through a predetermined portion (e.g., a
  • system 500 may automatically open a door of corresponding storage housing 515, 520, or 525 holding a worker device 530 in an appropriate category such as that has a highest amount of charge, has been charging for the longest period of time, is the newest worker device 530 in a fleet, and/or any other suitable criteria (e.g., from a business perspective).
  • system 500 may automatically open a door of a given storage housing 515, 520, or 525 based on an input of the identity of a given worker 540 (e.g., may select a given worker device 530 according to the exemplary criteria based on the input of an identity of worker 540 via an operation of user interface 510 and/or scanner 535).
  • worker 540 may indicate (e.g., provide input for example onscreen via user interface 510) that he or she is returning a worker device 530 that has been damaged, has scratches, does not function so that the proper repair or replacement cycle can be initiated, and/or exhibits any other unsuitable operation.
  • system 500 may communicate with staff and/or support personnel associated with workers 540 (e.g., provide an online portal such as an online portal for back-of-house management) to provide real time or near real-time data regarding a status of worker devices 530 (e.g., which have been removed and which are being stored and charged), and may provide data and reports of the status of worker devices 530 including for example “shrink” (e.g., lost or stolen devices).
  • staff and/or support personnel associated with workers 540 may include managers, business staff (e.g., corporate staff), tech support, IT department members, and/or third party vendors who may manage the exemplary disclosed devices.
  • System 500 may provide for communication (e.g., reporting and data transfer) regarding theft or loss (e.g., shrinkage) of devices, battery level of devices, damage to devices, and/or any other suitable information. For example, if a given worker 540 does not return one or more worker devices 530 within a predetermined time period (e.g., during a shift period of worker 540), an exception report may be issued by system 500 (e.g., via the exemplary disclosed portal, text message or email, user interface 510, and/or any other suitable communication technique) to alert managers as to which workers 540 have outstanding worker devices 530 (e.g., have not returned worker devices 530 to charging station 505).
  • theft or loss e.g., shrinkage
  • System 500 may operate for example to prevent a given worker 540 who has not returned one or more worker devices 530 from removing or checking out any additional worker devices 530 (e.g., without a manager override or other suitable approval action).
  • System 500 may include a detection device 542 that may be disposed on or at charging station 505 and/or in one or more of the exemplary disclosed storage housings.
  • Detection device 542 may be any suitable device for detecting a given worker 540 removing and/or returning a given worker device 530 such as, for example, a camera (e.g., picture or video), a biometric device such as a fingerprint scanner, an identification badge scanner, and/or any other suitable device for identifying an individual removing and/or returning devices.
  • system 500 may provide a back-of-house solution that may include many storage housings (e.g., lockers) and one or more user interfaces (e.g., screens) that allow users (e.g., workers) to access the lockers.
  • the lockers may vary in size depending on the device or devices to be stored, charged, and/or dispensed. For example, different sized lockers may be provided such as, for example, lockers that may be sized to accommodate relatively larger devices and/or may supply relatively more electrical current.
  • System 500 may include one or more charging stations 505 that may be configured as appropriate for a given field, industry, or type of organization utilizing system 500.
  • system 500 may check out and check in distinct devices to different users, and track whether or not these devices have been returned.
  • System 500 may track a location or status of worker devices 530 (e.g., including utilizing positioning such as GPS of worker devices 530 or other location data for example as described herein).
  • System 500 may utilize (e.g., leverage) user input to track a condition of worker devices 530.
  • System 500 may utilize identification data (e.g., as described above) to manage access of workers 540 to worker devices 530 (e.g., role -based access).
  • System 500 may utilize photo verification for example as described herein to track a last worker 540 to have checked a given worker device 530 in or out and to track and manage loss for users of system 500 (e.g., for retailers).
  • system 500 may operate to provide an electronic role-based ledger for device management (e.g., based on the exemplary disclosed computing systems) that also securely charges worker devices 530 between uses.
  • System 500 may include a plurality of charging stations 505 (e.g., a fleet of kiosks) to manage a plurality of worker devices 530 (e.g., a fleet of devices).
  • System 500 may provide access to an exemplary disclosed storage housing (e.g., locker) via worker input (e.g., input of an employee code), swiping or scanning an identification badge or other item, RFID badge, QR code, and/or any other suitable technique.
  • System 500 may track when a user (e.g., worker 540) checks out one or more worker devices 530 but does not return it (e.g., within a predetermined time period).
  • System 500 may transfer (e.g., share) data including photo-verification (e.g., photo or video data), drop-off and pick-up time of devices, employee codes, and/or any other suitable data with suitable parties.
  • photo-verification e.g., photo or video data
  • drop-off and pick-up time of devices e.g., employee codes, and/or any other suitable data with suitable parties.
  • System 500 may selectively open storage housings (e.g., lockers) based on % battery remaining of working devices 530 and/or time since start of charging. System 500 may selectively charge more than one device. System 500 may manage (e.g., enforce) role-based access to particular storage housings (e.g., lockers) based on which devices are used by particular workers and/or on particular shifts (e.g., based on worker ID). System 500 may track serial numbers and other data of worker devices 530. System 500 may include any desired number of exemplary disclosed storage housings.
  • FIGs. 10 and 11 illustrate an exemplary embodiment of the exemplary disclosed system, apparatus, and method.
  • System 700 may include a charging station 705 (e.g., a charging kiosk) that may be similar to charging station 505.
  • Charging station 705 may include a user interface 710a and a user interface 710b that may each be similar to user interface 510.
  • Charging station 705 may also include a plurality of storage housings 715 and 720 that may be similar to storage housings 515, 520, and 525.
  • Charging station 705 may further include a scanner 735 that may be similar to scanner 535.
  • an ARC system 1500 may include several interconnected components including exemplary disclosed charging stations such as charging stations 1505 (e.g., ARC Kiosks), an ARC Server 1605, and an ARC Client Portal 1610.
  • the exemplary disclosed charging stations 1505 e.g., ARC Kiosks
  • the exemplary disclosed charging stations 1505 may securely store worker devices such as mobile devices as described herein.
  • Charging stations 1505 e.g., the ARC Kiosks
  • ARC Server 1605 may track the state of some or all charging stations 1505 (e.g., the ARC Kiosks) and their corresponding lockers at a given location. When a status of a given locker changes, ARC Server 1605 may push communication to other ARC Kiosks in a same location 1601 (e.g., a geographic area such as a venue) so that some or all ARC Kiosks within a given location 1601 are in sync with each other.
  • An ARC Admin 1615 e.g., an ARC Admin Portal or Platform
  • charging stations 1505 e.g., the ARC Kiosks
  • the ARC Kiosks for functional features as well as to brand a given ARC Kiosk for a given client.
  • ARC Client Portal 1610 may track which employees and devices may be available for use at a given location. For example, workers (e.g., employees) may not check out or return a device without a valid employee ID or badge ID (e.g., the ID on a given worker’s badge may be the same or different than the given worker’s employee ID). ARC Client Portal 1610 may also track which worker devices are available or may be checked for repair.
  • workers e.g., employees
  • badge ID e.g., the ID on a given worker’s badge may be the same or different than the given worker’s employee ID.
  • ARC Client Portal 1610 may also track which worker devices are available or may be checked for repair.
  • ARC system 1500 may interface with any number of desired external systems (e.g., one or more client systems 1620).
  • Client system 1620 may for example maintain real-time or near real-time records of information such as workers 1540 (e.g., employees such as workers or technicians) similar to as described above regarding workers 540, managers, worker devices 1530, tickets (e.g., work tickets or maintenance tickets), and/or any other desired data records.
  • workers 1540 e.g., employees such as workers or technicians
  • tickets e.g., work tickets or maintenance tickets
  • client system 1620 may be an employee system that may include details (e.g., data of workers 1540 and/or managers) such as Employee First and Last Name, date of birth, email address, mobile number (e.g., for purposes of sending auto-generated email or SMS messages), employee role (e.g., to determine role-based access to systems), and/or any other suitable data.
  • ARC system 1500 may reduce or substantially minimize operational redundancies so that data for use by ARC system 1500 may not be maintained across multiple external databases and may be maintained by the exemplary disclosed databases of ARC system 1500.
  • ARC system 1500 may interface with client systems 1620 based on direct APIs, ARC Client Portal 1610 (e.g., which may accept manual inputs of worker 1540, managers, worker devices 1530, and/or bulk inputs for example via .csv files and/or any other suitable input or command entry).
  • client systems 1620 based on direct APIs, ARC Client Portal 1610 (e.g., which may accept manual inputs of worker 1540, managers, worker devices 1530, and/or bulk inputs for example via .csv files and/or any other suitable input or command entry).
  • the exemplary disclosed API may include an ARC App that may be an extension of ARC Client Portal 1610 and/or ARC Admin 1615, and may be downloaded to user devices of users (e.g., iOS or Android devices).
  • team leads 1540a and managers 1540b may have access to the exemplary disclosed API, and workers 1540 may not have access (e.g., or workers 1540 who may be technicians may have access, or some or substantially all workers 1540 may have some access).
  • team leads 1540a and managers 1540b may have a greater level of access to the exemplary disclosed API than workers 1540.
  • the exemplary disclosed system may include users having multiple roles and multiple corresponding levels of access.
  • a given manager e.g., manager 1540b
  • a team lead e.g., team lead 1540a
  • the exemplary disclosed API may provide managers the ability to view reports, add and remove employees and worker devices from the exemplary disclosed rosters of ARC system 1500, see issues that are to be addressed at charging stations 1505, and/or any other suitable features or information.
  • the exemplary disclosed API may be utilized in relatively large locations 1601 such as warehouses and arenas in which managers may not be stationary in an office, but may instead be moving around while at work.
  • the exemplary disclosed API may keep managers up-to-date with the status of charging stations 1505 under their management.
  • the exemplary disclosed API may also include a companion application (e.g., a third party device companion app).
  • the companion app e.g., for Android devices, Apple devices, or any other suitable operating system
  • the companion app may be installed on the client devices (e.g., client user devices).
  • the companion app may communicate with the servers (e.g., ARC Server 1605) of ARC system 1500 and may provide information such as device battery level, device serial number, and location data of worker devices 1530. This information may be used for purposes such as tracking worker devices 1530, maintaining an inventory list, tracking device battery levels, and/or any other suitable purpose.
  • the information may also be communicated (e.g., via data transfer with the server) while a device is stored in charging station 1505 (e.g., in a locker) and not in use.
  • the information may also be used in conjunction with information collected through the operation of ARC system 1500 to increase accuracy and functionality of ARC system 1500 (e.g., of certain features of ARC system 1500). For example, if the data from the companion app of the exemplary disclosed API indicates a low battery level while the worker device has been charging in charging station 1505 (e.g., a locker) for a relatively long period of time, then it can be inferred that there may be an issue with the device and/or locker.
  • the exemplary disclosed maintenance workflow for example as described herein may thereby be initiated.
  • ARC system 1500 may provide a ticketing system in which one or more workers 1540 (e.g., an employee) or managers indicate via the exemplary disclosed interface of charging station 1505 (e.g., an ARC touchscreen and/or a user device, worker device 1530, or exemplary disclosed API) that a worker device 1530 and/or charging station 1505 has been damaged.
  • ARC system 1500 may automatically generate and route data (e.g., a ticket) to a system operator, technician, manager, or worker 1540 who may inspect and/or repair the reported worker device 1530 and/or charging station 1505.
  • ARC system 1500 may interface with an employee database. For example if workers 1540 (e.g., an employee) do not return their worker device 1530 before the end of their shift, ARC system 1500 may store data indicating that a given worker 1540 has a worker device 1530 checked out. ARC system 1500 may interface with client system 1620 (e.g., an employee clock-in system) to provide data indicating the worker device 1530 is still checked out, and client system 1620 may prevent the worker 1540 from clock- in access or certain system permissions for their shift until the worker device 1530 is returned and corresponding data noted, received, and/or updated by ARC system 1500.
  • client system 1620 e.g., an employee clock-in system
  • ARC system 1500 may interface with client system 1620 to provide data indicating the worker device 1530 has been returned (e.g., at which point client system 1620 may restore access or permission to that worker 1540).
  • ARC system 1500 may interface with an employee database when a worker 1540 (e.g., a new employee) is hired and issued an Employee ID. Data of that ID may be transmitted to ARC in real-time or near real-time so that the worker 1540 may utilize ARC system 1500 to for example immediately check out a worker device 1530 on the employee’s first day of work.
  • a worker 1540 e.g., a new employee
  • Employee ID may be transmitted to ARC in real-time or near real-time so that the worker 1540 may utilize ARC system 1500 to for example immediately check out a worker device 1530 on the employee’s first day of work.
  • Figs. 13 and 14 illustrate an exemplary disclosed charging station 1505 of ARC system 1500.
  • ARC system 1500 may include one or more charging stations 1505 that may be similar to charging station 505 (e.g., a charging kiosk) that may for example include components generally similar to the exemplary disclosed charging stations disclosed above regarding Figs. 4A-4C. Some components of ARC system 1500 may operate similarly to system 500 for example as described above.
  • ARC system 1500 may include a plurality of charging stations 1505 that may be similar to charging stations 505.
  • Charging station 1505 may include a user interface 1510 that may be similar to user interface 510, and one or more storage housings 1515, 1520, and 1525, which may be similar to storage housings 515, 520, and 525, for securing and charging one or more worker devices 1530 that may be similar to worker devices 530.
  • Storage housings 1515, 1520, and/or 1525 may be upper lockers or lower lockers based on their position in charging station 1505.
  • storage housings 1515, 1520, and/or 1525 may be stored in columns with the exemplary disclosed storage housings disposed at various heights of the column.
  • storage housings 1515, 1520, and/or 1525 disposed at a bottom portion (e.g., a bottom third or a bottom half) of charging station 1505 may be lower lockers that may be below a height guideline provided by law or government policy (e.g., specified by the American Disabilities Act for individuals in wheelchairs). Lower lockers may also be suitable for individuals (e.g., workers 1540) who may be relatively short and may not be able to reach the upper lockers of charging station 1505.
  • storage housings 1515, 1520, and/or 1525 disposed at an upper portion (e.g., an upper third or an upper half) of charging station 1505 may be upper lockers that may be suitable for individuals (e.g., workers 1540) who may not want to bend down (e.g., or who have difficulty bending due to injuries or back problems) to retrieve or replenish worker devices 1530 stored in charging station 1505.
  • individuals e.g., workers 1540
  • data indicating whether a given worker 1540 may comfortably use upper lockers, lower lockers, or both upper and lower lockers of storage housings 1515, 1520, and/or 1525 may be provided to, stored by, and used during an operation of the exemplary disclosed system.
  • Workers 1540 may also use the exemplary disclosed user interface to select or request lower lockers or upper lockers.
  • charging station 1505 may also include an identification device such as a scanner 1535 that may be similar to scanner 535.
  • the exemplary disclosed identification device e.g., scanner 1535
  • the exemplary disclosed identification device may for example be a biometric device for determining an identity of a user, an RFID device, a scanning device, a manual entry device (e.g., for receiving input from a user to confirm the user’s identity), camera technology (e.g., an image recognition device such as a facial recognition imaging device), and/or any other suitable device for determining and/or confirming an identity of a user.
  • Charging station 1505 may also include a detection device 1542 that may be similar to detection device 542.
  • Charging station 1505 including scanner 1535 and detection device 1542 may for example operate similarly to the exemplary disclosed operation of charging station 505 described above.
  • Scanner 1535 may be any suitable device for validating an identity of a user for example as described herein.
  • Detection device 1542 may for example operate similarly to as described above regarding detection device 542.
  • Detection device 1542 may be any suitable device for detecting whether or not an exemplary disclosed worker device is disclosed in an exemplary disclosed storage housing or locker.
  • detection device 1542 may include a sensor or other suitable electrical component for detecting a current flow through one or more exemplary disclosed charging cables of charging station 1505.
  • Detection device 1542 may include a strain gauge, a weight sensor, and/or any other suitable type of sensor or device for detecting a change in objects or materials (e.g., a presence or absence of one or more worker devices 1530) in a given storage housing 1515, 1520, and/or 1525 of charging station 1505.
  • Detection device 1542 may include an infrared (IR) sensor and/or any other suitable sensing devices for detecting a presence and/or change of position of objects (e.g., one or more worker devices 1530) disposed in a given storage housing 1515, 1520, and/or 1525 of charging station 1505.
  • IR infrared
  • Detection device 1542 may also include sensors for reading tags (e.g., RFID or QR tags) or other identification components of worker devices 1530 to determine whether or not worker devices 1530 may be disposed in a given storage housing 1515, 1520, and/or 1525 of charging station 1505.
  • tags e.g., RFID or QR tags
  • other identification components of worker devices 1530 may be disposed in a given storage housing 1515, 1520, and/or 1525 of charging station 1505.
  • charging station 1505 may include one or more electronic control boards that may power components of ARC system 1500 and may charge different types of worker devices 1530.
  • charging station 1505 may include an AC current monitoring board 1545 and a locker control board 1550.
  • Workers 1540 may use multiple types of worker devices 1530 at a given venue such as location 1601.
  • Each worker device 1530 or type of worker devices 1530 may have a unique functionality and physical characteristics including unique charging methods.
  • a given type of handheld worker device 1530 may include a USB-C port and another given type of relatively larger handheld scanner worker device 1530 may utilize a charging cradle that includes an active AC power connection.
  • ARC system 1500 may thereby be powered by two or more types of electronic control boards (e.g., AC current monitoring board 1545 and locker control board 1550), which may be used in tandem for charging worker devices 1530 or may be interchangeable with each other in charging worker devices 1530.
  • each type of electronic control board e.g., AC current monitoring board 1545 and locker control board 1550
  • AC current monitoring board 1545 may be capable of charging some or any worker devices 1530 that involve an AC adapter or charging cradle.
  • locker control board 1550 may be capable of charging some or any worker devices 1530 using a USB and/or USB-C charging cable.
  • charging station 1505 may include one or more (e.g., a plurality of) indicators 1555.
  • doors of some or substantially all of storage housings 1515, 1520, and/or 1525 may include an indicator 1555.
  • Indicator 1555 may be any suitable device for indicating a status of any given storage housing 1515, 1520, and/or 1525 (e.g., locker).
  • indicator 1555 may be an indicator light such as an LED indicator light.
  • indicators 1555 that may be LED indicator lights may be disposed in or on or near doors of some or substantially all storage housings 1515, 1520, and/or 1525.
  • Indicator 1555 may indicate the status of a given storage housing 1515, 1520, and/or 1525 (e.g., a given locker).
  • a plurality of colors of indicators 1555 corresponding to statuses may be configured and controlled via ARC system 1500 (e.g., ARC Admin 1615).
  • ARC system 1500 e.g., ARC Admin 1615
  • a green light displayed by indicator 1555 may indicate normal operation of a given locker and a red light displayed by indicator 1555 may indicate a potential failure and/or unsuitable operation of a given locker.
  • ARC system 1500 may control indicators 1555 to change a display status in real-time or near real-time.
  • Indicator 1500 may control indicators 1555 to change a display status in real-time or near real-time.
  • ARC system 1500 may also emit audio indications or warnings. For example if a worker 1540 (e.g., a worker, team lead, and/or manager) is detected to be near a given locker based on system tracking of that worker’s worker device 1530, ARC system 1500 may control indicator 1555 of that given locker to emit an audio indication or warning.
  • a worker 1540 e.g., a worker, team lead, and/or manager
  • ARC system 1500 may control indicator 1555 of that given locker to emit an audio indication or warning.
  • At least some portions of charging station 1505 may be formed from structural members 1560. Because at least some or most (e.g., a large majority) of worker devices 1530 housed in charging station 1505 may utilize WiFi communication (e.g., to receive software updates or time sensitive notifications from operators and clients using ARC system 1500), structural members 1560 forming at least some portions of charging station 1505 may allow WiFi signals to pass through structural members 1560. Structural members 1560 may form doors and walls of storage housings 1515, 1520, and/or 1525 and other portions of charging station 1505. Structural members 1560 may be formed from any suitable structural material that allows WiFi signals to pass through them such as, for example, plastic. Structural members 1560 may be formed from non-metal material such as plastic and composite material. For example, structural members 1560 may include plastic locker windows and/or interior panels.
  • Fig. 15 illustrates an exemplary disclosed configuration of ARC system 1500.
  • ARC system 1500 may include one or more locations 1601.
  • a given location 1601 may include one or more stand-alone charging stations 1505 and/or one or more site clusters 1602.
  • Each site cluster 1602 may include a plurality of charging stations 1505.
  • ARC system 1500 may include a plurality of locations 1601 each including one or more standalone charging stations 1505 and one or more site clusters 1602 each including a plurality of charging stations 1505.
  • One or more workers 1540 may work at or near some or substantially all of the exemplary disclosed stand-alone charging stations 1505 and/or charging stations 1505 of site clusters 1602.
  • a team lead 1540a may lead or direct activity or work of workers 1540 at each of some or all of site clusters 1602 and/or locations 1601.
  • a manager 1540b may lead or direct activity or work of team leads 1540a and workers 1540 at a plurality of site clusters 1602 and/or locations 1601. Additional layers of supervisors may also lead or direct activity or work of managers 1540b, team leads 1540a, and workers 1540 such as, for example, supervisors, regional supervisors, directors, and/or any other suitable management role or function.
  • FIG. 16 illustrates an exemplary process 1700 of ARC system 1500.
  • Process 1700 begins at step 1705.
  • ARC system 1500 may validate a user identity.
  • ARC system 1500 may validate an identity of a worker 1540 (e.g., or a team lead 1540a or a manager 1540b). Users may utilize user interface 1510 and/or scanner 1535 of charging station 1505 and/or an API using a user device or worker device 1530 to validate their identities to ARC system 1500.
  • a worker 1540 e.g., or a team lead 1540a or a manager 1540b.
  • Users may utilize user interface 1510 and/or scanner 1535 of charging station 1505 and/or an API using a user device or worker device 1530 to validate their identities to ARC system 1500.
  • workers e.g., employees
  • devices e.g., worker devices 1530
  • ARC system 1500 may be validated in ARC system 1500 using a variety of methods such as manually entering a bar code number (e.g., via user interface 1510 or an exemplary disclosed API), scanning a barcode or QR code label or QR code (e.g., via scanner 1535), using RFID technology (e.g., via scanner 1535), and/or biometric scan (e.g., via detection device 1542).
  • a bar code number e.g., via user interface 1510 or an exemplary disclosed API
  • scanning a barcode or QR code label or QR code e.g., via scanner 1535
  • RFID technology e.g., via scanner 1535
  • biometric scan e.g., via detection device 1542
  • Users may use any desired charging station 1505 of ARC system 1500 to validate their identities or may be directed by ARC system 1500 to use certain charging stations 1505 or a specific charging station 1505 to validate their identities.
  • the user ID may be validated by ARC system 1500 for a user to gain access to storage housing 1515, 1520, or 1525 (e.g., a locker).
  • Charging station 1505 may be configured to support multiple techniques for validating that an acceptable ID is entered by a user. For example, syntactic validation may be used (e.g., any code that is 9 digits long and starts with a certain prefix may be accepted or any code that is exactly 9 digits long and contains at least one letter may be accepted). Also for example, a number of digits may be accepted in which any ID that is a certain number (e.g., six) of digits long may be accepted.
  • a match (e.g., a 100% match) to a database may be used for a user to gain access.
  • any code that has been entered into the database e.g., via the ARC Client Portal 1610 or API or a customer database
  • a user e.g., an employee
  • a company utilizing ARC system 1500 may change that user’s status to inactive. Then, even if an employee code of that user is entered at charging station 1505, access to ARC system 1500 for that user will be denied.
  • a user with an authorized role e.g. a manager such as team lead 1540a or manager 1540b or an Admin or a SuperAdmin of ARC system 1500 or a technician
  • a user with an authorized role may choose to add-to-database in real-time at the kiosk. This may update the database with the new code so that it can be used by a given user (e.g., employee) in the future.
  • a roster of users e.g., workers 1540, team leads 1540a, and managers 1540b
  • devices e.g., worker devices 1530
  • Charging stations 1505 may reference these rosters to determine if a user (e.g., an employee) is validated to transact at charging station 1505, and if a worker device 1530 is validated to be dispensed to a user.
  • This functionality may be configurable in ARC Admin 1615, which may provide flexibility to lift or change validation criteria when appropriate. This may occur for example in an early phase of a new roll out when data of employees or devices (e.g., worker devices 1530) may not be fully updated in ARC Client Portal 1610. Access of users to ARC system 1500 may also be updated based on data transfer with client systems 1620 for example as described above (e.g., access by users may be allowed or blocked based on updated data of employee databases of client systems 1620).
  • ARC system 1500 may determine whether or not a user is using ARC system 1500 for the first time based on stored data (e.g., via ARC Admin 1615). If ARC system 1500 determines that a given user (e.g., worker 1540, team lead 1540a, or manager 1540b) is using ARC system 1500 for the first time, process 1700 proceeds to step 1720.
  • a welcome flow or onboarding process may be presented to the user via user interface 1510 or an API of a user device.
  • any suitable special screens that may be relevant to a first time user may be presented (e.g., an opt-in to terms of the kiosk such as consent to take photos, and/or any other messaging appropriate for first-time users).
  • the welcome flow or onboarding process may include a series of screens that may direct users through the exemplary disclosed software interface.
  • the onboarding screens may educate the user about the functions and benefits of ARC system 1500, provide user opt-in and agreement to terms of use of ARC system 1500, and/or facilitate a positive user experience.
  • the welcome flow or onboarding process may be displayed the first time a user interacts with the system (e.g., displayed once per badge ID). Users may advance through the welcome flow (e.g., by pressing a ‘Next’ button) until the flow is complete.
  • the welcome flow may include a plurality (e.g., up to five) configurable screens that may be managed through ARC Admin 1615.
  • Each configurable screen may include a predefined area in which custom content (e.g., images) may be uploaded by ARC Admin 1615.
  • the uploaded images may be displayed on respective screens to form the welcome flow.
  • a roster of employees and devices may be maintained via ARC Client Portal 1610.
  • charging station 1505 may also support functionality to create or update employee and device records via user interface 1510 (e.g., the kiosk touchscreen) and/or the exemplary disclosed API.
  • user interface 1510 e.g., the kiosk touchscreen
  • an authorized manager e.g., team lead 1540a or manager 1540b
  • Data of the credentials provided via user interface 1510 of charging station 1505 may be sent (e.g., immediately sent) to ARC server 1605 and used to update the roster of ARC Client Portal 1610. After this occurs, the employee may be able to enter into transactions at charging station 1505.
  • ARC system 1500 determines that a given user (e.g., worker 1540, team lead 1540a, or manager 1540b) has used ARC system 1500 before (e.g., not for the first time), process 1700 proceeds to step 1725.
  • a given user e.g., worker 1540, team lead 1540a, or manager 1540b
  • ARC system 1500 may identify available worker devices 1530 (e.g., and/or available storage housings) that may be provided to a given user (e.g., worker 1540, team lead 1540a, or manager 1540b). ARC system 1500 may provide data (e.g., via the exemplary disclosed API) directing a given user to a specific charging station 1505 or to one of a specified group of charging stations 1505. ARC system 1500 may also identify available worker devices 1530 at a given charging station 1505 via user interface 1510 if the user is already at the given charging station 1505.
  • available worker devices 1530 e.g., and/or available storage housings
  • ARC system 1500 may provide data (e.g., via the exemplary disclosed API) directing a given user to a specific charging station 1505 or to one of a specified group of charging stations 1505.
  • ARC system 1500 may also identify available worker devices 1530 at a given charging station 1505 via user interface 1510 if the user is already at the given charging station 1505.
  • One or more device types of worker devices 1530 may be in use by employees at a given site cluster 1602 or location 1601.
  • a device type selection feature may allow an admin user of ARC system 1500 to configure one or more worker devices 1530 per organization (e.g., client) utilizing ARC system 1500.
  • a user e.g., employee
  • validates identity at step 1710 e.g., scans a badge or provides any other suitable validation for example as described above
  • a screen display showing available device types (e.g. iPhone 8 and Zebra C51) of worker devices 1530 may be provided to the user for example via the exemplary disclosed API and/or user interface 1510.
  • the user may select which type of worker device 1530 the user would like to have dispensed via charging station 1505.
  • ARC Client Portal 1610 may allow Admins (e.g., administrative users of ARC system 1500) the ability to specify which type of devices (e.g., worker devices 1530) each employee is allowed to use. Therefore, depending on identify validation at step 1710 (e.g., an employee badge scan or other suitable validation), an appropriate device or devices (e.g., worker devices 1530) may be displayed to the user.
  • Admins e.g., administrative users of ARC system 1500
  • identify validation at step 1710 e.g., an employee badge scan or other suitable validation
  • an appropriate device or devices e.g., worker devices 1530
  • ARC system 1500 may also employ role-based access at step 1725 to identify available devices.
  • each user may be assigned to various levels of device access based on the user’s working role such as position, role, rank, experience level, training level, and/or any other suitable criteria.
  • worker 1540 may be authorized to pick up and return a single type (e.g., or a reduced number of types) of worker device at charging station 1505.
  • a given worker 1540 may also be authorized to pick up and return two or more types of worker devices 1530.
  • Team leads 1540a may for example have access to a Manager’s Tools console of ARC system 1500 that may allow them to perform various types of troubleshooting including verifying users in the system, opening storage housings 1515, 1520, and 1525 that are empty, and/or other managerial tasks.
  • Managers 1540b may have the access granted to team leads 1540a as well as increased levels of access and authority to perform additional activities.
  • a full manager e.g., manager 1540b
  • manager 1540b may be able to perform functions of team leads 1540a along with additional functions such as opening storage housings 1515, 1520, and 1525 that include charging worker devices 1530, calibrating the touchscreen of user interface 1510, and/or any other suitable functions.
  • ARC system 1500 may also utilize updates based on client systems 1620 at step 1725 to identify available devices.
  • Worker devices 1530 that may be available to users may also be updated based on data transfer with client systems 1620 for example as described above (e.g., identification of worker devices 1530 that may be available may be updated based on updated data of ticketing and maintenance databases of client systems 1620). For example, worker devices 1530 that are to be repaired may be indicated as unavailable and not displayed as available to users.
  • Users may also indicate whether lower lockers or upper lockers are suitable for example as described above. For example, users may enter a preference for upper lockers or lower lockers via user interface 1510 and/or the exemplary disclosed API.
  • ARC system 1500 may update the identification of available devices at one or more charging stations 1505 based on whether lower lockers or upper lockers are specified by users.
  • the identification of available devices and/or storage housings at step 1725 may be based on (e.g., predicated on) identification of a presence or location of worker devices 1530 by ARC system 1500.
  • detection device 1542 and/or scanner 1535 of given charging stations 1505 may provide data to ARC system 1500 of a presence or absence of various types of worker devices 1530 disposed within charging stations 1505 (e.g., including in which storage housings 1515, 1520, and/or 1525 worker devices 1530 may be located).
  • Locations of worker devices 1530 may also be corroborated based on any other suitable data such as location data (e.g., provided by GPS sensors of worker devices 1530).
  • ARC system 1500 may update location and availability data of a fleet of worker devices 1530 based on processing data of detection devices 1542, scanners 1535, the exemplary disclosed location data, data from client systems 1620, data provided by users for example as described herein, and/or any other suitable data. For example, if an employee attempts to steal a worker device 1530 by entering data that the worker device 1530 was returned to charging station 1505, data of detection device 1542, scanner 1535, and/or the exemplary disclosed location data may alert ARC system 1500 that the worker device 1530 is missing (e.g., has been stolen).
  • ARC system 1500 may determine whether or not the identification of available devices at step 1725 should be further updated or modified. If ARC system 1500 determines that the identification of available devices at step 1725 should not be further updated or modified, process 1700 may proceed to step 1740 to dispense one or more worker devices 1530 to users (e.g., unlock doors of one or more select storage housings). If ARC system 1500 determines that the identification of available devices at step 1725 should be further updated or modified, process 1700 may proceed to step 1735.
  • ARC system 1500 may further update the identification of available devices (e.g., and/or available storage housings). Also for example, if users (e.g., workers 1540, team leads 1540a, and/or managers 1540b) and/or external systems 1620 provide additional data affecting availability, ARC system 1500 may update the identification of available devices and/or storage housings.
  • users e.g., workers 1540, team leads 1540a, and/or managers 1540b
  • external systems 1620 provide additional data affecting availability
  • ARC system 1500 may update the identification of available devices and/or storage housings.
  • ARC Client Portal 1610 may include a self-service website for client system administrators (e.g., user organizations of ARC system 1500) to maintain a roster of valid users to ARC system 1500 at each client location (e.g., location 1601 of the user organization).
  • the user roster may provide a method to maintain access control of the system by managing which users (e.g., workers 1540, team leads 1540a, and/or managers 1540b) may access ARC system 1500.
  • users e.g., workers 1540, team leads 1540a, and/or managers 1540b
  • ex-employee users may have their access revoked such that their access codes may be rejected when entered at step 1710.
  • ARC Client Portal 1610 may provide reporting (e.g., lifetime reporting) of employee transactions at charging stations 1505 associating a given user with a unique access code. Additionally for example, ARC Client Portal 1610 may be used to maintain a roster of devices in addition to the user roster. The device roster may allow for client system administrators to control which devices may be dispensed by charging stations 1505. The device roster may also provide reporting (e.g., life-time reporting) of worker devices 1530 and may provide a mechanism for reporting (e.g., via data transfer) when worker devices 1530 may be missing, out for repair, and/or permanently discarded and/or storage housings are to be checked and/or repaired. Also for example, ARC Client Portal 1610 may be used for system administrators to view and explore analytics and/or reporting of ARC system 1500 in a secure and constrained environment.
  • the identification of available devices may be updated based on actions taken based on indicators 1555 and data updates on which the operation of indicators 1555 is based.
  • an indicator 1555 indicates unsuitable operation of one or worker devices 1530 and/or charging stations 1505 (e.g., storage housings)
  • a software notification may be displayed on user interface 1510 and/or the exemplary disclosed API indicating that users should resolve a certain issue (e.g., repair of one or more worker devices 1530 or storage housings).
  • the notification could include text and/or a number message to inform how many issues are to be addressed and/or the severity of the one or more issues.
  • a message such as “Manager - 1” may indicate that there is 1 issue to be addressed by a manager (e.g., manager 1540b) and a “Team Lead - 3” could indicate that 3 issues are to be addressed by team leader 1540a.
  • the user e.g., worker 1540, team lead 1540a, and/or manager 1540b
  • may provide an update e.g., input data
  • ARC system 1500 which may be used to update available devices and/or storage housings (e.g., additional worker devices 1530 and/or storage housings may be displayed as available to users).
  • step 1735 data transfers (e.g., email notifications) may be sent in the event that a certain condition or conditions are triggered in ARC system 1500.
  • the condition or conditions may configured via ARC Client Portal 1610 and ARC Admin 1615.
  • an email notification may be sent to users of ARC system 1500 each time storage housings 1515, 1520, and/or 1525 are reported to have a technical issue by a user or sensor of ARC system 1500.
  • an email notification may be sent to a team lead 1540a or manager 1540b if an employee (e.g., users 1540) has a worker device 1540 that has been checked out for more than 24 hours or any other predetermined amount of time.
  • ARC system 1500 may also update the identification of available devices and/or storage housings at step 1735 (e.g., or any other desired step of process 1700) based on the data transfer (e.g., email notification).
  • charging station 1505 may dispense one or more devices (e.g., worker devices 1530) based on the identified available devices at steps 1725 and/or 1735 (e.g., by unlocking a door of a given storage housing).
  • charging station 1505 may dispense one or more devices (e.g., worker device 1530) based on a device type selected via input of the user.
  • charging station 1505 may dispense one or more devices (e.g., worker device 1530) based on one or more predetermined algorithms, criteria, and/or user input by unlocking doors of one or more corresponding storage housings (e.g., in which the devices are disposed).
  • charging station 1505 may dispense one or more devices (e.g., worker device 1530) based on a time duration that a device has been charging in the exemplary disclosed storage housing (e.g., locker). The time duration may begin using a timer that begins timing when a device (e.g., worker device 1530) is attached to the exemplary disclosed charging cable and a charge is detected.
  • Charging station 1505 may also dispense one or more devices (e.g., worker device 1530) based on an amount of energy the device has received from the exemplary disclosed charging port of a given storage housing, which may be determined by measuring a current drawn by the device over time.
  • Charging station 1505 may also dispense one or more devices (e.g., worker device 1530) based on a manual user override (e.g., in which an interface in manager tools allows the device to be dispensed immediately).
  • the manual user override may for example be initiated based on a supervisor (e.g., team lead 1540a or manager 1540b) or some other user having sufficient authority validating identity at step 1710.
  • the exemplary disclosed dispensing criteria may be configurable via the ARC Admin 1615 on a client-by-client basis (e.g., depending on a client organization using ARC system 1500), which may allow for appropriate criteria to be set to provide for adequately-charged devices (e.g., worker devices 1530) to be retrieved by users based on ARC system 1500 unlocking a door of a given storage housing in which the device is disposed.
  • adequately-charged devices e.g., worker devices 1530
  • step 1740 After worker device 1530 is dispensed at step 1740, the user may utilize the device to perform work as desired. When worker device 1530 is to be returned, for example at the end of a user’s shift or any other suitable time, process 1700 proceeds to step 1745.
  • the user e.g., worker 1540, team lead 1540a, or manager 1540b
  • ARC system 1500 may determine whether or not the user has requested to report an issue with worker device 1530 (e.g., and/or charging station 1505), for example based on the user entering input data to ARC system 1500. If the user has not indicated that an issue is to be reported, process 1700 proceeds to step 1760. If the user has indicated that an issue is to be reported, process 1700 proceeds to step 1755. [000132] At step 1755, the user (e.g., worker 1540, team lead 1540a, or manager 1540b) may report an issue.
  • worker device 1530 e.g., and/or charging station 1505
  • manager 1540b may report an issue.
  • a screen displayed by user interface 1510 or the exemplary disclosed API may prompt the user to report any issues the user has with one or more worker devices 1530 the user was utilizing, charging station 1505, and/or any other issues with ARC system 1500.
  • issue types e.g., any desired number of issue types
  • Examples of issue may include “WiFi Not Working,” “Screen Cracked,” “Device Won’t Turn On,” or any other suitable issue.
  • Each issue may be configured, when selected by a user, to trigger a different response by ARC system 1500.
  • a first given issue may put the exemplary disclosed storage housing (e.g., locker) out of service and notify a manager to handle the issue (e.g., via the exemplary disclosed email notification), a second given issue may put the storage housing out of service for a technician to handle, a third given issue may maintain the storage housing in service until the same issue is reported multiple times (e.g., in a row), a fourth given issue may put one or more worker devices 1530 out of service (e.g., not available), and/or any other suitable issues may be identified.
  • a first given issue may put the exemplary disclosed storage housing (e.g., locker) out of service and notify a manager to handle the issue (e.g., via the exemplary disclosed email notification)
  • a second given issue may put the storage housing out of service for a technician to handle
  • a third given issue may maintain the storage housing in service until the same issue is reported multiple times (e.g., in a row)
  • a fourth given issue may put one or more worker devices 1530
  • ARC system 1500 may perform diagnostic logic-driven checks based on collected data and issues reported by users. For example, ARC system 1500 may perform logic-driven checks based on data associated with storage housings 1515, 1520, and 1525 (e.g., based on data associated with a Eocker ID), worker devices 1530 (e.g., based on data associated with a Device ID), and users (e.g., based on data associated with a User ID). ARC system 1500 may prompt users to provide input and/or take actions based on the logic-driven checks. For example, if a user reports that a given worker device 1530 has insufficient charge (e.g., even after having charged for a suitable amount of time in charging station 1505), ARC system 1500 may store data of the report.
  • logic-driven checks based on data associated with storage housings 1515, 1520, and 1525 (e.g., based on data associated with a Eocker ID), worker devices 1530 (e.g., based on data associated with a Device ID
  • ARC system 1500 may take no action, put the affected worker device 1530 out of service to be checked by managers or technicians, put the involve storage housing (e.g., locker) out of service to be checked by managers or technicians, prompt the user to provide additional information, and/or take any other suitable action. If a similar report is given again, ARC system 1500 may identify whether the same worker device, storage housing, and/or user (e.g., reporting user or user who returned the device before the reporting user) is involved based on the Device ID, Locker ID, and User ID. If the same worker device is involved, ARC system 1500 may take the device out of service and indicate to managers and/or technicians that the device should be checked and possibly serviced (e.g., battery may be degraded).
  • storage housing e.g., locker
  • ARC system 1500 may identify whether the same worker device, storage housing, and/or user (e.g., reporting user or user who returned the device before the reporting user) is involved based on the Device ID, Locker ID, and User ID. If the same worker
  • ARC system 1500 may take the locker out of service and indicate to managers and/or technicians that the locker should be checked and possibly serviced (e.g., a problem may exist with the charging cable). If the same user is involved, ARC system 1500 may provide troubleshooting help or tips to the user regarding charging devices and/or reminders to the user to remember to return and recharge devices.
  • ARC system 1500 may determine a time period (e.g., based on user input via ARC Client Portal 1610) for how long a given storage housing (e.g., locker) may be out of service. For example based on user input (e.g., when a button is selected on the user interface or API), the storage housing may remain out of service for a predetermined period of time.
  • the role of the user who may be authorized to address a given issue e.g., manager, technician, or team lead
  • may be determined e.g., via ARC Client Portal 1610) such that certain roles may resolve certain out-of-service storage housings.
  • a pattern may be configured such that a storage housing remains in service when an issue is reported unless that issue has been repeatedly reported up to a predetermined threshold (e.g., based on an operation of ARC Client Portal 1610).
  • identification of available worker devices 1530 e.g., and/or available storage housings
  • process 1700 may return to step 1735 to update available devices and/or storage housings based on updates of step 1755.
  • ARC system 1500 may determine whether or not to cross-level worker devices 1530 between charging stations 1505, site clusters 1602, and/or locations 1601. If ARC system 1500 determines that worker devices 1530 should be cross-leveled, process 1700 proceeds to step 1765.
  • ARC system 1500 may determine that worker devices 1530 should be cross-leveled based on any suitable criteria and/or algorithm such as, for example, a differential in worker devices 1530 existing between charging stations 1505, a given charging station 1505 having less than a predetermined minimum number of worker devices 1530 or more than a predetermined maximum number of worker devices 1530, a first charging station having more or less worker devices than other charging stations, input provided by a user such as user request for additional worker devices 1530 at a given charging station 1505, and/or any other desired criteria. Also for example, ARC system 1500 may operate to ensure users pick up and return worker devices 1530 to the same (e.g., or different) charging station 1505, site cluster 1602, and/or location 1601.
  • any suitable criteria and/or algorithm such as, for example, a differential in worker devices 1530 existing between charging stations 1505, a given charging station 1505 having less than a predetermined minimum number of worker devices 1530 or more than a predetermined maximum number of worker devices 1530, a first charging station having more or less worker
  • ARC system 1500 may cross-level worker devices 1530 between charging stations 1505, site clusters 1602, and/or locations 1601 by channeling users into returning a given worker device 1530 to a desired charging station 1505, site cluster 1602, and/or location 1601 by instructing users to return worker device 1530 to a given charging station 1505, site cluster 1602, and/or location 1601 and/or by displaying an error message (e.g., via user interface 1510 and/or the exemplary disclosed API) if a user attempts to return worker device 1530 to an inappropriate charging station 1505, site cluster 1602, and/or location 1601.
  • an error message e.g., via user interface 1510 and/or the exemplary disclosed API
  • ARC system 1500 may also control one or more indicators 1555 to emit alert or warning lights and/or audio alarms if a user attempts to return worker device 1530 to an inappropriate charging station 1505, site cluster 1602, and/or location 1601.
  • Management personnel e.g., team lead 1540a and/or manager 1540b
  • ARC System 1500 may thereby operate to maintain a consistent stock of worker devices 1530 at any given charging station 1505, site cluster 1602, and/or location 1601. Desired cross-leveling may for example be configured via an operation of ARC Client Portal 1610 and/or ARC Admin 1615.
  • the exemplary disclosed system may block access of users (e.g., workers) to a full charging station 1505 station, which may not include an empty storage housing, when the worker is returning an in-use worker device of the plurality of worker devices.
  • users e.g., workers
  • the exemplary disclosed system may block access of users (e.g., workers) to an empty charging station 1505, which may lack an available storage housing including an available worker device of the plurality of worker devices, when the worker is retrieving the available worker device.
  • the exemplary disclosed system may block access to a full charging station 1505, which may not include an empty upper storage housing, when the worker is returning an in-use worker device of the plurality of worker devices and data of the worker indicates that the worker has input a preference for upper storage housings of the plurality of storage housings.
  • the exemplary disclosed system may also block access to a full charging station 1505, which may not include an empty lower storage housing, when the worker is returning an in-use worker device of the plurality of worker devices and data of the worker indicates that the worker has input a preference for lower storage housings of the plurality of storage housings.
  • the exemplary disclosed system may block access to an empty charging station 1505, which may lack an available upper storage housing including an available worker device of the plurality of worker devices, when the worker is retrieving the available worker device and data of the worker indicates that the worker has input a preference for upper storage housings of the plurality of storage housings.
  • the exemplary disclosed system may also block access to an empty charging station 1505, which may lack an available lower storage housing including an available worker device of the plurality of worker devices, when the worker is retrieving the available worker device and data of the worker indicates that the worker has input a preference for lower storage housings of the plurality of storage housings.
  • Detection device 1542 e.g., and/or scanner 1535 and/or the exemplary disclosed location data of worker device 1530
  • Process 1700 ends at step 1775.
  • an ongoing session of a user may be automatically ended based on that user’s device (e.g., worker device 1530) that was checked out by that user being returned to charging station 1505 by another user (e.g., any user).
  • a first employee checks out a device from charging station 1505 and then mistakenly leaves the device out (e.g., on a shelf).
  • a second employee finds the device and returns it to a charging station.
  • ARC system 1500 may end the first employee’s transaction and update the device status as returned.
  • ARC system 1500 may reject a badge scan (e.g., to remove additional devices) of a user if that user has already checked out a device or a predetermined number of devices.
  • a badge scan e.g., to remove additional devices
  • each user may have a predetermined number of devices (e.g., including type of device) that each user is authorized to remove, which may be recorded in ARC Admin 1615.
  • ARC system 1500 may prevent the user from engaging in additional transactions to remove devices until at least one device has been returned by that user.
  • ARC system 1500 may provide for creating a new session when a device to be retrieved is disposed in a locker that has been left open by a previous user.
  • a first user e.g., User A
  • a door e.g., a locker door
  • a second user e.g., User B
  • ARC system 1500 may prompt User B for feedback based on the door being closed (e.g., based on a discrepancy existing because the door should have been closed).
  • User B may report (enter input via user interface 1510 or the exemplary disclosed API) that User B is picking up a device.
  • ARC system 1500 may prompt User B to validate identity (e.g., scan User B’s Badge or any other suitable validation for example as described above regarding step 1710). After User B has validated identity, ARC system 1500 may reassign User A’s device to User B.
  • ARC system 1500 may end User A’s session and may begin a new checkout session for User B.
  • ARC system 1500 may provide for a manager (e.g., team lead 1540a or manager 1540b) to end a session.
  • the manager may end a given employee’s session (e.g., worker 1540) so that the given employee may check out a second device (e.g., or additional devices), thereby for example overriding a “one device per employee” functionality (e.g., or up to a predetermined number of devices per employee).
  • ARC system 1500 may provide warning messages (e.g., via user interface 1510 or the exemplary disclosed API) or alerts (e.g., via indicator 1555) when a user scans an Employee ID instead of a Device ID (e.g., or a Device ID instead of an Employee ID) during steps of process 1700.
  • warning messages e.g., via user interface 1510 or the exemplary disclosed API
  • alerts e.g., via indicator 1555
  • ARC system 1500 may differentiate between different types of scans by users, and may give users feedback onscreen (e.g., via user interface 1510 or the exemplary disclosed API) when the users may have scanned the wrong code.
  • ARC system 1500 may provide for a system rescan after a power outage. If power at a venue (e.g., one or more locations 1601) is lost and the charging stations 1505 go offline, managers (e.g., team leads 1540a and/or managers 1540b) may manually open storage housings (storage housings 1515, 1520, and/or 1525) to distribute worker devices 1530 and/or to return worker devices 1530 to continue work and operations.
  • a venue e.g., one or more locations 1601
  • managers e.g., team leads 1540a and/or managers 1540b
  • storage housings storage housings 1515, 1520, and/or 1525
  • ARC system 1500 may detect power loss such as a complete loss of power (e.g., loss of power at the wall and subsequent substantially complete draining of the exemplary disclosed Uninterruptible Power Supply “UPS” of each charging station 1505).
  • UPS Uninterruptible Power Supply
  • power may be lost at one or more charging stations 1505 (e.g., kiosks).
  • a worker 1540 e.g., Employee A
  • has a worker device 1530 e.g., Device 111) checked out for the worker’s shift.
  • the Manager e.g., team lead 1540a or manager 1540b
  • the Manager may assist Employee A by manually opening a locker and placing Device 111 in a storage housing (e.g., Locker #1).
  • ARC Server 1605 includes data indicating that there is no device in Locker #1.
  • the exemplary disclosed rescan e.g., SmartRescan
  • ARC system 1500 may detect a device (e.g., Device 111) in Locker #1.
  • ARC system 1500 may then change the status of Locker #1 from ‘Available’ to ‘Device Present- ID unknown’. This status prompts managers (e.g., the Manager) to take action the next time the Manager logs in to the Manager Tools Menu (e.g., following step 1710). Workflow screens (e.g., SmartRescan workflow screens displayed via user interface 1510 and/or the exemplary disclosed API) may prompt the Manager to open the locker, rescan the device, and close the locker door. The Device ID 111 then becomes known to charging station 1505 (e.g., and ARC system 1500), and assigned to Locker #1. Employee A’s return of the device is credited so that Employee A is able to check out devices on Employee A’s next shift.
  • charging station 1505 e.g., and ARC system 1500
  • ARC system 1500 may update an identification of available devices and lockers for example as described above in process 1700.
  • power may be lost at one or more charging stations 1505 (e.g., kiosks).
  • a worker 1540 e.g., Employee B
  • the Manager e.g., team lead 1540a or manager 1540b
  • the Manager may manually open an exemplary disclosed storage housing (e.g., Locker #5) and may give Employee B a device disposed in Locker #5.
  • Employee B’s Badge ID may be unknown (e.g., unknown to ARC system 1500 because step 1710 has not occurred). Power may be restored before Employee B finishes the employee’s shift.
  • Employee B may return to charging station 1505 (e.g., the kiosk), and perform identity validation (e.g., as described above regarding step 1710). For example, Employee B may scan the employee’s Badge ID, scan the Device ID (e.g., 222) of the device that was issued during the power outage, and place the device in Locker #7. Although ARC system 1500 had not received an update that Employee B had an ongoing transaction because of the power outage, ARC system 1500 may accept the return of the device. Accordingly, Employee B may be credited with the return and may be able to pick up a device on Employee B’s next shift. ARC system 1500 may record data indicating that Device 222 is now disposed in Locker #7. ARC system 1500 may update an identification of available devices and lockers for example as described above in process 1700.
  • identity validation e.g., as described above regarding step 1710
  • Employee B may scan the employee’s Badge ID, scan the Device ID (e.g., 222) of the device that was issued during the power outage,
  • ARC system 1500 may operate in an offline mode. Under normal conditions, ARC system 1500 may utilize connectivity between charging stations 1505 and ARC Server 1605 for data transfer. However, ARC system 1500 may operate resiliently when connectivity is lost so that operations are not interrupted. When one or more charging stations 1505 (e.g., ARC kiosks) at a given location 1601 lose connectivity, ARC system 1500 may automatically switch into an offline mode for some or all charging stations 1505 at one or more locations 1601 and/or site clusters 1602. During this time operating in the offline mode, offline charging stations 1505 may utilize local caching to record transaction events (e.g., removal and return of worker devices 1530).
  • transaction events e.g., removal and return of worker devices 1530.
  • ARC system 1500 may update statuses of devices and lockers. This may allow AC system 1500 to utilize an intelligent way of matching (e.g., or rematching) transactions so that reporting is up-to-date and accurate.
  • ARC system 1500 may also automatically initiate a locker- by-locker rescan (e.g., a rescan of each storage housing 1515, 1520, and 1525) for example as described above.
  • ARC system 1500 may record and store (e.g., capture) a significant amount of operational data during an operation of ARC system 1500, which may be analyzed (e.g., transformed) into meaningful reporting and analytics for various internal and external audiences. Machine learning operations may be used in analyzing the data.
  • the reporting and analytics may include for example analysis and reporting of life-time data about users and their interactions with kiosks, tracking and ranking levels of user compliance with kiosk procedures, analysis and reporting of life-time data about devices (e.g., worker devices 1530) dispensed by the kiosk including usage stats and device issues, analysis and reporting of operational data at charging station 1505 (e.g., the kiosk), site cluster 1602, location 1601, and brand level to monitor fleet health and performance metrics, and/or any other suitable analysis and reporting.
  • ARC system 1500 may provide visual and/or audio output to users (e.g., via user interface 1510 and/or the exemplary disclosed API). For example in addition to messaging on the exemplary disclosed touchscreens, ARC system 1500 may emit audio indicators at various points in the flow (e.g., flow of process 1700) to encourage proper user behavior (for example, emitting positive or encouraging audio sounds when successfully connecting a device to a charging cable of charging station 1505). These audio indicators may positively reinforce appropriate user activity at the kiosk. Similarly, ARC system 1500 may utilize audio indicators when ARC system 1500 detects an irregularity or unsuitable operation. The audio indicators may alert the user to rectify an issue or to provide diagnostic feedback.
  • managers and technicians maintain charging stations 1505 (e.g., the kiosks) in good working order, for example by resolving issues with storage housing 1515, 1520, and 1525 (e.g., lockers) that may have an Out of Service status recorded by ARC system 1500.
  • ARC System 1500 may use predefined workflows in various “Tools Menus” (e.g., Manager Tools accessed by managers and Tech Tools accessed by technicians) to address locker issues in a logical and orderly manner (e.g., as part of process 1700).
  • the workflows may provide for the lockers to be appropriately addressed according to operational procedures, with issues being suitably resolved or escalated.
  • the exemplary disclosed system may be a system for charging a plurality of worker devices for use by a plurality of users, comprising one or more charging stations, each charging station including a plurality of storage housings, one or more detection devices, and an identification device, and a controller.
  • the controller may be configured to selectively lock and unlock the plurality of worker devices in the plurality of storage housings of the one or more charging stations, electrically charge the plurality of worker devices when locked in the plurality of storage housings of the one or more charging stations, and validate an identity of the plurality of users with the identification device of the one or more charging stations when the plurality of users removes or returns the plurality of worker devices to the plurality of storage housings of the one or more charging stations.
  • the controller may also be configured to detect a presence of the plurality of worker devices in the plurality of storage housings using the one or more detection devices of the one or more charging stations, update data of the plurality of worker devices or the plurality of storage housings based on data transferred from the identification device and the one or more detection devices of the one or more charging stations, and identify available worker devices of the plurality of worker devices or available storage housings of the plurality of storage housings to the plurality of users based on the data of the plurality of worker devices or the plurality of storage housings.
  • Each of the plurality of storage housings of the one or more charging stations may include a plurality of light indicators configured to indicate whether or not the available worker devices are disposed in each of the plurality of storage housings of the one or more charging stations.
  • Each of the plurality of storage housings of the one or more charging stations includes a plurality of upper lockers and a plurality of lower lockers
  • the controller may be configured to identify the available worker devices based on whether the plurality of users specify the plurality of upper lockers or the plurality of lower lockers.
  • the exemplary disclosed method may include providing a plurality of worker devices for use by a plurality of users, providing one or more charging stations, each charging station including a plurality of storage housings, selectively locking and unlocking the plurality of worker devices in the plurality of storage housings of the one or more charging stations, and electrically charging the plurality of worker devices when locked in the plurality of storage housings of the one or more charging stations.
  • the exemplary disclosed method may also include validating an identity of the plurality of users when the plurality of users removes or returns the plurality of worker devices to the plurality of storage housings of the one or more charging stations, detecting a presence of the plurality of worker devices in the plurality of storage housings of the one or more charging stations, updating data of the plurality of worker devices or the plurality of storage housings based on data transferred from the one or more charging stations, and identifying available worker devices of the plurality of worker devices or available storage housings of the plurality of storage housings to the plurality of users based on the data of the plurality of worker devices or the plurality of storage housings.
  • Each charging station may include one or more detection devices and an identification device, validating the identity of the plurality of users includes using the identification device of the one or more charging stations, and detecting the presence of the plurality of worker devices in the plurality of storage housings includes using the one or more detection devices of the one or more charging stations.
  • the exemplary disclosed method may further include indicating some of the available worker devices or the available storage housings as unavailable based on the plurality of users reporting multiple errors involving at least one of a single worker device of the plurality of worker devices, a single storage housing of the plurality of storage housings, or a single user of the plurality of users.
  • the plurality of users may be a plurality of workers working at a location including the one or more charging stations that are grouped into a plurality of site clusters at the location, the plurality of worker devices being removed from and returned to the one or more charging stations by the plurality of workers during working hours of the plurality of workers at the location.
  • the exemplary disclosed method may also include directing a worker of the plurality of users to return a first device of the plurality of worker devices to a second station of the one or more charging stations that is different from a first station of the one or more charging stations from which the worker removed the first device.
  • the exemplary disclosed method may further include blocking access of a worker of the plurality of users to at least one of a full station of the one or more charging stations, which does not include an empty storage housing, when the worker is returning an in-use worker device of the plurality of worker devices, or an empty station of the one or more charging stations, which lacks an available storage housing including an available worker device of the plurality of worker devices, when the worker is retrieving the available worker device.
  • the exemplary disclosed method may also include blocking access of a worker of the plurality of users to at least one of: a full station of the one or more charging stations, which does not include an empty upper storage housing, when the worker is returning an in-use worker device of the plurality of worker devices and data of the worker indicates that the worker has input a preference for upper storage housings of the plurality of storage housings, a full station of the one or more charging stations, which does not include an empty lower storage housing, when the worker is returning an in-use worker device of the plurality of worker devices and data of the worker indicates that the worker has input a preference for lower storage housings of the plurality of storage housings, an empty station of the one or more charging stations, which lacks an available upper storage housing including an available worker device of the plurality of worker devices, when the worker is retrieving the available worker device and data of the worker indicates that the worker has input a preference for upper storage housings of the plurality of storage housings, or an empty station of the one or more charging stations, which lacks an available lower storage housing including an
  • Instructing the worker to return the first device to the second station may be based on a first amount of the plurality of worker devices locked in the first station being greater than a first predetermined amount, a second amount of the plurality of worker devices locked in the second station being less than a second predetermined amount, or the first amount being greater than the second amount.
  • the exemplary disclosed method may further include detecting the presence or absence of the plurality of worker devices in all of the plurality of storage housings using the one or more detection devices of the one or more charging stations when power is restored to the one or more charging stations following a power outage.
  • the exemplary disclosed method may further include locally caching data of the presence or absence of the plurality of worker devices in the plurality of storage housings at a first station of the one or more charging stations when the first station is in an offline mode and not connected to a network, and transferring the locally cached data from the first station to the network when connectivity is restored between the first station and the network.
  • the exemplary disclosed method may also include updating the data of the plurality of worker devices or the plurality of storage housings and identifying the available worker devices or the available storage housings based on receiving data of the plurality of users or the plurality of worker devices from an external database.
  • the exemplary disclosed method may further include unlocking a door of a first housing of the plurality of storage housings based on at least one selected from the group of a time duration that a first device of the plurality of worker devices has been charging in the first housing, an amount of energy that the first device has received from a charging port of the first housing, an amount of charge available to the first device, an amount of use time available to the first device, and combinations thereof.
  • the exemplary disclosed method may also include unlocking a door of a first housing of the plurality of storage housings of some or all of the one or more charging stations based on one or more users having a greater level of access than workers of the plurality of users entering input data to a user interface of the first station.
  • Validating the identity of the plurality of users may include displaying a plurality of screens to a first-time user of the plurality of users when the first-time user scans identification for the first time at the identification device of one of the one or more charging stations, the screens selected from the group of one or more onboarding screens, one or more instructional screens, one or more opt-in screens for terms of use, one or more preference setting screens, and combinations thereof.
  • the exemplary disclosed method may further include receiving input at a user interface of one of the one or more charging stations by a manager of a first-time user of the plurality of users, the input including at least one of updating the data of the plurality of worker devices or the plurality of storage housings with access for the first-time user to remove a device of the plurality of worker devices, or activating a first-time device of the plurality of worker devices, the first-time device activation being input for the first time.
  • the data of the plurality of worker devices or the plurality of storage housings may include an amount and a type of the plurality of worker devices that each of the plurality of users is authorized to use and which of the plurality of storage housings that each of the plurality of users is authorized to unlock based on a working role of each of the plurality of users.
  • the exemplary disclosed method may include providing a plurality of worker devices for use by a plurality of users, providing one or more charging stations, each charging station including a plurality of storage housings, one or more detection devices, and an identification device, selectively locking and unlocking the plurality of worker devices in the plurality of storage housings of the one or more charging stations, and electrically charging the plurality of worker devices when locked in the plurality of storage housings of the one or more charging stations.
  • the exemplary disclosed method may further include validating an identity of the plurality of users with the identification device of the one or more charging stations when the plurality of users removes or returns the plurality of worker devices to the plurality of storage housings of the one or more charging stations, detecting a presence of the plurality of worker devices in the plurality of storage housings using the one or more detection devices of the one or more charging stations, updating data of the plurality of worker devices or the plurality of storage housings based on data transferred from the identification device and the one or more detection devices of the one or more charging stations, and identifying available worker devices of the plurality of worker devices or available storage housings of the plurality of storage housings to the plurality of users based on the data of the plurality of worker devices or the plurality of storage housings.
  • the exemplary disclosed method may also include instructing a worker of the plurality of users to return a first device of the plurality of worker devices to a second site cluster of the one or more charging stations that is different from a first site cluster of the one or more charging stations from which the worker removed the first device, wherein the plurality of users is a plurality of workers working at a location including the one or more charging stations that are grouped into the first site cluster and the second site cluster that is located away from the first site cluster or that accepts different types of the plurality of worker devices than the first site cluster.
  • the exemplary disclosed method may further include blocking access of a worker of the plurality of users to at least one of a full station of the one or more charging stations, which does not include an empty storage housing, when the worker is returning an in-use worker device of the plurality of worker devices, or an empty station of the one or more charging stations, which lacks an available storage housing including an available worker device of the plurality of worker devices, when the worker is retrieving the available worker device.

Landscapes

  • Engineering & Computer Science (AREA)
  • Power Engineering (AREA)
  • Charge And Discharge Circuits For Batteries Or The Like (AREA)

Abstract

Est divulgué ici un système pour charger une pluralité de dispositifs de travailleurs destinés à être utilisés par plusieurs utilisateurs. Le système comprend une ou plusieurs stations de charge, chaque station de charge comprenant une pluralité de boîtiers de rangement, un ou plusieurs dispositifs de détection et un dispositif d'identification et un dispositif de commande. Le dispositif de commande est configuré pour verrouiller et déverrouiller sélectivement la pluralité de dispositifs de travailleurs dans la pluralité de boîtiers de rangement de la station ou des stations de charge, charger électriquement la pluralité de dispositifs de travailleurs lorsqu'ils sont verrouillés dans la pluralité de boîtiers de rangement de la station ou des stations de charge, et valider une identité de la pluralité d'utilisateurs avec le dispositif d'identification de la station ou des stations de charge lorsque la pluralité d'utilisateurs retirent la pluralité de dispositifs de travailleurs de la pluralité de boîtiers de rangement de la station ou des stations de charge, ou les replacent dans ceux-ci.
PCT/US2023/062840 2022-02-18 2023-02-17 Système et procédé pour fournir des stations de charge de dispositifs mobiles interconnectées et sécurisées WO2023159194A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US17/675,136 US20220181887A1 (en) 2012-12-03 2022-02-18 System and method for providing interconnected and secure mobile device charging stations
US17/675,136 2022-02-18

Publications (2)

Publication Number Publication Date
WO2023159194A2 true WO2023159194A2 (fr) 2023-08-24
WO2023159194A3 WO2023159194A3 (fr) 2023-10-19

Family

ID=87578984

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2023/062840 WO2023159194A2 (fr) 2022-02-18 2023-02-17 Système et procédé pour fournir des stations de charge de dispositifs mobiles interconnectées et sécurisées

Country Status (1)

Country Link
WO (1) WO2023159194A2 (fr)

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9348381B2 (en) * 2011-10-19 2016-05-24 Zeco Systems Pte Ltd Methods and apparatuses for charging of electric vehicles
ZA201205645B (en) * 2012-03-23 2013-04-24 Econet Wireless Ip Holdings Ltd A charging station for mobile electronic device and an associated system and method
US10678302B1 (en) * 2015-09-29 2020-06-09 Tech Friends, Inc. Secure charging system for electronic devices

Also Published As

Publication number Publication date
WO2023159194A3 (fr) 2023-10-19

Similar Documents

Publication Publication Date Title
US20220181887A1 (en) System and method for providing interconnected and secure mobile device charging stations
US11258282B2 (en) System and method for providing interconnected and secure mobile device charging stations
US11244523B1 (en) Managing access to secure indoor spaces
US20160019495A1 (en) System and method for context-sensitive delivery notification
US7932824B2 (en) Item tracking system
CN103875000B (zh) 用于自主移动机器人的监测、诊断和跟踪工具
US11031790B2 (en) System and method for providing interconnected and secure mobile device charging stations
US20160266733A1 (en) Event and staff management systems and methods
CN102165460A (zh) 用于生成密码的数据包发生器
US20150119069A1 (en) System, Method and Apparatus for Device Management and Tracking
CN106570641A (zh) 一种基于万物互联的智慧酒店管理系统
CN105190669A (zh) 用于移动销售点过程管理的系统和方法
US9396447B2 (en) Systems and methods for monitoring a headcount
US20210265843A1 (en) System and method for providing interconnected and secure mobile device charging stations
CN103810545A (zh) 一种物联网智能图书馆方法与装置
US20200258035A1 (en) Locker management system
CN108910381A (zh) 一种物品输送设备和物品输送的方法
US11995581B2 (en) Method of providing client service
US9984518B2 (en) Access monitoring system for remote locations
KR100683580B1 (ko) 지능형 플랜트 정보시스템
US9082099B1 (en) System and method for context-sensitive delivery notification
WO2020066425A1 (fr) Boîte de livraison à domicile, système de livraison à domicile, terminal portatif, procédé de communication et procédé de traitement d'informations
WO2023159194A2 (fr) Système et procédé pour fournir des stations de charge de dispositifs mobiles interconnectées et sécurisées
US20210279991A1 (en) Advanced access control using biometric data
US20220293281A1 (en) Multi-source health-based safety information aggregation in a graphical user interface

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23757129

Country of ref document: EP

Kind code of ref document: A2