Industrial device access control

Abstract

A mobile processing device is paired with an industrial device by reading a marker associated with the industrial device and extracting an electronic identifier of the industrial device from the marker. An authorization request is transmitted to a remote server to request authorization to operate the industrial device, where the authorization request includes the electronic identifier of the industrial device and an identifier of an operator expected to operate the industrial device. In response to the authorization request, an access response is received from the remote server. In response to the access response allowing the operator to access the industrial device, the process extracts pairing information and utilizes the extracted pairing information to pair the mobile processing device with a short-range transceiver of the industrial device. Upon successful pairing of the mobile processing device and the industrial device, the industrial device is enabled for normal operation.

Description

Technical Field

[0001] Various aspects of this disclosure generally relate to combining wireless communication technologies to link portable wireless processing devices (e.g., smartphones) to industrial equipment (e.g., industrial vehicles). Background Technology

[0002] Industrial vehicles are commonly used to move goods in industrial environments. Such vehicles typically include a power unit and a load handling assembly, which may include forks for carrying goods. The vehicle also has control structures for controlling its operation and movement. In some implementations, industrial vehicles are equipped with communication devices that link the vehicle to a remote server management system. These communication devices may include touchscreens or other interfaces to link the equipment operator to the management system. However, not all industrial vehicles have such communication devices, which makes managing such vehicles difficult. Summary of the Invention

[0003] According to various aspects of this disclosure, a process for pairing a mobile processing device with industrial equipment is provided. The process includes: reading a tag associated with the industrial equipment to be used by an operator by hardware on the mobile processing device (e.g., a smartphone). For example, the tag can be read by accessing a reader (e.g., a camera or scanning device) on the mobile processing device to electronically exchange information with the industrial vehicle (e.g., capturing images, barcodes, QR codes, etc.).

[0004] The process also includes: extracting the electronic identifier of the industrial equipment from the tag, and transmitting an authorization request from the mobile processing device to a remote server to request authorization to operate the industrial equipment. Here, the authorization request includes the electronic identifier of the industrial equipment and the identifier of the operator who wishes to operate the industrial equipment. The process also includes: receiving an access response from the remote server in response to the authorization request. The access response can grant or deny access to the industrial equipment.

[0005] In some embodiments, in response to an access response allowing an operator to access the industrial equipment, the process further includes: extracting pairing information from the access response by the mobile processing device, and pairing the mobile processing device with a short-range transceiver of the industrial equipment using the extracted pairing information. After successful pairing of the mobile processing device and the industrial equipment, the industrial equipment is enabled for normal operation. Alternatively, the mobile processing device can be paired with the industrial equipment using a Bluetooth pairing procedure based on the extracted pairing information.

[0006] Furthermore, in some embodiments, in response to an access response allowing an operator to access the industrial equipment, the process may also perform the following operations: setting the mobile device to a paired state, setting the industrial equipment to a paired state, graphically displaying a pairing acceptance icon on a selected one of the mobile device or the industrial equipment, and pairing the mobile processing device with the industrial equipment when the pairing acceptance icon is detected to be activated. Here, after the mobile processing device and the industrial equipment are successfully paired, the industrial equipment is enabled for normal operation.

[0007] Optionally, in response to an access response that allows the operator to access the industrial equipment, the process may further include automatically pairing the mobile device with the industrial equipment by a remote server.

[0008] Furthermore, in some embodiments, the process can trigger an indicator on the industrial equipment upon at least one of a pairing attempt, successful pairing, unsuccessful pairing, or any combination thereof. As several examples, the indicator may include at least one of light control, a message on a display, sound, haptic feedback, movement on the industrial equipment, or a combination thereof.

[0009] In some embodiments, reading a tag associated with industrial equipment by hardware on the mobile processing device may include accessing a reader on the mobile processing device to obtain information related to the industrial equipment. Furthermore, in some embodiments, accessing a reader on the mobile processing device to obtain information related to the industrial equipment may include accessing a camera on the mobile processing device to capture an image associated with the industrial equipment. Optionally, accessing a reader on the mobile processing device to obtain information related to the industrial equipment may include scanning at least one of a barcode or a QR code with a camera.

[0010] Furthermore, the process may optionally include: the mobile processing device receiving login credentials from the operator, which enable the operator to be authenticated as a valid operator by the remote server before reading the tag associated with the industrial equipment the operator intends to use. Additionally, the process may further include: software code running on the mobile processing device requiring the operator to be authenticated as a valid operator before the mobile processing device performs the operation of transmitting an authorization request from the mobile processing device to the remote server. As another example, the process may further include: the remote server requiring the operator's identifier to be authenticated as a valid operator before returning an access response to the mobile processing device.

[0011] In some embodiments, in response to an access response that allows an operator to access industrial equipment, the process further includes: granting access to the operator if the operator has a current certificate or credentials for appropriate training that is accessible to the remote server, prior to the operator being able to use the industrial equipment.

[0012] In some embodiments, transmitting an authorization request further includes transmitting information about the time block in which the industrial equipment is requested. It may also include having a remote server verify that the industrial equipment is available for the entire time block requested by the authorization request before authorizing its use. For example, verifying that the industrial equipment is available for the entire time block requested by the remote server may include rejecting the authorization request if the requested industrial equipment has already been reserved for an activity within the requested time block, the activity including at least one of the following: reserved by another user, locked for planned maintenance, or scheduled for battery maintenance.

[0013] In some embodiments, the access response includes denying access, and the process may further include: in response to denying access, outputting a message indicating that access is not permitted on the display screen of the mobile processing device.

[0014] In addition, in some embodiments, the industrial equipment is disabled before the mobile processing device is successfully paired with the industrial equipment.

[0015] According to another aspect of this disclosure, a process for pairing a mobile processing device with industrial equipment is provided. The process includes: launching a device interface application within the operating system of the mobile processing device. The device interface application performs the following operations: using hardware on the mobile processing device, an authorized component of the device interface application reads a tag associated with the industrial equipment to be used by the operator. The device interface application further performs: extracting the electronic identifier of the industrial equipment from the tag.

[0016] The device interface application also transmits an authorization request from the mobile processing device to a remote server to request authorization to operate the industrial equipment. This authorization request includes the electronic identifier of the industrial equipment and the identifier of the operator who wishes to operate the industrial equipment. The process also includes receiving an access response from the remote server in response to the authorization request. In response to the access response granting the operator permission to use the industrial equipment, the process further includes: the mobile processing device extracting pairing information from the access response and pairing the mobile processing device with the industrial equipment using the extracted pairing information. After successful pairing of the mobile processing device and the industrial equipment, the industrial equipment is activated for normal operation.

[0017] For example, the use of hardware on a mobile processing device to read a tag by an authorized component may include accessing a reader on the mobile processing device to electronically exchange information with industrial equipment, such as by accessing a camera on the mobile processing device to capture images (e.g., at least one of barcodes, QR codes, etc.) on the industrial equipment.

[0018] In some embodiments, the process may further include: the mobile processing device receiving login credentials from the operator, which enable the operator to log in to a remote server, wherein the operator must be authenticated as a valid operator at the remote server before reading the tag associated with the industrial equipment to be used by the operator. The process may further include: software code running on the mobile processing device requiring the operator to be authenticated as a valid operator before the mobile processing device performs the operation of transmitting an authorization request from the mobile processing device to the remote server. The process may further include: the remote server requiring the operator's identifier to be authenticated as a valid operator before returning the authorization request to the mobile processing device.

[0019] In some embodiments, in response to an access response that allows an operator to access the industrial equipment, the process may further include: granting access to the operator if the operator has a current certificate or credentials for appropriate training that is accessible to the remote server, prior to the operator being able to use the industrial equipment.

[0020] In some embodiments, transmitting the authorization request may further include transmitting a time block requesting the use of the industrial equipment. Here, the process may further include: verifying by a remote server that the industrial equipment is available throughout the entire time block requested by the authorization request before authorizing its use. For example, verifying by the remote server that the industrial equipment is available throughout the entire time block requested by the authorization request may include: rejecting the authorization request if the requested industrial equipment has already been reserved for an activity during the requested time block, the activity including at least one of the following: reserved by another user, locked for planned maintenance, or scheduled for battery maintenance.

[0021] In some embodiments, receiving an access response from a remote server in response to an authorization request may include receiving an access denied response. Here, the process may further include: in response to the access denied response, displaying a message indicating that access is not permitted on the screen of the mobile processing device.

[0022] Furthermore, in some embodiments, the industrial equipment is initially disabled until the mobile processing device is successfully paired with it. Here, in response to an access response that allows the mobile processing device to access the industrial equipment, the authorization component extracts pairing information for pairing the mobile processing device with the industrial equipment; and in response to an access response that disallows the operator from accessing the industrial equipment, it outputs a message to the mobile processing device indicating that access is not permitted. Attached Figure Description

[0023] Figure 1 This is a schematic diagram of the operating environment of an industrial vehicle; Figure 2This is a schematic diagram of an industrial equipment control system that implements serial, multimodal access control. Figure 3 This is a schematic diagram of serial, multimodal exchange between the operator and industrial equipment; Figure 4 This is an example graphical user interface illustrating sample graphics for logging into industrial equipment, based on various aspects of this document; Figure 5 It is a flowchart illustrating the process for performing serial, multimodal access control; and Figure 6 This is a block diagram of a computer system having a computer-readable storage medium for implementing the functions of various embodiments described in detail herein.

[0024] In the following detailed description of the illustrated embodiments, reference is made to the accompanying drawings, which form a part of the description, and specific embodiments in which the present disclosure may be practiced are shown in the drawings by way of illustration and not limitation. It should be understood that other embodiments may be utilized and modifications may be made without departing from the spirit and scope of the various embodiments of the present disclosure. Detailed Implementation

[0025] In many industrial environments, Wi-Fi, cellular, and other similar long-range wireless communication strategies are not practical for certain industrial equipment. In these cases, industrial equipment cannot communicate directly with remote server computers, for example, for data monitoring, data collection, data reception, and operations management.

[0026] However, equipping such industrial equipment with short-range wireless capabilities may be practical. In this specification, "short-range" and "local" wireless capabilities are used interchangeably.

[0027] As used herein, a "short-range" or "local" transceiver (and therefore short-range wireless communication) is defined as a transceiver or communication protocol that does not use Wi-Fi or cellular. Examples of "short-range" or "local" transceivers, as used herein, include Bluetooth, ultra-wideband, IR (infrared), radio frequency for radio frequency identification (RFID), etc. In this regard, some applications may allow a typical range of up to 30 feet (about 10 meters), for example, using Bluetooth. Ultra-wideband can extend to 80 feet (about 25 meters). However, in some embodiments, it may be necessary to reduce the appropriate short-range range to line-of-sight, or otherwise to close range (e.g., 10 feet (about 3 meters) or less).

[0028] As used in this article, a "long-range" transceiver (and therefore long-range wireless communication) is defined as a transceiver or communication protocol that uses Wi-Fi or cellular communication.

[0029] For example, “long-range” communication using Wi-Fi and / or cellular communication technologies can typically extend to more than 100 feet (about 30.5 meters), while “short-range” or “local” communication can typically extend to less than 100 feet (about 30.5 meters).

[0030] System Overview Now refer to the attached diagram, especially Figure 1 The illustration schematically depicts an industrial environment 100, which includes multiple hardware-equipped processing units 102 linked together via one or more networks 104.

[0031] Network 104 provides communication links between the various processing devices 102 and can be supported by network components 106 interconnecting the processing devices 102, including, for example, routers, hubs, firewalls, network interfaces, wired or wireless communication links and corresponding interconnections, cellular stations and corresponding cellular conversion technologies (e.g., conversion between cellular and TCP / IP, etc.). Furthermore, network 104 may include intranets, extranets, local area networks (LANs), wide area networks (WANs), wireless networks (Wi-Fi), the Internet (including the World Wide Web), ad hoc networks, localized networks, mesh networks (e.g., between two or more processing devices 102), cellular and / or other arrangements for enabling communication between the processing devices 102, etc.

[0032] The processing device 102 can be implemented as a server, personal computer, laptop computer, tablet computer, special equipment, Internet of Things (IoT) device, special purpose computing device, cellular device (such as smartphone), information processing device in vehicle, information processing device in machine (fixed or mobile), or other device capable of communicating via network 104.

[0033] Specifically, the processing device 102 may be mounted on one or more industrial vehicles 108, such as forklifts as shown. In practice, industrial vehicles may include, for example, low-level picking vehicles, forklifts, reach trucks, narrow aisle forklifts, stacker cranes, pallet trucks, tractors, picking vehicles, etc. In this regard, industrial vehicles may include liftable forks. In other example embodiments, industrial vehicles may include tractors with tow hooks or other coupling structures for pushing and / or pulling loads.

[0034] In an industrial environment, industrial vehicles can be equipped with a processing unit 102 capable of communicating across network 104. In this respect, an industrial vehicle equipped with a processing unit 102 is referred to as a "network-connected industrial vehicle".

[0035] In this example configuration, the processing unit 102 on the industrial vehicle 108 communicates wirelessly to one or more access points 110 via one or more technologies (e.g., via Wi-Fi). The access points 110 are connected to a corresponding network component 106, which acts as a connection within the industrial environment 100. As another example, the industrial vehicle 108 may be equipped with cellular or other suitable wireless technologies, allowing the processing unit 102 on the industrial vehicle 108 to communicate directly with remote devices (e.g., via network 104), for example, by using a suitable cellular-to-Internet bridge.

[0036] Industrial environment 100 also includes processing means implemented as server 112 (e.g., web server, file server, and / or other processing means), which supports platform 114 and corresponding data sources (collectively referred to as data source 116). In an example embodiment, platform 114 may be used to implement information-linked applications, as described more fully herein. For example, industrial vehicle 108 typically operates in work environments such as warehouses, distribution centers, and retail stores. Therefore, platform 114 provides industrial vehicle monitoring, management, control, or a combination thereof through information-linked applications.

[0037] In the illustrative example, data source 116 (no need for co-location) includes a database that links processes performed for the benefit of the enterprise from multiple different domains. In the illustrated example, data source 116 includes industrial equipment data source 118, which collects data from the operation of industrial equipment, such as industrial vehicles 108, for example, in the industrial vehicle domain. For example, an industrial vehicle information database may store electronic vehicle records wirelessly received from a fleet of industrial vehicles. In this respect, each electronic vehicle record may include driving-related data, operational data, maintenance data, observation data, configuration data, component status data, measured sensor data, impact data, or other information recorded by the processing unit 102 on the associated industrial vehicle 108. Each electronic vehicle record may also include the operator identifier of the corresponding operator of the industrial vehicle.

[0038] Data source 116 may also include management system data source 120, such as a warehouse management system (WMS). The WMS associates information on the movement and tracking of goods within the work environment within the WMS domain. Therefore, in some embodiments, WMS data (alone or in combination with data from one or more other data sources, such as industrial equipment data source 118) can be used to select, define, refine, and otherwise influence the operation of technical features, such as thresholds or threshold ranges characterizing remotely controlled travel distances within the work environment, and other examples that will be described in more detail herein.

[0039] In addition, data source 116 may include any other data source 122 required by the work environment, such as a workforce management system (LMS). In some embodiments, the system may also include data sources such as a geolocation system 124, which stores information about geographic features, geographic capabilities, and / or restrictions imposed on industrial vehicles in the environment (e.g., by technical characteristics or other means). Geolocation data may also include data related to location within the environment, such as through an environment-based location tracking system. The above list is not exhaustive and is merely illustrative.

[0040] In some embodiments, an industrial device 126 does not include a processing unit 102 capable of communicating via a network 104, for example, not via Wi-Fi or cellular communication. Here, the industrial device 126 may exemplary include industrial vehicles, including any of the aforementioned industrial vehicles 108, material handling equipment such as pallet trucks, electric pallet trucks, work assistance vehicles, tractors, mobile devices or machines, stationary devices or machines, etc. In this respect, the industrial device is referred to as a "non-networked" industrial device.

[0041] There are many reasons why an industrial device 126 may not include a processing unit 102 capable of communicating via a network connection (e.g., via a Wi-Fi wireless transceiver or a cellular transceiver). For example, the cost may be too high, the industrial device 126 may operate outside the range of Wi-Fi or cellular access, the industrial device 126 may operate in harsh environments that exclude the presence of the processing unit 102, the industrial device may be leased equipment, etc.

[0042] In this respect, industrial equipment 126 is typically isolated from communication with remote server 112 and the corresponding platform 114. However, there may be a need and / or requirement to link industrial equipment 126 to information linking applications on platform 114, such as for operator login applications, checklist applications, data collection or data monitoring applications, for maintenance reasons, etc.

[0043] In some embodiments, industrial equipment 126 may include processing means 102 capable of communicating via network 104 (e.g., using Wi-Fi or cellular), but for some reason, it may be desirable to simplify or restrict access to remote server 112 and corresponding platform 114. For example, industrial equipment 126 may be used by visiting or temporary workers, industrial equipment 126 may be in a data-restricted or bandwidth-restricted environment, industrial equipment 126 may be in an environment with security restrictions, etc.

[0044] However, in some embodiments, industrial device 126 includes or may be equipped with a communication and control system 128, which may include transceivers, such as short-range transceivers like Bluetooth transceivers, ultra-wideband transceivers, infrared transceivers, RFID transceivers, etc. In this respect, industrial device 126 can communicate over short ranges, such as... Figure 1 The circles and arrows in the diagram are shown schematically.

[0045] Furthermore, even the industrial vehicle 108 equipped with the processing unit 102 may include a short-range transceiver, such as a Bluetooth transceiver, an ultra-wideband transceiver, an infrared transceiver, an RFID transceiver, etc. In this respect, the aspects herein are not strictly limited to industrial equipment that does not have cellular or Wi-Fi capabilities.

[0046] Example communication and control system Now for reference Figure 2 The illustration shows an example communication and control system 228. Figure 2 In, with Figure 1 Similar structures are represented using the same reference numerals that are 100 higher. Therefore, Figure 1 The discussion was adopted. Figure 2 In the description.

[0047] For example, as shown in the figure, processing device 202 (e.g., a smartphone) can communicate with remote server 212 across network 204 (similar to processing device 102 communicating with remote server 112 across network 104). Figure 1 Similarly, the example communication and control system 228 can be used to implement... Figure 1 The communication and control system 128. Therefore, the example communication and control system 228 can be set up... Figure 1 On industrial equipment 128.

[0048] The illustrated communication and control system 228 generally includes a controller 230. The communication and control system 228 may also include one or more additional components, described more fully herein. For example, the communication and control system 228 may also include one or more transceivers. Exemplarily, the controller 230 is communicatively coupled to at least one short-range wireless transceiver 232.

[0049] controller In the example embodiment, controller 230 includes a processor, memory, and necessary circuitry to interface with any provided additional components, such as transceivers like the short-range wireless transceiver 232 in the example embodiment. Furthermore, controller 230 may be operatively configured to communicate with at least one vehicle component. Example vehicle components include native vehicle controllers (e.g., traction controllers, hydraulic controllers, vehicle control modules, etc.). Another example vehicle component includes one or more sensors, power systems, power-enabled relays, or systems (e.g., for controlling, powering on, or otherwise enabling industrial equipment for normal operation). For example, by way of illustration and not limitation, controller 230 may be communicatively coupled to native components, such as native device electronics 234, for example, via industrial device bus 236. In other applications, controller 230 may directly interface with components, such as via wired or wireless connections.

[0050] In some embodiments, the controller 230 is implemented as permanently or semi-permanently mounted to industrial equipment (e.g., a material handling vehicle) (see example...). Figure 1 An embedded system of industrial equipment 126. That is, in some embodiments, the embedded information core represents hardware and optional software designed to maintain coupling to the corresponding industrial equipment (e.g., pallet trucks, electric pallet trucks, work assistance vehicles, tractors, low-level picking vehicles, pallet trucks, forklifts, etc.). In this regard, the embedded information core can be directly integrated into the industrial equipment's electronics, alone or in combination with other electronics. In alternative embodiments, the embedded information core is packaged in a housing that can be mounted, attached to, or otherwise mounted onto the corresponding industrial equipment.

[0051] In some embodiments, controller 230 includes a processor coupled to memory for implementing computer instructions, including relevant processes or aspects thereof, which are more fully set forth and described herein.

[0052] In addition, the memory of controller 230 may include memory for storing processing instructions and memory for data storage, such as memory for implementing one or more databases, data storage, registers, arrays, etc., as described in more detail herein.

[0053] The communication and control system 228 may optionally include one or more peripheral devices 238. In this regard, the peripheral devices 238 may be directly integrated into or integrated with the controller 230, or one or more peripheral devices 238 may be communicatively coupled to the controller 230. For example, in some embodiments, the controller 230 includes monitoring input / output (I / O) capabilities to communicate with any optional peripheral devices 238 mounted on or otherwise on industrial equipment via wired or wireless connections. In other embodiments, one or more peripheral devices 238 may be integrated with the communication and control system 228 or the controller 230.

[0054] Native device electronic devices As described above, in some embodiments, controller 230 may communicate with native device electronics 234, for example, via industrial device bus 236. For example, in some embodiments, controller 230 controls native circuitry, such as device power enable circuitry. Power enable circuitry is controlled by controller 230 to selectively enable or disable industrial equipment and / or selectively enable or disable selected components of industrial equipment. In some embodiments, controller 230 controls vehicle power enable circuitry to partially enable operation of industrial equipment or fully enable operation of the industrial vehicle, for example, depending on correct operator login or maintenance technician login. For example, power enable circuitry may provide selective power to components via appropriate power connections (e.g., relays) or command certain vehicle components not to respond to vehicle operator control via vehicle messages (e.g., across one or more vehicle communication buses).

[0055] Other example native device electronics include traction controllers, hydraulic controllers, steering or rudder controllers, other device controllers, energy (e.g., battery) management systems or monitors, native sensor systems (e.g., laser, impact, LiDAR, ultrasonic, etc.), position tracking systems, or other native vehicle electronics capable of communicating via Industrial Device Bus 236. Other example native device electronics may exemplarily include displays, light strips, alarms, sensor systems, navigation systems, IoT devices, data collection devices, user interaction devices, etc.

[0056] Peripheral equipment Example peripheral device 238 includes a SIM card or other cellular communication enabled device, such as via an optional long-range transceiver 244 (e.g., Wi-Fi, cellular, etc.), a global positioning system (GPS), an environment-based location tracking system (EBL), etc.

[0057] Other examples of peripheral devices 238 may include cameras, impact sensors, temperature or other sensors, lasers, meters, encoders, light strips, switches, Internet of Things (IoT) devices, displays, speakers, etc. Controller 230 may also communicate with one or more third-party peripheral devices 238 via wired or wireless connections, such as radio frequency identification (RFID) scanners, displays, barcode scanners, or other devices.

[0058] Other example peripheral devices 238, such as those that may be built into or otherwise integrated with the communication and control system 228, include display engines, camera processing engines, data processing engines, video ports, camera ports, input / output ports, and interfaces (e.g., Universal Serial Bus interfaces, Spring Pin interfaces, Bluetooth interfaces, Ultra Wideband Network interfaces, event stacks, processing stacks, configuration data management, client management, event management, etc.).

[0059] In a non-limiting overview, the industrial device bus 236 enables seamless integration of components of industrial equipment with the controller 230. Exemplarily, the controller 230 can facilitate information communication from any electronic peripheral device or third-party device, etc. Therefore, in some embodiments, the controller 230 can connect to, understand, and communicate with vehicle components such as controllers, modules, devices, bus-enabled sensors, displays, lights, light strips, sound-emitting devices, headsets, microphones, haptic devices, peripherals, etc.

[0060] bus In some embodiments, the industrial device bus 236 is any wired or wireless network, bus, or other communication capability (or a combination of multiple independent networks, buses, or other communication capabilities) that allows the electronic components of an industrial device to communicate with each other. As an example, the industrial device bus 236 may include one or more Controller Area Network (CAN) buses, Zigbee (a registered trademark of Connectivity Standards Alliance, a California company), Bluetooth, Local Interconnect Network (LIN), Time Triggered Data Bus Protocol (TTP), RS422, Ethernet, USB, other suitable communication strategies, or combinations thereof.

[0061] Short-range wireless transceiver In the illustrative example, controller 230 is communicatively coupled to, or optionally integrated with, at least one short-range wireless transceiver 232 for wireless communication. In practice, at least one short-range wireless transceiver 232 may implement one or more short-range wireless communication technologies, such as Bluetooth, ultra-wideband (UWB), infrared (IR), any other short-range wireless technology, or combinations thereof, i.e., non-Wi-Fi or cellular. Furthermore, each technology may include one or more antennas, for example, for redundancy, for location / positioning, for reliability, or combinations thereof.

[0062] As an illustrative example, the short-range wireless transceiver 232 may include communication technologies such as Bluetooth. This allows the controller 230 to communicate with nearby Bluetooth-enabled devices, for example, via a nearby processing device 202 (e.g., similar to...). Figure 1 The processing device 102) is paired with a portable processing device such as a smartphone, tablet, etc. In this regard, see reference... Figure 1 Any combination of features described in the processing device 102 can be incorporated into the processing device 202.

[0063] As another example, in addition to or instead of Bluetooth, the short-range wireless transceiver 240 may include an ultra-wideband (UWB) transceiver. The UWB transceiver can be used to create temporary local mesh networks to facilitate communication with other nearby UWB devices, such as anchors, tags, chat tags, or other processing devices 202 (e.g., UWB-equipped smartphones or tablets). Here, the UWB transceiver may optionally include multiple antennas (e.g., two or more antennas) so that the controller 230 can perform location, positioning, distance determination, distance, direction, and orientation measurements of the corresponding nearby UWB badges.

[0064] In an example embodiment, the short-range transceiver 232 is connected to the controller 230 via a suitable electrical connection (e.g., Ethernet connection, USB connection, bus connection (e.g., via industrial device bus 236), direct connection, etc.). In some embodiments, the short-range transceiver 240 may be integrated into the controller 230 using other connectivity methods, or the separate short-range transceiver 232 may be completely omitted from the communication and control system 228, for example, where the industrial device already includes a short-range transceiver 232 accessible by the controller 230 (e.g., included in native device electronics 234).

[0065] In other embodiments, multiple short-range transceivers 232 (or transceiver instances) may exist, for example, for different purposes, for redundancy, for supporting selected functions, for supporting different communication protocols or combinations thereof. For example, if Bluetooth is unavailable on a nearby smartphone for some reason, the system may default to UWB or some other short-range communication technology available on the smartphone.

[0066] Long-range transceiver In some embodiments, the communication and control system 228 may include or otherwise communicatively coupled to an optional long-range transceiver 244, such as Wi-Fi, cellular (including 5G radio for communicating with 5G networks), etc. For example, a long-range transceiver 244 may be able to communicate with a remote server (e.g., server 212 across network 204 via 802.11) via network 204. Here, server 212 may be similar to Figure 1 Server 112, network 204 can be similar to Figure 1 Network 104. In industrial environments, communication can be achieved through... Figure 1 Access point 110 proceeds to Figure 1 Server 112. An optional second cellular transceiver can communicate with a 5G router or other form of cellular-to-IP (Internet Protocol) bridge to communicate directly with remote server 212 using cellular signals.

[0067] mark As shown in the figure, the processing device 202, such as a portable processing device implemented as a smartphone or tablet, is capable of interacting with the tag 250, such as an image, QR code, barcode, RFID chip or some other magnetic chip, smart tag, reflector, or some other tag that the processing device 202 can read by contact or non-contact means. In some embodiments, the tag 250 is associated with a corresponding industrial device, examples of which are described in more detail herein.

[0068] Operator-Industrial Equipment Interaction refer to Figure 3 Using the infrastructure described with reference to the foregoing figures, an example of operator interaction is described. Figure 3 In, with Figure 2 Similar structures are represented using the same reference numerals that are 100 higher. Similarly, in Figure 3 In, with Figure 1 Similar structures are represented using the same reference numerals that are 200 higher. Therefore, Figure 1 and Figure 2 The discussion adopted any combination of components, structures, features, etc. Figure 3 In the description.

[0069] Similar to the previously described system, mobile processing device 302, such as a smartphone, tablet, etc., includes a transceiver for communicating with a remote server 312 and a corresponding platform 314 via Wi-Fi or cellular. Mobile processing device 302 may also include a transceiver, such as a short-range transceiver like Bluetooth, UWB, RFID, optical, near-field communication, etc., capable of communicating with a corresponding transceiver on industrial equipment 326.

[0070] In short, in some embodiments, industrial equipment 326 may be initially disabled. For example, the industrial equipment's battery may power communication and control system 328. However, communication and control system 328 may include relays or other devices that prevent the industrial equipment from being powered to a normal operating state. This may be useful, for example, in situations where a reservation system is enabled (e.g., reserving certain industrial equipment for certain operators). With such a reservation system provided, the application may display appropriate messages in response to a user attempting to log in, such as "Reserved by operator 1234" (or some message that allows the individual to understand why access is denied). In some embodiments, optional override may be provided, for example, in cases where an operator who has made a reservation for the industrial equipment is unable to attend. This can be as simple as administratively canceling a reservation, or it may have a generic login that takes precedence over reservation requests.

[0071] In some embodiments, the communication and control system 328 may provide, for example, over-control for emergency purposes, which may allow, for example, the industrial equipment bus 236 to be activated for a short period of time (e.g., 5-15 minutes) to enable the industrial equipment to be moved, etc.

[0072] Furthermore, industrial device 326 can be enabled for normal operation in response to successful pairing with an operator's mobile processing device 302 (e.g., smartphone, tablet, etc.). Therefore, before an operator near industrial device 326 can operate the device, the operator must perform a successful login operation by pairing their mobile processing device 302 with industrial device 326. In this regard, industrial device 326 is operably configured to require the operator's mobile processing device 302 to obtain a pairing key from platform 314.

[0073] In some embodiments, the mobile processing device 302 may remember a pairing code from a previously logged-in industrial device 326. In other embodiments, the mobile processing device 302 may forget the pairing code, or the pairing code may be changed, requiring a complete pairing operation for each login. That is, unlike many Bluetooth devices that "remember" logins and login credentials, the industrial device 326 may need to obtain new pairing parameters each time it attempts to log in. In a further embodiment, after a successful login, the operator's mobile processing device 302 may retain the ability to automatically log in for a limited time (e.g., during an 8-hour shift after a successful login). This would allow the operator to temporarily go beyond the distance boundaries of the connection (e.g., Bluetooth) with the industrial device and still quickly regain access upon immediate return.

[0074] As shown in the figure, industrial equipment 326 includes a tag 350. The tag may include, for example, an image, a QR code, a barcode, a magnetic stripe, a reflector array, an RFID chip, or other configurations that can be used as identifiers for remote electronic devices (e.g., an operator's mobile processing device 302). For example, for clarity only, tag 350 is illustrated as a QR code. By reading the tag (e.g., scanning the QR code with a camera on the operator's mobile processing device 302), the operator's mobile processing device 302 can identify the industrial equipment 326 of interest.

[0075] The operator's mobile processing device 302 detects the industrial equipment 326 and optionally identifies the operator to the remote server 312 and platform 314.

[0076] Then, platform 314 returns an access response to the operator's mobile processing device 302.

[0077] In an example embodiment, if an operator is authorized to operate the identified industrial device 326, the platform 314 then returns the information required to pair with the industrial device 326 to the operator's mobile processing device 302, thereby enabling access to and operation of the industrial device 326.

[0078] For example, the information required to pair with industrial device 326 may include unique discovery parameters, access codes, pairing codes, passwords, etc. It is noteworthy that this information (e.g., discovery parameters, access codes, pairing codes, or passwords) is known to communication and control system 328. For example, industrial device 326 (e.g., via a transceiver on communication and control system 328) may already know the unique discovery parameters, access codes, pairing codes, passwords, etc. In other embodiments, platform 314 transmits the unique discovery parameters, access codes, pairing codes, passwords, etc., to industrial device 326.

[0079] Therefore, the system of this paper can use discovery parameters, access codes, pairing codes or passwords to establish a paired wireless connection between the operator's mobile processing device 302 and the communication and control system 328, and then use the paired wireless connection to wirelessly communicate information between the operator's mobile processing device 302 and the communication and control system 328.

[0080] More specifically, industrial equipment 326 (e.g., similar to...) Figure 1 Industrial equipment 126) includes communication and control systems 328 (e.g., similar to...). Figure 1 Communication and control systems 128 and / or Figure 2 The communication and control system 328 is capable of communicating with the mobile processing device 302 (e.g., similar to...). Figure 2 Processing device 202; Figure 1 The processing device 102 communicates with the other party, as will be described in more detail herein.

[0081] In practical applications, the marking 350 (similar to...) Figure 2 The tag 350 can be located at any desired location on the industrial equipment 326. Although schematically shown as a QR code, in practice, the tag 350 can be any tag that the corresponding nearby mobile processing device 302 can read, for example, by contact or non-contact means, as described more fully herein.

[0082] In this respect, "nearby" means within the range of communication capabilities between the operator's mobile processing device 302, camera, RFID reader, UWB device, etc., and the communication and control system 328 and the corresponding mobile processing device 302.

[0083] Serial, multimodal access control Operators can use Figure 3 The entire system shown (optionally combined) Figure 1 and / or Figure 2 The features described in the text can be combined to execute serial, multimodal industrial equipment access control schemes.

[0084] For example, in its initial state, industrial equipment 326 may be disabled or partially disabled. For example, see reference... Figure 2The native vehicle electronics may include power-enabling circuitry or other features that lock the industrial device 326 out of normal operation until and unless a corresponding controller within the communication and control system 328 of the industrial device 326 confirms successful login, and / or until and unless platform 314 confirms successful login. As noted more fully herein, in some embodiments, the industrial device 326 may not be able to natively perform direct communication with platform 314 because the industrial device 326 lacks a suitable Wi-Fi transceiver or cellular transceiver.

[0085] However, at T1, the operator can use the mobile processing device 302 to identify the tag 350 by interacting with it using appropriate technology on the mobile processing device 302 (e.g., scanning a QR code as shown). For example, the tag 350, which is implemented as a QR code on the industrial equipment 326, can be scanned using a camera on the mobile processing device 302. In practice, other methods can be used to read the tag, such as near field communication (NFC), radio frequency identification (RFID), barcodes, etc.

[0086] In some embodiments, the operator's mobile processing device 302 displays an identification of the industrial equipment. This allows the operator to perform manual checks to ensure that the operator is located at the correct or designated industrial equipment.

[0087] Here, the label 350, such as a barcode, QR code, etc., does not need to be co-located with the industrial equipment 326. Instead, the barcode, QR code, etc., can be on the equipment itself, or in a place easily accessible to the operator's mobile processing device 302 (e.g., a smartphone).

[0088] In some embodiments, at T2, the operator's mobile processing device 302 transmits the information obtained from the read tag 350 to the remote server 312. For example, communication between the mobile processing device 302 and the remote server 312 may be performed by a special application running on the mobile processing device 302. This application may require the operator to have previously logged into the application, provided credentials, etc., using an appropriate user authentication scheme, such as username, password, two-factor authentication, etc.

[0089] In some embodiments, the graphical user interface on the operator mobile processing device 302 requires the operator to actively manipulate controls, such as pressing a virtual button, to send communication to the remote server 312. In other embodiments, the application may automatically send requests to the remote server 312.

[0090] In any case, in response to receiving communication from the mobile processing device 302 via the remote server 312, the platform 314 can transmit an access response back to the mobile processing device 302 via the remote server 312. For example, the access response may include pairing data (e.g., information such as unique discovery parameters, access codes, pairing codes, passwords, PINs, etc., as described more fully herein), wherein the operator is authorized by the platform 314 to operate industrial equipment 326 with a tag 350 scanned by the mobile processing device 302.

[0091] Authorization can be based on platform 314 identifying correct operator information, compliant qualifications, appropriate training instructions, and good condition indications. Authorization can also be based on environmental factors, such as the location of the industrial equipment. As another example, authorization can be based on other factors, such as schedules, shifts, time of day, and equipment availability. For example, an operator may request access to industrial equipment during a shift (e.g., 8 hours). However, the industrial equipment may already be booked by another operator, or it may be scheduled for planned maintenance, battery charging, etc. In these respects, access can be denied, restricted, or modified. Furthermore, authorization can be based on the condition or factors of the industrial equipment, such as battery level and health status. In other embodiments, authorization is based on any combination of the above.

[0092] Conversely, in the event of access denial, platform 314 may return an access response that denies the authorization request. Additionally, platform 314 may optionally transmit other information, such as instructions, timestamps, time limits for completing login, etc.

[0093] In some embodiments, the mobile processing device 302 communicates directly with the communication and control system 328. For example, in an example embodiment, at T3, with authorization from platform 314, the mobile processing device 302 can use pairing data received from platform 314 to initiate communication with the communication and control system 328 of the industrial equipment 326.

[0094] In some embodiments, the communication and control system 328 knows the discovery parameters, access code, pairing code, password, PIN, etc. required to pair with the mobile processing device 302. In some embodiments, at T4, the communication and control system 328 obtains the discovery parameters, access code, pairing code, password, PIN, etc. required to pair with the mobile processing device 302.

[0095] In another embodiment, direct communication between the mobile processing device 302 and the communication and control system 328 is not required (i.e., communication at T3 is optional).

[0096] Therefore, in alternative embodiments, such as industrial device 326, an optional long-range transceiver (e.g., Figure 2In the case of 244), the communication and control system 228 can communicate with the platform 314, for example for additional authentication, obtaining corresponding pairing data, transmitting pairing confirmation, recording logs of operator pairing attempts, etc.

[0097] Therefore, in the example embodiment, pairing is handled indirectly by platform 314, for example by sending an acknowledgment to mobile processing device 302 via T2, and by platform 314 sending an acknowledgment to communication and control system 328 via T4.

[0098] In response, industrial device 326 may be automatically enabled for normal operation, or industrial device 326 may be enabled manually by an operator, for example by responding to a key-on operation or activation initiated by another operator.

[0099] In this way, serial, discrete steps / events are required for the mobile processing device 302 to communicate with the industrial equipment, such as T1, T2, T3, T4 (or any combination thereof) mentioned above.

[0100] Furthermore, the entire process can be multimodal. For example, the mobile processing device 302 needs a tag reading mode (e.g., a camera reading a QR code, etc.). The mobile processing device 302 also needs a long-range communication mode, such as a Wi-Fi transceiver or cellular transceiver communicating with a remote server 312 via a wireless network. Additionally, the mobile processing device 302 may need a short-range communication mode (e.g., Bluetooth) to pair with the communication and control system 328 (e.g., via a short-range transceiver of the communication and control system 328, an example of which is shown in...). Figure 2 (As described in the description).

[0101] However, industrial device 326 only needs to be associated with tag 350 and optionally has transceiver capabilities such as Bluetooth, UWB, Wi-Fi, cellular, or combinations thereof.

[0102] Following the brief introduction, this paper provides a more comprehensive description of examples of serial, multimodal access control and subsequent interactions between the mobile processing device 302 and the industrial equipment 326.

[0103] smartphone applications In some embodiments, the operator loads the application onto a mobile processing device 302, such as a smartphone, tablet, etc. The application includes manufacturer-specific programming for handling operator-side actions during the process described herein. Opening the application may require the operator to log in, register, or otherwise identify themselves to the application.

[0104] In this regard, operators may be required to log in to platform 314 before attempting to access industrial equipment. For example, the application may include a first graphical user interface that enables operators to log in to platform 314 using an operator ID and password, two-factor authentication, or other access protocols.

[0105] Using a mobile processing device 302 (e.g., a smartphone), an operator identifies an industrial piece of equipment 326 that the operator intends to use. This is achieved by using the mobile processing device 302 to sense, scan, or otherwise detect an identifier 350 associated with the industrial equipment 326. In practical applications, an application running on the mobile processing device 302 accesses the camera of the mobile processing device 302 to scan the tag 350 (e.g., a barcode, QR code, etc.). Here, the tag 350 may be on the equipment itself or in a location easily accessible to the mobile processing device 302.

[0106] Brief Reference Figure 4 The illustration shows a mobile processing device 402. The mobile processing device 402 is similar to... Figure 3 Mobile processing device 302; Figure 2 The mobile processing device 202; and Figure 1 The mobile processing device 102. The mobile processing device 402 runs an application that displays a graphical user interface 460, which can be used to display information related to the use of industrial equipment and / or perform many different functions related to the use of industrial equipment.

[0107] For example, once the application scans or otherwise identifies a device, the application can display a photo / image 462 of the industrial device 326 via a graphical user interface 460, for example, so that the operator can confirm that the scanned mark corresponds to the correct industrial device.

[0108] In some embodiments, the graphical user interface 460 may display data 464 about the device (e.g., brand, model, ID, etc.). In some embodiments, some operational data may also be displayed graphically. For example, remaining battery power, scheduled appointments, maintenance information, etc., enabling the operator to decide whether to continue logging into the industrial equipment.

[0109] In some embodiments, the graphical user interface 460 may provide buttons or other markers to send an "access request" 466 to a remote server (e.g., via Wi-Fi). In some embodiments, the application combines the identified device with the operator's identifier. This could be an ID code assigned by a company employer, a personal identification number, a login name the operator previously used to log in to the application, or other identifiers of the operator, etc.

[0110] The graphical user interface 460 may also include a "back" button so that instead of attempting to log in, users can return and select a different device.

[0111] Assuming the operator selects access request 466, the remote server 312 (e.g., via platform 314) verifies whether the operator has the appropriate credentials to use the device. For example, some devices require an individual to obtain a certificate or proof of appropriate training before using the device. The remote server may also verify whether the device is available for use. For example, the device may have been reserved by another user, locked for scheduled maintenance, scheduled battery charging, etc.

[0112] In some embodiments, the remote server returns an acknowledgment to the operator's application, which may include authorization to log in to the device or an indication that the operator is not authorized to use the device. Here, the application can provide indications regarding whether the server has authorized the operator or whether there are problems with the login attempt.

[0113] If the remote server authorizes the operator, the application and industrial equipment pair, for example, using Bluetooth. Once correctly paired, the industrial equipment is enabled for operation by the operator. Pairing can be performed by the application retrieving a pairing code from the confirmation, such as discovery parameters, personal identification numbers, or other codes that enable the application on mobile processing unit 402 to pair with the industrial equipment.

[0114] In some embodiments, before enabling the use of industrial equipment, the system may require the operator to perform checks, complete checklists, verify calibrations, verify operability, or perform other actions that may be required by the appropriate environment. In this regard, the mobile processing device 402 may include additional screens / graphical user interface screens as required by the application.

[0115] For example, in an example embodiment, once an operator logs into the industrial equipment, the industrial equipment and a smartphone can communicate, for example, via a Bluetooth link. Therefore, the mobile processing device 402 can be used to perform various functions. One example function is using a pre-checklist. The smartphone can then use its wireless, cellular, or other suitable radio to transmit the results of the checklist to a remote server (e.g., Figure 3 Server 312; Figure 2 Server 212; Figure 1 (Server 112). Industrial equipment may also include a basic display so that the equipment status can be easily seen on the equipment itself. In addition, smartphones can be used as an interface to perform maintenance tasks, such as executing maintenance checklists, calibrations, etc.

[0116] Back Figure 3In some embodiments, industrial equipment 326 can send information to an operator's mobile processing device 302 for display on the display screen of the mobile processing device 302. For example, battery or energy levels, timers, speed, or other data accessible to the controller of the communication and control system 328 can be passed to an application on the mobile processing device 302 for display. Such data can also be relayed from the mobile processing device 302 to the platform 314. Furthermore, in some embodiments, the mobile processing device 302 can collect data from the controller of the communication and control system 328, for example, by performing data logging operations. Here, the collected data can be relayed back to the platform 314. For example, the mobile processing device 302 can be used as a relay to relay event codes, status information, battery or energy levels, impact detection information, etc.

[0117] Similarly, in some embodiments, once paired, platform 314 can utilize mobile processing device 302 as a processor for industrial equipment and / or relay information to industrial equipment. For example, platform 314 can utilize mobile processing device 302 as an intermediary to transmit information to the controller of communication and control system 328. As a further example, platform 314 can transmit pre-inspection checklists, operator lists, maintenance checklists, etc., to mobile processing device 302. Mobile processing device 302 can then manipulate this information, for example, by displaying the checklists, operator lists, maintenance checklists, etc., using the display of mobile processing device 302, or mobile processing device 302 can act as a relay or intermediary to pass such information from platform 314 to the controller of communication and control system 328.

[0118] As another example, operational configurations, such as controller setpoints or other operational data, can be transmitted from platform 314 to the controller of communication and control system 328 using mobile processing device 302 as an intermediary. The controller of communication and control system 328 can then use the received information to modify the performance of industrial equipment 326.

[0119] In some embodiments, if pairing is interrupted, for example, when the operator leaves industrial equipment 326, the application automatically deregisters the operator from industrial equipment 326. In some embodiments, the operator can use the application to "book" industrial equipment 326, allowing the operator to establish, interrupt, and re-establish pairing with the industrial equipment during the booking window. In some embodiments, for example, where the operator is a picker who must occasionally leave the industrial equipment (e.g., to retrieve items), if the disconnection of the pairing connection does not time out (e.g., a few minutes, some programmable amount of time, a fixed amount of time, etc.), the communication and control system 328 will automatically re-pair with the operator's mobility processing device 302.

[0120] As a further example, the capabilities of the operator's mobile processing device 302 can be utilized to collect additional data. For example, a mobile processing device 302, such as a smartphone, typically has built-in GPS, accelerometer, and / or other sensing capabilities. When the operator's mobile processing device 302 is paired with industrial equipment 326, the application can use GPS, etc., to track the location of industrial equipment 326.

[0121] In a further embodiment, the application can be used to retrieve information about industrial equipment from a remote server. For example, service technicians can read timers, service history, or other information stored on the remote server. Operators can check battery levels, usage history, or other information provided back to the remote processing device by the remote server.

[0122] Application Functions In some embodiments, the application may include a graphical user interface to access operator manuals, learn about the characteristics or limitations of an industrial device that the operator has logged into, and learn about optional accessories, etc. Here, information may come from industrial devices, for example via Bluetooth, or data may be accessed from the platform by a smartphone.

[0123] In some embodiments, the application includes a graphical user interface that provides a dashboard to perform certain operator functions, such as executing checklists, executing maintenance checklists, checking the status of industrial equipment, etc. For example, the application may include a graphical user interface that displays widgets or other graphical representations for BDI, timers, error status, etc.

[0124] In a further example embodiment, such as in the case of providing an impact sensor on an industrial device, a small component for impact information may be provided.

[0125] Access with location tracking According to the example configuration, a registered operator using a mobile processing device 302 (e.g., a smartphone) scans a marker 350 (e.g., a QR code) at T1 to obtain a unique industrial equipment identifier. At T2, the mobile processing device 302 sends a request to the platform 314, which includes a request to unlock the industrial equipment. This request may include operator information, the obtained industrial equipment identifier, and other optional information, such as environmental information. In some embodiments, the mobile processing device 302 may send further information to the platform 314, such as location information, industrial equipment information (e.g., checklist results, industrial equipment status information, etc.). In some embodiments, the platform 314 returns information about the industrial equipment to the mobile processing device 302, such as battery level, equipment status, etc. If the platform 314 authorizes the operator, the operator can begin using the industrial equipment.

[0126] For example, the mobile processing device 302 may be able to pair with and enable direct communication with the industrial device 326, thereby sharing information between the operator's processing device 302 and the industrial device 326. In other embodiments, the operator's mobile processing device 302 does not need to be paired with the industrial device 326. For example, the platform 314 may implement a computer-implemented rule engine or other logic to determine whether to enable the industrial device 326 for operator operation. As an example, the platform may utilize information received from the operator's mobile processing device 302, such as operator information, device identification, the location of the industrial device 326, environmental information, etc., to determine whether to enable the operator to use the industrial device 326. In this regard, in some embodiments, if authorized, the platform 314 transmits electronic signals directly to the industrial device 326 to enable the industrial device to operate. In some embodiments, the platform 314 requires proper operator authentication (e.g., as described above) and a completed checklist before enabling the industrial device 326 for operator operation. However, in this example embodiment, the operator's mobile processing device 302 and the industrial equipment 326 do not need to be paired or even share information while the operator is using the industrial equipment 326.

[0127] Optionally, at triggers or intervals (e.g., every minute; some programmed interval; based on certain other triggers, such as detected events; based on requests from a remote server; combinations thereof), industrial equipment can send status information, such as location, industrial equipment status (e.g., battery level, health status, etc.), to platform 314, for example, via a long-range communication device. In some embodiments, this status information can be transmitted to the platform, for example, at T4, without passing through the operator's mobile processing device 302.

[0128] Exemplary access with Bluetooth In another example configuration, a registered operator using mobile processing device 302 turns on Bluetooth on mobile processing device 302 and places a smartphone within a certain range (e.g., 1-5 meters) of the industrial equipment. The operator then scans marker 350 at T1. Mobile processing device 302 and industrial equipment pair via Bluetooth at T3 (and optionally via initial authorization at T2, as described more fully above). For example, mobile processing device 302 may send a request to platform 314 at T2, which includes a request to unlock the industrial equipment. This request may include operator information, the obtained industrial equipment identifier, and other optional information such as environmental information.

[0129] In some embodiments, an application on a smartphone can unlock industrial equipment, for example, via an "unlock button" within the application's graphical user interface, without requiring direct authorization from platform 314.

[0130] In this example embodiment, industrial device 326 is unlocked when the operator presses the unlock button on the application, thereby initiating communication with industrial device 326 (directly, at T3, or indirectly, for example, via T2 and T4).

[0131] In some embodiments, the mobile processing device 302 can receive information about industrial equipment from the platform 314, such as location feedback information, industrial equipment information (e.g., checklist), and industrial equipment status information, such as battery level and equipment status.

[0132] Optionally, at triggers or intervals (e.g., every minute; some programmed interval; based on certain other triggers, such as detected events; based on requests from a remote server; combinations thereof), industrial equipment 326 may send status information, such as location and industrial equipment status (e.g., battery level, health status, etc.), to platform 314, for example, via a long-range communication device. In some embodiments, this status information may be transmitted to platform 314 without passing through the operator's mobile processing device 302.

[0133] In some embodiments, Bluetooth can be used as an alternative to tag 350 (e.g., QR code) or as a redundant backup system, for example, in case the QR code cannot be scanned correctly.

[0134] In some embodiments, an application and / or platform 314 on the mobile processing device 302 (e.g., a smartphone) controls access, allowing an operator to access only one industrial device at a time. Here, the platform 314 on the server 312 can implement decision logic that detects whether the operator is currently logged into an industrial device. If so, the platform can reject additional access attempts. As another example, if the mobile processing device 302 detects that it is already paired with the first industrial device, it can take appropriate action. Appropriate action may include issuing a message to first log out of the first industrial device; automatically logging the operator out of the first industrial device; or taking some other action to trigger a pairing request failure until the operator logs out of the first industrial device, etc.

[0135] Device pairing refer to Figure 5 This document provides a process 500 for pairing a mobile processing device (e.g., a handheld device, such as a smartphone, tablet, etc.) with industrial equipment, according to various aspects thereof. Process 500 can be performed, for example, using any hardware and / or software described in any combination with reference to any of the foregoing figures.

[0136] Process 500 is executed by reading a tag at 502. As an example, process 500 can be executed by reading a tag associated with an industrial equipment to be used by an operator at 502 by hardware on a mobile processing device (e.g., a smartphone).

[0137] As a non-limiting example, reading the tag at 502 can be performed by accessing a reader on a mobile processing device to obtain information related to the industrial equipment. As a further example, accessing a reader on a mobile processing device to obtain information related to the industrial equipment may include accessing a camera on the mobile processing device to capture images associated with the industrial equipment.

[0138] As a further example, accessing a reader on a mobile processing device to obtain information related to industrial equipment may include scanning at least one of a barcode or a QR code by a camera.

[0139] Process 500 also includes extracting the identifier at 504. As an example, the identifier can be extracted by extracting the electronic identifier of the industrial equipment from the tag, as described more fully in this article.

[0140] Process 500 also includes transmitting an authorization request at 506. For example, the authorization request communication can be transmitted from a mobile processing device to a remote server to request authorization to operate industrial equipment. For example, in an example embodiment, transmitting the authorization request at 506 may include transmitting the authorization request from the mobile processing device to a remote server to request authorization to operate industrial equipment, wherein the authorization request includes an electronic identifier of the industrial equipment and an identifier of the operator who wishes to operate the industrial equipment.

[0141] In this regard, the electronic identifier of the industrial equipment and the operator's identifier do not need to be transmitted to the remote server in the same message. For example, the information can be separated as described more fully herein. Exemplarily, before the remote processing device reads the identifier, the operator may be required to log in to the remote server by launching an application on the remote processing device. Here, the remote server combines the operator identifier received upon login with the identifier of the industrial equipment to form an authorization request.

[0142] Furthermore, process 500 includes receiving an access response at 508. In an example embodiment, process 500 includes receiving an access response from a remote server at 508 in response to an authorization request, the access response allowing or denying operator access to the industrial equipment.

[0143] As illustrative examples, in response to an access response that allows an operator to access industrial equipment, the process may further include, at 510, the mobile processing device extracting pairing information from the access response, and / or at 512, using the extracted pairing information to pair the mobile processing device with one or more of the industrial equipment. Thus, for example, after successful pairing of the mobile processing device and the industrial equipment, the industrial equipment can be enabled for normal operation.

[0144] In some embodiments, pairing a mobile processing device with industrial equipment using extracted pairing information may include pairing the mobile processing device with industrial equipment using a Bluetooth pairing procedure.

[0145] In some embodiments, in response to an access response allowing an operator to access the industrial equipment, the process may further perform: setting the mobile device to a paired state, setting the industrial equipment to a paired state, graphically displaying a pairing acceptance icon on a selected one of the mobile device or the industrial equipment, and pairing the mobile processing device with the industrial equipment upon detecting activation of the pairing acceptance icon. In an example embodiment, after successful pairing of the mobile processing device and the industrial equipment, the industrial equipment is enabled for normal operation.

[0146] In some embodiments, in response to an access response that allows the operator to access the industrial equipment, the process further performs automatic pairing of the mobile device with the industrial equipment by a remote server.

[0147] Furthermore, in some embodiments, process 500 further includes triggering an indicator on the industrial equipment in at least one of the following situations: a pairing attempt, successful pairing, unsuccessful pairing, or any combination thereof. For example, the indicator may include at least one of light control, a message on a display, sound, haptic feedback, movement on the industrial equipment, or a combination thereof.

[0148] As one of several additional example optional processes, in response to an access response that allows an operator to access the industrial equipment, process 500 may additionally include retrieving pairing information at 510. For example, a mobile processing device may retrieve pairing information from the access response.

[0149] In response to an access response that allows the operator to access the industrial equipment, the process may further include pairing at 512. For example, process 500 may use the extracted pairing information to pair the mobile processing device with the industrial equipment.

[0150] After the mobile processing unit and the industrial equipment are successfully paired, the industrial equipment is activated for normal operation.

[0151] In some embodiments, such as before transmitting the authorization request at 506, process 500 may include receiving login credentials from the operator by the mobile processing device, which enables the operator to log in to a remote server. Here, the operator may be authenticated as a valid operator at the remote server before reading the tag associated with the industrial equipment to be used by the individual. In other embodiments, the operator credentials may be transmitted to the remote server at any time, simultaneously with or before transmitting the authorization request.

[0152] As another example, in some embodiments, process 500 may further require (e.g., via software code running on a mobile processing device (e.g., a smartphone)) that the operator must be certified as a valid operator before the mobile processing device transmits the authorization request from the mobile processing device to a remote server.

[0153] In other embodiments, process 500 may further require (e.g., via software code running on the mobile processing device) that the operator be authenticated as a valid operator by a remote server before returning an access response to the mobile processing device.

[0154] In some embodiments, the authorization request received from the remote server includes an access response. Here, in response to the access response allowing the operator to access the industrial equipment, process 500 may further include providing access, wherein the remote server verifies that the operator has a current certificate or credentials with appropriate training before the individual can operate the industrial equipment.

[0155] In some embodiments, transmitting the authorization request may further include transmitting information specifying the time block for which the industrial equipment is requested to be used. Here, process 500 may further include having a remote server verify that the industrial equipment is available throughout the entire time block requested by the authorization request before authorizing the use of the industrial equipment.

[0156] As another example, in some embodiments, verifying by a remote server that the industrial equipment is available for the entire time block requested by the authorization request may include rejecting the authorization request if the requested industrial equipment has already been reserved for an activity during the requested time block. As several examples, the activity may include at least one of the following: reserved by another user, locked for planned maintenance, or scheduled for battery maintenance.

[0157] In other embodiments, access may be permitted, but the remote server may modify the time window assigned to the user's device, for example, restricting the user's authorization to a time when the industrial equipment has not yet been assigned to another user, not yet assigned to maintenance, not yet assigned to battery charging, etc.

[0158] In some embodiments, receiving an access response from a remote server in response to an authorization request may include receiving an access denied response. Here, process 500 may further include: in response to access denied response, outputting a message indicating that access was not permitted on a display screen of the mobile processing device. This indication may further include attribute data displaying the reason for the access denied request.

[0159] In some embodiments, the industrial device is disabled before the mobile processing device is successfully paired with it. For example, the industrial device may be initially disabled until the mobile processing device is successfully paired with it. Once paired, the industrial device may be fully enabled, partially enabled (e.g., based on operator credentials), or enabled for a period of time, etc.

[0160] Further example implementations As another illustrative example, a process for pairing a mobile processing device with industrial equipment is provided.

[0161] The process includes launching a device interface application within the operating system of the mobile processing device.

[0162] The operations performed by the device interface application include: using the hardware on the mobile processing device via the authorization component to read the tag associated with the industrial equipment to be used by the operator, and extracting the electronic identifier of the industrial equipment from the tag.

[0163] The process also includes transmitting an authorization request from the mobile processing device to a remote server to request authorization to operate the industrial equipment. Here, the authorization request includes the electronic identifier of the industrial equipment and the identifier of the operator who wishes to operate the industrial equipment.

[0164] The process further includes receiving an access response from a remote server in response to an authorization request.

[0165] In response to an access response granting the operator permission to access the industrial equipment, the process further includes: the mobile processing device extracting pairing information from the access response and pairing the mobile processing device with the industrial equipment using the extracted pairing information. In this respect, after successful pairing of the mobile processing device and the industrial equipment, the industrial equipment is activated for normal operation.

[0166] In an example embodiment, reading a tag by hardware on a mobile processing device includes accessing a reader on the mobile processing device to electronically exchange information with the industrial equipment. Accessing the reader on the mobile processing device to electronically exchange information with the industrial equipment may include, for example, accessing a camera on the mobile processing device to capture images on the industrial equipment. As a further example, accessing the camera on the mobile processing device to capture images on the industrial equipment may include scanning at least one of a barcode or a QR code with the camera.

[0167] In some embodiments, the process further includes receiving login credentials from the operator by the mobile processing device, which enables the operator to log in to a remote server, wherein the operator must be authenticated as a valid operator at the remote server before reading the tag associated with the industrial equipment to be used by the operator.

[0168] Furthermore, in some embodiments, the process further includes requiring the operator to be authenticated as a valid operator by software code running on the mobile processing device before the mobile processing device performs communication to transmit the authorization request from the mobile processing device to a remote server.

[0169] Some implementations require that the operator's identifier be authenticated as a valid operator before returning the authorization request to the mobile processing device from a remote server.

[0170] In some embodiments, in response to an access response that allows an operator to access industrial equipment, the process further includes granting access only if the operator has a current certificate or credentials for appropriate training that allows access to the remote server, after which the operator uses the equipment.

[0171] Furthermore, in some embodiments, transmitting the authorization request further includes transmitting a time block requesting the use of the industrial equipment, and further includes, prior to authorizing the use of the industrial equipment, having a remote server verify that the industrial equipment is available throughout the entire time block requested by the authorization request. For example, verifying by the remote server that the industrial equipment is available throughout the entire time block requested by the authorization request may include: rejecting the authorization request if the requested industrial equipment has already been reserved for an activity within the requested time block, wherein the activity includes at least one of the following: reserved by another user, locked for planned maintenance, or scheduled for battery maintenance.

[0172] In some embodiments, receiving an access response from a remote server in response to an authorization request includes receiving an access denied response. Here, the process further includes: in response to the access denied response, displaying a message indicating that access is not permitted on a screen of the mobile processing device.

[0173] Furthermore, in some embodiments, the industrial device is initially disabled until the mobile processing device is successfully paired with it. In this arrangement, in response to an access response that allows access to the mobile processing device for use with the industrial device, the authorization component extracts pairing information for pairing the mobile processing device with the industrial device; and in response to an access response that disallows the operator from using the industrial device, it outputs a message to the mobile processing device indicating that access is not permitted.

[0174] Overview of Computer Systems refer to Figure 6 The schematic block diagram illustrates an exemplary computer system 600 for implementing the various processes described herein. The exemplary computer system 600 includes one or more (hardware) microprocessors (μPs) 610 and corresponding (hardware) memories 620 (e.g., random access memory and / or read-only memory), which are connected to a system bus 630. Information can be transferred between the system bus 630 and a local bus 650 for communicating with various input / output devices via a suitable bridge 640. For example, the local bus 650 is used to interface peripheral devices with one or more microprocessors (μPs) 610, such as storage devices 660 (e.g., hard disk drives); removable media storage devices 670 (e.g., flash drives, DVD-ROM drives, CD-ROM drives, floppy disk drives, etc.); I / O devices 680, such as input devices (e.g., mice, keyboards, scanners, etc.), output devices (e.g., monitors, printers, etc.); and network adapters 690. The above list of peripheral devices is illustrative and not intended to be limiting. Other peripheral devices may be suitably integrated into the computer system 600.

[0175] Microprocessor 610 controls the operation of exemplary computer system 600. Furthermore, one or more microprocessors 610 execute computer-readable code (e.g., stored in memory 620, storage device 660, a removable medium inserted into removable medium storage device 670, or a combination thereof, collectively or individually referred to as a computer program product) that instructs microprocessor 610 to implement the computer-implemented processes described herein.

[0176] The computer implementation of the process described in this paper can be implemented as a machine-executable process that executes on a computer system, for example, one or more processing devices ( Figure 1 Processing device 102; Figure 2 Processing device 202; Figure 3 Mobile processing device 302; Figure 4 The mobile processing device 402).

[0177] Therefore, exemplary computer systems or components thereof may implement processes stored on one or more computer-readable storage devices and / or computer-implemented processes, as described in more detail herein. Other computer configurations may also implement processes stored on one or more computer-readable storage devices and / or computer-implemented processes, as described in more detail herein. Computer program code for performing the operations of various aspects of this disclosure may be written in any combination of one or more programming languages. The program code may be executed entirely or partially on computer system 600. In the latter case, a remote computer may be connected to computer system 600 via any type of network connection (e.g., using network adapter 590 of computer system 600).

[0178] In implementing the various computer aspects of this disclosure, any combination of computer-readable media may be used. A computer-readable medium may be a computer-readable signal medium, a computer-readable storage medium, or a combination thereof. Furthermore, a computer-readable storage medium may be implemented in practice as one or more different media.

[0179] Computer-readable signal media are themselves transient propagating signals. Computer-readable signal media may contain computer-readable program code embodied therein, for example, as propagated data signals in baseband or as part of a carrier wave. More specifically, computer-readable signal media do not include computer-readable storage media.

[0180] A computer-readable storage medium is a tangible means / hardware capable of holding and storing programs (instructions) for use by or in connection with an instruction execution system, device, or apparatus (e.g., a computer or other processing apparatus as more fully described herein). It is important to note that a computer-readable storage medium does not include a computer-readable signal medium. Therefore, a computer-readable storage medium as used herein should not be construed as being itself a transient signal, such as radio waves or other freely propagating electromagnetic waves transmitted through a transmission medium.

[0181] Specific examples of computer-readable storage media (a non-exhaustive list) include: hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, portable computer storage devices, optical storage devices such as optical disc read-only memory (CD-ROM) or digital video discs (DVDs), or any suitable combination of the foregoing. In particular, computer-readable storage media include computer-readable hardware, such as computer-readable storage devices like memory. Here, computer-readable storage devices and computer-readable hardware are non-transient, physical, tangible implementations.

[0182] Non-transient means that, unlike transient propagating signals that cease to exist naturally, the contents of a computer-readable storage device or computer-readable hardware that defines the subject matter of the claim persist until subjected to external action. For example, program code loaded into random access memory (RAM) is considered non-transient because the content persists until subjected to actions such as power failure, overwriting, deletion, or modification.

[0183] Furthermore, since hardware includes the physical elements or components of the corresponding computer system, the hardware itself does not contain software.

[0184] Miscellaneous As illustrated, the platform and server (e.g., server 112, platform 114) are implemented as computers in the cloud. In practical applications, the server and the corresponding platform can be a processing device 102 on industrial equipment, a cloud-based remote computer server, a discrete authentication device, a server computer in a local area network, etc.

[0185] Furthermore, the term "pairing" should be interpreted broadly to include direct pairing, such as direct pairing between a mobile processing device and a controller / communication and control system on industrial equipment. An example of direct pairing is through technology such as Bluetooth. Pairing can also occur virtually, for example, by storing temporary associations between an operator or mobile processing device and the corresponding industrial equipment in a database via a server. Additionally, pairing can occur indirectly, for example, by issuing certificates, codes, PINs, or other linking attributes to the mobile processing device and / or the controller / communication and control system on the industrial equipment via a server.

[0186] Therefore, examples of the pairing process include: cases where pairing information is sent only to the mobile processing device; cases where the server places both the mobile device and the industrial vehicle into a pairing state, which may include a simple accept button displayed on the mobile device; and cases where the server automatically pairs the mobile processing device with the industrial equipment. Furthermore, in some embodiments, successful pairing can trigger indications such as lights (displays, pairing lights, headlights, blue lights, etc.), sounds (speakers, display prompts, etc.), rapid / brief forward / backward movement of the industrial equipment (e.g., when sensors indicate there are no obstacles around the industrial equipment), or combinations thereof.

[0187] The disclosure herein describes various aspects and / or embodiments that characterize different features, combinations of features, capabilities, etc. In this regard, unless such combinations are expressly excluded by this specification, the configurations claimed herein may cover any combination of one or more embodiments and / or aspects and / or features, and any of the accompanying drawings herein may be combined in any desired manner.

[0188] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the terms “comprising” and / or “including” as used in this specification specify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0189] The description in this disclosure is intended to be illustrative and descriptive, but is not intended to be exhaustive or limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of this disclosure.

[0190] Having described the embodiments of this application in such detail, it will be apparent that modifications and variations may be made without departing from the scope of the embodiments as defined by the appended claims.

Claims

1. A process for pairing a mobile processing device with industrial equipment, comprising: The hardware on the mobile processing device reads the tag associated with the industrial equipment that the operator intends to use; Extract the electronic identifier of the industrial equipment from the tag; An authorization request is transmitted from the mobile processing device to a remote server to request authorization to operate the industrial equipment. The authorization request includes an electronic identifier of the industrial equipment and an identifier of the operator who wishes to operate the industrial equipment. as well as In response to the authorization request, an access response is received from the remote server, which may allow or deny the operator access to the industrial equipment.

2. The process according to claim 1, wherein, In response to an access response that allows the operator to access the industrial equipment, the process further performs: The mobile processing device extracts pairing information from the access response; as well as The mobile processing device is paired with the industrial equipment using the extracted pairing information; in: After the mobile processing device and the industrial equipment are successfully paired, the industrial equipment is activated for normal operation.

3. The process according to claim 2, wherein, Pairing the mobile processing device with the industrial equipment using the extracted pairing information includes: The mobile processing device is paired with the industrial equipment using a Bluetooth pairing procedure.

4. The process according to any one of the preceding claims, wherein, In response to an access response that allows the operator to access the industrial equipment, the process further performs: Set the mobile device to a paired state; Set the industrial equipment to a paired state; A pairing acceptance icon is graphically displayed on a selected device in the mobile device or the industrial equipment. as well as When the pairing acceptance icon is activated, the mobile processing device is paired with the industrial equipment; in: After the mobile processing device and the industrial equipment are successfully paired, the industrial equipment is activated for normal operation.

5. The process according to any one of the preceding claims, wherein, In response to an access response that allows the operator to access the industrial equipment, the process further performs: The remote server automatically pairs the mobile device with the industrial equipment.

6. The process according to any one of the preceding claims further includes: The indicator on the industrial equipment is triggered in at least one of the following situations: pairing attempt, successful pairing, unsuccessful pairing, or any combination thereof.

7. The process according to claim 6, wherein, The indicator includes at least one of the following: Light control; Messages on the monitor; sound; tactile feedback; Movement on the industrial equipment; or Its combination.

8. The process according to any one of the preceding claims, wherein, The reading of the tag associated with the industrial equipment by the hardware on the mobile processing device includes: Access the reader on the mobile processing device to obtain information related to the industrial equipment.

9. The process according to claim 8, wherein, Accessing the reader on the mobile processing device to obtain information related to the industrial equipment includes: Access the camera on the mobile processing device to capture images associated with the industrial equipment.

10. The process according to claim 9, wherein, Accessing the reader on the mobile processing device to obtain information related to the industrial equipment includes: The camera scans at least one of a barcode or a QR code.

11. The process according to any one of the preceding claims further comprises: The mobile processing device receives login credentials from the operator, which enable the operator to be authenticated as a valid operator by the remote server before reading the tag associated with the industrial equipment the operator intends to use.

12. The process according to claim 11, further comprising: The software code running on the mobile processing device requires that the operator be authenticated as a valid operator before the mobile processing device can execute communication of an authorization request from the mobile processing device to a remote server.

13. The process according to claim 11, further comprising: The remote server requires that the operator's identifier be authenticated as a valid operator before returning the access response to the mobile processing device.

14. The process according to any one of the preceding claims, wherein, In response to an access response that allows an operator to access the industrial equipment, the process further includes: Access is provided to the operator prior to their use of the industrial equipment, provided the operator possesses current certification or proof of appropriate training that is accessible through the remote server.

15. The process according to any one of the preceding claims, wherein: Transmitting the authorization request further includes transmitting information specifying the time block in which the industrial equipment is requested; Further includes: Before authorizing the use of the industrial equipment, the remote server verifies that the industrial equipment is available throughout the entire time block requested by the authorization request.

16. The process according to claim 15, wherein, Verifying by the remote server that the industrial equipment is available throughout the entire time block requested by the authorization request includes: The authorization request is rejected if the requested industrial equipment has already been reserved for an activity within the requested time block, and the activity includes at least one of the following: Reserved by another user; Locked for planned maintenance; or Battery maintenance is planned.

17. The process according to any one of the preceding claims, wherein: Receiving the access response from the remote server in response to the authorization request includes receiving an access denied response; Further includes: In response to the access denial, a message indicating that access is not permitted is displayed on the mobile processing device's screen.

18. The process according to any one of the preceding claims, wherein: The industrial equipment is disabled before the mobile processing device is successfully paired with the industrial equipment.

19. A process for pairing a mobile processing device with industrial equipment, comprising: The device interface application is launched within the operating system of the mobile processing device, and the device interface application executes: The authorized component, using the hardware on the mobile processing device, reads the tag associated with the industrial equipment to be used by the operator; as well as Extract the electronic identifier of the industrial equipment from the tag; An authorization request is transmitted from the mobile processing device to a remote server to request authorization to operate the industrial equipment. The authorization request includes an electronic identifier of the industrial equipment and an identifier of the operator who wishes to operate the industrial equipment. as well as In response to the authorization request, an access response is received from the remote server, wherein the access response grants the operator permission to access the industrial equipment: The mobile processing device extracts pairing information from the access response; and The mobile processing device is paired with the industrial equipment using the extracted pairing information; in, After the mobile processing device and the industrial equipment are successfully paired, the industrial equipment is activated for normal operation.

20. The process according to claim 19, wherein, The authorized component reads the tag using hardware on the mobile processing device, including: Access the reader on the mobile processing device to electronically exchange information with the industrial equipment.

21. The process according to claim 20, wherein, Accessing the reader on the mobile processing device to electronically exchange information with the industrial equipment includes: Access the camera on the mobile processing device to capture images on the industrial equipment.

22. The process according to claim 21, wherein, Accessing the camera on the mobile processing device to capture images on the industrial equipment includes scanning at least one of a barcode or a QR code by the camera.

23. The process according to claim 19, further comprising: The mobile processing device receives login credentials from the operator, which enable the operator to log in to the remote server, wherein the operator must be authenticated as a valid operator at the remote server before reading the tag associated with the industrial equipment to be used by the operator.

24. The process according to claim 23, further comprising: The software code running on the mobile processing device requires that the operator be authenticated as a valid operator before the mobile processing device can execute communication of an authorization request from the mobile processing device to a remote server.

25. The process according to claim 23, further comprising: The remote server requires that the operator's identifier be authenticated as a valid operator before returning the authorization request to the mobile processing device.

26. The process according to claim 23, wherein, In response to an access response that allows an operator to access the industrial equipment, the process further includes: Access is provided to the operator prior to their use of the industrial equipment, provided the operator possesses current certification or proof of appropriate training that is accessible through the remote server.

27. The process according to claim 19, wherein, Transmitting the authorization request further includes transmitting the time block in which the industrial equipment is requested, and further includes: Before authorizing the use of the industrial equipment, the remote server verifies that the industrial equipment is available throughout the entire time block requested by the authorization request.

28. The process according to claim 27, wherein: Verifying by the remote server that the industrial equipment is available throughout the entire time block requested by the authorization request includes: rejecting the authorization request if the requested industrial equipment has already been reserved for an activity within the requested time block, the activity including at least one of the following: Reserved by another user; Locked for planned maintenance; or Battery maintenance is planned.

29. The process according to claim 19, wherein, Receiving the access response from the remote server in response to the authorization request includes receiving an access denied response; Further includes: In response to the access denial, a message indicating that access is not permitted is displayed on the mobile processing device's screen.

30. The process according to claim 19, wherein, The industrial equipment is initially disabled until the mobile processing device is successfully paired with the industrial equipment. in: In response to an access response granting permission for the mobile processing device to access the industrial equipment, the authorization component extracts pairing information for pairing the mobile processing device with the industrial equipment; and In response to an access response that disallows the operator from accessing the industrial equipment, a message indicating that access is not permitted is output to the mobile processing device.

Images